> Exec Mode Commands (A-C)
> This section includes the commands aaa test through crypto-group
> The Exec Mode is the initial entry point into the command line interface system. Exec mode commands are useful in troubleshooting and basic system monitoring.
> aaa test
> This command tests AAA functionality between the system and a remote server.
> Product
> PDSN, HA, GGSN, SGSN, ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> aaa test { accounting username user_name | authenticate user_name password | session user_name password }
> accounting username user_name
> Tests RADIUS or GTPP accounting functionality for the specified user.
> user_name is the name of a user configured on the RADIUS or CFG server.
> Important: GTPP is used only in conjunction with the GGSN or SGSN product.
> authenticate user_name password
> Tests RADIUS authentication functionality for the specified user.
> user_name is the name of a user configured on the RADIUS server. password is the user’s password.
> session user_name password
> Tests both RADIUS authentication and RADIUS or GTPP accounting functionality for the specified user.
> user_name is the name of a user configured on the RADIUS server. password is the user’s password.
> Important: GTPP is used only in conjunction with the GGSN or SGSN product.
> Usage
> This command is used to test RADIUS-based authentication and RADIUS or GTPP accounting. This command may be useful for diagnosing problems with subscribers and access to the system and/or billing data.
> Example
> The following command verifies accounting for a user called user1:
> aaa test accounting username user1
> The following tests authentication for a user called user1 with a password of abc123:
> aaa test authentication user1 abc123
> The following command will test both accounting and authentication for the user called user1 with a password of abc123:
> aaa test session user1 abc123
> active-charging service
> This command creates an active charging service.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> active-charging service ecs_service_name [ -noconfirm ]
> ecs_service_name
> Specifies the active charging service name.
> service_name must be an alpha and/or numeric string of 1 through 15 characters in length.
> If the named service does not exist, it is created, and the CLI mode changes to the Active Charging Service Configuration mode wherein the service can be configured.
> If the named service already exists, the CLI mode changes to the Active Charging Service Configuration mode wherein the service can be reconfigured.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to create an active charging service on the system. This command can be used directly in Exec-mode after issuing the require active-charging command in the Global Configuration mode.
> This command allows an operator (rather than security administrators and administrators) to configure the Enhanced charging service functionality only.
> Important: Operator needs the special CLI privilege for Enhanced charging service functionality to be able to use this CLI command.
> Example
> The following command creates an active charging service named test:
> active-charging service test
> alarm
> This command is used to disable the internal audible alarm on the system management card.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> alarm cutoff
> Usage
> Alarm cutoff disables the audible alarm. The alarm may be enabled following this command if an event within the system results in the audible alarm being enabled.
> Example
> alarm cutoff
> autoconfirm
> This command disables or enables confirmation for certain commands. This command affects the current CLI session only.
> Important: Use the autoconfirm command in the Global Configuration Mode to change the behavior for all future CLI sessions.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> autoconfirm
> no autoconfirm
> Usage
> When autoconfirm is enabled, certain commands ask you to answer yes or no to confirm that you want to execute the command. When autoconfirm is disabled, the confirmation questions never appear. Disabling autoconfirm is active for the current session only.
> By default autoconfirm is enabled.
> Example
> The following command enables command confirmation:
> autoconfirm
> The following command disables command confirmation for the duration of the current CLI session:
> no autoconfirm
> bulkstats force
> This command is used to manage the system statistics for collection and delivery to the configured server.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> bulkstats force { gather | transfer }
> gather
> Immediately collects the system statistics.
> transfer
> Immediately send the currently collected statistics to the configured server.
> Usage
> When the current system statistics are desired immediately as opposed to the normal scheduled collection and delivery intervals issue this command.
> Troubleshooting the system may require the review of statistics at times when the scheduled delivery is not timely.
> Example
> The following causes the chassis to immediately collect system statistics. This would be in anticipation of a transfer command.
> bulkstats force gather
> The following command causes the chassis to immediately send all collected statistics to the configured server.
> bulkstats force transfer
> card halt
> This command halts a card. A card reboot must be issued to bring the card back into service after it is halted.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card halt slot_num [ -force ] [ -noconfirm ]
> slot_num
> Indicates the slot number of the card of interest.
> -force
> Over-rides any warnings to force the card to be halted.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Halt a card to stop the card for maintenance or emergency situations.
> Caution: Caution should be taken in using this command as halting a card which has no redundancy card available may cause a service interruption and loss of active sessions.
> Caution: The -force and -noconfirm options should only be used concurrently by experienced users as this will cause an immediate halt regardless of warnings and no confirmation from the user.
> Important: This command is not supported on all platforms.
> Example
> The following command temporarily stops the card in slot 1.
> card halt 1
> The following commands force the card to halt and indicate no confirmation is to take place, respectively.
> card halt 17 -force -noconfirm
> card halt 17 -noconfirm
> card lc switch
> This is the command for managing the line cards and their active/standby status.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card lc switch to target_slot [ -noconfirm ]
> switch to target_slot
> Indicates the card which is to become the active card specified as target_slot.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Line card switch overs change the active/standby status of a line card. This is useful when there is a maintenance activity on the active card which requires removing the card from service.
> Caution: Caution should be taken in using this command. Depending on the amount of bandwidth/traffic being switched, some subscribers may experience service interruptions.
> Important: This command is not supported on all platforms.
> Example
> The following command switches the active/standby status of the line cards where one of the cards is in slot 17. This command only executes after the user provides confirmation of the request.
> card lc switch to 17
> The following switches the active/standby status of the line cards where one of the cards is in slot 17. This command executes immediately with no additional user confirmation.
> card lc switch to 17 -noconfirm
> card lc upgrade
> This command upgrades the programmables on the line card.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> card lc upgrade slot_number
> upgrade
> Upgrades programmables on the specified card. Must be followed by a slot number of card to upgrade.
> Caution: This command should only be used if instructed by or working with Technical Support.
> Usage
> This command upgrades the linear flash on the line card.
> Important: This command is not supported on all platforms.
> Example
> The following command initiates a lc upgrade:
> card lc upgrade
> card psc
> This command moves processes from the source PSC to the destination PSC or disables the PSC from accepting any new calls.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card psc { migratefrom src_slot to dst_slot | busy-out } [ -noconfirm ]
> no card psc busy-out
> no card psc busy-out
> Disables busy-out. The PSC is re-enabled to accept new calls.
> migrate from src_slot to dst_slot
> This keyword moves processes from the specified source PSC to the specified destination PSC. The command prompt is returned once the command is initiated. The card migration is completed in background.
> src_slot indicates the source slot number of the card whose processes will be migrated from. dst_slot indicates the destination slot number of the card processes will be migrated to.
> busy-out
> When busy-out is enabled on a PSC, the PSC stops receiving new calls but continues to process calls it currently has until they are completed. The command prompt is returned once the command is initiated. The busy-out procedure is completed in background.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Migrating a packet accelerator card changes the active/standby status of a packet accelerator card. This results in the active sessions/processes being moved to the newly active PSC. This is useful when there is a maintenance activity on the active card which requires removing the card from service.
> The destination slot specified must contain a packet accelerator card which is in the standby state for the command to complete successfully.
> Caution: Caution should be taken in using this command. Depending on the number of active sessions being migrated, some subscribers may experience service interruptions.
> Using busy-out to refuse new calls on a PSC allows you to take a card out of service without any interruptions to the end user. An individual system can be taken completely out of service gracefully by enabling busy-out on all PSCs and waiting for current calls to complete. The show card info command shows if busy-out is enabled.
> Important: When a PSC fails, is migrated, or is restarted for any reason busy-out is reset to disabled, the default behavior.
> Important: This command is not supported on all platforms.
> Example
> The following command migrates the active processes from the PSC card in slot 12 to the card in slot 14. This command only executes after the user provides confirmation of the request.
> card psc migrate from 12 to 14
> The following command sets the PSC in slot 1 to stop accepting new calls:
> card psc busy-out 1
> card psc upgrade
> This command upgrades the programmables on the PSC card.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> card psc upgrade slot_number
> upgrade
> Upgrades programmables on the specified card. Must be followed by a slot number of card to upgrade.
> Caution: This command should only be used if instructed by or working with Technical Support.
> Usage
> You can only initiate an upgrade if:

> • | there is no migration occurring

> • | the card is active or standby

> • | there is no online upgrade in progress

> Important: The following operations are not allowed while a card is upgrading: change pac edc requirement (config) change card [no] shutdown (config) change card active (config) change card redundancy (config) card halt (exec) card reboot (exec) start an online upgrade
> Important: Level unlock operations are ignored while a card is upgrading.
> Important: This command is not supported on all platforms.
> Example
> The following command initiates a PSC upgrade:
> card psc upgrade
> card reboot
> This performs a reset of the target card. Rebooting a packet processing or line card will result in the card downloading the image from the system management card.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card reboot target_slot [ -force ] [ -noconfirm ]
> target_slot
> Indicates the slot number of the card which is the target of the reboot.
> -force
> Indicates the reboot is to take place ignoring any state or usage warnings that might be generated.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> A reboot is used to reset the card and receive a new download. This may be useful when a card is not responding or when it is necessary to cause the card to reload its image and restart.
> Important: Caution should be taken in using this command as rebooting a card which has no redundancy card available may cause a service interruption and loss of active sessions.
> Caution: The -force and -noconfirm options should only be used concurrently by experienced users as this will cause an immediate reboot regardless of warnings and no confirmation from the user.
> Important: This command is not supported on all platforms.
> Example
> The following will cause the card in slot 8 to reboot without any confirmation from the user. The card will not reboot if there are any warnings generated.
> card reboot 8 -noconfirm
> The following command will cause the card in slot 8 to reboot regardless of any warnings. The user must provide confirmation prior to this command executing.
> card reboot 8 -force
> The following command will cause the card in slot 8 to reboot regardless of any warnings with no additional user confirmation.
> card reboot 8 -force -noconfirm
> card restart
> This performs a soft-reset of the target card causing all application processes to restart.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card restart target_slot [ -force ] [ -noconfirm ]
> target_slot
> Indicates the slot number of the card which is the target of the restart.
> -force
> Indicates the restart is to take place ignoring any state or usage warnings that might be generated.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Restarting a card may be useful when a card is not performing as expected (performance drop, increased response delays, etc.). A restart may be preferred to a reboot as the card becomes available in less time than a reboot.
> When this command is issued for an active card, the user is prompted for confirmation unless the -force and/or -noconfirm keywords are used. Because the reboot of standby or redundant cards is non-service impacting, the reboot proceeds immediately after the command execution without user confirmation.
> Important: Caution should be taken in using this command as restarting a card which has no redundant card available may cause a service interruption and loss of active sessions.
> Important: This command is not supported on all platforms.
> Caution: The -force and -noconfirm options should only be used concurrently by experienced users as this will cause an immediate restart regardless of warnings and no confirmation from the user.
> Example
> The following will cause the card in slot 8 to restart without any confirmation from the user. The card will not reboot if there are any warnings generated.
> card restart 8 -noconfirm
> The following command will cause the card in slot 8 to restart regardless of any warnings. The user must provide confirmation prior to this command executing.
> card restart 8 -force
> The following command will cause the card in slot 8 to restart regardless of any warnings with no additional user confirmation.
> card restart 8 -force -noconfirm
> card smc
> This is command is for managing the switch processor cards and their active/standby status and synchronizing the filesystem between the active device and the standby device.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> cardsmc { switchover | synchronize filesystem [ /flash | /hd | /pcmcia1 | all ] [ checkonly ] [ reverse ] } [ -noconfirm ]
> -noconfirm
> Executes the command without any additional prompt and confirmation from the user.
> switchover
> Switches control from the active SMC to the defined standby SMC.
> synchronize filesystem [ /flash | /hd | /pcmcia1 | all ] [ checkonly ] [ reverse ]
> /flash: Synchronizes only the filesystem on the standby SMC’s /flash device.
> /hd: Synchronizes only the filesystem on the standby SMC’s hard drive.
> /pcmcia1: Synchronizes only the filesystem on the standby SMC’s /pcmcia1 device.
> all: Synchronizes file systems on all available matching local devices (/flash, /pcmcia1).
> checkonly: Displays a list of files that could be synchronized, without executing any synchronization actions.
> reverse: When used, the specified operation is performed from the standby SMC to the active SMC.
> Usage
> The switch over of an SMC changes the active/standby status of an SMC card. This is useful when there is a maintenance activity on the active card which requires removing the card from service.
> Each SMC contains independent local devices, namely a CompactFlash (/flash) and a PCMCIA card slot (/pcmcia1). Either of these devices may contain system files such as binary software images, configuration text files, boot system files, and others used to control and manage the system. This command allows the files contained on the active (currently managed) SMC to be synchronized, or mirrored, on the like local device(s) contained on the standby SMC.
> Important: Only filesystems on matching local devices are synchronized. For example, if the active SMC contains two local devices (/flash and /pcmcia1) and the standby SMC contains only one local device (/flash), then synchronization only occurs on the matching local device (i.e. /flash).
> Important: This command is not supported on all platforms.
> Example
> The following command switches the active/standby status of the switch processor cards. This command only executes after the user provides confirmation of the request.
> card smc switchover
> The following command switches the active/standby status of the SMCs and executes immediately with no additional user confirmation:
> card smc switchover -noconfirm
> The following command synchronizes the filesystems on all available matching local devices (/flash, /pcmcia1):
> card smc synchronize filesystem all
> The following command checks to see what files could be synchronized but no synchronization is performed:
> card smc synchronize filesystem checkonly
> card smc upgrade
> This command updates the programmables on the SMC.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> card smc upgrade slot_number
> upgrade
> Upgrades programmables on the specified card. Must be followed by a slot number of card to upgrade.
> Caution: This command should only be used if instructed by or working with Technical Support.
> Usage
> You can only initiate an upgrade if:

> • | there is no migration occurring

> • | the card is active or standby

> • | there is no online upgrade in progress

