Important: Unless otherwise indicated, all statistics are counters. For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create an ASN-GW schema called asngw_statistics that specifies a schema format of:
asngw schema asngw_statistics format “VPN name: %vpnname%\nVPN ID: %vpnid%\nASN-GW Service Name: %servname%\nASN-GW Service Identifier: %servid%\nPeer IP Address: %peeripaddr%”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
The following command creates a schema named bcmcs1stats1 that records the number of sessions currently facilitated by BCMCS:
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
Important: Not supported on all platforms
card schema cardresourcestats format “Chassis slot number: %slot%\nAvailable Memory: %memtotal%\tMemory Used (%): %memused%\nAvailable CPU (%): %cpuidle%”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3600 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For the complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a context schema called sfw_context_stats1 that specifies a schema format of:
context schema sfw_context_stats1 format “Packets received Rx: %sfw-total-rxpackets%\nPackets Sent Tx:: %sfw-total-txpackets%\nICMP Packets discarded: %fw-icmp-discardpackets%”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a CSCF schema called cscf_statistics that specifies a schema format of:
cscf schema cscf_statistics format
“Call Attempts Rx: %callattrx%\nCall Attempts Tx: %callatttx%\nCall Successes Rx: %callsuccrx%\nCall Successes Tx: %callsucctx%\nCall Failures Rx: %callfailrx%\nCall Failures Tx: %callfailtx%”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
For an eGTP-C-level schema called egtpcservicestats that specifies a schema format of:
egtpc schema egtpcservicestats format “Number of GTP Tunnel Requests Sent: %tun-sent-cresess%\nNumber of GTP Tunnel Requests Received: %tun-recv-cresess%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a FA-level schema named faservicestats that separates the
date,
time, and
vpnname by tabs, enter the following command:
fa schema faservicestats format %date%\t%time%\t%vpnname%
number must be an integer value from 1 to 4.
Important: Use of bulk statistics “files” is optional. If you do not wish to configure bulk statistic “files”, you can perform a standard configuration using the commands in the Bulk Statistic Configuration Mode. Note, however, that the system logically assigns “file 1” to the standard configuration. Therefore, if you wish to configure bulk statistics “files” at a later time, “file 1” will already be used.
Caution: If the Web Element Manager application is used to collect and process (XML parsing, graphing, etc.) bulk statistics data, “file 1” is used by the Web Element Manager’s default bulk statistics collection information and schemas. To avoid errors in processing by the Web Element Manager, do not configure "file 1" via the CLI. However, it is possible to configure files 1 through 4 using the system’s CLI, regardless of whether or not the Web Element Manager is configured as a receiver. In this case, the bulk statistics data is written to the server but not processed by the Web Element Manager application.
footer format format_string
Specifies the footer format string for use in generated data files. format_string must be from 1 to 2047 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described in the
Schema Format String Syntax section.
footer Command Format String Variables
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
gtpc_schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format gtpc_schema_format
gtpc_schema_format must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a GTPC-level schema named gtpc_stats that specifies a schema format of:
gtpc schema gtpc_stats format “Context Name: %vpnname%\nGGSN Service Name: %servname%\nTotal PDP Contexts Processed: %setup-total%\n”
gtpp_schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format gtpp_schema_format
gtpp_schema_format must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a GTPP schema named gtpp_statistics that specifies a schema format of:
gtpp schema gtpp_statistics format “Time: %time%\tTotal Redirection Requests Received: %redir-rcvd%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
For an HA schema named haservicestats that specifies a schema format of:
ha schema haservicestats format “Number of HA authentication failures: %reply-haauthfail%\nNumber of Mobile Node authentication failures: %reply-mnauthfail%\n”
header format format_string
Specifies the header format string for use in generated data files. format_string must be from 1 to 2047 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described in the
Schema Format String Syntax section.
header Command Format String Variables
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create an IP pool schema named ippoolstats that specifies a schema format of:
ippool schema ippoolstats format “
Number of IP addresses on hold: %hold%\nNumber of free IP addresses: %free%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create an IPSG schema named ipsgstats that specifies a schema format of:
ipsg schema ippoolstats format “
Context name: %vpnname%\nService name: %servname%\nTotal responses sent: %total-rsp-sent%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
TSchema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
lac schema lac1stats1 format
“%sess-curactive%-%sess-maxtunnel%”
To create a schema called lacresourcestats that specifies a schema format of:
lac schema lacresourcestats format “Number of Successful Session Connections: %sess-successful%\nNumber of Session Attempts That Failed: %sess-failed%\nNumber of Sessions Currently Active: %sess-curative%”
Caution: Bulk statistics are stored in Random Access Memory (RAM) on the SMC. In the event of power loss or system failure, the statistics will be lost. If the maximum storage limit has been reached before the system's configured transfer-interval is reached, the oldest information stored in the collection will be overwritten.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
For an LMA-level schema called lmaservicestats that specifies a schema format of:
lma schema lmaservicestats format “Number of Binding Updates Received: %bindupd%\nNumber of Binding Updates Received and Denied: %bindupd-denied%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
For a MAG-level schema called magservicestats that specifies a schema format of:
mag schema magservicestats format “Number of Binding Updates Sent: %bindupd%\nNumber of Binding Acknowledgements Received: %bindack%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
The following command creates a schema called mipv6haservicestats that records the number of authorization attempt failures due to access rejects from AAA:
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3600 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
The following command creates a schema called pdifschema1 for the category current active ipv4 sessions:
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
Important: The
card variable in the Port schema is not supported on all platforms
To create a port-level schema named portstats1 that separates the
card/port,
bcast_inpackets, and
bcast-outpackets variables by hyphens (“-”), enter the following command:
port schema portstats1 format “%card%/%port% - %bcast_inpackets% - %bcast_outpackets%”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a ppp-level schema named pppstats that specifies a schema format of:
ppp schema pppstats format “CHAP:\nAuth. Attempts: %auth-attempt-chap%\tAuth. Successes: %auth-success-chap%\nPAP:\nAuth. Attempts: %auth-attempt-pap%\tAuth. Successes: %auth-success-pap%\n”
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length and is case sensitive.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
To create a RADIUS schema named radius_statistics that specifies a schema format of:
radius schema radius_statistics format “Server: %ipaddr%\nAuthentication Requests Sent: %auth-req-sent%\nAccounting Requests Sent: %acc-req-sent%”
Default: secondary-on-failure
redundant: Files are transferred to both the primary and secondary receivers. If either transfer isn't possible, the file is transferred when possible. The system continues to hold in memory as much data as possible until the data has been successfully transferred to both receivers. Data is only discarded if the in-memory data reaches the configured limit. Refer to the
limit command.
secondary-on-failure: Files are transferred to the secondary receiver if the primary receiver fails. In-memory data is erased once the data is transferred to either the primary or secondary receiver. This is the default behavior.
Specifies the IP address of the receiver of interest. ip_address must be specified using the standard IPv4 dotted decimal notation.
primary: indicates the receiver is the primary receiver of data.
secondary: indicates the receiver is the secondary receiver of data.
mechanism { { { ftp | sftp } login user_name [ encrypted ] password pwd } | tftp } }
ftp login user_name [
encrypted ]
password pwd: the FTP protocol shall be used for data file transfer.
user_name specifies the user to provide for remote system secure logins and must be an alpha and/or numeric string of 1 through 31 characters in length. The password to use for remote system authentication is specified as
pwd and must be from 1 to 31 alpha and/or numeric characters or 1 to 64 alpha and/or numeric characters if the
encrypted keyword is also specified.
sftp login user_name [
encrypted ]
password pwd: the SFTP protocol shall be used for data file transfer.
user_name specifies the user to provide for remote system secure logins and must be an alpha and/or numeric string of 1 through 31 characters in length. The password to use for remote system authentication is specified as
pwd and must be from 1 to 31 alpha and/or numeric characters or 1 to 64 alpha and/or numeric characters if the
encrypted keyword is also specified.
tftp: the TFTP protocol is to be used to transfer files.
The encrypted keyword is intended only for use by the system while saving configuration scripts. The system displays the
encrypted keyword in the configuration file as a flag that the variable following the
password keyword is the encrypted version of the plain text password. Only the encrypted password is saved as part of the configuration file.
Important: For redundant receivers, configuration changes to the receivers are applied to all existing and all subsequent data sets pending transfer. If no receiver is configured, bulk statistics will be collected and stored on the system until the maximum amount of memory is used; they will not be transferred to the receiver(s). When the storage limit has been reached the oldest information is overwritten. When a receiver is configured for the primary and secondary target, this command will use both receivers as default if no receiver is specified.
receiver 1.2.3.4 primary mechanism tftpreceiver 1.2.3.5 secondaryno receiver 1.2.3.4
remotefile formatformat_string[ both-receivers | primary-receiver | secondary-receiver ]
Specifies the naming convention format to use. format_string must be from 1 to 127 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described in the
Schema Format String Syntax section.
Important: The remote file naming format should only use static text and bulk statistic variables to avoid any possible file creation issues on the receivers.
Important: For redundant receivers, the filenames for the output data files are applied when the information is first gathered. If the name format is modified, the change takes effect for the next data set. The current data set name remains unchanged. even if has not yet been transferred.
remotefile format simpleFormatremotefile format “%host%-%date%-%time%”remotefile format “%host%-%date%-%time%” [both-receivers]remotefile format “%host%-%date%” [primary-receiver]no remotefile format
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
rp schema rpservicestats format “Date: %date%\nTime: %time%\nNumber of Authentication Denials: %deny-auth%\n”
minutes must be an integer from 1 through 1440.
sccp schema schema_name format format_string
Specifies the naming convention format to use. format_string must be from 1 to 3599 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described by
Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
schemaschema_nameformatformat_string
schema_name must be an alpha and/or numeric string of 1 through 31 characters in length.
format_string must be an alpha and/or numeric string of 1 through 3599 characters in length, and cannot include spaces or must be a quoted string. For syntax details, see
Schema Format String Syntax section.
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
The following command creates a schema called systemstats1 that records the number of current Simple IP and the number of current Mobile IP sessions:
schema systemstats1 format “%sess-cursipconn% - %sess-curmipconn%”
schema bulksysstats format “Number of currently active sessions: %sess-curactcall%\nNumber of currently dormant sessions: %sess-curdormcall%\n”
Specifies the naming convention format to use. format_string must be from 1 to 3599 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described by
Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
Specifies the naming convention format to use. format_string must be from 1 to 3599 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described by
Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
Specifies the naming convention format to use. format_string must be from 1 to 3599 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described by
Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
Specifies the naming convention format to use. format_string must be from 1 to 3599 alpha and/or numeric characters with no spaces or as a quoted string. The format string syntax is described by
Schema Format String Syntax .
Important: For a complete list of the statistics that are supported for this schema, refer to the
Statistics and Counters Reference.
show variables [ [ apn | asngw
| bcmcs | card | closedrp | common | context
| cscf | ecs | fa | gprs
| gtpc | gtpp | ha
| ippool | ipsg
| lac | pdif | port | ppp | radius | rp | sccp | sgsn | sgtp | ss7rd |
ss7link| system | vpn ] [ obsolete ] ]
[ apn | asngw
| bcmcs | card | closedrp | common | context
| cscf | ecs | fa
| gtpc | gtpp | ha
| ippool | ipsg
| lac | pdif | port | ppp | radius | rp | sccp | sgsn | sgtp | ss7rd | ss7link| system | vpn ] [ obsolete ]
If the obsolete keyword is used, obsolete (but still available) schema variables are displayed. An asterisk (*) is displayed next to schema variables that have been obsoleted.