A10 Command Reference
A10 Command Reference
Patent Protection
A10 Networks products are protected by patents in the U.S. and elsewhere. The following website is provided to satisfy the
virtual pat- ent marking provisions of various jurisdictions including the virtual patent marking provisions of the America Invents
Act. A10 Net- works' products, including all Thunder Series products, are protected by one or more of U.S. patents and patents
pending listed at:
https://www.a10networks.com/company/legal-notices/a10-virtual-patent-marking.
Trademarks
The A10 logo, A10 Harmony, A10 Lightning, A10 Networks, A10 Thunder, aCloud, ACOS, Affinity, aFleX, aFlow, aGalaxy, aGAPI, aVCS,
AX, aXAPI, IDsentrie, IP-to-ID, SSL Insight, SSLi, Thunder, Thunder TPS, UASG, and vThunder are trademarks or registered trademarks of
A10 Networks, Inc. in the United States and other countries. All other trademarks are property of their respective owners.
Confidentiality
This document contains confidential materials proprietary to A10 Networks, Inc. This document and information and ideas herein may
not be disclosed, copied, reproduced or distributed to anyone outside A10 Networks, Inc. without prior written consent of
A10 Networks, Inc.
Anyone who uses the Software does so only in compliance with the terms of the End User License Agreement (EULA), provided later in
this document or available separately. Customer shall not:
1. reverse engineer, reverse compile, reverse de-assemble or otherwise translate the Software by any means
Disclaimer
This document does not create any express or implied warranty about A10 Networks or about its products or services, including
but not limited to fitness for a particular use and non-infringement. A10 Networks has made reasonable efforts to verify that the
information contained herein is accurate, but A10 Networks assumes no responsibility for its use. All information is provided "as-
is." The product specifications and features described in this publication are based on the latest information available; however,
specifications are sub- ject to change without notice, and certain features may not be available upon initial product release.
Contact A10 Networks for current information regarding its products or services. A10 Networks’ products and services are subject
to A10 Networks’ standard terms and conditions.
Environmental Considerations
Some electronic components may possibly contain dangerous substances. For information on specific component types, please
con- tact the manufacturer of that component. Always consult local authorities for regulations regarding proper disposal of
electronic com- ponents in your area.
Further Information
For additional information about A10 products, terms and conditions of delivery, and pricing, contact your nearest A10 Networks loca-
tion, which can be found by visiting www.a10networks.com.
Table of Contents
EXEC Commands...............................................................................................25
active-partition..................................................................................................................... 25
enable.................................................................................................................................. 26
exit....................................................................................................................................... 26
gen-server-persist-cookie.................................................................................................... 27
health-test............................................................................................................................ 28
help...................................................................................................................................... 28
no................................................................................................................................. 29
ping.............................................................................................................................. 29
show.................................................................................................................................... 30
ssh............................................................................................................................................31
telnet............................................................................................................................ 31
traceroute............................................................................................................................ 32
import........................................................................................................................... 46
locale................................................................................................................................... 49
no................................................................................................................................. 49
ping.............................................................................................................................. 49
reboot........................................................................................................................... 49
reload.................................................................................................................................. 52
repeat.................................................................................................................................. 53
show.................................................................................................................................... 53
shutdown...................................................................................................................... 53
ssh............................................................................................................................................54
Document No.: 410-P2-CLI-001 - 6/17/2016 | page 2
telnet............................................................................................................................ 54
terminal................................................................................................................................ 54
traceroute............................................................................................................................ 56
vcs.............................................................................................................................................56
write force............................................................................................................................ 56
write memory................................................................................................................ 57
write terminal................................................................................................................ 59
block-abort........................................................................................................................... 93
block-merge-end................................................................................................................. 93
block-merge-start................................................................................................................ 94
block-replace-end................................................................................................................ 94
block-replace-start............................................................................................................... 95
boot-block-fix....................................................................................................................... 95
bootimage............................................................................................................................ 96
bpdu-fwd-group............................................................................................................ 96
bridge-vlan-group................................................................................................................ 97
cgnv6................................................................................................................................... 98
class-list (for Aho-Corasick)......................................................................................................98
class-list (for IP limiting)...................................................................................................... 99
class-list (for VIP-based DNS caching)...................................................................................101
class-list (for many pools, non-LSN).......................................................................................103
class-list (string)......................................................................................................................104
class-list (string-case-insensitive)............................................................................................104
page 3 | Document No.: 410-P2-CLI-001 - 6/17/2016
configure sync................................................................................................................... 105
copy................................................................................................................................... 105
debug......................................................................................................................... 107
delete................................................................................................................................. 107
disable reset statistics.............................................................................................................108
disable slb......................................................................................................................... 108
disable-failsafe........................................................................................................................109
disable-management......................................................................................................... 109
dnssec.....................................................................................................................................111
do...................................................................................................................................... 111
enable-core....................................................................................................................... 111
enable-management......................................................................................................... 112
enable-password............................................................................................................... 114
end.................................................................................................................................... 114
environment temperature threshold........................................................................... 115
environment update-interval..............................................................................................116
erase.......................................................................................................................................117
event.................................................................................................................................. 118
exit..................................................................................................................................... 119
export-periodic................................................................................................................... 119
fail-safe...................................................................................................................................121
fw............................................................................................................................... 123
glid............................................................................................................................. 123
glm............................................................................................................................. 126
gslb.................................................................................................................................... 126
hd-monitor enable...................................................................................................... 126
health global...................................................................................................................... 126
health monitor............................................................................................................ 128
health-test.......................................................................................................................... 129
hostname........................................................................................................................... 129
hsm template..................................................................................................................... 130
icmp-rate-limit.................................................................................................................... 130
icmpv6-rate-limit................................................................................................................ 131
import......................................................................................................................... 132
import-periodic................................................................................................................... 133
interface............................................................................................................................. 135
ip................................................................................................................................ 136
ip-list.................................................................................................................................. 136
ipv6.................................................................................................................................... 136
key..........................................................................................................................................136
l3-vlan-fwd-disable............................................................................................................ 137
lacp system-priority........................................................................................................... 138
lacp-passthrough............................................................................................................... 138
ldap-server..............................................................................................................................138
link..................................................................................................................................... 140
lldp enable......................................................................................................................... 141
lldp management-address................................................................................................. 141
lldp notification interval............................................................................................... 142
lldp system-description...................................................................................................... 142
lldp system-name.............................................................................................................. 142
lldp tx fast-count......................................................................................................... 143
lldp tx fast-interval............................................................................................................. 143
lldp tx interval.................................................................................................................... 143
lldp tx hold.................................................................................................................. 144
Document No.: 410-P2-CLI-001 - 6/17/2016 | page 4
lldp tx reinit-delay....................................................................................................... 144
locale................................................................................................................................. 144
logging auditlog host.................................................................................................. 145
logging buffered......................................................................................................... 146
logging console................................................................................................................. 147
logging disable-partition-name.......................................................................................... 147
logging email buffer........................................................................................................... 147
logging email filter............................................................................................................. 148
logging email-address....................................................................................................... 151
logging export............................................................................................................ 151
logging facility.................................................................................................................... 152
logging host................................................................................................................ 152
logging monitor........................................................................................................... 153
logging single-priority........................................................................................................ 154
logging syslog.................................................................................................................... 154
logging trap................................................................................................................ 155
mac-address...........................................................................................................................155
mac-age-time.................................................................................................................... 156
maximum-paths................................................................................................................. 156
merge-mode-add............................................................................................................... 157
mirror-port.......................................................................................................................... 157
monitor....................................................................................................................... 158
multi-config................................................................................................................. 159
multi-ctrl-cpu............................................................................................................... 160
Show Commands.............................................................................................237
show aam.......................................................................................................................... 242
show access-list......................................................................................................................242
show active-partition.......................................................................................................... 242
show admin....................................................................................................................... 243
show aflex......................................................................................................................... 246
show arp............................................................................................................................ 247
show audit......................................................................................................................... 248
show axdebug capture...................................................................................................... 249
show axdebug config......................................................................................................... 249
show axdebug config-file...................................................................................................249
show axdebug file.............................................................................................................. 250
show axdebug filter........................................................................................................... 251
show axdebug status......................................................................................................... 251
show backup..................................................................................................................... 251
show bfd..................................................................................................................... 252
show bgp.................................................................................................................... 257
show bootimage......................................................................................................... 257
show bpdu-fwd-group................................................................................................. 258
show bridge-vlan-group..................................................................................................... 258
show bw-list............................................................................................................... 258
show class-list.........................................................................................................................260
show clns........................................................................................................................... 261
show clock......................................................................................................................... 262
show config................................................................................................................ 263
show config-block.............................................................................................................. 263
page 7 | Document No.: 410-P2-CLI-001 - 6/17/2016
show context.............................................................................................................. 263
show core.......................................................................................................................... 264
show cpu........................................................................................................................... 265
show debug................................................................................................................ 267
show disk........................................................................................................................... 267
AX Debug Commands......................................................................................365
apply-config....................................................................................................................... 366
capture.............................................................................................................................. 367
count.......................................................................................................................... 369
delete................................................................................................................................. 370
filter.................................................................................................................................... 370
incoming | outgoing.................................................................................................... 371
length......................................................................................................................... 372
maxfile............................................................................................................................... 372
outgoing..................................................................................................................... 373
save-config........................................................................................................................ 373
timeout....................................................................................................................... 373
This chapter describes how to use the Command Line Interface (CLI) to configure ACOS devices. The commands and their
options are described in the other chapters.
NOTE: By default, Telnet access is disabled on all interfaces, including the management inter-
face. SSH, HTTP, HTTPS, and SNMP access are enabled by default on the management
interface only, and disabled by default on all data interfaces.
ACOS>
This is the first level entered when a CLI session begins. At this level, users can view basic system information but cannot
con- figure system or port parameters.
• A10 Thunder Series models contain “ACOS” plus the model number in the prompt. For example, when an EXEC ses-
sion is started, the A10 Thunder Series 6430 will display the following prompt:
ACOS6430>
• AX Series models contain “AX” plus the model number in the prompt. For example, when an EXEC session is
started, the AX Series 5630 will display the following prompt:
AX5630>
The right arrow (>) in the prompt indicates that the system is at the “User EXEC” level. The User EXEC level does not
contain any commands that might control (for example, reload or configure) the operation of the ACOS device. To list the
commands available at the User EXEC level, type a question mark (?) then press Enter at the prompt; for example,
ACOS>?.
NOTE: For simplicity, this document uses “ACOS” in CLI prompts, unless referring to a specific
model. Likewise, A10 Thunder Series or AX Series devices are referred to as “ACOS
devices”, since they both run ACOS software.
ACOS#
This level is also called the “enable” level because the enable command is used to gain access. Privileged EXEC level
can be password secured. The “privileged” user can perform tasks such as manage files in the flash module, save the
system con- figuration to flash, and clear caches at this level.
Critical commands (configuration and management) require that the user be at the “Privileged EXEC” level. To change to the
Privileged EXEC level, type enable then press Enter at the ACOS> prompt. If an “enable” password is configured, the
ACOS device will then prompt for that password. When the correct password is entered, the ACOS device prompt will change
from ACOS> to ACOS# to indicate that the user is now at the “Privileged EXEC” level. To switch back to the “User EXEC”
level, type disable at the ACOS# prompt. Typing a question mark (?) at the Privileged EXEC level will now reveal
many more com- mand options than those available at the User EXEC level.
ACOS(config)#
The Privileged EXEC level’s configuration mode is used to configure the system IP address and to configure switching and
routing features. To access the configuration mode, you must first be logged into the Privileged EXEC level.
From the opening CLI prompt, enter the following command to change to the Privileged level of the EXEC mode:
ACOS> enable
To access the configuration level of the CLI, enter the config command:
ACOS# config
Commands at the Privileged EXEC level are available from configuration mode by prepending the command with do. For
example, the clock command is available in Privileged EXEC mode, while timezone is available in configuration mode. To
avoid having to switch configuration levels, like the following example:
You can use the do command to execute the clock command from configuration mode:
• VRRP-A status of the ACOS device: Active, Standby, or ForcedStandby (the VRRP-A status only appears on
devices that are configured in Active-Standby mode)
• Hostname of the ACOS device
• aVCS status (vMaster or vBlade), virtual chassis ID, and device ID
Below is an example of a CLI prompt that shows all these information items:
ACOS-Active-vMaster[1/1]>
By default, all these information items are included in the CLI prompt. You can customize the CLI prompt by explicitly
enabling the individual information items to be displayed.
• chassis-device-id – Display aVCS device id in the prompt. For example, this can be 7/1, where the number 7
indicates the chassis ID and 1 indicates the device ID within the aVCS set.
NOTE: The aVCS Chassis ID and the aVCS Device ID are configurable as part of the prompt if
aVCS is running. The prompt that you specify will be synchronized and reflected on all
the other devices in the aVCS set.
If the CLI session is on an L3V partition, the partition name is included in the CLI prompt. For example, for L3V
partition “corpa”, the prompt for the global configuration level of the CLI looks like the following:
ACOS[corpa](config)#
In this example, the partition name is shown in blue type. This example assumes that the hostname of the device is
“ACOS”. If the CLI session is in the shared partition, the prompt is as shown without a partition name. For example:
ACOS(config)#
1. Online Help
Enter “?” at a command prompt to list the commands available at that CLI level.
Enter "?" at any point within a command to list the available options.
2. Word Completion
The CLI supports command completion, so you do not need to enter the entire
name of a command or option. As long as you enter enough characters of the
command or option name to avoid ambiguity with other commands or options,
the CLI can complete the command or option.
After entering enough characters to avoid ambiguity, press "tab"
to auto-complete the command or option.
ACOS>
A space (or lack of a space) before the question mark (?) is significant when using context-sensitive help. To determine which
commands begin with a specific character sequence, type in those characters followed directly by the question mark; e.g.
ACOS#te?. Do not include a space. This help form is called “word help”, because it completes the word for you.
To list arguments or keywords, enter a question mark (?) in place of the argument or the keyword. Include a space before the
(?); e.g. ACOS# terminal ?. This form of help is called “command syntax help”, because it shows you which keywords
or arguments are available based on the command, keywords, and arguments that you already entered.
Users can abbreviate commands and keywords to the minimum number of characters that constitute a unique
abbreviation. For example, you can abbreviate the config terminal command to conf t. If the abbreviated form
of the command is unique, then ACOS accepts the abbreviated form and executes the command.
Enter the letters co at the system prompt followed by a question mark (?). Do not leave a space between the last letter
and the question mark. The system provides the commands that begin with co.
ACOS# co?
configure Entering config mode
ACOS# co
Enter the configure command followed by a space and a question mark to list the keywords for the command and a brief
explanation:
ACOS# configure ?
terminal Config from the terminal
<cr>
ACOS# configure
The <cr> symbol (“cr” stands for carriage return) appears in the list to indicate that one of your options is to press
the Return or Enter key to execute the command, without adding any additional keywords.
In this example, the output indicates that your only option for the configure command is configure terminal
(config- ure manually from the terminal connection).
From Privileged-EXEC mode, use the terminal history command to set the buffer size for the current session. For
exam- ple, to set the buffer to 500, then verify the change with the show terminal command:
Use the no terminal history size command to reset the buffer size for this session to the default value. For
example:
If you use the terminal history command from Global configuration mode, you are making a more permanent
change on the system; the buffer size will be the same for all configuration sessions, not just the current session.
Recalling Commands
To recall commands from the history buffer, use one of the commands or key combinations described in Table 3:
were chosen to simplify remembering their functions. In Table 4, characters bolded in the Function Summary column
indi- cate the relation between the letter used and the function.
The CLI will recognize a command once you enter enough text to make the command unique. For example, if you enter
conf while in the privileged EXEC mode, the CLI will associate your entry with the config command, because only the
config command begins with conf.
In the next example, the CLI recognizes the unique string conf for privileged EXEC mode of config after pressing the tab
key:
ACOS# conf<tab>
ACOS# configure
When using the command completion feature, the CLI displays the full command name. Commands are not executed until
the Enter key is pressed. This way you can modify the command if the derived command is not what you expected from
the abbreviation. Entering a string of characters that indicate more than one possible command (for example, te) results in
the following response from the CLI:
ACOS# te
% Ambiguous command
ACOS#
If the CLI can not complete the command, enter a question mark (?) to obtain a list of commands that begin with the char-
acter set entered. Do not leave a space between the last letter you enter and the question mark (?).
In the example above, te is ambiguous. It is the beginning of both the telnet and terminal commands, as shown in the fol-
lowing example:
ACOS# te?
telnet Open a telnet connection
terminal Set Terminal Parameters, only for current
terminal ACOS# te
The letters entered before the question mark (te) are reprinted to the screen to allow continuation of command entry
from where you left off.
When the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the first ten
charac- ters of the line, but you can scroll back and check the syntax at the beginning of the command. To scroll back,
press ctrl+B or the left arrow key repeatedly until you scroll back to the command entry, or press ctrl+A to return
directly to the begin- ning of the line.
The ACOS software assumes you have a terminal screen that is 80 columns wide. If you have a different screen-width, use
the
terminal width EXEC command to set the width of the terminal.
Use line wrapping in conjunction with the command history feature to recall and modify previous complex command
entries. See the Recalling Commands section in this chapter for information about recalling previous command
entries.
To proceed, press the Enter key to scroll down one line, or press the spacebar to display the next full screen of output.
• slb server
• slb service-group
• slb virtual-server
• member (at service-group configuration level)
• service-group (at virtual-port configuration level)
The following example displays the names of real servers that are already configured on the ACOS device. All options dis-
played in the output except “NAME” are real servers.
You can further refine the list that appears by entering part of the name. For example:
In the same manner that commands can be auto-completed by partially entering the command name and pressing
<TAB>, the ACOS device supports the ability to auto-complete the names of configured items. For example:
The output filter displays only the ARP entries that contain IP addresses that match “192.168.1.3” and any value following “3”.
The asterisk ( * ) matches on any pattern following the “3”. (See “Working with Regular Expressions” on page 15.)
A regular expression can be a single-character pattern or a multiple-character pattern. This means that a regular
expression can be a single character that matches the same single character in the command output or multiple
characters that match the same multiple characters in the command output. The pattern in the command output is
referred to as a string. This section describes creating single-character patterns.
Single-Character Patterns
The simplest regular expression is a single character that matches the same single character in the command output. You
can use any letter (A–Z, a–z) or digit (0–9) as a single-character pattern. You can also use other keyboard characters (such
as ! or ~) as single-character patterns, but certain keyboard characters have special meaning when used in regular
expressions. Table 8 lists the keyboard characters that have special meaning.
For information about the supported password length, see the CLI help or the command entry in this document.
• \ – To use a back slash in a string, enter another back slash in front of it: \\
For example, to use the string a"b?c\d, enter the following: "a\"b\077c\\d"
The \ character will be interpreted as the start of an escape sequence only if it is enclosed in double quotation marks.
(The ending double quotation mark can be omitted.) If the following characters do not qualify as an escape sequence, they
are take verbatim; for example, \ is taken as \, "\x41" is taken as A (hexadecimal escape), "\101" is taken as A
(octal escape), and "\10" is taken as \10.
NOTE: To use a double-quotation mark as the entire string, "\"". If you enter \", the result is \.
(Using a single character as a password is not recommended.)
It is recommended not to use i18n characters. The character encoding used on the
ter- minal during password change might differ from the character encoding on the
termi- nal used during login.
• Device ID Syntax
• aVCS Device Option for Configuration Commands
• aVCS Device Option for Show Commands
• CLI Message for Commands That Affect Only the Local Device
Device ID Syntax
In an aVCS virtual chassis, configuration items that are device-specific include the device ID. For these items, use the
follow- ing syntax:
To determine whether a command supports the DeviceID/ syntax, use the CLI help.
The following command accesses the configuration level for Ethernet data port 5 on device 4:
ACOS(config)# device-context 3
ACOS(config)# hostname ACOS3
ACOS3(config)#
For example, the following command shows how to connect to device 2 in a virtual chassis, then view the MAC address
table on that device:
CLI Message for Commands That Affect Only the Local Device
You can display a message when entering a configuration command that applies to only the local device. When this
option is enabled, a message is displayed if you enter a configuration command that affects only the local device, and
the com- mand does not explicitly indicate the device.
Local Device
The “local device” is the device your CLI session is on.
• If you log directly onto one of the devices in the virtual chassis, that device is the local device. For example, if you
log on through the management IP address of a vBlade, that vBlade is the local device.
• If you change the device context or router content to another ACOS device, that device becomes the local device.
• If you log onto the virtual chassis’ floating IP address, the vMaster is the local device.
Message Example
The following command configures a static MAC address:
This type of configuration change is device-specific. However, the command does not specify the device ID to which to
apply the configuration change. Therefore, the change is applied to the local device. In this example, the local device
is device 1 in the aVCS virtual chassis.
The message is not necessary if you explicitly specify the device, and therefore is not displayed:
ACOS(config)# device-context 2
ACOS(config)# mac-age-time 444 device 2
For commands that access the configuration level for a specific configuration item, the message is displayed only for the
command that accesses the configuration level. For example:
The message is not displayed after the ip address command is entered, because the message is already displayed after
the interface ethernet 2 command is entered.
The same is true for commands at the configuration level for a routing protocol. The message is displayed only for the
com- mand that accesses the configuration level for the protocol.
• In most cases, the message also is displayed following clear commands for device-specific items. An exception is
clear commands for routing information. The message is not displayed following these commands.
To enable this:
For example, see the following configuration where a real server is created:
The counters you will see for the sampling-enable ? command will vary depending on the object. You can select
specific counters you want to enable, or use the all keyword to enable all available counters.
The following example enables baselining for three counters under the SLB server configuration, then verifies the configura-
tion with the show running-config command:
This command shows the minimum, maximum, and average value for each enabled counter over the last 30 seconds.
This command shows the average value of each counter over the following intervals:
• last second
• last 5 seconds
• last 10 seconds
• last 30 seconds
Tagging Objects
Certain objects created in the CLI can be tagged by using the user-tag command. These tags can then be searched by
using the aXAPI. See the “Filters” page of the aXAPI Reference for more information.
NOTE: Do not enter the value “Security” for the custom tag from the CLI; this is a reserved
key- word. Doing so can interfere with the proper display of SSLi configurations
performed in the GUI.
Tagging objects is useful to help differentiate objects that can be used for multiple feature areas, like real servers, virtual
serv- ers, service group, or templates. Consider the following example, where multiple real servers are created for load
balancing. By tagging each server, the show running-config output can help you identify which servers are used for
FTP load bal- ancing (labeled with “FTP”) and which ones are used for HTTP load balancing (labeled with “HTTP):
user-tag HTTP-2
At a later point in time, suppose server “ftp1” has need to be re-purposed; rather than renaming the server and all of the
cor- responding configuration that might also have “FTP” in their object names, you can update the user tag to indicate
the actual purpose of the server while leaving the existing configuration intact.
The EXEC commands (sometimes referred to as the User EXEC commands) are available at the CLI level that is
presented when you log into the CLI.
The EXEC level command prompt ends with >, as in the following example:
ACOS>
• active-partition
• enable
• exit
• gen-server-persist-cookie
• health-test
• help
• no
• ping
• show
• ssh
• telnet
• traceroute
active-partition
Description CLI commands related to ADPs are located in Configuring Application Delivery
Partitions.
enable
Description Enter privileged EXEC mode, or any other security level set by a system administrator.
Syntax enable
Mode EXEC
Usage Entering privileged EXEC mode enables the use of privileged commands. Because many
of the privileged commands set operating parameters, privileged access should be
password- protected to prevent unauthorized use. If the system administrator has set a
password with the enable password global configuration command, you are
prompted to enter it before being allowed access to privileged EXEC mode. The password
is case sensitive.
Example In the following example, the user enters privileged EXEC mode using the enable com-
mand. The system prompts the user for a password before allowing access to the
privileged EXEC mode. The password is not printed to the screen. The user then exits back
to user EXEC mode using the disable command. Note that the prompt for user EXEC
mode is >, and the prompt for privileged EXEC mode is #.
ACOS>enable
Password: <letmein>
ACOS#disable
ACOS>
exit
Description When used from User EXEC mode, this command closes an active terminal session by
log- ging off the system. In any other mode, it will move the user to the previous
configuration level.
Syntax exit
Mode All
Example In the following example, the exit command is used three times:
1. To move from Global configuration mode to the previous config level (privileged
EXEC mode);
2. To move from privileged EXEC mode to the previous config level (User EXEC mode);
3. From User EXEC mode, the exit command is used to log off (exit the active session):
ACOS(config)#exit
ACOS#exit
ACOS>exit
Are you sure to quit (N/Y)?: Y
gen-server-persist-cookie
Description Generate a cookie for pass-through cookie-persistent SLB sessions.
Parameter Description
cookie-name Name of the cookie header. The default is “sto-id” if no name is specified.
port The port option creates a cookie based on the following format:
cookiename-vportnum-groupname=encoded-ip_encoded-rport
server The server option creates a cookie based on the following format:
cookiename=encoded-ip
service-group The service-group option creates a cookie based on the following format:
cookiename-vportnum-groupname=encoded-ip_encoded-rport
Default ACOS does not have a default pass-through cookie. When you configure one, the
default name is “sto-id”. There is no default match-type setting.
Usage Additional configuration is required. The pass-thru option must be enabled in the
cookie- persistence template bound to the virtual port.
health-test
Description Test the status of a device using a configured health monitor.
Parameter Description
ipaddr Specifies the IPv4 address of the device to test.
ipv6addr Specifies the IPv6 address of the device to test.
count num Specifies the number of health checks to send to the device. You can
specify a number 1 - 65535.
The default count is 1.
monitor-name Specifies the name of the health monitor you want to use, 1-29 char-
acters. The health monitor must already be configured.
See “Config Commands: Health Monitors” on page 547 for more infor-
mation about configuring a health monitor.
The default monitor is ICMP ping, which is the default Layer 3 health
check.
port-num Specifies the protocol port to test. You can specify any port 1 - 65535.
The default is the override port number set in the health monitor con-
figuration. If none is set there, then this option is not set by default.
Usage If an override IP address and protocol port are set in the health monitor configuration, the
ACOS device will use the override address and port, even if you specify an address and
port with the health-test command.
Example The following command tests port 80 on server 192.168.1.66, using configured health
moni- tor hm80:
help
Description Display a description of the interactive help system of the CLI.
Syntax help
Mode All
no
Description See “no” on page 49. This command is not used at this level.
ping
Description Send an ICMP echo packet to test network connectivity.
Parameter Description
ipv6 {hostname | ipaddr} Send a ping to the specified IPv6 hostname or address.
{hostname | ipaddr} Send a ping to the specified IPv4 hostname or address.
data HEX-word Hexadecimal data pattern to send in the ping. The pattern can be 1-8 hexadecimal
characters long.
This is not set by default.
ds-lite { Send a DS-Lite ping.
[source-ipv4 ipaddr]
[source-ipv6 ipaddr]
ipaddr}
flood Send a continuous stream of ping packets, by sending a new packet as soon as a
reply to the previous packet is received.
This is disabled by default.
interface { Use the specified interface as the source of the ping. Use ethernet for ethernet
ethernet port- interfaces, or ve for virtual ethernet interfaces.
num ve ve-num} By default, this is not set. The ACOS device looks up the route to the ping target in
the main route table and uses the interface associated with the route. (The manage-
ment interface is not used unless you specify the management IP address as the
source interface.)
pmtu Enable PMTU discovery.
repeat {count | unlimited} Number of times to send the ping. You can specify a number 1 - 10000000 (ten mil-
lion), or specify unlimited to ping continuously.
The default count is 5.
size num Specify the size of the datagram in bytes. You can specify a number from 1 - 10000.
The default size is 84 bytes.
Parameter Description
source { Forces the ACOS device to give the specified IP address (ipaddr), or the IP
ipaddr | address configured on the specified interface (either ethernet port-num or
ethernet port-num | ve ve-num), as the source address of the ping.
ve ve-num}
timeout secs Number of seconds the ACOS device waits for a reply to a sent ping packet, 1-2100
seconds.
The default timeout value is 10 seconds.
ttl num Maximum number of hops the ping is allowed to traverse, 1-255.
The default is 1.
Usage The ping command sends an echo request packet to a remote address, and then awaits
a reply. Unless you use the flood option, the interval between sending of each ping
packet is 1 second.
ACOS>ping 192.168.3.116
PING 192.168.3.116 (192.168.3.116) 56(84) bytes of data
64 bytes from 192.168.3.116: icmp_seq=1 ttl=128 time=0.206
ms 64 bytes from 192.168.3.116: icmp_seq=2 ttl=128
time=0.260 ms 64 bytes from 192.168.3.116: icmp_seq=3
ttl=128 time=0.263 ms 64 bytes from 192.168.3.116:
icmp_seq=4 ttl=128 time=0.264 ms 64 bytes from
192.168.3.116: icmp_seq=5 ttl=128 time=0.216 ms
--- 192.168.3.116 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.206/0.241/0.264/0.032 ms
Example The following command sends a ping to IP address 10.10.1.20, from ACOS Ethernet port 1.
The ping has data pattern “ffff”, is 1024 bytes long, and is sent 100 times.
show
Description Show system or configuration information.
Default N/A
Mode All
Usage For information about the show commands, see “Show Commands” on page 237 and “SLB
Show Commands” in the Command Line Interface Reference for ADC.
ss
h
Description Establish a Secure Shell (SSH) connection from the ACOS device to a different device.
Parameter Description
use-mgmt-port Uses the management interface as the source interface for the
connection to the remote device. The management route table is
used to reach the device. By default, the ACOS device attempts to
use the data route table to reach the remote device through a data
interface.
hostname Host name of the remote system.
ipaddr IP address of the remote system.
login-name The user name used to log in to the remote system.
protocol-port TCP port number on which the remote system listens for SSH client
traffic. Specify a number 1 - 65535.
The default port is 22.
telnet
Description Open a Telnet tunnel connection from the ACOS device to another device.
Parameter Description
use-mgmt-port Uses the management interface as the source interface for the con-
nection to the remote device. The management route table is used
to reach the device. By default, the ACOS device attempts to use
the data route table to reach the remote device through a data inter-
face.
hostname Host name of the remote system.
ipaddr IP address of the remote system.
protocol-port TCP port number on which the remote system listens for Telnet traf-
fic. Specify a number 1 - 65535.
The default port is 23.
Example The following command opens a Telnet session from one ACOS device to another
ACOS device at IP address 10.10.4.55:
ACOS>telnet 10.10.4.55
Trying 10.10.4.55...
Connected to 10.10.4.55.
Escape character is '^]'.
Welcome to Thunder
ACOS login:
traceroute
Description Display the router hops through which a packet sent from the ACOS device can reach
a remote device.
Parameter Description
ipv6 Indicates that the remote device is an IPv6 system.
use-mgmt-port Uses the management interface as the source interface. The man-
agement route table is used to reach the device. By default, the
ACOS device attempts to use the data route table to reach the
remote device through a data interface.
hostname Host name of the device at the remote end of the route to be
traced.
ipaddr IP address of the device at the remote end of the route to be
traced.
Default N/A
Usage If a hop does not respond within 5 seconds, asterisks ( * ) are shown in the row for that hop.
ACOS>traceroute 192.168.10.99
traceroute to 192.168.10.99 (192.168.10.99), 30 hops max, 40 byte
packets
1 10.10.20.1 (10.10.20.1) 1.215 ms 1.151 ms 1.243 ms
2 10.10.13.1 (10.10.13.1) 0.499 ms 0.392 ms 0.493 ms
...
The Privileged EXEC mode commands are available at the CLI level that is presented when you enter the enable
command and a valid enable password from the EXEC level of the CLI.
The Privileged EXEC mode level command prompt ends with #, as in the following example:
ACOS#
• active-partition
• axdebug
• backup log
• backup system
• clear
• clock
• configure
• debug
• diff
• disable
• exit
• export
• gen-server-persist-cookie
• health-test
• help
• import
• locale
• no
• ping
• reboot
• reload
• repeat
• show
• shutdown
• ssh
• telnet
• terminal
• traceroute
• vcs
• write force
• write memory
• write terminal
active-partition
Description Change the partition on an ACOS device configured for Application Delivery Partitioning
(ADP). (See “active-partition” on page 25.)
axdebug
Description Enters the AX debug subsystem. (See “AX Debug Commands” on page 365.)
backup log
Description Configure log backup options and save a backup of the system log.
Parameter Description
expedite Allocates additional CPU to the backup process. This option allows up to 50% CPU utilization
to be devoted to the log backup process.
period Specifies the period of time whose data you want to back up:
• all - Backs up the log messages contained in the log buffer.
• day - Backs up the log messages generated during the most recent 24 hours.
• month - Backs up the log messages generated during the most recent 30 days.
• week - Backs up the log messages generated during the most recent 7 days.
• days - Backs up the log messages generated using days as the interval (for example,
specify 5 to back up every 5 days).
The default period of time is one month.
Usage The expedite option controls the percentage of CPU utilization allowed exclusively to
the log backup process. The actual CPU utilization during log backup may be higher, if
other management processes also are running at the same time.
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
Example The following commands change the backup period to all, allow up to 50% CPU
utilization for the backup process, and back up the log:
Example The following command backs up statistical data from the GUI:
NOTE: The log period and expedite settings also apply to backups of the GUI statistical
data.
backup system
Description Back up the system. The startup-config file, aFleX policy files, and SSL certificates and keys
will be backed up to a .tar.gz file.
NOTE: Backing up system from one hardware platform and restoring it to another is not
supported.
Parameter Description
profile-name Profile name for the remote URL, 1-31 characters.
Profiles that can be used in place of the URL are configured with
the backup store command.
use-mgmt-port Uses the management interface as the source interface for the
con- nection to the remote device. The management route table
is used to reach the device. Without this option, the ACOS
device attempts to use the data route table to reach the remote
device through a data interface.
Parameter Description
url The url specifies the file transfer protocol, username (if required),
and directory path to the location where you want to save the
backup file.
You can enter the entire URL on the command line or press Enter to
display a prompt for each part of the URL. If you enter the entire
URL and a password is required, you will still be prompted for the
pass- word. The password can be up to 255 characters long.
To enter the entire URL, use one of the following:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Default N/A
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
Example This example backs up the system to the /home/backups folder on host 192.168.2.2.
The trailing slash (/) at the end of the URL tells ACOS that this is a directory path, and not a
file name. In this case, since no file name is specified, the file name will be automatically
generated by ACOS. This is the recommended method of performing system backups
because the file names are guaranteed to be unique. Your backups may fail if you
accidentally backup to a file that already exists with the same name.
Example This example backs up the system to a file called “back_file.tar.gz” on host 1.1.1.1:
clear
Description Clear statistics or reset functions. Sub-command parameters are required for specific
sub- commands.
Default N/A
Usage To list the options available for a clear command, enter ? after the command name.
For example, to display the clear gslb options, enter the following command:
clear gslb ?
On some ACOS models, entering either the clear slb switch or clear slb l4
command clears all anomaly counters for both show slb switch and show slb l4.
This applies to the following AX models: AX 3200-12, AX 3400, and AX 3530.
After entering the clear session command, the ACOS device may remain in session-
clear mode for up to 10 seconds. During this time, any new connections are sent to the delete
queue for clearing.
clock
Description Set the system time and date.
Parameter Description
time Set the time, using 24-hour format hh:mm:ss.
day Set the day of the month (1-31).
month Set the month (January, February, March, and so on).
year Set the year (2013, 2014, and so on).
Usage Use this command to manually set the system time and date.
If the system clock is adjusted while OSPF or IS-IS is enabled, the routing protocols may stop
working properly. To work around this issue, disable OSPF and IS-IS before adjusting the
system clock.
Example Set the system clock to 5:51 p.m. and the date to February 22nd, 2015.
configure
Description Enter the configuration mode from the Privileged EXEC mode.
ACOS#configure
ACOS(config)#
debug
NOTE: It is recommended to use the AXdebug subsystem instead of these debug com-
mands. See “AX Debug Commands” on page 365.
diff
Description Display a side-by-side comparison of the commands in a pair of locally stored configurations.
Usage The following command compares the configuration profile that is currently linked
to “startup-config” with the running-config.
diff startup-config running-config
Similarly, the following command compares the configuration profile that is currently
linked to “startup-config” with the specified configuration profile:
To compare any two configuration profiles, enter their profile names instead of startup-
config or running-config.
In the CLI output, the commands in the first profile name you specify are listed on the left
side of the terminal screen. The commands in the other profile that differ from the
commands in the first profile are listed on the right side of the screen, across from the
commands they differ from. The following flags indicate how the two profiles differ:
disable
Description Exit the Privileged EXEC mode and enter the EXEC mode.
Syntax disable
ACOS#disable
ACOS>
NOTE: The prompt changes from # to >, indicating change to EXEC mode.
exit
Description Exit the Privileged EXEC mode and enter the EXEC Mode.
Syntax exit
Example In the following example, the exit command is used to exit the Privileged EXEC mode
level and return to the User EXEC level of the CLI:
ACOS#exit
ACOS>
NOTE: The prompt changes from # to >, indicating change to EXEC mode.
export
Description Put a file to a remote site using the specified transport method.
Syntax export
{{
aflex file |
auth-portal file |
auth-portal-image file |
auth-saml-idp file |
axdebug file |
bw-list file |
ca_cert file |
cert file |
cert-key file |
class-list file |
crl file |
debug_monitor file |
dnssec-dnskey file |
dnssec-ds file |
fixed-nat file |
geo-location file |
health-external file |
key file |
local-uri-file file |
lw-4o6 file |
policy file |
running-config |
startup-config |
store {create | delete} profile-name url |
syslog file |
thales-secworld file |
wsdl file |
xml-schema file
}
{[use-mgmt-port] {url | export-store}
}} |
{startup-config-profile [use-mgmt-port] {url | export-store}}
Parameter Description
aflex Exports an aFleX file.
auth-portal Exports an authentication portal file for Application Access
Management (AAM).
auth-portal-image Exports the image file for the default portal.
auth-saml-idp Exports the SAML metadata of the identity provider.
axdebug Exports an AX debug capture file.
bw-list Exports a black/white list.
ca-cert Exports a CA cert file.
cert Exports an SSL cert file.
cert-key Exports a certificate and key together as a single file.
class-list Exports an IP class list.
crl Exports a certificate revocation list (CRL).
Parameter Description
debug_monitor Exports a debug monitor file.
dnssec-dnskey Exports a DNSEC key-signing key (KSK) file.
dnssec-ds Exports a DNSSEC DS file.
fixed-nat Exports the fixed NAT port mapping file.
geo-location Export the geo-location CSV file.
health-external Export the external program from the system.
key Exports an SSL key file.
license Exports a license file, if applicable to your model.
local-uri-file Exports the specified image file for the “sorry” page served to
RAM Caching clients if all servers are down.
lw-4o6 Exports the LW-4over6 binding table File.
policy Exports a WAF policy file.
running-config Exports the running configuration to a file.
startup-config Exports the startup configuration.
store Create or delete an export store profile.
syslog Exports the messages from the local log buffer.
wsdl Exports a Web Services Definition Language (WSDL) file.
xml-schema Exports an XML schema file.
profile-name Name of a startup-config profile to export.
use-mgmt-port Uses the management interface as the source interface for
the connection to the remote device. The management route
table is used to reach the device. By default, the ACOS
device attempts to use the data route table to reach the
remote device through a data interface.
url Protocol, user name (if required), and directory path you want
to use to send the file.
You can enter the entire URL on the command line or press
Enter to display a prompt for each part of the URL. If you enter
the entire URL and a password is required, you will still be
prompted for the password. The password can be up to 255
characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Usage If you omit the final forward slash in the url string, ACOS attempts to use the string after
the final slash as the filename. If you omit the extension, ACOS attempts to use the string
after
the final slash as the base name of the file. However, this can lead to an error in some cases.
If you are exporting AXdebug output, make sure to use the final slash in the url string.
Example The following command exports an aFleX policy from the ACOS device to an FTP server,
to a directory named “backups”.
gen-server-persist-cookie
Description See “gen-server-persist-cookie” on page 27.
health-test
Description See “health-test” on page 28.
help
Description Display a description of the interactive help system of the ACOS device.
Syntax help
import
Description Get a file from a remote site.
Syntax import
{
{
aflex file |
auth-portal file |
auth-portal-image file |
auth_saml_idp file |
bw-list file |
{
ca-cert file
[{certificate-type {pem | der | pfx [pfx-password pswd] | p7b}]
[{csr-generate digest {sha1 | sha256 | sha384 | sha512}}]
} |
{
cert file
[{certificate-type {pem | der | pfx [pfx-password pswd] | p7b}]
[{csr-generate digest {sha1 | sha256 | sha384 | sha512}}]
} |
cert-key bulk |
class-list file |
class-list-convert file class-list-type type |
crl file
dnssec-dnskey file |
dnssec-ds file |
geo-location file |
glm-license file |
health-external file
| helath-postfile
file | key file
license file |
local-uri-file file |
lw-4o6 file |
policy file |
store file |
thales-secworld file |
web-category-license file |
wsdl file |
xml-schema file
}
{[overwrite] {[use-mgmt-port] {url | import-store}}
} |
{
{
auth-saml-idp metadata-name
health-external program-name [description text] |
health-postfile file
}
{[overwrite] {[use-mgmt-port] url}
} |
{store {create | delete} profile-name url}
}
Parameter Description
aflex Import an aFleX file.
auth-portal Import an authentication portal file for Application Access Management
(AAM).
auth-portal-image Import an image file for the default authentication portal.
auth-saml-idp Import the SAML metadata of the identity provider.
bw-list Import a black/white list.
ca-cert Imports a CA cert file.
• Use the bulk option to import multiple files simultaneously as a .tgz
archive.
• Use certificate-type to specify a certificate type.
• Use csr-generate to generate a CSR file.
cert Imports an SSL cert file.
• Use the bulk option to import multiple files simultaneously as a .tgz
archive.
• Use certificate-type to specify a certificate type.
• Use csr-generate to generate a CSR file.
cert-key bulk Imports a certificate and key together as a single file.
class-list Import an IP class list.
class-list-convert ACOS imports a newline delimited text file and converts it to a class-list file of the
file class-list-type specified type:
{ac | string | ipv4 | ipv6 |
• ac - Aho-Corasick class list.
string-case-intensive}
See the “How to Convert Your SNI List to an A10 Class List” section in the SSLi
Configuration Guide for an example of converting to an A10 Aho-Corasick class
list.
• string
• ipv4
• ipv6
• string-case-insensitive
NOTE: Only the Aho-Corasick class list is compliant with the class list types cre-
ated through the class-list command.
Parameter Description
key Import the SSL key file.
• Use the bulk option to import multiple files simultaneously as a .tgz archive.
• Use csr-generate to generate a CSR file.
license Import a license file, if applicable to your model.
local-uri-file Import the local URI files for HTTP responses.
lw-4o6 Import the LW-4over6 binding table file.
policy Import a WAF policy file.
store Import a store name for a remote URL.
• Use create to create an import store profile
• Use delete to delete an import store profile
thales-secworld Import a Thales security world file.
web-category-license Import a web-category-license file, which is required if you wish to access the
BrightCloud server and use the web-categorization feature.
wsdl Import a WSDL file.
xml-schema Import an XML schema file.
use-mgmt-port Uses the management interface as the source interface for the
connection to the remote device. The management route table is used to
reach the device. Without this option, the ACOS device device attempts
to use the data route table to reach the remote device through a data
interface.
url Protocol, user name (if required), and directory path you want to use to send the
file.
You can enter the entire URL on the command line or press Enter to display a
prompt for each part of the URL. If you enter the entire URL and a password is
required, you will still be prompted for the password. The password can be up to
255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Example The following command imports an aFleX policy onto the ACOS device from a TFTP
server, from its directory named “backups”:
locale
Description Set the locale for the current terminal session.
Parameter Description
test Test the current terminal encodings for a specific locale.
en_US.UTF-8 English locale for the USA, encoding with UTF-8 (default)
zh_CN.UTF-8 Chinese locale for PRC, encoding with UTF-8
zh_CN.GB18030 Chinese locale for PRC, encoding with GB18030
zh_CN.GBK Chinese locale for PRC, encoding with GBK
zh_CN.GB2312 Chinese locale for PRC, encoding with GB2312
zh_TW.UTF-8 Chinese locale for Taiwan, encoding with UTF-8
zh_TW.BIG5 Chinese locale for Taiwan, encoding with BIG5
zh_TW.EUCTW Chinese locale for Taiwan, encoding with EUC-TW
ja_JP.UTF-8 Japanese locale for Japan, encoding with UTF-8
ja_JP.EUC-JP Japanese locale for Japan, encoding with EUC-JP
Default en_US.UTF-8
no
Description Negate a command or set it to its default setting.
Syntax no command
Mode All
Example The following command disables the terminal command history feature:
ping
Description Test network connectivity. For syntax information, see “ping” on page 29.
reboot
Description Reboot the ACOS device.
Syntax reboot [
all |
text |
in hh:mm [text] |
at hh:mm [month day | day month] [text] |
cancel
]
Parameter Description
all Reboot all devices when VCS is enabled, or only this device itself if VCS
is not enabled.
text Reason for the reboot, 1-127 characters long.
in hh:mm Schedule a reboot to take effect in the specified hours and minutes.
The reboot must take place within approximately 24 hours.
at hh:mm Schedule a reboot to take place at the specified time (using a 24-hour
clock). If you specify the month and day, the reboot is scheduled to
take place at the specified time and date. If you do not specify the
month and day, the reboot takes place at the specified time on the
current day (if the specified time is later than the current time), or on
the next day (if the specified time is earlier than the current time).
Specifying 00:00 schedules the reboot for midnight.
Usage The reboot command halts the system. If the system is set to restart on error, it
reboots itself. Use the reboot command after configuration information is entered into
a file and saved to the startup configuration.
You cannot reboot from a virtual terminal if the system is not set up for automatic booting.
This prevents the system from dropping to the ROM monitor and thereby taking the system
out of the remote user’s control.
If you modify your configuration file, the system will prompt you to save the configuration.
The at keyword can be used only if the system clock has been set on the ACOS device
(either through NTP, the hardware calendar, or manually). The time is relative to the
configured time zone on the ACOS device. To schedule reboots across several ACOS
devices to occur simultaneously, the time on each ACOS device must be synchronized with
NTP. To display information about a scheduled reboot, use the show reboot command.
ACOS(config)#reboot
System configuration has been modified. Save? [yes/no]:yes
Rebooting System Now !!!
Proceed with reboot? [yes/no]:yes
Example The following example reboots the ACOS device at 1:00 p.m. today:
Example The following example reboots the ACOS device on Apr 20 at 4:20 p.m.:
***
*** --- REBOOT ABORTED ---
***
reload
Description Restart ACOS system processes and reload the startup-config, without rebooting.
Parameter Description
all When VCS is enabled, this parameter causes all devices in the
virtual chassis to be reloaded.
When VCS is disabled, this parameter causes only the device on
which this command is run to be reloaded.
device-id When VCS is enabled, this parameter causes only the specified
device to be reloaded.
When VCS is disabled, this parameter will return an error message.
Usage The reload command restarts ACOS system processes and reloads the startup-config,
with- out reloading the system image. To also reload the system image, use the reboot
command instead. (See “reboot” on page 49.)
If the reload command is used without any optional parameters (see example below)
then only the device on which the command is run will be reloaded. This is the case for both
VCS- enabled and VCS-disabled devices.
ACOS(config)#reload
Reload ACOS. . . .Done.
ACOS(config)#
repeat
Description Periodically re-enter a show command.
Parameter Description
seconds Interval at which to re-enter the command. You can specify 1-
300 seconds.
command-options Options of the show command. See “Show Commands” on
page 237 and “SLB Show Commands” in the Command Line
Interface Reference for ADC.
Usage The repeat command is especially useful when monitoring or troubleshooting the system.
The elapsed time indicates how much time has passed since you entered the repeat
command. To stop the command, press Ctrl+C.
show
Description Display system or configuration information. See “Show Commands” on page 237 and “SLB
Show Commands” in the Command Line Interface Reference for ADC.
shutdown
Description Schedule a system shutdown at a specified time or after a specified interval, or cancel a
scheduled system shutdown.
Parameter Description
at Schedule a reboot to take place at the specified time (using a 24-hour clock). If you specify the month
and day, the reboot is scheduled to take place at the specified time and date. If you do not specify the
month and day, the reboot takes place at the specified time on the current day (if the specified time is
later than the current time), or on the next day (if the specified time is earlier than the current time).
Specifying 00:00 schedules the reboot for midnight.
in Shutdown after a specified time interval (hh:mm). For example, 00:10 causes the device to shut
down 10 minutes from now.
cancel Cancel pending shutdown
text Reason for shutdown
Example The following command schedules a system shutdown to occur at 11:59 p.m.:
ACOS#shutdown at 23:59
ACOS#shutdown cancel
***
*** --- SHUTDOWN ABORTED ---
***
ss
h
Description Establish a Secure Shell (SSH) connection from the ACOS device to another device. (See
“ssh” on page 31.)
telnet
Description Establish a Telnet connection from the ACOS device to another device. (See “telnet”
on page 31.)
terminal
Description Set terminal display parameters for the current session.
Syntax terminal
{
auto-size |
command-timestamp [unix]|
editing |
gslb-prompt options |
history [size number] |
length number |
monitor |
width lines
}
Parameter Description
auto-size Enables the terminal length and width to automatically change to match the terminal win-
dow size.
This is enabled by default.
command-timestamp Include timestamp information in the show command output.
The unix option displays the timestamp in Unix format (sec.us) since Unix Epoch. For
example:
See the example below for more information.
editing Enables command-line editing.
This is enabled by default.
gslb-prompt Enables the CLI prompt to display the role of the ACOS device within a GSLB group.
options
• disable - disables this feature so the CLI prompt does not display role information
• group-role - displays “Member” or “Master” in the CLI prompt. For example:
ACOS:Master(config)#
• symbol - displays “gslb” in the CLI prompt after the name of the ACOS device. For
exam- ple:
ACOS-gslb:Master(config)#
history [size] Enables and controls the command history function. The size option specifies the number of
command lines that will be held in the history buffer. You can specify 0-1000.
This is enabled by default, the default size is 256.
length num Sets the number of lines on a screen. You can specify 0-512. Specifying 0 disables pausing.
The default length is 24.
monitor Copies debug output to the current terminal.
This is disabled by default.
width num Sets the width of the display terminal. You can specify 0-512. The setting 0 means “infinite”.
The default width is 80.
Usage This command affects only the current CLI session. The command is not added to the run-
ning-config and does not persist across reloads or reboots. To make persistent changes,
use the command at the global configuration level. (See “terminal” on page 207.)
ACOS#terminal length 40
Example The following example shows the command-timestamp option. Note the “Command
start time” and “Command end time” lines added as the first and last lines of the output:
ACOS#terminal command-timestamp
ACOS#show config-block
Command start time : 1422647248.076561
!Block configuration: 24 bytes
!64-bit Advanced Core OS (ACOS) version 4.0.1, build 98 (Jan-29-
2015,15:55)
!
interface ethernet 1
!
!
end
!Configuration specified in merge mode
Command end time : 1422647248.077418
ACOS#
traceroute
Description Trace a route. See “traceroute” on page 32.
vcs
Description Enter operational commands for configuring ACOS Virtual Chassis System (aVCS).
For more information, refer to the CLI commands in Configuring ACOS Virtual Chassis
Systems.
write force
Description Forces the ACOS device to save the configuration regardless of whether the system is ready.
Parameter Description
primary Write the configuration to the configuration profile stored in the
default primary configuration area.
secondary Write the configuration to the configuration profile stored in the
default secondary configuration area.
name Write the configuration to a specified profile name.
Example Force the ACOS device to save the current configuration to a custom profile called
“custom- prof”:
ACOS#write memory
System is not ready. Cannot save the configuration.
ACOS#write force custom-prof
Building configuration...
Write configuration to profile "custom-prof"
Do you want to link "custom-prof" to startup-config profile? (y/n):n
[OK]
ACOS#
write memory
Description Write the running-config to a configuration profile.
Parameter Description
primary Replaces the configuration profile stored in the primary
image area with the running-config.
secondary Replaces the configuration profile stored in the secondary
image area with the running-config.
profile-name Replaces the commands in the specified configuration profile
with the running-config.
all-partitions Saves changes for all resources in all partitions.
shared Saves changes only for the resources in the shared partition.
part-name Saves changes only for the resources in the specified L3V partition.
Default If you enter write memory without additional options, the command replaces the
configu- ration profile that is currently linked to by “startup-config” with the commands in
the run- ning-config. If startup-config is set to its default (linked to the configuration
profile stored in the image area that was used for the last reboot), then write
memory replaces the configu- ration profile in the image area with the running-config.
Unless you use the force option, the command checks for system readiness and saves the
configuration only if the system is ready.
Example The following command saves the running-config to the configuration profile stored in
the primary image area of the hard disk:
Example The following command saves the running-config to a configuration profile named
"slbcon- fig2":
Example The following command attempts to save the running-config but the system is not ready:
ACOS#write memory
ACOS is not ready. Cannot save the configuration.
write terminal
Description Display the current running-config on your terminal.
Example Example output from this command (output is truncated for brevity):
ACOS#write terminal
!Current configuration: 2877 bytes
!Configuration last updated at 03:08:11 IST Tue Jul 7 2015
!Configuration last saved at 04:18:08 IST Tue Jul 7 2015
!version 3.2.0-TPS, build 177 (Jun-22-2015,04:56)
!
hostname ACOS
!
clock timezone Europe/Dublin
!
!
...
This chapter describes the commands for configuring global ACOS parameters.
To access this configuration level, use the configure command at the Privileged EXEC
level. To display global settings, use show commands. (See “Show Commands” on page
237.)
Common commands that are available at all configuration levels (for example, active-partition, backup, clear,
debug, diff, export, health-test, help, import, repeat, show, write) are described in detail elsewhere in this
guide.
• aam
• access-list (standard)
• access-list (extended)
• accounting
• admin
• admin-lockout
• admin-session clear
• aflex
• aflex-scripts start
• application-type
• arp
• arp-timeout
• audit
• authentication console type
• authentication enable
• authentication login privilege-mode
• authentication mode
• authentication multiple-auth-reject
• authentication type
• authorization
• backup-periodic
• backup store
• banner
• bfd echo
• bfd enable
• bfd interval
• bgp
• big-buff-pool
• block-abort
• block-merge-end
• block-merge-start
• block-replace-end
• block-replace-start
• boot-block-fix
• bootimage
• bpdu-fwd-group
• bridge-vlan-group
• cgnv6
• class-list (for Aho-Corasick)
• class-list (for IP limiting)
• class-list (for VIP-based DNS caching)
• class-list (for many pools, non-LSN)
• class-list (string)
• class-list (string-case-insensitive)
• configure sync
• copy
• debug
• delete
• disable reset statistics
• disable slb
• disable-failsafe
• disable-management
• dnssec
• do
• enable-core
• enable-management
• enable-password
• end
• environment temperature threshold
• environment update-interval
• erase
• event
• exit
• export-periodic
• fail-safe
• fw
• glid
• glm
• gslb
• hd-monitor enable
• health global
• health monitor
• health-test
• hostname
• hsm template
• icmp-rate-limit
• icmpv6-rate-limit
• import
• import-periodic
• interface
• ip
• ip-list
• ipv6
• key
• l3-vlan-fwd-disable
• lacp system-priority
• lacp-passthrough
• ldap-server
• link
• lldp enable
• lldp management-address
• lldp notification interval
• lldp system-description
• lldp system-name
• lldp tx fast-count
• lldp tx fast-interval
• lldp tx interval
• lldp tx hold
• lldp tx reinit-delay
• locale
• logging auditlog host
• logging buffered
• logging console
• logging disable-partition-name
• logging email buffer
• logging email filter
• logging email-address
• logging export
• logging facility
• logging host
• logging monitor
• logging single-priority
• logging syslog
• logging trap
• mac-address
• mac-age-time
• maximum-paths
• merge-mode-add
• mirror-port
• monitor
• multi-config
• multi-ctrl-cpu
• netflow common max-packet-queue-time
• netflow monitor
• no
• ntp
• object-group network
• object-group service
• overlay-mgmt-info
• overlay-tunnel
• packet-handling
• partition
• partition-group
• ping
• pki copy-cert
• pki copy-key
• pki create
• pki delete
• pki renew-self
• pki scep-cert
• poap
• radius-server
• raid
• rba enable
• rba disable
• rba group
• rba role
• rba user
• restore
• route-map
• router
• router log file
• router log log-buffer
• rule-set
• run-hw-diag
• running-config display
• scaleout
• session-filter
• sflow
• slb
• smtp
• snmp
• so-counters
• sshd
• syn-cookie
• system all-vlan-limit
• system anomaly log
• system attack log
• system cpu-load-sharing
• system ddos-attack
• system glid
• system ipsec
• system log-cpu-interval
• system module-ctrl-cpu
• system per-vlan-limit
• system promiscuous-mode
• system resource-usage
• system template
• system ve-mac-scheme
• system-jumbo-global enable-jumbo
• system-reset
• tacacs-server host
• tacacs-server monitor
• techreport
• terminal
• tftp blksize
• timezone
• tx-congestion-ctrl
• upgrade
• vcs
• ve-stats
• vlan
• vlan-global enable-def-vlan-l2-forwarding
• vlan-global l3-vlan-fwd-disable
• vrrp-a
• waf
• web-category
• web-service
• write
aam
access-list (standard)
Description Configure a standard Access Control List (ACL) to permit or deny source IP addresses.
Parameter Description
acl-num Standard ACL number (1-99).
seq-num Sequence number of this rule in the ACL. You can use this option to re-sequence the rules
in the ACL.
permit Allows traffic for ACLs applied to interfaces or used for management access.
For ACLS used for IP source NAT, this option is also used to specify the inside host
addresses to be translated into external addresses.
NOTE: If you are configuring an ACL for source NAT, use the permit action. For ACLs
used with source NAT, the deny action does not drop traffic, it simply does not use the
denied addresses for NAT translations.
deny Drops traffic for ACLs applied to interfaces or used for management access.
l3-vlan-fwd-disable Disables Layer 3 forwarding between VLANs for IP addresses that match the ACL rule.
remark string Adds a remark to the ACL. The remark appears at the top of the ACL when you display
it in the CLI.
NOTE: An ACL and its individual rules can have multiple remarks.
To use blank spaces in the remark, enclose the entire remark string in double quotes. The
ACL must already exist before you can configure a remark for it.
any Denies or permits traffic received from any source host.
host host-ipaddr Denies or permits traffic received from a specific, single host.
src-ipaddr Denies or permits traffic received from the specified host or subnet. The filter-mask
{filter-mask | speci- fies the portion of the address to filter:
/mask-length}
• Use 0 to match.
• Use 255 to ignore.
For example, the filter-mask 0.0.0.255 filters on a 24-bit subnet.
Alternatively, you can use /mask-length to specify the portion of the address to filter.
For example, you can specify “/24” instead “0.0.0.255” to filter on a 24-bit subnet.
log [transparent- Configures the ACOS device to generate log messages when traffic matches the ACL.
session-only]
The transparent-session-only option limits logging for an ACL rule to creation
and deletion of transparent sessions for traffic that matches the ACL rule.
Default No ACLs are configured by default. When you configure one, the log option is disabled
by default.
Usage An ACL can contain multiple rules. Each access-list command configures one rule.
Rules are added to the ACL in the order you configure them. The first rule you add appears
at the top of the ACL.
Rules are applied to the traffic in the order they appear in the ACL (from the top, which is the
first rule, downward). The first rule that matches traffic is used to permit or deny that traffic.
After the first rule match, no additional rules are compared against the traffic.
To move a rule within the sequence, delete the rule, then re-add it with a new sequence
number.
The syntax shown in this section configures a standard ACL, which filters based on source IP
address. To filter on additional values such as destination address, IP protocol, or TCP/UDP
ports, configure an extended ACL. (See “access-list (extended)” on page 70.)
A contiguous comparison mask is one that, when converted to its binary format, consists
entirely of ones. A non-contiguous mask, however, contains at least one zero. Table 3
shows some examples of IPv4 addresses with each of the ACL mask types, a contiguous
mask and a non-contiguous mask. The addresses and masks are shown in both their
decimal and binary formats.
The “F” column indicates the format, decimal (D) or binary (B).
Example The following commands configure a standard ACL and use it to deny traffic sent from
sub- net 10.10.10.x, and apply the ACL to inbound traffic received on Ethernet interface 4:
Example The commands in this example configure an ACL that uses a non-contiguous mask,
and applies the ACLto a data interface:
Based on this configuration, attempts to ping or open an SSH session with destination IP
address 172.17.3.130 from source 172.16.3.131 are denied. However, attempts from
172.16.4.131 are permitted.
access-list
(extended)
Description Configure an extended Access Control List (ACL) to permit or deny traffic based on
source and destination IP addresses, IP protocol, and TCP/UDP ports.
[log [transparent-session-only]]
or
*.
This message appears a maximum of 2 times within a given CLI session.
[log [transparent-session-only]]
or
[log [transparent-session-only]]
or
[log [transparent-session-only]]
Parameter Description
acl-num Extended ACL number (100-199).
seq-num Sequence number of this rule in the ACL. You can use this option to re-sequence the
rules in the ACL.
permit Allows traffic that matches the ACL.
deny Drop the traffic that matches the ACL.
l3-vlan-fwd-disable Disables Layer 3 forwarding between VLANs for IP addresses that match the ACL rule.
Parameter Description
remark string Adds a remark to the ACL. The remark appears at the top of the ACL when you
display it in the CLI.
NOTE: An ACL and its individual rules can have multiple remarks.
To use blank spaces in the remark, enclose the entire remark string in double quotes.
The ACL must already exist before you can configure a remark for it.
ip Filters on IP packets only.
icmp Filters on ICMP packets only.
tcp | udp Filters on TCP or UDP packets, as specified. These options also allow you to filter
based on protocol port numbers.
object-group Service object group name.
For more information, see “object-group service” on page 167.
type icmp-type This option is applicable if the protocol type is icmp. Matches based on the specified
ICMP type. You can specify one of the following. Enter the type name or the type num-
ber (for example, “dest-unreachable” or “3”).
• any-type – Matches on any ICMP type.
• dest-unreachable, or 3 – destination is unreachable.
• echo-reply, or 0 – echo reply.
• echo-request, or 8 – echo request.
• info-reply, or 16 – information reply.
• info-request, or 15 – information request.
• mask-reply, or 18 – address mask reply.
• mask-request, or 17 – address mask request.
• parameter-problem, or 12 – parameter problem.
• redirect, or 5 – redirect message.
• source-quench, or 4 – source quench.
• time-exceeded, or 11 – time exceeded.
• timestamp, or 14 – timestamp.
• timestamp-reply, or 13 – timestamp reply.
code icmp-code This option is applicable if the protocol type is icmp. Matches based on the specified
ICMP code.
Replace code-num with an ICMP code number (0-254), or specify any-code to
match on any ICMP code.
Parameter Description
any | The source IP addresses to filter.
host host-src-ipaddr |
• any - the ACL matches on any source IP address.
net-src-ipaddr {
filter-mask | • host host-src-ipaddr - the ACL matches only on the specified host IP address.
/mask-length} • net-src-ipaddr {filter-mask | /mask-length} - the ACL matches on
any host in the specified subnet. The filter-mask specifies the portion of the
address to fil- ter:
• Use 0 to match.
• Use 255 to ignore.
For example, the filter-mask 0.0.0.255 filters on a 24-bit subnet.
Alternatively, you can use /mask-length to specify the portion of the address to
fil- ter. For example, you can specify “/24” instead “0.0.0.255” to filter on a 24-bit
subnet.
eq src-port | The source protocol ports to filter for TCP and UDP:
gt src-port |
• eq src-port - The ACL matches on traffic from the specified source port.
lt src-port |
range • gt src-port - The ACL matches on traffic from any source port with a
start-src-port
higher number than the specified port.
end-src-port • lt src-port - The ACL matches on traffic from any source port with a lower
num- ber than the specified port.
• range start-src-port end-src-port - The ACL matches on traffic
from any source port within the specified range.
fragments Matches on packets in which the More bit in the header is set (1) or has a non-zero off-
set.
vlan vlan-id Matches on the specified VLAN. VLAN matching occurs for incoming traffic only.
dscp num Matches on the 6-bit Diffserv value in the IP header, 1-63.
Parameter Description
established Matches on TCP packets in which the ACK or RST bit is set.
This option is useful for protecting against attacks from outside. Since a TCP connec-
tion from the outside does not have the ACK bit set (SYN only), the connection is
dropped. Similarly, a connection established from the inside always has the ACK bit
set. (The first packet to the network from outside is a SYN/ACK.)
log Configures the ACOS device to generate log messages when traffic matches the ACL.
[transparent-session-
The transparent-session-only option limits logging for an ACL rule to
only]
creation and deletion of transparent sessions for traffic that matches the ACL rule.
Default No ACLs are configured by default. When you configure one, the log option is disabled
by default.
Usage An ACL can contain multiple rules. Each access-list command configures one rule.
Rules are added to the ACL in the order you configure them. The first rule you add appears
at the top of the ACL.
Rules are applied to the traffic in the order they appear in the ACL (from the top, which is the
first, rule downward). The first rule that matches traffic is used to permit or deny that traffic.
After the first rule match, no additional rules are compared against the traffic.
To move a rule within the sequence, delete the rule, then re-add it with a new sequence
number.
accounting
Description Configure TACACS+ as the accounting method for recording information about user activi-
ties. The ACOS device supports the following types of accounting:
• EXEC accounting – provides information about EXEC terminal sessions (user shells)
on the ACOS device.
• Command accounting – provides information about the EXEC shell commands exe-
cuted under a specified privilege level. This command also allows you to specify the
debug level.
Parameter Description
start-stop Sends an Accounting START packet to TACACS+ servers when a user establishes a CLI
session, and an Accounting STOP packet when the user logs out or the session times out.
stop-only Only sends an Accounting STOP packet when the user logs out or the session times out.
radius | tacplus Specifies the type of accounting server to use.
cmd-level Specifies which level of commands will be accounted:
• 15 (admin) - commands available to the admin (all commands).
• 14 (config) - commands available in config mode (not including the commands of the admin
and those under the admin mode).
• 1 (priv EXEC) - commands available in privileged EXEC mode.
• 0 (user EXEC) - commands available in user EXEC mode.
Command levels 2-13 as the same as command level 1.
debug-level Specifies the debug level for accounting. The debug level is set as flag bits for different types of
debug messages. The ACOS device has the following types of debug messages:
• 0x1 - Common information such as “trying to connect with TACACS+ servers”,
“getting response from TACACS+ servers”; they are recorded in syslog.
• 0x2 - Packet fields sent out and received by ACOS, not including the length fields; they
are printed out on the terminal.
• 0x4 - Length fields of the TACACS+ packets will also be printed on the terminal.
• 0x8 - Information about the TACACS+ MD5 encryption is recorded in syslog.
Default N/A
Usage The accounting server also must be configured. See “radius-server” on page 175 or “tacacs-
server host” on page 205.
Example The following command configures the ACOS device to send an Accounting START
packet to the previously defined TACACS+ servers when a user establishes a CLI session
on the device. The ACOS device also will send an Accounting STOP packet when a user
logs out or their session times out.
Example The following command configures the ACOS device to send an Accounting STOP
packet when a user logs out or a session times out.
Example The following command configures the ACOS device to send an Accounting STOP packet
to TACACS+ servers before a CLI command of level 14 is executed.
ACOS(config)#accounting debug l5
admin
Description Configure an admin account for management access to the ACOS device.
This command changes the CLI to the configuration level for the specified admin account,
where the following admin-related commands are available:
Command Description
access {cli | web | axapi} Specifies the management interfaces through which the admin is allowed to
access the ACOS device.
By default, access is allowed through the CLI, GUI, and aXAPI.
disable Disables the admin account.
By default, admin accounts are enabled when they are added.
enable Enables the admin account.
By default, admin accounts are enabled when they are added.
password string Sets the password, 1-63 characters. Passwords are case sensitive and can con-
tain special characters. (For more information, see “Special Character Support
in Strings” on page 15.)
The default password is “a10”; this is the default for the “admin” account
and for any admin account you configure if you do not configure the
password for the account.
Command Description
privilege Sets the privilege level for the account:
{
• read – The admin can access the User EXEC and Privileged EXEC levels
read | of the CLI only.
write |
partition-enable-disable
• write – The admin can access all levels of the CLI.
pertition-name | • partition-read – The admin has read-only privileges within the
partition-read L3V partition to which the admin is assigned, and read-only privileges
partition-name | for the shared partition.
partition-write • partition-write – The admin has read-write privileges within the
partition-name L3V partition to which the admin is assigned. The admin has read-only
} privi- leges for the shared partition.
Command Description
trusted-host { Specifies the host or subnet address from which the admin is allowed to log
ipaddr onto the ACOS device. The trusted host can be either a single host
{subnet-mask | /mask-length} | (specified with the IP address and subnet mask), or a configured access
access-list acl-id} control list (ACL) on your system.
The default trusted host is 0.0.0.0/0, which allows access from any host or sub-
net.
unlock Unlocks the account. Use this option if the admin has been locked out
due to too many login attempts with an incorrect password. (To configure
lockout parameters, see “admin-lockout” on page 79.)
Default The system has a default admin account, with username “admin” and password “a10”. The
default admin account has write privilege and can log on from any host or subnet address.
Usage An additional session is reserved for the “admin” account to ensure access. If the
maximum number of concurrent open sessions is reached, the “admin” admin can still log
in using the reserved session. This reserved session is available only to the “admin”
account.
Example The following commands add admin “adminuser1” with password “1234”:
ACOS(config)#admin adminuser1
ACOS(config-admin:adminuser1)#password 1234
Example The following commands add admin “adminuser3” with password “abcdefgh” and write priv-
ilege, and restrict login access to the 10.10.10.x subnet only:
ACOS(config)#admin adminuser3
ACOS(config-admin:adminuser3)#password abcdefgh
ACOS(config-admin:adminuser3)#privilege write
ACOS(config-admin:adminuser3)#trusted-host 10.10.10.0 /24
Example The following commands configure an admin account for a private partition:
Example The following commands deny management access by admin “admin2” using the CLI or
aXAPI:
ACOS(config)#admin admin2
ACOS(config-admin:admin2)#no access cli
ACOS(config-admin:admin2)#no access axapi
Example The following commands add admin “admin4” with password “examplepassword” and
default privileges, and restricts login access as defined by access list 2. The show output
con- firms that “ACL 2” is the trusted host:
admin-lockout
Description Set lockout parameters for admin sessions.
Parameter Description
duration minutes Number of minutes a lockout remains in effect. After the lock-
out times out, the admin can try again to log in. You can
specify 0-1440 minutes. To keep accounts locked until you or
another authorized administrator unlocks them, specify 0.
The default duration is 10 minutes.
enable Enables the admin lockout feature.
The lockout feature is disabled by default.
reset-time minutes Number of minutes the ACOS device remembers failed login
attempts. You can specify 1-1440 minutes.
The default reset time is 10 minutes.
threshold number Number of consecutive failed login attempts allowed before
an administrator is locked out. You can specify 1-10.
The default threshold is 5.
ACOS(config)#admin-lockout enable
admin-session clear
Description Terminate admin sessions.
Parameter Description
all Clears all other admin sessions with the ACOS device except
yours.
session-id Clears only the admin session you specify.
To display a list of active admin sessions, including their ses-
sion IDs, use the show admin session command (see
show admin for more information).
Default N/A
aflex
Description Configure and manage aFleX policies.
For complete information and examples for configuring and managing aFleX policies, see
the aFleX Scripting Language Reference Guide.
Syntax aflex {
check name |
copy src-name dst-name |
create name |
delete name |
help |
Parameter Description
check Check the syntax of the specified aFleX script.
copy Copy the src-name aFleX script to dst-name.
create Create an aFleX script with the specified name.
delete Delete the specified aFleX script.
help View aFleX help.
rename Rename an aFleX script from src-name to dst-name.
aflex-scripts start
Description Begin a transaction to edit an aFleX script within the CLI. See the aFleX Scripting
Language Reference Guide.
application-type
Description Define the type of application (ADC or CGN) that will be configured in this partition,
includ- ing the shared partition.
For more information, refer to the Configuration Application Delivery Partitions guide.
arp
Parameter Description
ipaddr IP address of the static entry.
mac-address MAC address of the static entry.
port-num Ethernet port number.
trunk-id Trunk ID number.
vlan-id If the ACOS device is deployed in transparent mode, and the
interface is a tagged member of multiple VLANs, use this option to
specify the VLAN for which to add the ARP entry.
Default The default timeout for learned entries is 300 seconds. Static entries do not time out.
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
arp-timeout
Description Change the aging timer for dynamic ARP entries.
Replace seconds with the number of seconds a dynamic entry can remain unused
before being removed from the ARP table (60-86400).
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
audit
Description Configure command auditing.
Parameter Description
enable Enables command auditing.
Command auditing is disabled by default.
privilege Enables logging of Privileged EXEC commands. Without this option,
only configuration commands are logged.
num-entries Specifies the number of entries the audit log file can hold. You can
specify 1000-30000 entries. When the log is full, the oldest entries
are removed to make room for new entries.
When the feature is enabled, the audit log can hold 20,000 entries by
default.
Usage Command auditing logs the following types of system management events:
• Admin logins and logouts for CLI, GUI, and aXAPI sessions
• Unsuccessful admin login attempts
• Configuration changes. All attempts to change the configuration are logged, even if
they are unsuccessful.
• CLI commands at the Privileged EXEC level (if audit logging is enabled for this level)
The audit log is maintained in a separate file, apart from the system log. The audit log is
ADP- aware. The audit log messages that are displayed for an admin depend upon the
admin’s role (privilege level). Admins with Root, Read Write, or Read Only privileges who
view the audit log can view all the messages, for all system partitions.
Admins who have privileges only within a specific partition can view only the audit
log messages related to management of that partition. Partition Real Server
Operator admins can not view any audit log entries.
Parameter Description
ldap Use LDAP for console authentication
local Use the ACOS configuration for console authentication.
radius Use RADIUS for console authentication.
tacplus Use TACACS+ for console authentication.
Example The following example grants LDAP and local console authentication:
authentication enable
Description Configuration authentication of admin enable (Privileged mode) access.
Parameter Description
local Uses the ACOS configuration for authentication of the enable password.
tacplus Uses TACACS+ for authentication of the enable password.
Default local
Default Disabled
authentication mode
Description Enable tiered authentication.
Parameter Description
multiple Enable “tiered” authentication, where the ACOS device will check the next method even if the primary
method does respond but authentication fails using that method.
For example, if the primary method is RADIUS and the next method is TACACS+, and RADIUS
rejects the admin, tiered authentication attempts to authenticate the admin using TACACS+.
This authentication behavior is summarized below:
1. Try method1. If a method1 server replies, permit or deny access based on the server reply.
2. If no method1 servers reply or a method1 server denies access, try method2.
3. If no method2 servers reply or a method2 server denies access, try method3.
4. If no method3 servers reply or a method3 server denies access, try method4. If authentication
suc- ceeds, the admin is permitted. Otherwise, the admin is denied.
single Enable single authentication mode, where the backup authentication method will only be used if the
primary method does not respond. If the primary method does respond but denies access, then the
secondary method is simply not used. The admin is not granted access.
This authentication behavior is summarized below:
1. Try method1. If a method1 server replies, permit or deny access based on the server reply.
2. Only if no method1 servers reply, try method2. If a method2 server replies, permit or deny
access based on the server reply.
3. Only if no method2 servers reply, try method3. If a method3 server replies, permit or deny
access based on the server reply.
4. Only if no method3 servers reply, try method4. If authentication succeeds, the admin is
permitted. Otherwise, the admin is denied.
authentication multiple-auth-reject
Description Configure support for multiple concurrent admin sessions using the same account.
Default Disabled. Multiple concurrent admin sessions using the same account are allowed.
authentication type
Description Set the authentication method used to authenticate administrative access to the ACOS
device.
Parameter Description
console Applies the authentication settings only to access through the
con- sole (serial) port. Without this option, the settings apply to all
types of admin access.
type method1 Uses the ACOS configuration for authentication. If the administrative
[method2 username and password match an entry in the configuration, the
[method3 administrator is granted access.
[method4]]]
The following authentication types are supported:
• ldap—Uses an external LDAP server for authentication.
• local—Uses the ACOS configuration for authentication. If the
administrative username and password match an entry in the con-
figuration, the administrator is granted access.
• radius—Uses an external RADIUS server for authentication.
• tacplus—Uses an external TACACS+ server for authentication.
By default, only local authentication is used.
Usage The local database (local option) must be included as one of the authentication
sources, regardless of the order is which the sources are used. Authentication using only
a remote server is not supported.
To configure the external authentication server(s), see “radius-server” on page 175 or “tacacs-
server host” on page 205.
Example The following commands configure a pair of RADIUS servers and configure the ACOS
device to try them first, before using the local database. Since 10.10.10.12 is added first,
this server
will be used as the primary server. Server 10.10.10.13 will be used only if the primary server
is unavailable. The local database will be used only if both RADIUS servers are unavailable.
authorization
Description Configure authorization for controlling access to functions in the CLI. The ACOS device
can use TACACS+ for authorizing commands executed under a specified privilege level.
This command also allows the user to specify the level for authorization debugging.
Parameter Description
cmd-level Specifies the level of commands that will be authorized. The com-
mands are divided into the following levels:
• Privilege 0: Read-only
• Privilege 1: Read-write
• Privilege 2–4: Not-used
• Privilege 5–14: Reserved for ACOS-specific roles
• Privilege 15: Read-write
Usage The authorization server also must be configured. See “radius-server” on page 175 or “tacacs-
server host” on page 205.
Example The following command specifies the authorization method for commands executed at
level 14: try TACACS+ first but if it fails to respond, then allow the command to execute
with- out authorization.
backup-periodic
Description Schedule periodic backups.
CAUTION: After configuring this feature, make sure to save the configuration. If the device
resets before the configuration is saved, the backups will not occur.
Parameter Description
target • Specify system to back up the following system files:
• Startup-config files
• Admin accounts and login and enable passwords
• aFleX scripts
• Class lists and black/white lists
• Scripts for external health monitors
• SSL certificates, keys, and certificate revocation lists
• If custom configuration profiles are mapped to the startup-config, they also are backed up.
• Specify log to back up the system log.
You can specify either option, or both options.
hour num | Specifies how often to perform the back ups. You can specify one of the following:
day num |
• hour num—Performs the backup each time the specified number of hours passes. For example,
week num specifying hour 3 causes the backup to occur every 3 hours. You can specify 1-65534 hours.
There is no default.
• day num—Performs the backup each time the specified number of days passes. For example,
specifying day 5 causes the backup to occur every 5 days. You can specify 1-199 days. There is
no default.
• week num—Performs the backup each time the specified number of weeks passes. For
example, specifying week 4 causes the backup to occur every 4 weeks. You can specify 1-
199 weeks. There is no default.
use-mgmt-port Uses the management interface as the source interface for the connection to the remote
device. The management route table is used to reach the device. Without this option, the
ACOS device attempts to use the data route table to reach the remote device through a data
interface.
url Specifies the file transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter to display a prompt for each
part of the URL. If you enter the entire URL and a password is required, you will still be prompted
for the password. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
Example The following commands schedule weekly backups of the entire system, verify the configu-
ration, and save the backup schedule to the startup-config:
backup store
Description Configure and save file access information for backup. When you back up system
informa- tion, you can save typing by specifying the name of the store instead of the
options in the store.
Parameter Description
store-name Name of the store.
url File transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter to
display a prompt for each part of the URL. If you enter the entire
URL and a password is required, you will still be prompted for the
pass- word. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Default None
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
banner
Description Set the banners to be displayed when an admin logs onto the CLI or accesses the
Privileged EXEC mode.
Parameter Description
exec Configures the EXEC mode banner (1-128 characters).
login Configures the login banner (1-128 characters).
multi-line Hexadecimal number to indicate the end of a multi-line message. The
end-marker end marker is a simple string up to 2-characters long, each of the
which must be an ASCII character from the following range: 0x21-
0x7e.
The multi-line banner text starts from the first line and ends at the
marker. If the end marker is on a new line by itself, the last line of
the banner text will be empty. If you do not want the last line to be
empty, put the end marker at the end of the last non-empty line.
Example The following examples set the login banner to “welcome to login mode” and set the
EXEC banner to a multi-line greeting:
bfd echo
Description Enables echo support for Bidirectional Forwarding Detection (BFD).
Default Disabled
Usage BFD echo enables a device to test data path to the neighbor and back. When a device
gener- ates a BFD echo packet, the packet uses the routing link to the neighbor device to
reach the device. The neighbor device is expected to send the packet back over the same
link.
bfd enable
Description Globally enable BFD packet processing.
Default Disabled
bfd interval
Description Configure BFD timers.
Parameter Description
interval ms Rate at which the ACOS device sends BFD control packets to its BFD neighbors. You can
specify 48-1000 milliseconds (ms). The default is 800 ms.
min-rx ms Minimum amount of time in milliseconds that the ACOS device waits to receive a BFD control
packet from a BFD neighbor. If a control packet is not received within the specified time, the
multiplier (below) is incremented by 1. You can specify 48-1000 ms. The default is 800 ms.
multiplier num Maximum number of consecutive times the ACOS device will wait for a BFD control packet
from a neighbor. If the multiplier value is reached, the ACOS device concludes that the routing
process on the neighbor is down. You can specify 3-50. The default is 4
Usage If you configure the interval timers on an individual interface, then the interface settings are
used instead of the global settings. Similarly, if the BFD timers have not been configured
on an interface, then the interface will use the global settings.
NOTE: BFD always uses the globally configured interval timer if it's for a BGP loopback
neighbor.
bgp
Description Information about BGP CLI commands is located in the “Config Commands: Router - BGP”
chapter in the Network Configuration Guide.
big-buff-pool
Description On high-end models only, you can enable the big-buff-pool option to expand
support from 4 million to 8 million buffers and increase the buffer index from 22 to 24 bits.
NOTE: The AX 5200-11 requires 96 Gb of memory to support this feature. To check that
your system meets this requirement, use the show memory system CLI com-
mand.
Default Disabled
Example The following commands enable a larger I/O buffer pool for an AX 5630:
ACOS(config)#no big-buff-pool
This will modify your boot profile to disable big I/O buffer pool.
It will take effect starting from the next reboot.
Please confirm: You want to disable the big I/O buffer pool(N/Y)?:
Y
block-abort
Description Use this command to exit block-merge or block-replace mode without implementing
the new configurations made in block mode.
Syntax block-abort
Default N/A
Usage Use this command to discard any changes you make while in block-merge or block-replace
mode. In order to exit block mode without committing the new configuration changes, use
block-abort. This command must be entered before block-merge-end or block-
replace-end in order for all block configuration changes to be deleted. This command
ends block configuration mode.
block-merge-end
Description Use this command to exit block-merge mode and integrate new configurations into the
cur- rent running config.
Syntax block-merge-end
Default N/A
Usage This command exits block-merge configuration mode and merges all of your new configura-
tion with the existing running configuration. In the case of overlapping configurations, the
new configuration will be used and any child instances will be deleted. Any old configura-
tions which are not replaced in block-merge mode will remain in the running configuration
after this command is entered. The new configurations are merged into the running configu-
ration without disturbing live traffic.
block-merge-start
Description Use this command to enter block-merge configuration mode.
Syntax block-merge-start
This command takes you to the Block-merge configuration level, where all configuration
commands are available.
Default Disabled.
Usage This command enters block-merge configuration mode but leaves the ACOS device up.
While in block-merge mode, new configurations will not be entered into the running
config- uration. At the block-merge configuration level, you can enter new configurations
which you want to merge into the running configuration. Any configuration that overlaps
with the cur- rent running configuration will be replaced when ending block-merge
mode. Any configura- tions in the running config which are not configured in block-
merge mode will continue to be included in the running configuration mode after exiting
block-merge mode.
block-replace-end
Description Enter this command to end block-replace configuration mode and replace the current
run- ning configuration with the new configurations.
Syntax block-replace-end
Default N/A
Usage This command exits block-replace configuration mode and replaces all of your existing
con- figuration with the new configuration. Any old configurations which are not
replaced in block-replace mode will be removed in the running configuration after this
command is
entered. The new configurations become the running configuration without disturbing live
traffic.
block-replace-start
Description Use this command to enter block-replace configuration mode.
Syntax block-replace-start
This command takes you to the Block-replace configuration level, where all configuration
commands are available.
Default Disabled.
Usage This command enters block-replace configuration mode but leaves the ACOS device up.
While in block-replace mode, new configurations will not be entered into the running con-
figuration. At the block-replace configuration level, you can enter a new configuration
which you want to replace the running configuration. All of the running configuration will
be replaced when ending block-merge mode. If an object that exists in the running
configura- tion is not configured in block-replace, then all configurations for that object will
be removed upon ending block-replace mode.
boot-block-fix
Description Repair the master boot record (MBR) on the hard drive or compact flash.
Parameter Description
cf Repair the compact flash.
hd Repair the hard disk.
Default N/A
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
Usage The MBR is the boot sector located at the very beginning of a boot drive. Under
advisement from A10 Networks, you can use the command if your compact flash or hard
drive cannot boot. If this occurs, boot from the other drive, then use this command.
bootimage
Description Specify the boot image location from which to load the system image the next time the
ACOS device is rebooted.
Parameter Description
cf | hd Boot medium. The ACOS device always tries to boot using the hard
disk (hd) first. The compact flash (cf ) is used only if the hard disk is
unavailable.
pri | sec Boot image location, primary or secondary.
Default The default location is primary, for both the hard disk and the compact flash.
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
Example The following command configures the ACOS device to boot from the secondary image
area on the hard disk the next time the device is rebooted:
bpdu-fwd-group
Description Configure a group of tagged Ethernet interfaces for forwarding Bridge Protocol Data Units
(BPDUs). BPDU forwarding groups enable you to use the ACOS device in a network that
runs Spanning Tree Protocol (STP).
A BPDU forwarding group is a set of tagged Ethernet interfaces that will accept and
broadcast STP BPDUs among themselves. When an interface in a BPDU forwarding group
receives an STP BPDU (a packet addressed to MAC address 01-80-C2-00-00-00), the
interface broadcasts the BPDU to all the other interfaces in the group.
If the ACOS device is a member of an aVCS virtual chassis, specify the group number as
follows: DeviceID/group-num
This command changes the CLI to the configuration level for the BPDU forwarding group,
where the following command is available.
This command enables you to specify the ethernet interfaces you want to add to the
BPDU forwarding group.
Default None
Usage This command is specifically for configuring VLAN-tagged interfaces to accept and forward
BPDUs.
Example The following commands create BPDU forwarding group 1 containing Ethernet ports 1-3,
and verify the configuration:
ACOS(config)# bpdu-fwd-group 1
ACOS(config-bpdu-fwd-group:1)# ethernet 1 to 3
ACOS(config-bpdu-fwd-group:1)# show bpdu-fwd-group
BPDU forward Group 1 members: ethernet 1 to 3
bridge-vlan-group
If the ACOS device is a member of an aVCS virtual chassis, specify the group number as
follows: DeviceID/group-num
This command changes the CLI to the configuration level for the specified bridge VLAN
group, where the following configuration commands are available:
Command Description
forward-all-traffic Configures the bridge VLAN group to be able to forward all kinds of
traffic.
forward-ip-traffic Configures the bridge VLAN group to be able to typical traffic
between hosts, such as ARP requests and responses.
This is the default setting.
[no] name string Specifies a name for the group. The string can be 1-63 characters
long. If the string contains blank spaces, use double quotation marks
around the entire string.
There is no default name set.
Command Description
[no] router-interface ve num Adds a Virtual Ethernet (VE) interface to the group. This command is
applicable only on ACOS devices deployed in routed (gateway)
mode. The VE number must be the same as the lowest numbered
VLAN in the group.
By default this is not set.
[no] vrid num Configure a VRID for the bridge VLAN group; this can be used
with additional groups sharing the same VRID in VRRP-A
configurations.
[no] vlan vlan-id Adds VLANs to the group.
[vlan vlan-id ... | to vlan vlan-id]
By default this is not set.
Default By default, the configuration does not contain any bridge VLAN groups. When you create
a bridge VLAN group, it has the default settings described above.
Usage VLAN-to-VLAN bridging is useful in cases where reconfiguring the hosts on the
network either into the same VLAN, or into different IP subnets, is not desired or is
impractical.
In bridge VLAN group configurations, the VE number must be the same as the lowest
numbered VLAN in the group.
Example For more information, including configuration notes and examples, see the “VLAN-to-VLAN
Bridging” chapter in the System Configuration and Administration Guide.
cgnv6
Description CGN and IPv6 migration commands.
For more information about these commands, refer to the Command Line Interface Reference
(for CGN).
Parameter Description
list-name Adds the list to the running-config.
ac Identifies this as an Aho-Corasick class list.
filename Saves the list to a standalone file on the ACOS device.
NOTE: A class list can be exported only if you use the file option.
This command changes the CLI to the configuration level for the specified class list, where
the following commands are available:
Command Description
[no] contains sni-string Matches if the specified string appears anywhere within the SNI value.
[no] ends-with sni-string Matches only if the SNI value ends with the specified string.
[no] equals sni-string Matches only if the SNI value completely matches the specified string.
[no] starts-with sni-string Matches only if the SNI value starts with the specified string.
(The other commands are common to all CLI configuration levels. See “Config Commands:
Global” on page 61.)
Default None
Usage The match options are always applied in the following order, regardless of the order in
which the rules appear in the configuration.
• Equals
• Starts-with
• Contains
• Ends-with
If a template has more than one rule with the same match option (equals, starts-with,
contains, or ends-with) and an SNI value matches on more than one of them, the most-
specific match is always used.
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
Parameter Description
list-name Adds the list to the running-config.
ac Identifies this as an Aho-Corasick class list.
dns Identifies this as a DNS class list.
ipv4 | ipv6 Identifies this as an IPv4 or IPv6 class list.
string Identifies this as a string class list.
Parameter Description
string-case-insensitive Identifies this as a case-insensitive string class list.
file filename Saves the list to a standalone file on the ACOS device.
NOTE: A class list can be exported only if you use the file option.
This command changes the CLI to the configuration level for the specified class list, where
the following command is available:
(The other commands are common to all CLI configuration levels. See “Config Commands:
Global” on page 61.)
Parameter Description
ipaddr /network-mask Specifies the IPv4 host or subnet address of the client. The network-mask specifies
the network mask.
To configure a wildcard IP address, specify 0.0.0.0 /0. The wildcard address
matches on all addresses that do not match any entry in the class list.
ipv6-addr/subnet-length Specifies the IPv6 host or network address of the client.
glid num | lid num Specifies the ID of the IP limiting rule to use for matching clients. You can use a
sys- tem-wide (global) IP limiting rule or an IP limiting rule configured in a PBSLB
policy template.
• To use an IP limiting rule configured at the Configuration mode level, use the
glid num option.
• To use an IP limiting rule configured at the same level (in the same PBSLB
policy template) as the class list, use the lid num option.
To exclude a host or subnet from being limited, do not specify an IP limiting rule.
Default None
Usage Configure the GLIDs or LIDs before configuring the class list entries. To configure a GLID
or LID for IP limiting, see “glid” on page 123 or “slb template policy” in the Command Line
Inter- face Reference for ADC.
As an alternative to configuring class entries on the ACOS device, you can configure the
class list using a text editor on another device, then import the class list onto the ACOS
device. To import a class list, see “import” on page 46.
NOTE: If you use a class-list file that is periodically re-imported, the age for class-list entries
added to the system from the file does not reset when the class-list file is re-
imported. Instead, the entries are allowed to continue aging normally. This is by
design.
For more information about IP limiting, see the DDoS Mitigation Guide (for ADC).
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
If a LID or GLID in a class list contains settings for request limiting or request-rate limiting, the
settings apply only if the following conditions are true:
In this case, the settings apply only to the virtual port. The settings do not apply in any of
the following cases:
• The policy template is applied to the virtual server, instead of the virtual port.
• The settings are in a system-wide GLID.
• The settings are in a system-wide policy template.
NOTE: This limitation does not apply to connection limiting or connection-rate limiting.
Those settings are valid in all the cases listed above.
Example The following commands configure class list “global”, which matches on all clients, and
uses IP limiting rule 1:
ACOS(config)#class-list global
ACOS(config-class list)#0.0.0.0/0 glid 1
Parameter Description
list-name Adds the list to the running-config.
dns Identifies this list as a DNS class list.
file filename Saves the list to a file.
This command changes the CLI to the configuration level for the specified class list, where
the following command is available:
This command specifies the match conditions for domain strings and maps matching
strings to LIDs.
Parameter Description
match-option Specifies the match criteria for the domain-string. The match-option
can be one of the following:
• dns contains – The entry matches if the DNS request is
for a domain name that contains the domain-string anywhere
within the requested domain name.
• dns starts-with – The entry matches if the DNS request is
for a domain name that begins with the domain-string.
• dns ends-with – The entry matches if the DNS request is for
a domain name that ends with the domain-string.
domain-string Specifies all or part of the domain name on which to match. You
can use the wildcard character * (asterisk) to match on any
single character.
For example, “www.example*.com” matches on all the following
domain names: www.example1.com, www.example2.com,
www.examplea.com, www.examplez.com, and so on.
For wildcard matching on more than one character, you can use the
dns contains, dns starts-with, and dns ends-with
options. For example, “dns ends-with example.com” matches on
both abc.example.com and www.example.com.
lid num Specifies a list ID (LID) in the DNS template. LIDs contain DNS cach-
ing policies. The ACOS device applies the DNS caching policy in the
specified LID to the domain-string.
(The other commands are common to all CLI configuration levels. See “Config
Commands: Global” on page 61.)
Default None
Usage Configure the LIDs before configuring the class-list entries. LIDs for DNS caching can be con-
figured in DNS templates. (See “slb template dns” in the Command Line Interface Reference
for ADC.
As an alternative to configuring class entries on the ACOS device, you can configure the
class list using a text editor on another device, then import the class list onto the ACOS
device. To import a class list, see “import” on page 46.
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
Example See the “DNS Optimization and Security” chapter in the Application Delivery and Server
Load Balancing Guide.
Parameter Description
list-name Adds the list to the running-config.
file filename Saves the list to a standalone file on the ACOS device.
ipv4 | ipv6 Identifies this list as an IPv4 or IPv6 class list.
This command changes the CLI to the configuration level for the specified class list, where
the following commands are available.
This command specifies the inside subnet that requires the NAT.
Parameter Description
/network-mask Specify the network mask.
To configure a wildcard IP address, specify 0.0.0.0 /0. The
wildcard address matches on all addresses that do not match
any entry in the class list.
glid num Specify the global LID that refers to the pool.
(The other commands are common to all CLI configuration levels. See “Config Commands:
Global” on page 61.)
Default None
Usage First configure the IP pools. Then configure the global LIDs. In each global LID, use the use-
nat-pool pool-name command to map clients to the pool. Then configure the class list
entries.
As an alternative to configuring class entries on the ACOS device, you can configure the
class list using a text editor on another device, then import the class list onto the ACOS
device. To import a class list, see “import” on page 46.
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
Example See the “Configuring Dynamic IP NAT with Many Pools” section in the “Network Address
Translation” chapter of the System Configuration and Administration Guide.
class-list (string)
Description Configure a class list that you can use to modify aFleX scripts, without he need to edit
the script files themselves.
Parameter Description
list-name Adds the list to the running-config.
file filename Saves the list to a standalone file on the ACOS device.
string Identifies this as a string class list.
Usage A class list can be exported only if you use the file option.
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
class-list (string-case-insensitive)
Description Configure a cast-insensitive class list that you can use to modify aFleX scripts, without he
need to edit the script files themselves.
Parameter Description
list-name Adds the list to the running-config.
file filename Saves the list to a standalone file on the ACOS device.
string-case-insensitive Identifies this as a case-insensitive string class list.
Usage A class list can be exported only if you use the file option.
If you delete a file-based class list (no class-list list-name), save the configuration
(“write memory” on page 57) to complete the deletion.
configure sync
Description Synchronize the local running-config to a peer’s running-config.
Parameter Description
running Synchronize the local running-config to a peer’s running-config.
all Synchronize the local running-config to a peer’s running-config, and the local startup-
con- fig to the same peer’s startup-config.
all-partitions Synchronize all partition configurations.
partition name Synchronize the configuration for the specified partition only.
auto-authentication Authenticate using the local user name and password.
dest-ipaddress IP address of the peer to which you want to synchronize your configurations.
Default N/A
Example The following example synchronizes both the local running-config and startup-config for
the shared partition only to the peer at IP address 10.10.10.4:
copy
Description Copy a running-config or startup-config.
Parameter Description
running-config Copies the commands in the running-config to the specified
URL or local profile name.
startup-config Copies the configuration profile that is currently linked to
“startup-config” and saves the copy under the specified
URL or local profile name.
use-mgmt-port Uses the management interface as the source interface for
the connection to the remote device. The management route
table is used to reach the device. By default, the ACOS
device attempts to use the data route table to reach the
remote device through a data interface.
Parameter Description
url Copies the running-config or configuration profile to a
remote device. The URL specifies the file transfer protocol,
username, and directory path.
You can enter the entire URL on the command line or press
Enter to display a prompt for each part of the URL. If you enter
the entire URL and a password is required, you will still be
prompted for the password. The password can be up to 255
characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
NOTE: You cannot use the profile name “default”. This name is reserved and always refers
to the configuration profile that is stored in the image area from which the ACOS
device most recently rebooted.
Default None
Usage If you are planning to configure a new ACOS device by loading the configuration from
another ACOS device:
1. On the configured ACOS device, use the copy startup-config url command
to save the startup-config to a remote server.
2. On the new ACOS device, use the copy url startup-config command to
copy the configured ACOS device’s startup-config from the remote server onto the
new ACOS device.
3. Use the reboot command (at the Privileged EXEC level) to reboot the new
ACOS device.
4. Modify parameters as needed (such as IP addresses).
If you attempt to copy the configuration by copying-and-pasting it from a CLI session on the
configured ACOS device, some essential parameters such as interface states will not be
copied.
Example The following command copies the configuration profile currently linked to “startup-
config” to a profile named “slbconfig3” and stores the profile locally on the ACOS
device:
debug
NOTE: It is recommended that you use the AXdebug commands instead of the debug
command. (See “AX Debug Commands” on page 365.)
delete
Description Delete a locally stored file from the ACOS device.
Parameter Description
file-type Type of file to be deleted:
• auth-portal (portal file for HTTP authentication)
• auth-portal-image (image file for the default authentication
por- tal)
• auth-saml-idp (SAML metadata of the identity provider)
• bw-list (blacklist or whitelist)
• cgnv6 fixed-nat (fixed-NAT port mapping file)
• debug-monitor (debug file)
• geo-location (geo-location file)
• geo-location-class-list (geo-location class-list file)
• health-external (external script program)
• health-postfile (HTTP POST data file)
• license (temporary license file for a virtual/soft/cloud ACOS
device)
• local-uri-file (local URI files for HTTP response)
• partition (hard delete an L3V partition)
• startup-config (startup configuration profile)
• web-category database (web-category database)
file-name Name of the file you want to delete.
NOTES:
• For the geo-location option, you can specify all instead of a
spe- cific file-name to delete all files.
• There is no file-name option for web-category database.
Default N/A
Usage The startup-config file type deletes the specified configuration profile linked to
startup- config. The command deletes only the specific profile file-name you specify.
Usage Admins with the following CLI roles are allowed to disable or re-enable clearing of SLB
and Ethernet statistics:
• write
• partition-write
Example The following command disables reset of SLB and Ethernet statistics:
disable slb
Description Disable real or virtual servers.
Parameter Description
server-name Disables the specified real or virtual server.
port port-num Disables only the specified service port. If you omit the server-
name option, the port is disabled on all real or virtual servers. Oth-
erwise, the port is disabled only on the server you specify.
Default Enabled
Example The following command disables port 8080 on real server “rs1”:
disable-failsafe
Description Disable fail-safe monitoring for software-related errors.
Parameter Description
all Disables fail-safe monitoring for all the following types of software
errors.
io-buffer Disables fail-safe monitoring for IO-buffer errors.
session-memory Disables fail-safe monitoring for session-memory errors.
system-memory Disables fail-safe monitoring for system-memory errors.
Default Fail-safe monitoring and automatic recovery are disabled by default, for both hardware
and software errors.
disable-management
Description Disable management access to the ACOS device.
Parameter Description
http Disables HTTP access to the management GUI.
https Disables HTTPS access to the management GUI.
ping Disables ping replies from ACOS. This option does not affect
the ACOS device’s ability to ping other devices.
snmp Disables SNMP access to the ACOS device’s SNMP agent.
ssh Disables SSH access to the CLI.
This command changes the CLI to the configuration level for the type of access you
specify. At this level, you can specify the interfaces for which to disable access, using
the following options:
Disable access for the specified protocol on the specified Ethernet interface. Use the
[to portnum] option to specify a range of Ethernet interfaces.
• management
Disable access for the specified protocol on the management interface.
The CLI lists options only for the interface types for which the access type is enabled by
default.
NOTE: Disabling ping replies from being sent by the device does not affect the device’s
ability to ping other devices.
Default Table 11 lists the default settings for each management service.
Usage If you disable the type of access you are using on the interface you are using at the time
you enter this command, your management session will end. If you accidentally lock
yourself out of the device altogether (for example, if you use the all option for all
interfaces), you can still access the CLI by connecting a PC to the ACOS device’s serial
port.
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
You can enable or disable management access, for individual access types and interfaces.
You also can use an Access Control List (ACL) to permit or deny management access
through the interface by specific hosts or subnets.
For more information, see “Access Based on Management Interface” in the Management
Access and Security Guide.
Example The following command disables HTTP access to the out-of-band management interface:
dnssec
Description Configure and manage Domain Name System Security Extensions (DNSSEC). See “Config
Commands: DNSSEC” on page 217.
do
Description Run a Privileged EXEC level command from a configuration level prompt, without
leaving the configuration level.
Syntax do command
Default N/A
Usage For information about the Privileged EXEC commands, see “Privileged EXEC Commands”
on page 35.
Example The following command runs the traceroute command from the Configuration
mode level:
enable-core
Description Change the file size of core dumps.
Parameter Description
a10 Enable A10 core dump files.
system Enable system core dump files.
System core dump files are larger than A10 core dump files.
Default If VRRP-A is configured, system core dump files are enabled by default. If VRRP-A is not
con- figured, A10 core dump files are enabled by default.
Usage You can save this command to the startup-config on SSD or HD. However, ACOS does
not support saving the command to a configuration file stored on Compact Flash (CF).
This is because the CF does not have enough storage for large core files.
enable-management
Description Enable management access to the ACOS device.
Parameter Description
acl-v4 id Permits or denies management access based on permit or deny rules in
the ACL for IPv4 addresses.
acl-v6 id Permits or denies management access based on permit or deny rules in
the ACL for IPv6 addresses.
http Allows HTTP access to the management GUI.
https Allows HTTPS access to the management GUI.
ping Allows ping replies from ACOS interfaces. This option does not affect the
ACOS device’s ability to ping other devices.
snmp Allows SNMP access to the ACOS device’s SNMP agent.
ssh Allows SSH access to the CLI.
telnet Allows Telnet access to the CLI.
NOTE: IPv6 ACLs are supported for management access through Ethernet data interfaces
and the management interface.
This command changes the CLI to the configuration level for the type of access you
specify. At this level, you can specify the interfaces for which to enable access, using
the following options:
• management
Enable access for the specified protocol on the management interface.
The CLI lists options only for the interface types for which the access type is disabled by
default.
Default The following table lists the default settings for each management service.
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
IPv6 ACLs are supported for management access through Ethernet data interfaces and the
management interface.
For more information, see “Access Based on Management Interface” in the Management
Access and Security Guide.
Example The following command enables Telnet access to Ethernet data interface 6:
Example The following commands configure IPv6 traffic filtering on the management interface and
display the resulting configuration:
ACOS(config-if:management)#show running-config
ipv6 access-list ipv6-acl1
permit ipv6 any any
!
interface management
ip address 192.168.217.28 255.255.255.0
ipv6 address 2001:192:168:217::28/64
ipv6 access-list ipv6-acl1 in
Example The following commands configure an IPv6 ACL, then apply it to Ethernet data ports 5 and
6 to secure SSH access over IPv6:
enable-password
Description Set the enable password, which secures access to the Privileged EXEC level of the CLI.
Parameter Description
string Password string (1-63) characters. Passwords are case sensitive
and can contain special characters. (For more information, see
“Special Character Support in Strings” on page 15.)
Example The following command sets the Privileged EXEC password to “execadmin”:
ACOS(config)#enable-password execadmin
end
Syntax end
Default N/A
Mode Config
Usage The end command is valid at all configuration levels of the CLI. From any configuration
level, the command returns directly to the Privileged EXEC level.
Example The following command returns from the Configuration mode level to the Privileged
EXEC level:
ACOS(config)#end
ACOS#
Syntax [no] environment temperature threshold low num medium num high num
Parameter Description
low num Low temperature threshold in Celcius; a log is generated when the
temperature drop below this threshold.
medium num Medium temperature threshold in Celcius.This threshold causes the
status in the show environment command to change between
“low/med” or “med/high”.
high num High temperature threshold in Celcius; a log is generated when the
temperature rises above this threshold.
Example Set the low temperature threshold to 20 degress Celcius, medium to 45 degrees Celcius,
and high temperature threshold to 55 degrees Celcius:
ACOS(config)#show environment
Updated information every 30 Seconds
Physical System temperature: 38C / 100F : OK-low/med
Thresholds: Low 20 / Medium 45 / High
55 Physical System temperature2: 34C / 93F : OK-low/med
Thresholds: Low 20 / Medium 45 / High 55
HW Fan Setting: Automatic
Fan1A : OK-med/high Fan1B : OK-med/high
In addition, both temperature status indicate “low/med” because the temperatures fall in
between the low threshold of 20 and medium threshold of 45.
environment update-interval
Description Configure the hardware polling interval for fault detection and log generation.
Parameter Description
num Polling interval in seconds (1-60).
The lower the update interval number, the faster the messages will
be seen in the sylog and the status reflected in the show
environment output.
Default 30 seconds
ACOS(config)#environment update-interval 5
Use the show environment to verify this change, or to view the current hardware polling
interval. The first line in the output shows the hardware polling interval:
ACOS(config)#show environment
erase
Description Erase the startup-config file.
This command returns the device to its factory default configuration after the next reload
or reboot.
To remove imported files or inactive partitions, you must use the system-reset
command. (See “system-reset” on page 204.)
Parameter Description
preserve-management Keeps the configured management IP address and default
gateway, instead of erasing them and resetting them to
their factory defaults following reload or reboot.
preserve-accounts Keeps the configured admin accounts, instead of
erasing them. Likewise, this option keeps any
modifications to the “admin” account, and does not
reset the account to its defaults following reload or
reboot.
reload Reloads ACOS after the configuration erasure is completed.
Default N/A
Usage The erasure of the startup-config occurs following the next reload or reboot. Until the
next reload or reboot, the ACOS device continues to run based on the running-config.
The management IP address is not erased. This is true even if you do not use the
preserve- management option. However, without this option, the default management
gateway is erased and reset to its factory default.
To recover the configuration, you can save the running-config or reload the configuration
from another copy of the startup-config file.
Example The following command erases the startup-config file. The change takes place following the
next reload or reboot.
ACOS(config)#erase
Example The following command erases the startup-config file, except for management interface
access and admin accounts, and reloads to place the change into effect.
event
Description Generate an event for the creation or deletion of an L3V partition.
Parameter Description
part-create Generate an event when a partition is created.
part-del Generate an event when a partition is deleted.
Default N/A
exit
Syntax exit
Default N/A
Usage The exit command is valid at all CLI levels. At each level, the command returns to the
previ- ous CLI level. For example, from the server port level, the command returns to the
server level. From the Configuration mode level, the command returns to the Privileged
EXEC level. From the user EXEC level, the command terminates the CLI session.
From the Configuration mode level, you also can use the end command to return to the
Privileged EXEC level.
Example The following command returns from the Configuration mode level to the Privileged
EXEC level:
ACOS(config)#exit
ACOS#
export-periodic
Syntax export-periodic
{
aflex file |
auth-portal file |
axdebug file |
bw-list file |
class-list file |
debug-monitor file |
dnssec-dnskey file |
dnssec-ds file |
geo-location file |
local-uri-file file |
policy file |
ssl-cert file |
ssl-cert-key bulk |
ssl-crl file |
ssl-key |
syslog file |
thales-secworld file [overwrite] |
wsdl file |
xml-schema file
}
[use-mgmt-port] url
period seconds
}
Parameter Description
aflex Export an aFleX file.
auth-portal Export an authentication portal file for Application Access Management (AAM).
axdebug Export an AX Debug packet file.
bw-list Export a black/white list.
class-list Export an IP class list.
dnssec-dnskey Export a DNSEC key-signing key (KSK) file.
dnssec-ds Export a DNSSEC DS file.
geo-location Export a geo-location data file for Global Server Load Balancing (GSLB).
local-uri-file Export a local URI file.
policy Export a WAF policy file.
ssl-cert Export a certificate.
ssl-cert-key Export a certificate and key together as a single file.
ssl-key Export a certificate key.
ssl-crl Export a certificate revocation list (CRL).
syslog Export a syslog file.
thales-secworld Export Thales security world files. Use the overwrite option to overwrite an existing file
with the same name.
wsdl Export a WSDL file.
xml-schema Export an XML schema file.
Parameter Description
use-mgmt-port Uses the management interface as the source interface for the connection to the remote
device. The management route table is used to reach the device. Without this option, the
ACOS device attempts to use the data route table to reach the remote device through a
data interface.
url Protocol, user name (if required), and directory path you want to use to send the file.
You can enter the entire URL on the command line or press Enter to display a prompt for
each part of the URL. If you enter the entire URL and a password is required, you will still be
prompted for the password. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
period seconds Enables automated updates of the file. You can specify 60 (one minute)-31536000 (one
year) seconds.
The period option simplifies update of imported files, especially files that are used by
mul- tiple ACOS devices. You can edit a single instance of the file, on the remote server,
then con- figure each of ACOS device to automatically update the file to import the latest
changes.
When you use this option, the ACOS device periodically replaces the specified file with the
version that is currently on the remote server. If the file is in use in the running-config, the
updated version of the file is placed into memory.
The updated file affects only new sessions that begin after the update but does not affect
existing sessions. For example, when an aFleX script that is bound to a virtual port is
updated, the update affects new sessions that begin after the update, but does not affect
existing sessions that began before the update.
Example The following command exports an aFleX policy onto the ACOS device from a TFTP
server, from its directory named “backups” every 30 days:
fail-safe
Description Configure fail-safe automatic recovery.
session-memory-recovery-threshold percentage |
sw-error-monitor-enable |
sw-error-recovery-timeout minutes |
total-memory-size-check Gb {kill | log}
}
Parameter Description
fpga-buff-recovery-threshold Minimum required number of free (available) FPGA buffers. If the
256-buffer-units num- ber of free buffers remains below this value until the recovery
timeout, fail-safe software recovery is triggered.
You can specify 1-10 units. Each unit contains 256 buffers.
The default is 2 units (512 buffers).
hw-error-monitor-disable Disables fail-safe monitoring and recovery for hardware errors.
This is enabled by default.
hw-error-monitor-enable Enables fail-safe monitoring and recovery for hardware errors.
This is enabled by default.
hw-error-recovery-timeout minutes Number of minutes fail-safe waits after a hardware error occurs to
reboot the ACOS device. You can specify 1-1440 minutes.
The default is 0 (not set).
session-memory-recovery-threshold Minimum required percentage of system memory that must be free. If
percentage the amount of free memory remains below this value long enough for
the recovery timeout to occur, fail-safe software recovery is triggered.
You can specify 1-100 percent. The default is 30 percent.
sw-error-monitor-enable Enables fail-safe monitoring and recovery for software errors.
This is disabled by default.
sw-error-recovery-timeout minutes Number of minutes (1-1440) the software error condition must remain
in effect before fail-safe occurs:
• If the system resource that is low becomes free again within the
recovery timeout period, fail-safe allows the ACOS device to
continue normal operation. Fail-safe recovery is not triggered.
• If the system resource does not become free, then fail-safe recovery
is triggered.
The default timeout is 3 minutes.
Default By default, fail-safe automatic recovery is enabled for hardware errors and disabled for
soft- ware errors. You can enable the feature for hardware errors, software errors, or both.
When
you enable the feature, the other options have the default values described in the table
above.
Usage Fail-safe hardware recovery also can be triggered by a “PCI not ready” condition. This fail-
safe recovery option is enabled by default and can not be disabled.
fw
Description Configuration commands for DC Firewall.
glid
Description Configure a global set of IP limiting rules for system-wide IP limiting.
NOTE: This command configures a limit ID (LID) for use with the IP limiting feature. To con-
figure a LID for use with Large-Scale NAT (LSN) instead, see the IPv4-to-IPv6
Transi- tion Solutions Guide.
This command changes the CLI to the configuration level for the specified global LID, where
the following command is available.
(The other commands are common to all CLI configuration levels. See “Config Commands:
Global” on page 61.)
Command Description
[no] conn-limit num Specifies the maximum number of concurrent connections allowed for a client. You
can specify 0-1048575. Connection limit 0 immediately locks down matching cli-
ents.
There is no default value set for this parameter.
[no] conn-rate-limit num Specifies the maximum number of new connections allowed for a client within the
per num-of-100ms specified limit period. You can specify 1-4294967295 connections. The limit period
can be 100-6553500 milliseconds (ms), specified in increments of 100 ms.
There is no default value set for this parameter.
[no] dns options Configure settings for IPv4 DNS features.
[no] dns64 options Configure settings for IPv6 DNS features.
Command Description
[no] over-limit- Specifies the action to take when a client exceeds one or more of the limits. The
action [forward | command also configures lockout and enables logging. Action can include:
reset] [lockout
• drop – The ACOS device drops that traffic. If logging is enabled, the ACOS
minutes] [log device also generates a log message. (There is no drop keyword; this is
minutes] default action.)
• forward – The ACOS device forwards the traffic. If logging is enabled, the
ACOS device also generates a log message.
• reset – For TCP, the ACOS device sends a TCP RST to the client. If logging
is enabled, the ACOS device also generates a log message.
The lockout option specifies the number of minutes during which to apply the
over-limit action after the client exceeds a limit. The lockout period is activated
when a client exceeds any limit. The lockout period can be 1-1023 minutes. There
is no default lockout period.
The log option generates log messages when clients exceed a limit. When you
enable logging, a separate message is generated for each over-limit occurrence,
by default. You can specify a logging period, in which case the ACOS device holds
onto the repeated messages for the specified period, then sends one message at
the end of the period for all instances that occurred within the period. The logging
period can be 0-255 minutes. The default is 0 (no wait period).
[no] request-limit num Specifies the maximum number of concurrent Layer 7 requests allowed for a client.
You can specify 1-1048575.
[no] request-rate-limit Specifies the maximum number of Layer 7 requests allowed for the client within
num per num-of-100ms the specified limit period. You can specify 1-4294967295 connections. The limit
period can be 100-6553500 milliseconds (ms), specified in increments of 100
ms.
[no] use-nat-pool Binds a NAT pool to the GLID. The pool is used to provide reverse NAT for class-list
pool-name members that are mapped to this GLID. (The use-nat-pool option, available in
GLIDs, is applicable only to transparent traffic, not to SLB traffic.)
Usage This command uses a single class list for IP limiting. To use multiple class lists for system-wide
IP limiting, use a policy template instead. See the “slb template policy” command in the Com-
mand Line Interface Reference for ADC.
A Global Limit ID (GLID) is an ID that identifies a set of limiting rules configured globally.
This ID is included in a class-list, as shown in the following example:
glid 10
request-limit 100
class-list HTTP-RL
10.100.0.0/16 lid 1
10.2.0.0/16 lid 2
0.0.0.0/0 glid 10
The limiting rules within a GLID can be reused in different class-list objects, unlike a Local
Limit ID (LID).
A LID is an ID that identifies a set of limiting rules configured inside an SLB template of a
certain type, such as an SLB policy template or an SLB DNS template, that support a class-
list. For example:
A local limit ID can be used if the same class-list is used for several different VIPs, and if
each VIP has different limiting rules; using the LID eliminates the need to create many
class-lists.
Note that GLIDs and LIDs are optional configurations within a class-list, and they are not
required if the class-list is used as a black-list or a white-list.
A policy template is also required if you plan to apply IP limiting rules to individual virtual
servers or virtual ports.
The use-nat-pool option is applicable only to transparent traffic, not to SLB traffic.
Example The following commands configure a global IP limiting rule to be applied to all IP clients
(the clients that match class list “global”):
ACOS(config)#glid 1
ACOS(config-glid:1)#conn-rate-limit 10000 per 1
ACOS(config-glid:1)#conn-limit 2000000
ACOS(config-glid:1)#over-limit forward logging
ACOS(config-glid:1)#exit
ACOS(config)#system glid 1
ACOS(config)#class-list global
ACOS(config-class list)#0.0.0.0/0 glid 1
glm
Default Disabled
The other glm commands are for internal use and testing purposes only.
gslb
Description Configure Global Server Load Balancing (GSLB) parameters. See the Global Server Load Bal-
ancing Guide.
hd-monitor enable
Description Enable hard disk monitoring on your ACOS device.
Example The example below shows how to enable hard disk monitoring.
ACOS(config)#hd-monitor enable
Harddisk monitoring turned on.
Please write mem and reload to take effect.
ACOS(config)#
health global
Description Globally change health monitor parameters.
This command changes the CLI to the configuration level for global health monitoring
parameters, where the following commands are available.
Parameter Description
[no] health check-rate threshold Change the health-check rate limiting threshold.
Replace threshold with the maximum number of health-check
pack- ets the ACOS device will send in a given 500-millisecond (ms)
period.
The valid range is 1-5000 health-check packets per 500-ms period.
When you disable auto-adjust mode, the default threshold is 1000
health-check packets per 500-ms period.
When auto-adjust mode is enabled, you can not manually change the
threshold. To change the threshold, you first must disable auto-adjust
mode. (See below.)
[no] health disable-auto-adjust Disable the auto-adjust mode of health-check rate limiting.
When necessary, the auto-adjust mode dynamically increases the
default interval and timeout for health checks. By increasing these
timers, health- check rate limiting provides more time for health-check
processing.
Auto-adjust mode is enabled by default.
[no] health external-rate scripts Specify the maximum number of external health-checks scripts the
per 100-ms-units ACOS device is allowed to perform during a given interval.
• scripts – Maximum number of external health-check scripts, 1-999.
• 100-ms-units – Interval to which the scripts option applies, 1-
20 100-ms units.
The default rate is 2 scripts every 200 ms.
interval seconds Number of seconds between health check attempt, 1-180 seconds. A
health check attempt consists of the ACOS device sending a packet to
the server. The packet type and payload depend on the health monitor
type. For example, an HTTP health monitor might send an HTTP GET
request packet. Default is 5 seconds.
multi-process cpus Enable use of multiple CPUs for processing health checks.
Replace cpus with the total number of CPUs to use for processing
health checks.
The default is 1.
retry number Maximum number of times ACOS will send the same health check to an
unresponsive server before determining that the server is down. You
can specify 1-5. Default is 3.
timeout seconds Number of seconds ACOS waits for a reply to a health check, 1-12 sec-
onds. Default is 5 seconds.
up-retry number Number of consecutive times the device must pass the same periodic
health check, in order to be marked Up. You can specify 1-10. The
default is 1.
You can change one or more parameters on the same command line.
NOTE: To change a global parameter back to its factory default, use the “no” form of the
command (for example: no up-retry 10).
Usage Globally changing a health monitor parameter changes the default for that parameter. For
example, if you globally change the interval from 5 seconds to 10 seconds, the default
inter- val becomes 10 seconds.
If a parameter is explicitly set on a health monitor, globally changing the parameter does
not affect the health monitor. For example, if the interval on health monitor hm1 is explicitly
set to 20 seconds, the interval remains 20 seconds on hm1 regardless of the global setting.
NOTE: Global health monitor parameter changes automatically apply to all new health
monitors configured after the change. To apply a global health monitor
parameter change to health monitors that were configured before the change,
you must reboot the ACOS device.
Example The following command globally changes the default number of retries to 5:
Example The following command globally changes the timeout to 10 seconds and default number of
retries to 4:
health monitor
Description Configure a health monitor.
The monitor-name can be 1-29 characters. This command changes the CLI
to the configuration level for the health monitor.
Default See the “Health Monitoring” chapter in the Application Delivery and Server Load
Balancing Guide for information on the defaults.
Usage For information about the commands available at the health-monitor configuration
level, see “Config Commands: Health Monitors” on page 547.
health-test
Description Test the status of a device at a specified IP address using a defined health monitor.
Parameter Description
ipaddr IPv4 or IPv6 address of the device you want to test.
count num Wait for count tests (1-65535).
The default count is 1.
monitorname name Specify the pre-configured health monitor to use for the test.
port portnum Specify the port to test.
hostname
Description Set the ACOS device’s hostname.
Replace string with the desired hostname (1-31 characters). The name can contain
any alpha-numeric character (a-z, A-Z, 0-9), hypen (-), period (.), or left or right
parentheses characters.
Default The default hostname is the name of the device; for example, an AX Series 5630 device
will have “AX5630” as the default hostname.
Usage The CLI command prompt also is changed to show the new hostname.
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
hsm template
Description Configure a template for DNSSEC Hardware Security Module (HSM) support.
This command changes the CLI to the configuration level for the specified template, where
the following command is available:
password hsm-passphrase
(The other commands are common to all CLI configuration levels. See “Config Commands:
Global” on page 61.)
icmp-rate-limit
Description Configure ICMP rate limiting, to protect against denial-of-service (DoS) attacks.
Parameter Description
normal-rate Maximum number of ICMP packets allowed per second. If the ACOS device receives more
than the normal rate of ICMP packets, the excess packets are dropped until the next one-sec-
ond interval begins. The normal rate can be 1-65535 packets per second.
lockup max-rate Maximum number of ICMP packets allowed per second before the ACOS device locks up
ICMP traffic. When ICMP traffic is locked up, all ICMP packets are dropped until the lockup
expires. The maximum rate can be 1-65535 packets per second. The maximum rate must be
larger than the normal rate.
lockup-time Number of seconds for which the ACOS device drops all ICMP traffic, after the maximum rate
is exceeded. The lockup time can be 1-16383 seconds.
Default None
Usage This command configures ICMP rate limiting globally for all traffic to or through the
ACOS device. To configure ICMP rate limiting on individual Ethernet interfaces, see the
icmp-
Specifying a maximum rate (lockup rate) and lockup time is optional. If you do not specify
them, lockup does not occur.
Log messages are generated only if the lockup option is used and lockup occurs.
Otherwise, the ICMP rate-limiting counters are still incremented but log messages are not
generated.
Example The following command globally configures ICMP rate limiting to allow up to 2048 ICMP
packets per second, and to lock up all ICMP traffic for 10 seconds if the rate exceeds
3000 ICMP packets per second:
icmpv6-rate-limit
Description Configure ICMPv6 rate limiting for IPv6 to protect against denial-of-service (DoS) attacks.
Parameter Description
normal-rate Maximum number of ICMPv6 packets allowed per second. If the ACOS device receives
more than the normal rate of ICMPv6 packets, the excess packets are dropped until the
next one- second interval begins. The normal rate can be 1-65535 packets per second.
lockup max-rate Maximum number of ICMPv6 packets allowed per second before the ACOS device locks up
ICMPv6 traffic. When ICMPv6 traffic is locked up, all ICMPv6 packets are dropped until the
lockup expires. The maximum rate can be 1-65535 packets per second. The maximum rate
must be larger than the normal rate.
lockup-time Number of seconds for which the ACOS device drops all ICMPv6 traffic, after the maximum
rate is exceeded. The lockup time can be 1-16383 seconds.
Default None
Usage This command configures ICMPv6 rate limiting globally for all traffic to or through the ACOS
device. To configure ICMPv6 rate limiting on individual Ethernet interfaces, see the
icmpv6- rate-limit command in the “Config Commands: Interface” chapter in the
Network Config- uration Guide. To configure it in a virtual server template, see “slb
template virtual-server” on page 259. If you configure ICMPv6 rate limiting filters at more
than one of these levels, all fil- ters are applicable.
Specifying a maximum rate (lockup rate) and lockup time is optional. If you do not specify
them, lockup does not occur.
Log messages are generated only if the lockup option is used and lockup occurs. Otherwise,
the ICMPv6 rate-limiting counters are still incremented but log messages are not generated.
import
Description See “import” on page 46.
import-periodic
Description Get files from a remote site periodically.
Syntax import-periodic
{
{
aflex file |
auth-portal file |
bw-list file |
class-list file |
class-list-convert file class-list-type type |
dnssec-dnskey file |
dnssec-ds file |
geo-location file |
license file |
local-uri-file file |
policy file |
{
ssl-cert file
{[certificate-type {pem | der | pfx pfx-password pswd | p7b}]
[csr-generate]
} |
ssl-cert-key bulk |
ssl-crl file [csr-generate] |
ssl-key file [csr-generate] |
thales-kmdata file [overwrite] |
thales-secworld file [overwrite] |
wsdl file |
xml-schema file
}
{[use-mgmt-port] url}
period seconds
}
Parameter Description
aflex Import an aFleX file.
auth-portal Import an authentication portal file for Application Access Management (AAM).
bw-list Import a black/white list.
class-list Import an IP class list.
class-list-convert ACOS imports a newline delimited text file and converts it to a class-list file of the type spec-
file class-list- ified a filetype keyword:
type {ac | string
• ac - Aho-Corasick class list.
|ipv4 | ipv6 |
string-case-inten-
See the “How to Convert Your SNI List to an A10 Class List” section in the SSL Insight book
for an example of converting to an A10 Aho-Corasick class list.
sive}
• string
• ipv4
• ipv6
• string-case-insensitive
NOTE: Only the Aho-Corasick class list is compliant with the class list types created
through the class-list command.
Parameter Description
dnssec-ds Import a DNSSEC DS file.
geo-location Imports a geo-location data file for Global Server Load Balancing (GSLB).
license Import a license file, if applicable to your model.
local-uri-file Import a local URI file.
policy Import a WAF policy file.
ssl-cert [bulk] Imports a certificate.
• Use the bulk option to import multiple files simultaneously as a .tgz archive.
• Use certificate-type to specify a certificate type.
• Use csr-generate to generate a CSR file.
ssl-cert-key [bulk] Imports a certificate and key together as a single file.
Specify bulk to import multiple files simultaneously as a .tgz archive
ssl-key [bulk] Import a certificate key.
Specify bulk to import multiple files simultaneously as a .tgz archive
ssl-crl Import a certificate revocation list (CRL).
wsdl Import a WSDL file.
xml-schema Import an XML schema file.
use-mgmt-port Uses the management interface as the source interface for the connection to the remote
device. The management route table is used to reach the device. Without this option, the
ACOS device attempts to use the data route table to reach the remote device through a
data interface.
Parameter Description
url Protocol, user name (if required), and directory path you want to use to send the file.
You can enter the entire URL on the command line or press Enter to display a prompt for
each part of the URL. If you enter the entire URL and a password is required, you will still be
prompted for the password. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
period seconds Enables automated updates of the file. You can specify 60 (one minute)-31536000 (one
year) seconds.
The period option simplifies update of imported files, especially files that are used by
mul- tiple ACOS devices. You can edit a single instance of the file, on the remote server,
then con- figure each of ACOS device to automatically update the file to import the latest
changes.
When you use this option, the ACOS device periodically replaces the specified file with the
version that is currently on the remote server. If the file is in use in the running-config, the
updated version of the file is placed into memory.
The updated file affects only new sessions that begin after the update but does not affect
existing sessions. For example, when an aFleX script that is bound to a virtual port is
updated, the update affects new sessions that begin after the update, but does not affect
existing sessions that began before the update.
Example The following command imports an aFleX policy onto the ACOS device from a TFTP
server, from its directory named “backups” every 30 days:
interface
Description Access the CLI configuration level for an interface.
Syntax interface {
ethernet port-num |
lif logical-interface-id |
loopback num |
management |
trunk num |
tunnel num |
ve ve-num
}
Default N/A
Usage If the ACOS device is a member of an aVCS virtual chassis, specify the interface number as
follows: DeviceID/Portnum
For information about the commands available at the interface configuration level, see
“Config Commands: Interface” in the Network Configuration Guide.
Example The following command changes the CLI to the configuration level for Ethernet interface 3:
ACOS(config)#interface ethernet 3
ACOS(config-if:ethernet:3)#
ip
Description Configure global IP settings. For information, see “Config Commands: IP” in the Network Con-
figuration Guide.
ip-list
Description Create a list of IP addresses with group IDs to be used by other GSLB commands.
For example, you can create an IP list and use it in a GSLB policy.
information.
After entering this command, you are placed in a sub-configuration mode where you can
enter the IP addresses as follows:
Example The following example shows how to use the ip-list command to create a list of IPv4
addresses from 10.10.10.1 to 10.10.10.44:
ACOS(config)#ip-list ipv4-list
ACOS(config-ip-list)#10.10.10.1 to 10.10.10.44
ipv6
Description Configure global IPv6 settings. For information, see “Config Commands: IPv6” in the Network
Configuration Guide.
key
Description Configure a key chain for use by RIP or IS-IS MD5 authentication.
Replace name with the name of the key chain (1-31 characters).
This command changes the CLI to the configuration level for the specified key chain,
where the following key-chain related command is available:
This command adds a key and enters configuration mode for the key. The key number can
be 1-255. This command changes the CLI to the configuration level for the specified key,
where the following key-related command is available:
This command configures the authentication string of the key, 1-16 characters.
Usage Although you can configure multiple key chains, it is recommends using one key chain per
interface, per routing protocol.
l3-vlan-fwd-disable
Description Globally disable Layer 3 forwarding between VLANs.
Default By default, the ACOS device can forward Layer 3 traffic between VLANs.
Usage This command is applicable only on ACOS devices deployed in gateway (route) mode. If
the option to disable Layer 3 forwarding between VLANs is configured at any level, the
ACOS device can not be changed from gateway mode to transparent mode, until the
option is removed.
Depending on the granularity of control required for your deployment, you can disable
Layer 3 forwarding between VLANs at any of the following configuration levels:
• Global – Layer 3 forwarding between VLANs is disabled globally, for all VLANs, on
ACOS devices deployed in gateway mode. (Use this command at the Configuration
mode level.)
• Individual interfaces – Layer 3 forwarding between VLANs is disabled for incoming traf-
fic on specific interfaces. (See the “l3-vlan-fwd-disable” command in the Network Con-
figuration Guide.)
• Access Control Lists (ACLs) – Layer 3 forwarding between VLANs is disabled for all traffic
that matches ACL rules that use the l3-vlan-fwd-disable action. (See “access-
list (standard)” on page 68 or “access-list (extended)” on page 70.)
To display statistics for this option, see “show slb switch” on page 427.
lacp system-priority
Description Set the Link Aggregation Control Protocol (LACP) priority.
Replace num with the LACP system priority, 1-65535. A low priority number indicates a high
priority value. The highest priority is 1 and the lowest priority is 65535.
Default 32768
Usage In cases where LACP settings on the local device (the ACOS device) and the remote
device at the other end of the link differ, the settings on the device with the higher priority
are used.
lacp-passthrough
Description Specify peer ports to which received LACP packets can be forwarded.
Parameter Description
fwd-port Peer member that will forward LACP packets.
rcv-port Peer member that will receive the forwarded LACP packets.
ldap-server
Description Set Lightweight Directory Access Protocol (LDAP) parameters for authenticating
administra- tive access to the ACOS device.
Parameter Description
hostname Host name of the LDAP server.
ipaddr IP address of the LDAP Server.
cn-name Value for the Common Name (CN) attribute.
dn-name Value for the Distinguished Name (DN) attribute.
The DN attribute does not support spaces or quotation marks. For
example, the following DN string syntax is valid:
cn=xxx3,dc=maxcrc,dc=com
The following string is not valid because of the quotation marks and
space character:
“cn=xxx3,dc=max crc,dc=com”
domain-name Active Directory domain name.
base-domain Base domain to which the user belongs.
group-id Group ID to which the user belongs.
portnum Protocol port on which the server listens for LDAP traffic.
The default is 389.
seconds Maximum number of seconds the ACOS device waits for a reply
from the LDAP server for a given request (1-60 seconds). If the
LDAP server does not reply before the timeout, authentication of the
admin fails.
The default is 44 seconds.
ssl Authenticate using SSL.
Default No LDAP servers are configured by default. When you add an LDAP server, it has the
default settings described in the table above.
Usage LDAP is a AAA protocol that the ACOS device can use to authenticate admins and
authorize their management access based on admin account information on external
LDAP servers.
• OpenLDAP
• Microsoft Active Directory (AD)
To enable LDAP authentication, use the following command at the global configuration level
of the CLI:
To use backup methods, specify them in the order you want to use them.
Nested OUs
To use nested OUs, specify the nested OU first, then the root. For example, a user account
could be nested as follows:
To configure the ACOS device to provide LDAP AAA for “UserAccUser1”, use a command
such as the following:
Example The following commands enable LDAP authentication and add LDAP server 192.168.101.24:
link
Description Link the “startup-config” token to the specified configuration profile. By default, “startup-
con- fig” is linked to “default”, which means the configuration profile stored in the image
area from which the ACOS device most recently rebooted.
Parameter Description
default Links “startup-config” to the configuration profile stored in the
image area from which the ACOS device was most recently
rebooted.
profile-name Links “startup-config” to the specified configuration profile.
primary | second- Specifies the image area. If you omit this option, the image
ary area last used to boot is selected.
Default The “startup-config” token is linked to the configuration profile stored in the image area
from which the ACOS device was most recently rebooted.
Usage This command enables you to easily test new configurations without replacing the
configu- ration stored in the image area.
The profile you link to must be stored on the boot device you select. For example, if you use
the default boot device (hard disk) selection, the profile you link to must be stored on the
hard disk. If you specify cf, the profile must be stored on the compact flash. (To display the
profiles stored on the boot devices, use the show startup-config all command.
See “show startup-config” on page 347.)
Likewise, the next time the ACOS device is rebooted, the linked configuration profile is
loaded instead of the configuration that is in the image area.
To relink “startup-config” to the configuration profile stored in the image area, use the default
option (link startup-config default).
Example The following command links configuration profile “slbconfig3” with “startup-config”:
Example The following command relinks “startup-config” to the configuration profile stored in
the image area from which the ACOS device was most recently rebooted”:
lldp enable
Description Use this command to enable or disable LLDP from the global level. You can enable LLDP
to either receive only, transmit only, or transmit and receive.
no lldp enable
Example To enable LLDP transmission and receipt from the global level, issue the following
com- mand:
lldp management-address
Description Configures the management-address that can include the following information:
• DNS name
• IPv4 address
• IPv6 address
Optionally, you can specify the interface on which the management address is configured.
The management interface can be either a physical Ethernet interface or a virtual
interface (VE).
Default 30
lldp system-description
Description Defines the alpha-numeric string that describes the system in the network.
Default None
lldp system-name
Description Defines the string that will be assigned as the system name.
Default hostname
Example The following command will set the LLDP system name to “testsystem”:
lldp tx fast-count
Description This value is used as the initial value for the Fast transmission variable. This value
determines the number of LLDP data packets that are transmitted during a fast
transmission period. This value can range from 1-8 seconds.
Default 4
Example The following command will set the LLDP fast count transmission value to 3 seconds:
lldp tx fast-interval
Description This variable defines the time interval in timer ticks between transmissions during fast
trans- mission periods (that is, txFast is non-zero). The range for this variable is 1-3600
seconds.
Default 1 second
Example The following command will set the LLDP fast transmission interval value to 2000 seconds:
lldp tx interval
Description Defines the transmission (tx) interval between a normal transmission period.
Default 30 seconds
Example The following command will set the transmission interval to 200:
lldp tx hold
Description Determines the value of the message transmission time to live (TTL) interval that is carried
in LLDP frames. The hold-value can be from 1 to 100 seconds.
Example The following command will set the transmission hold time to 255:
lldp tx reinit-delay
Description Indicates the delay interval when the administrative status indicates ‘disabled’ after which
re- initialization is attempted. The range for the
reinit-delay-value is 1-5 seconds.
Default 2 seconds
Example The following command will set the retransmission delay to 3 seconds:
locale
Description Set the CLI locale.
Default en_US.UTF-8
Usage Use this command to configure the locale or to test the supported locales.
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
Example The following commands test the Chinese locales and set the locale to zh_CN.GB2312:
Parameter Description
ipaddr IP address of the remote server.
hostname Host name of the remote server.
facility-name Name of a log facility:
• local0
• local1
• local2
• local3
• local4
• local5
• local6
• local7
There is no default.
Default N/A
Usage The audit log is automatically included in system log backups. You do not need this
com- mand in order to back up audit logs that are within the system log. To back up
the system log, see “backup system” on page 38 and “backup log” on page 36.
In the current release, only a single log server is supported for remote audit logging.
logging buffered
Description Configure the event log on the ACOS device.
Parameter Description
max-messages Specifies the maximum number of messages the event log buffer will hold. The default buffer
size (maximum messages) is 30000.
disable Disable logging to the monitor.
emergency Send emergency events (severity level 0—system unusable) to the monitor.
alert Send alert events (severity level 1—take action immediately) to the monitor.
critical Send critical events (severity level 2—system is in critical condition) to the monitor.
error Send error events (severity level 3—system has an error condition) to the monitor.
warning Send warning events (severity level 4—system has warning conditions) to the monitor.
notification Send notifications (severity level 5—normal but significant conditions) to the monitor.
information Send informational messages (severity level 6) to the monitor.
debugging Send debug level messages (severity level 7) to the monitor.
Example The following command sets the severity level for log messages to 7 (debugging):
logging console
Description Set the logging level for messages sent to the console.
Parameter Description
disable Disable logging to the console.
emergency Send emergency events (severity level 0—system unusable) to the console.
alert Send alert events (severity level 1—take action immediately) to the console.
critical Send critical events (severity level 2—system is in critical condition) to the console.
error Send error events (severity level 3—system has an error condition) to the console.
warning Send warning events (severity level 4—system has warning conditions) to the console.
notification Send notifications (severity level 5—normal but significant conditions) to the console.
information Send informational messages (severity level 6) to the console.
debugging Send debug level messages (severity level 7) to the console.
logging disable-partition-name
Description Disable display of L3V partition names in log messages.
Usage When this option is enabled partition names are included in log messages as the following
example illustrates.
Jan 24 2014 15:30:21 Info [HMON]:<partition_1> SLB server rs1 (4.4.4.4) is down
Jan 24 2014 15:30:19 Info [HMON]:<partition_1> SLB server rs1 (4.4.4.4) is
up Jan 24 2014 15:30:17 Info [ACOS]:<partition_1> Server rs1 is created
Parameter Description
num Specifies the maximum number of messages to buffer (16-256).
The default number is 50 messages.
minutes Specifies how long to wait before sending all buffered messages, if the
buffer contains fewer than the maximum allowed number of messages.
You can specify 10-1440 minutes.
The default time is 10 minutes.
Default By default, emailing of log messages is disabled. When you enable the feature, the
buffer options have the default values described in the table above.
Usage To configure the ACOS device to send log messages by email, you also must configure an
email filter and specify the email address to which to email the log messages. See “logging
email filter” on page 148 and “logging email-address” on page 151.
Example The following command configures the ACOS device to buffer log messages to be
emailed. Messages will be emailed only when the buffer reaches 32 messages, or 30
minutes passes since the previous log message email, whichever happens first.
Parameter Description
filter-num Specify the filter number (1-8).
conditions Message attributes on which to match. The conditions list can contain one or more of the
following:
• Severity levels of messages to send in email. Specify the severity levels by number or word:
• 0 - emergency
• 1 - alert
• 2 - critical
• 3 - error
• 4 - warning
• 5 - notification
• 6 - information
• 7 - debugging
• Software modules for which to email messages. Messages are emailed only if they come from
one of the specified software modules. For a list of module names, enter ? instead of a module
name, and press Enter.
• Regular expression. Standard regular expression syntax is supported. Only messages that meet
the criteria of the regular expression will be emailed. The regular expression can be a simple text
string or a more complex expression using standard regular expression logic.
operators Set of Boolean operators (AND, OR, NOT) that specify how the conditions should be compared.
The CLI Boolean expression syntax is based on Reverse Polish Notation (also called Postfix Notation), a
notation method that places an operator (AND, OR, NOT) after all of its operands (in this case, the con-
ditions list).
After listing all the conditions, specify the Boolean operator(s). The following operators are supported:
• AND – All conditions must match in order for a log message to be emailed.
• OR – Any one or more of the conditions must match in order for a log message to be emailed.
• NOT – A log message is emailed only if it does not match the
conditions For more information about Reverse Polish Notation, see:
http://en.wikipedia.org/wiki/Reverse_Polish_notation
trigger Immediately sends the matching messages in an email instead of buffering them. If you omit this
option, the messages are buffered based on the logging email buffer settings.
Usage To configure the ACOS device to send log messages by email, you also must specify the
email address to which to email the log messages. See “logging email-address” on page
151.
• You can configure up to 8 filters. The filters are used in numerical order, starting with
fil- ter 1. When a message matches a filter, the message will be emailed based on the
buf- fer settings. No additional filters are used to examine the message.
The severity-level can be one or more of the following (specify either the severity
number o r name):
• 0 - emergency
• 1 - alert
• 2 - critical
• 5 - notification
The command is treated as a special filter. This filter is placed into effect only if the
com- mand syntax shown above is in the configuration. The filter has an implicit trigger
option for emergency, alert, and critical messages, to emulate the behavior in previous
releases.
Example The following command configures a filter that matches on log messages if they are infor-
mation-level messages and contain the string “abc”. The trigger option is not used,
so the messages will be buffered rather than emailed immediately.
The following command reconfigures the filter to immediately email matching messages.
Example The following example configures a filter to send email if the log message is generated
by the “AFLEX” module and the severity level is “warning”:
Example The following example configures a filter to send email if the log message has the pattern
of “disk is full” or the severity level is “critical”:
Example The following example configures a filter to send email if the log message is generated
by (module “SYSTEM” or “ALB”) and (the severity level is “alert” or has pattern of
“unexpected error”)
ACOS(config)#logging email filter 3 “module SYSTEM module ALB or level alert pattern unex-
pected error or and”
logging email-address
Description Specify the email addresses to which to send event messages.
Parameter Description
address Email address to which event message will be sent.
To specify multiple Email addresses, use the logging email-
address command once for each address.
Default None
Usage To configure the ACOS device to send log messages by email, you also must configure
an email filter. See “logging email filter” on page 148.
Example The following command sets two email addresses to which to send log messages:
logging export
Description Send the messages that are in the event buffer to an external file server.
Parameter Description
all Include system support messages.
use-mgmt-port Use the management interface as the source interface for the connection to the remote
device. The management route table is used to reach the device. Without this option, the
ACOS device attempts to use the data route table to reach the remote device through a data
interface.
url Saves a backup of the log to a remote server.
You can enter the entire URL on the command line or press Enter to display a prompt for each
part of the URL. If you enter the entire URL and a password is required, you will still be
prompted for the password. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
Example The following example sends the event buffer to an external file server using FTP. The
file “event-buffer-messages.txt” will be created on the remote server.
logging facility
Description Enable logging facilities.
Parameter Description
facility-name Name of a log facility:
• local0
• local1
• local2
• local3
• local4
• local5
• local6
• local7
logging host
Description Specify a Syslog server to which to send event messages.
Parameter Description
ipaddr IP address of the Syslog server.
protocol-port Protocol port number to which to send messages (1-32767).
tcp Use TCP as the transport protocol.
use-mgmt-port Establish the connection to the Syslog server using the management port.
Usage Multiple log servers can be created by using the logging host command once for
each server. If you use the command with the same IP address as an existing logging
server, it replaces any existing configuration for that existing server.
Example The following command configures two external log servers. In this example, both
servers use the default syslog protocol port, 514, to listen for log messages.
logging monitor
Description Set the logging level for messages sent to the terminal monitor.
Parameter Description
disable Disable logging to the monitor.
emergency Send emergency events (severity level 0—system unusable) to the monitor.
alert Send alert events (severity level 1—take action immediately) to the monitor.
critical Send critical events (severity level 2—system is in critical condition) to the monitor.
error Send error events (severity level 3—system has an error condition) to the monitor.
warning Send warning events (severity level 4—system has warning conditions) to the monitor.
notification Send notifications (severity level 5—normal but significant conditions) to the monitor.
information Send informational messages (severity level 6) to the monitor.
debugging Send debug level messages (severity level 7) to the monitor.
logging single-priority
Description Configure single-priority logging to log one specific severity level from among the
standard syslog message severity levels.
Parameter Description
emergency Log emergency events (severity level 0—system unusable) only.
alert Log alert events (severity level 1—take action immediately) only.
critical Log critical events (severity level 2—system is in critical condition) only.
error Log error events (severity level 3—system has an error condition) only.
warning Log warning events (severity level 4—system has warning conditions) only.
notification Log notifications (severity level 5—normal but significant conditions) only.
information Log informational messages (severity level 6) only.
debugging Log debug level messages (severity level 7) only.
logging syslog
Description Set the syslog logging level for events sent to the syslog host.
Parameter Description
disable Disable logging of syslog events.
emergency Send emergency events (severity level 0—system unusable) to the syslog host.
alert Send alert events (severity level 1—take action immediately) to the syslog host.
critical Send critical events (severity level 2—system is in critical condition) to the syslog host.
error Send error events (severity level 3—system has an error condition) to the syslog host.
warning Send warning events (severity level 4—system has warning conditions) to the syslog host.
notification Send notifications (severity level 5—normal but significant conditions) to the syslog host.
information Send informational messages (severity level 6) to the syslog host.
debugging Send debug level messages (severity level 7) to the syslog host.
logging trap
Description Set the logging level for traps sent to the SNMP host.
Parameter Description
disable Disable logging of SNMP traps.
emergency Sent emergency events (severity level 0—system unusable) to the SNMP host.
alert Send alert events (severity level 1—take action immediately) to the SNMP host.
critical Send critical events (severity level 2—system is in critical condition) to the SNMP host.
mac-address
Description Configure a static MAC address.
Parameter Description
mac-address Hardware address, in the following format:
aabb.ccdd.eeff
port port-num ACOS Ethernet port to which to assign the MAC address.
If the ACOS device is a member of an aVCS virtual chassis, specify
the interface as follows:
DeviceID/Portnum
vlan vlan-id Layer 2 broadcast domain in which to place the device.
trap Send packets to the CPU for processing, instead of switching them
in hardware.:
• source – Send packets that have this MAC as a source address
to the CPU.
• dest – Send packets that have this MAC as a destination
address to the CPU.
• both – Send packets that have this MAC as either a
source or destination address to the CPU.
NOTE: The trap option is supported on only some AX models: AX 3200-12, AX 3400,
AX 5200-11 and AX 5630.
Example The following command configures static MAC address abab.cdcd.efef on port 5 in VLAN 3:
mac-age-time
Description Set the aging time for dynamic (learned) MAC entries. An entry that remains unused for
the duration of the aging time is removed from the MAC table.
Replace seconds with the number of seconds a learned MAC entry can remain unused
before it is removed from the MAC table (10-600).
On some AX models, the actual MAC aging time can be up to 2 times the configured value.
For example, if the aging time is set to 50 seconds, the actual aging time will be between
50 and 100 seconds. (This applies to the AX 3200-12, AX 3400, AX 5200-11 and AX
5630.)
On other models, the actual MAC aging time can be +/- 10 seconds from the configured
value.
Example The following command changes the MAC aging time to 600 seconds:
ACOS(config)#mac-age-time 600
maximum-paths
Description Change the maximum number of paths a route can have in the forwarding Information
Base (FIB).
Replace num for the maximum number of paths a route can have. You can specify 1-64.
Default 10
merge-mode-add
Description Use this command to enter “merge” mode and integrate new configurations into the
current running configuration. This is a setting of the “block-merge” command in which
any child instances of the old configuration are retained if not present in the new
configuration.
Parameter Description
server Controls block-merge behavior for slb server.
service- Controls block-merge behavior for slb service-group.
group
virtual- Controls block-merge behavior for slb virtual-server.
server
Default N/A
mirror-port
Description Specify a port to receive copies of another port’s traffic.
For more information about mirror port configuration, see “Multiple Port-Monitoring Mirror
Ports” in the System Configuration and Administration Guide.
Parameter Description
mirror-port Mirror port index number.
portnum
ethernet Ethernet port number. This is the port that will act as the mirror
portnum port. Mirrored traffic from the monitored port will be copied to and
sent out of this port.
input Configures the mirror port so that only inbound traffic from the moni-
tored port can be sent out of the mirror port.
output Configures the mirror port so that only outbound traffic from the
monitored port can be sent out of the mirror port.
both Configures the mirror port so that both inbound and outbound traffic
from the monitored port can be sent out of the mirror port.
This is the default behavior, meaning that if no traffic direction is
spec- ified, then both inbound and outbound traffic will be mirrored
with- out having to explicitly specify the both option.
Usage When enabling monitoring on a port, you can specify the mirror port to use. You also can
specify the traffic direction. A monitored port can use multiple mirror ports.
To specify the port to monitor, use the monitor command at the interface configuration
level. (See the “monitor” command in the Network Configuration Guide.)
Example The following command configures Ethernet port 4 so that it is able to send both inbound
and outbound traffic from the monitored port:
The following commands configure a monitor port, Ethernet port 8, to use Ethernet port 4
as the mirror port, using mirror index 1 from above:
ACOS(config)#inferface ethernet 8
ACOS(config-if:ethernet:8)#monitor 1 both
Example The following command configures Ethernet port 3 to send only inbound traffic from the
monitored port:
The following commands configure a monitor port, Ethernet port 6, to use Ethernet port 3
as the mirror port, using mirror index 2 from above. Note that the input parameter
must be used on the monitor port since the mirror port was also configured with the
input parameter:
ACOS(config)#inferface ethernet 6
ACOS(config-if:ethernet:6)#monitor 2 input
monitor
Description Specify event thresholds for utilization of resources.
Parameter Description
resource-type Type of resource for which to set the monitoring threshold:
• buffer-drop – Packet drops (dropped IO buffers)
• buffer-usage – Control buffer utilization
The conn-type resources configure the conn resource
type thresholds per CPU:
• conn-type0 – 32 bytes
• conn-type1 – 64 bytes
• conn-type2 – 128 bytes
• conn-type3 – 256 bytes
• conn-type4 – 512 bytes
• ctrl-cpu – Control CPU utilization
• data-cpu – Data CPUs utilization
• disk – Hard disk utilization
• memory – Memory utilization
The smp-type resources configure the Threshold for SMP
resources for the global session memory pool, shared across all
of the ACOS device’s CPUs:
• smp-type0 – 32 bytes
• smp-type1 – 64 bytes
• smp-type2 – 128 bytes
• smp-type3 – 256 bytes
• smp-type4 – 512 bytes
• warn-temp – CPU temperature
threshold-value The values you can specify depend on the event type and
on the ACOS device model. For information, see the CLI
help.
Default The default threshold values depend on the event type and on the ACOS model. For
infor- mation, see the CLI help.
Usage If utilization of a system resource crosses the configured threshold, a log message is
gener- ated. If applicable, an SNMP trap is also generated.
To display the configured event thresholds, see “show monitor” on page 323.
Example The following command sets the event threshold for data CPU utilization to 80%:
ACOS(config)#monitor data-cpu 80
multi-config
Description Enable simultaneous admin sessions.
Default Enabled
Mode Config
Usage Use the “no” form of the command to disable multiple admin access.
NOTE: Disabling multiple admin access does not terminate currently active admin ses-
sions. For example, if there are 4 active config sessions, disabling multi-user
access will cause the display of a permission prompt when a 5th user attempts to
log onto the device. However, the previous 4 admin sessions will continue to run
unaffected.
multi-ctrl-cpu
Description Enable use of more than one CPU for control processing.
Replace num with the number of CPUs to use for control processing. Up to one fourth of the
device’s CPUs can be used for control processing.
To display the number of CPUs your device has, enter the show hardware command.
This command is required if you plan to enable use of multiple CPUs for health-check
processing.
NOTE: There is no “no” form of this command. To disable multiple CPUs for control pro-
cessing and restore it back to default, simply configure multi-ctrl-cpu 1.
Example The following commands display the number of CPUs (cores) the device being
managed contains, and enable use of multiple CPUs for control processing.
The first attempt does not succeed because the number of CPUs requested (3) was more
than the number available for control processing on this device.
ACOS(config)# multi-ctrl-cpu 3
The number of control CPUs should be less than a quarter of the total number of CPUs
The next attempt succeeds. The number of CPUs requested (2) is one-fourth of the total
number of CPUs on the device, which is the maximum that can be allocated to control
processing.
ACOS(config)# multi-ctrl-cpu 2
This will modify your boot profile for multiple control CPUs.
It will take effect after the next reboot.
Please confirm: You want to configure multiple control CPUs (N/Y)?:Y
...
After the system is rebooted, the show running-config indicates that multiple CPUs are
being utilized:
The output of the show version command also contains information when multiple
CPUs are being utilized:
64- bit Advanced Core OS (ACOS) version 2.7.2-P5, build 129 (May-27-
2015,06:52) Booted from Hard Disk primary image
Replace queue-time-multiplier with the multiplier for the maximum queue time.
Multiply this value by 20 to calculate the maximum number of milliseconds (ms) ACOS will
hold a NetFlow packet in the queue before sending it. The multiplier can be 0-50. For
example, to specify a half-second maximum queue time, set the multiplier to 25. Likewise, to
specify a 1-second queue time, set the multiplier to 50.
Setting the multiplier to 0 means that there will be no delay for NetFlow packets to be
sent to the NetFlow collector, and NetFlow records will not be buffered.
netflow monitor
Description Enable ACOS to act as a NetFlow exporter, for monitoring traffic and exporting the data
to one or more NetFlow collectors for analysis.
This command changes the CLI to the configuration level for the specified NetFlow monitor,
where the following commands are available.
Command Description
[no] destination Configure the destination where NetFlow records will be sent.
ipaddr [portnum]
disable Disable this NetFlow monitor.
Command Description
[no] flow-timeout Timeout value interval at which flow records will be periodically exported for long-
lived sessions. Flow records for short-lived sessions (if any) are sent upon
termination of the session.
After the specified amount of time has elapsed, the ACOS device will send any
flow records to the NetFlow collector, even if the flow is still active. The flow
timeout can be set to 0-1440 minutes. The flow timeout default value is 10
minutes.
Setting the timeout value to 0 disables the flow timeout feature. Regardless of how
long-lived a flow might be, the ACOS device waits until the flow has ended and the
session is deleted before it sends any flow records for it.
[no] protocol Configure the version of the NetFlow protocol you want to use:
• v9 – Version 9 (default)
• v10 – Version 10
[no] record Configure the NetFlow record types to be exported. (See the “NetFlow v9 and v10
netflow-template-type (IPFIX)” chapter in the System Configuration and Administration Guide.)
[no] resend-template Configure when to resend the NetFlow template. The trigger can be either the num-
{records num | ber of records, or the amount of time that has passed.
timeout seconds}
• records – Specifies the counters by which the ACOS device resends
templates to the collectors. The num can be 0-1000000. The default is 1000.
• timeout – Specifies the time between when templates are resent to the
collec- tors. The num is the number of seconds and can be 0-86400. The
default is 1800.
NOTE: Specifying 0 means never resend the template.
[no] sample {ethernet | Enable sampling.
global | nat-pool | ve}
Configure filters for monitoring traffic. Identify the specific type and subset of
resources to monitor.
• ethernet portnum – Specify the list of Ethernet data ports to monitor.
Flow information for the monitored interfaces is sent to the NetFlow
collector(s).
• global – (Default) No filters are in effect. Traffic on all interfaces is monitored.
• nat-pool pool-name – NAT pool.
• ve ve-num – Specify the list of Virtual Ethernet (VE) data ports to monitor.
[no] source-address Uses the specified IP address as the source address for exported NetFlow packets.
{ip ipv4addr | By default, the IP address assigned to the egress interface is used. This command
ipv6 ipv6addr} does not change the egress port out which the NetFlow traffic is exported.
[no] source-ip-use-mgmt Use the management interface’s IP address as the source IP for exported NetFlow
packets. This command does not change the egress port out which the NetFlow traf-
fic is exported.
no
Syntax no command-string
Default N/A
Mode Config
Usage Use the “no” form of a command to disable a setting or remove a configured item. Configu-
ration commands at all Config levels of the CLI have a “no” form, unless otherwise noted.
The command is removed from the running-config. To permanently remove the command
from the configuration, use the write memory command to save the configuration
changes to the startup-config. (See “write memory” on page 57.)
Example The following command removes server “http99” from the running-config:
ntp
Description Configure Network Time Protocol (NTP) parameters.
The ntp server command changes the CLI to the configuration level for the server,
where the following commands are available.
Parameter Description
allow-data-ports Allow connections to NTP servers from data ports.
disable Disables synchronization with the NTP server.
enable Enables synchronization with the NTP server.
key ID-num Creates an authentication key. For ID-num, enter a value
between 1-65535.
prefer Directs ACOS to use this NTP server by default. Additional
NTP servers are used as backup servers if the preferred NTP
server is unavailable.
Parameter Description
{M | SHA | SHA1} Specifies the type of authentication key you want to create
{ascii | hex} for authenticating the NTP servers.
string
• M - encryption using MD5
• SHA - encryption using SHA
• SHA1 - encryption using SHA1
Specify the authentication key string (1-20 characters. Use
the hex parameter to specify the string in hex format (21-
40 characters), or ascii to specify it in text.
trusted-key ID-num Adds an authentication key to the list of trusted keys. For
num, enter the identification number of a configured
authentication key to add the key to the trusted key list. You
can enter more than one number, separated by whitespace,
to simultaneously add multiple authentication keys to the
trusted key list.
Default NTP synchronization is disabled by default. If you enable it, DST is enabled by default, if
appli- cable to the specified timezone.
If the system clock is adjusted while OSPF or IS-IS is enabled, the routing protocols may stop
working properly. To work around this issue, disable OSPF and IS-IS before adjusting the
system clock.
Example The following commands configure an NTP server and enable NTP:
Example The following example creates 3 authentication keys (1337 using MD5 encryption, 1001
using SHA encryption, and 1012 using SHA1 encryption) and adds these keys to the list of
trusted keys. The NTP server located at 10.1.4.20 is configured to use a trusted key (1337)
for authentication:
You can verify the NTP server and authentication key configuration with the show run
command. The following example includes an output modifier to display only NTP-related
configuration:
object-group network
Description Create a network object group, for specifying match criteria using Layer 3 parameters.
An object group is a named set of IP addresses or protocol values.
Parameter Description
group-name Name of the network object group (1-63 characters).
acl Create a network object group that will be used by Access Control Lists.
When you configure an IPv4 or IPv6 ACL, you can specify the name of
an object group in place of IP address or protocol parameters. This
capability can be useful in cases where the same match criteria are
used in more than one ACL. If you need to modify the match criteria,
you can apply the changes to all affected ACLs at the same time, by
modifying the object group. You do not need to edit each individual
ACL.
fw v4 Create a network object group that will be used for IPv4 firewall config-
urations.
f4 v6 Create a network object group that will be used for IPv4 firewall config-
urations.
This command changes the CLI to the configuration level for the network object group,
where the following commands are available:
Command Description
[no] any Matches on all IP addresses.
[no] host host-src-ipaddr Matches only on the specified host IPv4 or IPv6 address.
Command Description
[no] net-src-ipaddr { Matches on any host in the specified IPv4 subnet.
filter-mask |
The filter-mask specifies the portion of the address to filter:
/mask-length }
• Use 0 to match.
• Use 255 to ignore.
For example, the following filter-mask filters on a 24-bit subnet: 0.0.0.255
Alternatively, you can use mask-length to specify the portion of the address
to filter. For example, you can specify “/24” instead “0.0.0.255” to filter on a 24-bit
subnet.
[no] net-src-ipv6addr Matches on any host in the specified subnet. The prefix-length specifies
/prefix-length the portion of the address to filter.
Example The following commands configure network object groups INT_CLIENTS, HTTP_SERVERS
and FTP_SERVERS:
This command changes the CLI to the configuration level for the service object group, where
the following commands are available:
Command Description
description Description of this service object group instance.
[no] icmp Matches on ICMP traffic.
[type {type-option}
The type type-option parameter matches based on the
[code {any-code | code-num}]]
specified ICMP type. You can specify one of the following ICMP types
(enter either the number or the name):
• any-type – Matches on any ICMP type.
• dest-unreachable | 3 – Type 3, destination unreachable
• echo-reply | 0 – Type 0, echo reply
• echo-request | 8 – Type 8, echo request
• info-reply | 16 – Type 16, information reply
• info-request | 15 – Type 15, information request
• mask-reply | 18 – Type 18, address mask reply
• mask-request | 17 – Type 17, address mask request
• parameter-problem | 12 – Type 12, parameter problem
• redirect | 5 – Type 5, redirect message
• source-quench | 4 – Type 4, source quench
• time-exceeded | 11 – Type 11, time exceeded
• timestamp | 13 – Type 13, timestamp
• timestamp-reply | 14 – Type 14, timestamp reply
The code code-num option is applicable if the protocol type is icmp.
You can specify:
• any-code – Matches on any ICMP code.
• code-num – ICMP code number, 0-254
Command Description
[no] icmpv6 Matches on ICMPv6 traffic.
[type {type-option}
The type type-option parameter matches based on the specified
[code {any-code | code-num}]]
ICMPv6 type. You can specify one of the following types (enter either the
number or the name):
• any-type – Matches on any ICMPv6 type.
• dest-unreachable – Matches on type 1, destination unreachable
messages.
• echo-reply – Matches on type 129, echo reply messages.
• echo-request – Matches on type 128, echo request messages.
• packet-too-big – Matches on type 2, packet too big messages.
• param-prob – Matches on type 4, parameter problem messages.
• time-exceeded – Matches on type 3, time exceeded messages.
Example The following commands configure service object group WEB_SERVICES and display
the configuration:
Example The following command configures an ACL that uses service object group configured above:
overlay-mgmt-info
Description Configure management-specific data for an overlay network. (See the Configuring Overlay
Networks guide.)
overlay-tunnel
Description Configure an overlay network. (See the Configuring Overlay Networks guide.)
packet-handling
Description Configure how you want the system to handle unregistered broadcast packets.
Parameter Description
trap Trap packets to the CPU.
flood Flood packets to other ports.
partition
Description Configure an L3V private partition.
For more information, see “ADP CLI Commands” in Configuring Application Delivery
Partitions.
partition-group
Description Create a named set of partitions.
For more information, see “ADP CLI Commands” in Configuring Application Delivery
Partitions.
ping
Description Ping is used to diagnose basic network connectivity. For syntax information, see “ping” on
page 29.
pki copy-cert
Description Make a copy of the SSL certificate file.
Parameter Description
source-cert-name Name of the existing SSL certificate file (1-63 characters).
rotation Specify the rotation number of the SCEP generated certificate file (1-4).
dest-cert-name Name of the copy of the SSL certificate file (1-63 characters).
overwrite if there is an existing file with the same name as the specified dest-cert-name, overwrite
the existing file.
Example Create a copy of the existing SSL cert file (example_existing_cert.crt) to a new file
(exam- ple_new_cert.crt), and overwrite the destination file if it has the same name:
pki copy-key
Description Make a copy of the SSL key file.
Parameter Description
source-cert-name Name of the existing SSL key file (1-63 characters).
rotation Specify the rotation number of the SCEP generated key file (1-4).
dest-cert-name Name of the copy of the SSL key file (1-63 characters).
overwrite if there is an existing file with the same name as the specified dest-key-name, overwrite the
existing file.
Example Create a copy of the existing SSL key file (example_existing_key.key) to a new file
(exam- ple_new_key.key), and overwrite the destination file if it has the same name:
pki create
Description Create a self-signed certificate.
Commands Description
create Creates a self-signed certificate or a certificate signed request (CSR) file.
[certificate certificate- Creates the self-signed certificate. You can specify up to 255 characters in the
name] name.
[csr csr_name] Creates a certificate signed request (CSR) and allows you to specify a file
{name [renew cert-name] name. You can specify up to 255 characters in the name.
use-mgmt-port url | The following options apply to name:
cert-expiration-within
days {local | use-mgmt-
• name is the name of the CSR file.
port url} • renew allows you to create a CSR file name to renew an expiring
certificate.
• use-mgmt-port uses the management interface as the source
interface for the connection to the remote device. The management route
table is used to reach the device. By default, the ACOS device attempts to
use the data route table to reach the remote device through a data
interface.
The following options apply to cert-expiration-within:
• days allows you to specify in how many days the certificate will expire. You
can select from 0 to 100 days.
• local allows you to save the CSR file on your local drive.
• use-mgmt-port uses the management interface as the source interface
for the connection to the remote device. The management route table is used
to reach the device. By default, the ACOS device attempts to use the data
route table to reach the remote device through a data interface.
url File transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter to display a
prompt for each part of the URL. If you enter the entire URL and a password is
required, you will still be prompted for the password. The password can be up to
255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
pki delete
Description Deletes a self-signed certificate.
Commands Descriptions
delete Deletes the self-signed certificate or the CSR file.
cert-name Deletes a specific self-signed certificate.
crl_file_name Deletes a specific certificate revocation list (CRL) file.
priv_key_name Deletes a specific private key.
pki renew-self
Description Renews a self-signed certificate.
Commands Description
renew Renews the self-signed certificate or the CSR file.
cert-name Deletes a specific self-signed certificate.
Commands Description
days num Number of effective dates for which the certificate should be
extended. This should be a value from 30 to 3650 days. The default
value is a 730 day extension
days-others Presents a more extensive set of input options. After entering the
value for an option, press Enter to display the input prompt for the
next option. The following
specifications will be presented sequentially:
• input valid days, 30-3650, default 730: num
• input Common Name, 0-64: name
• input Division, 0-31: division-name
• input Organization, 0-63: organization-name
• input Locality, 0-31: city-or-region
• input State or Province, 0-31: state-or-province
• input Country, 2 characters: country-code
• input email address, 0-64: email-address
The num specifies the number of effective days for which the certifi-
cate should be extended, ranging from 30 to 3650 days. If this field
is left blank, then the default value is a 730 day extension.
Every other option can be left blank, except for the country-
code value. The numbers following Common Name, Division,
Organiza- tion, Locality, State or Province, and email address
specify the num- ber of characters allowed.
pki scep-cert
Description Create an SCEP certificate enrollment object.
Replace object-name with the name of the certificate you want to enroll (1-63
characters).
poap
Description Enables Power On Auto Provisioning (POAP).
NOTE: After using the poap command, you must reboot the system. The device will
return to service in POAP mode.
Default POAP mode is enabled by default on virtual appliances. However, the feature is disabled
by default on all physical devices.
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
radius-server
Description Set RADIUS parameters, for authenticating administrative access to the ACOS device.
Parameter Description
hostname | ipaddr Hostname or IP address of the RADIUS server.
secret secret-string Password, 1-128 characters, required by the RADIUS server for authentication
requests.
acct-port Protocol port to which the ACOS device sends RADIUS accounting information.
protocol-port
The default port is 1813.
auth-port Protocol port to which the ACOS device sends authentication requests.
protocol-port
The default port is 1812.
retransmit num Maximum number of times the ACOS device can resend an unanswered
authentication request to the server. If the ACOS device does not receive a
reply to the final request, the ACOS device tries the secondary server, if one is
config- ured.
If no secondary server is available, or if the secondary server also fails to
reply after the maximum number of retries, authentication fails and the
admin is denied access.
You can specify 0-5 retries. The default is 3 retries.
Parameter Description
timeout seconds Maximum number of seconds the ACOS device will wait for a reply to an
authentication request before resending the request. You can specify 1-15 sec-
onds.
The default is 3 seconds.
default-privilege-read-write Change the default privilege authorized by RADIUS from read-only to read-
write. The default privilege is used if the Service-Type attribute is not used, or
the A10 vendor attribute is not used.
This is disabled by default; if the Service-Type attribute is not used, or the A10
vendor attribute is not used, successfully authenticated admins are authorized
for read-only access.
Default No RADIUS servers are configured by default. When you add a RADIUS server, it has the
default settings described in the table above.
You can configure up to 2 RADIUS servers. The servers are used in the order in which you
add them to the configuration. Thus, the first server you add is the primary server. The
second server you add is the secondary (backup) server. Enter a separate command for each
of the servers. The secondary server is used only if the primary server does not respond.
Example The following commands configure a pair of RADIUS servers and configure the ACOS
device to use them first, before using the local database. Since 10.10.10.12 is added first,
this server will be used as the primary server. Server 10.10.10.13 will be used only if the
primary server is unavailable.
Description Enter the configuration level for RAID, if applicable to your device model.
Syntax raid
rba enable
Description Enable Role-Based Access Control (RBA) configuration.
This feature supports the creation of multiple users, groups, and roles with varying degrees
of permissions. RBA can limit the read/write privileges on different partitions and for different
objects.
For more information about this feature, see “Role-Based Access Control” in the Management
Access and Security Guide.
rba disable
Description Disable Role-Based Access Control (RBA) configuration.
For more information about this feature, see “Role-Based Access Control” in the Management
Access and Security Guide.
rba group
Description Configure an RBA group.
For more information about this feature, see “Role-Based Access Control” in the Management
Access and Security Guide.
Example The following example defines an RBA group “slb-group.” The group has two users, “slb-
user1” and “slb-user2.” Both users are granted write privileges on SLB server objects but
read only privileges on all other SLB objects in partition “companyA”:
!
rba group slb-group
user slb-user1
user slb-user2
partition companyA
slb read
slb.server write
rba role
Description Configure an RBA role.
For more information about this feature, see “Role-Based Access Control” in the Management
Access and Security Guide.
Example The following example defines an RBA role “role1.” Any user assigned this role will have
write access on SLB server objects, but read privileges on all other SLB objects.
!
rba role role1
slb read
slb.server write
rba user
Description Configure RBA for a user.
The user must be an existing admin account and can be authentication either locally or
externally using LDAP, RADIUS, or TACACS+.
For more information about this feature, see “Role-Based Access Control” in the Management
Access and Security Guide.
Example The following example configures RBA for user “user1”. In partition companyA, this user
has read privileges for SLB virtual server objects, write privileges for SLB server objects,
but no access to all other SLB objects. In partition companyB, this user has all privileges
defined by RBA role “role1”:
!
rba user user1
partition companyA
slb no-access
slb.server write
slb.virtual-server read
partition companyB
role role1
!
restore
Description Restore the startup-config, aFleX policy files, and SSL certificates and keys from a file
previ- ously created by the backup system command. The restored configuration takes
effect fol- lowing a reboot.
NOTE: Backing up system from one hardware platform and restoring it to another is not
supported.
Parameter Description
use-mgmt-port Uses the management interface as the source interface for the
connection to the remote device. The management route table is
used to reach the device. By default, the ACOS device attempts to
use the data route table to reach the remote device through a data
interface.
url File transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter
to display a prompt for each part of the URL. If you enter the entire
URL and a password is required, you will still be prompted for the
password. The password can be up to 255 characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[:port]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Default N/A
Usage Do not save the configuration (write memory) after restoring the startup-config. If you
do, the startup-config will be replaced by the running-config and you will need to restore the
startup-config again.
To place the restored configuration into effect, reboot the ACOS device.
route-map
Description Configure a rule in a route map. You can use route maps to provide input to routing com-
mands, like the “redistribute” or “default-information originate” command for OSPF. See
the Network Configuration Guide for more information.
Parameter Description
map-name Route map name.
deny | permit Action to perform on data that matches the rule.
sequence-num Sequence number of the rule within the route map, 1-65535. Rules
are used in ascending sequence order.
The action in the first matching rule is used, and no further match-
ing is performed.
You do not need to configure route map rules in numerical order.
The CLI automatically places them in the configuration (running-
config) in ascending numerical order.
This command changes the CLI to the configuration level for the specified route map rule,
where the following commands are available.
Command Description
match attribute Specifies the match criteria for routes:
• match as-path list-id – Matches on the BGP AS paths in the specified AS path list.
• match community list-id [exact-match] – Matches on the BGP communities
in the specified community list.
• match extcommunity list-id [exact-match]– Matches on the BGP
communities listed in the specified extended community list.
• match group num {active | standby} – Matches on VRRP-A set ID and state
(active or standby).
• match interface {ethernet portnum | loopback num | trunk num |
ve ve-num} – Matches on the data interface used as the first hop for a route.
• match ip address {acl-id | prefix-list list-name} – Matches on the
route IP addresses in the specified ACL or prefix list.
• match ip next-hop {acl-id | prefix-list list-name}– Matches on the
next- hop router IP addresses in the specified ACL or prefix list.
• match ip peer acl-id – Matches on the peer router IP addresses in the specified list.
• match ipv6 address {acl-id | prefix-list list-name} – Matches on
the route IP addresses in the specified ACL or prefix list.
• match ipv6 next-hop {acl-id | prefix-list list-name | ipv6-
addr} – Matches on the next-hop router IP addresses in the specified ACL or prefix list, or
the speci- fied IPv6 address.
• match ipv6 peer acl-id – Matches on the peer router IP addresses in the specified
ACL.
• match local-preference num – Matches on the specified local preference value,
0-4294967295.
• match metric num – Matches on the specified route metric value, 0-4294967295.
• match origin {egp | igp | incomplete} – Matches on the specified BGP
origin code.
• match route-type external {type-1 | type-2} – Matches on the
specified external route type.
• match tag tag-value – Matches on the specified TAG value, 0-4294967295.
Command Description
set attribute Sets information for matching routes:
• set aggregator as as-num ipaddr – Sets the aggregator attribute.
• set as-path prepend as-num [...]– Adds the specified BGP AS number(s)
to the front of the AS-path attribute.
• set atomic-aggregate – Specifies that a BGP route has been aggregated, and that
path information for the individual routes that were aggregated together is not available.
• set comm-list list-id delete – Sets the specified BGP community list to
be deleted.
• set community community-value – Sets the BGP community ID to the specified
value: 1-4294967295
AS:NN, where AS is the AS number and NN is a numeric value in the range 1-4294967295.
internet – Internet route.
local-AS – Advertises routes only within the local Autonomous System (AS), not to
exter- nal BGP peers.
no-advertise – Does not advertise routes.
no-export – Does not advertise routes outside the AS boundary.
none – No community attribute.
• set dampening [reachability-half-life [reuse-value [suppress-value]
[max-duration [unreachability-half-life]]]] – Enables route-flap
dampening. Route-flap dampening helps minimize network instability caused by unstable
routes.
reachability-half-life – Reachability half life, 1-45 minutes. After a route
remains reachable for this period of time, the penalty value for that route is divided in
half. The default is 15 minutes.
reuse-value [suppress-value] – Penalty thresholds for the suppression and
reuse (re-advertisement) of a route. The supported range for each value is 1-20000. The
default suppress-value is 2000. the default reuse-value is 750.
max-duration – Maximum amount of time a route will remain suppressed, 1-255 minutes.
The default is 4 times the reachability-half-life.
unreachability-half-life – Unreachability half life, 1-45 minutes. After a route
remains unreachable for this period of time, the penalty value for that route is divided in half.
(cont.)
Command Description
set attribute • set extcommunity comm-id [...]– Sets the BGP extended community attribute.
• set ip next-hop ipaddr – Sets the next hop for matching IPv4 routes.
• set ipv6 [local] ipv6addr – Set the next hop for matching IPv6 routes. If the
address is for an inside network (not globally routable), use the local option.
• set level {level-1 | level-1-2 | level-2} – Sets the IS-IS level for
exporting a route to IS-IS.
• et local-preference num – Sets the BGP local preference path attribute.
• set metric metric-value – Sets the metric value for the destination routing
protocol.
• set metric-type {external | internal | type-1 | type-2} – Sets the
metric type for the destination routing protocol.
• set origin {egp | igp | incomplete} – Sets the origin attribute:
egp – Exterior gateway protocol.
igp – Interior gateway protocol.
incomplete – Unknown
heritage.
• set originator-id ipaddr – Sets the BGP originator attribute.
• set tag tag-value – Sets the tag value for the destination routing protocol.
• set weight num – Sets the BGP weight value for the routing table.
Default None
Usage For options that use an ACL, the ACL must use a permit action. Otherwise, the route
map action is deny.
router
Description Enter the configuration mode for a dynamic routing protocol.
Command Description
bgp AS-num Specifies an Autonomous System (AS) for which to run Border Gateway Protocol
(BGP) on the ACOS device. This also enters BGP configuration mode.
For more information, see “Config Commands: Router - BGP” in the Network Configu-
ration Guide.
ipv6 {ospf [tag] | rip} Specifies an IPv6 OSPFv3 process (1-65535) or Routing Information Protocol (RIP)
pro- cess to run on the IPv6 link, and also enter configuration mode for the specified
pro- tocol.
For more information, see “Config Commands: Router - OSPF” or “Config Commands:
Router - RIP” in the Network Configuration Guide.
isis [tag] Enter configuration mode for Intermediate System to Intermediate System (IS-IS).
For more information, see “Config Commands: Router - IS-IS” in the Network Configu-
ration Guide.
ospf [process-id] Specifies an IPv4 OSPFv2 process (1-65535) to run on the ACOS device, and also
enter OSPF configuration mode.
For more information, see “Config Commands: Router - OSPF” in the Network Configu-
ration Guide.
rip Enter configuration mode for Routing Information Protocol (RIP).
For more information, see “Config Commands: Router - RIP” in the Network Configura-
tion Guide.
Usage This command is valid only when the ACOS device is configured for gateway mode (Layer 3).
Example The following command enters the configuration level for OSPFv2 process 1:
Parameter Description
name string Name of the log file.
per-protocol Uses separate log files for each protocol. Without this option, log mes-
sages for all protocols are written to the same file.
By default, this is disabled.
rotate num Specifies the number of backups to allow for each log file. When a
log file becomes full, the logs are saved to a backup file and the log
file is cleared for new logs. You can specify 0-100 backups. If the
maximum number of backups is reached, the oldest backups are
purged to make way for new ones.
The default is 0.
size Mbytes Specifies the size of each log file. You can specify 0-1000000 Mbytes. If
you specify 0, the file size is unlimited.
The default size is 0.
Usage When you enable logging, the default minimum severity level that is logged is debugging.
The per-protocol option is recommended. Without this option, messages from all
routing protocols will be written to the same file, which may make troubleshooting more
difficult.
rule-set
Description Configure a Data Center Firewall rule set.
run-hw-diag
Description Access the hardware diagnostics menu on the next reboot
CAUTION: The system will be unavailable for normal operations while a test is running.
NOTE: A reboot is required before the hardware diagnostics menu appears. If you reboot
to a software release that does not support the hardware diagnostics menu, the
menu is not available. Currently, the hardware diagnostics menu is supported in
AX Release 2.4.3-P3 and later 2.4.x releases, and in AX Release 2.6.1.
Syntax run-hw-diag
Usage The hardware diagnostic menu is available only on serial console sessions. To run a test,
you must use a serial console connection.
The run-hw-diag command requires a reboot. After the reboot is completed, a menu with
the following options appears:
• 1 - Memory Test
• 2 - HDD/CF Scan Test (1-2 hours)
• 3 - MBR (Master Boot Record) check
• 4 - Complete Test (all above)
• x - Reboot
NOTE: As indicated in the description for option 2, the media scan test, the test takes 1-2
hours to complete.
After a test is completed, you can use the x option to reboot. If you do not enter an
option to run another test or reboot, the system automatically reboots after 5 minutes.
The same software image that was running when you entered the run-hw-diag
command is reloaded during the reboot.
Example The following example shows how to access the hardware diagnostic menu:
ACOS(config)#run-hw-diag
Please confirm: You want to run HW diagnostics (N/Y)?:y
Please reboot the system when you are ready.
HW diagnostic will run when the system comes back up.
ACOS(config)#end
ACOS#reboot
Proceed with reboot? [yes/no]:yes
Rebooting......
00000000000
------------------------------------------------------
| Hardware Diagnostic Menu |
------------------------------------------------------
| 1 - Memory Test |
| 2 - HDD/CF Scan Test (1-2 hours) |
| 3 - MBR (Master Boot Record) check |
| 4 - Complete Test (all above) |
| x - Reboot |
------------------------------------------------------
running-config display
Description Configure whether or not aFleX and class-list file information should be included in the run-
ning-config.
Parameter Description
aflex Show aFleX scripts in the running-config.
class-list Show class-list files in the running-config.
scaleout
Description Configure Scaleout.
session-filter
Description Configure a session filter.
Parameter Description
dest-addr Matches on sessions that have a source or destination IPv4 address or port:
dest-port
• source-addr ipaddr [{subnet-mask | /mask-length}] – Matches on
source-addr IPv4 sessions that have the specified source IP address.
source-port
• source-port port-num – Matches on IPv4 sessions that have the specified
source protocol port number, 1-65535.
• dest-addr – Matches on IPv4 sessions that have the specified destination IP address.
• dest-port – Matches on IPv4 sessions that have the specified destination protocol
port number, 1-65535.
You can use one or more of the suboptions together in a single command, nested in the
order shown above. For example, if the first suboption you enter is dest-addr, the
only additional suboption you can specify is dest-port.
ipv6 Matches on all sessions that have a source or destination IPv6 address.
sip Matches on all SIP sessions.
Usage Session filters allows you to save session display options for use with the clear
session and show session commands. Configuring a session filter allows you to specify
a given set of options one time rather than re-entering the options each time you use the
clear ses- sion or show session command.
Example The following commands configure a session filter and use it to filter show session
output:
sflow
Description Enables the ACOS device to collect information about Ethernet data interfaces and send
the data to an external sFlow collector (v5).
Parameter Description
agent address Configure an sFlow agent. The ipaddr value can be any valid IPv4 or IPv6
{ipaddr | ipv6addr} address. By default, sFlow datagrams use the management IP of the ACOS
device as the source address, but you can specify a different IP address, if
desired. The informa- tion will appear in the Layer 4 information section of the
sFlow datagram, and it is not used to make routing decisions.
collector Configure up to four sFlow collectors. The IP address is that of the sFlow collector
{ip ipaddr | ipv6 ipv6addr} device. Specify the port number, with a range from 1-65535.
portnum
The default port number is 6343.
polling type Enables sFlow export of DDoS Mitigation statistics for the source IP address(es)
matched by this rule. You can enable polling for the following types of data:
• cpu-usage – Polls for CPU utilization statistics.
• ethernet – Polls for Ethernet data interface statistics.
• http-counter - Polls for HTTP statistics.
• ve - Polls for statistics for Virtual Ethernet (VE) interfaces.
All sFlow polling (collection) is disabled by default
Parameter Description
setting sub-options Configure global sFlow settings:
• counter-polling-interval seconds – Configure the sFlow counter
polling interval. The interval seconds option specifies the frequency with
which statistics for an interface are periodically sampled and sent to the sFlow
collector. The range can be configured to a value from 1-200 seconds. The
default polling interval is 20 seconds.
• max-header bytes – Maximum number of bytes to sample from any given
packet, 14-512 bytes. The default is 128 bytes.
• packet-sampling-rate num – Configure sFlow default packet sampling
rate. The num option specifies the value of N, where N is the value of the
denominator in the ratio at which a single packet will be sampled from a
denominator ranging from 10-1000000. The default is 1000, meaning one
packet out of every 1000 will be sampled.
• source-ip-use-mgmt – Enable use of the management interface’s IP as
the source address for outbound sFlow packets.
source-address Source IP address for sFlow packets sent from ACOS to sFlow collectors.
{ip ipaddr | ipv6 ipv6addr}
NOTE: By default, the IP address of the egress interface is used. You can
specify a data interface’s IP address or the management interface’s IP address
as the source address for sFlow packets sent to the collector. However, the
current release does not support routing of sFlow packets out the management
interface. The sFlow collector must be able to reach the ACOS device through a
data interface, even if you use the ACOS device’s management IP address as
the source address of sFlow packets sent to the collector.
Usage Enable either or both of the following types of data collection, for individual Ethernet
data ports:
• Packet flow sampling – ACOS randomly selects incoming packets on the monitored
interfaces, and extracts their headers. Each packet flow sample contains the first 128
bytes of the packet, starting from the MAC header. Note that setting a smaller value
for the num variable increases the sampling frequency, and larger numbers decrease
the sampling frequency. This is due to the fact that the variable is in the denominator.
• Counter sampling – ACOS periodically retrieves the send and receive statistics for
the monitored interfaces. These are the statistics listed in the Received and
Transmitted counter fields in show interface output.
Notes
• Sampling of a packet includes information about the incoming interface but not
the outgoing interface.
• None of the following are supported:
• Host resource sampling
• Application behavior sampling
• Duplication of traffic to multiple sFlow collectors
• Configuration of sFlow Agent behavior using SNMP
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
Example The following commands specify the sFlow collector, and enables use of the management
interface’s IP as the source IP for the data samples sent to the sFlow collector:
slb
Description Configure Server Load Balancing (SLB) parameters. For information about the slb com-
mands, see “Config Commands: Server Load Balancing” in the Command Line
Interface Reference for ADC.
smtp
Description Configure a Simple Mail Transfer Protocol (SMTP) server to use for sending emails from the
ACOS device.
Parameter Description
hostname | ipaddr Specifies an SMTP server.
mailfrom email-src-addr Specifies the email address to use as the sender (From) address.
needauthentication Specifies that authentication is required.
This is disabled by default.
port protocol-port Specifies the protocol port on which the server listens for SMTP traffic.
The default port is 25.
username string Specifies the username and password required for access. The password can be 1-31
password string characters long.
Default No SMTP servers are configured by default. When you configure one, it has the default
set- tings described in the table above.
Example The following command configures the ACOS device to use SMTP server “ourmailsrvr”:
ACOS(config)#smtp ourmailsrvr
snmp
Description For information about SNMP commands, see “Config Commands: SNMP” on page 225.
so-counters
Description Show scale out statistics.
Option Description
all All packets.
so_pkts_conn_in Total packets processed for an established con-
nection.
so_pkts_conn_redirect Total packets redirected for an established con-
nection.
so_pkts_dropped Total packets dropped.
so_pkts_errors Total packet errors.
so_pkts_in Total number of incoming packets.
so_pkts_new_conn_in Total packets processed for a new connection.
so_pkts_new_conn_redirect Total packets redirected for a new connection.
so_pkts_out Total number of packets sent out.
so_pkts_redirect Total number of packets redirected.
sshd
Syntax sshd
{
key generate [size {2048 | 4096}] |
key load [use-mgmt-port] url |
key regenerate [size {2048 | 4096}] |
key wipe |
restart
}
Parameter Description
key generate Generate an SSH key.
You can choose to specify a key size; use size 2048 to generate a 2048-bit key, or size 4096
to generate a 4096-bit key.
key load Load an SSH key.
Specify use-mgmt-port to use the management interface as the source interface for the
con- nection to the remote device. The management route table is used to reach the device. By
default, the ACOS device attempts to use the data route table to reach the remote device
through a data interface.
Specify the url to the SSH key. You can enter the entire URL on the command line or press
Enter to display a prompt for each part of the URL. If you enter the entire URL and a password
is required, you will still be prompted for the password. The password can be up to 255
characters long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
syn-cookie
Description Enable hardware-based SYN cookies, which protect against TCP SYN flood attacks.
Parameter Description
on-threshold num Maximum number of concurrent half-open TCP connections
allowed on the ACOS device, before SYN cookies are enabled.
If the number of half-open TCP connections exceeds the on-
threshold, the ACOS device enables SYN cookies. You can
specify 0-2147483647 half-open connections.
off-threshold num Minimum number of concurrent half-open TCP connections
for which to keep SYN cookies enabled. If the number of half-
open TCP connections falls below this level, SYN cookies are
disabled. You can specify 0-2147483647 half-open connec-
tions.
NOTE: It may take up to 10 milliseconds for the ACOS device to detect and respond to
crossover of either threshold.
Default Hardware-based SYN cookies are disabled by default. When the feature is enabled, there
are no default settings for the on and off thresholds.
If both hardware-based and software-based SYN cookies are enabled, only hardware-based
SYN cookies are used. You can leave software-based SYN cookies enabled but they are not
used. (Software-based SYN cookies are enabled at the virtual port level using the syn-
cookie enable command.)
If you omit the on-threshold and off-threshold options, SYN cookies are
enabled and are always on regardless of the number of half-open TCP connections present
on the ACOS device.
This command globally enables SYN cookie support for SLB and also enables SYN cookie
support for Layer 2/3 traffic. No additional configuration is required for SLB SYN cookie
support. However, to use Layer 2/3 SYN cookie support, you also must enable it at the
configuration level for individual interfaces. See the “ip tcp syn-cookie threshold” command
in the Network Configuration Guide.
If L3V partitions are configured, hardware-based SYN cookies must be enabled per individual
partition. Hardware-based SYN cookies are NOT partition-aware.
On FTA models only, it is recommended not to use hardware-based SYN cookies if DSR also
is enabled. If both features are enabled, a client who sends TCP requests to a VIP that is
configured for DSR will receive two SYN-ACKS, one from the ACOS hardware-based SYN-
cookie feature, and the other from the server. This can be confusing to a client because the
client expects only one SYN-ACK in reply to the client’s SYN.
ACOS(config)#syn-cookie enable
The command in the following example configures dynamic SYN cookies when the number
of concurrent half-open TCP connections exceeds 50000, and disables SYN cookies when
the number falls below 30000:
system all-vlan-limit
Description Set the global traffic limits for all VLANs.
The limit applies system-wide to all VLANs; collectively, all ACOS device VLANs
cannot exceed the specified limit.
To configure the limit per individual VLAN, use “system per-vlan-limit” on page 199.
Parameter Description
all-vlan-limit Limit applies system-wide to all VLANs. Collectively, all the
ACOS device’s VLANs together cannot exceed the specified
limit.
per-vlan-limit Limit applies to each VLAN. No individual can exceed the
speci- fied limit.
bast Limit broadcast traffic.
ipmcast Limit IP multicast traffic.
mcast Limit all multicast packets except for IP multicast packets.
unknown-ucast Limit all unknown unicast traffic.
num Specifies the maximum number of packets per second that are
allowed of the specified traffic type.
Example The following command limits each VLAN to 1000 multicast packets per second:
Default Disabled
Default Disabled
system cpu-load-sharing
Description The CPU Round Robin feature can be used to mitigate the effects of Denial of Service
(DoS) attacks that target a single CPU on the ACOS device. You can use this command to
configure thresholds for CPU load sharing. If a threshold is exceeded, CPU load sharing is
activated, and additional CPUs are enlisted to help process traffic and relieve the burden
on the targeted CPU. A round robin algorithm distributes packets across all of the other
data CPUs on the device. Load sharing will remain in effect until traffic is no longer
exceeding the thresholds that originally activated the feature. (See the “Usage” section
below for details.)
Parameter Description
cpu-usage low Lower CPU utilization threshold. Once the data CPU utilization rate drops below this
percent thresh- old, then CPU round robin redistribution will stop. The default is 60, but you
can specify 0- 100 percent.
cpu-usage high Upper CPU utilization threshold. Once the data CPU utilization rate exceeds this
percent threshold, then CPU round robin redistribution will begin. The default is 75, but you can
specify 0-100 percent.
Parameter Description
disable Disables CPU load sharing. The CPU round robin feature is not used, even if a triggering
threshold is breached.
packets-per-second Maximum number of packets per second any CPU can receive, before CPU load sharing is
min num-pkts used. You can specify 0-30000000 (30 million) packets per second.
Default The CPU load sharing feature is enabled. The thresholds have the following default values:
• cpu-usage low – 60 percent
• cpu-usage high – 75 percent
• packets-per-second – 100000
Usage If a hacker targets the ACOS device by repeatedly flooding the device with many
packets that have the same source and destination ports, this could overwhelm the
CPU that is being targeted. However, the CPU load sharing feature (which is enabled
by default) protects the device by using a round robin algorithm to distribute the load
across multiple CPUs when such an attack is detected.
ACOS will activate this round robin distribution across multiple CPUs if all of the following
conditions occur:
1. If the utilization rate of the CPU being targeted exceeds the configured high
threshold (which has a default value of 75%), AND
2. If the CPU being targeted is receiving traffic at a rate that exceeds the minimum
config- ured threshold (the default is 100,000 packets per second), AND
3. If the CPU being targeted is receiving significantly more traffic than the other CPUs on
the ACOS device. If all CPUs are under a heavy load, there would be no advantage to
using round robin to distribute the traffic. Therefore, the CPU being targeted must
have an elevated utilization rate that is at least 50% higher than the median utilization
rate of its peer CPUs. (For example, this criterion would be met if the non-targeted
CPUs have a median packet flow of 100,000 packets per second, but the targeted
CPU is receiving packets at a rate exceeding 150,00 packets per second, in which
case it would be 50% higher than the median of the rate of the other processors).
ACOS will de-activate CPU round robin mode and return to normal mode when the first
criterion, and either 2 or 3 above are no longer true.
1. If the targeted CPU utilization rate drops below the low threshold (default is 60%), AND
• If the targeted CPU is receiving packets at a rate below the minimum configured
packets-per-second threshold, OR
• If the utilization rate of the targeted CPU is no longer 50% higher than the median
of its neighboring CPUs.
system ddos-attack
Description Enable logging for DDoS attack events.
system glid
Description Apply a combined set of IP limiting rules to the whole system.
Default None
Usage This command uses a single global LID. To configure the global LID, see “glid” on page 123.
Example The following commands configure a standalone IP limiting rule to be applied globally to all
IP clients (the clients that match class list “global”):
ACOS(config)#glid 1
ACOS(config-glid:1)#conn-rate-limit 10000 per 1
ACOS(config-glid:1)#conn-limit 2000000
ACOS(config-glid:1)#over-limit forward logging
ACOS(config-glid:1)#exit
ACOS(config)#system glid 1
system ipsec
Description Configure Crypto Cores for IPsec processing.
Parameter Description
crypto-core num Number of crypto cores assigned for IPsec processing (0-56).
crypto-mem percentage Percentage of memory that can be assigned for IPsec processing.
Default N/A
system log-cpu-interval
Description Log occurrences where the CPU is at a high usage for a specified duration.
Replace seconds with the number of consecutive seconds that the CPU must be at a high
usage level before a log event is created.
system module-ctrl-cpu
Description Throttle CLI and SNMP output when control CPU utilization reaches a specific threshold.
Parameter Description
low Throttles CLI and SNMP output when control CPU utilization reaches
10 percent. This is the most aggressive setting.
medium Throttles CLI and SNMP output when control CPU utilization reaches
25 percent.
high Throttles CLI and SNMP output when control CPU utilization reaches
45 percent. This is the least aggressive setting.
Usage The command takes effect only for new CLI sessions that are started after you enter the
com- mand. After entering the command, close currently open CLI sessions and start a new
one.
system per-vlan-limit
Description Configure the packet flooding limit per VLAN.
The limit applies to each VLAN. No individual can exceed the specified limit.
To configure a global limit for all VLANs, use “system all-vlan-limit” on page 195.
Parameter Description
bcast Configure the limit for broadcast packets.
ipmcast Configure the limit for IP multicast packets.
mcast Configure the limit for multicast packets.
unknown-ucast Configure the limit for unknown unicast packets.
limit Configure the number of packets per second (1-65535).
Example The following example sets the packet limit to 5000 broadcast packets per second:
system promiscuous-mode
Description Enable the system to pass traffic in promiscuous mode.
This setting enables an interface to pass all received traffic directly to the CPU, instead of
passing only the packets that were intended for that interface. Promiscuous mode is
commonly used as a tool to help diagnose network connectivity problems.
system resource-usage
Description Change the capacity of a system resource.
Command Description
resource-type Specifies the resource type and the maximum allowed:
• auth-portal-html-file-size num – Maximum file size allowed for AAM HTML
files (4-120 Kbytes).
• auth-portal-image-file-size num – Maximum file size allowed for AAM
portal image files (1-80 Kbytes).
• class-list-ac-entry-count - Maximum SNI entries allowed per ACOS device
for Aho-Corasik class-lists (when used for SSL Insight bypass).
• class-list-ipv6-addr-count - Maximum number of IPv6 addresses allowed
within each IPv6 class list (524288-1048576).
• l4-session-count num – Maximum number of Layer 4 sessions supported (32768
- 524288).
• max-aflex-file-size num – Maximum size of an aFleX script in Kbytes (16-256).
The default maximum allowable file size is 32K.
Usage To place a change to l4-session-count into effect, a reboot is required. A reload will not
place this change into effect. For changes to any of the other system resources, a reload is
required but a reboot is not required.
system template
Description Globally applies a template to the ACOS device.
Default N/A
Usage This command applies on only to certain template types. For each valid option, a section in
the configuration guide describes it use.
system ve-mac-scheme
Description Configure MAC address assignment for Virtual Ethernet (VE) interfaces.
Parameter Description
round-robin In the shared partition, this option assigns MAC addresses in round-robin fashion, beginning with the
address for port 1. Each new VE, regardless of the VE number, is assigned the MAC address of the
next Ethernet data port. For example:
• The MAC address of Ethernet data port 1 is assigned to the first VE you configure.
• The MAC address of Ethernet data port 2 is assigned to the second VE you configure.
• The MAC address of Ethernet data port 3 is assigned to the third VE you configure.
This process continues until the MAC address of the highest-numbered Ethernet data port on the
ACOS device is assigned to a VE. After the last Ethernet data port’s MAC address is assigned to a
VE, MAC assignment begins again with Ethernet data port 1. The number of physical Ethernet data
ports on the ACOS device differs depending on the ACOS model.
This option is not supported in L3V partitions.
system-mac In the shared partition, this option assigns the system MAC address (the MAC address of Ethernet
data port 1) to all VEs.
In an L3V partition, this option allocates a system MAC for the partition and assigns the system MAC
address of the partition to all VLANs and VEs in the partition. This is useful when configuring cross
con- nect between partitions.
hash-based In the shared partition, this option causes ACOS to use a hash value based on the VE number to
select an Ethernet data port, and assigns that data port’s MAC address to the VE. This method
always assigns the same Ethernet data port’s MAC address to a given VE number, on any model,
regardless of the order in which VEs are configured.
This option is not supported in L3V partitions.
Default hash-based
Usage This command can be configured only in the shared partition, not in L3V partitions. A
reload or reboot is required to place the change into effect.
Example Below is an example of the system-mac parameter and how it is used with L3V
partitions. First, assume we have partitions “p1” and “P2” on the device, then execute the
command:
After rebooting or reloading the device, examine the MAC addresses to see the mac-scheme
applied on the VEs.
system-jumbo-global enable-jumbo
Description Globally enable jumbo frame support. In this release, a jumbo frame is an Ethernet frame
that is more than 1522 bytes long.
NOTE: Jumbo frames are not supported on all platforms. For detailed information, refer to
the Release Notes.
NOTE: This is the only command required to enable jumbo support on FTA models. See
the Usage section below for details on enabling jumbo support on non-FTA mod-
els.
Default Disabled
ments, regardless of the MTU set on the outbound interface. If it is less than 1500
bytes, it will be fragmented into the configured MTU.
• Setting the MTU on an interface indirectly sets the frame size of incoming packets
to the same value. (This is the maximum receive unit [MRU]).
• In previous releases, the default MTU is 1500 and can not be set to a higher value.
CAUTION: On non-FTA models, after you enable (or disable) jumbo frame support, you must
save the configuration (write memory command) and reboot (reboot com-
mand) to place the change into effect.
If jumbo support is enabled on a non-FTA model and you erase the startup-config, the
device is rebooted after the configuration is erased.Configuration mode.
system-reset
Description Restore the ACOS device to its factory default settings.
Syntax system-reset
Default N/A
Usage This command is helpful when you need to redeploy an ACOS device in a new
environment or at a new customer site, or you need to start over the configuration at the
same site.
The command does not automatically reboot or power down the device. The device
continues to operate using the running-config and any other system files in memory, until
you reboot or power down the device.
Reboot the ACOS device to erase the running-config and place the system reset into effect.
Example The following commands reset an ACOS device to its factory default configuration,
then reboot the device to erase the running-config:
ACOS(config)#system-reset
ACOS(config)#end
ACOS#reboot
tacacs-server host
Description Configure TACACS+ for authorization and accounting. If authorization or accounting is
spec- ified, the ACOS device will attempt to use the TACACS+ servers in the order they are
config- ured. If one server fails to respond, the next server will be used.
Parameter Description
hostname Host name of the TACACS+ server. If a host name is used, make
sure a DNS server has been configured.
ipaddr IP address of the TACAS+ server.
secret-string Password, 1-128 characters, required by the TACACS+ server for
authentication requests.
portnum The port used for setting up a connection with a TACACS+ server.
The default port is 49.
seconds The maximum number of seconds allowed for setting up a connec-
tion with a TACACS+ server. You can specify 1-12 seconds.
The default timeout is 12 seconds.
Usage You can configure up to 2 TACACS+ servers. The servers are used in the order in which
you add them to the configuration. Thus, the first server you add is the primary server. The
sec- ond server you add is the secondary (backup) server. Enter a separate command for
each of the servers. The secondary server is used only if the primary server does not
respond.
Example The following command adds a TACACS+ server "192.168.3.45" and sets its shared secret as
"SharedSecret":
Example The following command adds a TACACS+ server "192.168.3.72", sets the shared secret
as "NewSecret", sets the port number as 1980, and sets the connection timeout value as 6
sec- onds:
ACOS(config)#no tacacs-server
tacacs-server monitor
Description Check the status of TACACS+ servers.
Parameter Description
seconds Frequency (in seconds) that you want the ACOS device to check the
status of the TACACS+ server. You can specify 1 - 120 seconds.
Default Status checking of the TACACS+ server is not enabled. When enabled, the default interval
is 60 seconds.
Usage When TACACS+ server monitoring is configured, the ACOS device sends a TACACS+
monitor request, which contains the user name and password to the server in order to log
into the device and check if the server is available. If it is, then the
last_available_timestamp will be updated with current time.
• If a user login authentication request arrives at the ACOS device, then ACOS will send
the request to the TACACS+ server that has the most recent
last_available_timestamp value.
• If the user’s login attempt is successful, then timestamp for that server will
be updated to the current time.
• However, if the user authentication request fails, then ACOS will send the request
to the secondary TACACS+ server.
• To enable this feature, you must configure the user name and password for the
TACACS+ server’s administrative account. While a simple server port “ping” could
be used to check the status, this is not recommended because it could cause the
ACOS device to be mistakenly seen as an attacker, thus causing it to be added to
the ACL.
techreport
Description Configure automated collection of system information. If you need to contact Technical Sup-
port, they may ask you to for the techreports to help diagnose system issues.
Parameter Description
interval minutes Specifies how often to collect new information. You can specify 15-120 minutes.
The default interval is 15 minutes.
disable Disable automated collection of system information.
Automated collection of system information is enabled by default.
priority-partition name Configure the specified partition to automatically collect system information.
Default Automated collection of system information is enabled by default. The default interval is 15
minutes.
Usage The ACOS device saves all techreport information for a given day in a single file.
Timestamps identify when each set of information is gathered. The ACOS device saves
techreport files for the most recent 31 days. Each day’s reports are saved in a separate file.
The techreports are a light version of the output generated by the show techsupport
command. To export the information, use the show techsupport command. (See “show
techsupport” on page 355.)
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
terminal
Description Set the terminal configuration.
width lines
}
Parameter Description
auto-size Automatically adjusts the length and width of the terminal display.
Auto-sizing is enabled by default.
gslb-prompt options Enables display of the ACOS device’s role within a GSLB group at the CLI prompt.
• disable - disables display of the GSLB group status.
• group-role symbol - Displays “Member” or “Master” in the CLI prompt; for example:
ACOS:Master(config)#
• symbol - Displays “gslb” in the CLI prompt after the name of the ACOS device;
for example:
ACOS-gslb:Master(config)#
editing Enables command editing.
This feature is enabled by default.
history [size number] Enables the command history and specifies the number of commands it can contain, 0-
1000.
By default, history is enabled for up to 256 commands.
idle-timeout minutes Specifies the number of minutes a CLI session can be idle before it times out and is termi-
nated, 0-60 minutes. To disable timeout, enter 0.
The default idle timeout is 15 minutes.
length number Specifies the number of lines to display per page, 0-512. To disable paging, enter 0.
The default length is 24 lines.
prompt options See “Using the CLI” on page 1.
width lines Specifies the number of columns to display, 0-512. To use an unlimited number of col-
umns, enter 0.
The default width is 80 columns.
ACOS(config)#terminal idle-timeout 30
tftp blksize
Description Change the TFTP block size.
Replace bytes with the Maximum packet length the ACOS TFTP client can use when sending
or receiving files to or from a TFTP server. You can specify from 512-32768 bytes.
Usage Increasing the TFTP block size can provide the following benefits:
• TFTP file transfers can occur more quickly, since fewer blocks are required to a send a
file.
• File transfer errors due to the server reaching its maximum block size before a file
is transferred can be eliminated.
To determine the maximum file size a block size will allow, use the following formula:
1K-blocksize = 64MB-filesize
Increasing the TFTP block size of the ACOS device only increases the maximum block size
supported by the ACOS device. The TFTP server also must support larger block sizes. If the
block size is larger than the TFTP server supports, the file transfer will fail and a
communication error will be displayed on the CLI terminal.
If the TFTP block size is larger than the IP Maximum Transmission Unit (MTU) on any
device involved in the file transfer, the TFTP packets will be fragmented to fit within the
MTU. The fragmentation will not increase the number of blocks; however, it can re-add
some overhead to the overall file transmission speed.
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command.
Example The following commands display the current TFTP block size, increase it, then verify
the change:
ACOS(config)#show tftp
TFTP client block size is set to 512
ACOS(config)#tftp blksize 4096
ACOS(config)#show tftp
TFTP client block size is set to 4096
timezone
Description Configure the time zone on your system.
Parameter Description
zone Specify the time zone.
Enter timezone ? at the CLI prompt to see a list of available time
zones.
nodst Disable daylight savings time adjustments for the time on your sys-
tem.
Default GMT
Usage If you use the GUI or CLI to change the ACOS timezone or system time, the statistical
data- base is cleared. This database contains general system statistics (performance,
and CPU, memory, and disk utilization) and SLB statistics.
Example The following example sets the time zone to America/Los_Angeles. Daylight savings time
adjustments will be made.
ACOS(config)#timezone America/Los_Angeles
tx-congestion-ctrl
Description Configure looping on the polling driver, on applicable models.
NOTE: This command can impact system performance. It is recommended not to use this
command unless advised by technical support.
Default 1
upgrade
Description Upgrade the system.
Parameter Description
cf Write the upgrade image to the compact flash, replacing the image currently at that
location.
hd Write the upgrade image to the hard disk, replacing the image currently at that loca-
tion.
pri Replace the primary image on the specified location (compact flash or hard disk).
sec Replace the secondary image on the hard disk.
local image-name Use the specified upgrade image from the local VCS image repository.
Use show vcs images to view a list of available local images.
use-mgmt-port Uses the management interface as the source interface for the connection to the
remote device. The management route table is used to reach the device. By default,
the ACOS device attempts to use the data route table to reach the remote device
through a data interface.
url File transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter to display a prompt
for each part of the URL. If you enter the entire URL and a password is required, you
will still be prompted for the password. The password can be up to 255 characters
long.
To enter the entire URL:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• http://[user@]host/file
• https://[user@]host/file
• sftp://[user@]host/file
staggered-upgrade-mode Use VCS staggered upgrade mode.
reboot-after-upgrade Reboot the system after the upgrade is complete.
Default N/A
Usage For complete upgrade instructions, see the release notes for the ACOS release to which
you plan to upgrade.
vcs
The vcs commands are available only when aVCS is enabled. To enable aVCS, use the vcs
enable command.
For more information, see “aVCS CLI Commands” in Configuring ACOS Virtual Chassis Systems.
ve-stats
Description Enable statistics collection for Virtual Ethernet (VE) interfaces.
Default Disabled
Usage If the ACOS device is a member of an aVCS virtual chassis, use the device-context
com- mand to specify the device in the chassis to which to apply this command.
vlan
Description Configure a virtual LAN (VLAN). This command changes the CLI to the configuration level
for the VLAN.
If the ACOS device is a member of an aVCS virtual chassis, specify the vlan-id as follows:
DeviceID/vlan-id
Default VLAN 1 is configured by default. All Ethernet data ports are members of VLAN 1 by default.
Usage You can add or remove ports in VLAN 1 but you cannot delete VLAN 1 itself.
For information about the commands available at the VLAN configuration level, see the
“Config Commands: VLAN” chapter in the Network Configuration Guide.
Example The following command adds VLAN 69 and enters the configuration level for that VLAN:
ACOS(config)# vlan 69
ACOS(config-vlan:69)#
Example You cannot have duplicate VLANs configured across partitions. In this example, VLAN 10
is configured in the shared partition:
ACOS(config)# vlan 10
ACOS(config-vlan:10)# exit
ACOS(config)#
If you attempt to configure VLAN 10 in an L3V partition, you will receive an error message:
ACOS(config)# active-partition p2
Current active partition: p2
ACOS[p2]# configure ACOS[p2]
(config)# vlan 10
This VLAN or Port is owned by another partition.
vlan-global enable-def-vlan-l2-forwarding
Description Enable Layer 2 forwarding on the default VLAN (VLAN 1).
Default Layer 2 forwarding is disabled on VLAN 1, on ACOS devices deployed in route mode.
When Layer 2 forwarding on VLAN 1 is disabled, broadcast, multicast, and unknown unicast
packets are dropped instead of being forwarded. Learning is also disabled on the VLAN.
However, packets for the ACOS device itself (ex: LACP) are not dropped.
vlan-global l3-vlan-fwd-disable
Description Globally disable Layer 3 forwarding between VLANs.
Default By default, the ACOS device can forward Layer 3 traffic between VLANs.
Usage This option is applicable only on ACOS devices deployed in gateway (route) mode. If
the option to disable Layer 3 forwarding between VLANs is configured at any level, the
ACOS device can not be changed from gateway mode to transparent mode, until the
option is removed.
• Depending on the granularity of control required for your deployment, you can
disable Layer 3 forwarding between VLANs at any of the following configuration
levels:
• Global – Layer 3 forwarding between VLANs is disabled globally, for all VLANs. (Use
this command at the Configuration mode level.)
• Individual interfaces – Layer 3 forwarding between VLANs is disabled for incoming
traf- fic on specific interfaces.
• Access Control Lists (ACLs) – Layer 3 forwarding between VLANs is disabled for all traffic
that matches ACL rules that use the l3-vlan-fwd-disable action.
vrrp-a
Description Configure VRRP-A high availability for ACOS.
For more information, see “VRRP-A CLI Commands” in Configuring VRRP-A High Availability.
waf
Description Configure Web Application Firewall (WAF) parameters. See the Web Application Firewall
Guide.
web-category
Description Configure Web Category classification. See “Config Commands: Web Category” in the Com-
mand Line Interface Reference for ADC.
web-service
Description Configure web services.
Parameter Description
auto-redir Enables requests for the unsecured port (HTTP) to be automatically redirected to the
secure port (HTTPS).
This feature is enabled by default.
axapi-session-limit Specifies the maximum number of aXAPI sessions that can be run simultaneously
num (1- 100).
The default is 30.
axapi-timeout-policy Specifies the number of minutes an aXAPI session or GUI session can remain idle
idle minutes before being terminated. Once the aXAPI session is terminated, the session ID
generated by the ACOS device for the session is no longer valid. You can specify 0-60
minutes. If you spec- ify 0, sessions never time out.
The default timeout is 10 minutes.
port port Specifies the port number for the unsecured (HTTP) port.
The default HTTP port is 80.
secure Generate a new certificate for your ACOS device when it is booted for the first time.
Use the certificate or private-key parameters to load an externally-
generated certificate or private-key. For the URL, you can specify:
• tftp://host/file
• ftp://[user@]host[port:]/file
• scp://[user@]host/file
• sftp://[user@]host/file
Use generate or regenerate for certificate creation. You must specify the domain
name, and can optionally specify the country and state location.
Parameter Description
secure-port port Specifies the port number for the secure (HTTPS) port.
The default HTTPS port is 443.
server disable Disables the HTTP server.
This sever is enabled by default.
secure-server disable Disables the HTTPS server.
This sever is enabled by default.
Usage If you disable HTTP or HTTPS access, any sessions on the management GUI are immediately
terminated.
write
Description Write the current running-config. See the following related commands:
• “write force” on page 56
• “write memory” on page 57
• “write terminal” on page 59
This chapter lists the CLI commands for DNS Security Extensions (DNSSEC):
Common commands available at all configuration levels are available elsewhere in this guide:
NOTE: For information about Hardware Security Module (HSM) commands, see “Config Com-
mands: Hardware Security Module” on page 219.
• dnssec standalone
• dnssec template
dnssec standalone
Description Enable the ACOS device to run DNSSEC without being a member of a GSLB controller group.
Default Disabled
Usage GSLB is still required. The ACOS device must be configured to act as a GSLB controller, and
as an authoritative DNS server for the GSLB zone.
dnssec template
Description Configure a DNSSEC template.
This command changes the CLI to the configuration level for the specified DNSSEC template,
where the following commands are available.
Command Description
[no] algorithm Cryptographic algorithm to use for encrypting DNSSEC keys.
{RSASHA1 | RSASHA256 | RSASHA512}
The default algorithm is RSASHA256.
[no] combinations-limit num Maximum number of combinations per Resource Record Set (RRset),
where RRset is defined as all the records of a particular type for a
particu- lar domain, such as all the “quad-A” (IPv6) records for
www.example.com. You can specify 1-65535.
The default number of combinations is 31.
[no] dnskey-ttl seconds Lifetime for DNSSEC key resource records. The TTL can range from 1-
864,000 seconds.
The default is 14,400 seconds (4 hours).
[no] enable-nsec3 Enables NSEC3 support. This is disabled by default.
[no] hsm template-name Binds a Hardware Security Module (HSM) template to this DNSSEC tem-
plate.
[no] ksk keysize bits Key length for KSKs. You can specify 1024-4096 bits.
The default is 2048 bits.
[no] ksk lifetime seconds Lifetime for KSKs, 1-2147483647 seconds (about 68 years). The
[rollover-time seconds] roll- over-time specifies how long to wait before generating a
standby key to replace the current key. The rollover-time setting
also can be
1-2147483647 seconds. Generally, the rollover-time setting should
be shorter than the lifetime, to allow the new key to be ready when
needed.
The default is 31536000 seconds (365 days), with rollover-time
30931200 seconds (358 days)
Command Description
[no] return-nsec-on-failure Returns an NSEC or NSEC3 record in response to a client request for an
invalid domain. As originally designed, DNSSEC would expose the list of
device names within a zone, allowing an attacker to gain a list of network
devices that could be used to create a map of the network.
This is enabled by default.
[no] signature-validity-period Period for which a signature will remain valid. The time can range from 5
days to 30 days.
The default is 10 days.
[no] zsk lifetime seconds Lifetime for ZSKs, 1-2147483647 seconds. The rollover-time
[rollover-time seconds] specifies how long to wait before generating a standby key to replace the
current key. The rollover-time setting also can be 1-2147483647
seconds. Generally, the rollover-time setting should be shorter
than the life- time, to allow the new key to be ready when needed.
The default is 7776000 seconds (90 days), with rollover-time
7171200 seconds (83 days).
Because these are operational commands, they are not added to the running-config or saved to the startup-config.
Replace zone-name with the name of the zone for which to delete DNSKEY resource
records. If you do not specify a zone name, the DNSKEY resource records for all child
zones are deleted.
Default N/A
dnssec ds delete
Description Delete Delegation Signer (DS) resource records for child zones.
Replace zone-name with the name of the zone for which to delete DS resource records.
If you do not specify a zone name, the DS resource records for all child zones are deleted.
Default N/A
dnssec key-rollover
Description Perform key change (rollover) for ZSKs or KSKs.
Parameter Description
zone-name Name of the child zone for which to regenerate keys. If you do not spec-
ify a zone name, all child zones are re-signed.
KSK Regenerates key-signing keys (KSKs).:
{ds-ready-in-parent-zone | start}
• ds-ready-in-parent-zone – Indicates that the DS
resource record has already been transferred to the parent zone,
so it is ok to remove the old active key.
• start – Immediately begins KSK rollover.
ZSK start Immediately begins ZSK rollover.
Default N/A
dnssec sign-zone-now
Description Force re-signing of zone-signing keys (ZSKs).
Replace zone-name with the name of the child zone for which to re-sign the ZSKs. If you
do not specify a zone name, all child zones are re-signed.
Default N/A
Parameter Description
zone-name The name of the child zone. If you do not specify a zone name,
DNSKEY resource records for all child zones are displayed.
partition Display the information for a specific partition.
partition-name
show dnssec ds
Description Show the Delegation Signer (DS) resource records for child zones.
Parameter Description
zone-name The name of the child zone. If you do not specify a zone name,
DS resource records for all child zones are displayed.
partition Display the information for a specific partition.
partition-name
Parameter Description
default | The name of the template. If you do not specify a template name,
template-name all DNSSEC templates are displayed.
partition Display the information for a specific partition.
partition-name
This chapter lists the CLI commands for Simple Network Management Protocol
• snmp-server SNMPv1-v2c
• snmp-server SNMPv3
• snmp-server community
• snmp-server contact
• snmp-server enable
• snmp-server engineID
• snmp-server group
• snmp-server host
• snmp-server location
• snmp-server slb-data-cache-timeout
• snmp-server user
• snmp-server view
Common commands available at all configuration levels are available elsewhere in this guide:
snmp-server SNMPv1-v2c
Description Define an SNMPv1 or SNMPv2c community. The members of the community can
gain access to the SNMP data available on this device.
This command changes the CLI to an SNMP community configuration mode, where the
following commands are available:
Parameter Description
community read string Define a read-only community string (1-31 charac-
ters).
oid oid-value Object ID.
This option restricts the objects that the ACOS device
returns in response to GET requests. Values are
returned only for the objects within or under the
specified OID.
remote { Restricts SNMP access to a specific remote host
ipv4addr [/mask-length | mask] | or subnet.
ipv6addr [mask] |
When you use this option, only the specified host or
DNS-remote-host
subnet can receive SNMP data from the ACOS
}
device by sending a GET request to this community.
Default The configuration does not have any default SNMP communities.
Usage All SNMP communities are read-only. Read-write communities are not supported. The OID
for A10 Thunder Series and AX Series objects is 1.3.6.1.4.1.22610.
Example The following commands enable SNMP and define community string “a10community”:
Hosts in 10.10.10.0 /24 and 20.20.20.0 /24 can access the entire MIB tree using the
“a10community” community string. Hosts in 30.30.30.0 /24 and 40.40.40.0 /24 can access the
MIB sub-tree 1.2.3 using the community string “a10community.”
snmp-server SNMPv3
Description Define an SNMPv3 user.
Parameter Description
username Specifies the SNMP user name.
groupname Specifies the group to which the SNMP user belongs.
v3 Specifies SNMP version 3.
auth {md5 | sha} Specifies the encryption method to use for user authentication.
• md5 - Uses Message Digest Algorithm 5 (MD5) encryption.
• sha - Uses Security Hash Algorithm (SHA) encryption.
auth-password Password for user authentication (8-31 characters).
priv {aes | des} Specifies the encryption method to use for user privacy.
• aes - Uses Advanced Encryption Standard (AES) algorithm.
This uses a fixed block size of 128 bits, and has a key size of
128, 192, or 256 bits. AES encryption supersedes DES encryp-
tion.
• des - Uses Data Encryption Standard (DES) algorithm to
apply a 56-bit key to each 64-bit block of data. This is
considered strong encryption.
Usage SNMPv3 enables you to configure each user with a name, authentication type with an
asso- ciated key, and privacy type with an associated key.
• Authentication (auth) is performed by using the user’s authentication key to sign the
message being sent. This can be done using either MD5 or SHA encryption; the
authentication key is generated using the specified encryption method and the speci-
fied auth-password.
• Encryption (priv) is performed by using a user’s privacy key to encrypt the data
por- tion of the message being sent. This can be done using either AES or DES
encryption; the authentication key is generated using the specified encryption
method and the specified priv-password.
Example The following example shows how to configure an SNMP user “exampleuser”, who is a
mem- ber in “examplegroup”. Authentication using MD5 encryption for “authpassword” is
config- ured, along with message encryption using AES or “privpassword”.
snmp-server community
Description Deprecated command to configure an SNMP community string.
snmp-server contact
Description Configure SNMP contact information.
Replace contact-name with the SNMP contact; for example, an E-mail address.
By default, the SNMP sysContact OID value is synchronized among all member ACOS devices
of an aVCS virtual chassis. You can disable this synchronization, on an individual device basis.
NOTE: After configuring this option for an ACOS device, if you disable aVCS on that device,
the running-config is automatically updated to continue using the same
sysCon- tact value you specified for the device. You do not need to reconfigure
the sysCon- tact on the device after disabling aVCS.
Example The following command defines the SNMP contact with the E-mail address
“exampleu- [email protected]”:
snmp-server enable
Description Enable the ACOS device to accept SNMP MIB data queries and to send SNMP v1/v2c traps.
To use SNMP on the device, you must enter this command. Enter this command first, then
enter the other snmp-server commands to further configure the feature.
Parameter Description
traps Specify the traps you want to enable.
all Enable all the traps described below.
NOTE: The all option can be specified at any command level to enable all SNMP traps at that
level.
gslb Enable GSLB group traps:
• group – Enable group-related traps.
• service-ip – Enable traps related to service-IPs.
• site – Enable site-related traps.
• zone – Enable zone-related traps.
Parameter Description
routing Enable the routing group traps:
• bgp – Enables traps for BGP routing:
• bgpEstablishedNotification - A BGP neighbor transitions to the Established state.
• bgpBackwardTransNotification - a BGP neighbour transitions from a higher state to a
lower state; for example, if the BGP neighbour’s state transitions from Established to OpenCon-
firm or from Connect to Idle.
• isis – Enables traps for IS-ID routing:
• isisAdjancencyChange
• isisAreaMismatch
• isisAttemptToExceedMaxSequence
• isisAuthenticationFailure
• isisAuthenticationTypeFailure
• isisCorruptedLSPDetected
• isisDatabaseOverload
• isisIDLenMismatch
• isisLSPTooLargeToPropagate
• isisManualAddressDrops
• isisMaxAreaAddressesMismatch
• isisOriginatingLSPBufferSizeMismatch
• isisOwnLSPPurge
• isisProto9colSupportedMismatch
• isisRejectedAdjacency
• isisSequenceNumberSkip
• isisVersionSkew
• ospf – Enables traps for OSPF routing:
• ospfIfAuthFailure
• ospfIfConfigError
• ospfIfRxBadPacket
• ospfIfStateChange
• ospfLsdbApproachingOverflow
• ospfLsdbOverflow
• ospfMaxAgeLsa
• ospfNbrStateChange
• ospfOriginateLsa
• ospfTxRetransmit
• ospfVirtIfAuthFailure
• ospfVirtIfConfigError
• ospfVirtIfRxBadPacket
• ospfVirtIfStateChange
• ospfVirtIfTxRetransmit
• ospfVirtNbrStateChange
Parameter Description
slb Enable the SLB group traps:
• application-buffer-limit – Indicates that the configured SLB application buffer threshold
has been exceeded. (See “monitor” on page 158.)
• server-conn-limit – Indicates that an SLB server has reached its configured connection limit.
• server-conn-resume – Indicates that an SLB server has reached its configured connection-
resume value.
• server-disabled – Indicates that an SLB server has been disabled.
• server-down – Indicates that an SLB server has gone down.
• server-selection-failure – Indicates that SLB was unable to select a real server
for a request.
• server-up – Indicates that an SLB server has come up.
• service-conn-limit – Indicates that an SLB service has reached its configured connection
limit.
• service-conn-resume – Indicates that an SLB service has reached its configured connection-
resume value.
• service-down – Indicates that an SLB service has gone down.
• service-group-down – Indicates that an SLB service group has gone down.
• service-group-member-down – Indicates that an SLB service group member has gone down.
• service-group-member-up – Indicates that an SLB service group member has come up.
• service-group-up – Indicates that an SLB service group has come up.
• service-up – Indicates that an SLB service has come up.
• vip-connlimit – Indicates that the connection limit configured on a virtual server has
been exceeded.
• vip-connratelimit – Indicates that the connection rate limit configured on a virtual
server has been exceeded.
• vip-down – Indicates that an SLB virtual server has gone down.
• vip-port-connlimit – Indicates that the connection limit configured on a virtual port
has been exceeded.
• vip-port-connratelimit – Indicates that the connection rate limit configured on a
virtual port has been exceeded.
• vip-port-down – Indicates that an SLB virtual service port has gone down.
• vip-port-up – Indicates that an SLB virtual service port has come up. An SLB virtual
server’s ser- vice port is up when at least one member (real server and real port) in the service
group bound to the virtual port is up.
• vip-up – Indicates that an SLB virtual server has come up.
Parameter Description
snmp Enable SNMP group traps:
• linkdown – Indicates that an Ethernet interface has gone down.
• linkup – Indicates that an Ethernet interface has come up.
ssl Enable the SSL group traps:
• server-certificate-error – Indicates a certificate error.
system Enable the system group traps:
• control-cpu-high – Indicates that the control CPU utilization is higher than the
configured threshold. (See “monitor” on page 158.)
• data-cpu-high – Indicates that data CPU utilization is higher than the configured
threshold. (See “monitor” on page 158.)
• fan – Indicates that a system fan has failed. Contact A10 Networks.
• file-sys-read-only – Indicates that the file system has entered read-only mode.
• high-disk-use – Enables system high disk usage traps.
• high-memory-use – Indicates that the memory usage on the ACOS device is higher than
the configured threshold. (See “monitor” on page 158.)
• high-temp – Indicates that the temperature inside the ACOS chassis is higher than the
config- ured threshold. (See “monitor” on page 158.)
• license-management – Enables license management traps.
• packet-drop – Indicates that the number of dropped packets during the previous 10-
second interval exceeded the configured threshold. (See “monitor” on page 158.)
NOTE: This trap is not applicable to some device types. The trap is applicable to Thunder Series
and AX Series hardware-based models and software-based models.
• power – Indicates that a power supply has failed. Contact A10 Networks.
• pri-disk – Indicates that the primary Hard Disk has failed or the RAID system has failed. In
dual- disk models, the primary Hard Disk is the one on the left, as you are facing the front of the
ACOS device chassis.
• restart – Indicates that the ACOS device is going to reboot or reload.
• sec-disk – Indicates that the secondary Hard Disk has failed or the RAID system has failed.
The secondary Hard Disk is the one on the right, as you are facing the front of the ACOS device
chassis.
NOTE: This trap applies only to models that use disk drives.
• shutdown – Indicates that the ACOS device has shut down.
• start – Indicates that the ACOS device has started.
Default The SNMP service is disabled by default and all traps are disabled by default.
Usage For security, SNMP and SNMP trap are disabled on all data interfaces. Use the enable-
man- agement command to enable SNMP on data interfaces. (See “enable-
management” on page 112.)
If the ACOS device is a member of an aVCS virtual chassis, use the device-context
command to specify the device in the chassis to which to apply this command. This is only
valid for SNMP routing (snmp-server enable traps routing trap-name) and
network (snmp-server enable traps network trap-name) traps.
Example The following commands enable SLB traps server-conn-limit and server-conn-resume:
snmp-server engineID
Description Set the SNMPv3 engine ID of this ACOS device.
snmp-server group
Description Configure an SNMP group for SNMPv3.
Parameter Description
group-name Specifies the name of the SNMP group.
auth Uses packet authentication but does not encrypt the packets.
(This is the authNoPriv security level.)
noauth Does not use any authentication of packets.
(This is the noAuthNoPriv security level.)
Parameter Description
priv Uses packet authentication and encryption.
(This is the authPriv security level.)
read view-name Specifies the name of a read-only view for accessing the MIB
object values (1-31 characters).
Views can be created using the snmp-server view command.
Default The configuration does not have any default SNMP groups.
Example The following commands add SNMP v3 group “group1” with authPriv security and read-
only view “view1”:
snmp-server host
Description Configure an SNMP v1/v2c trap receiver.
Parameter Description
trap-receiver Hostname or IP address of the remote device to which
traps will be sent.
version {v1 | v2c | v3} SNMP version. If you omit this option, the trap receiver
can use SNMP v1 or v2c.
community-string Community string for the traps.
udp-port port-num UDP port to which the ACOS device will send the trap.
Default No SNMP hosts are defined. When you configure one, the default SNMP version is v2c
and the default UDP port is 162.
Example The following command configures SNMP trap receiver 100.10.10.12 to use
community string “public” and UDP port 166 for SNMP v2c traps.
snmp-server location
Description Configure SNMP location information.
snmp-server slb-data-cache-timeout
Description Configure the SLB data cache timeout.
Replace seconds with the number of seconds (5-120) for the SLB data cache timeout.
Default 60 seconds.
Example The following example sets the SLB data cache timeout to 45 seconds.
snmp-server user
Description Deprecated command to configure an SNMPv3 user.
snmp-server view
Description Configure an SNMP view.
Parameter Description
view-name Name of the SNMP view.
oid MIB family name or OID.
oid-mask OID mask. Use hex octets, separated by a dot ( . ) character.
Parameter Description
included MIB family is included in the view.
excluded MIB family is excluded from the view.
Default N/A
Example The following command adds SNMP view “view1” and includes all objects in the 1.3.6 tree:
In addition to the command options provided with some show commands, you can use output modifiers to search and filter
the output. See “Searching and Filtering CLI Output” on page 13.
To automatically re-enter a show command at regular intervals, see “repeat” on page 53.
NOTE: The show slb commands are described in a separate chapter. See “SLB Show Com-
mands” in the Command Line Interface Reference for ADC.
• show aam
• show access-list
• show active-partition
• show admin
• show aflex
• show arp
• show audit
• show axdebug capture
• show axdebug config
• show axdebug config-file
• show axdebug file
• show axdebug filter
• show axdebug status
• show backup
• show bfd
• show bgp
• show bootimage
• show bpdu-fwd-group
• show bridge-vlan-group
• show bw-list
• show class-list
• show clns
• show clock
• show config
• show config-block
• show context
• show core
• show cpu
• show debug
• show disk
• show dns cache
• show dns statistics
• show dnssec
• show dumpthread
• show environment
• show errors
• show event-action
• show fail-safe
• show glid
• show gslb
• show hardware
• show health
• show history
• show hsm
• show icmp
• show icmpv6
• show interfaces
• show interfaces brief
• show interfaces media
• show interfaces statistics
• show isis
• show json-config
• show json-config-detail
• show json-config-with-default
• show key-chain
• show lacp
• show lacp-passthrough
• show license
• show license-debug
• show license-info
• show lldp neighbor statistics
• show lldp statistics
• show local-uri-file
• show locale
• show log
• show mac-address-table
• show management
• show memory
• show mirror
• show monitor
• show netflow
• show ntp
• show object-group
• show overlay-mgmt-info
• show overlay-tunnel
• show partition
• show partition-config
• show partition-group
• show pbslb
• show pki
• show poap
• show vlans
• show vpn
• show vrrp-a
• show waf
• show web-category
show aam
Description Display information for Application Access Management (AAM). See the Application Access
Management Guide.
show access-list
Description Display the configured Access Control Lists (ACLs). The output lists the configuration
com- mands for the ACLs in the running-config.
Parameter Description
ipv4 | ipv6 IP address type.
acl-id ACL name or number.
Mode All
Example The following command displays the configuration commands for ACL 1:
NOTE: The ACL Hits counter is not applicable to ACLs applied to the management port.
show active-partition
Description This command is described in the Configuring Application Delivery Partitions guide.
show admin
Description Display the administrator accounts.
Parameter Description
admin-name Administrator name.
detail Shows detailed information about the admin account.
session Shows the current management sessions.
Example The following command lists the admins configured on an ACOS device:
Field Description
UserName Name of the ACOS admin.
Status Administrative status of the account.
Privilege Access privilege level for the account:
• R/W – Read-write. Allows access to all levels of the system.
• R – Read-only. Allows monitoring access to the system but not
config- uration access. In the CLI, this account can only access the
User EXEC and Privileged EXEC levels, not the configuration levels.
In the GUI, this account cannot modify configuration information.
• P.R/W – The admin has read-write privileges within the L3V partition
to which the admin has been assigned. The admin has read-only
privi- leges for the shared partition.
• P.R – The admin has read-only privileges within the L3V partition to
which the admin has been assigned, and read-only privileges for
the shared partition.
• P.En– The admin is assigned to an L3V partition but has permission
only to view service port statistics for real servers in the partition,
and to disable or re-enable the real servers or their service ports.
NOTE: The “P” (partition) privilege levels apply to Application Delivery
Partitions (ADP). For more information, see the Configuring
Application Delivery Partitions guide.
Example The following command lists details for the “admin” account:
Field Description
User Name Name of the ACOS admin.
Status Administrative status of the account.
Privilege Access privilege level for the account:
• R/W – Read-write. Allows access to all levels of the system.
• R – Read-only. Allows monitoring access to the system but not
con- figuration access. In the CLI, this account can only access the
User EXEC and Privileged EXEC levels, not the configuration
levels. In the GUI, this account cannot modify configuration
information.
• Partition-write – The admin has read-write privileges within the
pri- vate partition to which the admin has been assigned. The
admin has read-only privileges for the shared partition.
• Partition-read – The admin has read-only privileges within the pri-
vate partition to which the admin has been assigned, and read-
only privileges for the shared partition.
• Partition-enable-disable – The admin is assigned to a private
parti- tion but has permission only to view service port statistics
for real servers in the partition, and to disable or re-enable the
real servers and their service ports.
Partition Private partition to which the admin is assigned.
Note: A partition name appears only for admins with Partition-write,
Partition-read, or Partition-enable-disable privileges. For other privi-
lege levels, this field is blank.
Access type Management interfaces the admin is allowed to access, which can be
one or more of the following:
• cli
• web
• axapi
GUI role Role assigned to the admin for GUI access.
Note: If the admin is configured using the GUI, assignment of a role
is required. However, if the admin is configured using the CLI, a GUI
access role can not be assigned. In this case, the GUI role is
equivalent to ReadWriteAdmin.
Trusted IP host or subnet address from which the admin must log in.
Host(Netmask)
Lock Status Indicates whether the admin account is currently locked.
Lock Time If the account is locked, indicates how long the account has been
locked.
Unlock Time If the account is locked, indicates how long the account will continue
to be locked.
Password Type Indicates whether the password is encrypted when displayed in the
CLI or GUI and in the startup-config and running-config.
Password The admin’s password.
Example The following command lists all the currently active admin sessions:
Field Description
Id Admin session ID assigned by the ACOS device. The ID applies only to
the current session.
User Name Admin name.
Start Time System time when the admin logged onto the ACOS device to start
the current management session.
Source IP IP address from which the admin logged on.
Type Management interface through which the admin logged on.
Partition Partition that is currently active for the management session.
Authen Indicates the database used to authenticate the admin:
• Local – Admin database on the ACOS device
• RADIUS – Admin database on a RADIUS server
• TACACS – Admin database on a TACACS+ server
Role Indicates the role assigned to the admin for GUI access.
Cfg Indicates whether the admin is at the configuration level.
show aflex
Description Display the configured aFleX scripts.
Mode All
Usage To display the aFleX policies for a specific partition only, use the partition name option.
Example The following command shows the aFleX scripts on an ACOS device:
------------------------------------------------------------
aFleX_Remote No No
aFleX_check_agent No No
aFleX_relay_client Check No
bugzilla_proxy_fix Check Bind
http_to_https Check No
louis No No
Field Description
Total aFleX Total number of aFleX scripts on the ACOS device.
number
Name Name of the aFleX policy.
Syntax Indicates whether the aFleX policy has passed the syntax check per-
formed by the ACOS device:
• Check – The aFleX policy passed the syntax check.
• No – The aFleX policy did not pass the syntax check.
Virtual port Indicates whether the aFleX policy is bound to a virtual port.
show arp
Description Display ARP table entries.
Mode All
Example The following command lists the ARP entry for host 192.168.1.144:
Field Description
Total arp entries Total number of entries in the ARP table. This total includes static and
learned (dynamic) entries.
Age time Number of seconds a dynamic ARP entry can remain in the table
before being removed.
IP Address IP address of the device.
MAC Address MAC address of the device.
Type Indicates whether the entry is static or dynamic.
Age For dynamic entries, the number of seconds since the entry was last
used.
Interface ACOS interface through which the device that has the displayed
MAC address and IP address can be reached.
Vlan VLAN through which the device that has the MAC address can be
reached.
show audit
Description Show the command audit log.
Mode All
Usage The audit log is maintained in a separate file, apart from the system log. The audit log
mes- sages that are displayed for an admin depend upon the admin’s privilege level:
• Admins with Root, Read Write, or Read Only privileges who view the audit log can
view all the messages, for all system partitions. To display the messages for a specific
parti- tion only, use the partition option.
• Admins who have privileges only within a specific partition can view only the audit
log messages related to management of that partition. Admins with partition-
enable-dis- able privileges can not view any audit log entries.
Example Below is a sample output of the command audit log (truncated for brevity):
Parameter Description
partition name Displays files only for a select partition.
file-name Filters the show output for only files that partially match a speci-
fied file-name
Mode All
Mode All
Example This example shows the output of the show axdebug config command:
no incoming
no outgoing
count 3000
length 1518
Mode All
Mode All
Example The following command displays the list of AX debug capture files on the device:
Example The following command displays the packet capture data in file “file123”:
Mode All
Mode All
Example The following example shows the output for the show axdebug status command for all
CPUs:
Mode All
show bfd
Description Display information for Bidirectional Forwarding Detection (BFD).
Parameter Description
neighbors Displays summarized information for BFD neighbors.
detail Displays detailed information for BFD neighbors.
statistics Displays overall statistics for BFD packets.
Mode All
Example The following example shows how to view overall statistics for BFD packets:
Field Description
Our Address ACOS interface associated with the BFD session.
Neighbor Address Neighbor interface associated with the BFD session.
State Shows the local state of the session.
Holdtime Maximum amount of time the ACOS device waits for a BFD control packet from the neighbor.
txint Configured interval at which the ACOS device sends BFD control packets to the neighbor.
mult Maximum number of consecutive times the ACOS device will wait for a BFD control packet from
the neighbor.
diag Diagnostic codes for the local and remote ends of the BFD session.
Field Description
Our Address ACOS interface associated with the BFD session.
Neighbor Address Neighbor interface associated with the BFD session.
Clients Protocol that initiates this BFD session. It can be one or more of the following:
Static, OSPFv2, OSPFv3, IS-IS, or BGP.
Singlehop (or Multihop) BFD session can be either singlehop or multihop.
Echo Indicates whether Echo functionality has been enabled or disabled.
Demand Indicates whether Demand mode functionality has been enabled or disabled.
UDP source port UDP source port used for this BFD session.
Asynchronous mode (or Demand) If configured and running, indicates whether BFD is operating in Asynchronous
mode mode or Demand mode.
Authentication Authentication method. This can be either “None” (if it is not configured) or one
of the following supported authentication schemes:
• Simple password
• Keyed MD5
• Meticulous Keyed MD5
• Keyed SHA1
• Meticulous Keyed SHA1
CPU ID Since BFD traffic is distributed across multiple data CPUs, this CPU ID refers to
the one associated with the current BFD session.
Interface index Interface index associated with the current BFD session. This index is used mostly
for debugging purposes
Local State Shows the local state the session. The state can be one of the following:
• Init
• Up
• AdminDown
• Down
Remote State Shows the remote state the session. The state can be one of the following:
• Init
• Up
• AdminDown
• Down
Local discriminator The local discriminator value that the ACOS device assigns for the current BFD
ses- sion.
Remote discriminator The remote discriminator value that the neighboring router claims.
Config The configured timer values.
Local The configured timer values sent in the last BFD control packet. This value is
deter- mined based on BFD package exchange and negotiation.
Remote The timer values received in the last BFD control packet from the BFD neighbor.
Field Description
Local Multiplier The local multiplier sent in the last BFD packet.
Remote Multiplier The remote multiplier received in the last BFD packet from the neighbor.
Hold Down Time The expiration time after which the BFD session will be brought down. This value is
determined with the negotiated interval value and the remote multiplier value.
Transmit Interval The periodic interval to send BFD control packets.
Local Diagnostic: The diagnostic value sent in the last BFD control packet.
Remote Diagnostic: The diagnostic value received in the last BFD control packet from the neighbor.
Last sent echo sequence number A10 Network’s proprietary sequence number sent in the last echo packet.
Control Packet sent..received Statistics of control packets for this BFD session.
Echo Packet sent...received Statistics of echo packets received for this BFD session.
Field Description
IP Checksum error Number of BFD packets that had an invalid IP checksum.
UDP Checksum error Number of BFD packets that had an invalid UDP checksum.
No session found with your_discriminator Number of BFD packets whose Your Discriminator value did not match a
My Discriminator value on the ACOS device.
Multihop config mismatch A multihop configuration mismatch occurs when an ACOS device receives
a BFD packet with a source or destination that matches an existing BFD
ses- sion. It can also be caused in two other scenarios:
• Local is configured as singlehop, but the packet is received on the
UDP port for multihop.
• Local is configured as multihop, but packet is received on the UDP
port for singlehop.
BFD Version mismatch Number of BFD packets with a different BFD version than the one in use by
the ACOS device.
BFD Packet length field is too small Number of BFD packets whose Length field value was shorter than the
min- imum BFD packet length (24 bytes without authentication or 26 bytes
with authentication).
BFD Packet data is short The packet payload size is smaller than the BFD length value.
BFD Packet DetectMult is invalid The value of the received DetectMult is “0”.
BFD Packet Multipoint is invalid The value of the received multipoint flag is set to “1”.
BFD Packet my_discriminator is invalid Number of BFD packets whose My Discriminator value was invalid.
BFD Packet TTL/Hop Limit is invalid In a singlehop BFD session, the IP time-to-live or IPv6 hop limit value must
be 255. If a value other than 255 is detected, this field is incremented.
BFD Packet auth length is invalid The BFD length without the BFD packet header does not match the
expected authentication length byte value. The number of BFD control
packets have wrong authentication lengths in bytes
BFD Packet auth type mismatch Number of BFD packets carrying an authentication type that does not
match the BFD authentication type configured on the ACOS device.
BFD Packet auth key ID mismatch This field is incremented when the key ID in the authentication header does
not match the one configured on the ACOS device.
BFD Packet auth key mismatch This field is incremented when the received authentication key does not
match the one configured on the ACOS device.
BFD Packet auth seq# invalid This field is incremented when the received authentication sequence num-
ber is not equal to or greater than the sequence number received previ-
ously.
BFD Packet auth failed Number of BFD packets with an incorrect authentication value.
BFD local state is AdminDown Number of BFD packets received while the BFD session was administra-
tively down.
Field Description
BFD Destination unreachable Number of times the destination IP address for a BFD neighbor was
unreachable while the ACOS device was attempting to transmit a BFD
packet to the neighbor.
BFD Other error Number of BFD errors not counted in any of the fields above.
show bgp
Description Display information for Border Gateway Protocol (BGP). See the “Config Commands: Router -
BGP” chapter in the Network Configuration Guide.
show bootimage
Description Display the software images stored on the ACOS device.
Mode All
Example The following command shows the software images on an A10 Thunder Series 4430 device:
ACOS#show bootimage
(* = Default)
Version
-----------------------------------------------
Hard Disk primary 4.0.0.485
Hard Disk secondary 2.7.2-P2-SP6.1 (*)
Compact Flash primary 2.7.2.191 (*)
Compact Flash secondary 2.7.2.191
The asterisk ( * ) indicates the default image for each boot device (hard disk and compact
flash). The default image is the one that the ACOS device will try to use first, if trying to boot
from that boot device. (The order in which ACOS tries to use the image areas is controlled
by the bootimage command. See “bootimage” on page 96.)
show bpdu-fwd-group
Description Display the configured Bridge Protocol Data Units (BPDU) forwarding groups.
Specify a BPDU forwarding group number to view the configuration of the specified BPDU
forwarding group. If you omit this option, all configured BPDU forwarding groups are shown.
Mode All
Example The following command shows all configured BPDU forwarding groups:
ACOS#show bpdu-fwd-group
BPDU forward Group 1 members: ethernet 1 to 3
BPDU forward Group 2 members: ethernet 9 to 12
show bridge-vlan-group
Description Display information for a bridge VLAN group.
Mode All
show bw-list
Description Show black/white list information.
Parameter Description
name Name of a black/white list.
detail Displays the IP addresses contained in a black/white list.
ipaddr IP address within the black/white list.
Default N/A
Mode Config
Example The following command shows all the black/white lists on an ACOS device:
ACOS#show bw-list
Name Url Size(Byte) Date
----------------------------------------------------------------------------
bw1 tftp://192.168.1.143/bwl.txt 106 Jan/22 12:48:01
bw2 tftp://192.168.1.143/bw2.txt 211 Jan/23 10:02:44
Example The following command shows the IP addresses in black/white list “test”:
Content
------------------------------------------------------------------------------
1.1.1.0 #13
1.1.1.1 #13
1.1.1.2 #13
1.1.1.3 #13
1.1.1.4 #13
9.9.99.9 9
1.2.3.4/32 31
4.3.2.1/24 4
10.1.2.1/32 1
10.1.2.2/32 2
10.1.2.3/32 3
10.1.2.4/32 4
10.3.2.1/32 3
10.3.2.2/32 4
10.5.2.1/32 5
10.5.2.2/32 6
128.0.0.0/1 11
show class-list
Description Display information for class lists.
Replace name with the class list name or ipaddr with an IP address in the class list. If neither
option is specified, the list of configured class lists is displayed instead.
Mode All
Usage For Aho-Corasick (AC) class lists, enter the write memory command immediately before
entering show class-list.
Example The following command displays the class-list files on the ACOS device device:
ACOS#show class-list
Name IP Subnet Location
test 4 3 file
user-limit 14 4 config
Total: 2
Field Description
Name Name of the class list.
IP Number of host IP addresses in the class list.
Subnet Number of subnets in the class list.
Location Indicates whether the class list is in the startup-config or in a stand-
alone file:
• config – Class list is located in the startup-config.
• file – Class list is located in a standalone file.
Total Total number of class lists on the ACOS device device.
The following commands show the closest matching entries for specific IP addresses in
class list “test”:
The class list contains an entry for 1.1.1.1, so that entry is shown. However, since the class list
does not contain an entry for 1.1.1.2 but does contain a wildcard entry (0.0.0.0), the wildcard
entry is shown.
show clns
Description Show Connectionless Network Service (CLNS) information.
Parameter Description
is-neighbors Displays IS neighbor adjacencies.
neighbors Displays CLNS neighbor adjacencies.
ethernet num Display adjacency information for the specified ethernet interface.
lif num Display adjacency information for the specified logical interface.
loopback num Display adjacency information for the specified loopback interface.
management Display adjacency information for the management interface.
trunk num Display adjacency information for the specified trunk.
tunnel num Display adjacency information for the specified tunnel.
ve num Display adjacency information for the specified virtual interface.
detail Displays detailed information.
Mode All
Example The show clns neighbors command displays IS-IS helper information when ACOS is
in helper mode for a particular IS-IS neighbor. Here is an example:
The asterisk (*) character in the output indicates that IS-IS is in helper mode for the neighbor.
show clock
Description Display the time, timezone, and date.
Parameter Description
detail Shows the clock source, which can be one of the following:
• Time source is NTP
• Time source is hardware calendar
Mode All
Example The following command shows clock information for an ACOS device:
Example If a dot appears in front of the time, the ACOS device has been configured to use NTP but
NTP is not synchronized. The clock was in sync, but has since lost contact with all
configured NTP servers.
ACOS#show clock
.20:27:16 Europe/Dublin Sat Apr 28 2007
Example If an asterisk appears in front of the time, the clock is not in sync or has never been set.
ACOS#show clock
*20:27:16 Europe/Dublin Sat Apr 28 2007
show config
Description This command displays the entire running configuration
Default N/A
Mode Global
Usage Use this command to display the entire running configuration for the ACOS device, or
for the particular partition which you are viewing.
show config-block
Description This command displays the current configurations being made in either block-merge or
block-replace mode.
Default N/A
Usage Use this command to display the uncommitted configurations you have made in either
block-merge or block-replace mode. These commands are not a part of the running
configu- ration, but they will be implemented upon ending block-merge or block-replace
mode.
show context
Description View the configuration for the sub-module in which the command is run.
For example, if you are configuring a virtual port under a virtual server, the show
context command displays only the portion of the configuration within the context of
the virtual port configuration; see the examples below.
Unlike other show commands, the show context command is only available in Global
configuration mode, or any additional sub-mode. For example, if you are configuring a port
under an SLB server, this command shows only the configuration related to the port.
Example The following example shows the portion of the configuration related to BGP AS 1:
ACOS(config)#router bgp 1
ACOS(config-bgp:1)#show context
Example The following example first shows the portion of the running-config related to server s1,
then only the portion related to port 80:
ACOS(config-bgp:1-ipv6)#slb server s1
ACOS(config-real server)#show context
!Section configuration: 104 bytes
!
slb server s1 1.1.1.1
port 80 tcp
weight 2
conn-limit 2
conn-resume 1
port 81 tcp
ACOS(config-real server)#port 80 tcp
ACOS(config-real server-node port)#show context
!Section configuration: 64 bytes
!
port 80 tcp
weight 2
conn-limit 2
conn-resume 1
show core
Description Display core dump statistics.
The process parameter shows core dump statistics for processes on the ACOS
device. Without this option, system core dump statistics are shown instead.
ACOS#show core
The LB process has reloaded 1 time.
The LB process has crashed 0 time.
The LB process has been up for 2755 seconds.
show cpu
Description Display CPU statistics.
Parameter Description
history Show control CPU and data CPU usage information.
seconds Show CPU usage information in last 60 seconds.
minutes Show CPU usage information in last hour.
hours Show CPU usage information in last 72 hours.
control-cpu Show Control CPU usage information.
data-cpu Show Data CPU usage information.
interval Automatically refreshes the output at the specified interval. If you
seconds omit this option, the output is shown one time. If you use this option,
the output is repeatedly refreshed at the specified interval until you
press ctrl+c.
If you enter the show cpu command from within an L3V partition, the command shows
utilization for only that partition.
ACOS#
Field Description
Time System time when the statistics were gathered.
Controln Control CPU.
Datan Data CPU. The number of data CPUs depends on the ACOS model.
I/On IO CPU usage.
I/O fields are displayed on non-FTA platforms only.
1Sec-60sec Time intervals at which statistics are collected.
Example The following command output displays CPU utilization rates plotted over the last 60 sec-
onds. The x-axis represents the time elapsed and the y-axis represents the CPU utilization
rate. Asterisks appear along the bottom of the output to illustrate the CPU utilization rates
over time. The figure below only shows the usage for the Control CPU. The usage for the
Control CPU and Data CPU are displayed in separate figures. The CLI command prints 1
aster- isk for every 10 percent utilization. This means no asterisk will be printed if the CPU
usage is from 0-4; one asterisk will be printed if the CPU usage is 5-14; two asterisks will be
printed if the CPU usage is 15-24; and so on.
533743333333244342332253334382533636436465444746756446654678
100
90
80
70
60
50
40
30
20
10* * * * * * * * ** * **** *** ***
0....0....1....1....2....2....3....3....4....4....5....5....
5 0 5 0 5 0 5 0 5 0 5
Control CPU1: CPU% per second (last 60 seconds)
100
90
80
70
60
50
40
30
20
10
0....0....1....1....2....2....3....3....4....4....5....5....
5 0 5 0 5 0 5 0 5 0 5
Data CPU1: CPU% per second (last 60 seconds)
show debug
Description This command applies to debug output. It is recommended to use the AXdebug subsystem
commands instead of the debug commands. See the following:
• “AX Debug Commands” on page 365
• “show axdebug file” on page 250
• “show axdebug filter” on page 251
• “show axdebug status” on page 251
show disk
Description Display status information for the ACOS device hard disks.
Example The following command shows hard disk information for an A10 Thunder Series 4430 device:
NOTE: The output on your device may differ slightly from the one shown below.
ACOS#show disk
Total(MB) Used Free Usage
-----------------------------------------
95393 11301 84091 11.8%
Field Description
Total(MB) Total amount of data the hard disk can hold.
NOTE: The hard disk statistics apply to a single disk. This is true
even if your ACOS device contains two disks. In systems with two
disks, the second disk is a hot standby for the primary disk and is
not counted separately in the statistics.
Used Number of MB used.
Free Number of MB free.
Usage Percentage of the disk that is in use.
Device Virtual partition on the disk:
• md0 – The boot partition
• md1 – The A10 data partition
Primary Disk Status of the left hard disk in the redundant pair:
• Active – The disk is operating normally.
• Inactive – The disk has failed and must be replaced. Contact
tech- nical support.
• Synchronizing – The disk has just been installed and is
synchroniz- ing itself with the other disk.
Secondary Disk Status of the right hard disk in the redundant pair.
Parameter Description
client DNS client statistics.
entry DNS cache entries.
statistics DNS caching statistics.
Mode All
Field Description
Total Allocated Total memory allocated for cached entries.
Total Freed Total memory freed.
Field Description
Total Query Total number of DNS queries received by the ACOS device.
Total Server Response Total number of responses form DNS servers received by the ACOS device.
Total Cache Hit Total number of times the ACOS device was able to use a cached reply in
response to a query.
Query Not Passed Number of queries that did not pass a packet sanity check.
Response Not Passed Number of responses that did not pass a packet sanity check. The ACOS device
checks the DNS header and question in the packet, but does not parse the entire
packet.
Query Exceed Cache Size Number of queries that were not cached because they had a payload greater than
the maximum size of 512 bytes.
Response Exceed Cache Size Number of responses that were not cached because they had a payload greater
than the maximum size of 512 bytes.
Response Answer Not Passed Number of responses that were not cached because they were malformed DNS
responses.
Query Encoded Number of queries that were not cached because the domain name in the
ques- tion was encoded in the DNS query packet.
Response Encoded Number of queries that were not cached because the domain name in the
ques- tion was encoded in the DNS response packet.
Query With Multiple Questions Number of queries that were not cached because they contained multiple ques-
tions.
Response With Multiple Questions Number of responses that were not cached because they contained
answers for multiple questions.
Response With Multiple Answers Number of responses that were not cached because they contained more than
one answer.
Response with Short TTL Number of responses that had a short time to live (TTL).
Total Aged Out Total number of DNS cache entries that have aged out of the cache.
Total Aged for Lower Weight Number of cache entries aged out due to their weight value.
Total Stats Log Sent Total number of logs sent.
Current Allocate Current memory allocation.
Current Data Allocate Current data allocation.
Parameter Description
cache client Show DNS client statistics.
cache entry Show DNC cache entry.
cache statistics Show DNS cache statistics
statistics Show DNS packet statistics.
Usage This command lists statistics values only if the configuration contains a virtual port that
is bound to a UDP template.
show dumpthread
Description Show status information about the system threads.
ACOS#show dumpthread
It has been rebooted 1 time.
It has been crashed 0 time.
The process is up 101102 sec.
show environment
Description Display temperature, fan, and power supply status.
Mode All
Example The following command shows environment information for an A10 Thunder Series
3030S device:
NOTE: The output on your device may vary from the one shown below.
ACOS#show environment
Updated information every 30 Seconds
Physical System temperature: 40C / 104F :
OK-low/med Fan1A : OK-med/high Fan1B : OK-low/med
Fan2A : OK-med/high Fan2B : OK-low/med
Fan3A : OK-med/high Fan3B : OK-low/med
Fan4A : OK-med/high Fan4B : OK-low/med
System Voltage 12V : OK
System Voltage 5V : OK
System Voltage AVCC 3.3V : OK
System Voltage CC(3.3V) : OK
System Voltage VCore(0.9v) : OK
System Voltage VBAT 3.3V : OK
System Voltage PCH 1.05V : OK
System Voltage CPU0 VCore : OK
System Voltage VTT 1.05V : OK
System Voltage DDR 1.5V : OK
Right Power Unit(view from front) State: Off
Left Power Unit(view from front) State: On
show errors
Description Show error information for the system. This command provides a way to quickly view
system status and error statistics.
Parameter Description
sub-options Displays error information for ACOS applications. For a list of sub-
options, enter the following command:
show errors ?
show event-action
Description View the events generated for L3V partition creation or deletion as configured by the.event
command.
Parameter Description
partition-create View partition creation events.
partition-delete View partition deletion events.
Mode All
show fail-safe
Description Display fail-safe information.
Parameter Description
config Displays the fail-safe configuration entered by you or other admins.
information Displays fail-safe settings and statistics. The output differs
between models that use FPGAs in hardware and models that do
not. (See “Example” below.)
Mode All
Example The following commands configure some fail-safe settings and verify the changes.
ACOS(config)#fail-safe session-mem-recovery-threshold 30
ACOS(config)#fail-safe fpga-buff-recovery-threshold 2
ACOS(config)#fail-safe sw-error-recovery-timeout 3
ACOS(config)#show fail-safe config
fail-safe hw-error-monitor-enable
fail-safe session-memory-recovery-threshold 30
fail-safe fpga-buff-recovery-threshold 2
fail-safe sw-error-recovery-timeout 3
Example The following command shows fail-safe settings and statistics on an ACOS device that uses
FPGAs in hardware:
Field Description
Total Session Memory Total amount of the ACOS device’s memory that is allocated for session process-
ing.
Free Session Memory Amount of the ACOS device’s session memory that is free for new sessions.
Session Memory Recovery Threshold Minimum percentage of session memory that must be free before fail-safe
occurs.
Total Configured FPGA Buffers Total number of configured FPGA buffers the ACOS device has. These buffers
are allocated when the ACOS device is booted. This number does not change
during system operation.
The FPGA device is logically divided into 2 domains, which each have their
own buffers. The next two counters are for these logical FPGA domains.
Free FPGA Buffers in Domain 1 Number of FPGA buffers in Domain 1 that are currently free for new data.
Free FPGA Buffers in Domain 2 Number of FPGA buffers in Domain 2 that are currently free for new data.
Total Free FPGA Buffers Total number of free FPGA buffers in both FPGA domains.
FPGA Buffer Recovery Threshold Minimum number of packet buffers that must be free before fail-safe occurs.
Total System Memory Total size the ACOS device’s system memory.
Example The following command shows fail-safe settings and statistics on an ACOS device that does
not use FPGAs in hardware. (The FPGA buffer is an I/O buffer instead.)
Field Description
Total Session Memory Total amount of the ACOS device’s memory that is allocated for session process-
ing.
Free Session Memory Amount of the ACOS device’s session memory that is free for new sessions.
Session Memory Recovery Threshold Minimum percentage of session memory that must be free before fail-safe
occurs.
Total Configured FPGA Buffers Total number of configured FPGA buffers the ACOS device has. These buffers
are allocated when the ACOS device is booted. This number does not change
during system operation.
Free FPGA Buffers Number of FPGA that are free for new data.
Field Description
FPGA Buffer Recovery Threshold Minimum number of packet buffers that must be free before fail-safe occurs.
Total System Memory Total size the ACOS device’s system memory.
show glid
Description Show information for global IP limiting rules.
Parameter Description
num View configuration information for the specified GLID only.
Mode All
Example The following command the configuration of each global IP limiting rule:
ACOS#show glid
glid 1
conn-limit 100
conn-rate-limit 100 per 10
request-limit 1
request-rate-limit 10 per 10
over-limit-action reset log 1
glid 2
conn-limit 20000
conn-rate-limit 2000 per 10
request-limit 200
request-rate-limit 200 per 1
over-limit-action reset log 3
glid 30
conn-limit 10000
conn-rate-limit 1000 per 1
over-limit-action forward log
Example The following command shows the configuration of global IP limiting rule 1:
ACOS#show glid 1
glid 1
conn-limit 100
conn-rate-limit 100 per 10
request-limit 1
request-rate-limit 10 per 10
over-limit-action reset log 1
show gslb
show hardware
Description Displays hardware information for the ACOS device.
Default All
Example Below is a sample output for this command, the output you see may differ depending on
your specific platform.
show health
Description Show status information for health monitors.
Parameter Description
database Show the database health check log.
external [name] Shows configuration settings for the specified external health monitoring program.
gateway Shows configuration settings and statistics for gateway health monitoring.
monitor [name] Shows configuration settings and status for the specified health monitor.
postfile [name] Shows the files used for POST requests in HTTP/HTTPS health checks.
stat Shows health monitoring statistics. The statistics apply to all health monitoring activity on the
ACOS device.
Mode All
Usage To display health monitor information for a specific partition only, use the partition name
option.
Example The following command shows configuration settings and status for health monitor “ping”:
The output shows the method used for the monitor, and the settings for each of the
parameters that are configurable for that method.
Example The following command shows the configuration settings of external health monitoring
pro- gram “http.tcl”:
set ax_env(Result) 1
# Open a socket
if {[catch {socket $ax_env(ServerHost) $ax_env(ServerPort)} sock]}
{ puts stderr "$ax_env(ServerHost): $sock"
} else {
fconfigure $sock -buffering none -eofchar {}
Unexpected error: : 0
Conn Immediate Success: : 0
Socket closed before l7: : 0
Socket closed without fd notify: : 0
Configured health-check rate (/500ms) : Auto configured
Current health-check rate (/500ms): : 1600
External health-check max rate(/200ms) : 2
Total number: : 8009
Status UP: : 8009
Status DOWN: : 0
Status UNKN: : 0
Status OTHER: : 0
Field Description
Total run time Time elapsed since the health monitoring process started.
Number of burst Number of times the system detected that a health check would leave the ACOS
device as a traffic burst, and remedied the situation.
max scan jiffie These are internal counters used by technical support for debugging purposes.
min scan jiffie
average scan jiffie
Opened socket Number of sockets opened.
Open socket failed Number of failed attempts to open a socket.
Close socket Number of sockets closed.
Send packet Number of health check packets sent to the target of the health monitor.
Send packet failed Number of sent health check packets that failed. (This is the number of times a tar-
get server or service failed its health check.)
Receive packet Number of packets received from the target in reply to health checks.
Receive packet failed Number of failed receive attempts.
Retry times Number of times a health check was resent because the target did not reply.
Timeout Number of times a response was not received before the health check timed out.
Unexpected error Number of unexpected errors that occurred.
Conn Immediate Success These are internal counters used by technical support for debugging purposes.
Socket closed before l7
Socket closed without fd notify
Field Description
Configured health-check rate If auto-adjust is enabled, shows “Auto configured”.
If auto-adjust is disabled, shows the manually configured threshold.
Current health-check rate If auto-adjust is enabled, shows the total number of health monitors divided by the
global health-check timeout:
total-monitors / global-timeout
If auto-adjust is disabled, shows the manually configured threshold.
External health-check max rate The external health-check probe rate.
Total number Total number of health checks performed.
Status UP Number of health checks that resulted in status UP.
Status DOWN Number of health checks that resulted in status DOWN.
Status UNKN Number of health checks that resulted in status UNKN.
Status OTHER Number of health checks that resulted in status OTHER.
IP address IP address of the real server.
Port Protocol port on the server.
Health monitor Name of the health monitor.
If the name is “default”, the default health monitor settings for the protocol port type
are being used. (See “health-check” in the Command Line Interface Reference for
ADC for Layer 3 health checks or “port” in the Command Line Interface Reference
for ADC for Layer 4-7 health checks.)
Status Indicates whether the service passed the most recent health check.
Cause (Up/Down) Up and Down show internal codes for the reasons the health check reported the
server or service to be up or down. (See “Up and Down Causes for the show health
stat Command” on page 375.)
Retry Number of retries.
PIN Indicates the following:
• Current number of retries – Displayed to the left of the slash ( / ). The
number of times the most recent health check was retried before a response
was received or the maximum number of retries was used.
• Current successful up-retries – Displayed to the right of the slash ( / ). Number
of successful health check replies received for the current health check. This
field is applicable if the up-retry option is configured for the health check.
(See “health monitor” on page 128.)
show history
Description Show the CLI command history for the current session.
Usage Commands are listed starting with the oldest command, which appears at the top of the list.
Example The following example shows a history of CLI commands (truncated for brevity):
ACOS#show history
enable
show version
show access-list
show admin
show admin admin
show admin detail
show admin session
...
show hsm
Description See “Config Commands: DNSSEC” on page 217.
show icmp
Description Show ICMP rate limiting configuration settings and statistics.
Mode All
Example The following command shows ICMP rate limiting settings, and the number of ICMP
packets dropped because the threshold has been exceeded:
ACOS(config)#show icmp
Global rate limit: 5
Global lockup rate limit: 10
Lockup period: 20
Current global rate: 0
Global rate limit drops: 0
Interfaces rate limit drops: 0
Virtual server rate limit drops: 0
show icmpv6
Description Show ICMPv6 rate limiting configuration settings and statistics.
Mode All
show interfaces
Description Display interface configuration and status information.
Usage If no specific interface type and number are specified, statistics for all configured
interfaces are displayed. See the examples below.
• For information about the brief option, see “show interfaces brief” on page 285.
• For information about the media option, see “show interfaces media” on page 286.
• For information about the statistics options, see “show interfaces statistics”
on page 287.
• For information about the transceiver option, see “show interfaces transceiver”
on page 287.
Configured Speed auto, Actual 1Gbit, Configured Duplex auto, Actual fdx
Member of L2 Vlan 1, Port is Untagged
Flow Control is enabled, IP MTU is 1500 bytes
Port as Mirror disabled, Monitoring this Port disabled
0 packets input, 0 bytes
Received 0 broadcasts, Received 0 multicasts, Received 0 unicasts
0 input errors, 0 CRC 0 frame
0 runts 0 giants
0 packets output 0 bytes
Transmitted 0 broadcasts 0 multicasts 0 unicasts
0 output errors 0 collisions
300 second input rate: 158073232 bits/sec, 154368 packets/sec, 15% utilization
300 second output rate: 35704 bits/sec, 5 packets/sec, 0% utilization
Example The following example shows Virtual Ethernet (VE) interface statistics:
ACOS#show interface ve 10
VirtualEthernet 10 is up, line protocol is up
Hardware is VirtualEthernet, Address is 001f.a004.c0e2
Internet address is 110.10.10.1, Subnet mask is 255.255.255.0
IPv6 address is 2001:10::241 Prefix 64 Type: unicast
IPv6 link-local address is fe80::21f:a0ff:fe04:c0e2 Prefix 64 Type: unicast
Router Interface for L2 Vlan 10
IP MTU is 1500 bytes
28 packets input 2024 bytes
Received 0 broadcasts, Received 24 multicasts, Received 4 unicasts
10 packets output 692 bytes
Transmitted 8 broadcasts, Transmitted 2 multicasts, Transmitted 0 unicasts
300 second input rate: 48 bits/sec, 0 packets/sec
300 second output rate: 16 bits/sec, 0 packets/sec
Example Below is example output from the show interfaces brief command:
Port Link Dupl Speed Trunk Vlan MAC IP Address IPs Name
------------------------------------------------------------------------------------
mgmt Up Full 1000 N/A N/A 001f.a007.5930 10.6.10.56/24 1
1 Disb None None 2 1 001f.a007.5932 0.0.0.0/0 0 HA_TRUNK
2 Disb None None 2 1 001f.a007.5933 0.0.0.0/0 0
3 Disb None None None 1 001f.a007.5934 0.0.0.0/0 0
4 Disb None None None 1 001f.a007.5935 0.0.0.0/0 0
5 Up Full 10000 1 Tag 001f.a007.5936 0.0.0.0/0 0
6 Up Full 10000 1 Tag 001f.a007.5937 0.0.0.0/0 0
7 Up Full 10000 1 Tag 001f.a007.5938 0.0.0.0/0 0
8 Down None None 1 Tag 001f.a007.5939 0.0.0.0/0 0
9 Down None None None 1 001f.a007.593a 202.20.202.20/24 1
10 Down None None None 1 001f.a007.593b 20.20.20.20/24 1
11 Disb None None None 1 001f.a007.593c 0.0.0.0/0 0
12 Disb None None None 1 001f.a007.593d 0.0.0.0/0 0
13 Down None None 3 Tag 001f.a007.593e 0.0.0.0/0 0
14 Down None None 3 Tag 001f.a007.593f 0.0.0.0/0 0
15 Down None None None Tag 001f.a007.5940 0.0.0.0/0 0
16 Down None None None 1 001f.a007.5941 16.16.16.56/24 1
ve2 Up N/A N/A N/A 2 001f.a007.5932 1.2.2.252/24 1 conn-to-router
ve10 Down N/A N/A N/A 10 001f.a007.5933 192.168.111.1/24 1 VRRP-a_Int
ve71 Up N/A N/A N/A 71 001f.a007.5934 172.16.71.252/24 1 Cav-80-eth0.71
Parameter Description
num Show information for the specified interface only.
Usage On Virtual Chassis System (VCS), this command provides device-specific media information.
NOTE: This command does not show information on media installed in ports that belong
to an L3V partition.
Example The following example sample output for this command. The example displays output on
ports with an installed 1 Gigabit SFP and a 10 Gigabit SFP+ module. When an SFP is
not installed, or if the port has not been enabled, an error message appears in the
output, as shown below:
port 11:
No media detected.
port 18:
Type: SFP+ 10G Base-SR
Vendor: FINISAR CORP.
Part#: FTLX8571D3BCL Serial#:UG505PM
port 19:
No media detected.
port 20:
Cannot retrieve media information when port is disabled.
In this example, the SFP+ interface for port 18 is installed and its link is up. The other 10-
Gbps interfaces either are down or do not have an SFP+ installed.
Example The following example shows the CLI response if you enter show interfaces
media on an ACOS device that does not support SFP+ interfaces:
Parameter Description
ethernet Ethernet data interface numbers for which to display statistics. If you
portnum omit this option, statistics are displayed for all Ethernet data interfaces
and logical tunnel interfaces.
lif ifnum Logical tunnel interface numbers for which to display statistics. If you
omit this option, statistics are displayed for all Ethernet data
interfaces and logical tunnel interfaces.
in-pps Inbound traffic, in packets per second (PPS).
in-bps Inbound traffic, in bytes per second (BPS).
out-pps Outbound traffic, in packets per second (PPS).
out-bps Incoming traffic, in bytes per second (BPS).
interval Refreshes the statistics at the specified interval, 1-32 seconds. If you
seconds do not use this option, the statistics are displayed only once.
Example View information for all configured 40G and 100G ports with the show
interfaces transceiver command:
show ip
Description Show the IP mode in which the ACOS device is running, gateway or transparent mode.
Syntax show ip
Mode All
Example The following command shows that the ACOS device is running in gateway mode:
ACOS#show ip
System is running in Gateway Mode
Mode All
show ip bgp
Description Display BGP information. (See the “Config Commands: Router - BGP” chapter in the Network
Configuration Guide.)
show ip dns
Description Display system DNS information.
Mode All
Example The following example shows example output for this command.
ACOS#show ip dns
DNS suffix: ourcorp
Primary server: 10.10.20.25
Secondary server: 192.168.1.25
NOTE: This command is applicable only on ACOS devices that are configured in route
mode. The command returns an error if you enter it on a device configured for
transparent mode.
Mode All
Example The following command shows the IPv4 FIB entries on an ACOS device configured in
route mode:
ACOS#show ip fib
Prefix Next Hop Interface Distance
------------------------------------------------------------------------
0.0.0.0 /0 192.168.20.1 ve10 0
192.168.20.0 /24 0.0.0.0 ve10 0
Total routes = 2
Mode All
ICMPv6 Received 0
UDP Received 0
TCP Received 0
IP-in-IP Received 0
IPv6-in-IP Received 0
Other Received 0
ICMP Dropped 0
ICMPv6 Dropped 0
UDP Dropped 0
TCP Dropped 0
IP-in-IP Dropped 0
IPv6-in-IP Dropped 0
Other Dropped 0
Overlapping Fragment Drop 0
Bad IP Length 0
Fragment Too Small Drop 0
First TCP Fragment Too Small Drop 0
First L4 Fragment Too Small Drop 0
Total Sessions Exceeded Drop 0
Out of Session Memory 0
Fragmentation Fast Aging Set 0
Fragmentation Fast Aging Unset 0
Fragment Queue Success 0
Payload Length Unaligned 0
Payload Length Out of Bounds 0
Duplicate First Fragment 0
Duplicate Last Fragment 0
Total Queued Fragments Exceeded 0
Fragment Queue Failure 0
Fragment Reassembly Success 0
Fragment Max Data Length Exceeded 0
Fragment Reassembly Failure 0
MTU Exceeded Policy Drop 0
Fragment Processing Drop 0
Too Many Packets Per Reassembly Drop 0
Session Max Packets Exceeded 0
Field Description
Session Inserted Number of times the ACOS device received a new fragment that did not match
any existing session (based on source IP, destination ID, and fragment ID).
A fragment session represents multiple fragments that should be
reassembled together into a single logical packet.
Session Expired Number of times a fragment session timed out before all the fragments for the
packet were received.
ICMP Received Number of ICMP fragments received.
ICMPv6 Received Number of ICMPv6 fragments received.
UDP Received Number of UDP fragments received.
TCP Received Number of TCP fragments received.
IP-in-IP Received Number of IP-in-IP fragments received.
IPv6-in-IP Received Number of IPv6-in-IP fragments received.
Other Received Number of other types of fragments received.
ICMP Dropped Number of ICMP fragments that were dropped. This counter and the other
“Dropped” counters below are incremented when a fragment is dropped for
any of the following reasons:
• Invalid length
• Overlap with other fragments
• Exceeded fragmentation session threshold
ICMPv6 Dropped Number of ICMPv6 fragments that were dropped.
UDP Dropped Number of UDP fragments that were dropped.
TCP Dropped Number of TCP fragments that were dropped.
IP-in-IP Dropped Number of IP-in-IP fragments that were dropped.
IPv6-in-IP Dropped Number of IPv6-in-IP fragments that were dropped.
Other Dropped Number of other types of fragments that were dropped.
Overlapping Fragment Drop Number of fragments dropped because the data in the fragment overlapped
with data in another fragment already received by the ACOS device.
Bad IP Length This counter includes both of the following:
• Number of IPv4 packets for which the total length was invalid.
• Number of IPv6 packets for which the payload length was invalid.
Fragment Too Small Drop Number of fragments in which the length of the data was too short. IP frag-
mentation requires at least 8 bytes of data in all except the last fragment.
First TCP Fragment Too Small Drop Number of fragmented TCP packets that did not contain the entire
Layer 4 header in the first fragment.
First L4 Fragment Too Small Drop Number of fragmented packets other than TCP packets that did not
contain the entire Layer 4 header in the first fragment.
Total Sessions Exceeded Drop Number of times a fragment was dropped because the maximum number of
concurrent fragment sessions were already in use.
Out of Session Memory Number of times the ACOS device ran out of memory for fragment sessions.
Field Description
Fragmentation Fast Aging Set Number of times the ACOS device sped up aging of existing fragment
sessions in order to accommodate new sessions.
Fragmentation Fast Aging Unset Number of times the ACOS device returned to normal aging for fragment
ses- sions.
Fragment Queue Success Number of times a new fragment session was created, or a new fragment was
added to an existing session.
Payload Length Unaligned Number of fragments whose length did not consist of a multiple of 8 bytes.
Note: This counter does not apply to the final fragments of fragmented pack-
ets. The final fragment of a packet is not required to have a length that is a mul-
tiple of 8.
Payload Length Out of Bounds Number of times a fragmented packet’s data length exceeded what should
have been the end of the reassembled packet.
Duplicate First Fragment Number of times a duplicate first fragment was received for the same packet.
Duplicate Last Fragment Number of times a duplicate last fragment was received for the same packet.
Total Queued Fragments Exceeded Number of times the maximum number of concurrent fragmented packets
supported by the ACOS device was exceeded.
Fragment Queue Failure Total number of times a fragmented packet could not be queued to a
session, due to any of the errors listed separately by the following counters:
• Duplicate First Fragment
• Duplicate Last Fragment
• Payload Length Out of Bounds
• Payload Length Unaligned
Fragment Reassembly Success Number of times all fragments for a packet were reassembled successfully.
Fragment Max Data Length Exceeded Number of times the total length of all reassembled fragments for a packet
exceeded 65535. This type of error can indicate an attack such as a ping-
of- death attack.
Fragment Reassembly Failure Total number of fragment reassembly errors, including errors due to unlikely
causes such as memory corruption.
MTU Exceeded Policy Drop Number of packets dropped due to an MTU exceeded policy.
Fragment Processing Drop Number of packets dropped due to errors during fragment processing.
Too Many Packets Per Reassembly Number of packets dropped because too many fragments were received for
Drop the packet.
Session Max Packets Exceeded Number of times the limit for fragmented packets has been reached.
IPv4-in-IPv6 Fragmentation Statistics These are the same as the counters described above, but they apply to
(Not shown in the example above.) packets fragmented into IPv4 fragments before being sent in the IPv6 tunnel.
For exam- ple, these counters can apply to fragmented DS-Lite traffic.
These counters are displayed if you use the ipv6 option instead of the ip
option.
show ip helper-address
Description Display DHCP relay information.
Mode All
ACOS(config)#show ip helper-address
Interface Helper-Address RX TX No-Relay Drops
--------- -------------- ------------ ------------ ------------ ------------
eth1 100.100.100.1 0 0 0 0
ve5 100.100.100.1 1669 1668 0 1
ve7 1668 1668 0 0
ve8 100.100.100.1 0 0 0 0
ve9 20.20.20.102 0 0 0 0
Field Description
Interface ACOS interface. Interfaces appear in the output in either of the fol-
lowing cases:
• A helper address is configured on the interface.
• DHCP packets are sent or received on the interface.
Helper-Address Helper address configured on the interface.
RX Number of DHCP packets received on the interface.
TX Number of DHCP packets sent on the interface.
No-Relay Number of packets that were examined for DHCP relay but were not
relayed, and instead received regular Layer 2/3 processing.
Generally, this counter increments in the following cases:
• DHCP packets are received on an interface that does not have
a helper address and the packets are not destined to the relay.
• DHCP packets are received on an interface that does have a
helper address, but the packets are unicast directly from the
client to the server and do not need relay intervention.
Drops Number of packets that were ineligible for relay and were dropped.
Packets:
RX: 0
BootRequest Packets : 0
BootReply Packets : 0
TX: 0
BootRequest Packets : 0
BootReply Packets : 0
No-Relay: 0
Drops:
Invalid BOOTP Port : 0
Invalid IP/UDP Len : 0
Invalid DHCP Oper : 0
Exceeded DHCP Hops : 0
Invalid Dest IP : 0
Exceeded TTL : 0 No
Route to Dest : 0 Dest
Processing Err : 0
IP Interface: ve5
------------
Helper-Address: 100.100.100.1
Packets:
RX: 16
BootRequest Packets :
16 BootReply Packets
: 0
TX: 14
BootRequest Packets : 0
BootReply Packets : 14
No-Relay: 0
Drops:
Invalid BOOTP Port : 0
Invalid IP/UDP Len : 0
Invalid DHCP Oper : 0
Exceeded DHCP Hops : 0
Invalid Dest IP : 0
Exceeded TTL : 0 No
Route to Dest : 2 Dest
Processing Err : 0
IP Interface: ve7
------------
Helper-Address: None
Packets:
RX: 14
BootRequest Packets : 0
BootReply Packets : 14
TX: 14
BootRequest Packets :
14 BootReply Packets
: 0
No-Relay: 0
Drops:
Invalid BOOTP Port : 0
Invalid IP/UDP Len : 0
Invalid DHCP Oper : 0
Exceeded DHCP Hops : 0
Invalid Dest IP : 0
Exceeded TTL : 0 No
Route to Dest : 0 Dest
Processing Err : 0
Field Description
IP Interface ACOS interface.
Helper-Address IP address configured on the ACOS interface as the DHCP helper
address.
Packets DHCP packet statistics:
• RX – Total number of DHCP packets received on the interface.
• BootRequest Packets – Number of DHCP boot request
packets (Op = BOOTREQUEST) received on the interface.
• BootReply Packets – Number of DHCP boot reply packets (Op
= BOOTREPLY) received on the interface.
• TX – Total number of DHCP packets sent on the interface.
• BootRequest Packets – Number of DHCP boot request
packets (Op = BOOTREQUEST) sent on the interface.
• BootReply Packets – Number of DHCP boot reply packets (Op
= BOOTREPLY) sent on the interface.
Field Description
No-Relay Number of packets that were examined for DHCP relay but were not
relayed, and instead received regular Layer 2/3 processing.
Generally, this counter increments in the following cases:
• DHCP packets are received on an interface that does not have
a helper address and the packets are not destined to the relay.
• DHCP packets are received on an interface that does have a
helper address, but the packets are unicast directly from the client
to the server and do not need relay intervention.
Drops Lists the following counters for packets dropped on the interface:
• Invalid BOOTP Port – Number of packets dropped because they
had UDP destination port 68 (BOOTPC).
• Invalid IP/UDP Len – Number of packets dropped because the IP
or UDP length of the packet was shorter than the minimum
required length for DHCP headers.
• Invalid DHCP Oper – Number of packets dropped because the Op
field in the packet header did not contain BOOTREQUEST or BOOT-
REPLY.
• Exceeded DHCP Hops – Number of packets dropped because
the number in the Hops field was higher than 16.
• Invalid Dest IP – Number of packets dropped because the
destina- tion was invalid for relay.
• Exceeded TTL – Number of packets dropped because the TTL
value was too low (less than or equal to 1).
• No Route to Dest – Number of packets dropped because the relay
agent (ACOS device) did not have a valid forwarding entry
towards the destination.
• Dest Processing Err – Number of packets dropped because the
relay agent experienced an error in sending the packet towards the
desti- nation.
Mode All
Example The following command shows the IPv4 interfaces configured on Ethernet interface 1:
Example The following command shows the IPv4 interfaces configured on VEs:
ACOS#show ip interfaces ve
Port IP Netmask PrimaryIP
--------------------------------------------------
--------------------------------------------------
ve4 60.60.60.241 255.255.255.0 Yes
50.60.60.241 255.255.252.0 No
--------------------------------------------------
ve6 99.99.99.241 255.255.255.0 Yes
The PrimaryIP column indicates whether the address is the primary IP address for the
interface. (For more information, see the ip address command in the “Config
Commands: Interface” chapter of the Network Configuration Guide.
Example The following command displays the status of the PPTP NAT ALG feature:
Field Description
Calls In Progress Current call attempts, counted by inspecting the TCP control session. This counter will
decrease once the first GRE packet arrives.
Call Creation Failure Number of times a call could not be set up because the ACOS device ran out of mem-
ory or other system resources.
Truncated PNS Message Number of runt TCP PPTP messages received from clients.
Truncated PAC Message Number of runt TCP PPTP messages received from servers.
Mismatched PNS Call ID Number of calls that were disconnected because the GRE session had the wrong Call
ID.
Mismatched PAC Call ID Number of calls that were disconnected because they had the wrong Call ID.
Retransmitted PAC Message Number of TCP packets retransmitted from PAC servers.
Truncated GRE Packets Number of runt GRE packets received by the ACOS device.
Unknown GRE Packets Number of GRE packets that were not used for PPTP and were dropped.
No Matching GRE Session Number of GRE PPTP packets sent with no current call.
Parameter Description
pool-name Displays information only for the specified pool.
statistics Displays pool statistics.
Field Description
Pool Name Name of the pool.
Start Address Beginning IP address in the pool address range.
End Address Ending IP address in the pool address range.
Mask Network mask.
Gateway Default gateway for traffic mapped to an address in the pool.
Vrid VRRP-A VRID to which the pool is assigned, if applicable.
Entering a pool name displays the same fields but for only the specified pool:
-------------------------------------------------------------------------------
dmz2 10.10.10.200 0 0 0 0
Field Description
Pool Name of the pool.
Address IP address in the pool.
Port Usage Number of Layer 4 protocol port mappings currently in use on the port.
Note: A local address can have multiple NAT mappings. Each NAT mapping for a local
address consists of an IP:port tuple.
Total Used Total number of port mappings (IP:port tuples) used from the pool.
Total Freed Total number of port mappings that were used and then returned to the pool.
Failed Number of mappings that failed.
Field Description
Name Name of the range list.
Local Address/Mask Beginning local address of the range to be translated into global (NAT)
addresses.
Global Address/Mask Beginning global address of the range.
Field Description
Count Number of address translations in the range.
HA VRRP-A VRID to which the range list belongs, if applicable.
Parameter Description
statistics Displays statistics.
ipaddr Displays information for the specified IP address.
Example The following command displays the static source NAT binding for local address 10.10.10.20:
Field Description
Source Address Source IP address that is statically mapped to a global IP address (source NAT address).
Port Usage Number of Layer 4 protocol port mappings currently in use by the local address.
Note: A local address can have multiple NAT mappings. Each NAT mapping for a local
address consists of an IP:port tuple.
Total Used Total number of port mappings (IP:port tuples) used by the inside address.
Total Freed Total number of port mappings returned to the static pool.
The output lists the inside NAT and outside NAT interfaces and provides address translation
statistics.
Example The following command displays the timeout settings IP source NAT sessions.
ACOS(config)#show ip nat
timeouts NAT Timeout values in
seconds: TCP UDP ICMP
------------------------
300 300 fast
Service 53/udphas fast-aging configured
Mode All
Field Description
Prot Layer 4 protocol.
Inside global Global (NAT) address mapped by ACOS to the inside source address (the
inside local address).
Inside local Inside source address before translation.
Outside local Outside destination address of the traffic.
Outside global Outside destination address of the traffic. <<always the same as “Outside
local”?>>
Age For dynamic mappings, indicates how many seconds the entry is
allowed to continue remaining idle before being removed. <<is this
correct?>>
Hash <<?>>
Type Entry type:
• NF NAT – <<?>>
• NS NAT – <<?>>
show ip-list
Description Display IP-list information.
Parameter Description
list-name Displays the configuration of the specified list. If you omit this option, the config-
ured IP lists are listed instead.
Mode All
Example The following example shows the IP lists configured on an ACOS device:
ACOS-Active(config)#show ip-list
Name Type Entries
--------------------------------------------------
sample_ip_list_ng IPv4 3
test-list IPv4 0
Total: 2
20.20.3.1
123.45.6.7
Mode All
Example The following command displays configuration information for IPv6 router discovery on an
Ethernet interface. In this example, the interface is VE 10.
R.S. Truncated: 0
R.S. Bad ICMPv6 Checksum: 0
R.S. Unknown ICMPv6 Code: 0
R.S. Bad ICMPv6 Option: 0
R.S. Src Link-Layer Option and Unspecified Address: 0
No Free Buffers to send R.A.: 0
The error counters apply to router solicitations (R.S.) that are dropped by the ACOS device.
The Src Link-Layer Option and Unspecified Address counter indicates the number of times
the ACOS device received a router solicitation with source address “::” (unspecified IPv6
address) and with the source link-layer (MAC address) option set.
NOTE: In the current release, the ACOS device does not drop IPCMv6 packets that have
bad (invalid) checksums.
Mode All
Mode All
Mode All
Mode All
The show ip route summary command displays summary information for all IP
routes, including the total number of routes. The command output applies to both the data
route table and the management route table, which are separate route tables.
The following commands display routes for only one of the route tables:
• show ip route – Shows information for the data route table only.
• show ip route mgmt – Shows information for the management route table only.
The total number of routes listed by the output differs depending on the command you
use. For example, the total number of routes listed by the show ip route command
includes only data routes, whereas the total number of routes listed by the show ip
route summary command includes data routes and management routes.
ACOS#show ip route
Mode All
Mode All
show isis
Description See the “Config Commands: Router - IS-IS” chapter in the Network Configuration Guide.
show json-config
Description View the JSON/aXAPI data format associated with the running-config, or for a specific object.
If no object is specified, then the JSON configuration for the entire running-config will be
shown.
Mode All
Example The following example shows the JSON configuration for SLB server “web2”:
a10-url:/axapi/v3/slb/server/web2
{
"server":
{ "name":"web2",
"host":"10.10.10.2",
"health-check":"https-with-key",
"port-list": [
{
"port-number":80,
"protocol":"tcp",
"health-check-disable":1
}
]
}
}
show json-config-detail
Description View the JSON/aXAPI data format, including the URI and object type, associated with
the running-config, or for a specific object.
If no object is specified, then the JSON configuration for the entire running-config will be
shown.
Mode All
Example The following example shows the JSON configuration, with URI and object type
information, for SLB server “web2”:
a10-url:/axapi/v3/slb/server/web2
{
"server":
{ "name":"web2",
"host":"10.10.10.2",
"health-check":"https-with-key",
"port-list": [
{
"port-number":80,
"protocol":"tcp",
"health-check-disable":1,
"a10-url":"/axapi/v3/slb/server/web2/port/80+tcp",
"obj-type":"multi"
}
]
}
}
show json-config-with-default
Description View the JSON/aXAPI data format, including default values, associated with the running-
con- fig or for a specific object.
If no object is specified, then the JSON configuration for the entire running-config will be
shown.
Mode All
Example The following example shows the JSON configuration, with default values, for SLB
server “web2”:
a10-url:/axapi/v3/slb/server/web2
{
"server":
{ "name":"web2",
"host":"10.10.10.2",
"action":"enable",
"template-server":"default",
"health-check":"https-with-key",
"conn-limit":8000000,
"no-logging":0,
"weight":1,
"slow-start":0,
"spoofing-cache":0,
"stats-data-action":"stats-data-enable",
"extended-stats":0,
"port-list": [
{
"port-number":80,
"protocol":"tcp",
"range":0,
"action":"enable",
"no-ssl":0,
"health-check-disable":1,
"weight":1,
"conn-limit":8000000,
"no-logging":0,
"stats-data-action":"stats-data-enable",
"extended-stats":0,
"a10-url":"/axapi/v3/slb/server/web2/port/80+tcp"
}
]
}
}
show key-chain
Description Show configuration information for authentication key chains.
Example The following text is an example of the output for this command:
ACOS#show key-chain
key chain test1
key 1
key-string test1key1
key 2
key-string test1key2
key chain test2
key 2
key-string test2key2
show lacp
Description Show configuration information and statistics for Link Aggregation Control Protocol (LACP).
Parameter Description
counter View LACP packet statistics for all trunks, or for just
the specified trunk.
sys-id Shows the LACP system ID of the ACOS device.
admin-key-list-details View LACP admin key list details.
detail View detailed trunk information.
summary View trunk summary information.
Mode All
In this example, LACP has dynamically created two trunks, 5 and 10. Trunk 5 contains ports 1
and 2. Trunk 10 contains port 6.
show lacp-passthrough
Mode All
show license
Description Display the host ID and, if applicable, serial number of the license applied to this
ACOS device.
Specify the uid option to show the serial number associated with the UID.
Example The following example shows sample output for this command.
show license-debug
Description This command is for internal use and is documented to notify that it does not serve any use-
ful purpose to the consumer.
Mode All
GLM
show license-info
Description Show current product SKU and license information on the ACOS device.
Mode All
Example Example output for this command. This example shows that the CFW product is installed
(highlighted) along with the product modules that are included in this product. Refer to the
Release Notes for more information about product SKUs and licenses.
------------------------------------------------------------------------------------
SLB None
CGN None
GSLB None
RC None
DAF None
WAF None
SSLI None
DCFW None
GIFW None
URLF None
IPSEC None
AAM None
FP None
WEBROOT None Requires an additional Webroot license.
THREATSTOP None Requires an additional ThreatSTOP license.
Mode All
Mode All
show local-uri-file
Description Display local imported URI files.
Mode All
show locale
Description Display the configured CLI locale.
Mode All
Example The following command shows the locale configured on an ACOS device:
ACOS#show locale
en_US.UTF-8 English locale for the USA, encoding with UTF-8 (default)
show log
Description Display entries in the syslog buffer or display current log settings (policy). Log entries
are listed starting with the most recent entry on top.
Parameter Description
debug Show debug logging entries only.
length num Shows the most recent log entries, up to the number of entries
you specify. You can specify 1-1000000 (one million) entries.
policy Shows the log settings. To display log entries, omit this option.
Mode All
Facility: local0
Name Level
----------------------------
Console error
Syslog disable
Monitor disable
Buffer debugging
Email disable
Trap disable
Example The following command shows log entries (truncated for brevity):
ACOS#show log
Log Buffer: 30000
Jan 17 11:32:02 Warning A10LB HTTP request has p-
conn Jan 17 11:31:01 Notice The session [1] is
closed
Jan 17 11:31:00 Info Load libraries in 0.044 secs
Jan 17 11:26:19 Warning A10LB HTTP request has p-
conn
Jan 17 11:26:19 Warning A10LB HTTP response not beginning of
header: m counterType="1" hourlyCount="2396"
dailyCount="16295" weeklyCount="16295" monthly
Jan 17 11:16:18 Warning A10LB HTTP request has p-
conn Jan 17 11:16:01 Notice The session [1] is
closed
Jan 17 11:16:00 Info Load libraries in 0.055 secs
Jan 17 11:15:22 Warning A10LB HTTP request has p-
conn Jan 17 11:15:03 Notice The session [1] is
closed Jan 17 11:14:33 Warning A10LB HTTP request
has p-conn
...
show mac-address-table
Description Display MAC table entries.
Parameter Description
macaddr Shows the MAC table entry for the specified MAC address.
Enter the MAC address in the following format: aaaa.bbbb.cccc
port port-num Shows the MAC table entries for the specified Ethernet port.
vlan vlan-id Shows the MAC table entries for the specified VLAN.
Mode All
ACOS#show mac-address-table
Total active entries: 10 Age time: 300 secs
MAC-Address Port Type Index Vlan Trap
---------------------------------------------------------
001e.bd62.d021 2 Dynamic 85 0 None
001e.bd62.d01e 1 Dynamic 244 120 None
000c.2923.c500 lif2 Dynamic 456 1 None
000d.480a.6665 1 Dynamic 594 120 None
001f.a002.fdc3 1 Dynamic 676 120 None
Field Description
Total active entries Total number of active MAC entries in the table. An active entry is
one that has not aged out.
Age time Number of seconds a dynamic (learned) MAC entry can remain
unused before it is removed from the table.
MAC-Address MAC address of the entry.
Port Ethernet port through which the MAC address is reached.
Type Indicates whether the entry is dynamic or static.
Index The MAC entry’s position in the MAC table.
Vlan VLAN the MAC address is on.
Trap Shows any SNMP traps enabled on the port.
show management
Description Show the types of management access allowed on each of the ACOS device’s Ethernet
inter- faces.
Mode All
Usage To configure the management access settings, see “enable-management” on page 112
and “disable-management” on page 109.
NOTE: If you do not use either option, IPv4 access information is shown.
If management access is controlled by an ACL, the ACL ID would be listed instead of “on”
or “off” status.
show memory
Description Display memory usage information.
Parameter Description
cache Shows cache statistics.
system Shows summary statistics for memory usage.
active-vrid Show memory usage statistics for the specified VRID only. This
option is only available in VRRP-A environments.
Example The following command shows summary statistics for memory usage:
Example The following command shows memory usage for individual system modules:
ACOS#show memory
Total(KB) Used Free Usage
----------------------------------------------------
Memory: 31941112 8310060 23631052 26.0%
System memory:
Object size(byte) Allocated(#) Max(#)
----------------------------------------------------------------
4 223 3639
36 2536 3639
100 71095 71262
228 152 992
484 12 503
996 183 253
2020 92 127
4068 339 378
8164 72 93
aFleX memory:
Object size(byte) Allocated(#) Max(#)
----------------------------------------------------------------
32 1412 58224
64 7008 30816
128 7621 20960
256 181 12768
512 509 7168
1024 52 3824
2048 0 0
4096 0 0
TCP memory:
Object size(byte) Allocated(#) Max(#)
----------------------------------------------------------------
1104 1 225
184 0 0
Example The following command shows memory cache information (truncated for brevity):
show mirror
Description Display port mirroring information.
Mode All
Example The following example shows the port mirroring configuration on an ACOS device:
ACOS#show mirror
Mirror Ports 1: Input = 4 Output = 4
Ports monitored at ingress : 1
Mirror Ports 2: Input = None Output = 7
Mirror Ports 3: Input = 9 Output = 9
Mirror Ports 4: Input = 3 Output = None
Field Description
Mirror Port Mirror port index number.
Input Indicates that inbound mirrored traffic from the monitor port can be sent out of the
specified ethernet interface. If “None” appears instead of an ethernet interface
number, it means that inbound mirrored traffic will not be sent out of this ethernet
port.
Output Indicates that outbound mirrored traffic from the monitor port can be sent out of the
specified ethernet interface. If “None” appears instead of an ethernet interface
number, it means that outbound mirrored traffic will not be sent out of this ethernet
port.
Port monitored at ingress Port(s) whose inbound traffic is copied to the monitor port.
Port monitored at egress Port(s) whose outbound traffic is copied to the monitor port.
show monitor
Description Display the event thresholds for system resources.
Mode All
ACOS#show monitor
Current system monitoring threshold:
Hard disk usage: 85
Memory usage: 95
Control CPU usage: 90
Data CPU usage: 90
IO Buffer usage: 734003
show netflow
Description Display NetFlow information.
Parameter Description
common Displays the currently configured maximum
queue time for NetFlow export packets.
monitor [monitor-name] Displays information for NetFlow monitors.
Mode All
Field Description
Protocol Specifies the NetFlow Protocol version (NetFlow v9 or NetFlow v10/
IPFIX)
Status Specifies whether or not the NetFlow monitor is enabled.
Filter Identifies the specific type and subset of resources that are being
monitored (global, specific ports, or a NAT pool).
Destination Indicates the destination IP address and port, if configured.
Source IP Use Specifies whether the IP address of the management port of the
MGMT ACOS device is being used as the source IP of NetFlow packets.
Flow Timeout Timeout value interval at which flow records are periodically
exported for long-lived sessions. Flow records for short-lived
sessions (if any) are sent upon termination of the session.
Resend Tem- The number of records before the ACOS device resends the
plate Per Records NetFlow template that describes the data to perform a refresh of the
template on the NetFlow collector.
Resend Tem- The amount of time before the ACOS device resends the template
plate Timeout that describes the data to perform a refresh of the template on the
NetFlow collector.
Sent Total number of NetFlow packets and bytes sent.
Records Specifies the NetFlow template types configured, which define the
NetFlow records to export.
show ntp
Description Show the Network Time Protocol (NTP) servers and status.
Parameter Description
servers Lists the configured NTP servers and their state (enabled/disabled).
status Lists the configured NTP servers and the status of the connection
between ACOS and the server.
show object-group
Description Show object groups, a named set of IP addresses or protocol values used for extended IPv4
or IPv6 ACLs.
Parameter Description
network name Show a network object group which contains IP address match crite-
ria.
service name Show a service object group which contains protocol match criteria.
Mode All
show overlay-mgmt-info
Description See the Configuring Overlay Networks guide.
show overlay-tunnel
Description See the Configuring Overlay Networks guide.
show partition
Description All show commands related to partitions are available in Configuring Application Delivery
Par- titions.
show partition-config
Description All show commands related to partitions are available in Configuring Application Delivery
Par- titions.
show partition-group
Description All show commands related to partitions are available in Configuring Application Delivery
Par- titions.
show pbslb
Description Show configuration information and statistics for Policy-based SLB (PBSLB).
Field Description
name Shows information for virtual servers.
client [ipaddr] Shows information for black/white list clients.
system Shows system-wide statistics for PBSLB.
virtual-server Shows statistics for IP limiting on the specified vir-
virtual-server-name tual server.
[port port-num
service-type]
Mode All
Example The following command shows PBSLB class-list information for an ACOS device:
ACOS#show pbslb
Virtual server class list statistics:
F = Flag (C-Connection, R-Request), Over-RL = Over rate
limit Source Destination F Current Rate Over-limit Over-RL
---------------+---------------------+-+---------+---------+----------+----------
10.1.2.1 10.1.11.1:80 C 15 1 0 0
Total: 1
Field Description
Source Client IP address.
Destination VIP address.
Flag Indicates whether the row of information applies to connections
or requests:
• C – The statistics listed in this row are for connections.
• R – The statistics listed in this row are for HTTP requests.
Current Current number of connections or requests.
Rate Current connection or request rate, which is the number of connec-
tions or requests per second.
Over Limit Number of times client connections or requests exceeded the
con- figured limit.
Over Rate Limit Number of times client connections or requests exceeded the
con- figured rate limit.
Example The following command shows PBSLB black/white-list information for an ACOS device:
ACOS#show pbslb
Total number of PBSLB configured: 1
Virtual server Port Blacklist/whitelist GID Connection # (Establish Reset Drop)
------------------------------------------------------------------------------
PBSLB_VS1 80 sample-bwlist 2 0 0 0
4 0 0 0
Field Description
Total number of PBSLB configured Number of black/white lists imported onto the ACOS device.
Virtual server SLB virtual server to which the black/white list is bound.
Port Protocol port.
Blacklist/whitelist Name of the black/white list.
GID Group ID.
Connection # Establish Number of client connections established to the group and protocol port.
Connection # Reset Number of client connections to the group and protocol port that were reset.
Connection # Drop Number of client connections to the group and protocol port that were dropped.
Example The following command shows PBSLB information for VIP “vs-22-4”:
-------+-----------+-----------+-----------+-----------|-----------+------------
Virtual server: vs-22-4 Port: 80 B/W list: test
1 88 0 3 2 0 0
2 112 0 2 0 0 1
3 29 0 0 0 0 0
4 11 1 0 0 0 0
show pki
Description Shows information about the certificates on the ACOS device device.
Option Description
ca-cert cert-name Shows the CA certificate.
cert-name specifies a name for the certificate, and you can a
name with a maximum of 255 characters.
cert cert-name Shows information about the certificates on the ACOS device
device. To display information for a specific certificate, use the
cert-name option. To display additional details about the
certifi- cate, use the detail option.
crl Shows information about the Certificate Revocation Lists
(CRLs) that have been imported to the ACOS device device.
[all-partitions | partition | Allows you to select what type of information you want to
sort-by] dis- play:
• All partitions
• A specific partition
You can display information from the shared partition or from a
specific L3V partition.
• Sort by the certificate files
Mode All
show poap
Description Display the Power On Auto Provisioning (POAP) mode.
Mode All
ACOS(config)#show poap
Disabled
show process
system
Description Display the status of system processes.
Usage For descriptions of the system processes, see the “System Overview” chapter of the System
Configuration and Administration Guide.
Example The following command shows the status of system processes on an ACOS device:
ACOS#show process
system a10mon is
running syslogd is
running a10logd is
running a10timer is
running a10Stat is
running
a10hm is running
a10switch is running
a10rt is running
a10rip is running
a10ospf is running
a10snmpd is running
a10gmpd is running
a10wa is running
a10lb is running
show radius-server
Description Display statistics about a RADIUS server.
ACOS(config)#show radius-server
Radius server : 10.0.0.0
contact start : 5
contact failed : 3
authentication success : 1
authentication failed :
1
authorization success : 1
ACOS(config)#
Mode All
show reboot
Description Display scheduled system reboots.
Mode All
Example The following command shows a scheduled reboot on the ACOS device:
ACOS#show reboot
Reboot scheduled for 04:20:00 PST Sun Apr 20 2008 (in 63 hours and 16
minutes) by admin on 192.168.1.144
Reboot reason: Outlook_upgrade
show route-map
Description Show the configured route maps.
Mode All
Parameter Description
file-num Log file number.
bgpd [file-num] Displays the specified BGP log file, or all BGP log files.
isisd [file-num] Displays the specified IS-IS log file, or all IS-IS log files.
nsm [file-num] Displays the specified Network Services Module (NSM) log
file, or all NSM log files.
ospf6d [file-num] Displays the specified IPv6 OSPFv3 log file, or all OSPFv3
log files.
ospfd [file-num] Displays the specified IPv4 OSPFv2 log file, or all OSPFv2
log files.
ripd [file-num] Displays the specified IPv4 RIP log file, or all IPv4 RIP log files.
ripngd [file-num] Displays the specified IPv6 RIP log file, or all IPv6 RIP log files.
Mode All
show running-config
Description Display the running-config.
This command is used to view the running-config in the partition where the command is
issued. To view the running-config for a different partition, use the show partition-
config command.
Usage This command displays the entire running-config in the current partition.
Example The following example shows the running-config for SLB virtual servers:
show scaleout
Description Command related to Scaleout configuration are available in the Configuring Scaleout guide.
show session
Description Display session information.
radius |
sctp |
server [name] |
sip [addr-suboptions] |
sixrd-nat64 [suboptions] |
virtual-server [name]
]
Parameter Description
brief Displays summary statistics for all session types.
dns-id-switch Displays statistics for DNS switch sessions.
ds-lite Displays statistics for DS-Lite sessions. The following options are available:
• dest-port num—View sessions with the specified destination port (1-65535).
• dest-v4-addr ipaddr[/length]—View sessions with the specified destination IPv4
address.
• dest-v6-addr ipaddr[/length]—View sessions with the specified destination IPv6
address.
• source-port num—View sessions with the specified source port (1-65535).
• source-v4-addr ipaddr[/length]—View sessions with the specified source
IPv4 address.
• source-v6-addr ipaddr[/length]—View sessions with the specified source
IPv6 address.
Not all suboptions are available for use in conjunction with others. For example, if the first subop-
tion you enter is dest-addr, the only additional suboption you can specify is dest-port.
Parameter Description
ipv6 Displays information for IPv6 sessions. The following address suboptions are available:
• dest-port num—View sessions with the specified destination port (1-65535).
• dest-v6-addr ipaddr[/length]—View sessions with the specified destination IPv6
address.
• source-port num—View sessions with the specified source port (1-65535).
• source-v6-addr ipaddr[/length]—View sessions with the specified source
IPv6 address.
Not all suboptions are available for use in conjunction with others. For example, if the first subop-
tion you enter is dest-addr, the only additional suboption you can specify is dest-port.
sixrd-nat64 Displays 6rd-NAT64 session statistics. The available suboptions are the same as for ds-lite (see
above).
virtual-server Displays sessions for virtual servers, or a specific virtual server name.
[name]
Mode All
Usage For convenience, you can save session display options as a session filter. (See “session-filter”
on page 188.)
After entering the clear session command, the ACOS device may remain in session-
clear mode for up to 10 seconds. During this time, any new connections are sent to the delete
queue for clearing.
Example The following command lists information for all IPv4 sessions:
Total Sessions: 2
Field Description
TCP Established Number of established TCP sessions.
TCP Half Open Number of half-open TCP sessions. A half-open session is one for which the ACOS device has not yet
received a SYN ACK from the backend server.
TCP Half Close Number of half-closed TCP sessions. A half-closed TCP session is a session in which the server sends a
FIN but the client does not reply with an ACK.
UDP Number of UDP sessions.
Non TCP/UDP IP Number of IP sessions other than TCP or UDP sessions.
sessions This counter applies specifically to IP protocol load balancing. (See the “IP Protocol Load Balancing”
chapter in the Application Delivery and Server Load Balancing Guide.)
Other Number of internally used sessions. As an example, internal sessions are used to hold fragmentation
information.
Reverse NAT TCP Number of reverse-NAT TCP sessions.
Reverse NAT UDP Number of reverse-NAT UDP sessions.
Free Buff Count Number of IO buffers currently available.
Curr Free Conn Number of Layer 4 sessions currently available.
Conn Count Number of connections.
Conn Freed Number of connections freed after use.
TCP SYN Half Number of half-open TCP sessions. These are sessions that are half-open from the client’s perspective.
Open
Conn SMP Alloc Statistics for session memory resources.
Conn SMP Free
Conn SMP Aged
Conn Type 0-4
Available
Conn SMP Type
0-4 Available
Prot Transport protocol.
Field Description
Forward Source Client IP address when connecting to a VIP.
Notes:
• For DNS sessions, the client’s DNS transaction ID is shown instead of a protocol port number.
• The output for connection-reuse sessions shows 0.0.0.0 for the forward source and forward
desti- nation addresses.
• For source-IP persistent sessions, if the option to include the client source port (incl-
sport) is enabled in the persistence template, the client address shown in the Forward
Source column includes the port number.
• IPv4 client addresses – The first two bytes of the displayed value are the third and fourth
octets of the client IP address. The last two bytes of the displayed value represent the client
source port. For example, “155.1.1.151:33067” is shown as “1.151.129.43”.
• IPv6 client addresses – The first two bytes in the displayed value are a “binary OR” of the first
two bytes of the client’s IPv6 address and the client’s source port number. For example,
“2001:ff0:2082:1:1:1:d1:f000” with source port 38287 is shown as
“b58f:ff0:2082:1:1:1:d1:f000”.
Also see the output examples below.
Forward Dest VIP to which the client is connected.
Reverse Source Real server’s IP address.
Note: If the ACOS device is functioning as a cache server (RAM caching), asterisks ( * ) in this field
and the Reverse Dest field indicate that the ACOS device directly served the requested content to the
cli- ent from the ACOS RAM cache. In this case, the session is actually between the client and the
ACOS device rather than the real server.
Reverse Dest IP address to which the real server responds.
• If source NAT is used for the virtual port, this address is the source NAT address used by the
ACOS device when connecting to the real server.
• If source IP NAT is not used for the virtual port, this address is the client IP address.
Age Number of seconds since the session started.
Hash CPU ID.
Flags This is an internal flag used for debugging purposes. This identifies the attributes of a session.
Type Indicates the session type, which can be one of the following:
• SLB-L4 – SLB session for Layer 4 traffic.
• SLB-L7 – SLB session for Layer 7 traffic.
• NAT – Network Address Translation (NAT) session for dynamic NAT.
• ST-NAT – NAT session for static NAT.
• ACL – Session for an ACL.
• TCS – Transparent Cache Switching session.
• XNT – Transparent session.
• TCP Established
• TCP Half Open
• UDP
• Non TCP/UDP IP sessions
• Other
• Reverse NAT TCP
• Reverse NAT UDP
The other counters apply to all partitions, regardless of the partition from which the
command is entered.
Example The following command displays the IPv4 session for a specific source IP address:
Example The following commands display IPv4 source-IP persistent sessions, clear one of the
sessions, then verify that the session has been cleared:
In this example, IPv4 source-IP persistent sessions are shown. The incl-sport option in
the source-IP persistence template is enabled, so the value shown in the Forward Source
column is a combination of the client source IP address and source port number. The first
two bytes of the displayed value are the third and fourth octets of the client IP address. The
last two bytes of the displayed value represent the client source port.
[2001:ff0:2082:4:1:1:f000:1e4]:6880 300
In the output above, the Forward Source column shows the client’s IPv6 address but does
not show the port number. The port number is omitted because the incl-sport option
in the source-IP persistence template is disabled.
In the output below, the same client IPv6 address is shown. However, in this case, the
incl- sport option in the source-IP persistence template is enabled. Therefore, the
Forward Source column includes the port number. The first two bytes in the displayed value
are a “binary OR” of the first two bytes of the client’s IPv6 address and the client's source
port number. In this example, the Forward source value is “b58f:ff0:2082:1:1:1:d1:f000”. The
first two bytes, “b58f”, are a “binary OR” value of “2001” and port number 38287.
The session table contains a separate session for each RADIUS Identifier value. The
following address information is shown for each session:
• Forward Source – The sender of the RADIUS message. This is the IP address of the BRAS.
• Forward Dest – The RADIUS VIP on the ACOS device.
• Reverse Source – The RADIUS server to which the ACOS device sends requests
that have the Identifier listed in the RADIUS ID field.
• Reverse Dest – The destination of the RADIUS server reply forwarded by the ACOS
device. (This is the sender of the initial RADIUS message that started the session, the
BRAS in the example above.)
Example The following example displays the output when viewing the sessions on a real server
named “s2” whose IP address is 172.16.1.11:
show sflow
Description Show sFlow information.
Mode All
show shutdown
Description Display scheduled system shutdowns.
ACOS#show shutdown
Shutdown scheduled for 12:00:00 PST Sat Jan 19 2008 (in 358 hours and
23 minutes) by admin on 192.168.1.144
Shutdown reason: Scheduled shutdown
show slb
Description See “SLB Show Commands” in the Command Line Interface Reference for ADC.
show smtp
Description Display SMTP information.
Mode All
ACOS#show smtp
SMTP server address: 192.168.1.99
show snmp
Description Display SNMP OIDs.
Parameter Description
server svr-name Returns OIDs for the axServerStatTable.
If a name is specified, this command returns OIDs for the axServerPortStatTable.
service-group sg-name Returns OIDs for the axServiceGroupStatTable.
If a name is specified, this command returns OIDs for the axServerPortStatTable.
You can narrow the command output by specifying the IP address type for addr-type or
specific service-group member. Valid address types are firewall, tcp, or udp.
virtual-server vs-name Returns OIDs for the axVirtualServerStatTable.
If a name is specified, this command returns OIDs for the axVirtualServerPortStatTable.
port port-num Returns OIDs for the specific port of a virtual server.
If no port is specified, this command returns OIDs for all virtual port entries of the speci-
fied VIP.
Mode All
Example The sample command output below narrows the displayed OIDs for TCP IP addresses:
axServerPortStatusInServiceGroupMemberStat:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.12.3.115.103.49.2.2.115.50.80
axServiceGroupMemberStatTotalL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.13.3.115.103.49.2.2.115.50.80
axServiceGroupMemberStatTotalCurrL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.14.3.115.103.49.2.2.115.50.80
axServiceGroupMemberStatTotalSuccL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.15.3.115.103.49.2.2.115.50.80
axServiceGroupMemberStatResponseTime:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.16.3.115.103.49.2.2.115.50.80
axServiceGroupMemberStatPeakConns:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.17.3.115.103.49.2.2.115.50.80
service-group-name sg1: type 2: server-name s1: port 80
==========================================================================
axServiceGroupMemberStatName:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.1.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatAddrType:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.2.3.115.103.49.2.2.115.49.80
axServerNameInServiceGroupMemberStat:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.3.3.115.103.49.2.2.115.49.80
axServerPortNumInServiceGroupMemberStat:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.4.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatPktsIn:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.5.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatBytesIn:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.6.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatPktsOut:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.7.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatBytesOut:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.8.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatPersistConns:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.9.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatTotConns:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.10.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatCurConns:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.11.3.115.103.49.2.2.115.49.80
axServerPortStatusInServiceGroupMemberStat:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.12.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatTotalL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.13.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatTotalCurrL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.14.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatTotalSuccL7Reqs:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.15.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatResponseTime:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.16.3.115.103.49.2.2.115.49.80
axServiceGroupMemberStatPeakConns:
1.3.6.1.4.1.22610.2.4.3.3.4.1.1.17.3.115.103.49.2.2.115.49.80
Example This output narrows the displayed OIDs for the service-group member “s1”:
NOTE: SNMP statistics also are included automatically in show techsupport output.
Mode All
show startup-config
Description Display a configuration profile or display a list of all the locally saved configuration profiles.
Parameter Description
profile profile-name Displays the commands that are in the specified configuration profile.
all Displays a list of the locally stored configuration profiles.
Parameter Description
all-partitions Shows all resources in all partitions. In this case, the resources in the shared parti-
tion are listed first. Then the resources in each private partition are listed, organized
by partition.
partition Shows only the resources in the specified partition.
{shared | partition-name}
Mode All
Usage The profile name must be specified before any partition names.
When entered without the all or profile-name option, this command displays the
contents of the configuration profile that is currently linked to “startup-config”. Unless you
have relinked “startup-config”, the configuration profile that is displayed is the one that is
stored in the image area from which the ACOS device most recently rebooted.
Example The following example shows how to view the startup-config in partition “companyB”
(trun- cated for brevity):
exit
!
...
show statistics
Description Display packet statistics for Ethernet interfaces.
Mode All
Example The following command shows brief statistics for all Ethernet interfaces on an ACOS device:
Example The following command shows detailed statistics for Ethernet interface 1:
Port 1 Counters:
InBufAllocFailed 0
InUtilization 15 OutUtilization 0
show store
Description Display the configured file transfer profiles in the credential store. The credential store is
a saved set of access information for file transfer between the ACOS device and remote
file servers.
Mode All
show switch
Description Display internal system information from the ASIC registers for troubleshooting.
NOTE: This command is only supported on some AX Series devices, and not all parameters
are supported on all devices. Use the “?” character to find out whether or not this
command is supported on your system, and which parameters are supported.
Parameter Description
debug View debug information.
mac-table View the MAC addresses configured on the ASIC.
vlan-table View the VLANs configured on the ASIC.
xfp-temp View the XFP temperatures.
Mode All
Mode All
CPU load sharing can be configured using the system cpu-load-sharing command.
Parameter Description
statistics Shows CPU load sharing statistics.
detail Show per-CPU counters.
Mode All
Example The following command shows output from the CPU load sharing feature. In this example,
the counter for the “Load Sharing Trggered” field is incremented every time a CPU enters
into load-sharing mode. Similarly, the counter for the “Load Sharing Untriggered” field is
incre- mented every time a CPU is subsequently removed from load-sharing mode.
Example If the command is used without the statistics option, then the output simply
displays which CPUs are in load-sharing mode. The example below shows that CPU 1,
CPU 2, and CPU 3 are in load-sharing mode.
cpu-packet-statistics |
busy-counter |
interface-stats |
statistics
}
Parameter Description
buffer-stats Shows counters for buffer statistics.
cpu-packet-statistics Shows per-CPU packet statistics.
busy-counter Shows counters for system busy statistics.
interface-stats Shows counters for interface statistics.
statistics Shows counters for internal statistics.
Mode All
Mode All
For example, the “l4-session-count” row of the output shows the number of Layer 4 sessions
that are currently in use, as well as the maximum number currently supported by the
configuration (the default maximum), and the range of values that can be assigned to the
default maximum.
In general, if a resource listed in the output has the same value in the Current and Maximum
columns (GSLB resources, for example), then the allocation for that resource can not be
changed.
Mode All
Usage To change system resource usage settings, see “system resource-usage” on page 200 com-
mand.
You must reload or reboot the system after making changes to system resource-usage
settings in order to place the changes into effect. For most system resource-usage settings, a
reload is sufficient. However, a change to the l4-session-count setting requires a reboot.
If the target device is not reloaded, the system resource-usage settings synchronized
from the active device appear in the standby device’s running-config, but do not actually
take effect until the reload or reboot.
• If you manually synchronize the configuration, you have the option to reload the target
device immediately following the synchronization. If you do not use this option, you
can reload the device later.
• If you are using VRRP-A in combination with aVCS, configuration synchronization is
automatic. In this case, you must reload or reboot the target device to place the
system resource-usage changes into effect.
NOTE: The target device is not automatically reloaded following configuration synchroni-
zation.
The following table describes the fields in this output for each resource.
Field Description
Current Number of resources (for example, Layer 4 sessions) currently in use.
Default Default number of maximum resources (for example, Layer 4
sessions) that can be configured based on the current configuration.
Minimum Minimum number of resources (for example, Layer 4 sessions) that
can be configured.
Maximum Maximum number of resources (for example, Layer 4 sessions)
that can be configured.
show tacacs-server
Description Display TACACS statistics.
Parameter Description
hostname Only display information for the server with the specified host name.
ipaddr Only display information for the server with the specified IP address.
Mode All
Usage This command is available at all configuration levels, but the option to view information for
a specified server is only available at Global configuration mode or higher.
Example The following command shows information for TACACS server 5.5.5.5:
show techsupport
Description Display or export system information for use when troubleshooting.
Option Description
export Export the output to a remote server.
use-mgmt-port Use the management port to perform the export.
url The file transfer protocol, username (if required), and directory path.
You can enter the entire URL on the command line or press Enter to display a prompt for each
part of the URL. If you enter the entire URL and a password is required, you will still be
prompted for the password.
To enter the entire URL:
tftp://host/file
ftp://[user@]host[:port]/file
scp://[user@]host/file
sftp://[user@]host/file
page Shows the information page by page. Without this option, all the command’s output is sent
to the terminal at once.
Example Below is an example of the output for this command using the page option:
show terminal
Description Show the terminal settings.
Mode All
ACOS#show terminal
Idle-timeout is 00:59:00
Length: 32 lines, Width: 90 columns
Editing is enabled
History is enabled, history size is 256
Auto size is enabled
Terminal monitor is off
Terminal prompt format: hostname
Command timestamp format: none
show tftp
Description Display the currently configured TFTP block size.
Mode All
show trunk
Description Show information about a trunk group.
Mode All
Field Description
Trunk ID ID assigned to the trunk by the admin who configured it.
Member Count Number of ports in the trunk.
Trunk Status Indicates whether the trunk is up.
Members Port numbers in the trunk.
Cfg Status Configuration status of the port.
Oper Status Operational status of the port.
Ports-Threshold Indicates the minimum number of ports that must be up in order for
the trunk to remain up.
If the number of up ports falls below the configured threshold, ACOS
automatically disables the trunk’s member ports. The ports are dis-
abled in the running-config. The ACOS device also generates a log
message and an SNMP trap, if these services are enabled.
Timer Indicates how many seconds the ACOS device waits after a port goes
down before marking the trunk down, if the ports threshold is
exceeded.
Running Indicates whether the ports-threshold timer is currently
running. When the timer is running, a port has gone down but
the state change has not yet been applied to the trunk’s
state.
Working Lead Port number used for responding to ARP requests.
NOTE: If the lead port is shown as 0 or “None”, the trunk interface is
down.
show vcs
Description aVCS-specific show commands are available in Configuring ACOS Virtual Chassis Systems.
show version
Description Display software, hardware, and firmware version information.
Mode All
Example Below is sample output for this command; note that the output on your system will
differ depending on your specific platform.
Parameter Description
vlan-id View counters for the specified VLAN only (2-4094).
Mode All
show vlans
Description Display the configured VLANs.
Parameter Description
vlan-id View information for the specified VLAN only (1-4094).
Mode All
Example The following command lists all the VLANs configured on an ACOS device:
Router Interface: ve 60
show vpn
Description Show VPN information.
Parameter Description
all-partitions Show VPN configuration summary for all partitions.
crl Show cached VPN Certificate Revocation Lists (CRL) certificates.
default Show default VPN configuration.
ike-sa Show VPN IKE Security Association (SA).
ike-stats Show VPN IKE statistics.
ike-stats-global Show VPN IKE global statistics.
ipsec-sa Show VPN IPsec Security Association (SA).
log Show VPJN log and debug information.
ocsp Show cached VPN Online Certificate Status Protocol (OCSP)
cer- tificates.
partition Show VPN configuration for the specified partition only.
Mode All
IKE SA total: 0
IPsec SA total: 0
show vrrp-a
Description All show commands related to VRRP-A are available in Configuring VRRP-A High Availability.
show waf
Description Display information for the Web Application Firewall (WAF). See the Web Application
Firewall Guide.
show web-category
Description Show information the about current operation of the Web Category feature.
Parameter Description
bypassed- Lists the URLs bypassed by the Web Category feature.
urls
num – Specifies the number of URLs to list, 1-8000. The most
[num | all]
recently bypassed URLs, up to the number you specify, are listed.
all – Displays the entire list of URLs bypassed by the feature.
The entries are listed beginning with the most recently bypassed
URL on top. If a URL is bypassed multiple times, the URL is listed
separately for each time it bypassed.
By default, the 50 most recent entries are shown.
Mode All
Example The following command shows the URLs bypassed by the Web Category feature:
paper.example.com
paper.example.com
step.example.com
metrics1.example.com
step.example.com
paper.example.com
online.example.com
...
Example The following command shows information about the currently loaded BrightCloud data-
base:
Example The following command shows the URLs intercepted by the Web Category feature:
Default versioncheck-bg.addons.example.org
versioncheck-bg.addons.example.org
services.addons.example.org
aus3.example.org
fhr.data.example.com
...
Example The following commands show the web categories to which some individual URLs belong.
In this example, the categories for the URLs in the ACOS device’s local database match
the most recent categorizations from the BrightCloud server.
Example The following command shows the current version of the Web Category engine:
The AX debug subsystem enables you to trace packets on the ACOS device. To access the AX debug subsystem, enter the
following command at the Privileged EXEC level of the CLI:
ACOS# axdebug
ACOS(axdebug)#
1. Use the filter command to configure packet filters to match on the types of packets to capture.
2. (Optional) Use the count command to change the maximum number of packets to capture.
3. (Optional) Use the timeout command to change the maximum number of minutes during which to capture packets.
4. (Optional) Use the incoming | outgoing command to limit the interfaces on which to capture traffic.
5. Use the capture command to start capturing packets. The ACOS device begins capturing packets that match the
filter, and saves the packets to a file or displays them, depending on the capture options you specify.
6. To display capture files, use the show axdebug file command.
7. To export capture files, use the export command at the Privileged EXEC or global configuration level of the CLI.
The AXdebug utility creates a debug file in packet capture (PCAP) format. The PCAP format can be read by third-party
diag- nostic applications such as Wireshark, Ethereal (the older name for Wireshark) and tcpdump. To simplify export of
the PCAP file, the ACOS device compresses it into a zip file in tar format. To use a PCAP file, you must untar it first.
• apply-config
• capture
• count
• delete
• filter
• incoming | outgoing
• length
• maxfile
• outgoing
• save-config
• timeout
apply-config
Description Apply an AXdebug configuration file.
Replace file with the name of an existing AXdebug configuration file (1-63 characters).
Mode AX debug
Example The following example applies the debug configuration saved in the example-ax-debug file:
ACOS# axdebug
ACOS(axdebug)# apply-config testfile
Applying debug commands
Done
example-ax-debug has been applied.
ACOS(axdebug)#
capture
Description Start capturing packets.
Parameter Description
brief [save ...] Captures basic information about packets. (For save options, see save filename
below.)
detail [save ...] Captures packet content in addition to basic information. (For save options, see
save filename below.)
non-display [save ...] Does not display the captured packets on the terminal screen. Use the save
options to configure a file in which to save the captured packets.
save filename Saves captured packets in a file:
[max-packets]
• filename – Specifies the name of the packet capture file.
[incoming [portnum ...]]
[outgoing [portnum ...]] • max-packets – Specifies the maximum number of packets to capture in the
file, 0-65535. To save an unlimited number of packets in the file, specify 0.
• incoming [portnum ...] – Captures inbound packets. You can specify
one or more physical Ethernet interface numbers. Separate the interface
numbers with spaces. If you do not specify interface numbers, inbound traffic on
all physical Ethernet interfaces is captured.
• outgoing [portnum ...] – Captures outbound packets on the specified
phys- ical Ethernet interfaces or on all physical Ethernet interfaces. If you do not
specify interface numbers, outbound traffic on all physical Ethernet interfaces is
captured.
Default By default, packets in both directions on all Ethernet data interfaces are captured.
Mode AX debug
To display a list of AX debug capture files or to display the contents of a capture file, see
“show axdebug file” on page 250.
Example The following command captures brief packet information for display on the terminal
screen. The output is not saved to a file.
ACOS# axdebug
ACOS(axdebug)# capture brief
Wait for debug output, enter <ctrl c> to exit
(0,1738448) i( 1, 0, cca8)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 SA
78f07ab8:dbffc02d(0)
(0,1738448) o( 3, 0, cca8)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 SA
78f07ab8:dbffc02d(0)
(0,1738448) i( 1, 0, cca9)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 A
78f07ab9:dbffc0c2(0)
(0,1738448) o( 3, 0, cca9)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 A
78f07ab9:dbffc0c2(0)
(1,1738450) i( 1, 0, ccaa)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 PA
78f07ab9:dbffc0c2(191)
(1,1738450) o( 3, 0, ccaa)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 PA
78f07ab9:dbffc0c2(191)
(1,1738450) i( 1, 0, ccab)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 FA
78f07b78:dbffc0c3(0)
(1,1738450) o( 3, 0, ccab)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13632 FA
78f07b78:dbffc0c3(0)
...
• 0 – CPU ID. Indicates the CPU that processed the packet. CPU 0 is the control CPU.
• 1738448 – Time delay between packets. This is a jiffies value that increments in 4-
milli- second (4-ms) intervals.
• i – Traffic direction: 1 (input) or o (output).
• (1, 0, cca8) – Ethernet interface, VLAN tag, and packet buffer index. If the VLAN tag
is 0, then the port is untagged. In this example, the first packet is received on Ethernet
port 1, and the VLAN is not yet known. The packet is assigned to buffer index cca8.
NOTE: Generally, the VLAN tag for ingress packets is 0. It is normal for the ingress VLAN tag
to be 0 even when the egress VLAN tag is not 0.
The source and destination IP addresses are listed next, followed by the source and
destination protocol port numbers.
• S – Syn
• SA – Syn Ack
• A – Ack
• F – Fin
• PA – Push Ack
The TCP sequence number and ACK sequence number are then shown.
Example The following command captures packet information and packet contents for display on the
terminal screen. The output is not saved to a file.
ACOS# axdebug
ACOS(axdebug)# capture detail
Wait for debug output, enter <ctrl c> to exit
i( 1, 0, ccae)> ip 10.10.11.30 > 30.30.31.30 tcp 80 > 13638 SA 7ab6ae46:ddb87996(0)
Dump buffer(0xa6657048), len(80 bytes)...
0xa6657048: 00900b0b 3e83001d 09f0dec2 08004500 : ....>........E.
0xa6657058: 003c0000 40004006 e8580a0a 0b1e1e1e : .<..@[email protected]......
0xa6657068: 1f1e0050 35467ab6 ae46ddb8 7996a012 : ...P5Fz..F..y...
Example The following command saves captured packet information in file “file123”. The captured
traffic is not displayed on the terminal screen.
ACOS# axdebug
ACOS(axdebug)# capture save file123
count
Description Specify the maximum number of packets to capture.
Replace num with the maximum number of packets to capture, 0-65535. To capture
an unlimited number of packets, specify 0.
Default 3000
Mode AX debug
Example The following command sets the maximum number of packets to capture to 2048:
ACOS# axdebug
ACOS(axdebug)# count 2048
delete
Description Delete an axdebug capture file.
Default N/A
Mode AX debug
ACOS# axdebug
ACOS(axdebug)# delete file123
filter
Description Configure an AX debug filter, to specify the types of packets to capture.
This command changes the CLI to the configuration level for the specified AX debug filter,
where the following AX debug filter-related commands are available:
Command Description
dst Matches on the specified destination IP address, MAC
{ip ipaddr | mac macaddr | port portnum} address, or protocol port number.
l3-proto {arp | ip | ipv6} Matches on the specified Layer 3 protocol.
ip ipaddr {subnet-mask | /mask-length} Matches on the specified IPv4 address.
mac macaddr Matches on the specified MAC address.
offset position length bytes operator Matches on the specified length of bytes and value of those
value bytes within the packet:
• position – Starting position within the packet, 1-
65535 bytes.
• bytes – Number of consecutive bytes to filter on, from
1- 65535, beginning at the offset position.
• operator – One of the following:
• > (greater than)
• >= (greater than or equal to)
• <= (smaller than or equal to)
• < (smaller than)
• = (equal to)
• range min-value max-value (select a range)
• value – String to filter on.
port min-portnum max-portnum Matches on the specified range of protocol port numbers.
Command Description
proto Matches on the specified protocol or protocol port number.
{icmp | icmpv6 | tcp | udp | portnum}
src Matches on the specified source IP address, MAC address,
{ip ipaddr | mac macaddr | port port-num} or protocol port number.
Default No filters are configured by default. When you create one, all packets match the filter
by default.
Mode AX debug
Usage If a packet capture is running and you change the filter, there will be a 5-second delay
while the ACOS device clears the older filter. The delay does not occur if a packet capture
is not already running.
The packet filter for the debug command is internally numbered filter 0. In AXdebug,
you can create multiple filters, which are uniquely identified by filter ID. If you create
filter 0 in AXdebug, this filter will overwrite the debug packet filter. Likewise, if you
configure filter 0 in AXdebug, then configure the debug packet filter, the debug packet
filter will overwrite AXdebug filter 0.
Example The following commands configure an AX debug filter to match on source IP address
10.10.10.30, destination protocol port number 80, and source MAC address
aabb.ccdd.eeff. The show axdebug filter command displays the filter.
ACOS# axdebug
ACOS(axdebug)# filter 1
ACOS(axdebug-filter:1)# src ip 10.10.10.30
ACOS(axdebug-filter:1)# dst port 80
ACOS(axdebug-filter:1)# src mac aabb.ccdd.eeff
ACOS(axdebug-filter:1)# exit
ACOS(axdebug)# show axdebug filter
axdebug filter 1
src ip 10.10.10.30
dst port 80
src mac aabb.ccdd.eeff
incoming | outgoing
Description Specify the Ethernet interfaces and traffic direction for which to capture packets.
Default Disabled
Mode AX debug
Example The following command limits the packet capture to inbound packets on Ethernet interface
3 and outbound packets on Ethernet interface 4:
ACOS# axdebug
ACOS(axdebug)# incoming 3 outgoing 4
Example The following command limits the packet capture to outbound packets on Ethernet inter-
face 7. Inbound packets on all Ethernet interfaces are captured, unless specified otherwise
in AX debug filters.
ACOS# axdebug
ACOS(axdebug)# outgoing 7
length
Description Specify the maximum length of packets to capture. Packets that are longer are not captured.
Mode AX debug
Example The following command changes the maximum packet length to capture to 128:
ACOS# axdebug
ACOS(axdebug)# length 128
maxfile
Description Specify the maximum number of axdebug packet capture files to keep.
Once the maximum is reached, new axdebug files can not be created until existing files are
removed.
Mode AX debug
Example The following command changes the maximum number of AX debug capture files to
keep to 125:
ACOS# axdebug
ACOS(axdebug)# maxfile 125
outgoing
Description See “incoming | outgoing” on page 371.
save-config
Description Save your AXdebug configuration to a file.
This file can be retrieved at a later time with the apply-config command.
Replace name with the name of the configuration file (1-63 characters).
Mode AX debug
Example The following example saves the AX debug configuration to a file called “example-
ax- debug”:
ACOS# axdebug
ACOS(axdebug)# save-config example-ax-debug
Config has been saved to example-ax-debug.
ACOS(axdebug)#
timeout
Replace minutes with the number of minutes to capture the packets (0-65535).
Default 5 minutes.
Mode AX debug
ACOS# axdebug
ACOS(axdebug)# timeout 10
This chapter lists the cause strings for the numeric cause codes that appear in the Up and Down fields of the show
health stat output. The Up / Down cause codes are shown in the output under “Cause(Up/Down/Retry)”.
Up Causes
Table 12 lists the Up causes.
Down Causes
Table 13 lists the Down causes.