> Important: The following operations are not allowed while a card is upgrading: change pac edc requirement (config) change card [no] shutdown (config) change card active (config) change card redundancy (config) card halt (exec) card reboot (exec) start an online upgrade
> Important: Level unlock operations are ignored while a card is upgrading.
> Important: This command is not supported on all platforms.
> Example
> The following command initiates a PSC upgrade:
> card psc upgrade
> Caution: This command should only be used if instructed by or working with Technical Support.
> card spio
> This is the command for managing the switch processor I/O cards and their active/standby status.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> card spio switch to slot# [ -noconfirm ]
> slot#
> The slot number of the SPIO card that you want to switch to be the active card. The currently active SPIO card is put in standby mode and the SPIO card in the specified slot number is made active.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Switch over changes the active/standby status of a SPIO card. This is useful when there is a maintenance activity on the active card which requires removing the card from service.
> Important: This command is not supported on all platforms.
> Example
> The following command switches the active/standby status of the switch processor I/O cards. This command only executes after the user provides confirmation of the request.
> card spio switch
> The following switches the active/standby status of the switch processor I/O cards. This command executes immediately with no additional user confirmation.
> card lc switch -noconfirm
> cdr-push
> This command initiates manual push of CDR files to L-ESS.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator, Inspector
> Syntax
> cdr-push { all | local-filename file_name }
> all
> Specifies to push all CDR files to the configured URL.
> local-filename file_name
> Specifies to push the specified file to the configured URL.
> file_name must be the absolute path of local file name to push, and must be a string of 1 through 1023 characters in length.
> Usage
> Use this command to manually push CDR files to the configured L-ESS.
> For information on configuring the L-ESS, see the cdr command in the EDR Module Configuration Mode Commands/UDR Module Configuration Mode Commands chapters.
> On ASR 5000 chassis, run this command only from the local context. If you are in any other context, you will see this failure message: “Failure: Manual PUSH of CDRs supported only in the local context”
> Example
> The following command pushes all CDR files to the URL:
> cdr-push all
> clear
> The following commands clear a variety of items including statistics, conditions, alarms, sessions, and files:
> clear aaa
> This command is used to clear all AAA statistics in the current context.
> Product
> PDSN, GGSN, ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear aaa local counters
> Usage
> Clearing the AAA statistics which may be useful when monitoring the statistics manually. Clearing resets the counters to zero.
> The keyword local is not intended to imply the local context defined for all systems. Rather, the keyword local indicates the statistics within the current context are to be cleared.
> Example
> The following command zeroes out all the AAA statistics in the current context.
> clear aaa local counters
> clear active-charging analyzer statistics
> This command is used to clear protocol analyzer statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging analyzer statistics [ name protocol_name ] [ | { grep grep_options | more } ]
> name protocol_name
> Clears statistics for the specified protocol analyzer.
> If this keyword is not specified all statistics are cleared.
> protocol_name must be one of the following:

> • | dns

> • | file-transfer

> • | ftp

> • | http

> • | icmp

> • | icmpv6

> • | imap

> • | ip

> • | ipv6

> • | mms

> • | p2p [ application ]: Peer-to-peer analyzer. The supported applications are:

> • | actsync

> • | aimini

> • | applejuice

> • | ares

> • | battlefld

> • | bittorrent

> • | ddlink

> • | directconnect

> • | edonkey

> • | fasttrack

> • | feidian

> • | filetopia

> • | freenet

> • | fring

> • | gadu_gadu

> • | gnutella

> • | halflife2

> • | hamachivpn

> • | iax

> • | imesh

> • | iptv

> • | irc

> • | iskoot

> • | jabber

> • | manolito

> • | msn

> • | mute

> • | nimbuzz

> • | openft

> • | orb

> • | oscar

> • | paltalk

> • | pando

> • | pandora

> • | popo

> • | pplive

> • | ppstream

> • | qq

> • | qqgame

> • | qqlive

> • | quake

> • | rdp

> • | secondlife

> • | skinny

> • | skype

> • | slingbox

> • | sopcast

> • | soulseek

> • | steam

> • | tvants

> • | tvuplayer

> • | uusee

> • | vpnx

> • | vtun

> • | warcft3

> • | winmx

> • | winny

> • | wofwarcraft

> • | xbox

> • | yahoo

> • | zattoo

> • | pop3

> • | pptp

> • | rtcp

> • | rtp

> • | rtsp

> • | sdp

> • | secure-http

> • | sip

> • | smtp

> • | tcp

> • | tftp

> • | udp

> • | wsp

> • | wtp

> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear active charging analyzers.
> Example
> The following command clears active charging service analyzer information for analyzer named tcp:
> clear active-charging analyzer statistics name tcp
> clear active-charging charging-action statistics
> This command is used to clear charging action statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging charging-action statistics [ name string] [ | { grep grep_options| more } ]
> name string
> Clears detailed information for specific protocol analyzer.
> string must be the name of an existing charging action.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear active charging action statistics.
> Example
> The following command clears active charging action statistics information for charging action named pre-paid:
> clear active-charging charging-action statistics name pre-paid
> clear active-charging content-filtering category statistics
> This command is used to clear category-based content filtering statistics for the specified rulebase.
> Product
> CF
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging content-filtering category statistics [ rulebase name rulebase_name| all ] [ | { grep grep_options| more } ]
> all
> Clears the statistics of each and every configured rulebase.
> rulebase_name
> rulebase_name must be the name of an existing rulebase, and must be an alpha and/or numeric string of 1 through 15 characters in length.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to category-based content filtering statistics.
> Example
> The following command clears category-based content filtering statistics information for Rulebase named cf_rule1:
> clear active-charging content-filtering category statistics rulebase name cf_rule1
> clear active-charging credit-control statistics
> This command clears credit control statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging credit-control statistics [ group group_name]
> group group_name
> Clears statistics for the specified credit control group. group_name must be the name of a credit control group, and must be an alpha and/or numeric string of 1 through 63 characters in length.
> Usage
> Use this command to clear credit control statistics.
> Example
> The following command clears statistics information for credit control:
> clear active-charging credit-control statistics
> clear active-charging edr-format statistics
> Clears the statistics for the specified EDR format.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging edr-format statistics [ name edr_format]
> name edr_format
> Specifies name of the EDR format for which you want to clear the statistics.
> edr_format must be the name of a configured EDR format, and must be an alpha and/or numeric string of 1 through 63 characters in length.
> Important: If an EDR format name is not specified statistics for all EDR formats are cleared.
> Usage
> Use this command to clear the accumulated statistics for the specified EDR format.
> Example
> The following command clears the statistics for all EDR formats:
> clear active-charging edr-format statistics
> clear active-charging edr-udr-file statistics
> This command is used to clear EDR/UDR file related statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging edr-udr-file statistics
> Usage
> Use this command to clear EDR and UDR file statistics.
> Example
> The following command clears statistical information for EDR and UDR files:
> clear active-charging edr-udr-file statistics
> clear active-charging firewall statistics
> This command clears Active Charging Stateful Firewall statistics.
> Product
> FW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging firewall statistics [ callid call_id | domain-name domain_name | nat-realm nat_realm | protocol { icmp | ip | other | tcp | udp } | username user_name ] [ acsmgr instance instance_id ] [ | { grep grep_options| more } ]
> acsmgr instance instance_id
> Specifies an ACS Manager instance ID.
> instance_id must be an integer from 1 through 65535.
> callid call_id
> Specifies a Call Identification number.
> call_id must be an eight-digit HEX number.
> domain-name domain_name
> Specifies a domain name for the statistics.
> domain_name must be a string of 1 through 127 characters in length.
> nat-realm nat_realm
> Specifies a NAT realm name for the statistics.
> nat_realm must be a string of 1 through 31 characters in length.
> protocol { icmp | ip | other | tcp | udp }
> Specifies protocol for the stats.

> • | icmp: ICMP protocol

> • | ip: IP protocol

> • | other: Protocols other than TCP, UDP, and ICMP

> • | tcp: TCP protocol

> • | udp: UDP protocol

> username user_name
> Specifies a user name for the statistics.
> user_name must be a string of 1 through 127 characters in length.
> grep grep_options | more
> Indicates that the output of the command is to be piped (sent) to the command specified. A command to send the output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear Active Charging Stateful Firewall statistics.
> Example
> The following command clears all Stateful Firewall statistics:
> clear active-charging firewall statistics
> clear active-charging firewall track-list
> This command clears the list of servers being tracked for involvement in any Denial-of-Service (DOS) attacks.
> Product
> FW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging firewall track-list attacking-servers
> Usage
> Use this command to clear the list of servers being tracked for involvement in any DOS attacks.
> Example
> The following command clears the list of servers being tracked for involvement in any DOS attacks:
> clear active-charging firewall track-list attacking-servers
> clear active-charging fw-and-nat policy statistics
> This command clears statistics for all or a specific firewall-and-NAT policy.
> Product
> FW, NAT
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging fw-and-nat policy statistics { all | name policy_name } [ | { grep grep_options| more } ]
> all
> Displays information for all firewall-and-NAT policies configured.
> name policy_name
> Displays information for the specified firewall-and-NAT policy.
> policy_name must be the name of a firewall-and-NAT policy, and must be an alpha and/or numeric string of 1 through 63 characters in length.
> grep grep_options | more
> Specifies that output of this command is to be piped (sent) to the command specified. A command to send the output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Command Line Interface Reference.
> Usage
> Use this command to clear statistics for all or a specific firewall-and-NAT policy.
> Example
> The following command clears statistics for the firewall-and-NAT policy named test123:
> clear active-charging fw-and-nat policy statistics name test123
> clear active-charging group-of-ruledefs statistics
> This command clears statistical information related to Active Charging Service group of ruledefs.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging group-of-ruledefs statistics [ name group_of_ruledefs ] [ | { grep grep_options| more } ]
> name group_of_ruledefs
> Specifies name of the group of ruledefs for which statistics must be cleared. group_of_ruledefs must be the name of an existing group of ruledefs, and must be a string of 1 through 63 characters in length.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear statistical information related to all or specified Active Charging Service group of ruledefs.
> Example
> The following command clears statistical information related to the group of ruledefs named ruldef_group12:
> clear active-charging group-of-ruledefs statistics name ruledef_group12
> clear active-charging nat statistics
> This command clears NAT realm statistics.
> Product
> NAT
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging nat statistics [ nat-realm nat_realm ] [ | { grep grep_options| more } ]
> clear active-charging nat statistics
> This command when issued in the local context clears statistics for all NAT realms in all contexts. When issued in a specific context, this command clears statistics for all NAT realms in that context.
> clear active-charging nat statistics nat-realm nat_realm
> This command when issued in the local context clears statistics for the specified NAT realm in all contexts. When issued in a specific context, this command clears statistics for the specified NAT realm in that context.
> nat-realm nat_realm
> Specifies the NAT realm’s name.
> nat_realm must be an alpha and/or numeric string of 1 through 31 characters in length.
> grep grep_options | more
> Specifies that the command’s output be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section in the Command Line Interface Reference.
> Usage
> Use this command to clear NAT realm statistics.
> Example
> The following command when issued in the local context, clears NAT realm statistics for NAT realms named test135 in all contexts:
> clear active-charging nat statistics nat-realm test135
> clear active-charging rulebase statistics
> This command clears ACS rulebase statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging rulebase statistics [ name rulebase_name ] [ | { grep grep_options| more } ]
> rulebase_name
> Clears statistics for specified ACS rulebase.
> rulebase_name must be the name of an existing rulebase, and must be an alpha and/or numeric string of 1 through 15 characters in length.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear ACS rulebase statistics.
> Example
> The following command clears statistics for the ACS rulebase named postpaid:
> clear active-charging rulebase statistics name postpaid
> clear active-charging ruledef statistics
> This command clears ACS rule definition statistics.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging ruledef statistics [ charging | firewall | name ruledef_name ] [ | { grep grep_options | more } ]
> charging
> Clears statistics for all Charging rule definitions configured.
> firewall
> Clears statistics for all Firewall rule definitions configured.
> name ruledef_name
> Clears statistics for the specified active charging service rule definition.
> ruledef_name must be the name of an existing rule definition, and must be an alpha and/or numeric string of 1 through 63 characters in length.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear ACS ruledef statistics.
> Example
> The following command clears all ruledef statistics:
> clear active-charging ruledef statistics
> clear active-charging subsystem
> This command is used to clear all Active Charging service information.
> Product
> ECS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging subsystem
> Usage
> Use this command to clear all Active Charging subsystem information.
> Example
> The following command clears all Active Charging service information:
> clear active-charging subsystem
> clear active-charging url-blacklisting statistics
> This command clears URL Blacklisting feature related statistics.
> Product
> CF
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear active-charging url-blacklisting statistics [ rulebase name rulebase_name ] [ | { grep grep_options| more } ]
> rulebase name rulebase_name
> Clears URL Blacklisting information for the specified rulebase.
> rulebase_name must be the name of a rulebase, and must be a string of 1 through 63 characters in length.
> grep grep_options | more
> Specifies that the output of the command must be piped (sent) to the command specified. A command to send the output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear URL Blacklisting feature related statistics, optionally for a specific rulebase.
> Example
> The following command clears URL Blacklisting feature related statistics for rulebase12:
> clear active-charging url-blacklisting statistics rulebase name rulebase12
> clear administrator
> This command ends the session of an administrative user specified by either user name or session ID.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear administrator { name user_name| session id id_num}
> name user_name
> Identifies the user name of the administrative user.
> session id id_num
> Identifies the ID number of the administrative user session as displayed in the show administrators session id command output.
> Usage
> This command is used to terminate command line interface sessions for other administrative users.
> Example
> The following command ends the session of the administrative user identified as user1:
> clear administrator name user1
> The following command ends the session of the administrative user with the session ID of 3:
> clear administrator session id 3
> clear alarm
> Clears outstanding alarm conditions
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear alarm { all | chassis | id num | port slot/port | slot slot }
> all
> Clear all outstanding alarms
> chassis
> Clears chassis-wide and fan tray alarms
> id num
> Clears a specific alarm by its internal alarm ID. num is the internal alarm identification number.
> port slot/port
> Clears alarms for the specified port. slot/port is the port to clear alarms for.slot is the slot that the card is installed in and port is the port on that card.
> slot slot
> Clears alarms for the specified slot. slot is the slot to clear alarms for.
> Usage
> Use this command to clear outstanding alarm conditions.
> Example
> To clear all outstanding alarms, use the following command:
> clear alarm all
> To clear all alarms for slot 7, enter the following command:
> clear alarm slot 7
> clear asngw-service
> This command clears the service session statistics of an ASN GW service specified by either service name or trusted peer address.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clearasngw-service statistics [name svc_name| peer-address ip_address]
> name svc_name
> Identifies the name of the ASN GW service to clear all service statistics.
> peer-address ip_address
> Identifies the IP address of the ASN GW peer to clear all service statistics.
> Usage
> This command is used to terminate command line interface sessions for ASN GW services.
> Example
> The following command clears the service session statistics of ASN GW service named as asn_svc1:
> clear asngw-service statistics name asn_svc1
> clear asnpc-service
> This command clears the service session statistics of an ASN paging controller service specified by either ASN PC service name or trusted paging controller peer address.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clearasnpc-service statistics [name svc_name| peer-address ip_address]
> name svc_name
> Identifies the name of the ASN PC service to clear all service session statistics.
> peer-address ip_address
> Identifies the IP address of the ASN PC peer to clear all service statistics.
> Usage
> This command is used to terminate command line interface sessions for ASN PC services.
> Example
> The following command clears the service session statistics of ASN PC service named as asnpc_svc1:
> clear asnpc-service statistics name asnpc_svc1
> clear apn statistics
> Deletes all previously gathered statistics for either a specific APN or all APNs configured with the given context.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear apn statistics [ name apn_name]
> name apn_name
> Specifies the name of a specific APN configured in the context for which to clear statistics.
> apn_name is the name of the APN and can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> Usage
> Statistics for a single APN can be cleared using the name keyword. Statistics for all APNs in the context can be deleted by entering the command with no keywords.
> If this command is executed from within the local context with no keywords, statistics will be cleared for every APN configured on the system regardless of context. In addition, if the name keyword is used when executing from within the local context, statistics for all APNs configured with the specified name will be cleared regardless of context.
> Example
> The following command clears statistics for an apn called isp1:
> clear apn statistics isp1
> clear bcmcs statistics
> Clears BCMCS statistics.
> Product
> PDSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear bcmcs statistics [ pdsn-service service_name ]
> pdsn-service service_name
> Defines a specific PDSN service for which to clear BCMCS-specific statistics. This value must be a string consisting of up to 63 characters.
> Usage
> Use this command to clear accumulated BCMCS statistics. You may specify an individual PDSN or peer to selectively clear statistics.
> Example
> clear bcmcs statistics
> clear bcmcs statistics pdsn-service service_name
> clear blacklisted-gtpu-bind-address
> Clears the GTP-U loopback address blacklisted by a specific RNC as defined for a specific IuPS Service configuration.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear blacklisted-gtpu-bind-address ip_address rnc-id rnc-id mcc mcc_num mnc mnc_num iups-service name
> ip_address
> Specifies the IP loopback address that has been blacklisted. This loopback address was originally defined with the associate-gtpu-bind-addfress command in the Radio-Network-Controller configuration mode of the IuPS Service.
> ip_address must be specified using the standard IPv4 dotted decimal notation.
> Usage
> This command enables this loopback address to be used for future RAB-assignment requests.
> Example
> clear blacklisted-gtpu-bind-address 1.1.1.1 rnc-id 2 mcc 123 mnc 321 iups-service iups1
> clear bssap+ statistics
> Clears/deletes the statistics for Base Station System Application Part plus in a Gs service sessions.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator, Operator, Inspector
> Syntax
> clear bssap+ statistics [ gs-service gs_svc_name ] [ vlr { name vlr_name | isdn-number E164_ISDN_Num } ]
> gs-service gs_svc_name
> Specifies the name of a specific Gs service to clear the BSSAP+ information.
> gs_svc_name is the name of a configured Gs service for which BSSAP+ is applied and can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> vlr { name vlr_name | isdn-number E164_ISDN_Num }
> Specifies the name of the VLR or SS7 address in E.164 ISDN format to clear the BSSAP+ information.
> name vlr_name is name of the VLR must be an alpha and/or numeric string of 1 to 63 characters.
> E164_VLR_num is an ISDN number for VLR per E.164 number plan and must be an numerical string of 1 to 15 digits.
> Usage
> Use this command to delete or clear the statistics of BSSAP+ application on a system.
> Example
> The following command clears the information about BSSAP+ in a Gs service named gssvc1.
> clear bssap+ statistics gs-service gssvc1
> clear bulkstats
> Clears counters and accumulated bulk statistics related information.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear bulkstats { counters | data }
> counters
> Clears the counters maintained by the system’s “bulkstats” facility.
> data
> Clears any accumulated data that has not been transferred. This includes any “completed” files that haven't been successfully transferred.
> Usage
> Once bulk statistics collection is enabled, the system stores the information until the specified transfer criteria is met or until a manual transfer is initiated. The system maintains counters for the “bulkstats” software facility. (Refer to the data keyword for the show bulkstats command for information on viewing the counters.)
> This command can be used to delete bulk statistics information that has been collected but not transferred and/or to clear the counters that have been maintained.
> Example
> The following command clears bulk statistics-related counters:
> clear bulkstats counters
> clear config
> This command replaces the active configuration source file with an empty configuration where possible.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear config [ -noconfirm ]
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Clear the current configuration when a complete over right is desired or if it is necessary to start from an empty configuration.
> Important: Clearing the configuration will cause the active configuration source file to be empty and of no use in configuring the system to an active state providing service.
> Important: It is suggested that this command only be performed on configurations which have been backed up for easy restoration.
> Example
> The following command clears the active configuration after the user provides confirmation of the request.
> clear config
> The following command clears the active configuration source file immediately with no user confirmation.
> clear config -noconfirm
> clear congestion-control statistics
> Clears the congestion control statistics for all instances of the specified manager type.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clearcongestion-controlstatistics { a11mgr| asngwmgr | asnpcmgr| hamgr | gtpcmgr | l2tpmgr| imsimgr}
> a11mgr
> Clears the statistics for all A11 Manager instances.
> asngwmgr
> Clears the statistics for all ASN GW Manager instances
> asnpcmgr
> Clears the statistics for all ASN PC-LR Manager instances
> hamgr
> Clears the statistics for all HA Manager instances.
> gtpcmgr
> Clears the statistics for all GTPC Manager instances.
> l2tpmgr
> Clears the statistics for all L2TP Manager instances.
> imsimgr
> Clears the statistics for all IMSI Manager instances.
> Usage
> Use this command to statistics for all instances of the specified manager.
> Important: When this command is issued in any context other than the local context, only instances of the specified manager for the current context have the statistics cleared. When the current context is the local context, all instances of the specified manager type in all contexts have the statistics cleared.
> Example
> Clear the statistics for all instances of the A11 manger, by entering the following command:
> clear congestion-control statistics a11mgr
> clear content-filtering category statistics
> This command clears the Category-based Content Filtering application statistics.
> Product
> CF
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear content-filtering category statistics [ facility srdbmgr instance instance_value]
> facility srdbmgr instance instance_value
> Clears logged events for the specified SRDB Manager instance.
> instance_value must be an integer from 1 through 8.
> In StarOS 9.0 and later, instance_value must be an integer from 1 through 10000.
> Usage
> Use this command to clear all Category-based Content Filtering application statistics, or statistics for a specific SRDB Manager instance.
> Example
> The following command clears all Category-based Content Filtering application statistics:
> clear content-filtering category statistics
> clear crash
> The clear crash command removes a specific crash file or all crash files.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear crash [ list | number crash_num ]
> list | number crash_num
> list: removes all crash files.
> number crash_num: removes only the crash file specified as crash_num which must be within the range of 1 through 30.
> Usage
> CLear crashes for general maintenance activities in cleaning out old, unused, or files which are of no importance.
> Example
> The following will remove all crash files.
> clear crash list
> The following command will remove only crash file 27.
> clear crash number 27
> clear credit-control statistics
> This command is used to clear credit control statistics.
> Product
> PDSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear credit-control statistics cc-service cc_service_name
> cc-service cc_service_name
> Specifies the credit control service name.
> cc_service_name must be an existing Credit Control service, and must be an alpha and/or numeric string of 1 through 63 characters in length.
> Usage
> Use this command to clear active credit control statistics.
> Example
> The following command clears the configured credit control statistics for a service named service1:
> clear credit-control statistics cc-service service1
> clear crypto
> The clear crypto command clears crypto associations or crypto statistics.
> Product
> PDSN, HA, GGSN, PDG/TTG, PDIF, SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear crypto { isakmp [ tag map_name | peer peer_ip ] | security-association { counters tag map_name [ tx | rx ] | tag map_name | peer peer_ip } | statistics { ikev2 | ipsec-3gpp-cscf } [service-ip-address ip-address | service-name name ] }
> isakmp [ tag map_name | peer peer_ip ]
> When no keywords are specified, this command clears all of the ISAKMP security associations for the current context.
> tag map_name: Clears the ISAKMP SAs for the specified crypto map. map_name is the name of an existing crytpo map.
> peer peer_ip: Deletes the ISAKMP SAs for the specified peer. peer_ip must be entered in standard IPv4 notation.
> security-association { counters map map_name [ tx | rx ] | tag map_name | peer peer_ip }
> counters tag map_name [ tx | rx ]: Resets the counters for the specified crypto map. map_name is the name of an existing crypto map. tx specifies that only the transmit SA counters are reset. rx specifies that only the receive SA counters are reset. If neither tx or rx are specified, both transmit and receive SA counters are reset.
> tag map_name: Tears down a Security Association (SA) for the specified crypto map. map_name is the name of an existing crytpo map.
> peer peer_ip: Clears the SAs for all tunnels who have the peer at the specified IP address. peer_ip must be entered in standard IPv4 notation.
> Caution: Modification(s) to an existing crypto map and/or ISAKMP policy configuration will not take effect until the related security association has been cleared.
> statistics { ikev2 | ipsec-3gpp-cscf } [ service-ip-address ip-address | service-name name ]
> ikev2: Clears global IKEv2 statistics for the current context.
> ipsec-3gpp-cscf: Clears global CSCF IPSec statistics for the current context.
> service-ip-address ip-address: Clears statistics for the specified service-ip address. service-name name: Clears statistics for the specified service name.
> Usage
> Clear SAs and apply changes to the crypto map or clear the crypto statistics for this context.
> Example
> The following clears all IKEv2 crypto statistics for the current context:
> clear crypto statistics ikev2
> clear cscf service
> Resets statistics counters for a specific CSCF service, all CSCF services, or for all services within a specified context (VPN).
> Product
> SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear cscf service { diameter { location-info | policy-control} statistics [ service-name service_name | vpn-name name ] | li-packet-cable statistics [service-name service_name] | performance-counters name service_name | statistics name service_name { all | calls | ip-security | message | package-name { message-summary | presence | reg | winfo } | registrations | sigcomp | tcp | vpn-name name } }
> diameter { location-info | policy-control } statistics [ service-name service_name | vpn-name name ]
> Clears Diameter (DPECA) statistics on the CSCF Rx interface with the configuration information.
> service-name service_name: Specifies the name of a CSCF service for which the statistics will be reset. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> vpn-name name: Specifies the name of a context in which all statistics for all services will be reset. name must be an existing context and be from 1 to 79 alpha and/or numeric characters.
> li-packet-cable statistics [ service-name service_name ]
> Clears Lawful Intercept statistics.
> service-name service_name: Clears Lawful Intercept statistics for a specific CSCF service configured on this system. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> performance-counters name service_name
> Clears all CSCF performance counters for a specific CSCF service configured on this system. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters
> statistics name service_name { all | calls | ip-security | message | package-name { message-summary | presence | reg | winfo } | registrations | sigcomp | tcp | vpn-name name }
> Clears service statistics for a specific CSCF service configured on this system. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> all: Clears all CSCFservice statistics.
> calls: Clears statistics related to CSCF calls.
> ip-security: Clears statistics related to CSCF IPSec.
> message: Clears statistics for the SIP method MESSAGE.
> package-name: Clears statistics for the associated event package.

> • | message-summary: Clears statistics for the “message-summary” event package.

> • | presence: Clears statistics for the “presence” event package.

> • | reg: Clears statistics for the “reg” event package.

> • | winfo: Clears statistics for the “watcher-info” event package.

> registrations: Clears statistics related to CSCF registrations, re-registrations, and de-registrations.
> sigcomp: Clears statistics related to CSCF sigcomp.
> tcp: Displays session statistics related to CSCF TCP.
> vpn-name name: Clears statistics for a specific CSCF service configured in a specific context on this system. name must be an existing context and be from 1 to 79 alpha and/or numeric characters.
> Important: This keyword must be followed by another statistics-related keyword.
> Usage
> Use this command to reset statistics counters for CSCF services. This command will reset the counters in the output of the show cscf service statistics command.
> Important: This command will not clear current registered users and current CSCF sessions.
> Example
> The following command resets all statistics for a service named cscf1:
> clear cscf service statistics name cscf1 all
> clear cscf sessions
> Clears statistics for CSCF sessions on this system.
> Product
> SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear cscf sessions { counters { calls | subscription } service service_name | service service_name { all | aor aor | session-id id }
> counters { calls | subscription } service service_name
> Clears counters for all CSCF sessions matching the filter criteria.
> calls: Counters associated with calls in CSCF service.
> subscription: Counters associated with subscriptions in CSCF service.
> service service_name: Counters on specific CSCF service. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> service service_name { all | aor aor | session-id id }
> Clears session information for all CSCF sessions matching the filter criteria.
> service service_name: Session statistics on specific CSCF service. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.

> • | all: Specifies that session statistics are to be cleared for all sessions on this service.

> • | aor aor: Specifies that session statistics are to be cleared for sessions at this specific AoR. aor must be an existing AoR and be from 1 to 79 alpha and/or numeric characters.

> • | session-id id: Specifies that session statistics are to be cleared for sessions with this ID. id must be an existing session ID and be from 1 to 63 alpha and/or numeric characters.

> Usage
> Use this command to clear session information for CSCF sessions.
> Example
> The following command resets all session statistics for a service named cscf1:
> clear cscf sessions service cscf1 all
> clear cscf sip
> Resets SIP statistics counters for a specific CSCF service, all CSCF services, or for all services within a specified context (VPN) or interface.
> Product
> SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear cscf sip statistics [ name service_name [ interface { domain name domain_name | ip address ip_address } | vpn-name name ]
> name service_name
> Specifies the name of a CSCF service for which the SIP statistics will be reset. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> interface { domain name domain_name | ip address ip_address }
> SIP statistics will be reset in this interface.
> domain name domain_name: Specifies the domain associated with the CSCF service. domain_name must be an existing domain and be from 1 to 64 alpha and/or numeric characters.
> ip address ip_address: Specifies the destination or source ip address associated with the CSCF service.
> vpn-name name
> Specifies the name of a context in which all SIP statistics for all services will be reset. name must be an existing context and be from 1 to 79 alpha and/or numeric characters.
> Usage
> Use this command to reset SIP counters found in the output of the show cscf sip command.
> Example
> The following command resets the SIP statistics for a service named cscf1:
> clear cscf sip statistics name cscf1
> clear cscf subscription
> Clears all subscriptions for a named service or for individual subscribers within the service.
> Product
> SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear cscf subscription service service_name { all | from-aor subscriber_aor to-aor resource_aor }
> service service_name
> Specifies the name of a CSCF service for which the subscription(s) will be cleared. service_name must be an existing CSCF service and be from 1 to 63 alpha and/or numeric characters.
> all | from-aor subscriber_aor to-aor resource_aor
> all: Removes all CSCF subscriptions for the specified service.
> from-aor subscriber_aor: Removes all CSCF subscriptions for a specified subscriber in a specified service.
> subscribed-to resource_aor: Removes all CSCF subscriptions for a specified subscriber in a specified service with a specified subscribed-to resource AoR.
> Usage
> Use this command to clear subscriptions to enforce policies. This command initiates a SUBSCRIBE request with Expires as 0 in the corresponding subscription dialog.
> Example
> The following command clear all subscriptions for a CSCF service named cscf1:
> clear cscf subscription service cscf1 all
> clear diameter aaa-statistics
> This command clears Diameter AAA statistics.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear diameter aaa-statistics [ all | [ group aaa_group ] server diameter_server ] [ | { grep grep_options | more } ]
> all
> Clears all Diameter server statistics.
> group aaa_group
> Clears Diameter server statistics for the specified AAA group.
> aaa_group must be the name of a AAA group, and must be a string of 1 through 64 characters in length.
> server diameter_server
> Clears Diameter server statistics for the specified Diameter server.
> diameter_server must be the name of a Diameter server, and must be a string of 1 through 64 characters in length.
> | { grep grep_options | more }
> Indicates the output of the command is to be piped (sent) to the command specified.
> A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear Diameter AAA statistics.
> Example
> The following command clears Diameter server statistics for the specified AAA group:
> clear diameter aaa-statistics group <aaa_group>
> clear diameter statistics
> This command clears Diameter statistics.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear diameter statistics [ [ proxy ] endpoint endpoint_name [ peer-host host_id [ peer-realm realm_id ] ] ] [ | { grep grep_options | more } ]
> endpoint endpoint_name
> Clears endpoint related statistics.
> endpoint_name must be the name of an endpoint, and must be a string of 1 through 63 characters in length.
> proxy
> Clears proxy related statistics.
> peer-host host_id
> Clears statistics for the specified Diameter peer host ID.
> host_id must be the Diameter peer host ID, and must be a string 1 through 255 characters in length.
> peer-realm realm_id
> Clears statistics for the specified Diameter peer realm.
> realm_id must be the Diameter peer realm ID, and must be a string 1 through 127 characters in length.
> | { grep grep_options | more }
> Indicates the output of the command is to be piped (sent) to the command specified.
> A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Use this command to clear Diameter statistics.
> Example
> The following command clears all Diameter statistics for the specified endpoint:
> clear diameter statistics endpoint <endpoint_name>
> clear dhcp statistics
> Deletes all previously gathered statistics for either a specific DHCP server or all DHCP servers configured within the given context.
> Product
> GGSN, ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear dhcp statistics [ dhcp-service svc_name| server ip_address]
> dhcp-service svc_name
> The name of a specific DHCP service for which to clear statistics.
> svc_name is the name of the DHCP service and can be from 1 to 63 alpha and/or numeric characters in length and is case sensitive.
> server ip_address
> Specifies the IP address of a specific DHCP server configured in the context for which to clear statistics.
> ip_address must be entered in dotted decimal notation.
> Usage
> Statistics for a single server can be cleared using the server keyword. Statistics for all DHCP servers in the context can be deleted by entering the command with no keywords.
> This command can be executed from any context configured on the system.
> If this command is executed from within the local context with no keywords, statistics will be cleared for every DHCP server configured on the system regardless of context. In addition, if the server keyword is used when executing from within the local context, statistics for all DHCP servers configured with the specified name will be cleared regardless of context.
> Example
> The following command clears statistics for all configured DHCP servers within the context:
> clear dhcp statistics
> clear dns-client
> Clears DNS cache and/or statistics for a specified DNS client.
> Product
> SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear dns-client name { cache [ query-name nam e | query-type { A | SRV } ] | statistics }
> dns-client name
> Defines the name of the DNS client whose cache and/or statistics are being cleared. name must be an existing DNS client and be from 1 to 255 alpha and/or numeric characters in length.
> cache [ query-name nam e | query-type { A | SRV } ]
> Specifies that the cache for the defined DNS client is to be cleared.
> query-name name: Filters DNS results based on the domain name. name must be from 1 to 255 characters in length. name is the domain name used to perform the DNS query. name is different from the actual domain name which is resolved. For example, to resolve the SIP server for service.com, the query name is _sip._udp.service.com and the query type is SRV.
> query-type:

> • | A: Filters DNS results based on domain IP address records (A records).

> • | SRV: Filters DNS results based on service host records (SRV records).

> statistics
> Specifies that statistics for the defined DNS client are to be cleared.
> Usage
> Use this command to clear DNS cache and/or statistics for a specified DNS client.
> Example
> The following command clears statistics for a DNS client named domain1.com:
> clear dns-client domain1.com statistics
> clear egtpc
> Clears enhanced GPRS Tunneling Protocol control plane statistics and counters found in show command outputs and bulk statistics associated with all eGTP-C-related services or those defined by the parameters in this command.
> Product
> MME, P-GW, S-GW
> Privilege
> Operator
> Syntax
> clear egtpc statistics [ egtp-service name | interface-type { interface-mme | interface-pgw-ingress | interface-sgw-egress | interface-sgw-ingress } | mme-address ip_address | pgw-address ip_address | sgw-address ip_address ]
> egtp-service name
> Clears all statistics and counters associated with a specific eGTP service name. name must be an existing eGTP service name and be from 1 to 63 alpha and/or numeric characters.
> interface-type { interface-mme | interface-pgw-ingress | interface-sgw-egress | interface-sgw-ingress }
> interface-mme: Clears statistics and counters derived from all MME interface types associated with this system.
> interface-pgw-ingress: Clears statistics and counters derived from all P-GW ingress interface types associated with this system.
> interface-sgw-egress: Clears statistics and counters derived from all S-GW egress interface types associated with this system.
> interface-sgw-ingress: Clears statistics and counters derived from all S-GW ingress interface types associated with this system.
> mme-address ip_address
> Clears all statistics and counters derived from a specific MME IP address. ip_address must be an existing MME IP address and be specified in dotted decimal notation (for IPv4) or colon-separated notation (for IPv6).
> pgw-address ip_address
> Clears all statistics and counters derived from a specific P-GW IP address. ip_address must be an existing P-GW IP address and be specified in dotted decimal notation (for IPv4) or colon-separated notation (for IPv6).
> sgw-address ip_address
> Clears all statistics and counters derived from a specific S-GW IP address. ip_address must be an existing S-GW IP address and be specified in dotted decimal notation (for IPv4) or colon-separated notation (for IPv6).
> Usage
> Use this command to clear running statistics and counters found in show command and bulk statistics outputs for all eGTP-C-related services or for specific interfaces, services, or IP addresses as specified by parameters in this command.
> Example
> The following command clears eGTP-C statistics and counter associated with all P-GW ingress interfaces configured on this system:
> clear egtpc statistics interface-type interface-pgw-ingress
> The following command clears eGTP-C statistics and counter associated with all MME interfaces configured on this system:
> clear egtpc statistics interface-type interface-mme
> clear firewall flows
> This command is obsolete.
> clear firewall ruledef
> This command is obsolete.
> clear firewall statistics
> This command is obsolete.
> clear gmm-sm statistics
> Deletes all previously gathered GMM-SM statistics within the given context based on the specified criteria.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear gmm-sm statistics [ gmm-only | sm-only ] [ gprs-service srvc_name [ nsei nse_id | routing-area mcc mcc_id mnc mnc_id lac lac_id rac rac_id ] ] | [ sgsn-service srvc_name [ rnc mcc mcc_id mnc mnc_id rnc-id rnc_id | routing area mcc mcc_id mnc mnc_id lac lac_id rac rac_id ] ]
> gmm-only
> Enter this keyword to display only GPRS mobility management (GMM) information for other specified keyword parameters for the current context.
> sm-only
> Enter this keyword to display only session management (SM) information for other specified keyword parameters for the current context.
> gprs-service srvc_name
> Enter this keyword to display the statistics for the specified GPRS service. The display request can be narrowed by adding additional keywords.
> srvc_name must be an alphanumeric string of 1 to 63 alphanumeric characters.
> nsei
> Enter this keyword to display the GMM/SM session statistics for the identified network service entity (NSEI).
> sgsn-service srvc_name
> Enter this keyword to display the statistics for the specified SGSN service. The display request can be narrowed by adding additional keywords.
> srvc_name must be an alphanumeric string of 1 to 63 alphanumeric characters.
> rnc
> Enter this keyword to fine-tune the display of the GMM/SM session statistics just for the specified ( rnc-id) radio network controller (RNC).
> rnc-id rnc_id
> Enter this keyword to identify the specific RNC.
> rnc_id must be an integer from 0 through 4095.
> routing-area mcc mcc_id mnc mnc_id lac lac_id rac rac_id
> Enter the routing-area keyword to fine-tune the display of the GMM/SM session statistics for a specified routing area (RA) identified by the MCC, MNC, LAC and RAC.
> mcc mcc_id
> Enter this keyword to specify the mobile country code (MCC) as part of the identification of the RNC or RA.
> mcc_id must be an integer from 100 through 999.
> mnc mnc_id
> Enter this keyword to specify the mobile network code (MNC) as part of the identification of the RNC or RA.
> mnc_id must be an integer from 00 through 999.
> lac lac_id
> Enter this keyword to specify the location area code (LAC) as part of the identification of the RNC or RA.
> lac_id must be an integer from 1 through 65535.
> rac rac_id
> Enter this keyword to specify the routing area code (RAC) as part of the identification of the RNC or RA.
> rac_id must be an integer from 1 through 255.
> Usage
> Use this command to delete statistics for the GMM/SM session configurations for SGSN services.
> Example
> The following command deletes GMM/SM statistics for a specific routing area defined for the GPRS service:
> clear gmm-sm statistics gprs-service gprs1 routing-area mcc 123 mcc 131 lac 24 rac 11
> The following command clears all collected information for GMM/SM statistics:
> clear gmm-sm statistics verbose
> clear gtpc statistics
> Deletes all previously gathered GTPC (GTPv0, GTPv1-C, GTPv1-U) statistics within the given context based on the specified criteria.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear gtpc statistics [ apn apn_name] [ custom1 ] [ ggsn-service ggsn_name] [ sgsn-address sgsn_address]
> apn apn_name
> Specifies the name of an APN configured in the context for which to delete GTPC statistics.
> apn_name can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> custom1
> Clears the statistics of GTP-C messages for preservation mode and free of charge service.
> This keyword is customer-specific license enabled and used for Preservation-Mode and Free-of-Charge Service which are enabled under customer-specific license. For more information on this support, contact your local representative.
> ggsn-service ggsn_name
> Specifies the name of a GGSN service configured in the context for which to delete GTPC statistics.
> ggsn_name can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> sgsn-address sgsn_address
> Specifies the IP address of an SGSN for which to delete GTPC statistics.
> sgsn_address must be expressed in dotted decimal notation.
> Usage
> GT-C statistics can be cleared for a single APN, GGSN service, or SGSN. All GTPC statistics in the context can be deleted by entering the command with no keywords.
> This command can be executed from any context configured on the system.
> If this command is executed from within the local context with no keywords, all GTPC statistics will be cleared regardless of context.
> GTPP statistics are not affected by this command.
> Example
> The following command clears all GTPC statistics within the context:
> clear gtpc statistics
> clear gtpp statistics
> Deletes all previously gathered GTPP statistics within the given context based for either single or all charging gateway functions (CGFs).
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear gtpp statistics [ cgf-address ip-address]
> cgf-address cgf_address
> Deletes statistics for a particular CGF.
> cgf_address is the IP address of the CGF for which statistics are to be deleted. It must be expressed in dotted decimal notation
> Usage
> Statistics for a single CGF can be cleared using the cgf-address keyword. Statistics for all CGFs in the context can be deleted by entering the command with no keywords.
> This command can be executed from any context configured on the system.
> If this command is executed from within the local context with no keywords, statistics will be cleared for every CGF configured on the system regardless of context. In addition, if the cgf-address keyword is used when executing from within the local context, statistics for all CGFs configured with the specified name will be cleared regardless of context.
> Example
> The following command deletes all GTPP statistics for a CGF with an IP address of 192.168.1.42:
> clear gtpp statistics cgf-address 192.168.1.42
> clear gtpp storage-server local file statistics
> This command clears AAAproxy GTPP group level statistics for CDRs stored on the local SMC hard disk.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear gtpp storage-server local file statistics [ group name name ]
> Usage
> If executed from the local context, this command clears statistics for all GTPP groups configured on the system. If executed from the context within which the storage servers (SMC hard disk) is configured, statistics are deleted for only that context.
> clear gtpp storage-server statistics
> Clears statistics for configured GTPP storage servers (GSS).
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear gtpp storage-server statistics
> Usage
> If executed from the local context, this command clears statistics for all GTPP storage servers configured on the system. If executed from the context within which the servers are configured, statistics are deleted for only those servers.
> clear gtpu statistics
> Clears enhanced GPRS Tunneling Protocol user plane statistics and counters found in show command outputs and bulk statistics associated with all GTP-U-related services or those defined by the parameters in this command.
> Product
> P-GW, S-GW
> Privilege
> Operator
> Syntax
> clear gtpu statistics [ gtpu-service name | peer-address ip_address ]
> gtpu-service name
> Clears all statistics and counters associated with a specific GTP-U service name. name must be an existing GTP-U service name and be from 1 to 63 alpha and/or numeric characters.
> peer-address ip_address
> Clears all statistics and counters derived from a specific peer IP address. ip_address must be an existing peer IPv4 or IPv6 address and be specified in dotted decimal notation (for IPv4) or colon-separated notation (for IPv6).
> Usage
> Use this command to clear running statistics and counters found in show command and bulk statistics outputs for all GTP-U-related services or for specific services or IP addresses as specified by parameters in this command.
> Example
> The following command clears GTP-U statistics and counter associated with a GTP-U service name gtpu-12 configured on this system:
> clear gtpu statistics gtpu-service gtpu-12
> clear hd-storage-policy
> Clears statistic information for HD storage policies configured on the system.
> Product
> HSGW, P-GW, S-GW
> Privilege
> Operator
> Syntax
> clear hd-storage-policy statistics { all | name name }
> statistics { all | name name }
> all: Specifies that ACR statistic information for all HD storage policies configured on the system is to be cleared.
> name name: Specifies that ACR statistic information for an HD storage policy with the specified name is to be cleared.
> Usage
> Use this command to clear statistics for HD storage policies configured on the system.
> Example
> The following command clears statistics for an HD storage policy named pgwsgw:
> clear hd-storage-policy statistics name pgwsgw
> clear hsgw-service
> Clears statistic information for HSGW services configured on the system.
> Product
> HSGW
> Privilege
> Operator
> Syntax
> clear hsgw-service statistics { all | name name }
> statistics { all | name name }
> all: Specifies that HSGW service statistic information for all HSGW services configured on the system is to be cleared.
> name name: Specifies that HSGW service statistic information for an HSGW service with the specified name is to be cleared.
> Usage
> Use this command to clear statistics for HSGW services configured on the system.
> Example
> The following command clears statistics for an HSGW service named hsgw3:
> clear hsgw-servicey statistics name hsgw3
> clear ims-authorization
> This command clears statistics for all or for a specified IMS Authorization Service.
> Product
> GGSN, SCM
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear ims-authorization { policy-control statistics [ ims-auth-service service_name ] | service statistics [ name service_name ] } [ | { grep grep_options | more } ]
> ims-auth-service service_name
> Clears statistics for the specified IMSA service.
> service_name must be the name of an IMSA service, and must be a string of 1 through 64 characters in length.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Command Line Interface Reference.
> Usage
> Use this command to clear IMSA Service statistics.
> Example
> The following command clears IMSA policy-control statistics for an IMSA service named test_service:
> clear ims-authorization policy-control statistics ims-auth-service test_service
> clear ip access-group statistics
> This command clears all interface ACL statistics and the context level ACL statistics that have been configured in the current context. Be aware that updating an access list also causes all ip access-groups utilizing the list to be cleared.
> Product
> PDSN, GGSN. ASN-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> clear ip access-group statistics
> Usage
> Use this command to clear all interface ACL statistics and the context level ACL statistics that have been configured in the current context.
> The following command clears the ACL statistics:
> clear ip access-group statistics
> clear ip arp
> Clears the address resolution protocol cache for a given IP address.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear ip arp ip_address
> ip_address
> Specifies the IP address for which to clear the ARP cache. ip_address must be specified using the standard IPv4 dotted decimal notation.
> Usage
> Clear the ARP cache when network changes have occurred for the case where the cached data may cause undue overhead in routing of packets.
> Example
> The following command clears the ARP cache for the IP address 1.2.3.4:
> clear ip arp 1.2.3.4
> clear ip bgp peer
> Resets BGP connections for all peers or for specified peers in the current context.
> Product
> HA
> Privilege
> Security Administrator, Administrator
> Syntax
> clear ip bgp peer {ip_address| all | as as_num} [in | out | soft | vpnv4 ]
> ip_address
> The IP address of the neighbor for which BGP connections should be reset. ip_address is an IPv4 address in dotted-decimal notation.
> all
> Reset BGP connections for all peers.
> as as_num
> Reset BGP connections for all peers in the specified AS. as_num must be an integer from 1 through 65535.
> in
> Soft reconfigure inbound updates.
> out
> Soft reconfigure outbound updates.
> soft
> Soft reconfigure inbound and outbound updates.
> vpnv4
> Clears bgp sessions with the vpnv4 address family.
> Usage
> Use this command to BGP information for the current context.
> Example
> The following command resets BGP connections for all neighbors:
> clear ip bgp peer all
> clear ip localhosts
> This command removes the host specified from the current context’s local host list for IP address mappings.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear ip localhosts [ host_name ]
> host_name
> Specifies the name of the host to be removed. Value must be a string from 1 to 1023 characters. When omitted, all local host name mappings will be removed.
> Usage
> Clear a host name when it is no longer valid for the current context to access. The host name specified will be unrecognized by the current context once the command is performed.
> Example
> clear ip localhostsclear ip localhosts 1.2.3.4clear ip localhosts remoteABC
> clear ip ospf process
> Clears OSPF database information for the current context and re-establishes neighbor adjacency.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear ip ospf process
> Usage
> Use this command to clear the OSPF database information for the current context and re-establishes neighbor adjacency.
> Example
> The following command clears the OSPF database information for the current context and re-establishes neighbor adjacency:
> clear ip ospf process
> clear ipv6 neighbors
> Clears an ipv6 address from the neighbor cache.
> Product
> PDIF
> Privilege
> Administrator, Security Administrator
> Syntax
> clear ipv6 neighbors ipaddress
> Usage
> Clears a specific address from the neighbor cache.
> Example
> Use the following example to clear 3ffe:ffff:101::230:6eff:fe04:d9aa/48:
> clear ipv6 neighbors 3ffe:ffff:101::230:6eff:fe04:d9aa/48
> clear l2tp
> Clears all or specific L2TP statistics or clears and disconnects all or specified sessions or tunnels.
> Product
> PDSN, GGSN, LNS
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> statistics [ lac-service service_name | lns-service service_name | peer-address ip_address ]
> With no optional keywords specified, this command clears all L2TP statistics for the current context.
> lac-service service_name: Clears all L2TP statistics for the specified LAC service in the current context.
> lns-service service_name: Clears all L2TP statistics for the specified LNS service in the current context.
> peer-address ip_address: Clears all L2TP statistics for the destination (peer LNS) at the specified IP address. The IP address is specified using the standard IPv4 dotted decimal notation.
> tunnels { all [ clear-sa] | callid call_id | lac-service service_name [ clear-sa ] | peer-address ip_address [ clear-sa ] }
> all: Clears all tunnels in the current context.
> lac-service service_name: Clears all tunnels in the current context that belong to the specified LAC service and closes the tunnels.
> lns-service service_name: Clears all tunnels in the current context that belong to the specified LNS service and closes the tunnels.
> peer-address ip_address: Clears all tunnels in the current context whose destination (peer LNS) is the system at the specified IP address. The IP address is specified using the standard IPv4 dotted decimal notation.
> callid call_id: Uses the unique identifier that specifies a particular tunnel in the system to clear that tunnel and disconnect it. The output of the command show l2tp tunnels contains a field labeled Callid Hint which lists the call id information to use with this command. This is an 8-Byte Hexadecimal number.
> clear-sa: If any security associations have been established they are cleared.
> Usage
> Clear L2TP all or specific L2TP statistics or clear sessions in a tunnel and disconnect the tunnel.
> Example
> To clear all L2TP statistics for the current context, use the following command:
> clear l2tp statistics
> To clear all L2TP statistics for the LAC service named lac1, use the following command:
> clear l2tp statistics lac-service lac1
> Use the following command to clear L2TP statistics for the LNS peer at the IP address 10.10.10.100:
> clear l2tp statistics peer-address 10.10.10.100
> The following command clears and closes all tunnels in the current context:
> clear l2tp tunnels all
> The following command clears and closes all tunnels for the LAC service named lac2:
> clear l2tp tunnels lac-service lac2
> The following command clears and closes all tunnels the peer at the IP address 10.10.10.110:
> clear l2tp tunnels peer-address 10.10.10.110
> clear lawful-intercept
> Clears information pertaining to lawful interception capability.
> Product
> PDSN, HA, LNS, GGSN, ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear lawful-intercept statistics
> statistics
> Clears lawful-intercept statistics.
> Usage
> Use this command to clear statistics pertaining to Lawful Intercept functionality.
> Important: You must log in to the system through a Secure Shell (SSH) using a system account that has li-administrator privileges to use this command. For details on using the Lawful Intercept capability of the system, refer to System Administration and Configuration Guide.
> Example
> The following clears all statistics for the Lawful Intercept functionality.
> clear lawful-intercept statistics
> clear lma-service statistics
> Clears Local Mobility Anchor statistics and counters found in show command outputs and bulk statistics associated with all LMA services or a specific service defined by the parameter in this command.
> Product
> P-GW
> Privilege
> Operator
> Syntax
> clear lma-service statistics [ name servie_name ]
> name servie_name
> Clears statistics and counters for a specific LMA service name. name must be an existing LMA service name and be from 1 to 63 alpha and/or numeric characters.
> Usage
> Use this command to clear statistics and counters in show command outputs and bulk statistics for all LMA services or for a specific LMA service.
> Example
> The following command clears statistics and counters for an LMA service named lma3:
> clear lma-service statistics name lma3
> clear local-user
> Clears information pertaining to local-user administrative accounts.
> Product
> All
> Privilege
> Security Administrator
> Syntax
> clear local-user { database [ -noconfirm ] | statistics | username name lockout }
> database [ -noconfirm ]
> Clears the local-user database. This command deletes all information for all local-user accounts.
> Caution: Use this command only in the event of security concerns or to address concerns of the local-user account database integrity.
> statistics
> Clears statistics pertaining to local-user accounts.
> userame name lockout
> Removes lockouts associated with specific local-user accounts.
> name is the name of the local-user account and can consist of from 3 to 16 alpha and/or numeric characters and is case sensitive.
> Usage
> This command can be used to remove local-user account lockouts, reset local-user-related statistics to 0, or to delete the local-user database.
> Example
> The following command removes the lockout placed on a local-user account named SecureAdmin:
> clear local-user username SecureAdmin lockout
> clear mag-service statistics
> Clears Mobile Access Gateway statistics and counters found in show command outputs and bulk statistics associated with all MAG services or a specific service defined by the parameter in this command.
> Product
> HSGW, S-GW
> Privilege
> Operator
> Syntax
> clear mag-service statistics [ name servie_name ]
> name servie_name
> Clears statistics and counters for a specific MAG service name. name must be an existing MAG service name and be from 1 to 63 alpha and/or numeric characters.
> Usage
> Use this command to clears statistics and counters in show command outputs and bulk statistics for all MAG services or for a specific MAG service.
> Example
> The following command clears statistics and counters for a MAG service named mag1
> clear mag-service statistics name mag1
> clear maximum-temperatures
> Clears information pertaining to component maximum temperatures.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear maximum-temperatures
> Usage
> Reset the timestamp to the current time and clear previous maximum temperatures for all temperature monitored components. This may be useful when preparing to study system performance, monitor usage, or trouble shoot the administrative interfaces.
> Example
> The following command resets the maximum temperature statistics for all monitored chassis components.
> clear maximum-temperatures
> clear mipfa statistics
> This command clears the statistics for the mobile IP foreign agent. The statistics for a specific foreign agent service may be cleared by explicit command.
> Product
> PDSN, GGSN. ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear mipfa statistics [ fa-service name | peer-address ip_address ]
> fa-service name | peer-address ip_address
> fa-service name: Indicates the statistics for a specific service are to be cleared where the service is as specified by name. “Total sessions” counters for all peers associated with the service are also reset. name must be an existing FA service name.
> peer-address ip_address: Indicates the statistics for the specific IP address, ip_address, are to be cleared. “Total sessions” counter for the specified peer is also reset. The IP address is specified using the standard IPv4 dotted decimal notation.
> Usage
> Clear all statistics for the MIP foreign agent or for a specific service. This may be useful in monitoring performance and troubleshooting as the statistics may be cleared at a well known time and then collected and transferred for review.
> Example
> The following clears all statistics for the mobile IP foreign agent.
> clear mipfa statistics
> The following command clears the statistics for the example service only.
> clear mipfa statistics fa-service sampleService clear mipfa statistics peer-address 1.2.3.4
> clear mipha statistics
> This command clears the statistics for the mobile IP home agent. The statistics for a home agent service may be cleared by explicit command.
> Product
> HA
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear mipha statistics [ ha-service name | peer-address ip_address ]
> ha-service name | peer-address ip_address
> ha-service name: indicates the statistics for a specific service are to be cleared where the service is as specified by name. “Total sessions” counters for all peers associated with the service are also reset. name must be an existing HA service name.
> peer-address ip_address: indicates the statistics for the specific IP address, are to be cleared. “Total sessions” counter for the specified peer is also reset. The IP address is specified using the standard IPv4 dotted decimal notation.
> Usage
> Clear all statistics for the MIP home agent or for a specific service. This may be useful in monitoring performance and troubleshooting as the statistics may be cleared at a well known time and then collected and transferred for review.
> Example
> The following clears all statistics for the mobile IP foreign agent.
> clear mipha statistics
> The following command clears the statistics for the example service only.
> clear mipha statistics ha-service sampleService
> clear mipha statistics peer-address 1.2.3.4
> clear mme-service db statistics
> This command clears the MME database statistics for MME sessions for all or specific session instances on this system.
> Product
> MME
> Privilege
> Inspector
> Syntax
> clear mme-service db statistics [instance smgr_instance]
> instance smgr_instance
> This keyword specifies that MME database statistics are to be removed for a specific instance of session manager running for MME service.
> smgr_instance must be specified as an instance ID in the range 0 through 4294967295. If instance is not specified database statistics of all instances will be removed.
> Usage
> Use this command to clear/remove database statistics for all or a particular instance of session manager for MME services on this system.
> Example
> The following command removes/clears the database statistics of all instances of the MME service on a system:
> clear mme-service db statistics
> clear mme-service db record
> This command clears the MME database records all instances of session manager running for MME service filtered with IMSI or GUTI as criteria.
> Product
> MME
> Privilege
> Inspector
> Syntax
> clear mme-service db record {imsi imsi_identifier | callid call_id | guti plmn plmn_id group-id mme_grp_id code mme_code m-tmsi mtmsi_value} [ | { grep grep_options | more } ]
> imsi imsi_identifier
> This keyword specifies the filter criteria as International Mobile Subscriber Identity (IMSI) imsi_identifier to clear the database records of a session instance.
> imsi_identifier is a 15 character IMSI field which identifies the subscriber’s home country and carrier. Wildcard characters $ and * are allowed. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as a wildcard enclose them in single quotes ( ‘ ). For example; ‘$’.
> callid call_id
> This keyword specifies the filter criteria as call id call_id to clear the database records of a session instance.
> call_id must be specified as an 8-byte hexadecimal number.
> guti plmn plmn_id group-id mme_grp_id code mme_code m-tmsi mtmsi_value
> This set of keyword specifies the filter criteria as Globally Unique Temporary Identifier (GUTI) to clear the database records for MME service.
> The GUTI is constructed from the GUMMEI and the M-TMSI where GUMMEI is constructed from PLMN (MMC and MNC) plmn_id and MME Identifier is constructed from an MME Group ID (MMEGI) mme_grp_id and an MME Code (MMEC) mme_code.
> Within the MME, the mobile is identified by the M-TMSI mtmsi_value
> Usage
> Use this command to clear/remove database records for all or a particular instance of session manager for MME services on this system with IMSI or GUTI as filter criteria.
> Example
> The following command clears the summary database records of a session instance for subscriber having IMSI as 123455432112345 in the MME service:
> clear mme-service db record imsi 123455432112345
> clear mme-service statistics
> This command clears the service statistics of an MME service specified by various criteria.
> Product
> MME
> Privilege
> Security Administrator, Administrator
> Syntax
> clear mme-service statistics [emm-only [mme-service mme_svc_name| peer-id peer_identifier]] | esm-only [mme-service mme_svc_name| peer-id peer_identifier] | s1ap [mme-service mme_svc_name| peer-id peer_identifier] | sctp [mme-service mme_svc_name]]
> emm-only
> This keyword sets the filter criteria as MME service name or peer MME identifier to clear all EPS mobility management (EMM) related statistics.
> esm-only
> This keyword sets the filter criteria as MME service name or peer MME identifier to clear all EPS session management (ESM) related statistics.
> s1ap
> This keyword sets the filter criteria as MME service name of peer MME identifier to clear all S1-AP statistics.
> sctp
> This keyword sets the filter criteria as MME service name of peer MME identifier to clear all SCTP statistics.
> mme-service mme_svc_name
> This keyword sets the filter criteria as MME service name to clear all service statistics.
> peer-id peer_identifier
> This keyword sets the filter criteria as identifier of MME peer to clear all service statistics.
> Usage
> This command is used to clear the statistical information of an MME service based on various filter criteria.
> Example
> The following command clears the service session statistics of all MME service on a system:
> clear mme-service statistics
> clear mme-service statistics
> This command clears the service statistics of an MME service specified by various criteria.
> Product
> MME
> Privilege
> Security Administrator, Administrator
> Syntax
> clear mme-service statistics [emm-only [mme-service mme_svc_name| peer-id peer_identifier]] | esm-only [mme-service mme_svc_name| peer-id peer_identifier] | s1ap [mme-service mme_svc_name| peer-id peer_identifier] | sctp [mme-service mme_svc_name]]
> emm-only
> This keyword sets the filter criteria as MME service name or peer MME identifier to clear all EPS mobility management (EMM) related statistics.
> esm-only
> This keyword sets the filter criteria as MME service name or peer MME identifier to clear all EPS session management (ESM) related statistics.
> s1ap
> This keyword sets the filter criteria as MME service name of peer MME identifier to clear all S1-AP statistics.
> sctp
> This keyword sets the filter criteria as MME service name of peer MME identifier to clear all SCTP statistics.
> mme-service mme_svc_name
> This keyword sets the filter criteria as MME service name to clear all service statistics.
> peer-id peer_identifier
> This keyword sets the filter criteria as identifier of MME peer to clear all service statistics.
> Usage
> This command is used to clear the statistical information of an MME service based on various filter criteria.
> Example
> The following command clears the service session statistics of all MME service on a system:
> clear mme-service statistics
> clear multicast-sessions
> Disconnects broadcast-multicast sessions based on specified criteria.
> Product
> PDSN, GGSN
> Privilege
> Security Administrator Operator
> Syntax
> clearmulticast-sessions [ -noconfirm ] [ keywords ] [ verbose ]
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> all
> Disconnects all multicast sessions.
> callid call_id
> Clears the call specified by call_id. The call ID must be specified as an 8-digit hexadecimal number.
> card-num psc_num
> The slot number of the packet processing by which the multicast session is processed. psc_num is a slot number from 1 through 7 or 10 through 16
> flowid id
> Clears calls for a specific BCMCS flow, defined by id. The flow ID must be a hexidecimal number
> flowid-type [ flow | program ]
> Clears multicast sessions according to the type of flow.
> flow: Clears all multicast sessions for the flow ID type “flow”.
> program: Clears all multicast sessions for the flow ID type “program”.
> mcast-address ipv4_address
> Clear multicast sessions for a specific multicast address. Must be followed by the IP address of an interface, using dotted decimal notation.
> pcf ipv4_address
> Clears multicast sessions connected via the packet control function defined by ipv4_address. The address must be specified using the standard IPv4 dotted decimal notation.
> pdsn_service name
> Clears multicast sessions connected to the packet data service name. The packet data service must have been previously configured.
> verbose
> Indicates the output should provide as much information as possible. If this option is not specified then the output is the standard level which is the concise mode.
> Usage
> Clear multicast sessions to aid in troubleshooting the system when no additional subscribers may connect or when a specific service or remote address may be having connection problems. This command may also be useful when preparing for maintenance activities such that connects may be cleared to perform any necessary procedures.
> The keywords are filters that modify or filter the criteria for deciding which sessions to clear and are described below. Multiple keywords can be entered on a command line.
> When multiple keywords are specified, the multicast sessions deleted must meet the specifications of all of the keywords.
> Example
> The following command clears the broadcast-multicast sessions having multicast address 1.2.3.4:
> clear multicast-sessions mcast-address 1.2.3.4
> The following command clears the broadcast-multicast session(s) having call id 00004e22:
> clear multicast-sessions callid 00004e22
> clear orbem statistics
> Clears the CORBA element manager interface related statistics.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear orbem statistics
> Usage
> Clear the statistics to reset them to zero for the object request broker element manager interface. This may be useful when preparing to study system performance, monitor usage, or trouble shoot the administrative interfaces.
> Example
> The following command resets the statistics for the ORB element manager.
> clear orbem
> clear pdg-service statistics
> Deletes all previously gathered statistics for a specific PDG service or all PDG services configured within a context.
> Product
> PDG/TTG
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear pdg-service statistics [ name service_name ]
> name service_name
> Specifies the name of a specific PDG service configured in the context for which to clear statistics.
> service_name is the name of the PDG service and can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> Usage
> Usage Statistics for a single PDG service can be cleared using the name keyword. Statistics for all PDG services in the context can be deleted by entering the command with no keywords.
> If this command is executed from within the local context with no keywords, statistics will be cleared for every PDG service configured on the system regardless of context. In addition, if the name keyword is used when executing from within the local context, statistics for all PDG services configured with the specified name will be cleared regardless of context.
> Example
> Example(s) The following command clears statistics for a PDG service named pdg1:
> clear pdg-service statistics pdg1
> clear pgw-service
> Clears PDN Gateway statistics and counters found in show command outputs and bulk statistics associated with all P-GW services or a specific service defined by the parameter in this command.
> Product
> P-GW
> Privilege
> Operator
> Syntax
> clear pgw-service statistics { all | name service_name }
> all
> Clears statistics and counters for all P-GW services on the system.
> name service_name
> Clears statistics and counters for a specific P-GW service name. name must be an existing P-GW service name and be from 1 to 63 alpha and/or numeric characters.
> Usage
> Use this command to clear statistics and counters in show command outputs and bulk statistics for all P-GW services or for a specific P-GW service.
> Example
> The following command clears statistics and counters for an P-GW service named pgw5:
> clear lma-service statistics name pgw5
> clear port
> Clears port related statistics.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear port { datalink counters { all | slot/port } | npucounters { all | slot/port [ untagged | vlan tag_id ] }
> datalink
> Clear the data link port statistics.
> npu
> Clear statistics for the network processing unit port.
> all
> Clear counters for all datalink or NPU ports.
> slot/port
> Clear the statistics for the specified slot and port number.
> untagged
> Clear NPU statistics for all ports that do not have a VLAN tag.
> vlan tag_id
> Clear NPU statistics for the port that has the specified VLAN tag ID. tag_id must be a previously configured VLAN tag id.
> Usage
> Manually clear the statistics for a specified port. This is useful when preparing to trouble shoot or monitor the system.
> Example
> The following command clears the data link related statistics for port 1 in slot 17.
> clear port datalink counters 17/1
> The following command clears the network processing unit related statistics for port 1 in slot 17.
> clear port npu counters 17/1
> clear ppp statistics
> Clears point-to-point protocol related statistics. All PPP statistics may be cleared or just those for a specific packet data service may be cleared.
> Product
> PDSN, GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear ppp statistics [ggsn-service ggsn_name|lns-service lns_name| pcf-address [pcf_ip_addr| all ] | pdsn-service pdsn_name ]
> ggsn-service ggsn_name
> Display statistics only for the time the session is connected to the specified ggsn_name.
> lns-service lns_name
> Display statistics only for the time the session is connected to the specified lns_name.
> pcf-address [ pcf_ip_addr | all ]
> Display statistics only for the time the session is connected to the specified PCF (Packet Control Function) or for all PCFs. pcf_ip_addr must be specified using the standard IPv4 dotted decimal notation.
> pdsn-service pdsn_name
> Specifies the service as pdsn_name which is to have only its statistics cleared.
> Usage
> Allows you to manually reset PPP statistics when it is desired to have counts begin again from a specific point in time.
> Example
> The following clears the statistics for all PPP counters and services.
> clear ppp statistics
> The following clears only the point-to-point protocol statistics for the service named sampleService.
> clear ppp statistics pdsn-service sampleService
> clear prepaid 3gpp2 statistics
> This command clears all of the statistics counters for 3GPP2 Pre-paid accounting. Statistics may be cleared for all services or for an individual service.
> Product
> PDSN, GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear prepaid 3gpp2 statistics { all | {ggsn-service |ha-service | lns-service | pdsn-service} {all | name service_name} }
> all
> This keyword clears prepaid statistics for all services.
> ggsn-service
> Clear statistics for GGSN service(s).
> ha-service
> Clear statistics for HA service(s).
> lns-service
> Clear statistics for LNS service(s).
> pdsn-service
> Clear statistics for PDSN service(s).
> { all | name service_name }
> all: Clear statistics for all services of the specified type.
> name service_name: Clear statistics for the service named service_name of the specified service type.
> Usage
> Use this command to clear Pre-paid statistics for a particular named service or for all services.
> Example
> To clear statistics for a PDSN service name PDSN1, enter the following command:
> clear prepaid 3gpp2 statistics pdsn-service name PDSN1
> clear prepaid wimax
> This command clears all of the statistics counters for WiMAX prepaid accounting. Statistics may be cleared for all services or for an individual service.
> Product
> ASN GW
> Privilege
> Operator
> Syntax
> clear prepaid wimax statistics { all | asngw-service { all | name service_name} | ha-service { all | name service_name} }
> all
> This keyword clears prepaid statistics for all services.
> asngw-service
> Clears prepaid statistics for ASN GW service(s).
> ha-service
> Clears prepaid accounting statistics for HA service(s).
> { all | name service_name }
> all: Clears statistics for all services of the specified type.
> name service_name: Clears statistics for the service named service_name of the specified service type.
> Usage
> Use this command to clear prepaid WiMAX accounting statistics for named service or for all services.
> Example
> The following command clears prepaid WiMAX accounting statistics for an ASN GW service name asn1:
> clear prepaid wimax statistics asngw-service name asn1
> clear qos npu stats
> Clears information pertaining to NPU QoS priority queue bandwidth allocation and sharing.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear qos npu stats inter-subscriber traffic slot slot_num
> inter-subscriber traffic slot slot_num
> Clears inter-subscriber traffic statistics for the application or line card installed in the specified slot.
> slot_num indicates the number of the chassis slot in which the card is installed and can be configured to any integer value from 1 through 48.
> Usage
> Allows you to manually reset statistics pertaining to NPU QoS priority queue bandwidth allocation.
> Example
> The following command clears statistics for a card installed in chassis slot 4:
> clear qos npu stats inter-subscriber traffic slot 4
> clear radius accounting archive
> This command clears archived RADIUS accounting messages associated with a AAA group, or all the archived RADIUS accounting messages in the context in which the command is executed depending on the option chosen. The scope of the command is limited to the context in which it is executed including for local context.
> Important: This command is only available in StarOS 8.3 and later. For more information, please contact your local service representative.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clear radius accounting archive { all | radius group group_name } [ -noconfirm ]
> all
> Clears all archived RADIUS accounting messages in the context.
> radius group group_name
> Clears all archived RADIUS accounting messages for the specified group.
> group_name must be the name of a RADIUS group, and must be a string of 0 through 64 characters in length.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to clear the archived RADIUS accounting messages associated with a AAA group, or all the archived RADIUS accounting messages in the context in which the command is executed.
> Example
> Use the following command to clear all archived RADIUS accounting messages for the group named test12.
> clear radius accounting archive radius group test12
> clear radius counters
> Clears statistics for RADIUS servers and server group. The statistics for all RADIUS servers or server group may be cleared or only a specified server.
> Product
> PDSN, GGSN, ASN-GW
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear radius counters { all | radius group group_name| server ip_address [ port number ] }
> all | radius group group_name | server ip_address [ port number ]
> all: Clears statistics for all servers.
> server ip_address [ port number ]: Clears statistics only for the server specified by ip_address. Optionally specify the port which is to have its RADIUS statistics cleared, where port number must be an integer from 0 through 65535. ip_address must be specified using the standard IPv4 dotted decimal notation.
> radius group group_name: Clears all configured authentication / accounting servers in the specified RADIUS group. group_name must be name of server group configured in specific context for authentication/accounting, and must be a string of 1 through 63 characters in length.
> Usage
> Clear the statistics to reset them to zero prior to logging or monitoring the system for troubleshooting, performance measurements, etc.
> Example
> The following command clears the statistics for all RADIUS servers.
> clear radius counters all
> The following command resets the statistics only for the server 1.2.3.4.
> clear radius counters server 1.2.3.4
> The following command resets the statistics only for the server group named star1.
> clear radius counters radius group star1
> clear rohc statistics
> This command clears statistics and counters collected since the last reload or clear command was issued for ROHC IP header compression.
> Product
> PDSN
> Privilege
> Administrator, Config-administrator, Operator, Inspector
> Syntax
> clear rohc statistics [ pdsn-service pdsnsvc_name ]
> pdsn-service pdsnsvc_name
> Clear ROHC statistics and counters for the specified PDSN service.
> Usage
> Use this command to clear ROHC statistics for all services or for a specific PDSN.
> Example
> The following command clears ROHC statistics and counters for the PDSN service named pdsn1:
> clear rohc statistics pdsn-service pdsn1
> clear rp service-option
> Clears the R-P interface service option statistics.
> Product
> PDSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear rp service-option statistics [ number option_num | pdsn-service pdsn_name ]
> number option_num | pdsn-service pdsn_name
> Default: clear the statistics for all service options and all packet data services.
> number option_num: specifies the R-P service option number for which the statistics are to be cleared. option_num must be a value in the range 0 through 1000.
> pdsn-service pdsn_name: specifies the service as pdsn_name which is to have only its statistics cleared.
> Usage
> Clear the R-P service option statistics prior to monitoring the system for bench marking or for detecting areas of further research.
> Example
> The following resets the service option statistics for service option 23 and packet data service sampleService, respectively.
> clear rp service-option statistics number 23 clear rp service-option statistics pdsn-service sampleService
> clear rp statistics
> Clears the R-P interface statistics. The statistics for a specific packet data server or peer node may be cleared if specified.
> Product
> PDSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear rp statistics [ pdsn-service name | peer-address [ peer_address | all ] ]
> pdsn-service name | peer-address [ peer_address | all ]
> Default: clear all R-P associated statistics.
> pdsn-service name: specifies the packet data service specified by name is to have its statistics reset.
> peer-address [ peer_address | all ]: specifies that statistics for the specified peer, or all peers, are to be cleared. ip_address must be specified using the standard IPv4 dotted decimal notation.
> Usage
> Clear the statistics to prepare for monitoring the system.
> Example
> The following command resets all the associated statistics for the R-P interfaces.
> clear rp statistics
> The following clears the statistics for the packet data service sampleService.
> clear rp statistics pdsn-service sampleService
> The following command resets the statistics associated with peer node with IP address 1.2.3.4.
> clear rp statistics peer-address 1.2.3.4
> clear session disconnect-reasons
> Clears the session disconnect reason statistics for all sessions on the system.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear session disconnect-reasons
> Usage
> Sets the counters for session disconnect reasons to zero (0) in preparation for a monitoring or troubleshooting session.
> Example
> clear session disconnect-reasons
> clear session setuptime
> Clears the session setup time statistics for PCFs or SGSNs. If no keyword is specified the summary statistics displayed by the show session setuptime command are cleared.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clearsessionsetuptime { pcf { pcf_addr | all } | sgsn { sgsn_addr | all } }
> pcf { pcf_addr | all }
> pcf_addr: Clear the setup time counters for the PCF at the specified IP address. pcf_addr must ba an IP v4 addresses expressed in dotted decimal notation.
> all: Clear the setup time counters for all PCFs.
> sgsn { sgsn_addr | all }
> sgsn_addr: Clear the setup time counters for the SGSN at the specified IP address. sgsn_addr must ba an IP v4 addresses expressed in dotted decimal notation.
> all: Clear the setup time counters for all SGSNs.
> Usage
> Sets the counters for session disconnect reasons to zero (0) in preparation for a monitoring or troubleshooting session.
> Example
> To clear the statistics for the PCF at IP address 192.168.100.10, enter the following command:
> clear session setuptime pcf 192.168.100.10
> clear session subsystem
> Clears all session subsystem statistics for the current context.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear session subsystem
> Usage
> Clear the statistics in preparation for a troubleshooting or monitoring session so that the counters are at a well known values.
> Example
> clear session subsystem
> clear sgtpu statistics
> Clears all SGTPU statistics for the current context.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear sgtpu statistics [ ggsn-address ipv4_address | iups-service iups_srvc_name | rnc-address ipv4_address | sgtp-service sgtp_srvc_name |gprs-service gprs_srvc_name nsei nse_id ]
> Usage
> Clear the statistics in preparation for a troubleshooting or monitoring session so that the counters.
> Example
> clear sgtpu statistics gprs-service SGSN1Gprs1 nsei 2445
> clear sgw-service statistics
> Clears Serving Gateway statistics and counters found in show command outputs and bulk statistics associated with all S-GW services or a specific service defined by the parameter in this command.
> Product
> S-GW
> Privilege
> Operator
> Syntax
> clear sgw-service statistics { all | name service_name }
> all
> Clears statistics and counters for all S-GW services configured on the system.
> name service_name
> Clears statistics and counters for a specific S-GW service name. service_name must be an existing S-GW service name and be from 1 to 63 alpha and/or numeric characters.
> Usage
> Use this command to clears statistics and counters in show command outputs and bulk statistics for all S-GW services or for a specific S-GW service.
> Example
> The following command clears statistics and counters for an S-GW service named
> sgw3:
> clear sgw-service statistics name sgw3
> clear snmp trap
> Clears all SNMP event trap notifications from the buffer.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear snmp trap { history | statistics }
> history
> Clears all SNMP historical trap information from system buffer.
> statistics
> Clears all SNMP event trap information from system buffer.
> Usage
> Use this command to empty the buffer of all SNMP trap notifications.
> Example
> Following command clears the all historical SNMP traps from the system buffer:
> clear snmp trap history
> clear srp checkpoint statistics
> Clears the SRP checkpoint interface statistics.
> Product
> HA, GGSN PDIF
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear srp checkpoint statistics
> Usage
> Clears the srp checkpoint statistics to prepare for srp monitoring.
> Example
> The following command resets all the associated statistics for srp checkpoint.
> clear srp checkpoint statistics
> clear srp statistics
> Clears the SRP statistics.
> Product
> HA, GGSN PDIF
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear srp statistics
> Usage
> Clears the srp statistics to prepare for srp monitoring.
> Example
> The following command resets all the associated statistics for srp.
> clear srp statistics
> clear subscribers
> Disconnects subscribers based on specified criteria.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> clear subscribers [ keywords ] [ verbose ] [ -noconfirm ]
> The keywords are filters that modify or filter the criteria for deciding which subscriber sessions to clear and are described below. Multiple keywords can be entered on a command line.
> When multiple keywords are specified, the subscriber sessions deleted must meet the specifications of all of the keywords.
> For example; if you enter the following command:
> clear subscribers ip-pool pool1 card-num 1
> Only subscriber sessions that were assigned an IP address from the IP pool named pool1 and are also being processed by the processing card in slot 1 are cleared. All other subscriber sessions that do not meet these criteria remain and are not cleared.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Important: The Operator privilege does not have access to this keyword.
> active
> Only disconnects subscribers who currently have active sessions.
> all
> Disconnects all subscribers.
> Important: The Operator privilege does not have access to this keyword.
> apn name
> Clears all PDP contexts accessing a specific access point name (APN).
> apn_name is the name of the APN and can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> asn-peer-address ip_address
> Clears information for subscribers on an ASN GW trusted peer.
> ip_address is the IPv4 address of the ASN GW peer server in dotted decimal notation.
> asngw-service service_name
> Clears counters for subscribers accessing the ASN GW service.
> service_name must be an existing service and be from 1 to 63 alpha and/or numeric characters in length.
> asnpc-service service_name
> Clears counters for subscribers accessing the ASN PC service.
> service_name must be an existing service and be from 1 to 63 alpha and/or numeric characters in length.
> callid id
> Clears the call specified by call_id. The call ID must be specified as a 4-byte hexadecimal number.
> card-num card_num
> The slot number of the processing card by which the subscriber session is processed. card_num is a slot number from 1 through 7 or 10 through 16.
> ccoa-only
> This option clears the subscribers that registered a MIP co-located COA directly with the HA.
> This option is only valid when MIPHA session license is enabled.
> configured-idle-timeout [ < | > | greater-than | less-than ] value
> Disconnects subscribers whose idle timeout matches the specified criteria. A value of 0 (zero) indicates that the subscribers idle timeout is disabled.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 4294967295.
> connected-time [ < | > | greater-than | less-than ] value
> Disconnects subscribers who have been connected for the specified length of time.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 4294967295.
> cscf-service service_name
> Clears all subscribers from the specified CSCF service.
> service_name must be an existing service and be from 1 to 63 alpha and/or numeric characters.
> css-delivery-sequence name
> Important: This is a restricted keyword. In StarOS 9.0 and later, this keyword is obsoleted.
> css-service name
> Important: This is a restricted keyword. In StarOS 9.0 and later, this keyword is obsoleted.
> dhcp-server address
> Clears all PDP contexts that currently possess an IP address assigned from a specific DHCP server.
> dhcp_address is the IP address of the DHCP server expressed in dotted decimal notation.
> dormant
> Only disconnect subscriber sessions that are dormant (not transmitting or receiving data).
> fa address
> Disconnects all subscribers connected to the foreign agent specified by fa_address. The address must be specified using the standard IPv4 dotted decimal notation.
> fa-service name
> Disconnects all subscribers connected to the foreign agent specified by fa_name. The foreign agent name must have been previously defined.
> firewall { not-required | required }
> Clears all subscriber information for the specified subscribers:
> not-required: Subscribers for whom firewall processing is not-required.
> required: Subscribers for whom firewall processing is required.
> firewall-policy fw_policy_name
> This keyword is obsolete.
> ggsn-service name
> Clears all PDP contexts accessing a specific GGSN service.
> ggsn_name is the name of the APN and can be from 1 to 63 alpha and/or numeric characters and is case sensitive.
> gsm-traffic-class { background | conversational | interactive { priority } | streaming }
> Subscribers whose traffic matches the specified 3GPP traffic class.

> • | background: 3GPP QoS background class.

> • | conversational: 3GPP QoS conversational class.

> • | interactive: 3GPP QoS interactive class. Must be followed by a traffic priority. priority can be configured to any integer value from 1 to 3.

> • | streaming: 3GPP QoS streaming class.

> gtp-version
> Displays the specific GTP version number. Must be followed by one of the supported GTP versions (0 or 1).
> The following filter keywords are valid with this command:
> active-charging-service, apn, asngw-service, asnpc-service, asn-peer-address, bearer-establishment, callid, card-num, coaa-only, configured-idle-timeout, connected-time, cscf-service, dhcp-server, fa, fa-service, firewall, ggsn-service, gprs-service, gsm-traffic-class, gtp-version, ha, ha-ipsec-service, ha-service, idle-time, ims-auth-service, imsi, ip-address, ip-alloc-method, ip-pool, ipv6-address, ipv6-prefix, l3-tunnel-local-addr, lac, lac-service, lns, lns-service, long-duration-time-left, mip-udp-tunnel-only, mipv6ha-service, msid, msisdn, network-requested, network-type, pcf, pdg-service, pdif-service,, pdsn-service, plmn-type, rulebase, rx-data, session-time-left, sgsn-address, sgsn-service, tx-data, username, grep, more
> ha address
> Disconnects all subscribers connected to the home agent specified by ha_address. The address must be specified using the standard IPv4 dotted decimal notation.
> ha-ipsec-only
> Disconnects all MIP HA sessions with IPsec tunnels.
> ha-service name
> Disconnects all subscribers connected to the home agent specified by ha_name. The home agent name must have been previously defined.
> hsgw-service name
> Disconnects subscribers using this HRPD Serving Gateway (HSGW) service configured on this system. name must be an existing HSGW service and be from 1 to 63 alpha and/or numeric characters.
> idle-time [ < | > | greater-than | less-than ] value
> Disconnects subscribers whose idle time matches the specified length of time.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 4294967295.
> ims-auth-service name
> Disconnects subscribers using this IMS Authorization Service configured on this system. name must be an existing IMS Authorization Service and be from 1 to 63 alpha and/or numeric characters.
> imsi id
> Disconnects the subscriber with the specified id. The IMSI (International Mobile Subscriber Identity) ID is a 50-bit field which identifies the subscriber’s home country and carrier. Wildcard characters $ and * are allowed. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as a wildcard enclose them in single quotes ( ‘ ). For example; ‘$’.
> ip-alloc-method {aaa-assigned | dhcp [ relay-agent | proxy-client ] | dynamic-pool | l2tp-lns-assigned | mip-ha-assigned | ms-provided-static | not-ms-provided-static | static pool }
> Displays the specific IP Allocation Method. Must be followed by one of the IP Allocation Methods:

> • | aaa-assigned: Selects subscribers whose IP Addresses were assigned by AAA.

> • | dhcp: Selects subscribers whose IP Addresses were assigned by DHCP.

> • | relay-agent: Selects subscribers whose IP Addresses were assigned by the DHCP Relay Agent

> • | proxy-client: Selects subscribers whose IP Addresses were assigned by the DHCP Proxy Client

> • | dynamic-pool: Selects subscribers whose IP Addresses were assigned from a dynamic IP address pool.

> • | l2tp-lns-assigned: Selects subscribers whose IP Addresses were assigned by the Layer 2 Tunneling Protocol Network Server.

> • | mip-ha-assigned: Selects subscribers whose IP Addresses were assigned by the Mobile IP Home Agent.

> • | ms-provided-static: Selects subscribers whose IP Addresses were provided by the Mobile Station.

> • | not-ms-provided-static: Selects subscribers whose IP Addresses were not provided by the Mobile Station.

> • | static-pool: Selects subscribers whose IP Addresses were assigned from a static IP address pool.

> ip-address address
> Disconnects all subscribers connected to the specified ip_address. The address must be specified using the standard IPv4 dotted decimal notation.
> ip-pool name
> Disconnects all subscribers assigned addresses from the IP address pool pool_name. pool_name must be the name of an existing IP pool or IP pool group.
> ipv6-address address
> Clears all subscribers connected to the specified IPv6 address.
> ipv6-prefix prefix
> Clears subscribers from a specific IPv6 address prefix.
> lac address
> Disconnects all calls to the peer LAC (L2TP access concentrator) specified by address. The address must be specified using the standard IPv4 dotted decimal notation.
> lac-service name
> Disconnects all calls for this LAC service. name is a string of 1 to 63 characters.
> lma-service name
> Disconnects subscribers using this LMA service configured on this system. name must be an existing LMA service and be from 1 to 63 alpha and/or numeric characters.
> lns address
> Disconnects calls to the peer LNS (L2TP network server) specified by address. The address must be specified using the standard IPv4 dotted decimal notation.
> lns-service name
> Disconnects calls associated with the LNS service named name. name is a string of 1 to 63 characters.
> long-duration-time-left [ < | > | greater-than | less-than ] value
> Disconnects subscriber sessions whose time left for the maximum duration of their session matches the length of time specified.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 4294967295.
> mag-service name
> Disconnects subscribers using this Mobile Access Gateway (MAG) service configured on this system. name must be an existing MAG service and be from 1 to 63 alpha and/or numeric characters.
> mip-udp-tunnel-only
> This option clears the subscribers that negotiated MIP-UDP tunneling with the HA.
> This option is only valid when MIP NAT Traversal license is enabled.
> mme-address ipv4_addr
> Disconnects subscribers using this peer Mobility Management Entity (MME). ipv4_addr must be an existing peer MME IPv4 address and be specified in dotted decimal notation.
> mme-only
> Disconnects all MME subscriber sessions on the system.
> mme-service name
> Disconnects subscribers using this MME service configured on this system. name must be an existing MME service and be from 1 to 63 alpha and/or numeric characters.
> msid id
> Disconnects the mobile user identified by ms_id. ms_id must be from 7 to 16 digits specified as an IMSI, MIN, or RMI. Wildcard characters $ and * are allowed. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as a wildcard enclose them in single quotes ( ‘ ). For example; ‘$’.
> In case of enforce imsi-min equivalence is enabled on the chasis and MIN or IMSI numbers supplied, this filter will clear subscribers with a corresponding MSID (MIN or IMSI) whose lower 10 digits matches to lower 10 digits of the supplied MSID.
> clear subscribers msid 111110123456789 or
> clear subscribers msid 0123456789
> will clear any subscriber with a MSID that match the lower 10 digits of MSID supplied, i.e. 0123456789.
> msisdn msisdn
> Clears information for the mobile user identified by Mobile Subscriber ISDN Number (MSISDN). msisdn must be from 7 to 16 digits specified as an IMSI, MIN, or RMI.
> nat { not-required | required [ nat-ip nat_ip_address | nat-realm nat_realm ] }
> Clears all subscriber information for the specified subscribers:
> not-required: Subscribers for whom NAT processing is not required.
> required: Subscribers for whom NAT processing is required.
> Important: The nat-ip keyword is only available in StarOS 8.3 and later.
> nat-ip nat_ip_address: Subscribers for whom NAT processing is enabled and are using the specified NAT IP address. nat_ip_address specifies the NAT IP address and must be a standard IPv4 address.
> nat-realm nat_realm: Subscribers for whom NAT processing is enabled and are using the specified NAT realm. nat_realm specifies the NAT realm name and must be a string from 1 through 63 characters in length.
> network-requested
> Disconnect subscriber sessions that were initiated by the GGSN network requested create PDP context procedure.
> network-type { gre | ipv4 | ipv6 | ipip | l2tp | mobile-ip | proxy-mobile-ip }
> Disconnects subscriber sessions based on the network type. The following network types can be selected:

> • | gre : Generic Routing Encapsulation (GRE) per RFC 2784

> • | ipv4 : Internet Protocol version 4 (IPv4)

> • | ipv6 : Internet Protocol version 6 (IPv6)

> • | ipip : IP-in-IP encapsulation per RFC 2003

> • | l2tp: Layer 2 Tunneling Protocol encryption per RFC 2661

> • | mobile-ip : Mobile IP

> • | proxy-mobile-ip : Proxy Mobile IP

> pcf [ < | > | less-than | greater-than ] ipv4_address [ [ < | > | less-than | greater-than ] ipv4_address ]
> Displays information for subscribers connected via the packet control function with a specific or range of IP address ipv4_ddress. The address must be specified using the standard IPv4 dotted decimal notation.

> • | <: Filters output so that only information less than the specified IPv4 address value is displayed.

> • | >: Filters output so that only information greater than the specified IPv4 address value is displayed.

> • | less-than:Filters output so that only information less than the specified IPv4 address value is displayed.

> • | greater-than:Filters output so that only information greater than the specified IPv4 address value is displayed.

> Note: It is possible to define a limited range of IP addresses by using the less-than and greater-than options to define minimum and maximum values.
> pdsn-service name
> Disconnect all subscribers connected to the packet data service pdsn_name. The packet data service must have been previously configured.
> pdg-service service_name
> Disconnects subscriber sessions that are using the PDG service.
> service_namemust be an existing service and be from 1 to 63 alpha and/or numeric characters.
> pdif-service service_name
> Clears counters for subscribers accessing the Packet Data Interworking Function (PDIF) service.
> service_name must be an existing service and be from 1 to 63 alpha and/or numeric characters.
> pgw-only { all | imsi id ebi id | pgw-service name | sgw-address ipv4_addr }
> all: Disconnects all subscribers for all P-GW services on this system.
> imsi id ebi id: Disconnects subscribers based on their International Mobile Subscriber Identification (IMSI). id must be the 3 digit MCC (Mobile Country Code), follow by the 2 or 3 digits of the MNC (Mobile Network Code) and the MSIN (Mobile Subscriber Identification Number). id should not exceed 15 digits.
> Example: 123-45-678910234 must be entered as 12345678910234
> The EBI (EPS Bearer Identity) id must be a valid EBI and be an integer value from 5 to 15.
> pgw-service name: Disconnects all subscribers using this P-GW service. name must be an existing P-GW service and be from 1 to 63 alpha and/or numeric characters.
> sgw-address ipv4_addr: Disconnects all subscribers using this S-GW IP address. ipv4_addr must be an existing IPv4 address and be specified in dotted-decimal notation.
> plmn-type { home | roaming |visiting }
> For GGSN, disconnect subscribers whose subscriber type matches the specified type.
> qci { number }
> Disconnects subscribers based on their QCI identity. number must be an integer value from 0 to 9.
> rx-data [ < | > | greater-than | less-than ] value
> Disconnects subscribers who have received the specified number of bytes of data.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 18446744073709551615.
> s5-proto { gtp | pmip }
> Disconnects subscribers based on their S5 interface protocol type.
> gtp: Indicates that the GTP protocol is used on the S5 interface for the subscribers being disconnected.
> pmip: Indicates that the PMIP protocol is used on the S5 interface for the subscribers being disconnected.
> session-time-left [ < | > | greater-than | less-than ] value
> The amount of time left for the subscriber session.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 4294967295.
> sgsn-address address
> Clears all PDP contexts currently being facilitated by a specific SGSN.
> address is the IP address of the SGSN expressed in dotted decimal notation.
> sgsn-service name
> Clears all PDP contexts associated with SGSN. This keyword can be used with filtering keywords that are part of the clear subscriber command set.
> Using this keyword can trigger a network-initiated service request (paging) procedure.
> name is the identity of a specific SGSN-service configuration. The name consists of 1 to 63 alphanumeric characters.
> sgw-only
> Disconnects all S-GW subscriber sessions on the system.
> sgw-service name
> Disconnects subscribers using this Serving Gateway (S-GW) service configured on this system. name must be an existing S-GW service and be from 1 to 63 alpha and/or numeric characters.
> tx-data [ < | > | greater-than | less-than ] value
> Disconnects subscribers who have transmitted the specified number of bytes of data.
> <: Filters output so that only information less than the specified value is cleared.
> >: Filters output so that only information greater than the specified value is cleared.
> greater-than: Filters output so that only information greater than the specified value is cleared.
> less-than: Filters output so that only information less than the specified value is cleared.
> value: If no other filtering options are specified only output matching value is cleared. If value is not specified all data is cleared. value must be an integer from 0 through 18446744073709551615.
> username name
> Disconnect the subscriber with the specified username
> name is the username of the subscriber to be cleared. name must be a sequence of characters and/or wildcard characters ('$' and '*') from 1 to 127 characters in length. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as wildcard enclose them in single quotes ( ‘). For example; ‘$’.
> verbose
> Indicates the output should provide as much information as possible. If this option is not specified then the output is the standard level which is the concise mode.
> grep grep_options | more
> Indicates the output of the command is to be piped (sent) to the command specified. A command to send output to must be specified.
> For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in the Cisco ASR 500 Series Command Line Interface Reference.
> Usage
> Clear subscribers sessions to aid in troubleshooting the system when no additional subscribers may connect or when a specific service or remote address may be having connection problems. This command may also be useful when preparing for maintenance activities such that connects may be cleared to perform any necessary procedures.
> Example
> The following examples illustrate the basic command usage as well as the redirection of the command output. Not all options are exemplified as all options follow the same basic constructs.
> The following are basic subscriber clearing examples.
> clear subscribers username user1
> clear subscribers ha sampleService
> clear subscribers ip-pool poolName verbose
> The following command disconnects users connected to the foreign agent with IP address 1.2.3.4.
> clear subscribers fa 1.2.3.4
> The following redirects the output of the command to the more command for paging of the output to allow easier viewing of all output by the user. This example highlights the use of the verbose option as well.
> clear subscribers all verbose | more
> clear super-charger
> Deletes the subscriber’s backed-up subscription data.
> Product
> SGSN
> Privilege
> Administrator, Security Administrator
> Syntax
> clear super-charger { imsi | all }
> imsi
> Defines a specific subscriber’s international mobile subscriber identity (IMSI) number.
> imsi - up to 15 digits. This number includes the MCC (mobile country code), the MNC (mobile network code) and the MSIN (mobile station identification number),
> all
> Instructs the SGSN to delete subscription data for all super charger subscribers.
> Usage
> Use this command to clear (delete) the subscription data records for one or all subscribers with super charger subscription configuration
> Example
> The following command deletes the backed up records for the subscriber identified by the IMSI 90121882144672.
> clear super-charger imsi 90121882144672
> cli
> This command specifies command line interface (CLI) session behavior
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator, inspector
> Syntax
> cli { history | stop-on-first-error }
> no cli { history | stop-on-first-error }
> no
> Disables the specified keyword functionality.
> history
> Default: Enabled
> Enables command line history for the current command line session.
> stop-on-first-error
> Default: Disabled
> When this is enabled, when a configuration file is loaded, on the first syntax error the system stops loading the configuration file.
> Usage
> This command controls CLI settings pertaining to the maintenance of a per-session command history and syntax error monitoring during configuration file loading.
> By default, the system maintains a list of commands executed during each CLI session. This list is referred to as a history.
> In addition, the system can be configured to stop loading a configuration if a syntax error is detected. By default, the system identifies the error but continues to process the configuration file.
> Example
> The following command disables the keeping of a CLI history for the current session:
> no cli history
> clock set
> Sets the system time.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> clock set date_time
> date_time
> Specifies the date and time to set the system clock. Specified as YYYY:MM:DD:HH:mm or YYYY:MM:DD:HH:mm:ss. Where YYYY is a 4-digit year, MM is a 2-digit month in the range 01 through 12, DD is a 2-digit day in the range 01 through 31, HH is a 2-digit hour in the range 00 through 23, mm is a 2-digit minute in the range 00 through 59, and ss is a 2 digit second in the range 00 through 59.
> Usage
> Set the clock to adjust the system clock for such things as timing drift, day-light savings adjustment, etc. New settings are immediately applied to all CPUs in the system.
> Important: This command should only be used if there is no NTP server enabled for any context. If NTP is running on the system, this command returns a failure.
> Example
> The following commands set the system clock where one sets the exact second as well.
> clock set 2003:08:23:02:30 clock set 2003:08:23:02:30:30
> configure
> Sets the mode to the global configure mode. May also be used to set the mode to the configure mode and pre-load the configuration referred to by the options.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> configure [ url [ verbose ] ]
> url
> Specifies the location of a configuration file to pre-load. url may refer to a local or a remote file. url must be entered using one of the following formats:

> • | ASR 5000:

> • | [ file: ]{ /flash | /pcmcia1 | /hd } [ /directory ]/file_name

> • | tftp://{ host[ :port# ] } [ /directory ]/file_name

> • | [ http: | ftp: | sftp: ]//[ username [ :password ] @ ] { host } [ :port# ] [ /directory ]/file_name

> 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.
> verbose
> Displays each the line number and actual line content from the configuration as it is processed.
> Usage
> If no URL is specified, executing this command causes the CLI to enter the Global Configuration Mode.
> If a URL is specified, executing this command loads the specified configuration file.
> Example
> The following simply changes the mode to the command line interface global configuration mode.
> configure
> The following command loads a configuration file from the node sampleNode given the path specified and a local file, respectively.
> configure ftp://sampleNode/pub/glob.cfg
> configure /pcmcia1/pub/glob.cfg verbose
> context
> Sets the current context to the context specified.
> Product
> All
> Privilege
> Security Administrator, Administrator, Operator, Inspector
> Syntax
> context name
> name
> Specifies the context of interest. Must be a previously defined context.
> Usage
> Change the current context when it is desired to configure and/or manage a specific context.
> Example
> The following sets the current context to the sampleContext context.
> context sampleContext
> copy
> Copies files from one location to another. Allows files to be copied to/from locally as well as from one remote location to another.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> copy from_url to_url [ passive ] [ -noconfirm ]
> from_url
> Specifies the source of the copy. url may refer to a local or a remote file. url must be entered using one of the following formats:

> • | ASR 5000:

> • | [ file: ]{ /flash | /pcmcia1 | /hd }[ /directory ]/file_name

> • | tftp://{ host[ :port# ] }[ /directory ]/file_name

> • | [ http: | ftp: | sftp: ]//[ username [ :password ]@ ] { host }[ :port# ][ /directory ]/file_name

> 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.
> to_url
> Specifies the destination of the copy. url may refer to a local or a remote file. url must be entered using one of the following formats:

> • | ASR 5000:

> • | [ file: ]{ /flash | /pcmcia1 | /hd }[ /directory ] /file_name

> • | tftp://{ host[ :port# ] } [ /directory ] /file_name

> • | [ ftp: | sftp: ] / / [ username [ :password ] @ ] { host } [ :port# ] [ /directory ] /file_name

> 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.
> passive
> Indicates the file copy is to use the passive mode.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Important: Use of the -noconfirm option allows the over writing of an existing file if the destination file already exists.
> Usage
> Copy configuration files, log files, etc.,to provide backups of data through the network.
> Example
> The following copies files from the local /flash/pub directory to remote node remoteABC’s /pcmcia2/pub directory with and without confirmation respectively.
> copy http://remoteABC/pub/june.cfg /flash/pub/june.cfgcopy tftp://remoteABC/pub/june.cfg /pcmcia2/pub/june.cfg -noconfirm
> The following copies files from remote node remoteABC to remote node remote123.
> copy ftp://remoteABC/pub/may.cfg ftp://remote123/pub/may.cfg
> crash copy
> Copies individual crash files (one-at-a-time) and optionally the core dump file from the stored crash records on the chassis to a user-specified location.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> crash copy number number url to_url[ core ]
> number number
> The identification number of the crash record. number must be an integer representing a valid record number selected from a range of 1 to 120. To determine the numeric identity of a specific crash file, use the show crash list command in Exec mode.
> url to_url
> Specifies the destination of the copy. url may refer to a local or a remote file. url must be entered using one of the following formats:

> • | ASR 5000:

> • | [ file: ] { /flash | /pcmcia1 | /hd } [ /directory ] /

> • | tftp://{ host[ :port# ] } [ /directory ] /

> • | [ ftp: | sftp: ]//[ username [ :password ] @ ] { host } [ :port# ] [ /directory ] /

> Important: Use of the SMC hard drive is not supported in this release.
> directory: the name of the target directory.
> username: the username to be authenticated to provide access to targeted server.
> password: the username’s password to be authenticated.
> host: the IP address or host name of the targeted server.
> port#: the number of the target server’s logical port used for the selected communication protocol.
> Important: Do not specify a target filename as this will prevent the file from writing to the target server. The system generates and provides a timestamp-based filename that appears at the destination when the copy command completes.
> core
> Including this keyword as part of the command instructs the system to copy the core dump to the targeted storage server. The core cannot be copied alone; it must be part of a crash copy action included when copying a crash file.
> Usage
> Copy crash files of core dump to another location for backup or analysis.
> Example
> The following uses ftp to copy stored record number 5 and the core dump from the crash record list to a targeted remote node directory called crasharchive through port 22 of the targeted server remoteABC with access through user homeboy whose password is secret.7.word.
> crash copy number 5 url ftp://homeboy:secret.7.word@ remoteABC:22/crasharchive/ core
> crypto-group
> Allows the manual switchover of redundant IPSec tunnels belonging to a specific crypto group.
> Product
> PDSN, GGSN
> Privilege
> Security Administrator, Administrator, Operator
> Syntax
> crypto-group name group_name activate { primary | secondary }
> group_name
> group_name is the name of the crypto group to which the tunnels to be switched are associated.
> activate { primary | secondary }
> Allows you to specify which tunnel to activate (i.e. is to facilitate user traffic):

> • | primary : Switch traffic to the primary tunnel in the group.

> • | secondary : Switch traffic to the secondary tunnel in the group.

> Usage
> This command is used in conjunction with the Redundant IPSec Tunnel Fail-over feature.
> Use this command to manually switch traffic to a specific tunnel in a crypto group if the automatic switchover options have been disabled. Refer to the switchover command in the Crypto Group configuration mode for more information.
> Example
> The following command manually switches user traffic to the secondary tunnel in the crypto group called group1:
> crypto-group group1 activate secondary

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883