ZXSEC US CLI Reference Guide
ZXSEC US CLI Reference Guide
Version 1.0
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to
support or training are subject to change without notice.
Revision History
Document
ZXSEC US CLI Reference Guide
Name
Document Revision
Product Version V1.0 R1.0
Number
Equipment Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement of
this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
Chapter 1.......................................................................... 1
Chapter 2........................................................................ 29
Chapter 3........................................................................ 45
Alertemail....................................................................... 45
Overview ...........................................................................45
Setting ........................................................................ 45
Chapter 4........................................................................ 53
Antivirus......................................................................... 53
Overview ........................................................................... 53
Filepattern ................................................................... 53
Grayware..................................................................... 55
Heuristic ...................................................................... 57
Quarantine................................................................... 58
Quarfilepattern ............................................................. 62
Service ........................................................................ 63
How File Size Limits Work .................................................... 64
Chapter 5........................................................................ 67
Firewall........................................................................... 67
Overview ........................................................................... 67
Address, Address6 ........................................................ 68
Addrgrp, Addrgrp6 ........................................................ 70
Dnstranslation .............................................................. 71
GTP (US Carrier) ........................................................... 73
IP Macbinding Setting .................................................... 85
IP Macbinding Table ...................................................... 87
IP Pool......................................................................... 89
LDB-Monitor ................................................................. 90
Multicast-Policy............................................................. 92
Policy, Policy6............................................................... 94
Use the Following Steps to Configure NAT in Transparent Mode 110
Profile ....................................................................... 111
Schedule Onetime ....................................................... 175
Schedule Recurring ..................................................... 177
Service Custom .......................................................... 178
Service Group............................................................. 180
VIP ........................................................................... 182
VIP GRP..................................................................... 201
Chapter 7......................................................................207
IMP2P...........................................................................207
Overview ......................................................................... 207
AIM-user ................................................................... 207
ICQ-user.................................................................... 208
MSN-user................................................................... 209
Old-version ................................................................ 210
Policy ........................................................................ 211
Yahoo-user ................................................................ 212
Chapter 8......................................................................215
IPS................................................................................215
Overview ......................................................................... 215
DoS .......................................................................... 215
Config Limit...................................................................... 216
Custom ..................................................................... 219
Decoder..................................................................... 220
Global ....................................................................... 220
Rule .......................................................................... 222
Sensor ...................................................................... 223
Chapter 9......................................................................229
LOG ...............................................................................229
Overview ......................................................................... 229
Custom-field .............................................................. 230
{disk | Usla | memory | syslogd | webtrends | Usservice}
filter.......................................................................... 231
Disk Setting ............................................................... 237
Usla Setting ............................................................... 242
Usservice Setting ........................................................ 243
Memory Setting .......................................................... 244
Memory Global Setting................................................. 245
Syslogd Setting .......................................................... 247
Webtrends Setting ...................................................... 249
Trafficfilter ................................................................. 250
Config Rule ...................................................................... 251
Report Customization .................................................. 252
Report Definition......................................................... 253
Report Filter ............................................................... 254
Report Output ............................................................ 255
Report Period ............................................................. 257
Report Schedule ......................................................... 258
Report Scope.............................................................. 259
Report Selection ......................................................... 261
Report Summary-layout ............................................... 262
Router........................................................................... 267
Overview ......................................................................... 267
Access-list.................................................................. 268
Aspath-list ................................................................. 271
Auth-path .................................................................. 272
BGP .......................................................................... 274
Config Router BGP ............................................................ 277
Config Admin-Distance ...................................................... 282
Config Aggregate-Address .................................................. 283
Config Neighbor................................................................ 284
Config Network................................................................. 290
Config Redistribute............................................................ 292
Community-list ........................................................... 293
Key-chain .................................................................. 296
Multicast .................................................................... 298
Sparse Mode .................................................................... 299
Dense Mode ..................................................................... 300
Syntax ............................................................................ 301
Config Router Multicast ...................................................... 302
Config Interface................................................................ 304
Config Pim-sm-global......................................................... 309
OSPF......................................................................... 314
Syntax............................................................................. 314
Config Router OSPF ........................................................... 317
Config Area ...................................................................... 321
Config Distribute-list .......................................................... 327
Config Neighbor ................................................................ 328
Config Network ................................................................. 329
Config OSPF-Interface........................................................ 329
Config Redistribute ............................................................ 334
Config Summary-Address ................................................... 335
Policy ........................................................................ 336
Prefix-list ................................................................... 340
RIP ........................................................................... 343
Config Router RIP.............................................................. 345
Config Distance................................................................. 347
Config Distribute-list .......................................................... 348
Config Interface ................................................................ 349
Config Neighbor ................................................................ 351
Config Network ................................................................. 352
Config Offset-list ............................................................... 353
Config Redistribute ............................................................ 354
Route-map................................................................. 355
Using Route Maps with BGP ................................................ 358
Static ........................................................................ 364
Static6 ...................................................................... 367
Chapter 12....................................................................369
Spamfilter.....................................................................369
Overview ......................................................................... 369
BWord ....................................................................... 369
Emailbwl.................................................................... 372
USshield .................................................................... 374
IPBWL ....................................................................... 376
IPTrust ...................................................................... 377
MHeader .................................................................... 379
Options ..................................................................... 381
DNSBL....................................................................... 382
Chapter 13.................................................................... 385
Chapter 14....................................................................565
User ..............................................................................565
Overview ......................................................................... 565
Configuring users for authentication .............................. 566
Adgrp........................................................................ 567
Dynamic-profile (US Carrier) ........................................ 568
Endpoint-bwl (US Carrier) ............................................ 571
Endpoint-ip-filter (US Carrier) ....................................... 573
Endpoint-translation (US Carrier) .................................. 574
Fase.......................................................................... 576
Group........................................................................ 578
Ldap ......................................................................... 585
Local ......................................................................... 588
Peer .......................................................................... 590
Peergrp ..................................................................... 592
Radius ....................................................................... 593
Settings..................................................................... 596
Tacacs+..................................................................... 597
Chapter 17....................................................................691
Execute.........................................................................691
Overview ......................................................................... 691
Backup ...................................................................... 693
Batch ........................................................................ 695
CUS reload................................................................. 695
CUS save ................................................................... 696
Clear system arp table ................................................. 697
Cli status-msg-only ..................................................... 697
Cli check-template-status............................................. 698
Date ......................................................................... 698
Dhcp lease-clear ......................................................... 699
Dhcp lease-list............................................................ 699
Disconnect-admin-session ............................................ 699
Factoryreset ............................................................... 700
Formatlogdisk............................................................. 700
Usservice-log update ................................................... 700
Fsae refresh ............................................................... 701
Ha disconnect............................................................. 701
Ha manage ................................................................ 702
Ha synchronize ........................................................... 704
Interface dhcpclient-renew ........................................... 705
Interface pppoe-reconnect ........................................... 705
Log delete-all ............................................................. 706
Log delete-filtered....................................................... 706
Log delete-rolled ......................................................... 707
Log display ................................................................ 707
Log filter.................................................................... 708
Log USanalzyer test-connectivity................................... 710
Log list ...................................................................... 711
Log roll ...................................................................... 712
Modem dial ................................................................ 712
Modem hangup ........................................................... 712
Mrouter clear.............................................................. 712
Ping .......................................................................... 713
Ping-options ............................................................... 714
Ping6 ........................................................................ 716
Reboot ...................................................................... 716
Restore...................................................................... 717
Router clear bgp ......................................................... 719
Router clear bfd .......................................................... 720
Router clear ospf process ............................................. 720
Router restart............................................................. 720
Send-fds-statistics ...................................................... 721
Et-next-reboot............................................................ 721
Shutdown .................................................................. 721
Ssh ........................................................................... 722
Telnet ....................................................................... 722
Time ......................................................................... 722
Traceroute ................................................................. 723
Update-av.................................................................. 723
Update-ips ................................................................. 724
Update-now ............................................................... 724
Upd-vd-license ........................................................... 725
Usb-disk .................................................................... 725
Vpn certificate ca ........................................................ 725
Vpn certificate crl ........................................................ 727
Vpn certificate local ..................................................... 728
Vpn certificate remote ................................................. 731
Vpn sslvpn del-tunnel .................................................. 732
Vpn sslvpn del-web ..................................................... 733
Figures..........................................................................775
Tables ...........................................................................777
Index ............................................................................783
Chapter 1 About this Manual
Chapter Summary
Chapter 1, Using the Describes how to connect to and use the
CLI ZXSEC US CLI.
Chapter 2, Working Describes how to create and administer
with Virtual Domains multiple VDOMs. It also explains how
enabling vdom-admin changes the way
you work with the CLI.
Chapter 3, Alertemail It is an alphabetic reference to the
commands used to configure alertemail.
Chapter 4, Antivirus It is an alphabetic reference to the
commands used to configure antivirus
features.
Chapter 5, Firewall It is an alphabetic reference to the
commands used to configure firewall
policies and settings.
Chapter 6, GUI It is an alphabetic reference to the
commands used to set preferences for the
web-based manager CLI console and
topology viewer.
Chapter 7, IMP2P IMP2P is an alphabetic reference to the
commands used to configure user access
to Instant Messaging and Person-to-Person
applications.
Chapter 8, IPS IPS is an alphabetic reference to the
commands used to configure intrusion
detection and prevention features.
Chapter 9, LOG Log is an alphabetic reference to the
commands used to configure logging.
Chapter 10, Notification It is an alphabetic reference to the
(US Carrier) commands used to configure US Carrier
Chapter Summary
event notification.
Chapter 11, Router Router is an alphabetic reference to the
commands used to configure routing.
Chapter 12, Spamfilter Spamfilter is an alphabetic reference to
the commands used to configure spam
filtering features.
Chapter 13, System system is an alphabetic reference to the
commands used to configure the
ZXSEC US system settings.
Chapter 14, User User is an alphabetic reference to the
commands used to configure authorized
user accounts and groups.
Chapter 15, Vpn VPN is an alphabetic reference to the
commands used to configure ZXSEC US
VPNs.
Chapter 16, Webfilter Webfilter is an alphabetic reference to the
commands used to configure web content
filtering.
Chapter 17, Execute Execute is an alphabetic reference to the
execute commands, which provide some
useful utilities such as ping and traceroute,
and some commands used for
maintenance tasks.
Chapter 18, Get Get is an alphabetic reference to
commands that retrieve status information
about the ZXSEC US unit.
Note:
Diagnose commands are also available from the ZXSEC US CLI.
These commands are used to display system information and for
debugging. Diagnose commands are intended for advanced
users only, and they are not covered in this document. Contact
USnet technical support before using these commands.
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
Typeface Meaning
CAPS Keys on the keyboard and buttons on screens
and company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[] Optional parameters.
{} Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
What’s new
The tables below list commands which have changed since the
previous release, MR5.
Command Change
Click Refers to clicking the primary mouse
button (usually the left mouse button)
once.
config firewall ldb-monitor New command. Configures health check
settings which can be used when
enabling health checks for load balanced
real servers associated with a virtual IP.
config firewall policy, policy6
edit <index_int>
set auth-path New keyword. Enables authentication-
based routing.
set auth-redirect-addr New keyword. Specifies address used in
URL when performing HTTP-to-HTTPS
redirects for policy authentication.
set custom-log-fields New keyword. Selects custom log fields
to append to the policy’s log message.
set sslvpn-auth tacacs+ New SSL VPN client authentication
option. Selects TACACS+ authentication
method when the firewall policy action
is set to ssl-vpn.
config firewall profile Removed filetype option for all protocol
variables (smtp, pop3, etc.). Instead,
the block option is now used in
conjunction with file-pat-table.
edit <profile_str>
set aim block-long-chat New option. Blocks oversize chat
messages.
set ussrv-wf-options redir-block New option redir-block. Blocks
HTTP redirects.
set ussrv-wf-ovrd-group Keyword removed.
set ftp scanextended New option scanextended. Scans for
viruses and worms using the extended
database of virus definitions.
set http scanextended New option scanextended. Scans for
viruses and worms using the extended
database of virus definitions.
set icq archive-full Option archive-full renamed from
content-full.
set icq archive-summary Option archive-summary renamed from
content-meta.
set ips-anomaly Keyword removed. IPS sensors,
formerly signatures, are now configured
by selecting a sensor name.
set icq content-full Option content-full renamed to archive-
full.
Overview
This chapter explains how to connect to the CLI and describes
the basics of using the CLI. You can use CLI commands to view
all system information and to change all system configuration
settings.
This chapter describes:
CLI command syntax
Administrator access
Connecting to the CLI
CLI objects
CLI command branches
CLI basics
Administrator Access
The access profile you are assigned in your administrator
account controls which CLI commands you can access. You need
read access to view configurations and write access to make
changes. Access control in access profiles is divided into groups,
as follows:
T AB L E 4 AC C E S S P R O F I L E C O N T R O L O F AC C E S S T O CLI C OM M AN D S
Antivirus Configuration
antivirus
(avgrp)
Auth Users (authgrp) user
Firewall Configuration
firewall
(fwgrp)
USProtect Update system autoupdate execute update-av
(updategrp) execute update-ips execute update-now
IM, P2P & VoIP
Configuration imp2p
(imp2pgrp)
IPS Configuration
ips
(ipsgrp)
alertemail log
Log & Report (loggrp)
system Usla execute log
execute backup execute batch
Maintenance (mntgrp) execute formatlogdisk execute restore
execute usb-disk
Network Configuration system arp-table system dhcp system
(netgrp) interface system zone
execute clear system arp table
execute dhcp lease-clear execute dhcp
lease-list execute interface
Router Configuration router
(routegrp) execute mrouter execute router
Spamfilter Configuration spamfilter
(spamgrp)
System Configuration system except accprofile, admin, arp-
(sysgrp) table, autoupdate Usla, interface and
zone.
execute cus execute date execute deploy
execute disconnect-admin- session
execute factoryreset execute ha
execute ping execute ping6
execute ping-options execute reboot
execute set-next-reboot execute
shutdown
execute ssh execute telnet execute time
execute traceroute
VPN Configuration vpn
(vpngrp) execute vpn
Webfilter Configuration webfilter
(webgrp)
Note:
The following procedure describes how to connect to the ZXSEC
US CLI using Windows HyperTerminal software. You can use any
terminal emulation program.
To connect to the CLI
1. Connect the ZXSEC US console port to the available
communications port on your computer.
2. Make sure the ZXSEC US unit is powered on.
3. Start HyperTerminal, enter a name for the connection, and
select OK.
4. Configure HyperTerminal to connect directly to the
communications port on the computer to which you have
connected the ZXSEC US console port.
5. Select OK.
6. Select the following port settings and select OK.
Bits per second 9600 (115200 for the ZXSEC US550)
Data bits 8
Parity None
Stop bits 1
Flow control None
7. Press Enter to connect to the ZXSEC US CLI.
A prompt similar to the following appears (shown for the
ZXSEC US550): ZXSEC US550 login:
8. Type a valid administrator name and press Enter.
9. Type the password for this administrator and press Enter.
The following prompt appears:
Welcome!
You have connected to the ZXSEC US CLI, and you can enter
CLI commands.
edit <name_str>
set allowaccess https ssh telnet
end
Note:
Remember to press Enter at the end of each line in the
command example. Also, type end and press Enter to commit
the changes to the ZXSEC US configuration.
3. To confirm that you have configured SSH or Telnet access
correctly, enter the following command to view the access
settings for the interface:
get system interface <name_str>
The CLI displays the settings, including allowaccess, for the
named interface.
Other access methods
The procedure above shows how to allow access only for Telnet
or only for SSH.
If you want to allow both or any of the other management
access types you must include all the options you want to apply.
For example to allow PING, HTTPS and SSH access to an
interface, the set portion of the command is set allowaccess ping
https ssh.
Note:
A maximum of 5 SSH connections can be open at the same time.
To connect to the CLI using SSH
1. Install and start an SSH client.
2. Connect to a ZXSEC US interface that is configured for SSH
connections.
3. Type a valid administrator name and press Enter.
4. Type the password for this administrator and press Enter.
The ZXSEC US model name followed by a # is displayed.
You have connected to the ZXSEC US CLI, and you can enter
CLI commands.
Caution:
Telnet is not a secure access method. SSH should be used to
access the ZXSEC US CLI from the Internet or any other
unprotected network.
Note:
A maximum of 5 Telnet connections can be open at the same
time.
To connect to the CLI using Telnet
1. Install and start a Telnet client.
2. Connect to a ZXSEC US interface that is configured for Telnet
connections.
3. Type a valid administrator name and press Enter.
4. Type the password for this administrator and press Enter.
The following prompt appears:
Welcome!
You have connected to the ZXSEC US CLI, and you can enter CLI
commands.
CLI Objects
The ZXSEC US CLI is based on configurable objects. The top-
level objects are the basic components of ZXSEC US
functionality.
Config Branch
The config commands configure CLI objects, such as the firewall,
the router, antivirus protection, and so on. For more information
about CLI objects, see “CLI objects”.
Top-level objects are containers for more specific lower level
objects that are each in the form of a table. For example, the
firewall object contains tables of addresses, address groups,
policies and protection profiles. You can add, delete or edit the
entries in the table. Table entries consist of keywords that you
can set to particular values.
To configure an object, you use the config command to navigate
to the object’s command “shell”. For example, to configure
administrators, you enter the command
config system admin
The command prompt changes to show that you are now in the
admin shell.
(admin)#
This is a table shell. You can use any of the following commands:
delete Remove an entry from the ZXSEC US configuration. For
example in the config system admin shell, type delete
Note:
When using a set command to make changes to lists that
contain options separated by spaces, you need to retype the
whole list including all the options you want to apply and
excluding all the options you want to remove.
show Show changes to the default configuration in the form of
configuration commands.
Get Branch
Use get to display system status information. For information
about these commands, see “get”.
You can also use get within a config shell to display the settings
for that shell, or you can use get with a full path to display the
settings for a particular object.
To use get from the root prompt, you must include a path to a
shell. The root prompt is the ZXSEC US host name followed by a
#.
Example
The command get hardware status provides information about
various physical components of the ZXSEC US unit.
# get hardware status
Model name: ZXSEC US550
ASIC version: CP SRAM: 64M
CPU: Pentium III (Coppermine) RAM: 250 MB
Compact Flash: 122 MB /dev/hda
Hard disk: 38154 MB /dev/hdc
Network Card chipset: Intel(R) 8255x-based Ethernet Adapter (rev.0x0009)
Note:
Interface names vary for different ZXSEC US models. The
following examples use the interface names for a ZXSEC US550
unit.
Example
When you type get in the config system interface shell,
information about all of the interfaces is displayed.
At the (interface)# prompt, type:
get
The screen displays:
== [ internal ]
name: internal
mode: static
ip: 192.168.20.200 255.255.255.0
status: up
netbios-forward: disable
type: physical ip6-address: ::/0
ip6-send-adv: disable
== [ external ]
name: external
mode: static
ip: 192.168.100.99 255.255.255.0
status: up
netbios-forward: disable
type: physical ip6-address: ::/0
ip6-send-adv: disable
...
Example
When you type get in the internal interface shell, the
configuration values for the internal interface are displayed.
edit internal
At the (internal)# prompt, type:
get
The screen displays:
name : internal
allowaccess : ping https ssh
arpforword : enable
cli_conn_status: 0
detectserver : (null)
gwdetect : disable
ip : 192.168.20.200 255.255.255.0
and so on.
Example
You are working in the config system global shell and want to
see information about the ZXSEC US interfaces.
At the (global)# prompt, type:
get system interface
The screen displays:
== [ internal ]
name: internal
mode: static
ip: 192.168.20.200 255.255.255.0
status: up
netbios-forward: disable
type: physical ip6-address: ::/0
ip6-send-adv: disable
== [ external ]
name: external
mode: static
ip: 192.168.100.99 255.255.255.0
status: up
netbios-forward: disable
type: physical ip6-address: ::/0
ip6-send-adv: disable
...
Example
You want to confirm the IP address and netmask of the internal
interface from the root prompt.
At the # prompt, type:
get system interface internal
The screen displays:
name : internal
allowaccess : ping https ssh
arpforword : enable
cli_conn_status : 0
detectserver : (null)
gwdetect : disable
ip: 192.168.20.200 255.255.255.0
ip6-address: ::/0
ip6-default-life: 1800
...
Show Branch
Use show to display the ZXSEC US unit configuration. By default,
only changes to the default configuration are displayed. Use
show full-configuration to display the complete configuration.
You can use show within a config shell to display the
configuration of that shell, or you can use show with a full path
to display the configuration of the specified object.
To display the configuration of all objects, you can use show
from the root prompt. The root prompt is the ZXSEC US host or
model name followed by a #.
Example
When you type show and press Enter within the internal
interface shell, the changes to the default internal interface
configuration are displayed.
At the (internal)# prompt, type:
show
The screen displays:
config system interface
edit internal
set allowaccess ssh ping https
set ip 192.168.20.200 255.255.255.0
next
end
Example
You are working in the internal interface shell and want to see
the system global configuration. At the (internal)# prompt, type:
show system global
The screen displays:
config system global
set admintimeout 5
set authtimeout 15
set failtime 5
set hostname 'ZXSEC US550'
set interval 5
set lcdpin 123456
set ntpserver '132.246.168.148'
set syncinterval 60
set timezone 04
end
Execute Branch
Use execute to run static commands, to reset the ZXSEC US unit
to factory defaults, to back up or restore ZXSEC US
configuration files. The execute commands are available only
from the root prompt.
The root prompt is the ZXSEC US host or model name followed
by a #.
Example
At the root prompt, type:
execute reboot
and press Enter to restart the ZXSEC US unit.
Diagnose Branch
Commands in the diagnose branch are used for debugging the
operation of the ZXSEC US unit and to set parameters for
displaying different levels of diagnostic information. The
diagnose commands are not documented in this CLI Reference
Guide.
Caution:
Diagnose commands are intended for advanced users only.
Contact USnet technical support before using these commands.
Note:
Interface names vary for different ZXSEC US models. The
following examples use the interface names for a ZXSEC US550
unit.
To configure the primary and secondary DNS server addresses
1. Starting at the root prompt, type:
config system dns
and press Enter. The prompt changes to (dns)#.
2. At the (dns)# prompt, type ?
The following options are displayed.
set unset get show abort end
3. Type set ?
CLI Basics
This section includes:
Command help
Command completion
Recalling commands
Editing commands
Line continuation
Command abbreviation
Environment variables
Encrypted password support
Entering spaces in strings
Entering quotation marks in strings
Entering a question mark (?) in a string
International characters
Special characters
IP address formats
Editing the configuration file
Setting screen paging
Changing the baud rate
Using Perl regular expressions
Command Help
You can press the question mark (?) key to display command
help.
Press the question mark (?) key at the command prompt to
display a list of the commands available and a description of
each command.
Type a command followed by a space and press the question
mark (?) key to display a list of the options available for that
command and a description of each option.
Type a command followed by an option and press the
question mark (?) key to display a list of additional options
available for that command option combination and a
description of each option.
Command Completion
You can use the tab key or the question mark (?) key to
complete commands.
You can press the tab key at any prompt to scroll through
the options available for that prompt.
You can type the first characters of any command and press
the tab key or the question mark (?) key to complete the
command or to scroll through the options that are available
at the current cursor position.
After completing the first word of a command, you can press
the space bar and then the tab key to scroll through the
options available at the current cursor position.
Recalling Commands
You can recall previously entered commands by using the Up
and Down arrow keys to scroll through commands you have
entered.
Editing Commands
Use the Left and Right arrow keys to move the cursor back and
forth in a recalled command. You can also use the Backspace
and Delete keys and the control keys listed in Table 3 to edit the
command.
Line Continuation
To break a long command over multiple lines, use a \ at the end
of each line.
Command Abbreviation
You can abbreviate commands and command options to the
smallest number of non-ambiguous characters. For example, the
command get system status can be abbreviated to g sy st.
Environment Variables
The ZXSEC US CLI supports the following environment variables.
$USERFROM The management access type (SSH, Telnet and so
on) and the IP address of the logged in
administrator.
$USERNAME The user account name of the logged in
administrator.
$SerialNum The serial number of the ZXSEC US unit.
Variable names are case sensitive. In the following example, the
unit hostname is set to the serial number.
config system global
set hostname $SerialNum
end
International Characters
The CLI supports international characters in strings.The web-
based manager dashboard CLI Console applet supports the
appropriate character set for the current administration
language. If you want to enter strings that contain Asian
characters, configure the CLI Console to use the external
command input box.
International character support with external applications such
as SSH clients depends on the capabilities and settings of the
application.
Special Characters
The characters <, >, (, ), #, ’, and ” are not permitted in most
CLI fields. The exceptions are:
passwords
replacemsg buffer
firewall policy comments
ips custom signature
antivirus filepattern
antivirus exemptfilepattern
webfilter bword
spamfilter bword pattern
system interface username (PPPoE mode)
IP Address Formats
You can enter an IP address and subnet using either dotted
decimal or slash-bit format. For example you can type either:
set ip 192.168.1.1 255.255.255.0
or
set ip 192.168.1.1/24
The IP address is displayed in the configuration file in dotted
decimal format.
Note:
Changing the default baud rate is available for ZXSEC US units
with BIOS 3.03 and higher and US version 2.50 and higher.
Expression Matches
abc abc (that exact character sequence, but
anywhere in the string)
^abc abc at the beginning of the string
abc$ abc at the end of the string
a|b either of a and b
^abc|abc$ the string abc at the beginning or at the
end of the string
ab{2,4}c an a followed by two, three or four b's
followed by a c
ab{2,}c an a followed by at least two b's followed
by a c
ab*c an a followed by any number (zero or
more) of b's followed by a c
ab+c an a followed by one or more b's followed
by a c
ab?c an a followed by an optional b followed by
a c; that is, either abc or ac
Expression Matches
a.c an a followed by any single character (not
newline) followed by a c
a\.c a.c exactly
[abc] any one of a, b and c
[Aa]bc either of Abc and abc
[abc]+ any (nonempty) string of a's, b's and c's
(such as a, abba, acbabcacaa)
[^abc]+ any (nonempty) string which does not
contain any of a, b and c (such as deUS)
\d\d any two decimal digits, such as 42; same
as \d{2}
/i makes the pattern case insensitive. For
example, /bad language/i
blocks any instance of “bad language”
regardless of case.
\w+ a "word": a nonempty sequence of
alphanumeric characters and low lines
(underscores), such as foo and 12bar8 and
foo_1
100\s*mk the strings 100 and mk optionally
separated by any amount of white space
(spaces, tabs, newlines)
abc\b abc when followed by a word boundary
(e.g. in abc! but not in abcd)
perl\B perl when not followed by a word
boundary (e.g. in perlert but not in perl
stuff)
\x tells the regular expression parser to
ignore white space that is neither
backslashed nor within a character class.
You can use this to break up your regular
expression into (slightly) more readable
parts.
Overview
By default, the ZXSEC US unit has one virtual domain (root) and
one administrator (admin) with unrestricted access to the
system configuration. If you enable virtual domain configuration,
the super admin account can also:
Use the vdom command to create and configure additional
virtual domains.
Use the global command to create and assign administrators
to each virtual domain.
Use the global command to configure features that apply to
all virtual domains.
This section contains the following topics:
Enabling Virtual Domain Configuration
Accessing commands in virtual domain configuration
Creating and configuring VDOMs
Configuring inter-VDOM routing
Changing the management VDOM
Creating VDOM administrators
Troubleshooting ARP traffic on VDOMs
global
vdom
Accessing Commands in
Virtual Domain Configuration
When you log in as admin with virtual domain configuration
enabled, you have only four top-level commands:
config global Enter config global to access global commands.
In the global shell, you can execute commands
that affect all virtual domains, such as config
system autoupdate.
For a list of the global commands, see “global”.
config vdom Enter config vdom to access VDOM-specific
commands.
In the vdom shell, use the edit <vdom_name>
command to create a new VDOM or to edit the
configuration of an existing VDOM.
In the <vdom_name> shell, you can execute
commands to configure options that apply only
within the VDOM, such as config firewall policy.
For a list of VDOM-specific commands, see “vdom”.
When you have finished, enter next to edit
another vdom, or end.
get system status
see “vdom-link”.
exit Log off.
Creating a VDOM
You create a new VDOM using the config vdom command. For
example, to create a new VDOM
called vdomain2, you enter the following:
config vdom
edit vdomain2
end
This creates a new VDOM operating in NAT/Route mode. You can
have up to 10 VDOMs on your ZXSEC US unit by default.
For this VDOM to be useful, you need to assign interfaces or
VLAN subinterfaces to it.
end
Configuring inter-VDOM
routing
By default, VDOMs are independent of each other and to
communicate they need to use physical interfaces that are
externally connected. By using the vdom-link command that was
added in US v3.0, this connection can be moved inside the
ZXSEC US unit, freeing up the physical interfaces. This feature
also allows you to determine the level of inter-VDOM routing you
want - only 2 VDOMs inter-connected, or interconnect all VDOMs.
The vdom-link command creates virtual interfaces, so you have
access to all the security available to physical interface
connections. These internal interfaces have the added bonus of
being faster the physical interfaces unless the CPU load is very
heavy. As of US v3.0 MR3, BGP is supported over inter-VDOM
links.
VDOM-links can also be configured through the web-based
management interface. For more information, see the ZXSEC US
Administration Guide.
In this example you already have configured two VDOMs called
v1 and v2. You want to set up a link between them. The
following command creates the VDOM link called v12_link. Once
you have the link in place, you need to bind the two ends of the
link to the VDOMs it will be connecting. Then you are free to
apply firewall policies or other security measures.
config global
config system vdom-link
edit v12_link
end
config system interface
edit v12_link0
set vdom v1
next
edit v12_link1
set vdom v2
next
end
Note:
When you are naming VDOM links you are limited to 8
characters for the base name. In the example below the link
name v12_link that is used is correct, but a link name of
v12_verylongname is too long.
Note:
In an HA setup with virtual clusters, inter-VDOM routing must be
entirely within one cluster. You cannot create links between
virtual clusters, and you cannot move a VDOM that is linked into
another virtual cluster. In HA mode, with multiple vclusters
when you create the vdom-link in system vdom-link there is an
option to set which vcluster the link will be in.
Before inter-VDOM routing, VDOMs were completely separate
entities. Now, many new configurations are available such as a
service provider configuration (a number of VDOMS that go
through one main VDOM to access the internet) or a mesh
configuration (where some or all VDOMs are connected to some
or all other VDOMs). These configurations are discussed in-depth
in the ZXSEC US VLANs and VDOMs Guide.
Creating VDOM
Administrators
The super_admin admin accounts can create regular
administrators and assign them to VDOMs. The system admin
command, when accessed by admin, includes a VDOM
assignment.
For example, to create an administrator, admin2, for VDOM
vdomain2 with the default profile prof_admin, you enter:
config global
config system admin
edit admin2
set accprofile prof_admin
set password hardtoguess
set vdom vdomain2
end
The admin2 administrator account can only access the vdomain2
VDOM and can connect only through an interface that belongs to
that VDOM. The VDOM administrator can access only VDOM-
specific commands, not global commands.
Forward-domain Solution
You may run into problems using the multiple VDOMs solution. It
is possible that you have more VLANs than licensed VDOMs, not
enough physical interfaces or your configuration may work
better by grouping some VLANs together. In these situations the
separate VDOMs solution may not work for you.
In these cases, the solution is to use the forward-domain
<collision_group_number> command. This command tags VLAN
traffic as belonging to a particular forward-domain collision
group, and only VLANs tagged as part of that collision group
receive that traffic. By default ports and VLANs are part of
forward-domain collision group 0. For more information, see the
ZXSEC US VLANs and VDOMs Guide.
There are many benefits for this solution from reduced
administration, to using fewer physical interfaces to being able
to allowing you more flexible network solutions.
In the following example, forward-domain collision group 340
includes VLAN 340 traffic on Port1 and untagged traffic on Port2.
Forward-domain collision group 341 includes VLAN 341 traffic on
Port1 and untagged traffic on Port3. All other ports are part of
forward-domain collision group 0 by default.
These are the CLI commands to accomplish this setup.
config system interface
edit “port1”
next
edit "port2"
set forward_domain 340
next
edit “port3”
set forward_domain 341
next
edit "port1-340"
set forward_domain 340
set interface "port1"
set vlanid 340
next
edit "port1-341"
set forward_domain 341
set interface "port1"
set vlanid 341
next
end
There is a more detailed discussion of this issue in the
Asymmetric Routing and Other ZXSEC US Layer-2 Installation
Issues technical note.
Global
From the super_admin accounts, use this command to configure
features that apply to all virtual domains. Virtual domain
configuration (vdom-admin) must be enabled. See “system
global”.
Syntax
This command syntax shows how you access the commands
within config global. For information on these commands, refer
to the relevant sections in this Reference.
config global
config antivirus ...
config firewall service
config gui console
config imp2p ...
config ips ...
config log Usla setting
config log report definition
config log report filter
config log report output
config log report period
execute reboot
execute restore
execute set-next-reboot
execute shutdown
execute time
execute update-av
execute update-ips
execute update-now
execute usb-disk
execute vpn certificate ...
get firewall vip ...
end
Related topics
vdom
VDOM
From the super admin account, use this command to add and
configure virtual domains. The number of virtual domains you
can add is dependent on the ZXSEC US model. Virtual domain
configuration (vdom-admin) must be enabled. See “system
global”.
Once you add a virtual domain you can configure it by adding
zones, firewall policies, routing settings, and VPN settings. You
can also move physical interfaces from the root virtual domain
to other virtual domains and move VLAN subinterfaces from one
virtual domain to another.
By default all physical interfaces are in the root virtual domain.
You cannot remove an interface from a virtual domain if the
interface is part of any of the following configurations:
routing
proxy arp
DHCP server
zone
firewall policy
IP pool
redundant pair
link aggregate (802.3ad) group
Delete these items or modify them to remove the interface first.
You cannot delete the default root virtual domain and you
cannot delete a virtual domain that is used for system
management.
Syntax
This command syntax shows how you access the commands
within config global. Refer to the relevant sections in this
Reference for information on these commands.
config vdom
edit <vdom_name>
config antivirus
config firewall address, address6
config firewall addrgrp, addrgrp6
config firewall dnstranslation
config firewall ipmacbinding setting
config firewall ipmacbinding table
config firewall ippool
config firewall multicast-policy
config firewall policy, policy6
config firewall schedule onetime
config firewall schedule recurring
config firewall service custom
config firewall service group
config firewall vip
config gui
config log {disk | Usla | memory | syslogd | webtrends |
Usservice} filter
config log Usla setting
config log memory setting
config log trafficfilter
config router ...
config system admin
config system arp-table
config system dhcp reserved-address
config system dhcp server
config system gre-tunnel
config system interface
config system ipv6-tunnel
execute set-next-reboot
execute traceroute
execute usb-disk
execute vpn sslvpn del-tunnel
next
edit <another_vdom>
config ...
execute ...
end
end
Note:
The VDOM names vsys_ha and vsys_USfm are in use by the
ZXSEC US unit. If you attempt to name a new VDOM vsys_ha or
vsys_USfm it will generate an error.
Note:
Use config system settings set opmode {nat | transparent} to
set the operation mode for this VDOM to nat (NAT/Route) or
transparent.
Example
This example shows how to add a virtual domain called Test1.
config system vdom
edit Test1
end
Related topics
global
Alertemail
Overview
Use alertemail commands to configure the ZXSEC US unit to
monitor logs for log messages with certain severity levels. If the
message appears in the logs, the ZXSEC US unit sends an email
to a predefined recipient(s) of the log message encountered.
Alert emails provide immediate notification of issues occurring
on the ZXSEC US unit, such as system failures or network
attacks.
By default, the alertemail commands do not appear if no SMTP
server is configured. An SMTP server is configured using the
system alertemail commands. See “system alertemail” for more
information.
When configuring an alert email, you must configure at least one
DNS server. The ZXSEC US unit uses the SMTP server name to
connect to the mail server and must look up this name on your
DNS server. See “dns” for more information about configuring
DNS servers.
This chapter contains the following section:
Setting
Setting
Use this command to configure the ZXSEC US unit to send an
alert email to up to three recipients. This command can also be
configured to send an alert email a certain number of days
before the UDS license expires and/or when the disk usage
exceeds a certain threshold amount. You need to configure an
SMTP server before configuring alert email settings. See “system
alertemail” for more information.
Note:
The ZXSEC US unit must be able to look up the SMTP server
name on your DNS server because the ZXSEC US unit uses the
SMTP server to connect to the mail server. See “system dns” for
more information.
Syntax
config alertemail setting
set username <user-name-str>
set mailto1 <email-address-str>
set mailto2 <email-address-str>
set mailto3 <email-address-str>
set filter-mode <category> <threshold>
set email-interval <minutes-integer>
set severity {alert | critical | debug | emergency | error |
information | notification | warning}
set emergency-interval <minutes-integer>
set alert-interval <minutes-integer>
set critical-interval <minutes-integer>
set error-interval <minutes-integer>
set warning-interval <minutes-integer>
set notification-interval <minutes-integer>
set information-interval <minutes-integer>
set debug-interval <minutes-integer>
set IPS-logs {disable | enable}
set firewall-authentication-failure-logs {disable | enable}
set HA-logs {enable | disable}
set IPsec-error-logs {disable | enable}
set UDS-update-logs {disable | enable}
set PPP-errors-logs {disable | enable}
set sslvpn-authentication-errors-logs {disable | enable}
set antivirus-logs {disable | enable}
set webfilter-logs {disable | enable}
set configuration-changes-logs {disable | enable}
set violation-traffic-logs {disable | enable}
set admin-login-logs {disable | enable}
set local-disk-usage-warning {disable | enable}
set UDS-license-expiring-warning {disable | enable}
set UDS-license-expiring-days <integer>
Examples
This example shows how to configure the user name, add three
email addresses for sending alerts to, and what type of emails
will contain which log messages, such as HA and antivirus.
config alertemail setting
set username ZXSEC US@ourcompany.com
set mail1 admin1@ourcompany.com
set mail2 admin2@ourcompany.com
set mail3 admin3@ourcompany.com
set filter-mode category
set HA-logs enable
set UDS-update-logs enable
set antivirus-logs enable
set webfilter-logs enable
set admin-login-logs enable
set violation-traffic-logs enable
end
Related topics
system alertemail
system dns
Antivirus
Overview
Use antivirus commands to configure antivirus scanning for
services, quarantine options, and to enable or disable grayware
and heuristic scanning.
This chapter contains the following sections:
filepattern
grayware
heuristic
quarantine
quarfilepattern
service
Filepattern
Use this command to add, edit or delete the file patterns used
for virus blocking and to set which protocols to check for files to
block.
If you need to add configuration via CLI that requires ? as part
of config, you need to input CTRL-V first. If you enter the
question mark (?) without first using CTRL-V, the question mark
has a different meaning in CLI: it will show available command
options in that section.
For example, if you enter ? without CTRL-V:
edit "*.xe
token line: Unmatched double quote.
If you enter ? with CTRL-V:
edit "*.xe?"
new entry '*.xe?' added
Syntax
config antivirus filepattern
edit <filepattern_list_integer>
set name <filepattern_list>
set comment <filepattern_list_comment>
config entries
edit <filepattern_string>
set action <allow | block | intercept>
set active {ftp http im imap mm1 mm3 mm4 mm7 nntp pop3 smtp}
set file-type {unknown | ignored | activemime | arj | aspack |
base64 | bat | binhex | bzip | bzip2 | cab | com | elf | exe | fsg |
genscript | gzip | hlp | hta | html | javascript | lzh | mime | msc |
msoffice | perlscript | petite | rar | shellscript | sis | tar | upx | uue |
vbs | zip} (US Carrier)
set filter-type {pattern | type} (US Carrier)
end
Related topics
antivirus heuristic
antivirus grayware
antivirus quarantine
antivirus quarfilepattern
antivirus service
Grayware
Use this command to enable or disable grayware scanning for
the specified category.
Grayware programs are unsolicited commercial software
programs that get installed on computers, often without the
user’s consent or knowledge. Grayware programs are generally
considered an annoyance, but these programs can cause system
performance problems or be used for malicious purposes.
The ZXSEC US unit scans for known grayware executable
programs in each category enabled. The category list and
contents are added or updated whenever the ZXSEC US unit
receives a virus update package. New categories may be added
at any time and are loaded with virus updates. By default, all
new categories are disabled.
Adware Adware is usually embedded in freeware programs
and causes ads to pop up whenever the program
is opened or used.
BHO BHOs (Browser Helper Objects) are DLL files that
are often installed as part of a software package
so the software can control the behavior of
Internet Explorer 4.x and higher. Not all BHOs are
malicious, but the potential exists to track surfing
habits and gather other information.
Dial Dialers allow others to use the PC modem to call
premium numbers or make long distance calls.
Note:
The ZXSEC US CLI is case sensitive and the first letter of all
grayware category names is uppercase.
Example
This example shows how to enable grayware scanning for
Adware programs.
config antivirus grayware Adware
set status enable
end
Related topics
antivirus filepattern
antivirus heuristic
antivirus quarantine
antivirus quarfilepattern
antivirus service
system autoupdate schedule
execute update-av
Heuristic
Use this command to configure heuristic scanning for viruses in
binary files.
Syntax
config antivirus heuristic
set mode {pass | block | disable}
end
Example
This example shows how to disable heuristic scanning.
config antivirus heuristic
set mode disable
end
Related topics
antivirus filepattern
antivirus quarantine
antivirus quarfilepattern
antivirus servic
Quarantine
Use this command to set file quarantine options.
ZXSEC US units with a local disk can quarantine blocked and
infected files. The quarantined files are removed from the
content stream and stored on the ZXSEC US local disk. Users
receive a message informing them that the removed files have
been quarantined.
ZXSEC US units that do not have a local disk can quarantine
blocked and infected files to a Usla unit.
View the file names and status information about the file in the
quarantined file list. Submit specific files and add file patterns to
the autoupload list so they are automatically uploaded to USnet
for analysis.
Syntax
config antivirus quarantine
set agelimit <hours_integer>
set drop-blocked {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set drop-heuristic {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set drop-infected {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set drop-intercepted {ftp http imap mm1 mm3 mm4 mm7 pop3
smtp} (US Carrier)
set lowspace {drop-new | ovrw-old}
set maxfilesize <MB_integer>
set quar-to-Usla {enable | disable}
set store-blocked {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set store-heuristic {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set store-infected {ftp http im imap mm1 mm3 mm4 mm7 nntp
pop3 smtp}
set store-intercepted {ftp http imap mm1 mm3 mm4 mm7 pop3
smtp} (US Carrier)
end
Example
This example shows how to set the quarantine age limit to 100
hours, not quarantine blocked files from SMTP and POP3 traffic,
not quarantine heuristic tagged files from SMTP and POP3 traffic,
set the quarantine to drop new files if the memory is full, set the
maximum file size to quarantine at 2 MB, quarantine files from
IMAP traffic with blocked status, quarantine files with heuristic
status in IMAP, HTTP, and FTP traffic.
config antivirus quarantine
set agelimit 100
set drop-blocked smtp pop3
set drop-heuristic smtp pop3
set lowspace drop-new
set maxfilesize 2
set store-blocked imap
set store-heuristic imap http ftp
end
Related topics
antivirus filepattern
antivirus heuristic
antivirus quarfilepattern
antivirus service
Quarfilepattern
Use this command to configure the file patterns used by
automatic file uploading. This command is only available on
ZXSEC US units with a hard drive.
Configure the ZXSEC US unit to upload suspicious files
automatically to USnet for analysis. Add file patterns to be
uploaded to the autoupload list using the * wildcard character.
File patterns are applied for autoupload regardless of file
blocking settings.
Also upload files to USnet based on status (blocked or heuristics)
or submit individual files directly from the quarantined files list.
For more information, see antivirus quarantine.
Syntax
config antivirus quarfilepattern
edit pattern_str
set status {enable | disable}
end
Example
Use the following commands to enable automatic upload of *.bat
files.
config antivirus quarfilepattern
edit *.bat
set status enable
end
Related topics
antivirus filepattern
antivirus heuristic
antivirus quarantine
antivirus service
Service
Use this command to configure how the ZXSEC US unit handles
antivirus scanning of large files in HTTP, HTTPS, FTP, POP3,
IMAP, and SMTP traffic and what ports the ZXSEC US unit scans
for these services.
For HTTPS, you can only configure the ports.
Syntax
config antivirus service <service_str>
set port <port_integer>
set scan-bzip2 {enable | disable}
set uncompnestlimit <depth_integer>
set uncompsizelimit <MB_integer>
end
Note:
If the file in uncompnestlimit has more levels than the limit you
set, or if the file in uncompsizelimit is larger than the limit you
set, the file will pass through without being virus scanned.
Firewall
Overview
Use firewall commands to configure firewall policies and the data
they use, including protection profiles, IP addresses and virtual
IP addresses, schedules, and services. You can also configure
DNS translation, IP/MAC binding, and multicast policies.
This chapter contains the following sections:
address, address6
addrgrp, addrgrp6
dnstranslation
gtp (US Carrier)
ipmacbinding setting
ipmacbinding table
ippool
ldb-monitor
multicast-policy
policy, policy6
profile
schedule onetime
schedule recurring
service custom
service group
vip
vipgrp
Address, Address6
Use this command to configure firewall addresses used in
firewall policies. An IPv4 firewall address is a set of one or more
IP addresses, represented as a domain name, an IP address and
a subnet mask, or an IP address range. An IPv6 firewall address
is an IPv6 6-to-4 address prefix.
By default, ZXSEC US units have the firewall address All, which
represents any IP address. Addresses, address groups, and
virtual IPs must have unique names to avoid confusion in
firewall policies. If an address is selected in a policy, it cannot be
deleted until it is deselected from the policy.
Syntax
config firewall address
edit <name_str>
set associated-interface <interface_str>
set end-ip <address_ipv4>
set fqdn <domainname_str> set start-ip <address_ipv4>
set subnet <address_ipv4mask>
set type {ipmask | iprange | fqdn}
end
config firewall address6
edit <name_str>
set ip6 <address_ipv6prefix>
end
Example
This example shows how to add one IPv4 address of each type:
ipmask, iprange, and fqdn. It also shows how to configure an
IPv6 address prefix.
config firewall address
edit Example_Subnet
set type ipmask
set subnet 192.168.1.0 255.255.255.0
next
edit Example_Range set type iprange
Addrgrp, Addrgrp6
Use this command to configure firewall address groups used in
firewall policies.
You can organize related firewall addresses into firewall address
groups to simplify firewall policy configuration. For example,
rather than creating three separate firewall policies for three
firewall addresses, you could create a firewall address group
consisting of the three firewall addresses, then create one
firewall policy using that firewall address group.
Addresses, address groups, and virtual IPs must all have unique
names to avoid confusion in firewall policies. If an address group
is selected in a policy, it cannot be deleted unless it is first
deselected in the policy.
Syntax
config firewall addrgrp, addrgrp6
edit <name_str>
set member <name_str>
end
T AB L E 1 6 AD D R G R P , AD D R G R P 6 S E T T I NG
Example
This example shows how to add two firewall addresses to a
firewall address group.
config firewall addrgrp
edit Group1
set Example_Subnet Example_Range
end
Related topics
firewall address, address6
firewall policy, policy6
Dnstranslation
Use this command to add, edit or delete a DNS translation entry.
If DNS translation is configured, the ZXSEC US unit rewrites the
payload of outbound DNS query replies from internal DNS
servers, replacing the resolved names’ internal network IP
addresses with external network IP address equivalents, such as
a virtual IP address on a ZXSEC US unit’s external network
interface. This allows external network hosts to use an internal
network DNS server for domain name resolution of hosts located
on the internal network.
For example, if a virtual IP provided network address translation
(NAT) between a public network, such as the Internet, and a
private network containing a web server, hosts on the public
network could access the web server by using its virtual IP
address. However, if hosts attempted to access the web server
by domain name, and the DNS server performing name
resolution for that domain name was also located on the private
network, the DNS query reply would contain a private network
IP address, which is not routable from the external network. To
solve this, you might configure DNS translation, and substitute
the web server’s private network IP address with the virtual IP
address in DNS query replies to the public network.
DNS translation mappings between src and dst must be one-to-
one; you cannot create one-to-many or many-to-one mappings.
For example, if src is a single IP address, it cannot be DNS
Example
This example shows how to translate the resolved addresses in
DNS query replies, from an internal (source) subnet to an
external (destination) subnet.
config firewall dnstranslation
edit 1
set src 192.168.100.12
set dst 172.16.200.190
set netmask 255.255.255.0
end
Related topics
firewall vip
ip-policy
The following commands are the options for config ip-policy.
<index_int> Enter the unique ID number No default.
of the encapsulated IP traffic
filtering policy.
action {allow | Select to allow or deny allow
deny} traffic matching both the
source and destination
addresses specified for this
APN filter profile
dstaddr Enter the name of a No default.
<address_str> destination address or
address group.
srcaddr Enter the name of a source No default.
<address_str> address or address group.
noip-policy
The following commands are the options for config noip-policy.
<index_int> Enter the unique ID number No default.
of the encapsulated non-IP
traffic filtering policy.
Related topics
firewall vip
IP Macbinding Setting
Use this command to configure IP to MAC address binding
settings.
IP/MAC binding protects the ZXSEC US unit and/or the network
from IP address spoofing attacks. IP spoofing attacks attempt to
use the IP address of a trusted computer to connect to, or
through, the ZXSEC US unit from a different computer. It is
simple to change a computer’s IP address to mimic that of a
trusted host, but MAC addresses are often added to Ethernet
cards at the factory, and are more difficult to change. By
Note:
If IP/MAC binding is enabled, and the IP address of a host with
an IP or MAC address in the IP/MAC table is changed, or a new
computer is added to the network, update the IP/MAC table. If
you do not update the IP/MAC binding list, the new or changed
hosts will not have access to or through the ZXSEC US unit. For
details on updating the IP/MAC binding table, see “ipmacbinding
table”.
Caution:
If a client receives an IP address from the ZXSEC US unit’s DHCP
server, the client’s MAC address is automatically registered in
the IP/MAC binding table. This can simplify IP/MAC binding
configuration, but can also neutralize protection offered by
IP/MAC binding if untrusted hosts are allowed to access the
DHCP server. Use caution when enabling and providing access to
the DHCP server.
Syntax
config firewall ipmacbinding setting
set bindthroughfw {enable | disable}
set bindtofw {enable | disable}
set undefinedhost {allow | block}
end
Example
This example shows how to enable IP/MAC binding for traffic
both going to and through the ZXSEC US unit, and block
undefined hosts (IP/MAC address pairs).
config firewall ipmacbinding setting
set bindthroughfw enable
set bindtofw enable
set undefinedhost block
end
Related topics
firewall ipmacbinding table
IP Macbinding Table
Use this command to configure IP and MAC address pairs in the
IP/MAC binding table. You can bind multiple IP addresses to the
same MAC address, but you cannot bind multiple MAC addresses
to the same IP address.
To configure the IP/MAC binding settings, see “ipmacbinding
setting”. To enable or disable IP/MAC binding for an individual
ZXSEC US unit network interface, see ipmac in “system
interface”.
Note:
If IP/MAC binding is enabled, and the IP address of a host with
an IP or MAC address in the IP/MAC table is changed, or a new
computer is added to the network, update the IP/MAC table. If
you do not update the IP/MAC binding list, the new or changed
hosts will not have access to or through the ZXSEC US unit.
Caution:
If a client receives an IP address from the ZXSEC US unit’s DHCP
server, the client’s MAC address is automatically registered in
the IP/MAC binding table. This can simplify IP/MAC binding
configuration, but can also neutralize protection offered by
IP/MAC binding if untrusted hosts are allowed to access the
DHCP server. Use caution when enabling and providing access to
the DHCP server.
Syntax
config firewall ipmacbinding table
edit <index_int>
set ip <address_ipv4>
set mac <address_hex>
set name <name_str>
set status {enable | disable}
end
Example
This example shows how to add and enable an IP/MAC entry to
the IP/MAC binding table.
config firewall ipmacbinding table
edit 1
set ip 172.16.44.55
set mac 00:10:F3:04:7A:4C
set name RemoteAdmin
set status enable
end
Related topics
firewall ipmacbinding setting
IP Pool
Use this command to configure IP address pools that you can
use to configure NAT mode firewall policies. An IP pool, also
called a dynamic IP pool, is a range of IP addresses added to a
firewall interface. You can enable Dynamic IP Pool in a firewall
policy to translate the source address to an address randomly
selected from the IP pool. To use IP pools, the IP pool interface
must be the same as the firewall policy destination interface.
Add an IP pool if in order to add NAT mode policies that
translate source addresses to addresses randomly selected from
the IP pool rather than being limited to the IP address of the
destination interface. IP pools are only available in NAT/Route
mode. Add multiple IP pools to any interface and configure the
firewall policy to select the IP pool to use for that firewall policy.
Syntax
config firewall ippool
edit <index_int>
set endip <address_ipv4>
set interface <name_str>
set startip <address_ipv4>
end
Example
You might use the following commands to add an IP pool to the
internal network interface. The IP pool would then be available
when configuring firewall policies.
config firewall ippool
edit 1
set startip 192.168.1.100
set endip 192.168.1.200
set interface internal
end
Related topics
firewall policy, policy6
LDB-Monitor
Use this command to configure health check settings.
Health check settings can be used by load balancing VIPs to
determine if a real server is currently responsive before
forwarding traffic. One health check is sent per interval using the
specified protocol, port and HTTP-GET, where applicable to the
protocol. If the server does not respond during the timeout
Example
You might configure a health check for a server using the HTTP
protocol to retrieve a web page. To ensure that a web page reply
containing an error message, such as an HTTP 404 page, does
not inadvertently cause the health check to succeed, you might
search the reply for text that does not occur in any web server
error page, such as unique text on a main page.
config firewall ldp-monitor
edit httphealthchecksettings
set type http set port 8080
set http-get “/index.php”
set http-match “Welcome to Example, Inc.”
set interval 5 set timeout 2 set retry 2
end
Related topics
firewall vip
Multicast-Policy
Use this command to configure a source NAT IP. This command
can also be used in Transparent mode to enable multicast
forwarding by adding a multicast policy.
The matched forwarded (outgoing) IP multicast source IP
address is translated to the configured IP address. For additional
Example
This example shows how to configure a multicast NAT policy.
config firewall multicast-policy edit 1
set dstaddr 10.0.0.1 255.255.255.0
set dstintf dmz
set nat 10.0.1.1
set srcaddr 192.168.100.12 255.255.255.0
set srcintf internal
end
Related topics
system global
Policy, Policy6
Use this command to add, edit, or delete firewall policies.
Firewall policies control all traffic passing through the ZXSEC US
unit. Firewall policies are instructions used by the ZXSEC US unit
to decide what to do with a connection request. The policy
directs the firewall to allow the connection, deny the connection,
require authentication before the connection is allowed, or apply
IPSec or SSL VPN processing.
Note:
If you are creating an IPv6 policy, some of the IPv4 options,
such as NAT and VPN settings, are not applicable.
Syntax
config firewall policy, policy6
edit <index_int>
set action {accept | deny | ipsec | ssl-vpn}
set auth-cert <certificate_str>
set auth-path {enable | disable}
set auth-redirect-addr <domainname_str>
set comments <comment_str>
set custom-log-fields <fieldid_int>
set diffserv-forward {enable | disable}
set diffserv-reverse {enable | disable}
set diffservcode-forward <dscp_bin>
set diffservcode-rev <dscp_bin>
set disclaimer {enable | disable}
set dstaddr <name_str>
set dstintf <name_str>
set fixedport {enable | disable}
set USDesktop-check {enable | disable}
set USDesktop-ra-notinstalled {enable | disable}
set USDesktop-ra-notlicensed {enable | disable}
set USDesktop-ra-db-outdated {enable | disable}
set USDesktop-ra-no-av {enable | disable}
set USDesktop-ra-no-fw {enable | disable}
set USDesktop-ra-no-wf {enable | disable}
set USDesktop-redir-portal {enable | disable}
set fsae {enable | disable}
set fsae-guest-profile <profile_str>
set gbandwidth <limit_int>
set groups <name_str>
set gtp_profile <name_str> (US Carrier)
set inbound {enable | disable}
set ippool {enable | disable}
set logtraffic {enable | disable}
set maxbandwidth <limit_int>
set nat {enable | disable}
set natinbound {enable | disable}
set natip <address_ipv4mask>
set natoutbound {enable | disable}
Note:
You can add the firewall policy from the web-based manager and
then use the CLI to enable NAT and add the IP Pool.
Related topics
firewall address, address6
firewall profile
firewall schedule onetime
firewall schedule recurring
firewall service custom
firewall service group
Profile
Use this command to configure protection profiles which can be
applied to traffic by selecting the protection profile in one or
more firewall policies, or by associating a protection profile with
a firewall user group. The firewall policy will apply the subset of
the protection profile that is relevant to the service or service
group.
Syntax
config firewall profile
edit <profile_str>
set aim {enable-inspect | } {archive-full archive-summary block-
audio block-encrypt block-file block-im block-long-chat block-
photo inspect-anyport no-content-summary}
set bittorrent {block | pass | limit}
set bittorrent-limit <limit_int>
set comment <comment_str>
end
config sip
set status {enable | disable}
set ack-rate <rate_int>
set archive-summary {enable | disable}
set block-ack {enable | disable}
set block-bye {enable | disable}
set block-cancel {enable | disable}
set block-info {enable | disable}
set block-invite {enable | disable}
set block-long-lines {enable | disable}
set block-notify {enable | disable}
set block-options {enable | disable}
set block-prack {enable | disable}
set block-publish {enable | disable}
set block-refer {enable | disable}
set block-register {enable | disable}
set block-subscribe {enable | disable}
set block-unknown {enable | disable}
set block-update {enable | disable}
set call-keepalive <limit_int>
set info-rate <rate_int>
set invite-rate <limit_int>
set max-dialogs <limit_int>
set max-line-length <limit_int>
set nat-trace {enable | disable}
set no-sdp-fixup {enable | disable}
set notify-rate <limit_int>
set options-rate <limit_int>
set prack-rate <limit_int>
set preserve-override {enable | disable}
set primary-secondary {enable | disable}
set refer-rate <limit_int>
set register-rate <limit_int>
set rtp {enable | disable}
set strict-register {enable | disable}
set subscribe-rate <limit_int>
set timeout-buffer <calls_int>
rate-server-ip: Send
both the URL and the IP
address of the requested
site for checking,
providing additional
security against
attempts to bypass the
Usservice system.
redir-block: Block HTTP
redirects. Many web
sites use HTTP redirects
legitimately; however, in
some cases, redirects
may be designed
specifically to
circumvent web filtering,
as the initial web page
could have a different
rating than the
destination web page of
the redirect.
strict-blocking: Block
any web pages if any
classification or category
matches the rating. This
option does not apply to
HTTPS.
To remove an option from
the list or add an option to
the list, retype the list with
the option removed or
added. These options take
effect only if Usservice web
filtering is enabled for the
protocol.
ussrv-wf-ovrd Enter all, or enter one or No default.
no-content-summary:
Omit content
information from the
dashboard.nto email,
FTP, and HTTP
categories.
oversize: Block files that
are over the file size
limit.
quarantine: Quarantine
files that contain
viruses. This feature is
available for ZXSEC US
units that contain a hard
disk or a connection to a
Usla unit.
scan: Scan files for
viruses and worms.
spam-mail-log: Include
spam in the email log.
spamemailbwl: Block
email containing
addresses in the email
address list.
spamfschksum: Use
Usservice Antispam
email message
checksum spam
checking.
spamfsip: Use the
Usservice Antispam IP
address blacklist.
spamfssubmit: Add a
link to the message
body to allow users to
report messages
incorrectly marked as
spam. If an email
message is not spam,
click the link in the
message to inform
Usservice of the false
positive.
spamfsurl: Use the
Usservice Antispam URL
blacklist.
spamhdrcheck: Filter
email using the MIME
header list.
spamipbwl: Filter email
using the email IP
dupe
The following commands are the options for config dupe.
(US Carrier)
{mm1 | mm4} Select to configure detection No default.
of excessive MMS message
duplicates for the MM1 or
MM4 interface.
status {enable | Select to detect and act disable
disable} upon duplicate MMS
messages.
(US Carrier)
action {archive block Select which actions to take, archive block
intercept log} if any, when excessive intercept log
(US Carrier) duplicate messages are
detected. To select more
than one action, separate
each action with a space.
archive: Content
archive excessive
duplicates.
block: Block and
intercept excess
duplicates. If block is
selected, messages
are also intercepted,
even if intercept is
not selected.
intercept: Intercept
Example
This example shows how to create a profile called spammail,
using:
filtering of email according to the email banned word list, the
MIME header list, and the return DNS check, enable spam to
be logged and tagged with the tag “Spam” in the subject for
POP3 traffic
filtering of email based on the DNSBL server, and discard
messages identified as spam for SMTP traffic
config firewall profile
edit spammail
set pop3 spamemailbwl spamhdrcheck spamraddrdns
set pop3-spamaction log tag
set pop3-spamtagmsg Spam
set pop3-spamtagtype subject set smtp spamrbl
set smtp-spamaction discard
end
This example shows how to add HTTP category blocking to the
spammail profile created above, using:
category blocking to deny access to web pages categorized
as Games (20), Personals and Dating (37), Shopping and
Auction (42) and the category group Objectionable or
Controversial (g02)
category monitoring to log access to web pages categorized
as Computer Security (50) and the category group
Potentially Bandwidth Consuming (g04)
config firewall profile
edit spammail
set ussrv-wf-deny 20 37 42 g02
set ussrv-wf-log 50 g04
end
Related topics
firewall policy, policy6
alertemail
antivirus
ips
webfilter
Schedule Onetime
Use this command to add, edit, or delete one-time schedules.
Use scheduling to control when policies are active or inactive.
Use one-time schedules for policies that are effective once for
the period of time specified in the schedule.
Note:
To edit a schedule, define the entire schedule, including the
changes. This means entering all of the schedule parameters,
both those that are changing and those that are not.
Syntax
config firewall schedule onetime
edit <name_str>
set end <hh:mm> <yyyy/mm/dd>
set start <hh:mm> <yyyy/mm/dd>
end
Example
Use the following example to add a one-time schedule named
Holiday that is valid from 5:00 pm on 3 September 2004 until
8:45 am on 7 September 2004.
config firewall schedule onetime
edit Holiday
set start 17:00 2004/09/03
set end 08:45 2004/09/07
end
Related topics
firewall policy, policy6
firewall schedule recurring
Schedule Recurring
Use this command to add, edit, and delete recurring schedules
used in firewall policies.
Use scheduling to control when policies are active or inactive.
Use recurring schedules to create policies that repeat weekly.
Use recurring schedules to create policies that are effective only
at specified times of the day or on specified days of the week.
Note:
If a recurring schedule is created with a stop time that occurs
before the start time, the schedule starts at the start time and
finishes at the stop time on the next day. You can use this
technique to create recurring schedules that run from one day to
the next. To create a recurring schedule that runs for 24 hours,
set the start and stop times to the same time.
Syntax
config firewall schedule recurring
edit <name_str>
set day <name_str>
set end <hh:mm>
set start <hh:mm>
end
Service Custom
Use this command to configure a firewall service that is not in
the predefined service list.
Note:
To display a list of all predefined service names, enter the
command get firewall service predefined ?. To display a
predefined service’s details, enter the command get firewall
service predefined <service_str>. For details, see “get firewall
service predefined”.
Syntax
config firewall service custom
edit <name_str>
set icmpcode <code_int>
set icmptype <type_int>
Example
This example shows how to add a custom service called
Custom_1. The service destination port range is TCP 4501 to
4503. The service can use any source port.
config firewall service custom
edit Custom_1
set protocol TCP/UDP
set tcp-portrange 4501-4503
end
A second example shows how to add a custom service called
Custom_2. The service destination port range is TCP 4545 to
4550. The service uses source port 9620.
config firewall service custom
edit Custom_1
set protocol TCP/UDP
set tcp-portrange 4545-4550:9620
end
Related topics
firewall policy, policy6
Service Group
Use this command to configure firewall service groups.
To simplify policy creation, you can create groups of services
and then add one policy to provide or block access for all the
services in the group. A service group can contain predefined
services and custom services in any combination. A service
group cannot contain another service group.
Note:
To edit a service group, enter all of the members of the service
group, both those changing and those staying the same.
Syntax
config firewall service group
edit <name_str>
set member <name_str>
end
Example
This example shows how to add a service group called
web_Services that includes the FTP, HTTP, HTTPS, and Real
Audio services.
config firewall service group
edit web_Services
set member FTP HTTP HTTPS RAUDIO
end
This example shows how to add the TELNET service to the
web_Services service group.
config firewall service group
edit web_Services
set member FTP HTTP HTTPS RAUDIO TELNET
end
Related topics
firewall policy, policy6
VIP
Use this command to configure virtual IPs and their associated
address and port mappings (NAT). Virtual IPs can be used to
allow connections through a ZXSEC US unit using network
address translation (NAT) firewall policies. Virtual IPs can use
proxy ARP so that the ZXSEC US unit can respond
to ARP requests on a network for a server that is actually
installed on another network. Proxy ARP is defined in RFC 1027.
For example, you can add a virtual IP to an external ZXSEC US
unit interface so that the external interface can respond to
connection requests for users who are actually connecting to a
server on the DMZ or internal network.
Note:
Virtual IPs are not available in Transparent mode.
Depending on your configuration of the virtual IP, its mapping
may involve port address translation (PAT), also known as port
forwarding or network address port translation (NAPT), and/or
network address translation (NAT) of IP addresses.
If you configure NAT in the virtual IP and firewall policy, the NAT
behavior varies by your selection of:
static vs. dynamic NAT mapping
the dynamic NAT’s load balancing style, if using dynamic NAT
mapping
full NAT vs. destination NAT (DNAT)
The following table describes combinations of PAT and/or NAT
that are possible when configuring a firewall policy with a virtual
IP.
Static NAT Static, one-to-one NAT mapping: an
external IP address is always translated to
the same mapped IP address.
If using IP address ranges, the external IP
address range corresponds to a mapped IP
address range containing an equal number
of IP addresses, and each IP address in the
external range is always translated to the
same IP address in the mapped range.
Static NAT with Port Forwarding
Static, one-to-one NAT mapping with port
forwarding: an external IP address is
always translated to the same mapped IP
address, and an external port number is
always translated to the same mapped port
number.
Note:
If the NAT check box is not selected when building the firewall
policy, the resulting policy does not perform full (source and
destination) NAT; instead, it performs destination network
address translation (DNAT).
For inbound traffic, DNAT translates packets’ destination address
to the mapped private IP address, but does not translate the
source address. The private network is aware of the source’s
public IP address.
For reply traffic, the ZXSEC US unit translates packets’ private
network source IP address to match the destination address of
the originating packets, which is maintained in the session table.
Virtual IPs have the following requirements.
The Mapped IP Address/Range cannot be 0.0.0.0 or
255.255.255.255.
The Mapped IP Address/Range must not include any
interface IP addresses.
If the virtual IP is mapped to a range of IP addresses and its
type is Static NAT, the External IP Address/Range cannot be
0.0.0.0.
When port forwarding, the External IP Address/Range cannot
include any interface IP addresses.
When port forwarding, the count of mapped port numbers
and external port numbers must be the same, and the last
port number in the range must not exceed 65535.
Example
This example shows how to add a static NAT virtual IP named
Web_Server that allows users on the Internet to connect to a
single web server on the private network. The public IP address
of the web server is 64.32.21.34 and the IP address of the web
server on the internal network is 192.168.1.44.
config firewall vip
edit Web_Server
set extintf external
set extip 64.32.21.34
set mappedip 192.168.1.44
end
This example shows how to edit the static NAT virtual IP named
Web_Server to change the IP address of the web server on the
internal network to 192.168.110.23.
config firewall vip
edit web_Server
set mappedip 192.168.110.23
end
This example shows how to add a static NAT port forwarding
virtual IP that uses port address translation to allow external
access to a web server on the private network if there is no
separate external IP address for the web server. In this example,
the IP address of the external interface is 192.168.100.99 and
the real IP address of the web server on the internal network is
192.168.1.93.
config firewall vip
edit web_Server
set portforward enable set extintf external
set extip 192.168.100.99
set extport 80
set mappedip 192.168.1.93
set mappedport 80
end
This example shows how to enter a static NAT virtual IP named
Server_Range that allows Internet users to connect to a range of
10 virtual IP addresses on the Internet and have the IP
addresses in this range mapped to a range of IP addresses on
the DMZ network. The DMZ network contains 10 servers with IP
addresses from 10.10.10.20 to 10.10.10.29. The Internet IP
addresses for these servers are in the range 219.34.56.10 to
219.34.56.19. In this example you do not have to enter the
external IP address range. Instead you enter the first IP address
in the external IP address range and the
ZXSEC US unit calculates the end of the IP address range based
on the number of IP addresses defined by the mapped IP
address range. Also in the example, port2 is connected to the
Internet.
config firewall vip
edit Server_Range
set extintf port2
set extip 219.34.56.10
set mappedip 10.10.10.20 10.10.10.19
end
This example shows how to enter a load balancing virtual IP
named Ext_Load_Balance that allows Internet users to connect
VIP GRP
You can create virtual IP groups to facilitate firewall policy traffic
control. For example, on the DMZ interface, if you have two
email servers that use Virtual IP mapping, you can put these two
VIPs into one VIP group and create one external-to-DMZ policy,
instead of two policies, to control the traffic.
Firewall policies using VIP Groups are matched by comparing
both the member VIP IP address(es) and port number(s).
Syntax
config firewall vipgrp
edit <name_str>
set interface <name_str>
set member <virtualip_str>
end
Example
config firewall vipgrp
edit group_one
set interface internal
set member vipone viptwo vipthree
end
Related topics
firewall policy, policy6
vip
GUI
Overview
This chapter covers the commands to restore web-based
manager CLI console and topology viewer. This chapter contains
the following sections:
Console
Topology
Console
Use this command to configure the web-based manager CLI
console.
Syntax
config gui console
set preferences <filedata>
end
To obtain base-64 encoded data from a configured CLI console,
use:
show gui console
Example
Topology
Use this command to configure the web-based manager
topology viewer.
Syntax
config gui topology
set background-image <filedatabackground>
set database <filedatabase>
set preferences <filedatapref>
end
To obtain base-64 encoded data from a configured topology
viewer, use:
show gui topology
Example
This example shows how to upload the data file (topguifile)
containing commands to set up the topology GUI on the ZXSEC
US unit and the background image (backgroundfile).
config gui topology
set preferences topguifile
set background-image backgroundfile
end
IMP2P
Overview
Use imp2p commands to configure user access to Instant
Messaging and Person-to-Person applications, and to configure a
global policy for unknown users who might use these
applications.
This chapter contains the following sections:
aim-user
icq-user
msn-user
old-version
policy
yahoo-user
AIM-user
Use this command to permit or deny a specific user the use of
AOL Instant Messenger.
Syntax
config imp2p aim-user
edit <name_str>
set action {permit | deny}
end
T A B L E 3 4 AI M - U S E R S E T T I N G
Example
This example shows how to add user_1 and permit the user to
use the AIM protocol if the policy is set to allow AOL Instant
Messenger.
config imp2p aim-user
edit user_1
set action permit
end
Related topics
imp2p icq-user
imp2p msn-user
imp2p old-version
imp2p policy
imp2p yahoo-user
ICQ-user
Use this command to permit or deny a specific user the use of
ICQ Instant Messenger.
Syntax
config imp2p icq-user
edit <name_str>
set action {permit | deny}
end
Example
This example shows how to add user_1 and permit the user to
use the ICQ protocol if the policy is set to allow ICQ Instant
Messenger.
config imp2p icq-user
edit user_1
set action permit
end
Related topics
imp2p aim-user
imp2p msn-user
imp2p old-version
imp2p policy
imp2p yahoo-user
MSN-user
Use this command to permit or deny a specific user the use of
MSN Messenger.
Syntax
config imp2p msn-user
edit <name_str>
set action {permit | deny}
end
Example
This example shows how to add user_1 and permit the user to
use the MSN protocol if the policy is set to allow MSN Messenger.
config imp2p msn-user
edit user_1
set action permit
end
Related topics
imp2p aim-user
imp2p icq-user
imp2p old-version
imp2p policy
imp2p yahoo-user
Old-version
Some older versions of IM protocols are able to bypass file
blocking because the message types are not recognized. The
following command provides the option to disable these older IM
protocol versions. Supported IM protocols include:
MSN 6.0 and above
ICQ 4.0 and above
AIM 5.0 and above
Yahoo 6.0 and above
Syntax
config imp2p old-version
set aim {block | best-effort}
set icq {block | best-effort}
set msn {block | best-effort}
set yahoo {block | best-effort}
end
Example
This example shows how to block older versions of MSN
Messenger and inspect older versions of Yahoo Messenger.
Policy
Use this command to create a global policy for instant
messenger applications. If an unknown user attempts to use one
of the applications, the user can either be permitted use and
added to a white list, or be denied use and added to a black list.
Syntax
config imp2p policy
set aim {allow | deny}
set icq {allow | deny}
set msn {allow | deny}
set yahoo {allow | deny}
end
Example
This example shows how to configure the IM/P2P policy to allow
AOL Instant Messenger, MSN Messenger, and Yahoo Messenger
but deny ICQ Instant Messenger.
config imp2p policy
set aim allow
set msn allow set icq deny
set yahoo allow
end
Related topics
imp2p aim-user
imp2p icq-user
imp2p msn-user
imp2p old-version
imp2p yahoo-user
Yahoo-user
Use this command to permit or deny a specific user the use of
Yahoo Messenger.
Syntax
config imp2p yahoo-user
edit <name_str>
set action {permit | deny}
end
Example
This example shows how to add user_1 and permit the user to
use the Yahoo protocol if the policy is set to allow Yahoo
Messenger.
config imp2p yahoo-user
edit user_1
set action permit
end
Related topics
imp2p aim-user
imp2p icq-user
imp2p msn-user
imp2p old-version
imp2p policy
IPS
Overview
Use ips commands to configure IPS sensors to define which
signatures are used to examine traffic and what actions are
taken when matches are discovered. DoS sensors can also be
defined to examine traffic for anomalies
This chapter contains the following sections:
DoS
Custom
Decoder
Global
Rule
Sensor
Note:
If the IPS test can’t find the destination MAC address, the peer
interface will be used. To ensure packets get IPS inspection,
there must be a Peer Interface. Both interfaces must be in the
same VDOM, and one interface cannot be both the peer and
original interface. For information on how to set the Peer
Interface see “interface”.
DoS
ZXSEC US Intrusion Protection uses Denial of Service (DoS)
sensors to identify network traffic anomalies that do not fit
known or preset traffic patterns. Four statistical anomaly types
for the TCP, UDP, and ICMP protocols can be identified.
Note:
It is important to estimate the normal and expected traffic on
the network before changing the default anomaly thresholds.
Setting the thresholds too low could cause false positives, and
setting the thresholds too high could allow some attacks.
The list of anomalies can be updated only when the ZXSEC US
firmware image is upgraded.
Config Limit
Access the config limit subcommand using the config ips
anomaly <name_str> command.
Use this command for session control based on source and
destination network address. This command is available for
tcp_src_session, tcp_dst_session, icmp_src_session,
icmp_dst_session, udp_src_session, udp_dst_session.
The default entry cannot be edited. Addresses are matched from
more specific to more general. For example, if thresholds are
defined for 192.168.100.0/24 and 192.168.0.0/16, the address
with the 24 bit netmask is matched before the entry with the 16
bit netmask.
Syntax
config ips DoS
edit <sensor_int>
config address
edit <address_int>
set dst-ip <dst_ipv4mask>
set dst-port <dstport_int>
set src-ip <src_ipv4mask>
end
config anomaly
edit <anomaly_str>
set status {enable | disable}
set log {enable | disable}
set action {block | pass}
set threshold <threshold_int>
end
set comment <comment_str>
set name <name_str>
set status {disable | enable}
end
Examples
This example shows how to create a DoS sensor, name it, and
enable blocking of the udp_flood anomaly with the default
threshold.
config ips DoS
edit 12
set name test
set comment "This is for test"
config anomaly
edit udp_flood
set action block
set status enable
end
end
Related topics
ips custom
ips global
ips fail-open {enable | disable}
Custom
Create custom IPS signatures and add them to IPS sensors.
Custom signatures provide the power and flexibility to customize
ZXSEC US Intrusion Protection for diverse network environments.
The ZXSEC US predefined signatures cover common attacks. If
an unusual or specialized application or an uncommon platform
is being used, add custom signatures based on the security
alerts released by the application and platform vendors.
Use custom signatures to block or allow specific traffic.
The custom signature settings are configured when it is defined
as a signature override in an IPS sensor. This way, a single
custom signature can be used in multiple sensors with different
settings in each. See “ips sensor” for details.
For more information on custom signature syntax see the ZXSEC
US IPS Custom Signatures Technical Bulletin.
Note:
Custom signatures are an advanced feature. This document
assumes the user has previous experience writing intrusion
detection signatures.
Syntax
config ips custom
edit <sig_str>
set signature <signature_str>
end
Example
This example shows how to add a custom signature.
config ips custom
edit bad_things
set signature 'F-SBID (--protocol tcp; --flow bi_direction;
--pattern "nude cheerleader"; --no_case)'
end
Related topics
ips global
execute backup
execute restore
ips fail-open {enable | disable}
Decoder
The Intrusion Protection system looks for certain types of traffic
on specific ports. Using the decoders command, you can change
ports if your configuration uses non-standard ports.
Syntax
config ips decoder
edit <decoder_str>
set port_list <port_int>
end
Example
This example shows how to modify the dns_decoder to examine
ports 1, 2, and 3 instead of the default 53.
config ips decoder dns_decoder
set port_list "1,2,3"
end
Global
Use this command to ignore sessions after a set amount of
traffic has passed.
Syntax
config ips global
set anomaly-mode {continuous | periodical}
Example
This example shows how to set intrusion protection to ignore
sessions after 204800 bytes.
config ips global
set ignore-session-bytes 204800
end
This example shows how to see the current configuration of ips
global.
# get ips global
anomaly-mode: continuous
engine-count: 0
fail-open: enable
ignore-session-bytes:204800
session-limit-mode: heuristic
socket-size: 8 (MB)
traffic-submit: disable
Related topics
execute backup
execute restore
ips fail-open {enable | disable}
Rule
The IPS sensors use signatures to detect attacks. These
signatures can be listed with the rules command. Details about
the default settings of each signature can also be displayed.
Syntax
config ips rule <rule_str>
get
Example
Sensor
The IPS sensors use signatures to detect attacks. IPS sensors
are made up of filters and override rules. Each filter specifies a
number of signature attributes and all signatures matching all
the specified attributes are included in the filter. Override rules
allow you to override the settings of individual signatures.
Syntax
config ips sensor
edit <sensor_str>
config filter
edit <filter_str>
set location {all | client | server}
set severity {all | info low medium high critical}
set protocol <protocol_str>
set os {all | other windows linux bsd solaris macos}
set application <app_str>
set status {default | enable | disable}
set log {default | enable | disable}
set action {block | default | pass | reject}
end
config override
edit <override_int>
config exempt-ip
edit <exempt_int>
set dst-ip <dest_ipv4mask>
set src-ip <source_ipv4mask>
end
set action {block | pass | reset}
set log {disable | enable}
set log-packet {disable | enable}
set status {disable | enable}
end
set comment <comment_str>
end
Example
This example shows how to create an IPS sensor containing a
filter that includes all signatures to protect against Windows
server attacks.
config ips sensor
edit dept_srv
set comment "Department file servers"
LOG
Overview
Use the config log commands to set the logging type, the
logging severity level, and the logging location for the ZXSEC US
unit.
Note:
In Transparent mode, certain log settings and options may not
be available because certain features do not support logging or
are not available in this mode. For example, SSL VPN events are
not available in Transparent mode.
custom-field
{disk | Usla | memory | syslogd | webtrends | Usservice}
filter
disk setting
Usla setting
Usservice setting
memory setting
memory global setting syslogd setting
webtrends setting
trafficfilter
report customization
report definition
report filter
report output
report period
report schedule
report scope
report selection
report summary-layout
Custom-field
Use the following command to customize the log fields with a
name and/or value. The custom name and/or value will appear
in the log message.
Syntax
config log custom-field
edit id <integer>
set name <name>
set value <integer>
end
Example
This example shows how to configure a customized field for logs
for branch offices in a company and are associated with specific
firewall policies.
config log custom-field edit 1
set name company_branch1
set value 2
next edit 2
set name company_branch2
set value 4
next edit 3
set name company_branch3
set value 5
end
Related topics
{disk | Usla | memory | syslogd | webtrends | Usservice}
filter
Example
This example shows how to set the logging severity level to
warning, enable virus logging for infected files, and enable event
logging for anomaly and IPSec events.
config log disk filter
set severity warning set virus enable
set infected enable set event enable
set anomaly enable set ipsec enable
end
Related topics
log Usla setting
log memory setting
log syslogd setting
log webtrends setting
log trafficfilter
log report definition
firewall
Disk Setting
Use this command to configure log settings for logging to the
local disk. Disk logging is only available for ZXSEC US units with
an internal hard disk. You can also use this command to
configure the ZXSEC US unit to upload current log files to an FTP
server every time the log files are rolled.
If you have an AMC disk installed on your ZXSEC US unit, you
can use disk setting to configure logging of traffic to the AMC
disk. The AMC disk behaves as a local disk after being inserted
into the ZXSEC US unit and the ZXSEC US unit rebooted. You
can view logs from Log&Report > Log Access > Disk when
logging to an AMC disk.
Note:
AMC disk is supported on all ZXSEC US units that have single-
wide AMC slots.
Syntax
config log disk setting
set status {enable | disable}
set log full-first-warning threshold
set log full-second-warning threshold
set log full-final-warning threshold
set max-log-file-size <integer max>
set roll-schedule {daily | weekly}
set roll-time <hh:mm>
set diskfull {nolog | overwrite}
set upload {enable | disable}
set upload-destination {Usla | ftp-server}
set uploadip <class_ip>
set uploadport <port_integer>
set uploaduser <user_str>
set uploadpass <passwd>
set uploaddir <dir_name_str>
set uploadtype {attack event im spamfilter traffic virus voip
webfilter}
set uploadzip {disable | enable}
set uploadsched {disable | enable}
set uploadtime <time_integer>
set upload-delete-files {enable | disable}
set drive-standby-time <0-19800>
end
Example
This example shows how to enable logging to the local disk, set
the action to stop logging when the disk is full, log files have a
maximum size of 300MB, roll log files daily and start a new one
at 1:30pm every day.
config log disk setting
set status enable
set diskfull nolog
set max-log-file-size 300
set roll-schedule daily
set roll-time 01:30
end
This example shows how to enable uploading the traffic log and
content archive files to an FTP server. The FTP server has the IP
address 172.30.120.24, the user name is ftpone, the password
is ftppass1, and the directory on the FTP server is ZXSEC
US\login.
config log disk setting
set upload enable
set uploadip 172.30.120.24
set uploaduser ftpone
set uploadpass ftppass1
set uploadtype traffic content
set uploaddir ZXSEC US\logs
end
Related topics
Usla Setting
Use this command to configure the ZXSEC US unit to send log
files to a Usla unit. See “fips-cc” to set the Usla configuration
settings.
Usla units are network appliances that provide integrated log
collection, analysis tools and data storage. Detailed log reports
provide historical as well as current analysis of network and
email activity to help identify security issues and reduce network
misuse and abuse.
Using the CLI, you can send logs to up to three different Usla
units for maximum fail-over protection of log data. After
configuring logging to Usla units, the ZXSEC US unit will send
the same log packets to all configured Usla units. Additional Usla
units are configured using the Usla 2 and Usla 3 commands.
Use the multi-report command to enable configuring Usla
reports. By default, multi-report is disabled and only the default
Usla report is available.
Note:
The Usla CLI commands are not cumulative. Using a syntax
similar to the following is not valid:
config log Usla Usla2 Usla3 setting
Syntax
config log Usla setting
set status {disable | enable}
set multi-report {enable | disable}
set max-buffer-size
end
Example
This example shows how to enable logging to a Usla unit.
config log Usla setting
set status enable
end
Related topics
system fips-cc
log {disk | Usla | memory | syslogd | webtrends | Usservice}
filter
log Usla setting
log memory setting
log syslogd setting
log webtrends setting
log trafficfilter
log report definition
Usservice Setting
Use this command for configuring Usservice Analysis Service
settings. See the ZXSEC US Administration Guide for more
information about subscription-based Usservice Analysis and
Management Service, including enabling logging to a Usservice
Analysis server.
Note:
The Usservice setting command is only available when Usservice
Analysis and Management Service subscription-based services
are enabled. The storage space is a specified amount, and varies,
depending on the services requested.
Syntax
config log Usservice setting
set quotafull {nolog | overwrite}
set status {disable | enable}
end
Example
In this example, the ZXSEC US unit is logging to a Usservice
Analysis server, and will stop logging when the maximum
storage space on the server is reached.
config log Usservice setting
set quotafull nolog
set status enable
end
Related topics
{disk | Usla | memory | syslogd | webtrends | Usservice}
filter
Memory Setting
Use this command to configure log settings for logging to the
ZXSEC US system memory.
The ZXSEC US system memory has a limited capacity and only
displays the most recent log entries. Traffic logs are not stored
in the memory buffer, due to the high volume of traffic
information. After all available memory is used, by default, the
ZXSEC US unit begins to overwrite the oldest messages. All log
entries are deleted when the ZXSEC US unit restarts.
Syntax
config log memory setting
set diskfull <overwrite>
Example
This example shows how to enable logging to the ZXSEC US
system memory.
config log memory setting
set status enable
set diskfull overwrite
end
Related topics
log {disk | Usla | memory | syslogd | webtrends | Usservice}
filter
log Usla setting
log syslogd setting
log webtrends setting
log trafficfilter
log report definition
memory global setting
Example
This example shows how to configure the first, second, and final
threshold warnings as well as the maximum lines for the
memory buffer log.
config log memory global setting
set first-full-warning-threshold 40
set second-full-warning-threshold 60
set final-full-warning-threshold 80
set max-lines 60
end
Related topics
log {disk | Usla | memory | syslogd | webtrends | Usservice}
filter
log Usla setting
log syslogd setting
log webtrends setting
log trafficfilter
log report definition
memory setting
Syslogd Setting
Use this command to configure log settings for logging to a
remote syslog server. You can configure the ZXSEC US unit to
send logs to a remote computer running a syslog server.
Using the CLI, you can send logs to up to three different syslog
servers. Configure additional syslog servers using syslogd2 and
syslogd3 commands and the same keywords outlined below.
Note:
Syslog CLI commands are not cumulative. Using a syntax similar
to the following is not valid:
config log syslogd syslogd2 syslogd3 setting
Syntax
config log syslogd setting
set csv {disable | enable}
set facility {alert | audit | auth | authpriv | clock | cron | daemon | ftp
| kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 |
local7 | lpr | mail | news | ntp | syslog | user | uucp}
set port <port_integer>
set server <address_ipv4>
set status {disable | enable}
end
Example
This example shows how to enable logging to a remote syslog
server, configure an IP address and port for the server, and
enable logging in CSV format.
config log syslogd setting
set status enable
set server 220.210.200.190
Webtrends Setting
Use this command to configure log settings for logging to a
remote computer running a NetIQ WebTrends firewall reporting
server.
ZXSEC US log formats comply with WebTrends Enhanced Log
Format (WELF) and are compatible with NetIQ WebTrends
Security Reporting Center and Firewall Suite 4.1.
Syntax
config log webtrends setting
set server <address_ipv4>
set status {disable | enable}
end
Example
This example shows how to enable logging to and set an IP
address for a remote WebTrends server.
config log webtrends setting
set status enable
set server 220.210.200.190
end
Related topics
log {disk | Usla | memory | syslogd | webtrends | Usservice}
filter
log Usla setting
log memory setting
log syslogd setting
log trafficfilter
log report definition
Trafficfilter
Use this command to configure the following global settings for
traffic logging:
resolve IP addresses to host names
display the port number or service (protocol) in the log
message
Syntax
config log trafficfilter
set display {name | port}
set resolve {disable | enable}
end
The config log trafficfilter command has 1 subcommand.
config rule
Example
This example shows how to display the service name and enable
resolving IP addresses to host names in log messages.
config log trafficfilter
Config Rule
Access the rule subcommand using the log trafficfilter command.
Use the following commands to configure traffic filter rules based
on source IP address, destination IP address, and service
(protocol).
Syntax
config rule
edit <name_str>
set dst <any_ip&any_netmask>
set service <name_str>
set src <class_ip&net_netmask>
end
Example
This example shows how to configure a traffic filter called TF_1,
to configure the source and destination IP and netmask, and to
set the service to HTTP.
config log trafficfilter config rule
edit TF_1
set dst 220.210.200.190 255.255.255.0
set src 192.168.100.1 255.255.255.0
set service HTTP
end
end
Related topics
log {disk | Usla | memory | syslogd | webtrends | Usservice}
filter
log Usla setting
log memory setting
log syslogd setting
log webtrends setting
log report definition
Report Customization
Use this command to customize your report with the company
name, or to customize footers and headers.
Syntax
config log report customization
set company <company_name>
set footer-option {custom | report-title} <footer>
set header <header_name>
end
Example
This example shows how to customize the report with the
company name XYN, along with a customized footer and header
for the report.
Report Definition
Use this command to add information to the report, including
the title of the report and a description of what is contained in
the report.
Syntax
config log report definition
set description <report_description>
set title <report_title>
end
Example
This example shows how to set the report name and title.
Report Filter
Use this command to view or remove information from a report
to provide a more concise report. For example, you only want
reports on specific error messages, or you do not want include
certain IP address destinations.
Syntax
config log report filter
set filter-string <filter_string>
end
Related topics
report definition
report output
report period
report schedule
report scope
report selection
Report Output
Use this command to configure a file format for the report for
email recipients, saved to the Usla hard disk. Use this command
to also configure the Usla unit to upload the report files to an
FTP server when completed.
Syntax
config log report output config addresses
edit address <address_str>
set from <from_sender>
set server <server_ip>
next
end
set email {html | pdf | rtf | txt}
set email-attachment-name <name_str>
set email-body <string>
set email-subject <subject_str>
set file {html | pdf | rtf | txt}
set upload {enable | disable}
set upload-delete {enable | disable}
set upload-dir <directory_str>
set upload-gzipped {enable | disable}
set upload-ip <ip_str>
set upload-password <passwd_str>
set upload-server-type {FTP | SCP | SFTP}
set upload-username <username_str>
end
Example
This example shows how to set the report output to HTML and
PDF formats.
config log report output
set output file html pdf
end
Related topics
report definition
report filter
report period
report schedule
report scope
report selection
Report Period
Use this command to select the time span for the report period
or select a specific time frame. When the Usla unit generates the
report, it uses the log data found within the specified time period
only.
Syntax
config log report period
set type {last-14-days | last-2-weeks |last-30-days | last-7-
days|last-month | last-n-days | last-n-hours | last-n-weeks | last-
quarter | last week | other | this-month | this-quarter | this-week |
this-year | today | yesterday}
end
Example
This example shows how to set the reporting period to the
previous weeks data.
config log report period
Report Schedule
Use this command to set a schedule when the Usla unit
generates the reports.
Syntax
config log report schedule
set type {daily | dates | days | none}
set dates {1-31}
set days {mon | tue | wed | thu | fri | sat |sun}
set time <hh:mm>
end
Example
This example shows how to set the report to run every Monday
at 9:56.
config log report schedule
set type days
set days mon set time 09:56
end
Related topics
report definition
report filter
report output
report period
report scope
report selection
Report Scope
Use this command to select the type of results you would like to
include in the report.
Syntax
config log report scope
set audit <integer>
set exclude-summary {enable |disable}
set include-nodata {enable | disable}
set include-summary {enable | disable}
set include-table-of-content {enable | disable}
set obfuscate-user {enable | disable}
set resolve-host {enable | disable}
set resolve-service {enable | disable}
set result {all} set top1 {1-30}
set top2 {1-30}
end
Example
This example shows how to set the resolving of the host and
service names in the report.
config log report scope
set resolve-host enable
set resolve-service enable
end
Related topics
report definition
report filter
report output
report period
report schedule
report selection
Report Selection
Use this command to select the reports to include within the
report profile.
Syntax
config log report selection
set selection <report_category> [<report> <report>...]
end
For a list of report categories and reports, see the list in the
command line interface.
Example
This example shows how to set the network activity report.
config log report selection
set network-activity net-date-dir net-dir
end
Related topics
report definition
report filter
report output
report period
report schedule
report scope
Report Summary-layout
Use this command to customize the summary reports.
Syntax
config log report summary-layout
set summary-column {1 | 2 | 3 | 4}
config summary-reports
edit name <sum_category> [<sum_report> <sum_report>...]
set order <integer>
set style {bar | line | pie}
set topN <integer>
end
end
Example
In this example, the number of columns in the summary layout
is three. There are four summary reports included in this report,
the summary protocol distribution, total viruses detected, total
spam activity, and total web filter activity. The summary report,
total viruses detected, will come first and all summary reports
will be pie charts.
config log report summary-layout set summary-column 3
config summary-reports edit name sum-proto
set order 4
set style column set topN 5
next
edit name sum-tv set order 1
set style bar set topN 5
next
edit name sum-mf set order 2
set style line set topN 5
next
edit name sum-wf
set order 3 set style pie
set topN 5
end
end
Related topics
report definition
report filter
report output
report period
report schedule
report scope
Chapter 10
Overview
This chapter covers the commands to configure event notification. This
chapter contains the following sections:
Notification
Notification
Use this command to configure event notification.
Syntax
config notification
set maximum-retries <integer>
set maximum-sessions <integer>
set mem-percent <integer>
end
Router
Overview
Routers move packets from one network segment to another
towards a network destination. When a packet reaches a router,
the router uses data in the packet header to look up a suitable
route on which to forward the packet to the next segment. The
information that a router uses to make routing decisions is
stored in a routing table. Other factors related to the availability
of routes and the status of the network may influence the route
selection that a router makes when forwarding a packet to the
next segment.
The ZXSEC US unit supports many advanced routing functions
and is compatible with industry standard Internet routers. The
ZXSEC US unit can communicate with other routers to determine
the best route for a packet.
The following router commands are available to configure
options related to ZXSEC US unit router communications and
packet forwarding:
access-list
aspath-list
auth-path
bgp
community-list
key-chain
multicast
ospf
policy
prefix-list
rip
route-map
static
static6
Access-list
Use this command to add, edit, or delete access lists. Access
lists are filters used by ZXSEC US unit routing processes. For an
access list to take effect, it must be called by a ZXSEC US unit
routing process (for example, a process that supports RIP or
OSPF).
Each rule in an access list consists of a prefix (IP address and
netmask), the action to take for this prefix (permit or deny), and
whether to match the prefix exactly or to match the prefix and
any more specific prefix.
Note:
The default route, 0.0.0.0/0 can not be exactly matched with an
access-list. A prefix-list must be used for this purpose. See
“prefix-list”.
The ZXSEC US unit attempts to match a packet against the rules
in an access list starting at the top of the list. If it finds a match
for the prefix, it takes the action specified for that prefix. If no
match is found the default action is deny.
Syntax
config router access-list edit <access_list_name> set comments
<string>
config rule
edit <access_list_id>
set action {deny | permit}
set exact-match {enable | disable}
set prefix { <prefix_ipv4mask> | any }
set wildcard <address_ipv4> <wildcard_mask>
end
end
Note:
The action and prefix keywords are required. The exact-match
keyword is optional.
T AB L E 6 7 AC C E S S -L I S T S ET T I N G
Example
This example shows how to add an access list named acc_list1
with two rules. The first rule denies the subnet that exactly
matches the prefix 192.168.50.0 255.255.255.0 and permits all
other subnets that match the prefix 192.168.0.0 255.255.0.0.
config router access-list
edit acc_list1
config rule
edit 1
set prefix 192.168.50.0 255.255.255.0
set action deny
set exact-match enable
next
edit 2
set prefix 192.168.0.0 255.255.0.0
set action permit
set exact-match disable
end
end
The next example shows how to add an access list that permits
all subnets matching network address 10.20.4.1 through
10.20.4.255 (addresses 10.20.4.x are processed):
config router access-list
edit acc_list2
config rule
edit 1
set action permit
set wildcard 10.20.4.0 0.0.0.255
end
end
The next example shows how to add an access list that permits
“odd” subnets according to the third- octet of network address
172.16.x.0 (networks 172.16.1.0, 172.16.3.0, 172.16.5.0, and
so on are processed):
config router access-list
edit acc_list3
config rule edit 1
set action permit
set wildcard 172.16.1.0 0.0.254.0
end
Related topics
router ospf
router prefix-list
router rip
Aspath-list
Use this command to set or unset BGP AS-path list parameters.
By default, BGP uses an ordered list of Autonomous System (AS)
numbers to describe the route that a packet takes to reach its
destination.
A list of AS numbers is called an AS path. You can filter BGP
routes using AS path lists.
When the ZXSEC US unit receives routing updates from other
autonomous systems, it can perform operations on updates from
neighbors and choose the shortest path to a destination. The
shortest path is determined by counting the number of AS
numbers in the AS path. The path that has the least number of
AS numbers is considered the shortest AS path.
Use the config router aspath-list command to define an access
list that examines the AS_PATH attributes of BGP routes to
match routes. Each entry in the AS-path list defines a rule for
matching and selecting routes based on the setting of the
AS_PATH attribute. The default rule in an AS path list (which the
ZXSEC US unit applies last) denies the matching of all routes.
Syntax
config router aspath-list
edit <aspath_list_name>
config rule
edit <as_rule_id>
set action {deny | permit}
set regexp <regexp_str>
end
end
Note:
The action and regexp keywords are required.
T AB L E 6 8 AS P AT H -L I S T S E T T I N G
Example
This example shows how to create an AS-path list named
ebgp_in. The list contains a single rule that permits operations
on BGP routes whose AS_PATH attribute references an AS
number of 333, 334, 338, or 71. The AS path list will match
routes that originate in AS 333, AS 334, AS 338, or AS 71.
config router aspath-list
edit ebgp_in
config rule edit 1
set action permit
set regexp _(333|334|338|71)$
end
end
Related topics
router bgp
router community-list
Using route maps with BGP
router key-chain
Auth-path
Authentication based routing allows firewall policies to direct
network traffic flows.
This command configures a RADIUS object on your ZXSEC US
unit. The same object is required to be configured on the
RADIUS server.
To configure authentication based routing on your ZXSEC US
unit
1. Configure your ZXSEC US unit to communicate with a
RADIUS authentication server.
2. Configure a user that uses the RADIUS server.
Note:
The auth-path command is not available when the ZXSEC US
unit is in Transparent mode.
Syntax
config router auth-path
edit <aspath_list_name>
set device <interface>
set gateway <gway_ipv4>
end
T AB L E 6 9 AU T H -P AT H S E T T I N G
Example
This example shows how to configure an auth-path object called
auth_route that routes traffic over the dmz interface using
172.20.120.4. These settings also need to be configured on the
RADIUS server used to authenticate.
config router auth-path
edit auth_route
set device dmz
set gateway 172.20.120.4
next
end
Related topics
user local
user radius
firewall policy, policy6
BGP
Use this command to set or unset BGP-4 routing parameters.
BGP can be used to perform Classless Interdomain Routing
(CIDR) and to route traffic between different autonomous
systems or domains using an alternative route if a link between
a ZXSEC US unit and a BGP peer (such as an ISP router) fails.
USnet BGP-4 complies with RFC 1771 and supports IPv4
addressing.
When BGP is enabled, the ZXSEC US unit sends routing table
updates to the upstream ISP router whenever any part of the
routing table changes. The update advertises which routes can
be used to reach the ZXSEC US unit. In this way, routes are
made known from the border of the internal network outwards
(routes are pushed forward) instead of relying on upstream
routers to propagate alternative paths to the ZXSEC US unit.
ZXSEC US unit BGP supports the following extensions to help
manage large numbers of BGP peers:
Communities — The ZXSEC US unit can set the COMMUNITY
attribute of a route to assign the route to predefined paths
(see RFC 1997). The ZXSEC US unit can examine the
COMMUNITY attribute of learned routes to perform local
filtering and/or redistribution.
Internal BGP (IBGP) route reflectors — The ZXSEC US unit
can operate as a route reflector or participate as a client in a
cluster of IBGP peers (see RFC 1966).
External BGP (EBGP) confederations — The ZXSEC US unit
can operate as a confederation member, using its AS
confederation identifier in all transactions with peers that are
not members of its confederation (see RFC 3065).
Bi-directional Forwarding Detection (BFD) is a protocol used by
BGP and OSPF. It is used to quickly locate hardware failures in
the network. Routers running BFD communicate with each other,
and if a timer runs out on a connection then that router is
declared down. BFD then communicates this information to the
routing protocol and the routing information is updated. BFD
support was added in US v3.0 MR4, and can only be configured
through the CLI.
Syntax
config router bgp
end
config aggregate-address
edit <aggr_addr_id>
set as-set {enable | disable}
set prefix <address_ipv4mask>
set summary-only {enable | disable}
end
config neighbor
edit <neighbor_address_ipv4>
set activate {enable | disable}
set advertisement-interval <seconds_integer>
set allowas-in <max_num_AS_integer>
set allowas-in-enable {enable | disable}
set attribute-unchanged [as-path] [med] [next-hop]
set bfd {enable | disable}
set capability-default-originate {enable | disable}
set capability-dynamic {enable | disable}
set capability-graceful-restart {enable | disable}
set capability-orf {both | none | recieve | send}
set capability-route-refresh {enable | disable}
set connect-timer <seconds_integer>
set description <text_str>
set distribute-list-in <access-list-name_str>
set distribute-list-out <access-list-name_str>
set dont-capability-negotiate {enable | disable}
set ebgp-enforce-multihop {enable | disable}
set ebgp-multihop-ttl <seconds_integer>
set filter-list-in <aspath-list-name_str>
set filter-list-out <aspath-list-name_str>
set holdtime-timer <seconds_integer>
set interface <interface-name_str>
set keep-alive-timer <seconds_integer>
set maximum-prefix <prefix_integer>
set maximum-prefix-threshold <percentage_integer>
set maximum-prefix-warning-only {enable | disable}
set next-hop-self {enable | disable}
set override-capability {enable | disable}
set passive {enable | disable}
Note:
In the following table, the as and router-id keywords are
required. All other keywords are optional.
Example
The following example defines the number of the AS of which
the ZXSEC US unit is a member. It also defines an EBGP
neighbor at IP address 10.0.1.2.
config router bgp
set as 65001
set router-id 172.16.120.20
config neighbor edit 10.0.1.2
set remote-as 65100
end
end
Config Admin-Distance
Use this subcommand to set administrative distance
modifications for bgp routes.
Example
This example shows how to manually adjust the distance
associated with a route. It shows adding 25 to the weight of the
route, that it will apply to neighbor routes with an IP address of
192.168.0.0 and a netmask of 255.255.0.0, that are also
permitted by the access-list “downtown_office”.
config router bgp
config admin-distance
edit 1
set distance 25
set neighbour-prefix 192.168.0.0 255.255.0.0
set route-list downtown_office next
end
end
Config Aggregate-Address
Use this subcommand to set or unset BGP aggregate-address
table parameters. The subcommand creates a BGP aggregate
entry in the ZXSEC US unit routing table.
When you aggregate routes, routing becomes less precise
because path details are not readily available for routing
purposes. The aggregate address represents addresses in
several autonomous systems. Aggregation reduces the length of
the network mask until it masks only the bits that are common
to all of the addresses being summarized.
Note:
The prefix keyword is required. All other keywords are optional.
Example
This example shows how to define an aggregate prefix of
192.168.0.0/16. The as-set command enables the generation of
an unordered list of AS numbers to include in the path
information.
config router bgp
config aggregate-address
edit 1
Config Neighbor
Use this subcommand to set or unset BGP neighbor
configuration settings. The subcommand adds a BGP neighbor
configuration to the ZXSEC US unit.
You can clear all or some BGP neighbor connections (sessions)
using the exec router clear bgp command (see “router clear
bgp”).
Note:
The remote-as keyword is required. All other keywords are
optional.
Example
This example shows how to set the AS number of a BGP
neighbor at IP address 10.10.10.167 and enter a descriptive
name for the configuration.
config router bgp
config neighbor
edit 10.10.10.167
set remote-as 2879
set description BGP_neighbor_Site1
end
end
Config Network
Use this subcommand to set or unset BGP network configuration
parameters. The subcommand is used to advertise a BGP
network (that is, an IP prefix)—you specify the IP addresses
making up the local BGP network.
When you enable the network-import-check attribute on the
ZXSEC US unit (see “network- import-check {enable | disable})
and you specify a BGP network prefix through the config
network command, the ZXSEC US unit searches its routing table
Note:
The prefix keyword is required. All other keywords are optional.
Example
This example defines a BGP network at IP address 10.0.0.0/8. A
route map named BGP_rmap1 is used to modify the attributes of
the local BGP routes before they are advertised.
config router bgp
config network
edit 1
set prefix 10.0.0.0/8
set route-map BGP_rmap1
end
end
config router route-map
edit BGP_rmap1
config rule edit 1
set set-community no-export end
end
Config Redistribute
Use this subcommand to set or unset BGP redistribution table
parameters. You can enable BGP to provide connectivity
between connected, static, RIP, and/or OSPF routes. BGP
redistributes the routes from one protocol to another. When a
large internetwork is divided into multiple routing domains, use
the subcommand to redistribute routes to the various domains.
As an alternative, you can use the config network subcommand
to advertise a prefix to the BGP network (see “config network”).
The BGP redistribution table contains four static entries. You
cannot add entries to the table. The entries are defined as
follows:
connected—Redistribute routes learned from a direct
connection to the destination network.
static—Redistribute the static routes defined in the ZXSEC US
unit routing table.
rip—Redistribute routes learned from RIP.
ospf—Redistribute routes learned from OSPF.
When you enter the subcommand, end the command with one of
the four static entry names (that is, config redistribute
{connected | static | rip | ospf}).
Note:
The status and route-map keywords are optional.
Example
The following example changes the status and route-map fields
of the connected entry.
config router bgp
config redistribute connected
set status enable
Community-list
Use this command to identify BGP routes according to their
COMMUNITY attributes (see RFC 1997). Each entry in the
community list defines a rule for matching and selecting routes
based on the setting of the COMMUNITY attribute. The default
rule in a community list (which the ZXSEC US unit applies last)
denies the matching of all routes.
You add a route to a community by setting its COMMUNITY
attribute. A route can belong to more than one community. A
route may be added to a community because it has something in
common with the other routes in the group (for example, the
attribute could identify all routes to satellite offices).
When the COMMUNITY attribute is set, the ZXSEC US unit can
select routes based on their COMMUNITY attribute values.
Syntax
config router community-list
edit <community_name>
set type {standard | expanded}
config rule
edit <community_rule_id>
set action {deny | permit}
set match <criteria>
set regexp <regular_expression>
end
end
Note:
The action keyword is required. All other keywords are optional.
Example
This example creates a community list named Satellite_offices.
The list permits operations on BGP routes whose COMMUNITY
attribute is set to no-advertise.
config router community-list
edit Satellite_offices
set type standard config rule
edit 1
set action permit
set match no-advertise end
end
The next example creates a community list named
ext_community. The list permits operations on BGP routes
whose COMMUNITY attribute has the number 3 in the second
part of the first instance and the number 86 in the second part
of the second instance. For example, the community list could
match routes having the following COMMUNITY attribute values:
“100:3 500:86 300:800”, “1:3 4:86”, or “69:3 69:86 69:69
70:800 600:333”).
config router community-list
edit ext_community
set type expanded config rule
edit 1
set action permit
set regexp “.*:3 .*:86”
end
end
Related topics
router aspath-list
router bgp
router Using route maps with BGP
router key-chain
Key-chain
Use this command to manage RIP version 2 authentication keys.
You can add, edit or delete keys identified by the specified key
number.
RIP version 2 uses authentication keys to ensure that the
routing information exchanged between routers is reliable. For
authentication to work both the sending and receiving routers
must be set to use authentication, and must be configured with
the same keys.
A key chain is a list of one or more keys and the send and
receive lifetimes for each key. Keys are used for authenticating
routing packets only during the specified lifetimes. The ZXSEC
US unit migrates from one key to the next according to the
scheduled send and receive lifetimes. The sending and receiving
routers should have their system dates and times synchronized,
but overlapping the key lifetimes ensures that a key is always
available even if there is some difference in the system times.
See “config system global” to ensure that the ZXSEC US unit
system date and time are correct.
Syntax
config router key-chain edit <key_chain_name>
config key
edit <key_id>
set accept-lifetime <start> <end>
set key-string <password>
set send-lifetime <start> <end>
end
end
Note:
The accept-lifetime, key-string, and send-lifetime keywords are
required.
Example
This example shows how to add a key chain named test1 with
three keys. The first two keys each have send and receive
lifetimes of 13 hours, and the 3rd key has send and receive
lifetimes that never expire.
Multicast
A ZXSEC US unit can operate as a Protocol Independent
Multicast (PIM) version 2 router in the root virtual domain.
ZXSEC US units support PIM sparse mode (RFC 4601) and PIM
dense mode (RFC 3973) and can service multicast servers or
receivers on the network segment to which a ZXSEC US unit
interface is connected. Multicast routing is only available in the
root virtual domain. It is not supported in Transparent mode (TP
mode).
Note:
To support PIM communications, the sending/receiving
applications and all connecting PIM routers in between must be
enabled with PIM version 2. PIM can use static routes, RIP, OSPF,
or BGP to forward multicast packets to their destinations. To
enable source-to-destination packet delivery, either sparse mode
or dense mode must be enabled on the PIM-router interfaces.
Sparse mode routers cannot send multicast messages to dense
mode routers. In addition, if a ZXSEC US unit is located between
a source and a PIM router, two PIM routers, or is connected
Sparse Mode
Initially, all candidate BSRs in a PIM domain exchange bootstrap
messages to select one BSR to
which each RP sends the multicast address or addresses of the
multicast group(s) that it can service. The selected BSR chooses
one RP per multicast group and makes this information available
to all of the PIM routers in the domain through bootstrap
messages. PIM routers use the information to build packet
distribution trees, which map each multicast group to a specific
RP. Packet distribution trees may also contain information about
the sources and receivers associated with particular multicast
groups.
Note:
When a ZXSEC US unit interface is configured as a multicast
interface, sparse mode is enabled on it by default to ensure that
distribution trees are not built unless at least one downstream
receiver requests multicast traffic from a specific source. If the
sources of multicast traffic and their receivers are close to each
other and the PIM domain contains a dense population of active
receivers, you may choose to enable dense mode throughout the
PIM domain instead.
An RP represents the root of a non-source-specific distribution
tree to a multicast group. By joining and pruning the information
contained in distribution trees, a single stream of multicast
packets (for example, a video feed) originating from the source
can be forwarded to a certain RP to reach a multicast destination.
Each PIM router maintains a Multicast Routing Information Base
(MRIB) that determines to which neighboring PIM router join and
prune messages are sent. An MRIB contains reverse-path
information that reveals the path of a multicast packet from its
source to the PIM router that maintains the MRIB.
To send multicast traffic, a server application sends IP traffic to
a multicast group address. The locally elected DR registers the
sender with the RP that is associated with the target multicast
Dense Mode
The packet organization used in sparse mode is also used in
dense mode. When a multicast source begins to send IP traffic
and dense mode is enabled, the closest PIM router registers the
IP traffic from the multicast source (S) and forwards multicast
packets to the multicast group address (G). All PIM routers
initially broadcast the multicast packets throughout the PIM
domain to ensure that all receivers that have requested traffic
for multicast group address G can access the information if
needed.
To forward multicast packets to specific destinations afterward,
the PIM routers build distribution trees based on the information
in multicast packets. Upstream PIM routers depend on
prune/graft messages from downstream PIM routers to
determine if receivers are actually present on directly connected
network segments. The PIM routers exchange state refresh
messages to update their distribution trees. ZXSEC US units
store this state information in a Tree Information Base (TIB),
which is used to build a multicast forwarding table. The
information in the multicast forwarding table determines
whether packets are forwarded downstream. The forwarding
table is updated whenever the TIB is modified.
PIM routers receive data streams every few minutes and update
their forwarding tables using the source (S) and multicast group
(G) information in the data stream. Superfluous multicast traffic
is stopped by PIM routers that do not have downstream
receivers — PIM routers that do not manage multicast groups
send prune messages to the upstream PIM routers. When a
receiver requests traffic for multicast address G, the closest PIM
router sends a graft message upstream to begin receiving
multicast packets.
Syntax
config router multicast
set igmp-state-limit <limit_integer>
set multicast-routing {enable | disable}
set route-limit <limit_integer>
set route-threshold <threshold_integer>
config interface
edit <interface_name>
set cisco-exclude-genid {enable | disable}
set dr-priority <priority_integer>
set hello-holdtime <holdtime_integer>
set hello-interval <hello_integer>
set neighbour-filter <access_list_name>
set passive {enable | disable}
set pim-mode {sparse-mode | dense-mode}
set propagation-delay <delay_integer>
set rp-candidate {enable | disable}
set rp-candidate-group <access_list_name>
set rp-candidate-interval <interval_integer>
set rp-candidate-priority <priority_integer>
set state-refresh-interval <refresh_integer>
set ttl-threshold <ttl_integer>
end
config join-group
edit address <address_ipv4>
end
config igmp
set access-group <access_list_name>
set immediate-leave-group <access_list_name>
set last-member-query-count <count_integer>
set last-member-query-interval <interval_integer>
set query-interval <interval_integer>
set query-max-response-time <time_integer>
set query-timeout <timeout_integer>
set router-alert-check { enable | disable }
set version {1 | 2 | 3}
end
end
config pim-sm-global
set accept-register-list <access_list_name>
set bsr-allow-quick-refresh {enable | disable}
set bsr-candidate {enable | disable}
set bsr-priority <priority_integer>
set bsr-interface <interface_name>
set bsr-hash <hash_integer>
set cisco-register-checksum {enable | disable}
set cisco-register-checksum-group <access_list_name>
set cisco-crp-prefix {enable | disable}
set cisco-ignore-rp-set-priority {enable | disable}
set message-interval <interval_integer>
set register-rate-limit <rate_integer>
set register-rp-reachability {enable | disable}
set register-source {disable | interface | ip-address}
set register-source-interface <interface_name>
set register-source-ip <address_ipv4>
set register-suppression <suppress_integer>
set rp-register-keepalive <keepalive_integer>
set spt-threshold {enable | disable}
set spt-threshold-group <access_list_name>
set ssm {enable | disable}
set ssm-range <access_list_name>
config rp-address edit <rp_id>
set ip-address <address_ipv4>
set group <access_list_name>
end
end
Note:
The end-user multicast client-server applications must be
installed and configured to initiate Internet connections and
handle broadband content such as audio/video information.
Client applications send multicast data by registering IP traffic
with a PIM-enabled router. An end-user could type in a class D
multicast group address, an alias for the multicast group address,
or a call- conference number to initiate the session. Rather than
sending multiple copies of generated IP traffic to more than one
specific IP destination address, PIM-enabled routers encapsulate
the data and use the one multicast group address to forward
multicast packets to multiple destinations. Because one
destination address is used, a single stream of data can be sent.
Client applications receive multicast data by requesting that the
traffic destined for a certain multicast group address be
delivered to them— end-users may use phone books, a menu of
ongoing or future sessions, or some other method through a
user interface to select the address of interest.
A class D address in the 224.0.0.0 to 239.255.255.255 range
may be used as a multicast group address, subject to the rules
assigned by the Internet Assigned Numbers Authority (IANA). All
class D addresses must be assigned in advance. Because there
is no way to determine in advance if a certain multicast group
address is in use, collisions may occur (to resolve this problem,
end-users may switch to a different multicast address).
To configure a PIM domain
1. If you will be using sparse mode, determine appropriate
paths for multicast packets.
2. Make a note of the interfaces that will be PIM-enabled. These
interfaces may run a unicast routing protocol.
3. If you will be using sparse mode and want multicast packets
to be handled by specific (static) RPs, record the IP
addresses of the PIM-enabled interfaces on those RPs.
4. Enable PIM version 2 on all participating routers between the
source and receivers. On ZXSEC US units, use the config
router multicast command to set global operating
parameters.
5. Configure the PIM routers that have good connections
throughout the PIM domain to be candidate BSRs.
6. If sparse mode is enabled, configure one or more of the PIM
routers to be candidate RPs.
7. If required, adjust the default settings of PIM-enabled
interface(s).
Note:
All keywords are optional.
Config Interface
Use this subcommand to change interface-related PIM settings,
including the mode of operation (sparse or dense). Global
settings do not override interface-specific settings.
Note:
All keywords are optional.
Config Pim-sm-global
These global settings apply only to sparse mode PIM-enabled
interfaces. Global PIM settings do not override interface-specific
PIM settings.
If sparse mode is enabled, you can configure a DR to send
multicast packets to a particular RP by specifying the IP address
of the RP through the config rp-address subcommand. The IP
address must be directly accessible to the DR. If multicast
packets from more than one multicast group can pass through
the same RP, you can use an access list to specify the associated
multicast group addresses.
Note:
To send multicast packets to a particular RP using the config rp-
address subcommand, the ip- address keyword is required. All
other keywords are optional.
Example
This example shows how to enable a ZXSEC US unit to support
PIM routing in sparse mode and enable BSR candidacy on the
dmz interface:
config router multicast
set multicast-routing enable config interface
edit dmz
set pim-mode sparse-mode end
end
config pim-sm-global
set bsr-candidate enable
set bsr-priority 1
set bsr-interface dmz set bsr-hash 24
end
This example shows how to enable RP candidacy on the port1
interface for the multicast group addresses given through an
access list named multicast_port1:
config router multicast
set multicast-routing enable config interface
edit port1
set pim-mode sparse-mode
set rp-candidate enable
set rp-candidate-group multicast_port1
set rp-candidate-priority 15
end
end
Related topics
get router info multicast
execute mrouter clear
OSPF
Use this command to configure Open Shortest Path First (OSPF)
protocol settings on the ZXSEC US unit. More information on
OSPF can be found in RFC 2328.
OSPF is a link state protocol capable of routing larger networks
than the simpler distance vector RIP protocol. An OSPF
autonomous system (AS) or routing domain is a group of areas
connected to a backbone area. A router connected to more than
one area is an area border router (ABR). Routing information is
contained in a link state database. Routing information is
communicated between routers using link state advertisements
(LSAs).
Bi-directional Forwarding Detection (BFD) is a protocol used by
BGP and OSPF. It is used to quickly locate hardware failures in
the network. Routers running BFD communicate with each other,
and if a timer runs out on a connection then that router is
declared down. BFD then communicates this information to the
routing protocol and the routing information is updated. BFD
support was added in US v3.0 MR4, and can only be configured
through the CLI.
Syntax
config router ospf
set abr-type {cisco | ibm | shortcut | standard}
set auto-cost-ref-bandwidth <mbps_integer>
set bfd {enable | disable | global}
set database-overflow {enable | disable}
set database-overflow-max-lsas <lsas_integer>
set database-overflow-time-to-recover <seconds_integer>
set default-information-metric <metric_integer>
set default-information-metric-type {1 | 2}
set default-information-originate {always | disable | enable}
set default-information-route-map <name_str>
set default-metric <metric_integer>
set distance <distance_integer>
set distance-external <distance_integer>
set distance-inter-area <distance_integer>
set distance-intra-area <distance_integer>
set distribute-list-in <access_list_name>
set passive-interface <name_str>
end end
config distribute-list
edit <distribute-list_id>
set access-list <name_str>
set protocol {connected | rip | static}
end
end
config neighbor
edit <neighbor_id>
set cost <cost_integer>
set ip <address_ipv4>
set poll-interval <seconds_integer>
set priority <priority_integer>
end
end
config network
edit <network_id>
set area <id-address_ipv4>
set prefix <address_ipv4mask>
end
end
config ospf-interface
edit <ospf_interface_name>
set authentication {md5 | none | text}
set authentication-key <password_str> set
set cost <cost_integer>
set database-filter-out {enable | disable}
set dead-interval <seconds_integer>
set hello-interval <seconds_integer>
set interface <name_str>
set ip <address_ipv4>
set md5-key <id_integer> <key_str>
set mtu <mtu_integer>
set mtu-ignore {enable | disable}
set network-type <type>
set priority <priority_integer>
set resync-timeout <integer>
set retransmit-interval <seconds_integer>
Note:
The router-id keyword is required. All other keywords are
optional.
Example
This example shows how to set the OSPF router ID to 1.1.1.1 for
a standard area border router:
config router ospf
set abr-type standard
set router-id 1.1.1.1
end
Config Area
Use this subcommand to set OSPF area related parameters.
Routers in an OSPF autonomous system (AS) or routing domain
are organized into logical groupings called areas. Areas are
linked together by area border routers (ABRs). There must be a
backbone area that all areas can connect to. You can use a
virtual link to connect areas that do not have a physical
connection to the backbone. Routers within an OSPF area
maintain link state databases for their own areas.
You can use the config filter-list subcommand to control the
import and export of LSAs into and out of an area. See “config
filter-list variables”. You can use access or prefix lists for OSPF
area filter lists. For more information, see “access-list” and
“prefix-list”.
You can use the config range subcommand to summarize routes
at an area boundary. If the network numbers in an area are
contiguous, the ABR advertises a summary route that includes
all the networks within the area that are within the specified
range. See “config range variables”.
You can configure a virtual link using the config virtual-link
subcommand to connect an area to the backbone when the area
has no direct connection to the backbone (see “config virtual-link
variables”). A virtual link allows traffic from the area to transit a
directly connected area to reach the backbone. The transit area
cannot be a stub area. Virtual links can only be set up between
two ABRs.
Note:
If you define a filter list, the direction and list keywords are
required. If you define a range, the prefix keyword is required. If
you define a virtual link, the peer keyword is required. All other
keywords are optional.
Example
This example shows how to configure a stub area with the id
15.1.1.1, a stub type of summary, a default cost of 20, and MD5
authentication.
config router ospf
config area
edit 15.1.1.1
set type stub
set stub-type summary
set default-cost 20
set authentication md5
end
end
This example shows how to use a filter list named acc_list1 to
filter packets entering area 15.1.1.1.
config router ospf
config area
edit 15.1.1.1
config filter-list
edit 1
set direction in set list acc_list1
end
end
This example shows how to set the prefix for range 1 of area
15.1.1.1.
config router ospf
config area
edit 15.1.1.1
config range
edit 1
set prefix 1.1.0.0 255.255.0.0
end
end
This example shows how to configure a virtual link.
config router ospf
config area
edit 15.1.1.1
config virtual-link
edit vlnk1
set peer 1.1.1.1
end
end
Config Distribute-list
Use this subcommand to filter the networks in routing updates
using an access list. Routes not matched by any of the
distribution lists will not be advertised.
You must configure the access list that you want the distribution
list to use before you configure the distribution list. To configure
an access list, see “access-list”.
Note:
The access-list and protocol keywords are required.
Example
This example shows how to configure distribution list 2 to use an
access list named acc_list1 for all static routes.
config router ospf
config distribute-list
edit 2
set access-list acc_list1
set protocol static end
end
Config Neighbor
Use this subcommand to manually configure an OSPF neighbor
on non-broadcast networks. OSPF packets are unicast to the
specified neighbor address. You can configure multiple neighbors.
Note:
The ip keyword is required. All other keywords are optional.
Example
This example shows how to manually add a neighbor.
config router ospf
config neighbor
edit 1
set ip 192.168.21.63
end
end
Config Network
Use this subcommand to identify the interfaces to include in the
specified OSPF area. The prefix keyword can define one or
multiple interfaces.
Note:
The area and prefix keywords are required.
Example
Use the following command to enable OSPF for the interfaces
attached to networks specified by the IP address 10.0.0.0 and
the netmask 255.255.255.0 and to add these interfaces to area
10.1.1.1.
config router ospf
config network
edit 2
set area 10.1.1.1
set prefix 10.0.0.0 255.255.255.0
end
end
Config OSPF-Interface
Use this subcommand to change interface related OSPF settings.
Note:
Example
This example shows how to assign an OSPF interface
configuration named test to the interface named internal and
how to configure text authentication for this interface.
config router ospf config ospf-interface
edit test
set interface internal set ip 192.168.20.3
set authentication text
set authentication-key a2b3c4d5e
end
end
Config Redistribute
Use this subcommand to redistribute routes learned from BGP,
RIP, static routes, or a direct connection to the destination
network.
The OSPF redistribution table contains four static entries. You
cannot add entries to the table. The entries are defined as
follows:
bgp—Redistribute routes learned from BGP.
connected—Redistribute routes learned from a direct
connection to the destination network.
static—Redistribute the static routes defined in the ZXSEC US
unit routing table.
rip—Redistribute routes learned from RIP.
When you enter the subcommand, end the command with one of
the four static entry names (that is, config redistribute {bgp |
connected | static | rip}).
Example
This example shows how to enable route redistribution from RIP,
using a metric of 3 and a route map named rtmp2.
config router ospf
config redistribute rip
set metric 3
set routemap rtmp2
Config Summary-Address
Use this subcommand to summarize external routes for
redistribution into OSPF. This command works only for
summarizing external routes on an Autonomous System
Boundary Router (ASBR). For information on summarization
between areas, see “config range variables”. By replacing the
LSAs for each route with one aggregate route, you reduce the
size of the OSPF link-state database.
Note:
The prefix keyword is required. All other keywords are optional.
Example
This example shows how to summarize routes using the prefix
10.0.0.0 255.0.0.0.
config router ospf
config summary-address
edit 5
set prefix 10.0.0.0 255.0.0.0
end
end
Related topics
router access-list
Policy
Use this command to add, move, edit or delete a route policy.
When you create a policy route, any packets that match the
policy are forwarded to the IP address of the next-hop gateway
through the specified outbound interface.
You can configure the ZXSEC US unit to route packets based on:
a source address
a protocol, service type, or port range
the inbound interface
When the ZXSEC US unit receives a packet, it starts at the top
of the policy routing list and attempts to match the packet with a
policy in ascending order. If no packets match the policy route,
the ZXSEC US unit routes the packet using the routing table.
Route policies are processed before static routing. You can
change the order of policy routes using the move command. See
“config branch”.
Note:
For static routing, any number of static routes can be defined for
the same destination. When multiple routes for the same
destination exist, the ZXSEC US unit chooses the route having
the lowest administrative distance. Route redundancy is not
available for policy routing: any packets that match a route
policy are forwarded according to the route specified in the
policy.
Syntax
config router policy
move <seq-num1> {before | after} <seq-num2>
edit <policy_integer>
set dst <dest-address_ipv4mask>
set end-port <port_integer>
set gateway <address_ipv4>
set input-device <interface-name_str>
set output-device <interface-name_str>
set protocol <protocol_integer>
Note:
The input-device keyword is required. All other keywords are
optional.
Example
If a ZXSEC US unit provides Internet access for multiple internal
subnets, you can use policy routing to control the route that
traffic from each network takes to the Internet. For example, if
the internal network includes the subnets 192.168.10.0 and
192.168.20.0 you can enter the following route policies:
Enter the following command to route traffic from the
192.168.10.0 subnet to the 100.100.100.0 subnet. Force the
packets to the next hop gateway at IP address 1.1.1.1
through the interface named external.
config router policy
edit 1
set input-device internal
set src 192.168.10.0 255.255.255.0
set dst 100.100.100.0 255.255.255.0
set output-device external
set gateway 1.1.1.1
end
Enter the following command to route traffic from the
192.168.20.0 subnet to the 200.200.200.0 subnet. Force the
packets to the next hop gateway at IP address 2.2.2.1
through the interface named external.
config router policy
edit 2
set input-device internal
set src 192.168.20.0 255.255.255.0
set dst 200.200.200.0 255.255.255.0
set output-device external
set gateway 2.2.2.1
end
Prefix-list
Use this command to add, edit, or delete prefix lists. A prefix list
is an enhanced version of an access list that allows you to
control the length of the prefix netmask.
Each rule in a prefix list consists of a prefix (IP address and
netmask), the action to take for this prefix (permit or deny), and
maximum and minimum prefix length settings.
The ZXSEC US unit attempts to match a packet against the rules
in a prefix list starting at the top of the list. If it finds a match
for the prefix it takes the action specified for that prefix. If no
match is found the default action is deny. A prefix-list should be
used to match the default route 0.0.0.0/0.
Note:
The action and prefix keywords are required. All other keywords
are optional.
Examples
This example shows how to add a prefix list named prf_list1 with
three rules. The first rule permits subnets that match prefix
lengths between 26 and 30 for the prefix 192.168.100.0
255.255.255.0. The second rule denies subnets that match the
prefix lengths between 20 and 25 for the prefix 10.1.0.0
255.255.0.0. The third rule denies all other traffic.
config router prefix-list edit prf_list1
config rule edit 1
set prefix 192.168.100.0 255.255.255.0
set action permit
set ge 26
set le 30
next edit 2
set prefix 10.1.0.0 255.255.0.0
set action deny
set ge 20
set le 25
next edit 3
set prefix any set action deny
end
end
The following example shows how to create a prefix-list that will
drop the default route but allow all other prefixes to be passed.
The first rule matches the default route only and is set to deny,
the second rule will match all other prefixes and allow them to
be passed.
config router prefix-list
edit "drop_default"
config rule
edit 1
set action deny
set prefix 0.0.0.0 0.0.0.0
unset ge
unset le
next
edit 2
set prefix any
unset ge
unset le
next
end
next
end
Related topics
router access-list
router rip
RIP
Use this command to configure the Routing Information Protocol
(RIP) on the ZXSEC US unit. RIP is a distance-vector routing
protocol intended for small, relatively homogeneous, networks.
RIP uses hop count as its routing metric. Each network is usually
counted as one hop. The network diameter is limited to 15 hops
with 16 hops.
Syntax
config router rip
set default-information-originate {enable | disable}
set default-metric <metric_integer>
set garbage-timer <timer_integer>
set passive-interface <name_str>
set timeout-timer <timer_integer>
set update-timer <timer_integer>
set version {1 2}
config distance
edit <distance_id>
set access-list <name_str>
set distance <distance_integer>
set prefix <address_ipv4mask>
end
config distribute-list
edit <distribute_list_id>
Note:
All keywords are optional.
Example
This example shows how to enable the advertising of a default
static route into RIP, enable the sending and receiving of RIP
version 1 packets, and raise the preference of local routes in the
static routing table (the default metric) from the default of 1 to 5
- those routes well be less preferred.
config router rip
set default-information-originate enable
set version 1
set default-metric 5
end
Config Distance
Use this subcommand to specify an administrative distance.
When different routing protocols provide multiple routes to the
same destination, the administrative distance sets the priority of
those routes.
The lowest administrative distance indicates the preferred route.
If you specify a prefix, RIP uses the specified distance when the
source IP address of a packet matches the prefix.
Note:
The distance keyword is required. All other keywords are
optional.
Example
This example shows how to change the administrative distance
to 10 for all IP addresses that match the internal_example
access-list.
config router rip config distance
edit 1
set distance 10
set access-list internal_example
end
end
Config Distribute-list
Use this subcommand to filter incoming or outgoing updates
using an access list or a prefix list. If you do not specify an
interface, the filter will be applied to all interfaces. You must
configure the access list or prefix list that you want the
distribution list to use before you configure the distribution list.
For more information on configuring access lists and prefix lists,
see “access-list” and “prefix-list”.
Note:
The direction and listname keywords are required. All other
keywords are optional.
Example
This example shows how to configure and enable a distribution
list to use an access list named acc_list1 for incoming updates
on the external interface.
config router rip
config distribute-list edit 1
set direction in
set interface external
set listname acc_list1
set status enable
end
end
Config Interface
Use this subcommand to configure RIP version 2 authentication,
RIP version send and receive for the specified interface, and to
configure and enable split horizon.
Authentication is only available for RIP version 2 packets sent
and received by an interface. You must set auth-mode to none
when receive-version or send-version are set to 1 or 1 2 (both
are set to 1 by default).
A split horizon occurs when a router advertises a route it learns
over the same interface it learned it on.
In this case the router that gave the learned route to the last
router now has two entries to get to another location. However,
if the primary route fails that router tries the second route to
find itself as part of the route and an infinite loop is created. A
poisoned split horizon will still advertise the route on the
interface it received it on, but it will mark the route as
unreachable. Any unreachable routes are automatically removed
from the routing table. This is also called split horizon with
poison reverse.
Note:
All keywords are optional.
Example
This example shows how to configure the external interface to
send and receive RIP version 2, to use MD5 authentication, and
to use a key chain called test1.
config router rip config interface
edit external
set receive-version 2
set send-version 2
set auth-mode md5
set auth-keychain test1
end
end
Config Neighbor
Use this subcommand to enable RIP to send unicast routing
updates to the router at the specified address. You can use the
neighbor subcommand and “passive-interface <name_str>” to
allow RIP to send unicast updates to the specified neighbor while
blocking broadcast updates on the specified interface. You can
configure multiple neighbors.
Note:
The ip keyword is required. All other keywords are optional.
Example
This example shows how to specify that the router at
192.168.21.20 is a neighbor.
config router rip config neighbor
edit 1
set ip 192.168.21.20
end
end
Config Network
Use this subcommand to identify the networks for which to send
and receive RIP updates. If a network is not specified, interfaces
in that network will not be advertised in RIP updates.
Note:
The prefix keyword is optional.
Example
Use the following command to enable RIP for the interfaces
attached to networks specified by the IP address 10.0.0.0 and
the netmask 255.255.255.0.
config router rip
config network
edit 2
set prefix 10.0.0.0 255.255.255.0
end
end
Config Offset-list
Use this subcommand to add the specified offset to the metric
(hop count) of a route from the offset list.
Note:
The access-list, direction, and offset keywords are required. All
other keywords are optional.
Example
This example shows how to configure and enable offset list
number 5 that adds a metric of 3 to incoming routes that match
the access list named acc_list1 on the external interface.
config router rip config offset-list
edit 5
set access-list acc_list1
set direction in
set interface external
set offset 3
Config Redistribute
Use this subcommand to redistribute routes learned from OSPF,
BGP, static routes, or a direct connection to the destination
network.
The RIP redistribution table contains four static entries. You
cannot add entries to the table. The entries are defined as
follows:
bgp—Redistribute routes learned from BGP.
connected—Redistribute routes learned from a direct
connection to the destination network.
ospf—Redistribute routes learned from OSPF.
static—Redistribute the static routes defined in the ZXSEC US
unit routing table.
When you enter the subcommand, end the command with one of
the four static entry names (that is, config redistribute {bgp |
connected | ospf | static}).
Note:
All keywords are optional.
Example
This example shows how to enable route redistribution from
OSPF, using a metric of 3 and a route map named rtmp2.
config router rip
config redistribute ospf
set metric 3
set routemap rtmp2
set status enable
end
Related topics
router access-list
router key-chain
router prefix-list
router route-map
get router info protocols
get router info rip
get router info routing-table
Route-map
Use this command to add, edit, or delete route maps. To use the
command to limit the number of received or advertised BGP
route and routing updates using route maps, see “Using route
maps with BGP”.
Route maps provide a way for the ZXSEC US unit to evaluate
optimum routes for forwarding packets or suppressing the
routing of packets to particular destinations. Compared to access
lists, route maps support enhanced packet-matching criteria. In
addition, route maps can be configured to permit or deny the
addition of routes to the ZXSEC US unit routing table and make
changes to routing information dynamically as defined through
route-map rules.
The ZXSEC US unit compares the rules in a route map to the
attributes of a route. The rules are examined in ascending order
until one or more of the rules in the route map are found to
match one or more of the route attributes:
When a single matching match-* rule is found, changes to
the routing information are made as defined through the
rule’s set-ip-nexthop, set-metric, set-metric-type, and/or
set- tag settings.
If no matching rule is found, no changes are made to the
routing information.
When more than one match-* rule is defined, all of the
defined match-* rules must evaluate to TRUE or the routing
information is not changed.
If no match-* rules are defined, the ZXSEC US unit makes
changes to the routing information only when all of the
Note:
Any keywords and rules that to not appear here can be found in
the BGP route-map section. See“Using route maps with BGP”.
Syntax
config router route-map
edit <route_map_name>
set comments <string>
config rule
edit <route_map_rule_id>
set action {deny | permit}
set match-interface <name_str>
set match-ip-address <access/prefix-listname_str>
set match-ip-nexthop <access/prefix-listname_str>
set match-metric <metric_integer>
set match-route-type {1 | 2}
set match-tag <tag_integer>
set set-ip-nexthop <address_ipv4>
set set-metric <metric_integer>
set set-metric-type {1 | 2}
set set-tag <tag_integer>
end
end
Note:
All keywords are optional.
Example
This example shows how to add a route map list named rtmp2
with two rules. The first rule denies routes that match the IP
addresses in an access list named acc_list2. The second rule
permits routes that match a metric of 2 and changes the metric
to 4.
config router route-map
edit rtmp2
config rule edit 1
set match-ip-address acc_list2
set action deny next
edit 2
set match-metric 2 set action permit set set-metric 4
end
end
Note:
When you specify a route map for the dampening-route-map
value through the config router bgp command (see “dampening-
route-map <routemap-name_str>”), the ZXSEC US unit ignores
global dampening settings. You cannot set global dampening
settings for the ZXSEC US unit and then override those values
through a route map.
Syntax
config router route-map
edit <route_map_name>
set comments <string>
config rule
edit <route_map_rule_id>
set match-as-path <aspath-list-name_str>
set match-community <community-list-name_str>
set match-community-exact {enable | disable}
set match-origin {egp | igp | incomplete | none}
set set-aggregator-as <id_integer>
set set-aggregator-ip <address_ipv4>
set set-aspath <id_integer> <id_integer> <id_integer> ...
Note:
All keywords are optional.
Example
This example shows how to create a route map named
BGP_rtmp2. The route map contains two rules. The first rule
permits operations on routes that match the IP addresses in an
access list named acc_list2. The second rule permits operations
on routes according to a community list named com_list3.
config router route-map
edit BGP_rtmp2
set comments “example BGP route map”
config rule
edit 1
set match-ip-address acc_list2
set action permit next
edit 2
set match-community com_list3
set action permit
end
end
Related topics
router access-list
router prefix-list
router rip
router aspath-list
router bgp
router community-list
router key-chain
Static
Use this command to add, edit, or delete static routes for IPv4
traffic. For IPv6 traffic, use the static6 command. You add static
routes to control traffic exiting the ZXSEC US unit. You configure
routes by specifying destination IP addresses and network
masks and adding gateways for these destination addresses.
Gateways are the next-hop routers to which traffic that matches
the destination addresses in the route are forwarded.
You can adjust the administrative distance of a route to indicate
preference when more than one route to the same destination is
available. The lower the administrative distance, the greater the
preferability of the route. If the routing table contains several
entries that point to the same destination (the entries may have
different gateways or interface associations), the ZXSEC US unit
compares the administrative distances of those entries, selects
the entries having the lowest distances, and installs them as
routes in the ZXSEC US unit forwarding table. Any ties are
resolved by comparing the routes’ priority, with lowest priority
being preferred. As a result, the ZXSEC US unit forwarding table
only contains routes having the lowest distances to every
possible destination.If both administrative distance and priority
are both tied for two or more routes, an equal cost multi-path
(ECMP) situation occurs. In this case, the egress index for the
routes will be used to determine the selected route.
After the ZXSEC US unit selects static routes for the forwarding
table based on their administrative distances, the sequence
numbers of those routes determines routing priority. When two
routes to the same destination exist in the forwarding table, the
ZXSEC US unit selects the route having the lowest sequence
number.
Syntax
config router static
edit <sequence_number>
set blackhole {enable | disable}
set device <interface_name>
set distance <distance>
set dst <destination-address_ipv4mask>
set dynamic-gateway {enable | disable}
set gateway <gateway-address_ipv4>
set priority <integer>
end
Note:
The dst and gateway keywords are required when blackhole is
disabled. When blackhole is enabled, the dst keyword is required.
All other keywords are optional.
Example
This example shows how to add a static route that has the
sequence number 2.
config router static
edit 2
set dev internal
set dst 192.168.22.0 255.255.255.0
set gateway 192.168.22.44
end
This example shows how to add a static route for a dynamic
modem interface with a administrative distance of 1 and a
priority of 1. These settings makes this the preferred route.
config route static
edit 3
set dev modem
set dynamic-gateway enable
set dst 10.0.0.7 255.255.255.0
set distance 1
set priority 1
end
Related topics
system interface
Static6
Use this command to add, edit, or delete static routes for IPv6
traffic. You add static routes to specify the destination of traffic
exiting the ZXSEC US unit. You configure routes by adding
destination IP addresses and network masks and adding
gateways for these destination addresses. The gateways are the
next-hop routers to which traffic that matches the destination
addresses in the route are forwarded.
Note:
You can configure static routes for IPv6 traffic on ZXSEC US
units that run in NAT/Route mode.
Syntax
config router static6
edit <sequence_number>
set device <interface_name>
set dst <destination-address_ipv6mask>
set gateway <gateway-address_ipv6>
end
Note:
The device, dst, and gateway keywords are all required.
Example
This example shows how to add an IPv6 static route that has the
sequence number 2.
config router static6
edit 2
set dev internal
set dst 2001:DB8::/32
set gateway 2001:DB8:0:CD30:123:4567:89AB:CDEF
end
Related topics
system interface
get router info routing-table
Chapter 12
Spamfilter
Overview
Use spamfilter commands to create a banned word list, configure filters
based on email addresses, ip addresses, and MIME headers, and to
configure the Usservice-Antispam service.
This chapter contains the following sections:
BWord
Emailbwl
USshield
Ipbwl
Iptrust
Mheader
Options
DNSBL
BWord
Use this command to add or edit and configure options for the spam filter
banned word list. The ZXSEC US spam filters are applied in the following
order:
For SMTP
1. IP address BWL check - Last hop IP
2. DNSBL & ORDBL check, IP address Usservice check, HELO DNS lookup
3. E-mail address BWL check
4. MIME headers check
5. IP address BWL check (for IPs extracted from “Received” headers)
6. Return e-mail DNS check, Usservice Antispam check (for IPs extracted
from “Received” headers, and URLs in email content)
7. Banned word check
For POP3 and IMAP
1. E-mail address BWL check
2. MIME headers check, IP BWL check
3. Return e-mail DNS check, Usservice Antispam check, DNSBL & ORDBL
check
4. Banned word check
For SMTP, POP3, and IMAP
Control spam by blocking email messages containing specific words or
patterns. If enabled in the protection profile, the ZXSEC US unit searches
for words or patterns in email messages. If matches are found, values
assigned to the words are totalled. If a user-defined threshold value is
exceeded, the message is marked as spam. If no match is found, the
email message is passed along to the next filter.
Use Perl regular expressions or wildcards to add banned word patterns to
the list. See “Using Perl regular expressions”. Add one or more banned
words to sort email containing those words in the email subject, body, or
both. Words can be marked as spam or clear. Banned words can be one
word or a phrase up to 127 characters long.
If a single word is entered, the ZXSEC US unit blocks all email that contain
that word. If a phrase is entered, the ZXSEC US unit blocks all email
containing the exact phrase. To block any word in a phrase, use Perl
regular expressions.
Note:
Perl regular expression patterns are case sensitive for Spam Filter banned
words. To make a word or phrase case insensitive, use the regular
expression /i. For example, /bad language/i blocks all instances of bad
language regardless of case. Wildcard patterns are not case sensitive.
Syntax
config spamfilter bword
edit <banned_word_list_integer>
set name <banned_word_list>
set comment <banned_word_list_comment>
config entries
edit <banned_word_integer>
set action {clear | spam}
set language {french | japanese | korean | simch | thai | trach | western}
set pattern <banned_word_str>
set pattern-type {regexp | wildcard}
set score <integer_value>
Related topics
spamfilter emailbwl
spamfilter USshield
spamfilter ipbwl
spamfilter iptrust
spamfilter mheader
spamfilter options
spamfilter
DNSBL
Emailbwl
Use this command to filter email based on the sender’s email address or
address pattern. The ZXSEC US spam filters are applied in the following
order:
For SMTP
1. IP address BWL check - Last hop IP
2. DNSBL & ORDBL check, IP address Usservice check, HELO DNS lookup
3. E-mail address BWL check
4. MIME headers check
5. IP address BWL check (for IPs extracted from “Received” headers)
6. Return e-mail DNS check, Usservice Antispam check (for IPs extracted
from “Received” headers, and URLs in email content)
7. Banned word check
For POP3 and IMAP
1. E-mail address BWL check
2. MIME headers check, IP BWL check
3. Return e-mail DNS check, Usservice Antispam check, DNSBL & ORDBL
check
4. Banned word check
For SMTP, POP3, and IMAP
The ZXSEC US unit uses the email address list to filter incoming email. The
ZXSEC US unit compares the email address or domain of the sender to the
list in sequence. If a match is found, the corresponding action is taken. If
no match is found, the email is passed on to the next spam filter.
The ZXSEC US unit can filter email from specific senders or all email from
a domain (such as example.net). Each email address can be marked as
clear or spam.
Use Perl regular expressions or wildcards to add email address patterns to
the list. See “Using Perl regular expressions”.
Syntax
config spamfilter emailbwl
edit <emailbwl_list_integer>
set name <emailbwl_list>
set comment <emailbwl_list_comment>
config entries
edit <email_address_integer>
set action {clear | spam}
set email-pattern <email_address_str>
set pattern-type {regexp | wildcard}
set status {enable | disable}
end
Related topics
spamfilter bword
spamfilter USshield
spamfilter ipbwl
spamfilter iptrust
spamfilter mheader
spamfilter options
spamfilter DNSBL
USshield
Use this command to configure the settings for the Usservice-Antispam
Service. The ZXSEC US spam filters are applied in the following order:
For SMTP
1. IP address BWL check - Last hop IP
2. DNSBL & ORDBL check, IP address Usservice check, HELO DNS lookup
3. E-mail address BWL check
4. MIME headers check
5. IP address BWL check (for IPs extracted from “Received” headers)
6. Return e-mail DNS check, Usservice Antispam check (for IPs extracted
from “Received” headers, and URLs in email content)
7. Banned word check
For POP3 and IMAP
1. E-mail address BWL check
2. MIME headers check, IP BWL check
3. Return e-mail DNS check, Usservice Antispam check, DNSBL & ORDBL
check
4. Banned word check
For SMTP, POP3, and IMAP
Usservice-Antispam Service is an antispam system from USnet that
includes an IP address black list, a URL black list, and spam filtering tools.
The IP address black list contains IP addresses of email servers known to
be used to generate Spam. The URL black list contains found in Spam
email.
Usservice-Antispam Service compiles the IP address and URL list from
email captured by spam probes located around the world. Spam probes
are email addresses purposely configured to attract spam and identify
known spam sources to create the antispam IP address and URL list.
Usservice- Antispam Service combines IP address and URL checks with
other spam filter techniques in a two- pass process.
On the first pass, if spamfsip is selected in the protection profile,
Usservice-Antispam Service extracts the SMTP mail server source address
and sends the IP address to a Usservice-Antispam Service server to see if
this IP address matches the list of known spammers. If spamfsurl is
selected in the protection profile, Usservice-Antispam Service checks the
body of email messages to extract any URL links. These URL links will be
sent to a Usservice-Antispam Service server to see if any of them is listed.
Typically Spam messages contain URL links to advertisements (also called
spamvertizing).
Related topics
spamfilter bword
spamfilter emailbwl
spamfilter ipbwl
spamfilter iptrust
spamfilter mheader
spamfilter options
spamfilter DNSBL
IPBWL
Use this command to filter email based on the IP or subnet address. The
ZXSEC US spam filters are generally applied in the following order:
For SMTP
1. IP address BWL check - Last hop IP
2. DNSBL & ORDBL check, IP address Usservice check, HELO DNS lookup
3. E-mail address BWL check
4. MIME headers check
5. IP address BWL check (for IPs extracted from “Received” headers)
6. Return e-mail DNS check, Usservice Antispam check (for IPs extracted
from “Received” headers, and URLs in email content)
7. Banned word check
For POP3 and IMAP
1. E-mail address BWL check
2. MIME headers check, IP BWL check
3. Return e-mail DNS check, Usservice Antispam check, DNSBL & ORDBL
check
4. Banned word check
For SMTP, POP3, and IMAP
The ZXSEC US unit uses the IP address list to filter incoming email. The
ZXSEC US unit compares the IP address of the sender to the list in
sequence. If a match is found, the corresponding protection profile action
is taken. If no match is found, the email is passed on to the next spam
filter.
Enter an IP address and mask in one of two formats:
x.x.x.x/x.x.x.x, for example 192.168.10.23/255.255.255.0
x.x.x.x/x, for example 192.168.10.23/24
Configure the ZXSEC US unit to filter email from specific IP addresses.
Mark each IP address as clear, spam, or reject. Filter single IP addresses,
or a range of addresses at the network level by configuring an address and
mask.
Syntax
config spamfilter ipbwl
edit <ipbwl_list_integer>
set name <ipbwl_list>
set comment <ipbwl_list_comment>
config entries
edit <address_ipv4_integer>
set action {clear | reject | spam}
set ip/subnet
{<address_ipv4> | address_ipv4>/<address_ipv4mask>}
set status {enable | disable}
end
Related topics
spamfilter bword
spamfilter emailbwl
spamfilter USshield
spamfilter iptrust
spamfilter mheader
spamfilter options
spamfilter DNSBL
IPTrust
Use this command to add an entry to a list of trusted IP addresses.
If the ZXSEC US unit sits behind a company’s Mail Transfer Units, it may
be unnecessary to check email IP addresses because they are internal and
trusted. The only IP addresses that need to be checked are those from
outside of the company. In some cases, external IP addresses may be
added to the list if it is known that they are not sources of spam.
Syntax
config spamfilter iptrust
edit <iptrust_list_integer>
set name <iptrust_list>
set comment <iptrust_list_comment>
config entries
edit <address_integer>
set ip/subnet {<address_ipv4> |
<address_ipv4>/<address_ipv4mask>}
set status {enable | disable}
end
Related topics
spamfilter bword
spamfilter emailbwl
spamfilter USshield
spamfilter ipbwl
spamfilter mheader
spamfilter options
spamfilter DNSBL
MHeader
Use this command to configure email filtering based on the MIME header.
MIME header settings are configured with this command but MIME header
filtering is enabled within each protection profile.
The ZXSEC US spam filters are applied in the following order:
For SMTP
1. IP address BWL check - Last hop IP
2. DNSBL & ORDBL check, IP address Usservice check, HELO DNS lookup
3. E-mail address BWL check
4. MIME headers check
5. IP address BWL check (for IPs extracted from “Received” headers)
6. Return e-mail DNS check, Usservice Antispam check (for IPs extracted
from “Received” headers, and URLs in email content)
7. Banned word check
For POP3 and IMAP
1. E-mail address BWL check
2. MIME headers check, IP BWL check
3. Return e-mail DNS check, Usservice Antispam check, DNSBL & ORDBL
check
4. Banned word check
For SMTP, POP3, and IMAP
The ZXSEC US unit compares the MIME header key-value pair of incoming
email to the list pair in sequence. If a match is found, the corresponding
action is taken. If no match is found, the email is passed on to the next
spam filter.
MIME (Multipurpose Internet Mail Extensions) headers are added to email
to describe content type and content encoding, such as the type of text in
the email body or the program that generated the email. Some examples
of MIME headers include:
X-mailer: outgluck
X-Distribution: bulk
Content_Type: text/html
Content_Type: image/jpg
The first part of the MIME header is called the header key, or just header.
The second part is called the value. Spammers often insert comments into
header values or leave them blank. These malformed headers can fool
some spam and virus filters.
Use the MIME headers list to mark email from certain bulk mail programs
or with certain types of content that are common in spam messages. Mark
the email as spam or clear for each header configured.
Note:
MIME header entries are case sensitive.
Syntax
config spamfilter mheader
edit <mime_list_integer>
set name <mime_list>
set comment <mime_list_comment>
config entries
edit <mime_integer>
set action {clear | spam}
set fieldbody <mime_str>
set fieldname <mime_str>
set pattern-type {regexp | wildcard}
set status {enable | disable}
end
end
Related topics
spamfilter bword
spamfilter USshield
spamfilter USshield
spamfilter ipbwl
spamfilter iptrust
spamfilter options
spamfilter DNSBL
Options
Use this command to set the spamfilter dns query timeout.
Syntax
config spamfilter options
set dns-timeout <timeout_integer>
end
Example
This example shows how to set the dns timeout.
config spamfilter options
set dns-timeout 15
end
Related topics
spamfilter bword
spamfilter emailbwl
spamfilter USshield
spamfilter ipbwl
spamfilter iptrust
spamfilter mheader
spamfilter DNSBL
DNSBL
Use this command to configure email filtering using DNS-based Blackhole
List (DNSBL) or Open Relay Database List (ORDBL) servers. DSNBL and
ORDBL settings are configured with this command but DSNBL and ORDBL
filtering is enabled within each protection profile.
The ZXSEC US spam filters are generally applied in the following order:
For SMTP
1 IP address BWL check - Last hop IP
2 DNSBL & ORDBL check, IP address Usservice check, HELO DNS
lookup
3 E-mail address BWL check
4 MIME headers check
5 IP address BWL check (for IPs extracted from “Received” headers)
6 Return e-mail DNS check, Usservice Antispam check (for IPs
extracted from “Received” headers, and URLs in email content)
7 Banned word check
For POP3 and IMAP
1 E-mail address BWL check
2 MIME headers check, IP BWL check
3 Return e-mail DNS check, Usservice Antispam check, DNSBL &
ORDBL check
4 Banned word check
For SMTP, POP3, and IMAP
The ZXSEC US unit compares the IP address or domain name of the
sender to any database lists configured in sequence. If a match is found,
the corresponding action is taken. If no match is found, the email is
passed on to the next spam filter.
Some spammers use unsecured third party SMTP servers to send
unsolicited bulk email. Using DNSBLs and ORDBLs is an effective way to
tag or reject spam as it enters the network. These lists act as domain
name servers that match the domain of incoming email to a list of IP
addresses known to send spam or allow spam to pass through.
There are several free and subscription servers available that provide
reliable access to continually updated DNSBLs and ORDBLs. Please check
with the service being used to confirm the correct domain name for
connecting to the server.
Note:
Because the ZXSEC US unit uses the server domain name to connect to
the DNSBL or ORDBL server, it must be able to look up this name on the
DNS server. For information on configuring DNS, see “system dns”.
Syntax
config spamfilter DNSBL
edit <DNSBL_list_integer>
set name <DNSBL_list>
set comment <DNSBL_list_comment>
config entries
edit <server_integer>
set action {reject | spam}
set server <name_str>
set status {enable | disable}
end
Related topics
spamfilter bword
spamfilter emailbwl
spamfilter USshield
spamfilter ipbwl
System
Overview
Use system commands to configure options related to the overall
operation of the ZXSEC US unit, including:
Administrative access
Automatic updating of antivirus and attack definitions
High availability (HA)
Network interfaces
Replacement messages
VLANs and virtual domains
This chapter contains the following sections:
accprofile
admin
alertemail
arp-table
auto-install
autoupdate
clientoverride
autoupdate
override
autoupdate
push-update
autoupdate
schedule
autoupdate
tunneling
aux
bug-report console
dhcp reserved-address
dhcp server dns
fips-cc
Usla, Usla2, Usla3
gi-gk (US Carrier)
global
gre-tunnel ha interface
ipv6-tunnel
mac-address-table management-tunnel
modem
npu
proxy-arp
replacemsg
admin
replacemsg
alertmail
replacemsg
auth
replacemsg
Usservice-wf
replacemsg
ftp
replacemsg
http
replacemsg
im
replacemsg
mail
replacemsg mm1 (US Carrier)
replacemsg mm3 (US Carrier)
replacemsg mm4 (US Carrier)
replacemsg mm7 (US Carrier)
replacemsg nntp
replacemsg spam
replacemsg sslvpn
replacemsg-group (US Carrier)
replacemsg-image (US Carrier)
session-helper
session-sync
session-ttl
settings
snmp community
snmp sysinfo
switch-interface
tos-based-priority
vdom-link
wireless mac-filter
wireless settings
zone
Accprofile
Use this command to add access profiles that control
administrator access to ZXSEC US features. Each ZXSEC US
administrator account must include an access profile. You can
create access profiles that deny access, allow read only, or allow
both read and write access to ZXSEC US features.
You cannot delete or modify the super_admin access profile, but
you can use the super_admin profile with more than one
administrator account.
Syntax
config system accprofile
edit <profile-name>
set <access-group> <access-level>
config fwgrp-permission
set address {none | read | read-write}
set others {none | read | read-write}
set policy {none | read | read-write}
set profile {none | read | read-write}
set schedule {none | read | read-write}
set service {none | read | read-write}
end
config loggrp-permission
set config {none | read | read-write}
set data-access {none | read | read-write}
end
end
routegrp router
configuration
spamgrp spamfilter
configuration
sysgrp system
configurati
on except
accprofile,
admin and
autoupdat
e
updategrp Usservice
antivirus
and IPS
updates,
manual
and
automati
c
vpngrp VPN
configuration
webgrp webfilter
configuration
<access-level> Enter the level of administrator none
access to this feature:
custom configures
custom access
for fwgrp or
loggrp access
selections only
none no access
read read-only
access
read-write read and write
access
config fwgrp-permission keywords. Available if fwgrp is set to
custom.
address Enter the level of administrator none
{none | read | access to firewall addresses.
read-write}
others Enter the level of administrator none
{none | read | access to virtual IP
Examples
Use the following commands to add a new access profile named
policy_profile that allows read and write access to firewall
policies and that denies access to all other ZXSEC US features.
An administrator account with this access profile can view and
edit firewall policies, but cannot view or change any other ZXSEC
US settings or features.
config system accprofile
edit policy_profile
set fwgrp read-write
end
Use the following commands to add a new access profile named
policy_profile_cu that allows customized read and write access
to firewall policies and that denies access to all other ZXSEC US
features. An administrator account with this access profile can
view and edit the selected custom firewall permissions (address,
policy, and schedule), but cannot view or change any other
ZXSEC US settings or features.
config system accprofile
edit policy_profile_cu
set fwgrp custom
config fwgrp-permission
set address read-write
Admin
Use this command to add, edit, and delete administrator
accounts. Administrators can control what data modules appear
in the ZXSEC US unit system dashboard by using the config
system admin command. Administrators must have read and
write privileges to make dashboard GUI modifications.
Use the default admin account or an account with system
configuration read and write privileges to add new administrator
accounts and control their permission levels. Each administrator
account except the default admin must include an access profile.
You cannot delete the default super admin account or change
the access profile (super_admin). In addition, there is also an
access profile that allows read-only super admin privileges,
super_admin_readonly. The super_admin_readonly profile
cannot be deleted or changed, similar to the super_admin profile.
This read-only super-admin may be used in a situation where it
is necessary to troubleshoot a customer configuration without
making changes.
You can authenticate administrators using a password stored on
the ZXSEC US unit or you can use a RADIUS server to perform
authentication. When you use RADIUS authentication, you can
authenticate specific administrators or you can allow any
account on the RADIUS server to access the ZXSEC US unit as
an administrator.
Note:
For users with super_admin access profile, you can reset the
password in the CLI.
For a user ITAdmin with the access profile super_admin,
to set the password to 123456:
config sys admin
edit ITAdmin
set password 123456
end
Note:
You cannot change the management VDOM if any administrators
are using RADIUS authentication.
Syntax
config system admin
edit <name_str>
set accprofile <profile-name>
set comments <comments_string>
set password <admin_password>
set peer-auth <peer_auth>
set peer-group <peer-grp>
set remote-auth {enable | disable}
set remote-group <name>
set schedule <schedule-name>
set ssh-public-key1 "<key-type> <key-value>"
set ssh-public-key2 "<key-type> <key-value>"
set ssh-public-key3 "<key-type> <key-value>"
set trusthost1 <address_ipv4mask>
set trusthost2 <address_ipv4mask>
set trusthost3 <address_ipv4mask>
set vdom <vdom_name> setsystem wildcard {enable | disable}
config dashboard
edit moduleid <module_name>
Example
Use the following commands to add a new administrator account
named new_admin with the password set to p8ssw0rd and that
includes an access profile named policy_profile. It is accessible
on the main_office VDOM. Administrators that log in to this
account will have administrator access to the ZXSEC US unit
from any IP address. The dashboard setting alert > show-
system-restart is enabled and displays in column 2 of the US
GUI.
config system admin
edit new_admin
set password p8ssw0rd
set accprofile policy_profile
set vdom main_office
config dashboard
edit alert
set column 2
set status open
show-system-restart enable end
end
end
Related topics
system accprofile
Alertemail
Use this command to configure the ZXSEC US unit to access an
SMTP server to send alert emails. This command is global in
scope.
To configure alertemail settings you must first configure the
server, and enable authenticate. Then you will be able to see all
the keywords.
Note:
You must configure the server setting under config system
alertemail before the commands under config alertemail become
accessible. For more information on config alertemail, see
“alertemail”.
Syntax
config system alertemail
set authenticate {disable | enable}
set password <password-str>
set server {<name-str> | <address-ipv4>}
set username <username-str>
end
Examples
This example shows how to configure the ZXSEC US unit to send
alert emails using the SMTP server smtp.ourcompany.com. The
order of the keywords is important. The server must be defined
first. Then authentication needs to be next. The ZXSEC US unit
uses the user name admin2 and the password h8rdt0g3uss to
connect to the SMTP server.
config system alertemail
set server smtp.ourcompany.com
set authenticate enable
set password h8rdt0g3uss
set username admin2
end
ARP-table
Use this command to manually configure the ARP table entries
on the ZXSEC US unit. You can only access the arp-table values
from the CLI.
This command is not available when VDOMs are enabled or in TP
mode.
Syntax
config system arp-table
edit <table_value>
set interface <port>
set ip <address-ipv4>
set mac <mac_address>
end
Examples
This example adds an entry to the arp-table with a MAC address
of 00-09-0f-69-00-7c and an IP address of 172.20.120.161 on
the port2 interface.
config system arp-table
edit 3
set interface port2
set ip 172.20.120.161
set mac 00:09:0f:69:00:7c
end
Related topics
get system arp
Auto-install
Use this command to configure automatic installation of
firmware and system configuration from a USB disk when the
ZXSEC US unit restarts. This command is available only on units
that have a USB disk connection.
If you set both configuration and firmware image update, both
occur on the same reboot. The ZXSEC US unit will not reload a
firmware or configuration file that is already loaded.
USUSB and generic USB disks are supported. However, the USB
disk must be formatted as a FAT16 drive. No other partition type
is supported.
To format your USB Disk when its connected to your ZXSEC US
unit, at the CLI prompt type “exe usb- disk format”.
To format your USB disk when it is connected to a Windows
system, at the command prompt type “format <drive_letter>:
/FS:FAT /V:<drive_label>” where <drive_letter> is the letter of
the connected USB drive you want to format, and <drive_label>
is the name you want to give the USB disk volume for
identification.
Note:
This command is available only when a USB key is installed on
the ZXSEC US unit. Formatting your USB disk will delete all
information on your USB disk.
Syntax
config system auto-install
set auto-install-config {disable | enable}
set auto-install-image {disable | enable}
set default-config-file
set default-image-file
end
Autoupdate Clientoverride
Use this command to receive updates on a different interface
than the interface connected to the Usservice Distribution
Network (UDN). This command changes the source IP address of
update requests to the Usservice server, causing it to send the
update to the modified source address.
This is useful if your company uses an internal updates server
instead of UDN.
Syntax
config system autoupdate clientoverride
set address <address_ipv4>
set status {enable | disable}
end
Example
This example shows how to add a push update client IP address
192.0.2.45 which is on the port4 interface.
config system autoupdate clientoverride
set address 192.0.2.45
set status enable
end
Related topics
system autoupdate override
system autoupdate push-update
system autoupdate schedule
system autoupdate tunneling
execute update-av
Autoupdate Override
Use this command to specify an override UDS server.
If you cannot connect to the Usservice Distribution Network
(UDN) or if your organization provides updates using their own
Usservice server, you can specify an override UDS server so that
the ZXSEC US unit connects to this server instead of the UDN.
Note:
If you are unable to connect to the UDS server, even after
specifying an override server, it is possible your ISP is blocking
the lower TCP and UDP ports for security reasons. Contact your
ISP to make sure they unblock TCP and UDP ports 1025 to 1035
to enable UDS server traffic.
Syntax
config system autoupdate override
set address <UDS_address>
set status {enable | disable}
end
Example
This example shows how to add and enable your company’s own
UDS override server with an IP address of 192.168.87.45.
config system autoupdate override
set address 192.168.87.45
set status enable
end
Related topics
system autoupdate push-update
system autoupdate schedule
system autoupdate tunneling
execute update-av
execute update-ips
Autoupdate Push-update
Use this command to configure push updates. The Usservice
Distribution Network (UDN) can push updates to ZXSEC US units
to provide the fastest possible response to critical situations
such as software exploits or viruses. You must register the
ZXSEC US unit before it can receive push updates.
When you configure a ZXSEC US unit to allow push updates, the
ZXSEC US unit sends a SETUP message to the UDN. The next
time an update is released, the UDN notifies all ZXSEC US units
that are configured for push updates that a new update is
available. Within 60 seconds of receiving a push notification, the
ZXSEC US unit requests an update from the UDN.
Using this command you can enable or disable push updates.
You can also configure push IP address and port overrides. If the
UDN must connect to the ZXSEC US unit through a NAT device,
you must configure port forwarding on the NAT device and add
the port forwarding information to the push update override
configuration.
Note:
You cannot receive push updates through a NAT device if the
external IP address of the NAT device is dynamic (for example,
set using PPPoE or DHCP).
Syntax
config system autoupdate push-update
set address <push_ipv4>
set override {enable | disable}
set port <UDN_port>
set status {enable | disable}
end
Example
This example shows how to enable push updates on port 9993.
config system autoupdate push-update
set status enable
set port 9993
end
Related topics
system autoupdate override
system autoupdate schedule
system autoupdate tunneling
execute update-av
execute update-ips
Autoupdate Schedule
Use this command to enable or disable scheduled UDN updates
at regular intervals throughout the day, once a day, or once a
week.
To have your ZXSEC US unit to update at a random time during
a particular hour, select a time that includes 60 minutes as this
will choose a random time during that hour for the scheduled
update.
Syntax
config system autoupdate schedule
set day <day_of_week>
set frequency {every | daily | weekly}
set status {enable | disable}
set time <hh:mm>
end
Example
This example shows how to configure the ZXSEC US unit to
check the Usservice Distribution Network (UDN) for updates
once a day at 3:00 in the morning.
config system autoupdate schedule
set frequency daily
set time 03:00
set status enable
end
This example is the same as the above example but it will check
for updates once a day at sometime between 3:00 and 4:00 in
the morning.
config system autoupdate schedule
Autoupdate Tunneling
Use this command to configure the ZXSEC US unit to use a
proxy server to connect to the Usservice Distribution Network
(UDN). To use the proxy server, you must enable tunneling and
add the IP address and port required to connect to the proxy
server. If the proxy server requires authentication, add the user
name and password required to connect to the proxy server.
The ZXSEC US unit connects to the proxy server using the HTTP
CONNECT method, as described in RFC 2616. The ZXSEC US
unit sends a HTTP CONNECT request to the proxy server
(optionally with authentication information) specifying the IP
address and port required to connect to the UDN. The
proxy server establishes the connection to the UDN and passes
information between the ZXSEC US unit and the UDN.
The CONNECT method is used mostly for tunneling SSL traffic.
Some proxy servers do not allow CONNECT to connect to any
port; proxy servers restrict the allowed ports to the well known
ports for HTTPS and perhaps some other similar services.
Because ZXSEC US autoupdates use HTTPS on port 8890 to
connect to the UDN, your proxy server might have to be
configured to allow connections on this port.
Syntax
config system autoupdate tunneling
set address <proxy_address>
set password <password>
set port <proxy_port>
set status {enable | disable}
set username <name>
end
Example
This example shows how to enable tunneling where the ZXSEC
US unit must connect to a proxy server with IP address
67.35.50.34 that uses port 8080, requires the user id
proxy_user and the password proxy_pwd.
config system autoupdate tunneling
set address 67.35.50.34
set port 8080
set username proxy_user
set password proxy_pwd
set status enable
end
Related topics
system autoupdate override
system autoupdate push-update
system autoupdate schedule
Aux
Use this command to configure the AUX port on 2010, 2010A,
and 2350 models for remote console connection. You would use
a modem to remotely connect to a console session on the ZXSEC
US unit.
The main difference between the standard console port and the
aux port is that the standard console port is for local serial
console connections only - it cannot accept a modem connection
to establish a remote console connection. The aux console port
allows you to establish a local connection, but it has some
limitations the standard console port does not have.
The AUX port will not display the booting messages that the
standard console connection displays.
The AUX port will send out modem initializing strings (AT
strings) that will appear on an aux console session at the
start.
Syntax
config system aux
set baudrate <baudrate>
end
<baudrate> is the speed of the connection. It can be set to one
of the following: 9600, 19200, 38400, 57600, or 115200. The
default is 9600.
Ensure devices on both ends of the connection are set to the
same baudrate.
Related topics
system console
Bug-report
Use this command to configure a custom email relay for sending
problem reports to USnet customer support.
Syntax
config system bug-report
set auth {no | yes}
set mailto <email_address>
set password <password>
set server <servername>
set username <name>
set username-smtp <account_name>
end
Example
This example shows how to configure the ZXSEC US unit to send
bug report email from the ourmailserver.com email server to
bug_report@ourcompany.com using the User1 account. The
email server requires authentication.
config system bug-report
set auth yes
set mailto bug_report@ourcompany.com
set password 123456
set server ourmailserver.com
set username OurAdmin
end
Related topics
system dns
Console
Use this command to set the console command mode, the
number of lines displayed by the console, and the baud rate.
ZXSEC US2010 and 2010A models have an AUX port that can be
used for remote console connections using a modem. This port
on these models is configured with the system aux command,
see “aux”.
Syntax
config system console
set baudrate <speed>
set mode {batch | line}
set output {standard | more}
end
Example
This example shows how to set the baudrate to 38400 and set
the output style to more so it will pause after each screen full of
information.
config system console
set baudrate 38400 set output more
end
Related topics
system aux
DHCP Reserved-address
Use this command to reserve an IP address for a particular client
identified by its device MAC address and type of connection. The
DHCP server then always assigns the reserved IP address to the
client. The number of reserved addresses that you can define
ranges from 10 to 200 depending on the ZXSEC US model.
Note:
For this configuration to take effect, you must configure at least
one DHCP server using the config system dhcp server command,
see “dhcp server”.
Syntax
config system dhcp reserved-address
edit <name_str>
set ip <address_ipv4>
set mac <address_hex>
Example
Use the following command to add a reserved address named
client_1 consisting of IP address 192.168.110.3 and MAC
address 00:09:0F:0A:01:BC for a regular ethernet connection.
config system dhcp reserved-address
edit client_1
set ip 192.168.110.3
set mac 00:09:0F:0A:01:BC
set type regular
end
Related topics
system dhcp server
system interface
DHCP Server
Use this command to add one or more DHCP servers for any
ZXSEC US interface. As a DHCP server, the interface dynamically
assigns IP addresses to hosts on a network connected to the
interface. On ZXSEC US models numbered 100 and below, you
can configure up to 8 DHCP servers. On all other models, you
can configure up to 32 DHCP servers.
You can add more than one DHCP server to a single interface to
be able to provide DHCP services to multiple networks. For more
information on configuring your network and ZXSEC US unit to
Example
DNS
Use this command to set the DNS server addresses. Several
ZXSEC US functions, including sending email alerts and URL
blocking, use DNS.
On models numbered 100 and lower, you can use this command
to configure DNS forwarding. The autosvr and fwdintf keywords
are only available on models numbered 100 and lower.
Syntax
config system dns
set autosvr {enable | disable}
set cache-notfound-responses {enable | disable}
set dns-cache-limit <integer>
set domain <domain_name>
set fwdintf <interface>
set primary <dns_ipv4>
set secondary <dns_ip4>
end
Example
This example shows how to set the primary ZXSEC US DNS
server IP address to 45.37.121.76 and the secondary ZXSEC US
DNS server IP address to 45.37.121.77.
config system dns
set primary 45.37.121.76
set secondary 45.37.121.77
end
FIPS-CC
Use this command to set the ZXSEC US unit into FIPS-CC mode.
Enable Federal Information Processing Standards-Common
Criteria (FIPS-CC) mode. This is an enhanced security mode that
is valid only on FIPS-CC-certified versions of the ZXSEC US
firmware.
When switching to FIPS-CC mode, you will be prompted to
confirm, and you will have to login.
Note:
When you enable FIPS-CC mode, all of the existing configuration
is lost.
For more information on FIPS-CC mode, see the FIPS-CC
technote on the Knowledge Center website.
Syntax
config system fips-cc
set
end
Example
This example shows how to set the ZXSEC US unit to
communicate with a US700 unit that is using a static IP address
of 192.20.120.100:
config system Usla
set address-mode static
set encrypt enable
set localid US700
set psksecret <128-character string>
set server 192.20.120.100
set status enable set ver-1 disable
set conn-timeout 60
end
Related topics
log Usla setting
Usservice
Use this command to configure communications with the
Usservice Distribution Network (UDN) for Usservice subscription
services such as:
Usservice Antivirus and IPS
Usservice Web Filtering and Antispam
Usservice Analysis and Management Service
By default, ZXSEC US units connect to the UDN using a set of
default connection settings. You can override these settings to
use IP addresses and port numbers other than the defaults.
Note:
If the ZXSEC US unit is unable to connect to the UDN, verify
connectivity on required ports. For a list of required ports, see
the USnet Knowledge Center article Traffic Types and TCP/UDP
Ports Used by USnet Products.
IP address and port number overrides for Usservice Analysis and
Management Service are configured separately from other
Usservice services. For details, see “system Usservice-log”. For
additional information on the Usservice Analysis and
Management Service, see the Usservice Analysis and
Management Service Administration Guide.
Syntax
config system Usservice
set antispam-status {enable | disable}
set antispam-cache {enable | disable}
set antispam-cache-ttl <ttl_int>
set antispam-cache-mpercent <ram_int>
set antispam-timeout <timeout_int>
set avquery-status {enable | disable}
set avquery-cache {enable | disable}
set avquery-cache-ttl <ttl_int>
set avquery-cache-mpercent <max_int>
set avquery-timeout <timeout_int>
set central-mgmt-auto-backup {enable | disable}
set central-mgmt-scheduled-config-restore {enable | disable}
set central-mgmt-scheduled-upgrade {enable | disable}
set central-mgmt-status {enable | disable}
set client-override-ip <ovrd_ipv4>
set client-override-status {enable | disable}
config serv-ovrd-list
This command is available only if srv-ovrd is enable.
<index_int> Enter the index number of a No default.
Usservice Antivirus and IPS server
override.
ip <ovrd_ipv4> Enter the IP address that will 0.0.0.0
override the default server IP
address. This may be the IP
address of a specific UDN server.
Example
This example shows how to configure the ZXSEC US unit for
remote administration by Usservice
Analysis and Management Service.
config system Usservice
set central-mgmt-status enable
set service-account-id ExampleCo
set central-mgmt-auto-backup enable
set central-mgmt-config-restore enable
set central-mgmt-scheduled-upgrade enable
end
config system management-tunnel
end
Related topics
get system dashboard
system Usservice-log
system management-tunnel
Usservice setting
Usservice-log
Use this command to override default ports and IP addresses to
which the ZXSEC US unit connects for Usservice Analysis and
Management Service.
Syntax
config system Usservice-log
set controller-ip <address_ipv4>
set controller-port <port_int>
set override-controller {enable | disable}
end
Example
This example shows how to override the default IP address and
port number to which the ZXSEC US unit connects when
communicating with the Usservice Analysis and Management
Service for features such as remote logging and reporting.
config system Usservice-log
set override-controller enable
set controller-ip 172.168.1.5
set controller-port 1234
end
Related topics
system Usservice
system management-tunnel
Usservice setting
Related topics
system interface
Global
Use this command to configure global settings that affect various
ZXSEC US systems and configurations.
Runtime-only config mode was introduced in US v3.0 MR2. This
mode allows you to try out commands that may put your ZXSEC
US unit into an unrecoverable state normally requiring a physical
reboot. In runtime-only config mode you can set a timeout so
after a period of no input activity the ZXSEC US unit will reboot
with the last saved configuration. Another option in runtime-only
configuration mode is to manually save your configuration
periodically to preserve your changes. For more information see
set CUS-save {automatic | manual | revert}, set CUS-revert-
timeout <seconds>, and execute CUS reload.
Switch mode is available on ZXSEC US120, 180 (Rev2.0 and
higher), and 350 (Rev2.0 and higher) models where the internal
interface is a four or six port switch. Normally the internal
Example
This example shows how to change to enable daylight savings
time.
config system global
set dst enable
end
Related topics
execute CUS reload
execute CUS save
GRE-tunnel
Use this command to configure the tunnel for a GRE interface. A
new interface of type “tunnel” with the same name is created
automatically as the local end of the tunnel. This command is
available only in NAT/Route mode.
To complete the configuration of a GRE tunnel, you need to:
configure a firewall policy to pass traffic from the local
private network to the tunnel interface
configure a static route to the private network at the remote
end of the tunnel using the GRE tunnel“device”
optionally, define the IP addresses for each end of the tunnel
to enable dynamic routing through the tunnel or to enable
pinging of each end of the tunnel for testing
Syntax
config system gre-tunnel edit <tunnel_name>
set interface <interface_name>
set local-gw <localgw_IP>
set remote-gw <remotegw_IP>
end
Example
In this example, a GRE tunnel is needed between two sites using
ZXSEC US units. Users on the 192.168.2.0/24 network at Site A
need to communicate with users on the 192.168.3.0/24 network
at Site B. At both sites the private network is connected to Port
2 of the ZXSEC US unit and the connection to the Internet is
through Port 1. At Site A, the public IP address is 172.16.67.199
and at Site B it is 172.16.68.198.
Site A configuration Site B configuration
config system gre-tunnel
edit toSiteB
set interface port1
set local-gw 172.16.67.199
set remote-gw 172.16.68.198
end
config system gre-tunnel
edit toSiteA
set interface port1
set local-gw 172.16.68.198
set remote-gw 172.16.67.199
end
Ha
Use this command to enable and configure ZXSEC US high
availability (HA) and virtual clustering. HA is supported on ZXSEC
US and USWiFi models numbered 120 and higher. Using the
config system ha command you must configure all cluster
members with the same group name, mode, and password before
the ZXSEC US units can form a cluster.
Group name, mode, password, as well as priority and group ID
are not synchronized between cluster units. The primary unit
synchronizes all other configuration settings, including the other
HA configuration settings.
When virtual domains are enabled for the ZXSEC US units to be
operating in HA mode you are configuring virtual clustering.
Using virtual clustering you create two virtual clusters and add
virtual domains to each cluster. Configuring virtual clustering is
very similar to configuring normal HA except that in a virtual
cluster, the HA mode can only be set to active-passive. As well
additional options are available for adding virtual domains to
each virtual cluster and for setting the device priority for each
device in each virtual cluster.
Note:
You cannot enable HA mode if one of the ZXSEC US unit
interfaces uses DHCP or PPPoE to acquire an IP address. If DHCP
or PPPoE is configured, the config ha mode keyword is not
available.
For complete information about how to configure and operate
ZXSEC US HA clusters and more detail about the config system
ha CLI command, see the ZXSEC US HA Overview, the ZXSEC US
HA Guide, and the USnet Knowledge Center.
Command syntax pattern
config system ha
set arps <arp_integer>
set arps-interval <interval_integer>
set authentication {disable | enable}
Example
This example shows how to configure a ZXSEC US unit for
active-active HA operation. The example shows how to set up a
T A B L E 1 3 2 E X A MP L E W EI G H TS F O R T H R E E C L U ST E R U N I TS
config system ha
set schedule weight-round-robin set weight 0 1
set weight 1 3
set weight 2 3
end
These commands have the following results:
The first connection is processed by the primary unit (priority
0, weight 1)
The next three connections are processed by the first
subordinate unit (priority 1, weight 3)
The next three connections are processed by the second
subordinate unit (priority 2, weight 3)
The subordinate units process more connections than the primary
unit, and both subordinate units, on average, process the same
number of connections.
This example shows how to display the settings for the system
ha command.
get system ha
This example shows how to display the configuration for the
system hacommand.
show system ha
F I G U R E 1 E X AM P LE H A R E M OT E I P M O N IT O R I NG T O PO LO GY
Note:
If you add two IP addresses to the detectserver keyword the
ping will be sent to both at the same time, and only when
neither server responds will the ping server fail.
Add secondary IPs to any interface and enter detectserver and
ha-priority for each of the secondary IPs. You can do this to
monitor multiple IP addresses on any interface and set a
different HA priority for each one. By adding multiple ping
servers to the remote HA monitoring configuration and setting
the HA priorities for each you can fine tune remote IP
monitoring. For example, if its more important to maintain
connections to some remote IPs you can set the HA priorities
higher for these IPs. And if its less important to maintain
connections to other remote IPs you can set the HA priorities
lower for these IPs. You can also adjust the pingserver-
failover-threshold so that if the cluster cannot connect to one
or two high priority IPs a failover occurs. But a failover will
not occur if the cluster cannot connect to one or two low
priority IPs.
Interface
Use this command to edit the configuration of a ZXSEC US
physical interface, VLAN subinterface, IEEE 802.3ad aggregate
interface, redundant interface or IPSec tunnel interface.
In the following table, VLAN subinterface can be substituted for
interface in most places except that you can only configure VLAN
subinterfaces with static IP addresses. Use the edit command to
add a VLAN subinterface.
Some keywords are specific to aggregate interfaces. These
appear at the end of the list of commands under “variables for
aggregate and redundant interfaces (models 550, 700, 900, and
1300 or higher)”.
Syntax
Entering a name string for the edit keyword that is not the name
of a physical interface adds a VLAN subinterface.
config system interface
edit <interface_name>
set allowaccess <access_types>
set alias <name_string>
set arpforward {enable | disable}
set auth-type <ppp_auth_method>
set bfd {enable | disable | global}
set bfd-desired-min-tx <interval_msec>
end
config wifi-mac_list
edit <entry_number>
set mac <mac_address>
end
Note:
A VLAN cannot have the same name as a zone or a virtual
domain.
Example
This example shows how to set the ZXSEC US550 internal
interface IP address and netmask to 192.168.100.159
255.255.255.0, and the management access to ping, https, and
ssh.
config system interface edit internal
set allowaccess ping https ssh
set ip 192.168.110.26 255.255.255.0
end
This example shows how to add a loopback interface with a
name of loop1. The IP address is set to 10.0.0.10 255.255.255.0
and bfd is set to global. Any traffic sent to this interface will be
dropped, as it is a blackhole route.
config system interface edit loop1
set type loopback
set ip 10.0.0.10 255.255.255.0
set bfd global
end
This example shows how to add a secondary IP address and
netmask of 192.176.23.180 255.255.255.0 to the internal
interface. Also configure ping and https management access to
this secondary IP address. You can not add a secondary IP that is
part of the subnet of the original interface IP address.
config system interface edit internal
config secondaryip edit 1
set allowaccess ping https
set ip 192.176.23.180 255.255.255.0
end
end
Ipv6-tunnel
Use this command to tunnel IPv6 traffic over an IPv4 network.
The IPv6 interface is configured under config system interface.
Note:
This command is not available in Transparent mode.
Syntax
config system ipv6-tunne
edit <tunnel_name>
set destination <tunnel_address>
set interface <name>
set ip6 <address_ipv6>
set source <address_ipv4>
end
Example
Use the following commands to set up an IPv6 tunnel.
config system ipv6-tunnel
edit test_tunnel
set destination 10.10.10.1
set interface internal
set ip6 12AB:0:0:CD30::/60
set source 192.168.50.1
end
Related topics
f system interface
mac-address-table
Use this command to create a static MAC table. The table can
hold up to 200 entries. This command is available in Transparent
mode only.
Syntax
config system mac-address-table
edit <mac-address_hex>
set interface <if_name>
end
Example
Use the following commands to add a static MAC entry for the
internal interface.
config system mac-address-table
edit 11:22:33:00:ff:aa
set interface internal
end
Management-tunnel
Use this command to configure the remote management tunnel
that is required by some Usservice Analysis and Management
Service remote administration features, such as the real-time
monitor, and which remote management actions the ZXSEC US
unit will allow from Usservice Analysis and Management Service.
To complete remote management setup with Usservice
Management Service, also configure their required settings, such
as providing the service account ID. For details on enabling
remote administration and remote management connections
initated by the ZXSEC US unit rather than the Usservice Analysis
and Management Service, see “system Usservice”.
Syntax
config system management-tunnel
set allow-collect-statistics {enable | disable}
set allow-config-restore {enable | disable}
set allow-push-configuration {enable | disable}
set allow-push-firmware {enable | disable}
set authorized-manager-only {enable | disable}
set serial-number <serial_str>
set status {enable | disable}
end
Example
This example shows how to configure the remote management
tunnel to allow Usservice Analysis and Management Service to
query for real-time monitor (SNMP) statistics, but not to initiate
remote firmware upgrades.
config system Usservice
set central-mgmt-status enable
set service-account-id ExampleCo
end
config system management-tunnel
set status enable
set allow-collect-statistics enable
set allow-push-firmware disable
end
Related topics
f system Usservice
f system Usservice-log
Npu
Use this command to configure the Network Processing Unit (NPU)
for ZXSEC US units that support FB4.
Note:
If you use the traffic-shaping-mode command, the bidirection
option counts twice as much traffic. You need to allow twice the
bandwidth as with unidirection.
Syntax
config system npu
set enc-offload-antireplay {enable | disable}
set dec-offload-antireplay {enable | disable}
set offload-ipsec-host {enable | disable}
set traffic-shaping-mode {unidirection | bidirection}
next
end
Defaul
Variables Description
t
Defaul
Variables Description
t
Enable this option for the system
enc-offload-antireplay to offload IPSEC packet
encryption to FB4 when the disable
{enable | disable} egress port of the tunnel is on
FB4.
Enable this option for the system
dec-offload-antireplay to offload IPSEC packet
encryption to FB4 when the enable
{enable | disable} ingress port of the tunnel is on
FB4.
Enable this option for the system
offload-ipsec-host to offload packet encryption to
disable
{enable | disable} FB4 when the egress port of this
packet is on FB4.
Select the fast path bandwidth
calculation method.
In unidirection, traffic in each
direction is counted separately.
traffic-shaping-mode In bidirectionthe traffic in both
{unidirection | directions is counted at the same
bidirection} time.
The default value on 6010
models is bidirection.
The default value on 3810B
models is unidirection.
Proxy-arp
Use this command to add IP addresses to MAC address
translation entries to the proxy ARP table.
Syntax
config system proxy-arp
edit <table_entry>
set interface <port>
set ip <ipv4_address>
next
end
Related topics
f system arp-table
f get router info bgp
Eplacemsg admin
Use this command to change the administration disclaimer page.
These are HTML messages with HTTP headers.
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg admin admin_disclaimer_text
set buffer <message>
set format <format>
set header <header_type>
end
format html No
<format> text default
none
T A B L E 1 3 4 R E P L A C E ME N T M E SS A G E TAG S
Tag Description
%%AUTH_RE
Link to open a new window. (optional).
DIR_URL%%
%%AUTH_LO
Immediately close the connection policy.
GOUT%%
URL the keep alive page connects to that keeps the
%%KEEPALIV
connection policy alive. Connects every
EURL%%
%%TIMEOUT%% seconds.
Tag Description
%%TIMEOUT Configured number of seconds between
%% %%KEEPALIVEURL%% connections.
Replacemsg alertmail
Alertmail can be configured to alert users or admins about
important system events such as blocked files or viruses
detected.
Use this command to change the alertmail pages including:
the block message that alerts users a file transfer was
blocked
the critical firewall event message
the hard disk log is full message
the nids event message to notify a network intrusion event
has occurred
the virus message to indicate that a message was found
These are HTML messages with HTTP headers.
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg alertmail
auth_msg_type
set buffer <message>
set format <format>
set header <header_type>
end
none
T A B L E 1 3 5 R E P L A C E ME N T M E SS A G E TAG S
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
%%FILE%% virus or was blocked by antivirus file blocking.
%%FILE%%can be
used in virus and file block messages.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%%can be used in
%
virus messages
The URL of a web page. This can be a web page
that is blocked by web filter content
%%URL%% or URL blocking. %%URL%%can also be used in
http virus and file block messages to be the URL of
the web page from which a user attempted to
download a file that is blocked.
Tag Description
Added to alert email critical event email messages.
%%CRITICAL %%CRITICAL_EVENT%% is replaced with the
_EVENT%% critical event message that triggered the alert
email.
The protocol (HTTP, FTP, POP3, IMAP, SMTP) in
%%PROTOCO which a virus was detected.
L%% %%PROTOCOL%% is added to alert email virus
messages.
%%SOURCE_ IP address of the email server that sent the email
IP%% containing the virus.
IP address of the user’s computer that attempted to
%%DEST_IP
download the message from which the file was
%%
removed.
%%EMAIL_FR The email address of the sender of the message
OM%% from which the file was removed.
%%EMAIL_TO The email address of the intended receiver of the
%% message from which the file was removed.
%%NIDS_EVE The IPS attack message. %%NIDS_EVENT%% is
NT%% added to alert email intrusion messages.
Example
The default message for a detected virus is:
Virus/Worm detected: %%VIRUS%% Protocol:
%%PROTOCOL%% Source IP: %%SOURCE_IP%% Destination
IP: %DST_IP%% Email Address From: %%EMAIL_FROM%%
Email Address To:
%%EMAIL_TO%%
Replacemsg auth
Use this command to change the authentication pages including:
the challenge page that prompts users for additional
verification past initial login information
the disclaimer page that notifies users when they are leaving
the protected network
the keepalive page that keeps a session open by renewing
the connection at a set interval
the failed login page that informs the user of their failed
attempt to authenticate themselves and provides the login
prompt for them to try again
the login page presented to users who must authenticate
themselves to use firewall policies or VPNs
the reject page that is displayed when the user rejects the
disclaimer page
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg auth
auth_msg_type
set buffer <message>
set format <format>
set header <header_type>
end
none
T A B L E 1 3 6 R E P L A C E ME N T M E SS A G E TAG S
Tag Description
%%AUTH_RE
Link to open a new window. (optional).
DIR_URL%%
%%AUTH_LO
Immediately close the connection policy.
GOUT%%
%%FAILED_M Message displayed on failed login page after user
ESSAGE%% login fails.
URL the keep alive page connects to that keeps the
%%KEEPALIV
connection policy alive. Connects every
EURL%%
%%TIMEOUT%% seconds.
The default login and rejected login pages use this
text immediately preceding the username and
password fields. the default challenge page uses
%%QUESTION this as the challenge question. These are treated as
%% two different variables by the server.
If you want to use different text, replace
%%QUESTION%%with the text that you prefer.
%%TIMEOUT Configured number of seconds between
%% %%KEEPALIVEURL%% connections.
%%USERNAM Username of the user logging in. This tag is used on
EID%% the login and failed login pages.
%%PASSWOR Password of the user logging in. This tag is used on
DID%% the challenge, login and failed login pages.
Replacemsg Usservice-wf
Use this command to change the default messages that replace a
web pages that Usservice web filtering has blocked.
By default, these are HTML messages.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg Usservice-wf <Usservice_msg_type>
set buffer <message>
set format <format>
set header <header_type>
end
T A B L E 1 3 7 R E P L A C E ME N T M E SS A G E TAG S
Tag Description
The URL of a web page. This can be a web page
that is blocked by web filter content
%%URL%% or URL blocking. %%URL%%can also be used in
http virus and file block messages to be the URL of
the web page from which a user attempted to
download a file that is blocked.
Replacemsg ftp
Use this command to change default replacement messages
added to FTP sessions when the antivirus engine blocks a file either
because of a matching file pattern or because a virus is detected.
By default, these are text-format messages with no header.
Note:
If you unset the buffer for a replacement message, it will be cleared.
Syntax
config system replacemsg ftp <message-type>
set buffer <message>
set format <format>
set header <header_type>
end
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
%%FILE%% virus or was blocked by antivirus file blocking.
%%FILE%% can be
used in virus and file block messages.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%% can be used in
%
virus messages
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The URL of a web page. This can be a web page
that is blocked by web filter content
%%URL%% or URL blocking. %%URL%% can also be used in
http virus and file block messages to be the URL of
the web page from which a user attempted to
download a file that is blocked.
The protocol (HTTP, FTP, POP3, IMAP, SMTP) in
%%PROTOCO which a virus was detected.
L%% %%PROTOCOL%%is added to alert email virus
messages.
The IP address from which a virus was received. For
email this is the IP address of the email server that
%%SOURCE_ sent the email containing the virus. For HTTP this is
IP%% the IP address
of the web page that sent the virus.
Tag Description
The IP address of the computer that would have
received the blocked file. For email this is the IP
%%DEST_IP
address of the user’s computer that attempted to
%%
download the message from which the file was
removed.
Example
This example shows how to change the message sent when an
FTP download is oversize.
config system replacemsg ftp ftp-dl-filesize
set buffer "This file download was blocked because it is > 10MB."
end
Replacemsg http
Use this command to change default replacement messages
added to web pages when the antivirus engine blocks a file in an HTTP
session because of a matching file pattern or because a virus is detected;
or when web filter blocks a web page.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg http <message-type>
set buffer <message>
set format <format>
set header <header_type>
end
T A B L E 1 3 9 R EP L A C E M E N T M E S S A G E TAG S
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
%%FILE%% virus or was blocked by antivirus file blocking.
%%FILE%% can be
used in virus and file block messages.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%% can be used in
%
virus messages
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The URL of a web page. This can be a web page
that is blocked by web filter content
%%URL%% or URL blocking. %%URL%% can also be used in
http virus and file block messages to be the URL of
the web page from which a user attempted to
download a file that is blocked.
The protocol (HTTP, FTP, POP3, IMAP, SMTP) in
%%PROTOCO which a virus was detected.
L%% %%PROTOCOL%%is added to alert email virus
messages.
%%SOURCE_ The IP address of the web page from which a virus
IP%% was received.
The IP address of the computer that would have
received the blocked file. For email this is the IP
%%DEST_IP
address of the user’s computer that attempted to
%%
download the message from which the file was
removed.
Example
This example shows how to change the message that replaces a
web page blocked for banned words.
config system replacemsg http http-client-bannedword
set buffer "This web page was blocked. It contains banned words."
end
Replacemsg im
Use this command to change default replacement messages
added to instant messaging and peer-to-peer sessions when
either file-transfer or voice-chat is blocked.
By default, these are text messages with an 8-bit header.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg im <message-type>
set buffer <message>
set format <format>
set header <header_type>
end
T A B L E 1 4 0 R E P LA C E M E NT M E S S A G E TAG S
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
%%FILE%% virus or was blocked by antivirus file blocking.
%%FILE%% can be
used in virus and file block messages.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%% can be used in
%
virus messages
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The protocol (HTTP, FTP, POP3, IMAP, SMTP) in
%%PROTOCO which a virus was detected.
L%% %%PROTOCOL%%is added to alert email virus
messages.
The IP address from which a virus was received. For
email this is the IP address of the email server that
%%SOURCE_ sent the email containing the virus. For HTTP this is
IP%% the IP address
of the web page that sent the virus.
The IP address of the computer that would have
received the blocked file. For email this is the IP
%%DEST_IP
address of the user’s computer that attempted to
%%
download the message from which the file was
removed.
Example
This example shows how to change the message added to
instant messaging sessions when voice chat is blocked.
config system replacemsg im im-voice-chat-block
set buffer "Use of chat applications is not permitted."
end
Replacemsg mail
Use this command to change default replacement messages
added to email messages when the antivirus engine blocks a file
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg mail <message-type>
set buffer <message>
set format <format>
set header <header_type>
end
T A B L E 1 4 1 R E P LA C E M E NT M E S S A G E TAG S
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
%%FILE%% virus or was blocked by antivirus file blocking.
%%FILE%% can be
used in virus and file block messages.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%% can be used in
%
virus messages
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The protocol (HTTP, FTP, POP3, IMAP, SMTP) in
%%PROTOCO which a virus was detected.
L%% %%PROTOCOL%%is added to alert email virus
messages.
%%SOURCE_ IP address of the email server that sent the email
IP%% containing the virus.
IP address of the user’s computer that attempted to
%%DEST_IP
download the message from which the file was
%%
removed.
Tag Description
%%EMAIL_FR The email address of the sender of the message
OM%% from which the file was removed.
%%EMAIL_TO The email address of the intended receiver of the
%% message from which the file was removed.
Example
This example shows how to change the email message that is
sent to test the alert email system.
config system replacemsg mail email-virus
set buffer "The attachment was blocked because it contains a virus."
end
Keywords and
Description Default
variable
MM1 replacement message types, one
of:
mm1-retr-conf-block
mm1-retr-conf-bword
mm1-retr-conf-sis-block
mm1-retr-conf-virus
mm1-send-conf-block
<message_type No
> mm1-send-conf-bword default.
mm1-send-conf-sis-block
mm1-send-conf-virus
mm1-send-req-block
mm1-send-req-bword
mm1-send-req-sis-block
mm1-send-req-virus
utf-8
Keywords and
Description Default
variable
Set the format of the message, one
of:
html
none
format <format> text
text
wml
Not all formats are supported by all
message types.
from
Address the message is from. null
<from_address>
from-sender Enable for the notification message to
{enable | be sent from the recipient. This is to disable
disable} avoid billing problems.
Keywords and
Description Default
variable
Response status code, one of:
err-content-not-accepted
err-msg-fmt-corrupt
err-msg-not-found
err-
rsp-status err-net-prob content-
<rsp_status> err-snd-addr-unresolv not-
accepted
err-srv-denied
err-unspecified
err-unsupp-msg
ok
rsp-text Depends
on
<response_text Response text.
message
> type.
Sender visibility, one of:
show
Example
This example shows how to set the message sent when a virus
being sent by this user on the MM1 network. It uses the default
message text.
config system replacemsg mm1 mm1-send-conf-virus
set charset utf-8 set class automatic set format text
set header none set priority high
set rsp-status err-content-not-accepted
set subject “File you sent contains a virus”
set message "The message you sent has been blocked because the
file
%%FILE%% in the message contains the virus %%VIRUS%%.
The message has been quarantined as
%%QUARFILENAME%%."
end
Keywords and
Description Default
variable
MM3 replacement message types, one
of:
mm3-block
mm3-block-notif
mm3-bword
<message_type mm3-bword-notif No
> default
mm3-sis-block
mm3-sis-block-notif
mm3-sis-block-notif
mm3-virus
mm3-virus-block
utf-8
text
wml
Keywords and
Description Default
variable
from
Address the message is from. null
<from_address>
Set the format of the message
header, one of:
header 8bit
none
<header_type>
http
none
Depends
message on
Text of the replacement message.
<message_text> message
type.
Priority of the message, one of:
high
priority low
normal
<priority>
normal
not included
Depends
subject on
Subject text string.
<subject_text> message
type.
Example
This example shows how to set the message sent when a user on
the MM3 network sends one or more viruses. It uses the default
message text.
config system replacemsg mm3 mm3-virus
set charset utf-8 set class automatic set format text
set header none set priority high
set rsp-status err-content-not-accepted
set subject “Messages sent containing viruses”
set message "This device has sent %%NUM_MSG%% messages
containing the virus %%VIRUS%% in the last %%DURATION%%
hours."
end
Keywords and
Description Default
variables
MM4 replacement message types, one
of:
mm4-block
mm4-block-notif
mm4-bword
<message_type No
> mm4-bword-notif default
mm4-sis-block
mm4-sis-block-notif
mm4-virus
mm4-virus-block
Keywords and
Description Default
variables
Character encoding used for
replacement messages, one of:
charset
us-ascii utf-8
<character_set>
utf-8
domain
<address_domai The from address domain. null
n>
Replacement message format flag,
one of:
html
format <format> none text
text
wml
from
Address the message is from. null
<from_address>
from-sender Enable for the notification message to
{enable | be sent from the recipient. This is to disable
disable} avoid billing problems.
Keywords and
Description Default
variables
Priority of the message, one of:
high
priority low
normal
<priority>
normal
not included
Example
This example shows how to set the message sent when a user on
the MM4 network sends one or more viruses. It uses the default
message text.
config system replacemsg mm4 mm4-virus-notif
set class automatic set domain ‘’
set format text set header none set priority high
set subject “Messages sent containing viruses”
set message "This device has sent %%NUM_MSG%% messages
containing the virus %%VIRUS%% in the last %%DURATION%%
hours."
end
Keywords and
Description Default
variables
MM7 replacement message types, one
of:
mm7-block
mm7-block-notif
mm7-bword
<mm7message_ No
type> mm7-bword-notif default
mm7-sis-block
mm7-sis-block-notif
mm7-virus
mm7-virus-block
Keywords and
Description Default
variables
From address types, one of:
number
addr_type
number
<addr_type> rfc2882-addr
short-code
utf-8
text
wml
from
Address the message is from. null
<from_address>
from-sender Enable for the notification message to
{enable | be sent from the recipient. This is to disable
disable} avoid billing problems.
Keywords and
Description Default
variables
Priority of the message, one of:
high
priority low
normal
<priority>
normal
not included
Example
This example shows how to set the message sent when a user on
the MM7 network sends one or more viruses. It uses the default
message text.
config system replacemsg mm7 mm7-virus-notif
set charset utf-8 set class automatic set format text
set header none set priority high
set rsp-status err-content-not-accepted
set subject “Messages sent containing viruses”
set message "This device has sent %%NUM_MSG%% messages
containing the virus %%VIRUS%% in the last %%DURATION%%
hours."
end
Replacemsg nntp
Use this command to change the net news transfer protocol
(NNTP) download pages including:
NNTP download blocked
NNTP download filesize error
NNTP download infected
These are HTML messages with HTTP headers.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg nntp auth_msg_type
set buffer <message>
set format <format>
set header <header_type>
end
format html No
<format> text default
none
T A B L E 1 4 2 R E P LA C E M E NT M E S S A G E TAG S
Tag Description
The name of a file that has been removed from a
content stream. This could be a file that contained a
virus or was blocked by antivirus file blocking. The
%%FILE%%
file may have been quarantined if a virus was
detected. %%FILE%% can be used in virus and file
block messages.
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The name of a virus that was found in a file by the
%%VIRUS%
antivirus system. %%VIRUS%% can be used in
%
virus messages
Example
The default message for a detected virus is:
Virus/Worm detected: %%VIRUS%% Protocol:
%%PROTOCOL%% Source IP: %%SOURCE_IP%% Destination
IP: %DST_IP%% Email Address From: %%EMAIL_FROM%%
Email Address To:
%%EMAIL_TO%%
Replacemsg spam
Use this command to change default replacement messages
added to SMTP email messages when spam filter blocks an email
message. By default, these are text messages with an 8-bit
header.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg spam <message-type>
set buffer <message>
set format <format>
set header <header_type>
end
T A B L E 1 4 3 R E P LA C E M E NT M E S S A G E TAG S
Tag Description
Tag Description
The name of a file that has been removed from a
content stream and added to the quarantine. This
could be a file that contained a virus or was blocked
%%QUARFILE
by antivirus file blocking. %%QUARFILENAME%%
NAME%%
can be used in virus and file block messages.
Quarantining is only available on ZXSEC US units
with a local disk.
The IP address from which a virus was received. For
email this is the IP address of the email server that
%%SOURCE_ sent the email containing the virus. For HTTP this is
IP%% the IP address
of the web page that sent the virus.
The IP address of the computer that would have
received the blocked file. For email this is the IP
%%DEST_IP
address of the user’s computer that attempted to
%%
download the message from which the file was
removed.
%%EMAIL_FR The email address of the sender of the message
OM%% from which the file was removed.
%%EMAIL_TO The email address of the intended receiver of the
%% message from which the file was removed.
Example
This example shows how to change the message added to SMTP mail
that the spam filter has blocked.
config system replacemsg spam ipblocklist
set buffer "This email was blocked as spam."
end
Replacemsg sslvpn
Use this command to change the login page presented to SSL-
VPN users. This is an HTML message with an HTTP header.
Note:
If you unset the buffer for a replacement message, it will be
cleared.
Syntax
config system replacemsg sslvpn sslvpn-login
set buffer <message>
set format <format>
set header <header_type>
end
Replacemsg-group (US
Carrier)
In US Carrier, replacement messages can be created and applied
to specific protection profiles. This allows the customization of
messages for specific users or user groups. Users are assigned to
a group through the protection profile feature of firewall. See
“firewall profile” for more information on protection profiles.
If a user is not part of a custom replacement message group,
their replacement messages come from the ‘default’ group.
The ’default’ group always exists, and cannot be deleted. All
additional replacement message groups inherit from the default
group. Any messages in custom groups that have not been
edit
Create or edit a replacement message
<groupname_stri
group.
ng>
buffer ftp
<string> http
mail
nntp
spam
Other replacement messages use the
messagekeyword.
format html
<format_fla none
g>
text
wml
message mm1
<string> mm3
mm4
mm7
Other replacement messages use the
bufferkeyword.
Example
In this example you have 2 groups of users that use different
replacement messages due to language and regional differences.
The first group is in the United States, and the other group is in
the United Kingdom. Different spelling and different speech
patterns mean, each group expects different messages. To keep
it simple, the format will be text only.
config system replacemsg-group
edit united_states
set comment “messages for United States customers”
config http edit 1
set msg-type bannedword set format text
set message “Your attempt to access this unauthorized web page has
been blocked. It contains off-color words that violate the banned word
list. URL = http://%%URL%%”
end
end
edit united_kingdom
Replacemsg-image (US
Carrier)
Use this command to add, edit, or delete images to be used in
SMIL parts of replacement messages. Both image-base64 and
image-type must be present for a valid entry.
Syntax
config system replacemsg-image
edit <image_name>
set image-base64 <image_data>
set image-type <format>
end
Defaul
Variables Description
t
edit Enter the name or tag to use for this
none.
<image_name> image
Enter the image in base64 encoding.
image-base64 You can also use the graphical
none.
<image_data> interface to add images by browsing
to their location.
Select the format of the image.
Available formats include:
gif
image-type
jpeg none.
<format>
png
tiff
Session-helper
A session helper binds a service to a TCP or UDP port. By default,
there are session helpers that bind services to standard ports.
Use this command to configure a new session helper or to edit
an existing one.
Syntax
config system session-helper
edit <helper-number>
set name <helper-name>
set port <port_number>
set protocol <protocol_number>
end
Keywords and
Description Default
variables
Enter the number of the
session-helper that you want
to edit, or enter an unused No
edit <helper-number>
number to create a new default.
session-helper.
The name of the session
helper. One of:
dns-tcp, dns-udp, ftp, h245I, No
name <helper-name>
h245O, h323, ident, mms, default.
pmap, pptp, ras, rtsp, sip,
tftp, tns.
Keywords and
Description Default
variables
Enter the port number to use No
port <port_number>
for this protocol. default.
The protocol number for this
protocol service, as defined in No
<protocol_number> default.
RFC 1700.
Example
Use the following commands to edit the file transfer protocol
(FTP) and change it to port 111, but remain as protocol 6:
config system session-helper edit 8
set name ftp set port 111 set protocol 6
end
Session-sync
Use this command to configure TCP session synchronization
between two standalone ZXSEC US units. You can use this feature
with external routers or load balancers configured to distribute or
load balance TCP sessions between two peer ZXSEC US units. If
one of the peers fails, session failover occurs and active sessions
fail over to the peer that is still operating. This failover occurs
without any loss of data.
As well the external routers or load balancers will detect the
failover and re-distribute all sessions to the peer that is still
operating.
Note:
TCP session synchronization between two standalone ZXSEC US
units is also sometimes called standalone session
synchronization or session synchronization between non-HA
ZXSEC US units.
Standalone session synchronization can be used instead of HA to
provide session synchronization between two peer ZXSEC US
units. If the external load balances direct all sessions to one peer
the
affect is similar to active-passive HA. If external load balancers
or routers load balance traffic to both peers, the affect is similar
to active-active HA. The load balancers should be configured so
that all of the packets for any given session are processed by the
same peer. This includes return packets.
Unlike HA, standalone session synchronization does not include
configuration synchronization. In fact, the configuration of the
two peers is not identical because in most cases the peers would
have different
F I G U R E 2 S TA ND AL ON E SESSIO N SYNCHR O NI Z AT I ON
Note that the index numbers of the matching interfaces and VLAN
interfaces can be different. Also the VLAN IDs of the matching
VLAN interfaces can be different.
As well, the session synchronized virtual domains should have
the same firewall policies so that sessions can be resumed after
a failover using the same firewall policies.
For a configuration example, see “Basic example configuration”.
Configuring the session synchronization link
When session synchronization is operating, the peers share
session information over an Ethernet link between the peers
similar to an HA heartbeat link. Usually you would use the same
interface on each peer for session synchronization. You should
connect the session synchronization interfaces directly without
using a switch or other networking equipment. If possible use a
crossover cable for the session synchronization link. For ZXSEC
US systems you can use a backplane interface as the session
synchronization link.
You can use different interfaces on each peer for session
synchronization links. Also, if you multiple sessions
synchronization configurations, you can have multiple session
synchronization links between the peers. In fact if you are
synchronizing a lot of sessions, you may want to configure and
connect multiple session synchronization links to distribute
session synchronization traffic to these multiple links.
You cannot configure backup session synchronization links. Each
configuration only includes one session synchronization link.
The session synchronization link should always be maintained. If
session synchronization communication is interrupted and a
failure occurs, sessions will not failover and data could be lost.
Session synchronization traffic can use a considerable amount of
network bandwidth. If possible, session synchronization link
interfaces should only be used for session synchronization traffic
and not for data traffic.
Syntax
config system session-sync
edit <sync_id>
set peerip <peer_ipv4> set peervd <vd_name>
set syncvd <vd_name> config filter
set dstaddr <string>
set dstintf <interface_name>
set service <string>
set srcaddr <string>
set srcintf <interface_name>
end
end
Configuration steps
1. Configure the load balancer or router to send all sessions to
peer_1.
2. Configure the load balancer or router to send all traffic to
peer_2 if peer_1 fails.
3. Use normal ZXSEC US configuration steps on peer_1:
Enable virtual domain configuration.
Add the vdom_1 virtual domain.
Add port1 and port2 to the vdom_1 virtual domain and
configure these interfaces.
Set the IP address of port1 to 192.168.20.1.
Set the IP address of port2 to 172.110.20.1.
Set the IP address of port3 to 10.10.10.1.
Add route mode firewall policies between port1 and port2 to
vdom_1.
4. Enter the following commands to configure session
synchronization for peer_1
config system session-sync
edit 1
set peerip 10.10.10.2
set peervd root set syncvd vdom_1
end
5. Use normal ZXSEC US configuration steps on peer_2:
Enable virtual domain configuration.
Add the vdom_1 virtual domain.
Add port1 and port2 to the vdom_1 virtual domain and
configure these interfaces.
Set the IP address of port1 to 192.168.20.2.
Set the IP address of port2 to 172.110.20.2.
Set the IP address of port3 to 10.10.10.1.
Add route mode firewall policies between port1 and port2 to
vdom_1.
6. Enter the following commands to configure session
synchronization for peer_1
config system session-sync
edit 1
set peerip 10.10.10.1
set peervd root set syncvd vdom_1
end
Session-ttl
Use this command to increase or decrease the length of time a
TCP session can be idle before being dropped. You can set the
general default timeout or set the timeout for a specific port.
Syntax
config system session-ttl
set default <seconds> config port
edit <port_number>
set timeout {<seconds> | never}
end
end
Note:
While it is possible to set a timeout for a session to a value that
never expires, this is not a secure configuration and should be
avoided.
Examples
The following command increases the default session timeout:
config system session-ttl
set default 62000
end
Use the following command to change the session timeout for
SSH on port 22 to 3600 seconds.
config system session-ttl config port
edit 22
set timeout 3600
end
end
Settings
Use this command to change settings that are per VDOM settings
such as the operating mode and default gateway.
When changing the opmode of the VDOM, there are keywords
that are visible depending on which opmode you are changing to.
They are only visible after you set the opmode ab before you
commit the changes with either ‘end or ‘next’. If you do not set
these keywords, the opmode change will fail.
T A B L E 1 4 5 K EY W O R D S A S SO C I A T ED W I T H E AC H O PM O D E
bfd-dont-enforce-
src-port Enable to not enforce the BFD
disable
source port.
{enable | disable}
Enter a descriptive comment for
comments <string> null
this virtual domain.
Enter the interface to use for
management access. This is the
interface to which ipapplies.
device No
<interface_name> This keyword is visible only after default.
you change opmode from
transparent to nat, before you
commit the change.
Example
Changing the opmode from Transparent to NAT involves a
number of steps. For example, before you change the opmode,
the other required keywords ip, device, and gateway are not
visible.
This example changes to NAT opmode in a VDOM called vdom2.
The management interface is set to internal, and the
management IP is set to 192.168.10.8 with a gateway of
192.168.10.255 .
config vdom edit vdom2
config system settings
set opmode nat
set device internal
set ip 192.168.10.8
set gateway internal
end
end
Related Commands
f vdom
Snmp community
Use this command to configure SNMP communities to your
ZXSEC US unit. You add SNMP communities so that SNMP
managers can connect to the ZXSEC US unit to view system
information and receive SNMP traps. You can add up to three
SNMP communities. Each community can have a different
configuration for SNMP queries and traps. Each community can
be configured to monitor the ZXSEC US unit for a different set of
events. You can also the add IP addresses of up to 8 SNMP
managers to each community.
Part of configuring an SNMP manager is to list it as a host in a
community on the ZXSEC US unit it will be monitoring.
Otherwise the SNMP monitor will not receive any traps from that
ZXSEC US unit, or be able to query it.
Syntax
config system snmp community
edit <index_number>
set events <events_list>
set name <community_name>
set query-v1-port <port_number>
set query-v1-status {enable | disable}
hosts variables
Enter the index number of the
host in the table. Enter an
edit <host_number>
unused index number to create
a new host.
Enter the name of the ZXSEC
No
interface <if_name> US interface to which the
Default
SNMP manager connects.
Enter the IP address of the
ip <address_ipv4> 0.0.0.0
SNMP manager.
Example
This example shows how to add a new SNMP community named
SNMP_Com1. The default configuration can be used in most
cases with only a few modifications. In the example below the
community is added, given a name, and then because this
community is for an SNMP manager that is SNMP v1 compatible,
all v2c functionality is disabled. After the community is
configured the SNMP manager is added. The SNMP manager IP
Snmp sysinfo
Use this command to enable the ZXSEC US SNMP agent and to
enter basic system information used by the SNMP agent. Use
information about the ZXSEC US unit to identify it. When your
SNMP manager receives traps from the ZXSEC US unit, you will
know which unit sent the information.
Syntax
config system snmp sysinfo
set contact-info <info_str>
set description <description>
set location <location>
set status {enable | disable}
set trap-high-cpu-threshold <percentage>
set trap-log-full-threshold <percentage>
set trap-low-memory-threshold <percentage>
end
Keywords and
Description Default
variables
Add the contact information for
the person responsible for this
contact-info
ZXSEC US unit. The contact No default
<info_str>
information can be up to 35
characters long.
Add a name or description of
description the ZXSEC US unit. The
No default
<description> description can be up to 35
characters long.
Keywords and
Description Default
variables
Describe the physical location of
the ZXSEC US unit. The system
location <location> No default
location description can be up
to 35 characters long.
status {enable | Enable or disable the ZXSEC US
disable
disable} SNMP agent.
Enter the percentage of CPU
trap-high-cpu-
used that will trigger the
threshold 80
threshold
<percentage>
SNMP trap for the high-cpu.
Example
This example shows how to enable the ZXSEC US SNMP agent
and add basic SNMP information.
config system snmp sysinfo set status enable
set contact-info 'System Admin ext 245'
set description 'Internal network unit'
set location 'Server Room A121'
end
Related topics
f system snmp community
Switch-interface
Use this command to group interfaces into a ‘soft-switch’ - a
switch that is implemented in software instead of hardware. A
group of switched interfaces have one IP address between them
to connect to the ZXSEC US unit. This feature is only available
on models that have the switch-mode feature Interfaces that
may be members of a ‘soft-switch’ are physical and wlan
interfaces that are not used anywhere else in US. Member
interfaces cannot be monitored by HA or used as heart beat
devices.
Syntax
config system switch-interface
edit <group_name>
set member <if1_ipv4> <if2_ipv4> ...
end
Keywords and
Description Default
variables
The name for this group of interfaces.
Cannot be in use by any other No
<group_name>
interfaces, vlans, or inter-VDOM default
links.
Enter all the interfaces that will be
member part of this switch on one line.
<if1_ipv4> Separate each by a space. No
default
<if2_ipv4> ... Use <tab> to advance through the list
of available interfaces.
Example
This example shows how to create a group of 3 interfaces called
low_speed ideally that are all at 10m speed. It assumes these
interfaces are not referred to in US by anything else.
config system switch-interface edit low_speed
set member port1 wlan dmz
end
Tos-based-priority
Use this command to prioritize your network traffic based on its
type-of-service (TOS).
IP datagrams have a TOS byte in the header (as described in
RFC 791). Four bits within this field determine the delay, the
throughput, the reliability, and cost associated with that service.
Together these bits are the tos variable of the tos-based-priority
command.
The TOS information can be used to manage network traffic
based on the needs of the application or service. TOS application
routing (RFC 1583) is supported by OSPF routing.
Syntax
config system tos-based-priority
edit <name>
set tos <ip_tos_value>
set priority [high | medium | low]
end
Examples
It is a good idea to have your entry names in the tos-based-
priority table and their TOS values be the same. Otherwise it can
become confusing.
config tos-based-priority edit 1
set tos 1
set priority low
next
edit 4
set tos 4
set priority medium
next
edit 6
set tos 6
set priority high
next
end
Related topics
f system global
f router ospf
f execute ping-options
Vdom-link
Use this command to create an internal point-to-point interface
object. This object is a link used to join virtual domains.
Creating the interface object also creates 2 new interface objects
by the name of <name>0 and <name>1. For example if your
object was named v_link, the 2 interface objects would be
named v_link0 and v_link1. You can then configure these new
interfaces as you would any other virtual interface using config
system interface.
When using vdom-links in HA, you can only have vdom-links in
one vcluster. If you have vclusters defined, you must use the
vcluster keyword to determine which vcluster will be allowed to
contain the vdom-links.
As of US v3.0 MR3, inter-VDOM links support BGP routing.
As of US v3.0 MR6, DHCP is supported on inter-VDOM links.
For more information on the vdom-link command see
“Configuring inter-VDOM routing” and the ZXSEC US VLANs and
VDOMs Guide.
Syntax
config system vdom-link
edit <name>
end
Examples
In this example you have already created two virtual domains
called v1 and v2. You want to set up a
link between them. The following command creates the VDOM
link called v12_link. Once you have the link you need to bind its
two ends to the VDOMs it will be working with.
config system vdom-link edit v12_link
end
config system interface edit v12_link0
set vdom v1
next
edit v12_link1
set vdom v2
end
Wireless mac-filter
Use this command to configure the WLAN interface MAC filter on
the 120W unit in Access Point mode.
Syntax
config system wireless mac-filter
set default-acl {allow | deny}
set status {enable | disable}
config mac-list
edit <list_number>
set acl {allow | deny }
set mac <mac_address>
end
end
Examples
This example shows how to enable the MAC filter, specify that
unlisted MAC addresses should be denied access, and add MAC
address 12:34:56:78:90:AB to the MAC filter Allow list:
config system wireless mac-filter
set status enable
set default-acl deny config mac-list
edit 1
set acl allow
set mac 12:34:56:78:90:AB
end
end
Related topics
f system wireless settings
f system interface
Wireless settings
Use this command to configure the WLAN interface wireless
settings on the 120W unit.
Syntax
config system wireless settings
set band {802.11a | 802.11b | 802.11g}
set beacon_interval <integer>
set broadcast_ssid {enable | disable}
set channel <channel_number>
set fragment_threshold <bytes>
set geography <americas | EMEA | Israel | Japan | World>
set key <WEP-key_hex>
set mode <opmode>
set passphrase <string>
set power_level <dBm>
set radius-server <radius_name>
set rts_threshold <integer>
set security <sec_mode>
set ssid <ssid_string>
end
Client
Connect to another wireless
network as a client.
Example
This example shows how to configure the wireless interface.
config system wireless settings
set channel 4
set geography Americas
set security WEP128
set ssid test_wifi
end
Related topics
f system interface
f system vdom-link
f wireless mac-filter
Zone
Use this command to add or edit zones.
In NAT/Route mode, you can group related interfaces or VLAN
subinterfaces into zones. Grouping interfaces and subinterfaces
into zones simplifies policy creation. For example, if you have
two interfaces connected to the Internet, you can add both of
these interfaces to the same zone. Then you can configure
policies for connections to and from this zone, rather than to and
from each interface.
In Transparent mode you can group related VLAN subinterfaces
into zones and add these zones to virtual domains.
Syntax
config system zone edit <zone_name>
set interface <name_str>
set intrazone {allow | deny}
end
Keywords and
Description Default
variables
Enter the name of a new or
edit <zone_name>
existing zone.
Add the specified interface to this
zone. You cannot add an interface No
interface <name_str>
if it belongs to another zone or if default.
firewall policies are defined for it.
Allow or deny traffic routing
intrazone {allow |
between different interfaces in deny
deny}
the same zone.
Example
This example shows how to add a zone named Zone1, add the
internal interface to it, and to deny routing between different
zones.
config system zone
edit Zone1
set interface internal
set intrazone deny
end
Related topics
system interface
Chapter 14
User
Overview
This chapter covers:
configuration of the ZXSEC US unit to use external
authentication servers, including
Windows Active Directory
configuration of user accounts and user groups for firewall
policy authentication, administrator authentication and some
types of VPN authentication
configuration of peers and peer groups for IPSec VPN
authentication and PKI user authentication
configuration of dynamic profiles and msisdn filters (US
Carrier)
This chapter contains the following sections:
Configuring users for authentication
adgrp
dynamic-profile (US Carrier)
endpoint-bwl (US Carrier)
endpoint-ip-filter (US Carrier)
endpoint-translation (US Carrier)
fsae
group
ldap
loca
peer
peergrp
radius
settings
tacac+
Adgrp
Use this command to list Active Directory user groups.
Syntax
get user adgrp [<adgroupname>]
If you do not specify a group name, the command returns information for
all Active Directory groups. For example:
== [ DOCTEST/Cert Publishers ]
name: DOCTEST/Cert Publishers server-name: ADserv1
== [ DOCTEST/Developers ]
name: DOCTEST/Developers server-name: ADserv1
== [ DOCTEST/Domain Admins ]
name: DOCTEST/Domain Admins server-name: ADserv1
== [ DOCTEST/Domain Computers ]
name: DOCTEST/Domain Computers server-name: ADserv1
== [ DOCTEST/Domain Controllers ]
name: DOCTEST/Domain Controllers server-name: ADserv1
== [ DOCTEST/Domain Guests ]
name: DOCTEST/Domain Guests server-name: ADserv1
== [ DOCTEST/Domain Users ]
name: DOCTEST/Domain Users server-name: ADserv1
== [ DOCTEST/Enterprise Admins ]
name: DOCTEST/Enterprise Admins server-name: ADserv1
== [ DOCTEST/Group Policy Creator Owners ]
name: DOCTEST/Group Policy Creator Owners server-name: ADserv1
== [ DOCTEST/Schema Admins ]
name: DOCTEST/Schema Admins server-name: ADserv1
If you specify an Active Directory group name, the command returns
information for only that group. For example:
name : DOCTEST/Developers server-name : ADserv1
Keywords and
Description Default
variables
Timeout value for user context
context-timeout
table entries. In seconds, 28800
<timeout_seconds>
0 disables the timeout feature.
Keywords and
Description Default
variables
endpoint-attribute
RADIUS attribute used to hold
<endpoint_attribute Endpoint name.
>
Time to hold in proxy connection
hold-time state to receive RADIUS START. In
seconds, 0 disables the feature and 5
<proxy_hold_time> the proxy will wait until the session
times out.
Enter one or more of the following
options, separated by spaces:
none disable all RADIUS event
logging accounting-event enable to
log accounting events accounting-
stop- enable to log missed
accounting All
missed events options
log-flags <lflags>
context-missingenable to log except
missing context errors profile- none.
missing enable to log missing
profile errors protocol-error enable
to log protocol errors radiusd-other
enable to log other radius
log
messages
Enter the minimum time period to
log-period
use for event logs. In seconds, 0 0
<log_time>
means forever.
mem-percent Maximum percentage of system
<memory_percent memory to use for context tables. 4
> CLI only.
Keywords and
Description Default
variables
Enter the RADIUS server shared
secret No
secret for responses/validating
<server_password> default.
requests.
Enable dynamic profile queries for
protection profile features. The
following options are available:
status-ussrv Usservice overrides
status-ftp FTP
status-http HTTP, MM1, and
MM7
status enable
status-imap IMAP
status-im-ips IM, IPS, and VOIP
status-log log messages
status-nntp NNTP
status-pop3 POP3
status-smtp SMTP
validate-request- Enable to validate RADIUS request
secret shared secret. Maximum 12 disable
{enable | disable} characters.
Example
This example shows how to enable a dynamic profile in the root
vdom that will send RADIUS responses/validate the RADIUS
request secret, will use the default profile if the HTTP header is
not present in the MMS transaction, and log all events.
config user dynamic-profile set status enable
set vdom “root”
set radius-response enable
set validate-request-secret enable set http-header-status enable
set http-header-fallback default-profile
set log-flags protocol-error profile-missing context-missing accounting-
stop-missed accounting-event radiusd-other
end
Related topics
f endpoint-bwl (US Carrier)
f endpoint-ip-filter (US Carrier)
f endpoint-translation (US Carrier)
Keywords and
Description Default
variables
The action (or actions archiveand
intercept) to take if the End Point
expression is found in the list.
none: no action is taken
Keywords and
Description Default
variables
Example
The following example details the End Point filter list
EndPoint2+List. Entries combine features including the action
(none, block, exempt from mass MMS, exempt from all scanning),
status (enable/disable), and pattern type (wildcard/regular
expression/single End Point).
config user endpoint-bwl
edit 2
set comment "Description+of+EndPoint2+list."
config entries edit "*504*"
set action exempt-mass-mms
Note:
With the End Point IP Filter, only the block action applies, there
is no intercept or archive capability.
Syntax
config user endpoint-ip-filter
edit endpoint_filter_list_integer
set log-status {enable | disable}
next
end
Keywords and
Description Default
variables
endpoint_filter_list_integ A unique number to identify No
er the End Point IP filter list. default
Enable End Point IP filter
log-status {enable |
search for End Point disable
disable}
expression.
Related topics
dynamic-profile (US Carrier)
endpoint-bwl (US Carrier)
endpoint-translation (US Carrier)
Endpoint-translation (US
Carrier)
With End Point filtering, MM1/3/4/7 messages are filtered by the
End Point specified in the ‘from’ or ‘to’ addresses. End Point
filtering is available in VDOM mode, on a per-vdom basis.
The End Point information is normally found in the HTTP header,
but there is a variety of formats and in some cases, a
requirement to extract this information from a cookie. The
endpoint-translation feature sets up the process to extract the
End Point information if it is not present in the HTTP header.
Syntax
config user endpoint-translation
set missing-header-fallback <policy-profile | session-ip>
set endpoint-header <endpoint_header_title>
set profile-query-type < extract-ip | extract-endpoint | session-ip >
set endpoint-prefix {enable | disable}
set endpoint-prefix-string <prefix_string>
Keywords and
Description Default
variables
Specify method to determine user
identification if http_header is not
missing-header- present in the End Point
fallback information. policy-
<policy-profile | policy-profile: use the default profile
session-ip> profile
session-ip: use the ip header
address
endpoint-header x-up-
Name of the End Point header. Up
<endpoint_header_ calling-
to 64 character maximum. String.
title> line-id
Keywords and
Description Default
variables
Select the source of the End Point
identifier.
endpoint-source
http-header: source is the http http-
{http- header |
header field in the sender’s address header
cookie}
cookie: source is the attributes of
the sender’s address cookie
endpoint-convert- Enable to convert the sender
hex address from HEX to ASCII, if disable
{enable | disable} required, for blocking and logging.
Example
This example shows how to configure End Point filtering address
translation with the name ‘enable’ that uses the session IP
address (including the ability to convert from HEX to ASCII) and
is able to remove the address header to set up the dynamic
profile from the HTTP request:
config user endpoint-translation
set missing-header-fallback session-ip
set profile-query-type extract-ip
set endpoint-header “enable”
set endpoint-convert-hex
set ip-header-suppress enable
end
Related topics
dynamic-profile (US Carrier)
endpoint-bwl (US Carrier)
endpoint-ip-filter (US Carrier)
Fase
Use this command to configure the ZXSEC US unit to receive
user group information from a Windows Active Directory server
equipped with the USnet Server Authentication Extensions
(FSAE). You can specify up to five computers on which a FSAE
collector agent is installed. The ZXSEC US unit uses these
collector agents in a redundant configuration. If the first agent
Related topics
user group
execute fsae refresh
firewall policy, policy6
Group
Use this command to add or edit user groups. There are three
types of user groups:
Firewall user group Provides access to firewall policies that require
authentication. A firewall policy specifies the user groups that are
allowed to use the policy. Members of a firewall user group can be local
users defined in user local, peer members defined in user peer, or
accounts on RADIUS or LDAP servers configured in user radius or
user ldap. Users must provide a user name and password to use the
firewall policy.
SSL-VPN user group Provides access to the ZXSEC US SSL-VPN
tunnel and SSL-VPN web applications. Members of an SSL-VPN user
group can be local users defined in user local or accounts on RADIUS
or LDAP servers configured in user radius or user ldap. Users
authenticate using their VPN client or through the SSL-VPN web portal
login page.
Active Directory user group Provides access to firewall policies that
require authentication. Members of an Active Directory user group are
members of selected Active Directory user groups on Active Directory
Note:
User groups can utilize defined peer members as part of a group.
When you add user names, RADIUS servers, and LDAP servers
to a user group, the order in which they are added determines
the order in which the ZXSEC US unit checks for authentication.
If user names are first, then the ZXSEC US unit checks first for a
match with the local user names. If a match is not found, the
ZXSEC US unit checks the RADIUS or LDAP server. If a RADIUS
or LDAP server is added first, the ZXSEC US unit checks the
server and then the local user names.
Syntax
config user group
edit <groupname>
set authtimeout <timeout>
set group-type <grp_type>
set member <names>
set profile <profilename>
Example
This example shows how to add a group named User_Grp_1, and
add User_2, User_3, Radius_2 and
LDAP_1 as members of the group, and set the protection profile
to strict:
config user group edit User_Grp_1
set member User_2 User_3 Radius_2 LDAP_1
Ldap
Use this command to add or edit the definition of an LDAP server
for user authentication.
To authenticate with the ZXSEC US unit, the user enters a user
name and password. The ZXSEC US unit sends this user name
and password to the LDAP server. If the LDAP server can
authenticate the user, the user is successfully authenticated with
the ZXSEC US unit. If the LDAP server cannot authenticate the
user, the connection is refused by the ZXSEC US unit.
The ZXSEC US unit supports LDAP protocol functionality defined
in RFC2251 for looking up and validating user names and
passwords. ZXSEC US LDAP supports all LDAP servers compliant
with LDAP v3.
ZXSEC US LDAP support does not extend to proprietary
functionality, such as notification of password expiration, that is
available from some LDAP servers. ZXSEC US LDAP support does
not supply information to the user about why authentication
failed.
LDAP user authentication is supported for PPTP, L2TP, IPSec VPN,
and firewall authentication. With PPTP, L2TP, and IPSec VPN, PAP
(Packet Authentication Protocol) is supported and CHAP
(Challenge Handshake Authentication Protocol) is not.
Syntax
config user ldap
edit <server_name>
set cnid <id>
set dn <dname>
set port <number>
set server <domain>
set type <auth_type>
set username <ldap_username>
set password <ldap_passwd>
set group <group>
Example
This example shows how to add an LDAP server called LDAP1
using the IP address 23.64.67.44, the default port, the common
name cn, and the distinguished names
ou=marketing,dc=USnet,dc=com for simple authentication.
config user ldap edit LDAP1
set server 23.64.67.44
set cnid cn
set dn ou=marketing,dc=USnet,dc=com
end
This example shows how to change the distinguished name in
the example above to
ou=accounts,ou=marketing,dc=USnet,dc=com.
config user ldap edit LDAP1
set dn ou=accounts,ou=marketing,dc=USnet,dc=com
end
Related topics
user group
user local
user radius
user tacacs+
Local
Use this command to add local user names and configure user
authentication for the ZXSEC US unit. To add authentication by
LDAP or RADIUS server you must first add servers using the
config user ldap and config user radius commands.
Syntax
config user local
edit <username>
set ldap-server <servername>
Keywords and
Description Default
variables
Enter the user name. Enter a new
name to create a new user account
edit <username>
or enter an existing user name to
edit that account.
Enter the name of the LDAP server
with which the user must
authenticate. You can only select an
ldap-server LDAP server that has been added to No
<servername> the list of LDAP servers. See “ldap”.
default.
Keywords and
Description Default
variables
The RADIUS server
specified in
radius
radius-server verifies
the password.
Example
This example shows how to add and enable a local user called
Admin7 for authentication using the RADIUS server RAD1.
config user local
edit Admin7
set status enable
set type radius
set radius-server RAD1
end
This example shows how to change the authentication method
for the user Admin7 to password and enter the password.
config user local
edit Admin7
set type password
set passwd abc123
end
Related topics
user group
user ldap
user radius
user tacacs+
Peer
Use this command to add or edit peer (digital certificate holder)
information. You use the peers you define here in the config
vpn ipsec phase1 command if you specify peertype as peer.
Also, you can add these peers to peer groups you define in the
config user peergrp command.
For PKI user authentication, you can add or edit peer information
and configure use of LDAP server to check access rights for client
certificates.
This command refers to certificates imported into the ZXSEC US
unit. You import CA certificates using the vpn certificate ca
Note:
If you create a PKI user in the CLI with no values in subject or
ca, you cannot open the user record in the GUI, or you will be
prompted to add a value in Subject (subject) or CA (ca).
Syntax
config user peer
edit <peer_name>
set ca <ca_name>
set cn <cn_name>
set cn-type <type>
set ldap-password <ldap_password>
set ldap-server <ldap_server>
set ldap-username <ldap_user>
set subject <constraints>
end
Keywords and
Description Default
variables
Enter the CA certificate name, as
No
ca <ca_name> returned by execute vpn certificate ca
default.
list.
Enter the peer certificate common No
cn <cn_name>
name. default.
Enter the peer certificate common
cn-type <type> string
name type:
Fully-qualified domain
FQDN
name.
email The user’s email address.
The user’s IP address
ipv4
(IPv4).
The user’s IP address
ipv6
(IPv6).
Any other piece of
string
information.
Enter the peer name. Enter a new
edit name to create a new peer or enter No
<peer_name> an existing peer name to edit that default.
peer’s information.
Keywords and
Description Default
variables
ldap-password Enter the login password for the LDAP
No
<ldap_password server used to perform client access
default.
> rights check for the defined peer.
Example
This example shows how to add the branch_office peer.
Configure the peer using the CA certificate name and peer
information:
config user peer
edit branch_office
set ca CA_Cert_1
set cn ouraddress@example2.com
set cn-type email
end
Configure the peer with empty subject and ca fields.
config user peer
edit peer2
end
Related topics
user peergrp
vpn ipsec phase1
vpn certificate ca
vpn certificate local
Peergrp
Use this command to add or edit a peer group. Peers are digital
certificate holders defined using the config user peer command.
You use the peer groups you define here in the config vpn ipsec
phase1 command if you specify peertype as peergrp.
For PKI user authentication, you can add or edit peer group
member information. User groups that use
PKI authentication can also be configured using config user
group.
Syntax
config user peergrp
edit <groupname>
set member <peer_names>
end
Keywords and
Description Default
variables
Enter a new name to create a
new peer group or enter an
edit <groupname>
existing group name to edit that
group.
Enter the names of peers to add
to the peer group. Separate
names by spaces. To add or
member No
remove names from the group
<peer_names> default.
you must re-enter the whole list
with the additions or deletions
required.
Example
This example shows how to add peers to the peergrp
EU_branches.
config user peergrp edit EU_branches
set member Sophia_branch Valencia_branch Cardiff_branch
end
Related topics
user peer
vpn ipsec phase1
vpn l2tp
vpn pptp
Radius
Use this command to add or edit the information used for
RADIUS authentication.
The default port for RADIUS traffic is 1812. If your RADIUS
server is using a different port you can change the default
RADIUS port. You may set a different port for each of your
RADIUS servers.
Keywords and
Description Default
variables
Enter a name to identify the
RADIUS server.
edit Enter a new name to create a new
<server_name> server definition or enter an
existing server name to edit that
server definition.
all-usergroup
{enable | Enable to automatically include this
disable
RADIUS server in all user groups.
disable}
Select the authentication method
auth-type {auto | for this RADIUS server.
chap | ms_chap | auto
ms_chap_v2 | pap} auto uses pap, ms_chap_v2, and
chap.
IP address used as NAS-IP-Address
and
Called-Station-ID attribute in
RADIUS access requests. No
nas-ip <use_ip>
default.
RADIUS setting or IP address of US
interface used to talk with
RADIUS server, if not configured.
Example
This example shows how to add the radius server RAD1 at the IP
address 206.205.204.203 and set the shared secret as
R1a2D3i4U5s.
config user radius
edit RAD1
set secret R1a2D3i4U5s
set server 206.205.204.203
end
Related topics
user group
user ldap
user local
user tacacs+
Settings
Use this command to change per VDOM user settings such as the
firewall user authentication time out and protocol support for
firewall policy authentication.
user settings differ from system global settings in that system
global settings keywords apply to the entire ZXSEC US unit,
where user settings keywords apply only to the user VDOM.
Syntax
config user setting
set auth-cert <cert_name>
set auth-keepalive {enable | disable}
set auth-secure-http {enable | disable}
set auth-type {ftp | http | https | telnet}
set auth-timeout <auth_timeout_minutes>
end
Keywords and
Description Default
variables
HTTPS server certificate for policy
authentication. USnet_Factory,
USnet_Firmware (if applicable to
auth-cert
your ZXSEC US unit), and self- self- sign
<cert_name>
sign are built-in certificates but
others will be listed as you add
them.
Enable to extend the
auth-keepalive authentication time of the session
disable
{enable | disable} through periodic traffic to prevent
an idle timeout.
Keywords and
Description Default
variables
Set the user authentication
auth-type {ftp | protocol support for firewall policy
http | authentication. User controls
https | telnet} which protocols should support
the authentication challenge.
Set the number of minutes before
the firewall user authentication
timeout requires the user to
auth-timeout authenticate again.
<auth_timeout_min The maximum authtimeout 5
utes> interval is 480 minutes (8 hours).
To improve security, keep the
authentication timeout at the
default value of 5 minutes.
Example
This example shows how to enable https user authentication, and
set the firewall user authentication timeout to 15 minutes.
config user setting set auth-type https
set auth-timeout 15
end
Tacacs+
Use this command to add or edit the information used for
TACACS+ authentication.
Terminal Access Controller Access-Control System (TACACS+) is
a remote authentication protocol used to communicate with an
authentication server. TACACS+ allows a client to accept a
username and password and send a query to a TACACS+
authentication server. The server host determines whether to
accept or deny the request and sends a response back that
allows or denies network access to the user.
The default port for a TACACS+ server is 49.
You may select an alternative authentication method for each
server. These include CHAP, PAP, MS- CHAP, and ASCII.
Syntax
config user tacacs+
edit <server_name>
set authen-type {ascii | auto | chap | ms_chap | pap}
set key <server_key>
set tacacs+-port <tacacs+_port_num>
set server <domain>
end
Keywords and
Description Default
variables
Enter a name to identify the
TACACS+ server.
edit Enter a new name to create a new
<server_name> server definition or enter an
existing server name to edit that
server definition.
authen-type {ascii | Select the authentication method
auto for this TACACS+ server.
auto
| chap | ms_chap | auto uses pap, ms_chap_v, and
pap} chap, in that order.
key <server_key> Enter the key to access the server.
Example
This example shows how to add the TACACS+ server TACACS1 at
the IP address 206.205.204.203, set the server key as
R1a2D3i4U5s, and authenticate using PAP.
config user tacacs+
edit TACACS1
set authen-type pap set key R1a2D3i4U5s
set server 206.205.204.203
end
Related topics
user group
user local
user ldap
user radius
Vpn
Overview
Use vpn commands to configure options related to virtual private
networking through the ZXSEC US unit, including:
IPSec operating parameters
a local address range for PPTP or L2TP clients
SSL VPN configuration settings
This chapter contains the following sections:
certificate ca
certificate crl
certificate local
certificate ocsp
certificate remote
ipsec concentrator
ipsec USDesktop
ipsec manualkey
ipsec manualkey-interface
ipsec phase1
ipsec phase1-interface
ipsec phase2
ipsec phase2-interface
l2tp
pptp
ssl monitor
ssl settings
ssl web bookmarks
Certificate ca
Use this command to install Certificate Authority (CA) root
certificates.
When a CA processes your Certificate Signing Request (CSR), it
sends you the CA certificate, the signed local certificate and the
Certificate Revocation List (CRL).
1. The process for obtaining and installing certificates is as
follows:
2. Use the execute vpn certificate local command to
generate a CSR. Send the CSR to a CA. The CA sends you the
CA certificate, the signed local certificate and the CRL.
3. Use the vpn certificate local command to install the
signed local certificate.
4. Use the vpn certificate ca command to install the CA
certificate.
5. Use the vpn certificate crl command to install the
CRL.Depending on your terminal software, you can copy the
certificate and paste it into the command.
Syntax
config vpn certificate ca
edit <ca_name>
set ca <cert>
end
To view all of the information about the certificate, use the get
command:
get vpn certificate ca <ca_name>
<keyword> Description
edit
Enter a name for the CA certificate.
<ca_name>
ca <cert> Enter or retrieve the CA certificate in PEM format.
Related topics
vpn certificate crl
vpn certificate local
vpn certificate ocsp
vpn certificate remote
execute vpn certificate ca
Certificate crl
Use this command to install a Certificate Revocation List (CRL).
When a CA processes your Certificate Signing Request (CSR), it
sends you the CA certificate, the signed local certificate and the
Certificate Revocation List (CRL).
The process for obtaining and installing certificates is as follows:
1. Use the execute vpn certificate local command to
generate a CSR.
2. Send the CSR to a CA.
The CA sends you the CA certificate, the signed local certificate
and the CRL.
3. Use the vpn certificate local command to install the
signed local certificate.
4. Use the vpn certificate ca command to install the CA
certificate.
5. Use the vpn certificate crl command to install the CRL.
Depending on your terminal software, you can copy the
certificate and paste it into the command. The CRL now updates
automatically from a remove server.
Syntax
config vpn certificate crl
edit <crl_name>
set crl <crl_PEM>
set ldap-server <ldap_server_name>
set ldap-username <ldap_username>
set ldap-password <ldap_password>
set scep-cert <scep_certificate>
set scep-url <scep_url>
set update-vdom <update_vdom>
set http-url <http_url>
end
<keyword> Description
edit Enter a name for the Certificate Revocation List
<crl_name> (CRL).
crl <crl_PEM> Enter the CRL in PEM format.
ldap-server
Name of the LDAP server defined in config user ldap
<ldap_server_ table for CRL auto-update.
name>
<keyword> Description
ldap-
username
LDAP login name.
<ldap_userna
me>
ldap-password
<ldap_passwo LDAP login password.
rd>
scep-cert
Local certificate used for SCEP communication for
<scep_certific CRL auto-update.
ate>
scep-url URL of the SCEP server used for automatic CRL
<scep_url> certificate updates. Start with http://.
update-vdom
VDOM used to communicate with remote SCEP
<update_vdo server for CRL auto-update.
m>
http-url URL of an http server used for automatic CRL
<http_url> certificate updates. Start with http://.
Related topics
vpn certificate ca
vpn certificate local
vpn certificate ocsp
vpn certificate remote
execute vpn certificate crl
Certificate local
Use this command to install local certificates.
<keyword> Description
edit <cert_name> Enter the local certificate name.
certificate
Enter the signed local certificate in PEM format.
<cert_PEM>
comments Enter any relevant information about the
<comment_text> certificate.
You should not modify the following variables if you generated the
CSR on this unit.
csr <csr_PEM> The CSR in PEM format.
password <pwd> The password in PEM format.
private-key
The private key in PEM format.
<prkey>
Related topics
vpn certificate ca
vpn certificate crl
vpn certificate ocsp
Certificate ocsp
Use this command to install remote certificates. The remote
certificates are public certificates without a private key. They are
used as OCSP (Online Certificate Status Protocol) server
certificates.
Syntax
<keyword> Description
Enter the OCSP server public certificate (one of
cert <cert_name>
the remote certificates).
url <ocsp_url> Enter the URL of the OCSP server.
unavail-action Action taken on client certification when the
<unavailable_acti OCSP server is unreachable.
on> revokeor ignore. Default is revoke.
Related topics
vpn certificate local
vpn certificate ca
vpn certificate crl
vpn certificate remote
execute vpn certificate remote
Certificate remote
Use this command to install remote certificates. The remote
certificates are public certificates without a private key. They are
used as OCSP (Online Certificate Status Protocol) server
certificates.
Syntax
config vpn certificate remote
edit cert <cert_name>
set remote <remote_cert_detail>
end
To view all of the information about the certificate, use the get
command:
get vpn certificate remote [cert_name]
<keyword> Description
cert <cert_name> Enter the name of the public certificate.
<keyword> Description
remote
<remote_cert_det Details/description of the remote certificate.
ail>
Related topics
vpn certificate local
vpn certificate ca
vpn certificate crl
vpn certificate ocsp
execute vpn certificate remote
Ipsec concentrator
Use this command to add IPSec policy-based VPN tunnels to a
VPN concentrator. The VPN concentrator collects hub-and-spoke
tunnels into a group.
The concentrator allows VPN traffic to pass from one tunnel to
the other through the ZXSEC US unit. The ZXSEC US unit
functions as a concentrator, or hub, in a hub-and-spoke network.
Note:
VPN concentrators are not available in Transparent mode.
Syntax
config vpn ipsec concentrator edit <concentrator_name>
set member <member_name> [<member_name>] [<member_name>]
end
Note:
The member keyword is required.
Example
Use the following commands to add an IPSec VPN concentrator
named Concen_1 and add three tunnels to the concentrator.
config vpn ipsec concentrator
edit Concen_1
set member Tunnel_1 Tunnel_2 Tunnel_3
end
Related topics
vpn ipsec phase1
vpn ipsec manualkey
Ipsec USDesktop
Use this command to configure automatic VPN configuration for
USDesktop Host Security application users.
The USDesktop users who will use automatic configuration must
be members of a user group. The config vpn ipsec USDesktop
command creates a “realm” that associates the user group with
the phase 2 VPN configuration. You can create multiple realms to
associate different user groups with different phase 2
configurations.
The user group identifies the user name and password settings
that the dialup client’s credentials must match in order for
authentication to be successful. The phase 2 tunnel definition
and its associated firewall encryption policy provides the
configuration parameters to download to the USDesktop Host
Security application.
Syntax
Set or unset VPN policy distribution parameters.
config vpn ipsec USDesktop
edit <realm_name>
Example
The following example enables VPN policy distribution for a user
group called Dialup_users. The phase 2 tunnel configuration
named US1toDialup_tunnel provides the ZXSEC US unit with
the information it needs to find and apply the associated firewall
encryption policy:
config vpn ipsec USDesktop
edit Standard_VPN_policy
set phase2name US1toDialup_tunnel
set usergroupname Dialup_users
set status enable
end
Related topics
vpn ipsec phase2
user group
Ipsec manualkey
Use this command to configure manual keys for IPSec tunnel-
mode VPN tunnels. You configure a manual key tunnel to create
an IPSec tunnel-mode VPN tunnel between the ZXSEC US unit
and a remote IPSec VPN client or gateway that is also using
manual key.
A manual key VPN tunnel consists of a name for the tunnel, the
IP address of the VPN gateway or client at the opposite end of
the tunnel, and the encryption and authentication algorithms to
use for the tunnel. Because the keys are created when you
configure the tunnel, no negotiation is required for the VPN
tunnel to start. However, the VPN gateway or client that connects
to this tunnel must use the same encryption and authentication
algorithms and must have the same encryption and
authentication keys.
Syntax
config vpn ipsec manualkey
edit <tunnel_name>
set authentication <authentication_algorithm>
set authkey <authentication_key>
set encryption <method>
set enckey <encryption_key>
set interface <interface_name>
set localspi <local_spi_number>
set local-gw <address_ipv4>
set remote-gw <address_ipv4>
set remotespi <remote_spi_number>
end
The authentication, encryption, interface, remote-gw,
localspi, and remotespi keywords are required. All other
keywords are optional.
encryption aes256
null
<method> des
null
Make sure you use the same
algorithm at both ends of the
tunnel. encryption and
authentication cannot both be
null.
Example
Use the following command to add an IPSec VPN manual key
tunnel with the following characteristics:
Tunnel name: Manual_Tunnel
Local SPI: 1000ff
Remote SPI: 2000ff
Remote gateway IP address: 206.37.33.45
Encryption algorithm: 3DES
Encryption keys: 003f2b01a9002f3b 004f4b0209003f01
3b00f23bff003eff
Authentication algorithm: MD5
Authentication keys: ff003f012ba900bb 00f402303f0100ff
config vpn ipsec manualkey
edit Manual_Tunnel
set localspi 1000ff
set remotespi 2000ff
set remote-gw 206.37.33.45
set encryption 3des
set enckey 003f2b01a9002f3b-004f4b0209003f01-
3b00f23bff003eff set authentication md5
set authkey ff003f012ba900bb-00f402303f0100ff
end
Related topics
vpn ipsec phase2
Ipsec manualkey-interface
Use this command to configure manual keys for a route-based
(interface mode) IPSec VPN tunnel. When you create a route-
based tunnel, the ZXSEC US unit creates a virtual IPSec interface
automatically. The interface can be modified afterward using the
system network interface CLI command. This command is
available only in NAT/Route mode.
Syntax
config vpn ipsec manualkey-interface
edit <tunnel_name>
set auth-alg <authentication_algorithm>
set auth-key <authentication_key>
set enc-alg <method>
set enc-key <encryption_key>
set interface <interface_name>
set ip-version <4 | 6>
set local-gw <address_ipv4>
set local-gw6 <address_ipv6>
set local-spi <local_spi_number>
set remote-gw <address_ipv4>
set remote-gw6 <address_ipv6>
set remote-spi <remote_spi_number>
end
Note:
The auth-alg, enc-alg, interface, remote-gw, local-spi, and
remote-spi keywords are required. All other keywords are
optional.
Example
Use the following command to add a route-based (interface-
mode) IPSec VPN tunnel having the following characteristics:
Tunnel name: Manual-inf_tunnel
Local SPI: 1000ff
Remote SPI: 2000ff
VLAN interface name: vlan_1
Remote gateway IP address: 206.37.33.45
Encryption algorithm: 3DES
Encryption keys: 003f2b01a9002f3b 004f4b0209003f01--
3b00f23bff003eff
Authentication algorithm: MD5
Authentication keys: ff003f012ba900bb 00f402303f0100ff
config vpn ipsec-intf manualkey-interface edit Manual-inf_tunnel
set auth-alg md5
set auth-key ff003f012ba900bb-00f402303f0100ff set enc-alg 3des
set enc-key 003f2b01a9002f3b-004f4b0209003f01-
3b00f23bff003eff set interface vlan_1
set local-spi 1000ff set remote-spi 2000ff
set remote-gw 206.37.33.45
end
Related topics
Ipsec phase1
Use this command to add or edit IPSec tunnel-mode phase 1
configurations. When you add a tunnel- mode phase 1
configuration, you define how the ZXSEC US unit and a remote
VPN peer (gateway or client) authenticate themselves to each
other as part of establishing an IPSec VPN tunnel.
The phase 1 configuration specifies the name of a remote VPN
peer, the nature of the connection (static IP, dialup, or dynamic
DNS), the encryption and authentication keys for the phase 1
proposal, and the authentication method (preshared key or
certificate). For authentication to be successful, the ZXSEC US
unit and the remote VPN peer must be configured with
compatible phase 1 settings.
You can change all settings except the type setting after you
define the configuration: if the address type of a remote peer
changes, you must delete the original phase 1 configuration and
define a new one. As a general rule, create only one phase 1
configuration per remote VPN peer.
syntax
config vpn ipsec phase1
edit <gateway_name>
set add-gw-route {enable | disable}
set authmethod <authentication_method>
set authpasswd <password>
set authusr <user_name>
set authusrgrp <group_name>
set dhgrp {1 2 5}
set dpd {disable | enable}
set dpd-retrycount <retry_integer>
set dpd-retryinterval <seconds> [<milliseconds>]
set interface <interface_name>
set keepalive <seconds>
set keylife <seconds>
set local-gw <address_ipv4>
set localid <local_id>
set mode {aggressive | main}
set nattraversal {disable | enable}
set peer <CA_certificate_name>
Note:
In NAT/Route mode, the interface keyword is required. A
remote-gw value may be required depending on the value of the
type attribute. You must also enter a preshared key or a
certificate name depending on the value of authmethod. All
other keywords are optional.
Example
Use the following command to add a tunnel-mode IPSec VPN
phase 1 configuration with the following characteristics:
Phase 1 configuration name: Simple_GW
Physical interface name: port6
Remote peer address type: Dynamic
Encryption and authentication proposal: des-md5
Authentication method: psk
Pre-shared key: Qf2p3O93jIj2bz7E
Mode: aggressive
Dead Peer Detection: disable
config vpn ipsec phase1
edit Simple_GW
set interface port6
set type dynamic
set proposal des-md5
set authmethod psk
set psksecret Qf2p3O93jIj2bz7E
set mode aggressive set dpd disable
end
Related topics
vpn ipsec phase2
user group
user local
user peer
user peergrp
user radius
execute vpn certificate local
vpn certificate ca
Ipsec phase1-interface
Use this command to define a phase 1 definition for a route-
based (interface mode) IPSec VPN tunnel that generates
authentication and encryption keys automatically. A new
interface of type “tunnel” with the same name is created
automatically as the local end of the tunnel. To complete the
configuration of an IPSec tunnel, you need to:
configure phase 2 settings
configure a firewall policy to pass traffic from the local
private network to the tunnel interface
configure a static route to the private network at the remote
end of the tunnel using the IPSec tunnel“device”
optionally, define the IP addresses for each end of the tunnel
to enable dynamic routing through the tunnel or to enable
pinging of each end of the tunnel for testing
syntax
config vpn ipsec phase1-interface
edit <gateway_name>
set add-gw-route {enable | disable}
set authmethod <authentication_method>
set authpasswd <password>
set authusr <user_name>
set authusrgrp <group_name>
set dhgrp {1 2 5}
set dpd {disable | enable}
set dpd-retrycount <retry_integer>
set dpd-retryinterval <seconds> [<milliseconds]
Note:
The interface keyword is required. A remote-gw value may be
required depending on the value of the type attribute. You must
also enter a preshared key or a certificate name depending on
the value of authmethod. All other keywords are optional.
Example
In this example, an IPSec tunnel is needed between two sites
using ZXSEC US units. Users on the 192.168.2.0/24 network at
Site A need to communicate with users on the 192.168.3.0/24
network at Site B. At Site A, the public IP address is
172.16.67.199 and at Site B it is 172.16.68.198. At both ends:
Port 2 of the ZXSEC US unit: connects to the private network
user radius
vpn certificate local
vpn certificate ca
Ipsec phase2
Use this command to add or edit an IPSec tunnel-mode phase 2
configuration. The ZXSEC US unit uses the tunnel-mode phase 2
configuration to create and maintain an IPSec VPN tunnel with a
remote VPN peer (the VPN gateway or client).
The phase 2 configuration consists of a name for the VPN tunnel,
the name of an existing phase 1 configuration, the proposal
settings (encryption and authentication algorithms) and DH
group used for phase 2. For phase 2 to be successful, the ZXSEC
US unit and the remote VPN peer must be configured with
compatible proposal settings.
syntax
config vpn ipsec phase2
edit <tunnel_name>
set auto-negotiate {enable | disable}
set dhcp-ipsec {disable | enable}
set dhgrp {1 | 2 | 5}
set dst-addr-type <type>
set dst-end-ip <address_ipv4>
set dst-name <address_name>
set dst-port <destination_port_number>
set dst-start-ip <address_ipv4>
set dst-subnet <address_ipv4mask>
set keepalive {disable | enable}
set keylife-type <keylife_type>
set keylifekbs <kb_integer>
set keylifeseconds <seconds>
set pfs {disable | enable}
set phase1name <gateway_name>
set proposal <encryption_combination>
set protocol <protocol_integer>
set replay {disable | enable}
set route-overlap {overlap_option}
set selector-match <match_type>
Note:
The phase1name keyword is required. All other keywords are
optional.
Example
Use the following command to add a tunnel-mode phase 2
configuration with the following characteristics:
Name: New_Tunnel
Phase 1 name: Simple_GW
Encryption and authentication proposal: 3des-sha1
des-md5
aes256-sha1
Keylife type: seconds
Keylife seconds: 18001
Diffie-Hellman group: 2
Replay detection: enable
Perfect forward secrecy: enable
Keepalive: enable
Authentication keys: ff003f012ba900bb
00f402303f0100ff
config vpn ipsec phase2
Ipsec phase2-interface
Use this command to add a phase 2 configuration for a route-
based (interface mode) IPSec tunnel or edit an existing
interface-mode phase 2 configuration. This command is available
only in NAT/Route mode.
Syntax
config vpn ipsec phase2-interface
edit <tunnel_name>
set auto-negotiate {enable | disable}
set dhgrp {1 | 2 | 5}
set dst-addr-type <type>
set dst-end-ip <address_ipv4>
set dst-end-ip6 <address_ipv6>
set dst-name <address_name>
set dst-port <destination_port_number>
set dst-start-ip <address_ipv4>
set dst-start-ip6 <address_ipv6>
set dst-subnet <address_ipv4mask>
set dst-subnet6 <address_ipv6mask>
Note:
The phase1name keyword is required. All other keywords are
optional.
Example
L2tp
Use this command to enable L2TP and specify a local address
range to reserve for remote L2TP clients. When a remote L2TP
client connects to the internal network through a L2TP VPN, the
client is assigned an IP address from the specified range.
L2TP clients must authenticate with the ZXSEC US unit when a
L2TP session starts. To support L2TP authentication on the
ZXSEC US unit, you must define the L2TP users who need
access and then add them to a user group. For more information,
see “user group”, “user ldap”, “user local”, and “user radius”.
You need to define a firewall policy to control services inside the
L2TP tunnel. For more information, see “firewall”. When you
define the firewall policy:
Create an “external -> internal” policy.
Set the source address to match the L2TP address range.
Set the destination address to reflect the private address
range of the internal network behind the local ZXSEC US unit.
Set the policy service(s) to match the type(s) of traffic that
L2TP users may generate.
Set the policy action to accept.
Enable NAT if required.
Caution:
ZXSEC US units support L2TP with Microsoft Point-to-Point
Encryption (MPPE) encryption only. Later implementations of
Microsoft L2TP for Windows use IPSec and require certificates for
authentication and encryption. If you want to use Microsoft L2TP
with IPSec to connect to a ZXSEC US unit, the IPSec and
certificate elements must be disabled on the remote client. For
more information, see the Disabling Microsoft L2TP for IPSec
article in the USnet Knowledge Center.
syntax
config vpn l2tp
set eip <address_ipv4>
set sip <address_ipv4>
set status {disable | enable}
set usrgrp <group_name>
end
Note:
You can configure L2TP VPNs on ZXSEC US units that run in
NAT/Route mode. The commands are available in NAT/Route
mode only. When you configure an L2TP address range for the
first time, you must enter a starting IP address, an ending IP
address, and a user group.
Example
This example shows how to enable L2TP and set the L2TP
address range for the first time using a starting address of
192.168.1.150, an ending address of 192.168.1.160 and an
existing group of L2TP users named L2TP_users:
config vpn l2tp
set sip 192.168.1.150
set eip 192.168.1.160
set status enable
set usrgrp L2TP_users
end
Related topics
user group
firewall policy, policy6
Pptp
Use this command to enable PPTP and specify a local address
range to reserve for remote PPTP clients. When a remote PPTP
client connects to the internal network through a PPTP VPN, the
client is assigned an IP address from the specified range.
PPTP clients must authenticate with the ZXSEC US unit when a
PPTP session starts. To support PPTP authentication on the
ZXSEC US unit, you must define the PPTP users who need
access and then add them to a user group. For more information,
see “user group”, “user ldap”,“user local”, and “user radius”.
You need to define a firewall policy to control services inside the
PPTP tunnel. For more information, see “firewall”. When you
define the firewall policy:
Create an “external -> internal” policy.
Set the source address to match the PPTP address range.
Note:
You can configure PPTP VPNs on ZXSEC US units that run in
NAT/Route mode. The commands are available in NAT/Route
mode only. When you configure an L2TP address range for the
first time, you must enter a starting IP address, an ending IP
address, and a user group.
Example
This example shows how to enable PPTP and set the PPTP
address range for the first time using a starting address of
192.168.1.100, an ending address of 192.168.1.130 and an
existing group of PPTP users named PPTP_users:
config vpn pptp
set sip 192.168.1.100
Ssl monitor
Use this command to display information about logged in SSL
VPN users and current SSL VPN sessions.
syntax
get vpn ssl monitor
Output
Related topics
vpn ssl settings
Ssl settings
Use this command to configure basic SSL VPN settings including
interface idle-timeout values and SSL encryption preferences. If
required, you can also enable the use of digital certificates for
authenticating remote clients.
You can optionally specify the IP address of any Domain Name
Service (DNS) server and/or Windows Internet Name Service
(WINS) server that resides on the private network behind the
ZXSEC US unit. The DNS and/or WINS server will find the IP
addresses of other computers whenever a connected SSL VPN
user sends an email message or browses the Internet.
Note:
You can configure SSL VPNs on ZXSEC US units that run in
NAT/Route mode. The commands are available in NAT/Route
mode only.
syntax
config vpn ssl settings
set algorithm <cipher_suite>
set auth-timeout <auth_seconds>
set dns-server1 <address_ipv4>
Note:
Set the sslvpn-enable attribute to enable to view all possible
settings. The tunnel-endip and tunnel-startip keywords are
required for tunnel-mode access only. All other keywords are
optional.
Example
The following command enables the ZXSEC US unit to assign
virtual IP addresses in the 10.10.10.100 to 10.10.10.105 range
to authenticated clients (an IP address range is needed to
support tunnel-mode access). The command also sets timeout
values for authenticated connections and connection inactivity
respectively.
config vpn ssl settings
set sslvpn-enable enable
set tunnel-startip 10.10.10.100
set tunnel-endip 10.10.10.105
Example
The following command creates a bookmark named
Company_intranet to the corporate Intranet home page at
www.example.com:
config vpn ssl web bookmarks edit Company_intranet
set apptype web set url http://www.example.com
end
Related topics
vpn ssl settings
vpn ssl web bookmarks-group
vpn ssl web favorite
Note:
The user, group and title keywords are required. Other keywords
might be required depending on apptype. See Variables
description above.
Example
The following command creates a bookmark group that includes
the bookmark to the corporate Intranet home page at
www.example.com named Company_intranet and a link to the
Google search site named Google_site:
config vpn ssl web bookmarks-group
edit <bkmark_groupname>
set “Company_intranet” “Google_site”
end
Related topics
vpn ssl settings
vpn ssl web bookmarks
vpn ssl web favorite
Example
The following command creates a bookmark to the corporate
Intranet home page at www.example.com for the user juser who
is a member of the SSL VPN user group sslusergroup:
Chapter 16
Webfilter
Overview
Use webfilter commands to add banned words to the banned word list,
filter URLs, and configure Usservice-Web category filtering.
This chapter contains the following sections:
Bword
Exmword
Usservice
ussrv-local-cat
ussrv-local-rating
ussrv-ovrd
urlfilter
Bword
Control web content by blocking specific words or patterns. If enabled in
the protection profile, the ZXSEC US unit searches for words or patterns
on requested web pages. If matches are found, values assigned to the
words are totalled. If a user-defined threshold value is exceeded, the web
page is blocked.
Use this command to add or edit and configure options for the Web
content block list. Banned words can be one word or a text string up to 80
characters long. The maximum number of banned words and patterns in
the list is 9000.
When a single word is entered, the ZXSEC US unit checks Web pages for
that word. Add phrases by enclosing the phrase in ‘single quotes’. When a
phrase is entered, the ZXSEC US unit checks Web pages for any word in
the phrase. Add exact phrases by enclosing the phrases in “quotation
marks”. If the phrase is enclosed in quotation marks, the ZXSEC US
checks Web pages for the exact phrase.
Note:
Perl regular expression patterns are case sensitive for Web Filter content
block. To make a word or phrase case insensitive, use the regular
expression /i. For example, /bad language/i blocks all instances of bad
language regardless of case. Wildcard patterns are not case sensitive.
syntax
config webfilter bword
edit <banned_word_list_integer>
set name <banned_word_list>
set comment <banned_word_list_comment>
config entries edit <word_str>
set lang {french | japanese | korean | simch | thai | trach |
western}
set pattern-type {regexp | wildcard}
set score <integer_value>
set status {enable | disable}
end
Keywords and
Description Default
variables
<banned_word_list_ A unique number to identify the
integer> banned word list.
<banned_word_list
The name of the banned word list.
>
<banned_word_list_ The comment attached to the
comment> banned word list.
<word_str> The word to be blocked.
Enter the language character set
lang {french | used for the banned word or
japanese | korean | phrase. Choose from French,
western
simch | thai | trach | Japanese, Korean, Simplified
western} Chinese, Thai, Traditional Chinese,
or Western.
Set the pattern type for the
pattern-type banned word. Choose from regexp
or wildcard.Create patterns for wildcard
{regexp | wildcard} banned words using Perl regular
expressions or wildcards.
Keywords and
Description Default
variables
A numerical weighting applied to
the banned word. The score values
of all the matching words
appearing on a web page are
added, and if the total is greater
than the webwordthreshold value
score set in the protection profile, the
page is processed according to 10
<integer_value>
whether the bannedword option is
set with the http command in the
protection profile. The score for a
banned word is counted once even
if the word appears multiple times
on the web page.
status {enable | Enable or disable the banned
disable
disable} word.
Related topics
exmword
webfilter Usservice
webfilter ussrv-local-cat
webfilter ussrv-local-rating
webfilter ussrv-ovrd
webfilter urlfilter
Exmword
Web content exempt allows overriding of the web content block feature. If
any patterns defined in the web content exempt list appear on a web page,
the page will not be blocked even if the web content block feature would
otherwise block it.
Use this command to add or edit and configure options for the Web
content exempt list. Exempt words can be one word or a text string up to
80 characters long. The maximum number of exempt words and patterns
in the list is 9000.
When a single word is entered, the ZXSEC US unit checks Web pages for
that word. Add phrases by enclosing the phrase in ‘single quotes’. When a
phrase is entered, the ZXSEC US unit checks Web pages for any word in
the phrase. Add exact phrases by enclosing the phrases in “quotation
marks”. If the phrase is enclosed in quotation marks, the ZXSEC US
checks Web pages for the exact phrase.
Create exempt word patterns using wildcards or Perl regular expressions.
See “Using Perl regular expressions”.
You can add multiple exempt word lists, and then select the best web
content exempt list for each protection profile. Choose the command
syntax list below according to your ZXSEC US unit model.
Note:
Perl regular expression patterns are case sensitive for Web Filter content
exempt. To make a word or phrase case insensitive, use the regular
expression /i. For example, /good language/i exempts all instances of
good language regardless of case. Wildcard patterns are not case sensitive.
syntax
config webfilter exmword
edit <exempt_word_list_integer>
set name <exempt_word_list>
set comment <exempt_word_list_comment>
config entries
edit <word_str>
set lang {french | japanese | korean | simch | thai | trach |
western}
set pattern-type {regexp | wildcard}
set status {enable | disable}
end
Keywords and
Description Default
variables
<exempt_word_list_ A unique number to identify the
integer> exempt word list.
<exempt_word_list
The name of the exempt word list.
>
<exempt_word_list_ The comment attached to the
comment> exempt word list.
<word_str> The word to be exempted.
Enter the language character set
lang {french | used for the exempt word or
japanese | korean | phrase. Choose from French,
western
simch | thai | trach | Japanese, Korean, Simplified
western} Chinese, Thai, Traditional Chinese,
or Western.
Set the pattern type for the
pattern-type exempt word. Choose from regexp
or wildcard.Create patterns for wildcard
{regexp | wildcard} exempt words using Perl regular
expressions or wildcards.
status {enable | Enable or disable the exempt
disable
disable} word.
Related topics
bword
webfilter Usservice
webfilter ussrv-local-cat
webfilter ussrv-local-rating
webfilter ussrv-ovrd
webfilter urlfilter
Usservice
Use this command to enable Web filtering by specific categories using
Usservice-Web URL filtering.
Usservice-Web category blocking
Usservice-Web is a web filtering solution provided by USnet. Usservice-
Web sorts thousands of Web pages into a wide variety of categories that
users can allow, block, or monitor. Categories are also organized into
broader groups to make configuration fast and easy. The ZXSEC US unit
accesses the nearest Usservice-Web server to determine the category of a
requested web page and then follows the firewall policy configured for that
user or interface. Usservice-Web servers are located worldwide.
Usservice-Web licensing
Every ZXSEC US unit comes with a free 30 day Usservice-Web trial license.
Usservice-Web license management is done by the Usservice-Web server,
so there is no need to enter a license number.
The ZXSEC US unit automatically contacts the Usservice-Web servers
when Usservice-Web category blocking is enabled.
To renew the Usservice-Web license after the free trial, contact USnet
Technical Support.
Usservice-Web configuration
Once enabled, Usservice-Web category block settings apply globally. After
enabling Usservice-Web, configure different categories for each firewall
protection profile create.
See “firewall profile” to configure Usservice-Web category blocking in a
protection profile. See “Usservice-Web categories” in the ZXSEC US
Administration Guide for a complete list and description of the Usservice-
Web web filter categories.
HTTP and HTTPS Usservice override traffic
The Usservice override for HTTP and HTTPS is no longer a single global
forward rule. Instead, a separate rule is created for each protection profile
to redirect both the Usservice override HTTP and HTTPS ports, as required,
into the authentication daemon. This ensures that these ports only appear
open when the appropriate options are enabled in the profile. A matrix of
how the profile options affect the port status follows:
There are two separate ports for HTTP and HTTPS override traffic which
can be configured independently.
In addition, HTTPS uses the HTTPS override form regardless of the ovrd-
auth-https status. If ovrd-auth-https is enabled, any attempts to use the
HTTP version of the override form will transparently be re-directed to the
HTTPS version.
syntax
config webfilter Usservice
set cache-mode {ttl | db-ver}
set cache-mem-percent <percent_integer> set ovrd-auth-port-http <port_integer>
set ovrd-auth-https <enable | disable> set ovrd-auth-port-https <port_integer>
set cache-prefix-match <enable | disable>
end
Keywords and
Description Default
variables
Keywords and
Description Default
variables
Change the cache entry
expiration mode. Choices are ttl
or db-ver.
Using ttl, cache entries are
deleted after a number of
seconds determined by the
cache-mode {ttl | cache-ttlsetting, or until newer
ttl
db-ver} cache entries force the removal
of older ones.
When set to db-ver, cache
entries are kept until the
Usservice database changes, or
until newer cache entries force
the removal of older ones.
Change the maximum
cache-mem-percent percentage of memory the
2
<percent_integer> cache will use. Enter a value
from 1 to 15 percent.
The port to use for Usservice
ovrd-auth-port-http
Web Filter HTTP 8008
<port_integer>
override authentication.
ovrd-auth-https Enable to use HTTPS for
disable
<enable | disable> override authentication.
Related topics
webfilter bword
webfilter ussrv-local-cat
webfilter ussrv-local-rating
webfilter ussrv-ovrd
webfilter urlfilter
Ussrv-local-cat
Use this command to add local categories to the global URL category list.
The categories defined here appear in the global URL category list when
configuring a protection profile. Users can rate URLs based on the local
categories.
syntax
config webfilter ussrv-local-cat edit <local_cat_str>
set id <id_integer>
end
Keywords and
Description Default
variables
The description of the local
<local_cat_str>
category.
The local category unique ID
id <id_integer> 0
number.
Example
This example shows how to add the category local_block with an ID of 10.
config webfilter ussrv-local-cat
edit local_block
set id 10
end
Related topics
webfilter bword
webfilter Usservice
webfilter ussrv-local-rating
webfilter ussrv-ovrd
webfilter urlfilter
Ussrv-local-rating
Use this command to rate URLs using local categories.
Users can create user-defined categories then specify the URLs that belong
to the category. This allows users to block groups of web sites on a per
profile basis. The ratings are included in the global URL list with associated
categories and compared in the same way the URL block list is processed.
The user can also specify whether the local rating is used in conjunction
with the Usservice rating or is used as an override.
syntax
config webfilter ussrv-local-rating edit <local_url_str>
Keywords and
Description Default
variables
<local_url_str> The URL being rated.
Example
This example shows how to configure a local rating for the web site
www.example.com. with a rating including category 12, all categories in
group 4, and classification 1.
config webfilter ussrv-local-rating edit www.example.com
set rating 12 g4 c1
end
Related topics
webfilter bword
webfilter Usservice
webfilter ussrv-local-cat
webfilter ussrv-ovrd
webfilter urlfilter
Ussrv-ovrd
Use this command to configure Usservice-Web filtering overrides.
Users may require access to web sites that are blocked by a policy. In this
case, an administrator can give the user the ability to override the block
for a specified period of time.
When a user attempts to access a blocked site, if override is enabled, a
link appears on the block page directing the user to an authentication form.
The user must provide a correct user name and password or the web site
remains blocked. Authentication is based on user groups and can be
performed for local, RADIUS, and LDAP users.
syntax
config webfilter ussrv-ovrd edit <override_integer>
set expires
Keywords and
Description Default
variables
The unique ID number of the
<override_integer>
override.
The date and time the override
expires
expires.
ext-ref <allow | Allow or deny access to off-site
allow
deny> URLs.
The user who initiated the override
initiator
rule. This keyword is get- only.
When the scope is IP, the IP
ip <ipv4_address> address for which the override rule 0.0.0.0
applies.
When the scope is profile, the
profile <profile_str> profile for which the override rule
applies.
Keywords and
Description Default
variables
The URL for which the override
url <url_str>
rule applies.
When the scope is user, the user
user <user_str>
for which the override rule applies.
Example
This example shows how to set an override (13).
config webfilter ussrv-ovrd
edit 13
set rating 12 g4 c1
end
Use the following command to get information about an override.
get webfilter ussrv-ovrd 1
id :1
expires : Wed Jul 6 07:00:30 2005
ext_ref : allow initiator : admin scope : user status : enable type : dir
url : 192.168.2201.23
user : user_1
Related topics
webfilter bword
webfilter Usservice
webfilter ussrv-local-cat
webfilter ussrv-local-rating
webfilter urlfilter
Urlfilter
Use this command to control access to specific URLs by adding them to the
URL filter list. The ZXSEC US unit exempts or blocks Web pages matching
any specified URLs and displays a replacement message instead.
Configure the ZXSEC US unit to allow, block, or exempt all pages on a
website by adding the top-level URL or IP address and setting the action to
allow, block, or exempt.
Block individual pages on a website by including the full path and filename
of the web page to block. Type a top-level URL or IP address to block
access to all pages on a website. For example, www.example.com or
172.16.144.155 blocks access to all pages at this website.
Type a top-level URL followed by the path and filename to block access to
a single page on a website. For example, www.example.com/news.html or
172.16.144.155/news.html blocks the news page on this website.
To block all pages with a URL that ends with example.com, add
example.com to the block list. For example, adding example.com blocks
access to www.example.com, mail.example.com,
www.finance.example.com, and so on.
Use this command to exempt or block all URLs matching patterns created
using text and regular expressions (or wildcard characters). For example,
example.* matches example.com, example.org, example.net and so on.
The ZXSEC US unit exempts or blocks Web pages that match any
configured pattern and displays a replacement message instead.
The maximum number of entries in the list is 9000.
syntax
config webfilter urlfilter
edit <url_filter_list_integer>
set name <urlfilter_list>
set comment <urlfilter_list_comment>
config entries edit <url_str>
set action {allow | block | exempt}
set status {enable | disable}
set type {simple | regex}
end
end
Keywords and
Description Default
variables
<url_filter_list_integ A unique number to identify the
er> URL filter list.
<urlfilter_list> The name of the URL filter list.
<urlfilter_list_comm The comment attached to the URL
ent> filter list.
<url_str> The URL to added to the list.
The action to take for matches.
An allow match exits the URL filter
list and checks the other web
action filters.
{allow | block | An exempt match stops all further exempt
exempt} checking including AV
scanning.
A block match blocks the URL and
no further checking will be done.
status {enable |
The status of the filter. enable
disable}
Keywords and
Description Default
variables
type {simple | The type of URL filter: simple or
simple
regex} regular expression.
Related topics
webfilter bword
webfilter Usservice
webfilter ussrv-local-cat
webfilter ussrv-local-rating
webfilter ussrv-ovrd
Execute
Overview
The execute commands perform immediate operations on the
ZXSEC US unit. You can:
Back up and restore the system configuration, or reset the
unit to factory settings.
Execute the run but not save feature
Set the unit date and time.
View and clear DHCP leases.
Clear arp table entries.
View and delete log messages. Delete old log files.
Manually dial or hang up the modem (models 70, 120 only).
Use ping or traceroute to diagnose network problems.
Restart the router or the entire ZXSEC US unit.
Update the antivirus and attack definitions on demand.
Generate certificate requests and install certificates for VPN
authentication.
This chapter contains the following sections:
backup
batch
central-mgmt
CUS reload
CUS save
clear system arp table
cli status-msg-only
cli check-template-status
date
deploy
dhcp lease-clear
dhcp lease-list
disconnect-admin-session
factoryreset
formatlogdisk
Usservice-log update
fsae refresh
ha disconnect
ha manage
ha synchronize
interface dhcpclient-renew
interface pppoe-reconnect
log delete-all
log delete-filtered
log delete-rolled
log display
log filter
log USanalzyer test-connectivity
log list
log roll
modem dial
modem hangup
mrouter clear
ping
ping-options
ping6
reboot
restore
router clear bgp
router clear bfd
router clear ospf process
router restart
send-fds-statistics
set-next-reboot
shutdown
ssh
telnet
time
traceroute
update-av
update-ips
update-now
upd-vd-license
usb-disk
vpn certificate ca
vpn certificate crl
vpn certificate local
vpn certificate remote
vpn sslvpn del-tunnel
vpn sslvpn del-web
Backup
Back up the ZXSEC US configuration files, logs, or IPS user-
defined signatures file to a TFTP server. When virtual domain
configuration is enabled (in system global, vdom-admin is
enabled), the content of the backup file depends on the
administrator account that created it.
A backup of the system configuration from the super admin
account contains the global settings and the settings for all
of the VDOMs. Only the super admin can restore the
configuration from this file.
When you back up the system configuration from a regular
administrator account, the backup file contains the global
settings and the settings for the VDOM to which the
administrator belongs. Only a regular administrator account
can restore the configuration from this file.
syntax
execute backup {disk | memory} alllogs <tftp_ipv4>
execute backup config tftp <filename> <tftp_ipv4> [<password>]
execute backup config usb <filename> [<password>]
execute backup full-config tftp <filename> <tftp_ipv4> [<password>]
execute backup full-config usb <filename> [<password>]
execute backup ipsuserdefsig <filename> <tftp_ipv4>
execute backup {disk | memory} log <tftp_ipv4> <log_type>
Example
This example shows how to backup the ZXSEC US unit system
configuration to a file named US.CUS on a TFTP server at IP
address 192.168.1.23. execute backup config tftp USt.CUS
192.168.1.23
Related topics
execute restore
ips custom
Batch
Execute a series of CLI commands.
Note:
execute batch commands are controlled by the Maintenance
(mntgrp) access control group.
Syntax
execute batch [<cmd_cue>]
where <cmd_cue> is one of:
end - exit session and run the batch commands
lastlog - read the result of the last batch commands
start - start batch mode
status - batch mode status reporting if batch mode is
running or stopped
Example
To start batch mode:
execute batch start Enter batch mode...
To enter commands to run in batch mode:
config system global
set refresh 5
end
To execute the batch commands:
execute batch end Exit and run batch commands...
CUS reload
Use this command to restore the saved configuration when the
configuration change mode is manual or revert. This command
has no effect if the mode is automatic, the default. The set CUS-
save command in system global sets the configuration change
mode.
When you reload the saved system configuration, the your
session ends and the ZXSEC US unit restarts.
CUS save
Use this command to save configuration changes when the
configuration change mode is manual or revert. If the mode is
automatic, the default, all changes are added to the saved
configuration as you make them and this command has no effect.
The set CUS-save command in system global sets the
configuration change mode.
In manual mode, commands take effect but do not become part
of the saved configuration unless you execute the execute CUS
save command. When the ZXSEC US unit restarts, the saved
configuration is loaded. Configuration changes that were not
saved are lost.
The revert mode is similar to manual mode, except that
configuration changes are saved automatically if the
administrative session is idle for more than a specified timeout
Cli status-msg-only
Enable standardized CLI error output messages. If executed, this
command stops other debug messages from displaying in the
current CLI session.
Syntax
exec cli status-msg-only <enable | disable>
The message format is:
[error code]: text message
There are two error categories: Keyword Error, and Data Error.
The error code provides details about the type of error.
An ERROR message indicates that the command generated an
error. A Keyword Error [1000x] indicates that the keyword is not
supported, or the attempted command is not recognized. A Data
Error [2000x] indicates that the data source is already in use.
Keywords and
Description
variables
status-msg-only
<enable | Enables standardized CLI error output
messages.
disable>
Cli check-template-status
Reports the status of the SCP script template.
Syntax
exec cli check-template-status
Date
Get or set the system date.
Syntax
execute date [<date_str>]
date_str has the form yyyy-mm-dd, where
yyyy is the year and can be 2001 to 2037
mm is the month and can be 01 to 12
dd is the day of the month and can be 01 to 31
If you do not specify a date, the command returns the current
system date. Shortened values, such as
‘ 06’ instead of ‘2006’ for the year or ‘1’ instead of ‘01’ for
month or day, are not valid.
Example
This example sets the date to 17 September 2004:
execute date 2004-09-17
Related topics
execute time
Dhcp lease-clear
Clear all DHCP address leases.
Syntax
execute dhcp lease-clear
Related topics
execute dhcp lease-list
system dhcp server
system dhcp reserved-address
Dhcp lease-list
Display DHCP leases on a given interface
Syntax
execute dhcp lease-list [interface_name]
If you specify an interface, the command lists only the leases
issued on that interface. Otherwise, the list includes all leases
issued by DHCP servers on the ZXSEC US unit.
If there are no DHCP leases in user on the ZXSEC US unit, an
error will be returned.
Related topics
execute deploy
system dhcp server
system dhcp reserved-address
Disconnect-admin-session
Disconnect an administrator who is logged in.
Syntax
execute disconnect-admin-session <index_number>
To determine the index of the administrator that you want to
disconnect, view the list of logged-in administrators by using the
following command:
execute disconnect-admin-session ?
The list of logged-in administrators looks like this:
Connected:
TIME
Factoryreset
Reset the ZXSEC US configuration to factory default settings.
Syntax
execute factoryreset
Caution:
This procedure deletes all changes that you have made to the
ZXSEC US configuration and reverts the system to its original
configuration, including resetting interface addresses.
Related topics
execute backup
execute reboot
Formatlogdisk
Format the ZXSEC US hard disk to enhance performance for
logging.
Syntax
execute formatlogdisk
Caution:
This operation will erase all quarantine files and logging data on
the hard disk.
Usservice-log update
Update the Usservice Analysis and Management Service contract.
Syntax
execute Usservice-log update
Related topics
system Usservice
log Usla setting
{disk | Usla | memory | syslogd | webtrends | Usservice}
filter
Fsae refresh
Use this command to manually refresh user group information
from Windows AD servers connected to the ZXSEC US unit using
the USnet Server Authentication Extensions (FSAE).
syntax
execute fsae refresh
Related topics
user fsae
Ha disconnect
Use this command to disconnect a ZXSEC US unit from a
functioning cluster. You must specify the serial number of the
unit to be disconnected. You must also specify an interface name
and assign an IP address and netmask to this interface of the
disconnected unit. You can disconnect any unit from the cluster
even the primary unit. After the unit is disconnected the cluster
responds as if the disconnected unit has failed. The cluster may
renegotiate and may select a new primary unit.
To disconnect the unit from the cluster, the execute ha
disconnect command sets the HA mode of the disconnected unit
to standalone. In addition, all interface IP addresses of the
disconnected unit are set to 0.0.0.0. The interface specified in
the command is set to the IP address and netmask that you
specify in the command. In addition all management access to
this interface is enabled. Once the ZXSEC US unit is
disconnected you can use SSH, telnet, HTTPS, or HTTP to
connect to and manage the ZXSEC US unit.
syntax
execute ha disconnect <cluster-member-serial_str> <interface_str>
<address_ipv4> <address_ipv4mask>
Keywords and
Description
variables
cluster-member- The serial number of the cluster unit to be
serial_str disconnected.
The name of the interface to configure. The
command configures the IP address and
interface_str
netmask for this interface and also enables
all management access for this interface.
Example
This example shows how to disconnect a cluster unit with serial
number US0900. The internal interface of the disconnected unit
is set to IP address 1.1.1.1 and netmask 255.255.255.0.
execute ha disconnect US0900 internal 1.1.1.1 255.255.255.0
Related topics
execute ha manage
execute ha synchronize
system ha
Ha manage
Use this command from the CLI of a ZXSEC US unit in an HA
cluster to log into the CLI of another unit in the cluster. Usually
you would use this command from the CLI of the primary unit to
log into the CLI of a subordinate unit. However, if you have
logged into a subordinate unit CLI, you can use this command to
log into the primary unit CLI, or the CLI of another subordinate
unit.
You can use CLI commands to manage the cluster unit that you
have logged into. If you make changes to the configuration of
any cluster unit (primary or subordinate unit) these changes are
synchronized to all cluster units.
syntax
execute ha manage <cluster-index>
Keywords and
Description
variables
The cluster index number of the cluster unit to
log into. The first
subordinate unit has a cluster index of zero. If
there are more subordinate
units their index numbers are 1, 2, and so on.
The primary unit has the
highest index number. So in a cluster of three
ZXSEC US units:
cluster-index The first subordinate unit has a cluster
index of 0
The second subordinate unit has a cluster
index of 1
The primary unit has a cluster index of 2
Enter ?to list the cluster units that you can log
into. The list does not show the unit that you
are already logged into.
Example
This example shows how to log into a subordinate unit in a
cluster of three ZXSEC US units. In this example you have
already logged into the primary unit. The primary unit has serial
number UST3082103000056. The subordinate units have serial
numbers UST3012803021709 and UST3082103021989.
execute ha manage ?
<id> please input slave cluster index.
<0> Subsidary unit UST3012803021709
<1> Subsidary unit UST3082103021989
Type 0 and press enter to connect to the subordinate unit with
serial number UST3012803021709. The CLI prompt changes to
the host name of this unit. To return to the primary unit, type
exit.
From the subordinate unit you can also use the execute ha
manage command to log into the primary unit or into another
subordinate unit. Enter the following command:
execute ha manage ?
<id> please input slave cluster index.
<1> Subsidary unit UST3082103021989
<2> Subsidary unit UST3082103000056
Type 2 and press enter to log into the primary unit or type 1 and
press enter to log into the other subordinate unit. The CLI
prompt changes to the host name of this unit.
ZXSEC US CLI Version 3.0 MR5 Reference
494 01-30005-0015-20070622
execute ha manage
Related topics
execute ha disconnect
execute ha synchronize
system ha
Ha synchronize
Use this command from a subordinate unit in an HA cluster to
manually synchronize its configuration with the primary unit.
Using this command you can synchronize the following:
Configuration changes made to the primary unit (normal
system configuration, firewall configuration, VPN
configuration and so on stored in the ZXSEC US configuration
file),
Antivirus engine and antivirus definition updates received by
the primary unit from the Usservice Distribution Network
(UDN),
IPS attack definition updates received by the primary unit
from the UDN,
Web filter lists added to or changed on the primary unit,
Email filter lists added to or changed on the primary unit,
Certification Authority (CA) certificates added to the primary
unit,
Local certificates added to the primary unit.
You can also use the start and stop keywords to force the cluster
to synchronize its configuration or to stop a synchronization
process that is in progress.
Syntax
execute ha synchronize {config| avupd| attackdef| weblists|
emaillists|ca| localcert| all | start | stop}
Variables Description
config Synchronize the ZXSEC US configuration.
Synchronize the antivirus engine and antivirus
avupd
definitions.
attackdef Synchronize attack definitions.
weblists Synchronize web filter lists.
emaillists Synchronize email filter lists.
ca Synchronize CA certificates.
localcert Synchronize local certificates.
Variables Description
all Synchronize all of the above.
start Start synchronizing the cluster configuration.
Stop the cluster from completing synchronizing its
stop
configuration.
Example
From the CLI of a subordinate unit, use the following commands
to synchronize the antivirus and attack definitions on the
subordinate ZXSEC US unit with the primary unit after the UDN
has pushed new definitions to the primary unit.
execute ha synchronize avupd execute ha synchronize attackdef
Related topics
execute ha disconnect
execute ha manage
system ha
Interface dhcpclient-renew
Renew the DHCP client for the specified DHCP interface and
close the CLI session. If there is no
DHCP connection on the specified port, there is no output.
syntax
execute interface dhcpclient-renew <port>
Example
This is the output for renewing the DHCP client on port1 before
the session closes:
# exec interface dhcpclient-renew port1
renewing dhcp lease on port1
Related topics
execute deploy
execute dhcp lease-list
Interface pppoe-reconnect
Reconnect to the PPPoE service on the specified PPPoE interface
and close the CLI session. If there is no PPPoE connection on the
specified port, there is no output.
syntax
Log delete-all
Use this command to clear all log entries in memory and current
log files on hard disk. If your ZXSEC US unit has no hard disk,
only log entries in memory will be cleared. You will be prompted
to confirm the command.
syntax
execute log delete-all
Related topics
execute log delete-filtered
execute log delete-rolled
execute log display
execute log filter
execute log list
execute log stats display
execute log stats reset
Log delete-filtered
Use this command to delete log messages that match the
current filter. You need to first set the log filter with the execute
log filter <filter> command.
syntax
execute log delete-filtered
Example
To delete all traffic logs, enter the following commands: execute
log filter category traffic execute log delete-filtered
Related topics
execute log filter
execute log delete-rolled
execute log display
execute log list
execute log stats display
Log delete-rolled
Use this command to delete rolled log files.
syntax
execute log delete-rolled <category> <start> [<end>]
Variable Description
Enter the category of rolled log files that you want to
delete:
event
ids
<category>
spam
traffic
virus
webfilter
Enter the number of the first log to delete. If you are
<start> deleting multiple rolled log files, you must also enter
a number for end.
Enter the number of the last log to delete, if you are
<end>
deleting multiple rolled log files.
Log display
Use this command to display log messages that you have
selected with the execute log filter command.
syntax
execute log display
The console displays the first 10 log messages. To view more
messages, run the command again. You can do this until you
have seen all of the selected log messages. To restart viewing
the list from the beginning, use the commands
execute log filter start_index 1
execute log display
You can restore the log filters to their default values using the
command
execute log filter reset
Related topics
execute log filter
execute log delete-filtered
Log filter
Use this command to select log messages for viewing or deletion.
You can view one log category on one device at a time.
Optionally, you can filter the messages to select only specified
date ranges or severities of log messages. For traffic logs, you
can filter log messages by source or destination IP address.
Commands are cumulative. If you omit a required variable, the
command displays the current setting.
syntax
execute log filter category <category_name>
execute log filter device {disk | memory}
execute log filter field action <action> [action2 action3 ..] execute log filter
field date <from_date> <to_date> <negate> execute log filter field detail
<string> [string1 string2 ...] execute log filter field log_id <logid> [logid2
logid3 ...] execute log filter field msg <string> [string2 string3 ...]
execute log filter field pri <priority> [priority2 priority3 ...]
execute log filter field reason <string> [string1 string2 ...] execute log filter
field status <string> [string1 string2 ...] execute log filter field subtype
<subtype> [subtype2 subtype3 ...] execute log filter field time <from_time>
<to_time> <negate>
execute log filter field type <type> [type2 type3 ...]
execute log filter field ui <string> [string1 string2 ...] execute log filter field
user <user_id> [user_id2 user_id3 ...] execute log filter lines_per_view
<count>
execute log filter list
execute log filter reset
TABLE 147 EXECUTE LOG FILTER COMM AND KEYWORDS AND VARI ABLES
traffic
virus
webfilter
device {disk |
Device where the logs are stored. disk
memory}
field action <action> Filter according to action. You can No
[action2 action3 ..] specify up to five actions. default.
Example
When Usla is connected, the output looks like this:
Usla Host Name: Usla-800
ZXSEC US Device ID: US0550
Registration: registered
Connection: allow
Disk Space (Used/Allocated): 0/1000 MB Total Free Space:
456690 MB
Log: Tx & Rx
Report: Tx & Rx
Content Archive: Tx & Rx
Quarantine: Tx & Rx
When Usla is not connected, the output is: Connect Error
Related topics
log Usla setting
Log list
You can view the list of current and rolled log files on the
console. The list shows the file name, size and timestamp.
syntax
execute log list <category>
<category> must be one of: event, ids, spam, traffic, virus or
webfilter.
Example
The output looks like this:
elog 8704 Fri Jan 28 14:24:35 2005
elog.1 1536 Thu Jan 27 18:02:51 2005
elog.2 35840 Wed Jan 26 22:22:47 2005
At the end of the list the total number of files in the category is
displayed. For example:
501 event log file(s) found.
Related topics
execute log delete-rolled
Log roll
Use this command to roll all log files.
syntax
execute log roll
Related topics
execute log delete-rolled
Modem dial
Dial the modem.
The dial command dials the accounts configured in config system
modem until it makes a connection or it has made the maximum
configured number of redial attempts.
This command applies only to models 70, 120 and 120W and is
effective only if the modem is in Standalone mode.
Syntax
execute modem dial
Related topics
system modem
execute modem hangup
Modem hangup
Hang up the modem.
This command applies only to models 70, 120 and 120W and is
effective only if the modem is in Standalone mode.
Syntax
execute modem hangup
Related topics
system modem
execute modem dial
Mrouter clear
Clear multicast routes, RP-sets, IGMP membership records or
routing statistics.
Syntax
Clear IGMP memberships:
execute mrouter clear igmp-group {{<group-address>} <interface-name>}
execute mrouter clear igmp-interface <interface-name>
Clear multicast routes:
execute mrouter clear <route-type> {<group-address> {<source-address>}}
Clear PIM-SM RP-sets learned from the bootstrap router (BSR):
execute mrouter clear sparse-mode-bsr
Clear statistics:
execute mrouter clear statistics {<group-address> {<source-address>}}
TABLE 148 EXECUTE MROUTER CLEAR COMM AND KEYWORDS AND V ARIABLES
Variables Description
<interface- Enter the name of the interface on which you want
name> to clear IGMP memberships.
<group- Optionally enter a group address to limit the
address> command to a particular group.
Enter one of:
dense-routes - clear only PIM dense routes
<route-type>
routes- clear all types of multicast routes
sparse-routes - clear only sparse routes
Related topics
router multicast
get router info bgp
Ping
Send an ICMP echo request (ping) to test the network
connection between the ZXSEC US unit and another network
device.
Syntax
execute ping {<address_ipv4> | <host-name_str>}
<host-name_str> should be an IP address, or a fully qualified domain
name.
Example
This example shows how to ping a host with the IP address
172.20.120.16.
Ping-options
Set ICMP echo request (ping) options to control the way ping
tests the network connection between the ZXSEC US unit and
another network device.
Syntax
execute ping-options data-size <bytes> execute ping-options df-bit {yes |
no} execute ping-options pattern <2-byte_hex> execute ping-options
repeat-count <repeats>
execute ping-options source {auto | <source-intf_ip>}
execute ping-options timeout <seconds> execute ping-options tos
<service_type> execute ping-options ttl <hops>
execute ping-options validate-reply {yes | no}
Example
Use the following command to increase the number of pings sent.
execute ping-options repeat-count 10
Use the following command to send all pings from the ZXSEC US
interface with IP address
192.168.10.23.
execute ping-options source 192.168.10.23
Related topics
execute ping
execute ping6
execute traceroute
system tos-based-priority
Ping6
Send an ICMP echo request (ping) to test the network
connection between the ZXSEC US unit and an IPv6 capable
network device.
Syntax
execute ping6 {<address_ipv6> | <host-name_str>}
Example
This example shows how to ping a host with the IPv6 address
12AB:0:0:CD30:123:4567:89AB:CDEF.
execute ping6 12AB:0:0:CD30:123:4567:89AB:CDEF
Related topics
execute ping
execute ping-options
f router static6
Reboot
Restart the ZXSEC US unit.
Syntax
execute reboot <comment “comment_string”>
<comment “comment_string”> allows you to optionally add a
message that will appear in the hard disk log indicating the
reason for the reboot. If the message is more than one word it
must be enclosed in quotes.
Example
This example shows the reboot command with a message
included.
execute reboot comment “December monthly maintenance”
Related topics
execute backup
execute factoryreset
Restore
Use this command to
restore the configuration from a file
change the ZXSEC US firmware
change the ZXSEC US backup firmware
restore an IPS custom signature file
When virtual domain configuration is enabled (in system
global, vdom-admin is enabled), the content of the backup
file depends on the administrator account that created it.
A backup of the system configuration from the super admin
account contains the global settings
and the settings for all of the VDOMs. Only the super admin
account can restore the configuration from this file.
A backup file from a regular administrator account contains
the global settings and the settings for the VDOM to which
the administrator belongs. Only a regular administrator
account can restore the configuration from this file.
Syntax
execute restore av <filename> <ftp_ipv4 [ftp_port]> <password>
execute restore av tftp <avfile> <tftp_ip4>
execute restore config ftp <filename> <ftp_ipv4 [ftp_port]> <password>
execute restore config management-station <type> <revision> execute
restore config tftp <filename> <tftp_ipv4> [<password>] execute restore
config usb <filename> [<password>]
execute restore image ftp <filename> <ftp_ipv4>
execute restore image management-station <image_version>
execute restore image tftp <filename> <tftp_ipv4>
execute restore image usb <filename>
execute restore ips ftp <filename> <ftp_ipv4 [ftp_port]> <password>
execute restore ips tftp <filename> <tftp_ipv4>
execute restore ipsuserdefsig <filename> <ftp_ipv4 [ftp_port]>
<password>
execute restore ipsuserdefsig <filename> <tftp_ipv4>
execute restore secondary-image ftp <filename> <ftp_ipv4
[ftp_port]><password>
execute restore secondary-image tftp <filename> <tftp_ipv4>
execute restore secondary-image usb <filename>
execute restore USDesktop <fc_filename> <tftp_ipv4>
Variables Description
Restore the system configuration from
a file on a TFTP server. The new
configuration replaces the existing
config tftp <filename> configuration, including administrator
<tftp_ipv4> [<password>] accounts and passwords.
If the backup file was created with a
password, you must specify that
password.
Restore the system configuration from
a file on a USB disk. The new
configuration replaces the existing
config usb <filename> configuration, including administrator
[<password>] accounts and passwords.
If the backup file was created with a
password, you must specify that
password.
Upload the antivirus database file from
av tftp <avfile> a TFTP server to the
<tftp_ip4>
ZXSEC US unit.
Upload the USDesktop image from a
TFTP server to the ZXSEC US unit. The
filename must have the format:
USDesktop <fc_filename>
USDesktopSetup_versionmajor.version
<tftp_ipv4> minor.build.exe.
For example,
USDesktopSetup.3.0.377.exe.
Upload a firmware image from an FTP
server to the ZXSEC US unit. The
image ftp <filename> ZXSEC US unit reboots, loading the
<ftp_ipv4> new firmware.
This command is not available in
multiple VDOM mode.
Upload a firmware image from a TFTP
server to the ZXSEC US unit. The
image tftp <filename> ZXSEC US unit reboots, loading the
<tftp_ipv4> new firmware.
This command is not available in
multiple VDOM mode.
Upload a firmware image from a USB
disk to the ZXSEC US unit. The ZXSEC
image usb <filename>
US unit reboots, loading the new
firmware.
ips tftp <ipsfile> Upload the IPS database file from a
<tftp_ip4> TFTP server to the ZXSEC US unit.
Variables Description
Upload a firmware image from a USB
disk as the backup
firmware of the ZXSEC US unit. The
secondary-image usb unit restarts when the upload
<filename>
is complete. This is available only on
models numbered 100 and
higher.
Example
This example shows how to upload a configuration file from a
TFTP server to the ZXSEC US unit and restart the ZXSEC US unit
with this configuration. The name of the configuration file on the
TFTP server is backupconfig. The IP address of the TFTP server
is 192.168.1.23.
execute restore config tftp backupconfig 192.168.1.23
Related topics
execute backup
ips custom
Variables Description
all Clear all BGP peer connections.
Clear BGP peer connections by AS
as <as_number>
number.
dampening {ip_address | Clear route flap dampening
ip/netmask} information for peer or network.
external {in prefix-filter} Clear all external peers.
Clear BGP peer connections by IP
ip <ip_address>
address.
Clear all members of a BGP peer-
peer-group
group.
Optionally limit clear operation to
[in | out]
inbound only or outbound only.
Variables Description
flap-statistics {ip_address | Clear flap statistics for peer or
ip/netmask} network.
Related topics
router bgp
Variables Description
Select the source IP address of the
<src_ip>
session.
Select the destination IP address of
<dst_ip>
the session.
<interface> Select the interface for the session.
Related topics
router bgp
Router restart
Use this command to restart the routing software.
Syntax
execute router restart
Related topics
router
Send-fds-statistics
Use this command to send an UDS statistics report now, without
waiting for the UDS statistics report interval to expire.
Syntax
execute send-fds-statistics
Et-next-reboot
Use this command to start the ZXSEC US unit with primary or
secondary firmware after the next reboot. This command is
useful only on models numbered 100 and higher which are able
to store two firmware images. By default, the ZXSEC US unit
loads the firmware from the primary partition.
VDOM administrators do not have permission to run this
command. It must be executed by a super administrator.
Syntax
execute set-next-reboot {primary | secondary}
Related topics
execute reboot
execute shutdown
Shutdown
Shut down the ZXSEC US unit now. You will be prompted to
confirm this command.
Syntax
execute shutdown <comment> <comment_string> <comment>
allows you to optionally add a message that will appear in the
hard disk log indicating the reason for the shutdown. If the
message is more than one word it must be enclosed in quotes.
Example
This example shows the reboot command with a message
included.
execute shutdown comment “emergency facility shutdown”
Related topics
execute factoryreset
execute reboot
Ssh
Use this command to establish an ssh session with another
system.
Syntax
execute ssh <destination> <destination> - the destination in the form
user@ip or user@host.
Related topics
execute ping
execute traceroute
system interface
Telnet
Use telnet client. You can use this tool to test network
connectivity.
Syntax
execute telnet <telnet_ipv4> <telnet_ipv4> is the address to connect with.
Type exit to close the telnet session.
Related topics
execute ping
execute traceroute
system interface
Time
Get or set the system time.
Syntax
execute time [<time_str>]
time_str has the form hh:mm:ss, where
hh is the hour and can be 00 to 23
mm is the minutes and can be 00 to 59
ss is the seconds and can be 00 to 59
If you do not specify a time, the command returns the current
system time.
Traceroute
Test the connection between the ZXSEC US unit and another
network device, and display information about the network hops
between the device and the ZXSEC US unit.
Syntax
execute traceroute {<ip_address> | <host-name>}
Example
This example shows how to test the connection with
http://docs.UScare.com. In this example the traceroute
command times out after the first hop indicating a possible
problem.
#execute traceoute docs.UScare.com
traceroute to docs.UScare.com (65.39.139.196), 30 hops max,
38 byte packets
1. 172.20.120.2 (172.20.120.2) 0.324 ms 0.427 ms
0.360 ms
2. * * *
If your ZXSEC US unit is not connected to a working DNS server,
you will not be able to connect to remote host-named locations
with traceroute.
Related topics
execute ping
execute ping-options
Update-av
Use this command to manually initiate the virus definitions and
engines update. To update both virus and attack definitions, use
the execute update-now command.
Syntax
execute update-av
Related topics
execute update-now
system autoupdate override
system autoupdate push-update
system autoupdate schedule
Update-ips
Use this command to manually initiate the Intrusion Prevention
System (IPS) attack definitions and engine update. To update
both virus and attack definitions, use the execute update-now
command.
Syntax
execute update-ips
Related topics
execute update-now
system autoupdate override
system autoupdate override
system autoupdate push-update
system autoupdate schedule
Update-now
Use this command to manually initiate both virus and attack
definitions and engine updates. To initiate only virus or attack
definitions, use the execute update-av or execute update-ids
command respectively.
Syntax
execute update-now
Related topics
execute update-av
execute update-ips
system autoupdate override
system autoupdate push-update
system autoupdate schedule
Upd-vd-license
Use this command to enter a license key. If your ZXSEC US unit
is model 3000 or higher, you can purchase a license key from
USnet to increase the maximum number of VDOMs to 25, 50,
100 or 250. By default, ZXSEC US units support a maximum of
10 VDOMs.
syntax
execute upd-vd-license <license_key>
Variables Description
The license key is a 32-character string
supplied by USnet. USnet requires your
<license_key>
unit serial number to generate the
license key.
Usb-disk
Use these commands to manage your USB disks.
syntax
execute usb-disk delete <filename>
execute usb-disk format execute usb-disk list
execute usb-disk rename <old_name> <new_name>
Variables Description
Delete the named file from the USB
delete <filename>
disk.
format Format the USB disk.
list List the files on the USB disk.
rename <old_name>
Rename a file on the USB disk.
<new_name>
Related topics
execute backup
execute restore
Vpn certificate ca
Use this command to import a CA certificate from a TFTP or
SCEP server to the ZXSEC US unit, or to export a CA certificate
from the ZXSEC US unit to a TFTP server.
Before using this command you must obtain a CA certificate
issued by a CA.
Note:
VPN peers must use digital certificates that adhere to the X.509
standard.
Note:
Digital certificates are not required for configuring ZXSEC US
VPNs. Digital certificates are an advanced feature provided for
the convenience of system administrators. This manual assumes
the user has prior knowledge of how to configure digital
certificates for their implementation.
Syntax
execute vpn certificate ca export tftp <certificate-name_str>
<file-name_str> <tftp_ip>
execute vpn certificate ca import auto <ca_server_url> <ca_identifier_str>
execute vpn certificate ca import tftp <file-name_str> <tftp_ip>
Keyword/variable Description
Import the CA certificate from a TFTP
import
server to the ZXSEC US unit.
Export or copy the CA certificate from the
export ZXSEC US unit to a file on the
TFTP server. Type ? for a list of certificates.
<certificate-
Enter the name of the CA certificate.
name_str>
<file-name_str> Enter the file name on the TFTP server.
<tftp_ip> Enter the TFTP server address.
Retrieve a CA certificate from a SCEP
auto
server.
Import the CA certificate to the ZXSEC US
tftp unit from a file on a TFTP
server (local administrator PC).
<ca_server_url> Enter the URL of the CA certificate server.
CA identifier on CA certificate server
<ca_identifier_str>
(optional).
Examples
Use the following command to import the CA certificate named
trust_ca to the ZXSEC US unit from a
Note:
VPN peers must use digital certificates that adhere to the X.509
standard.
Note:
Digital certificates are not required for configuring ZXSEC US
VPNs. Digital certificates are an advanced feature provided for
the convenience of system administrators. This manual assumes
the user has prior knowledge of how to configure digital
certificates for their implementation.
syntax
execute vpn certificate crl import auto <crl-name>
Keyword/variable Description
Keyword/variable Description
Import the CRL from the configured LDAP,
import HTTP, or SCEP
authentication server to the ZXSEC US unit.
<crl-name> Enter the name of the CRL.
Trigger an auto-update of the CRL from the
auto configured LDAP, HTTP, or
SCEP authentication server.
Related topics
execute vpn certificate ca
execute vpn certificate local
execute vpn certificate remote
execute vpn sslvpn del-tunnel
execute vpn sslvpn del-web
vpn certificate ca
vpn certificate local
vpn certificate crl
vpn certificate remote
Note:
VPN peers must use digital certificates that adhere to the X.509
standard.
Digital certificates are not required for configuring ZXSEC US
VPNs. Digital certificates are an advanced feature provided for
Syntax - generate
execute vpn certificate local generate <certificate-name_str>
<key-length> {<host_ip> | <domain-name_str> | email-
addr_str>}[<optional_information>]
Variable Description
Enter a name for the certificate. The name can
contain numbers (0-9), uppercase and lowercase
<certificate-
letters (A-Z, a-z), and the special characters - and
name_str>
_. Other special characters and spaces are not
allowed.
<host_ip>
Enter the host IP address (host_ip), the domain
name
(domain-name_str), or an email address (email-
addr_str) to
identify the ZXSEC US unit being certified.
Preferably use an IP address
or domain name. If this is impossible (such as
with a dialup client), use
an e-mail address.
For host_ip, enter the IP address of the ZXSEC US
unit.
{<host_ip> | For domain-name_str, enter the fully qualified
domain name of the
<domain-
name_str> | ZXSEC US unit.
email- For email-addr_str, enter an email address that
addr_str>} identifies the
ZXSEC US unit.
If you specify a host IP or domain name, use the
IP address or domain name associated with the
interface on which IKE negotiations will take place
(usually the external interface of the local ZXSEC
US unit). If the IP address in the certificate does
not match the IP address of this interface
(or if the domain name in the certificate does not
match a DNS query of the ZXSEC US unit’s IP),
then some implementations of IKE may reject
the connection. Enforcement of this rule varies for
different IPSec products.
Enter 1024, 1536 or 2048 for the size in bits of
<key-length>
the encryption key.
Variable Description
Enter optional_information as required to further
identify the certificate. See “Optional information
variables” for the list of optional information
variables. You must enter the optional variables
in order that they are listed in the table. To enter
[<optional_info any optional variable you must enter all of the
rmation>] variables that come before it in the list. For
example, to enter the organization_name_str, you
must first enter the country_code_str,
state_name_str, and city_name_str. While
entering optional variables, you can type ? for help
on the next required variable.
Variable Description
Enter the two-character country code.
Enter execute vpn certificates local
generate <name_str> country followed by
<country_code_str>
a ? for a list of country codes. The country
code is case sensitive. Enter nullif you do
not want to specify a country.
Enter the name of the state or province
<state_name_str>
where the ZXSEC US unit is located.
Enter the name of the city, or town, where
<city_name_str> the person or organization certifying the
ZXSEC US unit resides.
Enter the name of the organization that is
<organization-
requesting the certificate for the ZXSEC
name_str>
US unit.
Enter a name that identifies the
<organization- department or unit within the organization
unit_name_str> that is requesting the certificate for the
ZXSEC US unit.
Enter a contact e-mail address for the
<email_address_str>
ZXSEC US unit.
Enter the URL of the CA (SCEP) certificate
<ca_server_url> server that allows auto- signing of the
request.
Enter the challenge password for the SCEP
<challenge_password>
certificate server.
Example - generate
Use the following command to generate a local certificate
request with the name branch_cert, the domain name
www.example.com and a key size of 1536.
execute vpn certificate local generate branch_cert 1536
www.example.com
Syntax - import/export
execute vpn certificate local import tftp <file-name_str> <tftp_ip>
Keyword/variable Description
Import the local certificate from a TFTP
import
server to the ZXSEC US unit.
Export or copy the local certificate from the
export ZXSEC US unit to a file on the TFTP server.
Type ? for a list of certificates.
<certificate-
Enter the name of the local certificate.
name_str>
<tftp_ip> Enter the TFTP server address.
<file-name_str> Enter the file name on the TFTP server.
list List local certificates.
Examples - import/export
Use the following command to export the local certificate
request generated in the above example from the ZXSEC US
unit to a TFTP server. The example uses the file name testcert
for the downloaded file and the TFTP server address
192.168.21.54.
exec vpn certificate local export branch_cert testcert
192.168.21.54 Use the following command to import the signed
local certificate named branch_cert to the ZXSEC US unit from a
TFTP server with the address 192.168.21.54.
exec vpn certificate local import branch_cert 192.168.21.54
Related topics
execute vpn certificate ca
execute vpn certificate remote
execute vpn certificate crl
execute vpn sslvpn del-tunnel
execute vpn sslvpn del-web
vpn certificate ca
vpn certificate local
vpn certificate crl
vpn certificate remote
Keyword/variable Description
Import the remote certificate from the TFTP
import
server to the ZXSEC US unit.
Export or copy the remote certificate from
export the ZXSEC US unit to a file on the TFTP
server. Type ? for a list of certificates.
<certificate-ame_str> Enter the name of the public certificate.
<file-name_str> Enter the file name on the TFTP server.
<tftp_ip> Enter the TFTP server address.
Import/export the remote certificate via a
tftp
TFTP server.
Related topics
execute vpn certificate ca
execute vpn certificate local
execute vpn certificate crl
execute vpn sslvpn del-tunnel
execute vpn sslvpn del-web
vpn certificate ca
vpn certificate local
vpn certificate crl
vpn certificate remote
Get
Overview
The get commands retrieve information about the operation and
performance of your ZXSEC US unit. This chapter contains the
following sections:
chassis status
firewall service predefined
gui console status
gui topology status hardware status
ips decoder
ips rule
ipsec tunnel list
router info bgp
router info bfd
router info multicast
router info ospf
router info protocols
router info rip
router info routing-table
system admin list
system admin status
system arp
system central-mgmt status
system checksum
system cmdb status
system dashboard
system Usla-connectivity
system Usservice-log-service status
system Usservice-service status
system ha status
system info admin ssh
system info admin status
system performance status
system session list
system session status
system status
Chassis Status
For ZXSEC US series modules installed in a ZXSEC US9005 or
ZXSEC US9014 chassis, you can use the get chassis status
command to view real-time operating status information about
the hardware components installed in the chassis.
Information displayed depends on the ZXSEC US series chassis
and not on the ZXSEC US series module that you are connecting
to. You can use this command to view information about all of
the hardware components installed in the chassis (including
ZXSEC US, USController and other USnet modules installed in
the chassis as well as the chassis shelf managers).
The get chassis status command displays information received
from the chassis shelf manager. The command only displays
information if at least one shelf manager is functioning in the
chassis and only if the ZXSEC US module that you have
connected to can communicate with a shelf manager.
Syntax
get chassis status
The command display includes the following fields. For more
information see the example that follows.
Keyword Description
Chassis type The ZXSEC US chassis type: 5050 or 5140.
Active shelfmanager The number of the shelf manager slot
containing the active shelf manager: 1 or 2.
Current blade The slot number that the ZXSEC US module
that you are connected to is installed in.
Shelfmanager 2 Indicates whether a shelf manager is
operating in shelf manager slot 2. exist if a
Keyword Description
shelf manager is installed and operating in
slot 2. empty if shelf manager slot 2 is empty
or if the shelf manager in slot 2 is not
operating.
Shelfmanager 1 Indicates whether a shelf manager is
operating in shelf manager slot 1. exist if a
shelf manager is installed and operating in
slot 1. empty if shelf manager slot 1 is empty
or if the shelf manager in slot 1 is not
operating.
Blade <slot_integer> indicated the slot number in
<slot_integer>: the chassis. Slots 1 to 5 are listed for the
ZXSEC US9005 chassis and slots 1 to 14 are
<module_name>
listed for the ZXSEC US5140 chassis.
<module_name> indicates the name of the
module installed in the chassis slot.
<module_name> can be 8004 for the ZXSEC
US8005, for the US8005, and empty if the
slot is empty.
The command displays voltage and
temperature information for each module in
the chassis. The voltage and temperature
information that is displayed is different for
each module and depends on the voltage and
temperature sensors on the module.
Voltage, V For each slot in the chassis the command
displays voltages detected by the voltage
sensors in the module installed in the slot.
The information displayed for each sensor
includes the design voltage (for example
3.3V) followed by the actual voltage (for
example, 3.488V). The design voltage
depends on the sensor.
The voltages that are displayed are different
for each module type.
Temp For each slot in the chassis the command
displays temperatures in degrees Celsius
detected by the temperature sensors in the
module. The information displayed for each
sensor includes the name of the temperature
sensor and the temperature reading.
The temperatures that are displayed are
different for each module type.
Example
The following example shows the get chassis status output for a
ZXSEC US9000 chassis that contains the following modules:
Slot 1: empty
Shelf Manager: one shelf manager in shelf manager slot 1
Chassis type: 5050
Active shelfmanager: 1
Current blade: 3
Shelfmanager 2: empty
Shelfmanager 1: exist
Blade 4: 9005
CPU1 Voltage: 1.1956V
CPU2 Voltage: 1.1858V
+5.0V: 4.8755V
+3.3V: 3.321V
+2.5V CPU 1: 2.5742V
+2.5V CPU 2: 2.5376V
+1.2V 1: 1.2054V
+1.2V 2: 1.2348V
Incoming Air-Flo: 35C
CPU Board Temp: 42C
CPU1 Temp: 59C
CPU2 Temp: 60C
Blade 4: 8004
5V: 5.0739V
3.3V: 3.4992V
2.5V: 2.497V
1.8V: 1.8124V
1.5V: 1.5345V
TEMP1: 41C
TEMP2: 35C
Blade 1: empty
Syntax
get firewall service predefined <service_name>
Example output
ZXSEC US350 # get firewall service predefined FTP
name : FTP
icmpcode :
icmptype :
protocol : TCP/UDP
protocol-number: 6
tcpport-range : 21-21:0-65535
udpport-range :
ZXSEC US350 # get firewall service predefined SIP
name : SIP
icmpcode :
icmptype :
protocol : TCP/UDP
protocol-number: 17
tcpport-range :
udpport-range: 5060-5060:0-65535
ZXSEC US350 # get firewall service predefined AOL
name : AOL
icmpcode :
icmptype :
protocol : TCP/UDP
protocol-number: 6
tcpport-range : 5190-5194:0-65535
udpport-range:
Hardware Status
Report information about the ZXSEC US unit hardware.
Syntax
get hardware status
Example
The output looks like this:
IPS Decoder
Displays all the port settings of all the IPS decoders.
Syntax
get ips decoder
Related topics
ips decoder
get ips rule
IPS Rule
Displays all the port settings of all the IPS decoders.
Syntax
get ips rule
get ips rule status
Enter get ips rule to display a list of all the intrusion protection
signatures. Enter get ips rule status to list the default settings of
all the signatures. The default settings of any individual
signature can be displayed using the config ips rule command.
Related topics
ips decoder
get ips decoder
ips rule
Keyword Description
cidr-only Show all BGP routes having non-natural
network masks.
community Show all BGP routes having their COMMUNITY
attribute set.
community-info Show general information about the
configured BGP communities, including the
routes in each community and their
associated network addresses.
community-list Show all routes belonging to configured BGP
community lists.
dampening Display information about dampening:
{dampened-paths |
Type dampened-paths to show all paths
flap- statistics |
that have been suppressed due to
parameters}
flapping.
Type flap-statistics to show flap statistics
related to BGP routes.
Type parameters to show the current
dampening settings.
Keyword Description
filter-list Show all routes matching configured AS-path
lists.
inconsistent-as Show all routes associated with inconsistent
autonomous systems of origin.
memory Show the BGP memory table.
neighbors Show information about connections to TCP
[<address_ipv4> | and BGP neighbors.
<address_ipv4>
advertised-routes |
<address_ipv4>
received prefix-filter
|
<address_ipv4>
received-routes |
<address_ipv4>
routes]
network Show general information about the
[<address_ipv4mas configured BGP networks, including their
k>] network addresses and associated prefixes.
network-longer- Show general information about the BGP
prefixes route that you specify (for example,
<address_ipv4mask 12.0.0.0/14) and any specific routes
> associated with the prefix.
Example
For the command get router info bgp memory, the output looks
like:
Memory type Alloc count Alloc bytes
===================================
============= ===============
BGP structure : 2 1408
BGP VR structure: 2 104
BGP global structure: 1 56
BGP peer: 2 3440
BGP as list master: 1 24
Community list handler: 1 32
BGP Damp Reuse List Array :2 4096
BGP table: 62 248
----------------------------------- ------------- ---------------
Temporary memory: 4223 96095
Hash: 7 140
Hash index: 7 28672
Hash bucket: 11 132
Thread master: 1 564
Thread : 4 144
Link list: 32 636
Link list node: 24 288
Show: 1 396
Show page: 1 4108
Show server: 1 36
Prefix IPv4: 10 80
Route table: 4 32
Route node: 63 2772
Vector: 2180 26160
Vector index: 2180 18284
Host config: 1 2
Message of The Day: 1 100
IMI Client: 1 708
VTY master: 1 20
VTY if: 11 2640
VTY connected: 5 140
Message handler: 2 120
NSM Client Handler: 1 12428
NSM Client: 1 1268
Host: 1 64
Log information: 2 72
Context: 1 232
----------------------------------- ------------- ---------------
bgp proto specifc allocations:9408 B
bgp generic allocations: 196333 B
bgp total allocations: 205741 B
Related topics
router aspath-list
router bgp
router community-list
Keyword Description
Show Internet Group Management
Protocol (IGMP) membership information
according to one of these qualifiers:
Type groups [{<interface-name> |
<group-address>}] to show IGMP
information for the multicast group(s)
associated with the specified interface
or multicast group address.
Keyword Description
Show information related to sparse mode
operation according to one of these
qualifiers:
Type bsr-info to show Boot Strap
Router (BSR) information.
Type interface to show information
about PIM-enabled interfaces.
Type interface-detail to show detailed
information about PIM- enabled
interfaces.
Type neighbor to show the current
status of PIM neighbors.
pim sparse-mode
Type neighbor-detail to show detailed
information about PIM neighbors.
Type next-hop to show information
about next-hop PIM routers.
Type rp-mapping to show
Rendezvous Point (RP) information.
Type table [<group-
address>][<source-address>] to
show the multicast routing table
entries associated with the specified
multicast group address and/or
multicast source address.
Examples
This example displays all of the PIM entries in the multicast
routing table:
get router info multicast table
This example displays IGMP information for the multicast group
associated with multicast group address 239.254.2.0:
get router info multicast igmp groups 239.254.2.0
Related topics
router multicast
execute mrouter clear
Keyword Description
Show OSPF routing table entries that have an
Area Border Router (ABR) or Autonomous
border-routers
System Boundary Router (ASBR) as a
destination.
Show information from the OSPF routing
database according to one of these qualifiers.
target can be one of the following values:
Type adv_router <address_ipv4> to limit
database
the information to LSAs originating from
<qualifier>
the router at the specified IP address.
Type self-originate <address_ipv4> to
limit the information to LSAs originating
from the ZXSEC US unit.
Keyword Description
AS.
Examples
The following example shows how to display information from
LSAs originating from a neighboring router at IP address
10.2.4.1:
get router info ospf database router adv_router 10.2.4.1
The following example shows how to display the number and
type of LSAs associated with each OSPF area to which the
ZXSEC US unit is linked:
get router info ospf database brief
The following command shows the status of all ZXSEC US
interfaces and whether OSPF is enabled on those interfaces.
Keyword Description
database Show the entries in the RIP routing
database.
interface Show the status of the specified ZXSEC US
[<interface_name>] unit interface <interface_name> and
whether RIP is enabled.
If interface is used alone it lists all the
ZXSEC US unit interfaces and whether RIP
is enabled on each.
Example
The following command displays the RIP configuration
information for the port1 interface:
get router info rip interface port1
Related topics
get router info protocols
get router info routing-table
router rip
system interface
Keyword Description
Name of the admin account
username admin
for this session
The protocol this session
local used to connect to the sshv2
ZXSEC US unit.
The interface, IP address,
and port used by this session port1:172.20.1
device
to connect to the ZXSEC US 20.148:22
unit.
The IP address and port used
by the originating computer 172.20.120.16:
remote
to connect to the ZXSEC US 4167
unit.
The time the current session 2006-08-09
started
started. 12:24:20
Keyword Description
Name of the admin account username:
username
currently logged in. admin
The protocol used to start login local:
login local
the current session. sshv2
The login information from login remote:
the ZXSEC US unit including
login device 172.20.120.16:
interface, IP address, and
port number. 4167
System ARP
View the ARP table entries on the ZXSEC US unit.
This command is not available in multiple VDOM mode.
Syntax
get system arp
Keyword Description
The IP address that is
Address linked to the MAC 0.0.0.0
address.
Current duration of the
Age 0
ARP entry in minutes.
The hardware, or MAC
Hardware address, to link with this
IP 00:00:00:00:00:00:
Addr
address.
The physical interface the
Interface
address is on.
Example
System Checksum
View the checksums for global, root, and all.
Syntax
get system checksum status
Example
The output looks like this:
# get system checksum status
global: 7a 87 3c 14 93 bc 98 92 b0 58 16 f2 eb bf a4 15
root: bb a4 80 07 42 33 c2 ff f1 b5 6e fe e4 bb 45 fb all:
1c 28 f1 06 fa 2e bc 1f ed bd 6b 21 f9 4b 12 88
Keyword Description
version Version of the cmdb software.
owner id Process ID of the cndbsvr daemon.
The updated index shows how many changes
update index
have been made in cmdb.
last request pid The last process to access the cmdb.
last requst type Type of the last attempted access of cmdb.
The number of the last attempted access of
last request
cmdb.
System Dashboard
Display organization of the modules on the dashboard. The order
the modules are listed in is the order they appear - top to
bottom, left to right.
Syntax
get system cmdb status
Example
The output looks like this:
# get system dashboard
== [ sysinfo ]
name: sysinfo help: system information
== [ licinfo ]
name: licinfo help: license information
== [ sysop ]
name: sysop help: system operation
== [ sysres ]
name: sysres help: system resource
== [ alert ]
name: alert help: alert console
== [ statistics ]
name: statistics help: statistics
== [ jsconsole ]
name: jsconsole help: CLI console
System Usla-Connectivity
Display connection and remote disk usage information about a
connected Usla unit.
Syntax
get Usla-connectivity status
Example
The output looks like this:
# get system Usla-connectivity status
Status: connected
Disk Usage: 0%
System Usservice-log-
Service Status
Command returns information about the status of the Usservice
Log & Analysis Service including license and disk information.
Syntax
get system Usservice-log-service status
Example
This shows a sample output.
# get system Usservice-log-service status
Usservice Log & Analysis Service
Expire on: 20071231
Total disk quota: 1111 MB Max daily volume: 111 MB
Current disk quota usage: n/a
System Usservice-service
Status
COMMAND REPLACED. Command returns information about the
status of the Usservice service including the name, version late
update, method used for the last update and when the update
expires. This information is shown for the AV Engine, virus
definitions, attack definitions, and the IPS attack engine.
Syntax
get system Usservice-service status
Example
This shows a sample output.
LAST
AME VERSION METHOD EXPIRE
UPDATE
2006-01-26 2006-06-12
AV Engine 2.002 manual
19:45:00 08:00:00
System HA Status
Use this command to display information about an HA cluster.
The command displays general HA configuration settings. The
command also displays information about how the cluster unit
that you have logged into is operating in the cluster.
Usually you would log into the primary unit CLI using SSH or
telnet. In this case the get system ha status command displays
information about the primary unit first, and also displays the HA
state of the primary unit (the primary unit operates in the work
state). However, if you log into the primary unit and then use
the execute ha manage command to log into a subordinate unit,
(or if you use a console connection to log into a subordinate unit)
the get system status command displays information about this
subordinate unit first, and also displays the HA state of this
subordinate unit. The state of a subordinate unit is work for an
active-active cluster and standby for an active-passive cluster.
Keyword Description
Model The ZXSEC US model number.
Mode The HA mode of the cluster: a-a or a-p.
Group The group ID of the cluster.
Debug The debug status of the cluster.
The status of session pickup: enable or
ses_pickup
disable.
The status of the load-balance-all
load_balance keyword: enable or disable. Displayed for
active-active clusters only.
The active-active load balancing schedule.
schedule
Displayed for active-active clusters only.
Master displays the device priority, host
name, serial number, and actual cluster
index of the primary (or master) unit.
Slave displays the device priority, host
name, serial number, and actual cluster
index of the subordinate (or slave, or
backup) unit or units.
The list of cluster units changes depending
Master on how you log into the CLI. Usually you
would use SSH or telnet to log into the
Slave
primary unit CLI. In this case the primary
unit would be at the top the list followed
by the other cluster units.
If you use execute ha manage or a console
connection to log into a subordinate unit
CLI, and then enter get system ha status
the subordinate unit that you have logged
into appears at the top of the list of cluster
units.
Keyword Description
The number of virtual clusters. If virtual
domains are not enabled, the cluster has
number of vcluster one virtual cluster. If virtual domains are
enabled the cluster has two virtual
clusters.
Keyword Description
The HA state (hello, work, or standby) and
HA heartbeat IP address of the cluster unit
that you have logged into in virtual cluster
1. If virtual domains are not enabled,
vcluster 1 displays information for the
cluster. If virtual domains are enabled,
vcluster 1 displays information for virtual
cluster 1.
The HA heartbeat IP address is 10.0.0.1 if
you are logged into a the primary unit of
virtual cluster 1 and 10.0.0.2 if you are
logged into a subordinate unit of virtual
cluster 1. vcluster 1 also lists the primary
unit (master) and subordinate units
(slave) in virtual cluster 1. The list
includes the operating cluster index and
serial number of each cluster unit in virtual
cluster 1. The cluster unit that you have
logged into is at the top of the list.
If virtual domains are not enabled and you
connect to the primary unit CLI, the HA
state of the cluster unit in virtual cluster 1
is work. The display lists the cluster units
starting with the primary unit.
If virtual domains are not enabled and you
connect to a subordinate unit CLI, the HA
vcluster 1 state of the cluster unit in virtual cluster 1
is standby. The display lists the cluster
units starting with the subordinate unit
that you have logged into.
If virtual domains are enabled and you
connect to the virtual cluster 1 primary
unit CLI, the HA state of the cluster unit in
virtual cluster 1 is work. The display lists
the cluster units starting with the virtual
cluster 1 primary unit.
If virtual domains are enabled and you
connect to the virtual cluster 1 subordinate
unit CLI, the HA state of the cluster unit in
virtual cluster 1 is standby. The display
lists the cluster units starting with the
subordinate unit that you are logged into.
In a cluster consisting of two cluster units
operating without virtual domains enabled
all clustering actually takes place in virtual
cluster 1. HA is designed to work this way
to support virtual clustering. If this cluster
was operating with virtual domains
enabled, adding virtual cluster 2 is similar
to adding a new copy of virtual cluster 1.
Virtual cluster 2 is visible in the get system
ha status command output when you add
virtual domains to virtual cluster 2.
Keyword Description
vcluster 2 only appears if virtual domains
are enabled. vcluster 2 displays the HA
state (hello, work, or standby) and HA
heartbeat IP address of the cluster unit
that you have logged into in virtual cluster
2. The HA heartbeat IP address is 10.0.0.2
if you are logged into the primary unit of
virtual cluster 2 and 10.0.0.1 if you are
logged into a subordinate unit of virtual
cluster 2.
vcluster 2 also lists the primary unit
(master) and subordinate units (slave) in
virtual cluster 2. The list includes the
cluster index and serial number of each
vcluster 2
cluster unit in virtual cluster 2. The cluster
unit that you have logged into is at the top
of the list.
If you connect to the virtual cluster 2
primary unit CLI, the HA state of the
cluster unit in virtual cluster 2 is work. The
display lists the cluster units starting with
the virtual cluster 2 primary unit.
If you connect to the virtual cluster 2
subordinate unit CLI, the HA state of the
cluster unit in virtual cluster 2 is standby.
The display lists the cluster units starting
with the subordinate unit that you are
logged into.
Examples
The following example shows get system ha status output for a
cluster of two ZXSEC US units operating in active-active mode.
The cluster group ID, session pickup, load balance all, and the
load balancing schedule are all set to the default values. The
device priority of the primary unit is also set to the default value.
The device priority of the subordinate unit has been reduced to
100. The host name of the primary unit is 8004_Slot_4. The
host name of the subordinate unit in is 8004_Slot_3.
The command output was produced by connecting to the
primary unit CLI (host name 8004_Slot_4).
Model: 5000
Mode: a-a
Group: 0
Debug: 0
ses_pickup: disable load_balance: disable schedule:
round robin
Master:128 8004_Slot_4 US0900 1
Slave :100 8004_Slot_3 US0900 0
number of vcluster: 1
Mode: a-p
Group: 0
Debug: 0
ses_pickup: disable
Master:128 8004_slot_7 US0900 0
Slave :200 8004_slot_11 US0900 1
number of vcluster: 1
vcluster 1: work 10.0.0.2
Master:1 US0900
Slave :0 US0900
The actual cluster indexes have not changed but the operating
cluster indexes have. Also, the HA heartbeat IP address
displayed for vcluster 1 has changed to 10.0.0.2.
Virtual clustering example output
The get system ha status command output is the same if a
cluster is operating with virtual clustering turned on but with all
virtual domains in virtual cluster 1. The following get system ha
status command output example shows the same cluster
operating as a virtual cluster with virtual domains in virtual
cluster 1 and added to virtual cluster 2. In this example the
cluster unit with serial number US0900 is the primary unit for
virtual cluster 1 and the cluster unit with serial number US0900
is the primary unit for virtual cluster 2.
get system ha status
Model: 5000
Mode: a-p
Group: 0
Debug: 0
ses_pickup: disable
Master:128 8004_slot_7 US0900 0
Slave :200 8004_slot_11 US0900 1
number of vcluster: 2
vcluster 1: work 10.0.0.2
Master:1 US0900
Slave :0 US0900
vcluster 2: standby 10.0.0.1
Master:0 US0900
Slave :1 US0900
This example shows three sets of indexes. The indexes in lines
six and seven are still used by the execute ha manage command.
The indexes on lines ten and eleven are for the primary and
Keyword Description
The order the administrators
Index 0
logged in.
The name of the user account
User name admin
logged in.
Which interface was used to log
Login type CLI
in.
The IP address this user logged
From 172.20.120.16
in from.
Related topics
get system info admin ssh
Keyword Description
The percentages of CPU cycles 0% user 0% system
CPU states used by user, system, nice and
idle categories of processes. 0% nice 100% idle
DESTINA
PRO EXPI SOURC DESTINA
SOURCE TION-
TO RE E-NAT TION
NAT
127.0.0.1:
tcp 0 127.0.0.1:1083 - -
514
DESTINA
PRO EXPI SOURC DESTINA
SOURCE TION-
TO RE E-NAT TION
NAT
127.0.0.1:
tcp 0 127.0.0.1:1085 - -
514
127.0.0.1:
tcp 10 127.0.0.1:1087 - -
514
127.0.0.1:
tcp 20 127.0.0.1:1089 - -
514
127.0.0.1:
tcp 30 127.0.0.1:1091 - -
514
127.0.0.1:
tcp 40 127.0.0.1:1093 - -
514
127.0.0.1:
tcp 60 127.0.0.1:1097 - -
514
127.0.0.1:
tcp 70 127.0.0.1:1099 - -
514
127.0.0.1:
tcp 80 127.0.0.1:1101 - -
514
90 127.0.0.1:
tcp 127.0.0.1:1103 - -
514
127.0.0.1:
tcp 100 127.0.0.1:1105 - -
514
127.0.0.1:
tcp 110 127.0.0.1:1107 - -
514
172.20.120.16: 172.20.12
tcp 103 - -
3548 0.133:22
172.20.120.16: 172.20.12
tcp 3600 - -
3550 0.133:22
127.0.0.1:
udp 175 127.0.0.1:1026 - -
53
127.0.0.1:
tcp 5 127.0.0.1:1084 - -
514
127.0.0.1:
tcp 5 127.0.0.1:1086 - -
514
127.0.0.1:
tcp 15 127.0.0.1:1088 - -
514
127.0.0.1:
tcp 25 127.0.0.1:1090 - -
514
127.0.0.1:
tcp 45 127.0.0.1:1094 - -
514
127.0.0.1:
tcp 59 127.0.0.1:1098 - -
514
127.0.0.1:
tcp 69 127.0.0.1:1100 - -
514
127.0.0.1:
tcp 79 127.0.0.1:1102 - -
514
DESTINA
PRO EXPI SOURC DESTINA
SOURCE TION-
TO RE E-NAT TION
NAT
127.0.0.1:
tcp 99 127.0.0.1:1106 - -
514
127.0.0.1:
tcp 109 127.0.0.1:1108 - -
514
127.0.0.1:
tcp 119 127.0.0.1:1110 - -
514
Keyword Description
The transfer protocol
PROTO tcp
of the session.
How long before this
EXPIRE session will 3600
terminate.
The source IP
SOURCE address and port 127.0.0.1:1083
number.
The source of the
SOURCE-NAT NAT. ‘-’ indicates -
there is no NAT.
The destination IP
DESTINATION address and port 127.0.0.1:514
number.
The destination of the
DESTINATION-NAT NAT. ‘-’ indicates -
there is no NAT.
System Status
Use this command to display system status information including:
ZXSEC US firmware version, build number and branch point
virus and attack definitions version
ZXSEC US unit serial number and BIOS version
log hard disk availability
host name
operation mode
virtual domains status: current VDOM, max number of
VDOMs, number of NAT and TP mode VDOMs and VDOM
status
current HA status
system time
Syntax
get system status
Example output
Version: ZXSEC US700 3.00,build0305,060512
Virus-DB: 6.473(2006-05-12 10:21)
IPS-DB: 2.295(2006-05-09 11:30)
Serial-Number: US0900
BIOS version: 03006000
Log hard disk: Available
Hostname: ZXSEC US700
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 10
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
Common Criteria mode: disable
Current HA mode: standalone
Distribution: International
Branch point: 305
System time: Mon May 15 13:39:03 2006
Related topics
hardware status
A
abort
abr-type
router ospf
accept-lifetime
router key-chain
access control list
access-group
router multicast interface igmp
access-list
router
router
ospf
router rip distance
router rip offset-list
accprofile
system
system admin
ACK
acl
system wireless mac-filter
action
antivirus filepattern
firewall multicast-policy
firewall policy
imp2p aim-user
imp2p icq-user
imp2p msn-user
router access-list
router aspath-list
router prefix-list
router route-map
spamfilter bword
spamfilter DNSBL
spamfilter emailbwl
spamfilter ipbwl
spamfilter mheader
webfilter urlfilter
activate
router bgp neighbor
active
antivirus filepattern
address
firewall
log report output
system autoupdate clientoverride
system autoupdate override
system autoupdate push-update
system autoupdate tunneling
address overlap
address-mode
system USLA
addrgrp
firewall
admin
log filter
system
admingrp
access group for system accprofile
administrative distance
administrator access
access profiles description
system accprofile command
administrators
info
all
execute ha synchronize
router info routing-table
alllogs
execute backup
allowaccess
system interface
allowas-in
router bgp neighbor
allowas-in-enable
router bgp neighbor
allowed
log filter
allow-interface-subnet-overlap
system global
altmode
system modem
always-compare-med
router bgp
anomaly
ips
log filter
antispam
antispam-cache
system Usservice
antispam-cache-ttl
system Usservice
antispam-timeout
system Usservice
antivirus
antivirus configuration
AP mode
system wireless settings
area
router ospf network
area border router (ABR)
system alertemail
authentication
router ospf area
router ospf area virtual-link
router ospf ospf-interface
system ha
vpn ipsec manualkey
authentication based routing
authentication keys, RIP v2 255 authentication-key
router ospf area virtual-link
router ospf ospf-interface
authgrp
access group for system accprofile
auth-key
vpn ipsec manualkey-interface
authkey
vpn ipsec manualkey
auth-keychain
router rip interface
authmethod
vpn ipsec phase1
vpn ipsec phase1-interface
auth-mode
router rip interface
authpasswd
vpn ipsec phase1
vpn ipsec phase1-interface
auth-string
router rip interface
auth-timeout
vpn ssl settings
auth-type
system interface
authusr
vpn ipsec phase1
vpn ipsec phase1-interface
system Usservice
avquery-status
system Usservice
avupd
execute ha synchronize
B
backdoor
router bgp network
backplane interfaces
backup ipsec interface
example
monitor-phase1
backup, execute
bandwidth limiting for interfaces
batch
execute
batch mode
batch_cmdb
system global
baudrate
system console
beacon_interval
system wireless settings
bestpath-as-path-ignore router bgp
bestpath-cmp-confed-aspath router bgp
bestpath-cmp-routerid
router bgp
bestpath-med-confed
router bgp
bestpath-med-missing-as-worst
router bgp
BGP
AS-path list
BGP-4
External
C
ca
execute ha synchronize
cache
spamfilter USshield
cache-mem-percent webfilter Usservice
cache-mode
webfilter Usservice
cache-notfound-responses
system dns
capability-default-originate
router bgp neighbor
capability-dynamic
router bgp neighbor
capability-graceful-restart
router bgp neighbor
capability-orf
router bgp neighbor
capability-route-refresh
router bgp neighbor
case sensitivity
Perl regular expressions
Central Management Service
certificate
vpn ca
vpn crl
vpn local
certificate ca
virtual
cluster-id
router bgp
cnid
user ldap
command abbreviation
command completion
command help
comment
firewall profile
comments
firewall policy
Common Criteria (CC)
community
router info bgp
community-info
router info bgp
community-list router
router info bgp
confederation-identifier
router bgp
config
execute backup
ha synchronize
restore
config checksum
system cmdb status
config limit
ips anomaly
config router
config srv-ovrd-list
system Usservice
connected
router info routing-table
connecting to the CLI
through the console
D
daily-restart
system global
dampening
router bgp
router info bgp
dampening-max-suppress-time
router bgp
dampening-reachability-half-life
router bgp
dampening-reuse
router bgp
dampening-route-map
router bgp
dampening-suppress
router bgp
dampening-unreachability-half-life
router bgp
database
router info ospf
router info RIP
router info
routing-table
database-filter-out
router ospf ospf-interface
database-overflow
router ospf
database-overflow-max-lsas
router ospf
database-overflow-time-to-recover
router ospf
data-size
execute ping-options
date, execute 586
day
firewall schedule recurring
system autoupdate schedule
daylight saving time
ddns
system interface
ddns-domain
system interface
ddns-password
system interface
ddns-profile-id
system interface
default-local-preference
router bgp
default-metric
router ospf
router rip
delete
shell command
denial of service (DoS) sensor
denial of service attacks
dense mode
deploy, execute
description
log report definition
router bgp neighbor
system interface
system snmp sysinfo
destination
system ipv6-tunnel
details
router info routing-table
detection summary statistics
detection-summary system global
detectserver
system interface
deterministic-med
router bgp
device
router static
router static6
system settings
df-bit
execute ping-options
DHCP exclusion range
dhcp lease-clear, execute
dhcp lease-list, execute
DHCP Options
diskfull
log disk setting
log memory setting
display
log trafficfilter
distance
router ospf
router rip distance
router static
system interface
system modem
vpn ipsec phase1
vpn ipsec phase1-interface
distance-external router bgp
router ospf
distance-inter-area
router ospf
distance-internal
router bgp
distance-intra-area
router ospf
distance-local
router bgp
distribute-list-in
router bgp neighbor
router ospf
distribute-list-out
router bgp neighbor
dn
user ldap
dns
system
DNSBL
spamfilter
dns-cache-limit
system dns
router static6
system global
dstaddr
firewall multicast-policy
firewall policy
dst-addr-type
vpn ipsec phase2
vpn ipsec phase2-interface
dst-end-ip
vpn ipsec phase2
vpn ipsec phase2-interface
dst-end-ip6
vpn ipsec phase2-interface
dstintf
firewall multicast-policy
firewall policy
dst-name
vpn ipsec phase2
vpn ipsec phase2-interface
dst-port
vpn ipsec phase2
vpn ipsec phase2-interface
dst-start-ip
vpn ipsec phase2
vpn ipsec phase2-interface
dst-start-ip6
vpn ipsec phase2-interface
dst-subnet
vpn ipsec phase2
vpn ipsec phase2-interface
dst-subnet6
vpn ipsec phase2-interface
dynamic DNS
Dynamic DNS service (DDNS)
dynamic routing
restore
router clear bfd
router clear bgp
router restart
set-next-reboot
shutdown
ssh
telnet
time
traceroute
update-av
update-ips
update-now
upd-vd-license
usb-disk
vpn certificate ca
vpn certificate crl
vpn certificate local
vpn sslvpn del-tunnel
expires
webfilter ussrv-ovrd
export
execute vpn certificate ca
extintf
firewall vip
extip
firewall vip
extport
firewall vip
ext-ref
webfilter ussrv-ovrd
F
facility
log syslogd setting
factoryreset, execute
address
addrgrp
multicast-policy
profile
firewall configuration
access profile setting
firmware performance optimization
fixedport
firewall policy
footer-option
log report customization
format
system replacemsg auth
system replacemsg Usservice-wf
system replacemsg ftp
system replacemsg http
system replacemsg im
system replacemsg mail
system replacemsg spam
system replacemsg sslvpn 442
formatlogdisk, execute
USLA system
USLA filter log
USLA setting log
ZXSEC US SNMP agent
ZXSEC US system configuration
ZXSEC US6110
ZXSEC US-ASM-FB4
Usservice
system
webfilter
Usservice Distribution Network (UDN)
Usservice filter log
Usservice Log & Analysis configuration
Usservice setting log
Usservice updates
firewall profile
ussrv-wf-block
log filter
ussrv-wf-deny
firewall profile
ussrv-wf-errors
log filter
ussrv-wf-log
firewall profile
ussrv-wf-options
firewall profile
ussrv-wf-ovrd
user group
ussrv-wf-ovrd-dur
user group
ussrv-wf-ovrd-dur-mode
user group
ussrv-wf-ovrd-ext
user group
ussrv-wf-ovrd-scope
user group
ussrv-wf-ovrd-type
user group
ftp
firewall profile
ftp, message added when virus detected
ftpcomfortamount
ftpcomUSnterval firewall profile
ftpoversizelimit
firewall profile
fwdintf
system dns
fwgrp
access group for system accprofile
system accprofile
system ha
groups
firewall policy
gui
gwdetect
system interface
H
HA
heart beat device
monitored interface
remote IP monitoring
slave, error messages
ha
arps
arps-interval
authentication
encryption
group-id
group-name
hbdev
hb-interval
hb-lost-threshold
helo-holddown
link-failed-signal
load-balance-all
mode
monitor
override
password
priority
route-hold
route-ttl
route-wait
schedule
secondary-vcluster
high availability
holddown-timer
system modem
holdtime-timer router bgp
router bgp neighbor
hop count.
hostname
spamfilter USshield
system Usservice
system global
http
firewall profile
HTTP session, antivirus
httpcomUSnterval firewall profile
http-obfuscate
system global
httpoversizelimit firewall profile
http-retry-count firewall profile
I
IBGP
RFC 1966
ICMP dropped packets logging
icmpcode
firewall service custom
icmptype
firewall service custom
icq
firewall profile
imp2p old-version
imp2p policy
icq-user
imp2p
ICSA compliant logs
id
webfilter ussrv-local-cat
firewall profile
imoversizelimit
firewall profile
imp2p
imp2pgrp
access group for system accprofile
import
execute vpn certificate ca
execute vpn certificate crl
inbandwidth
config system interface
inbound
firewall policy
inbound traffic, limiting
include-nodata
log report scope
include-summary
log report scope
include-table-of-content log report scope
inconsistent-as
router info bgp
infected
log filter
info ospf
router
info protocols
router
info rip
router
info routing-table
router
initiator
webfilter ussrv-ovrd
input-device
router policy
interface
ipsuserdefsig
execute backup
execute restore
iptrust
spamfilter
ipunnumbered
system interface
IPv6
6-to-4 address prefix
ipv6-tunnel system
ISP
J
join-group
router multicast interface
jumbo frames
K
kazaa
firewall profile
kazaa-limit
firewall profile
keepalive
vpn ipsec phase1
vpn ipsec phase1-interface
vpn ipsec phase2
vpn ipsec phase2-interface
keep-alive-timer router bgp
router bgp neighbor
key
system wireless settings
key-chain router
keylife
vpn ipsec phase1
keylifekbs
vpn ipsec phase2-interface
L
l2forward
system interface
l2tp
vpn
lacp-ha-slave
system interface
lacp-mode
system interface
lacp-speed
system interface
language
spamfilter bword
system global
webfilter bword
last request
system cmdb status
last request pid
system cmdb status
last requst type
system cmdb status
lcdpin
system global
lcdprotection
system global
lcp-echo-interval
system interface
lcp-max-echo-failures
system interface
LDAP
ldap
user
ldapconntimeout
system global
ldap-server
user local
le
router prefix-list
lease-time
system dhcp server
license
spamfilter USshield
license key entry
line continuation
lines_per_view
execute logfilter
Link Aggregation Control Protocol (LACP)
link-failed-signal system ha
list
router ospf area filter-list
listname
router rip distribute-list
load-balance-all system ha
local
user
localcert
execute ha synchronize
local-gw
system gre-tunnel
vpn ipsec manualkey
vpn ipsec manualkey-interface
vpn ipsec phase1
localid 527
vpn ipsec phase1
local-spi
loglocaldeny
system global
log-neighbor-changes
router bgp
log-spam
logtraffic
firewall policy
log-web-content
firewall profile
log-web-filter-activex
firewall profile
log-web-filter-applet
firewall profile
log-web-filter-cookie
firewall profile
log-web-ussrv-err
firewall profile
log-web-url
firewall profile
loopback interface
lowspace
antivirus quarantine
M
mac
firewall ipmacbinding table
system arp-table
system dhcp reserved-address
system interface, config wifi-mac_list
system wireless mac-filter 466
MAC address 396
arp-table
macaddr
system interface
mac-address-table system
mac-list
match-origin
match-route-type
router route-map
match-tag
router route-map
maxbandwidth
firewall policy
maxfilesize
antivirus quarantine
maximum transmission unit (MTU)
maximum-prefix
router bgp neighbor
maximum-prefix-threshold
router bgp neighbor
maximum-prefix-warning-only
router bgp neighbor
max-log-file-size
log disk setting
mc-ttl-notchange
system global
md5-key
router ospf area virtual-link
router ospf ospf-interface
member
firewall addrgrp
firewall service group
system interface
user group
user peergrp
vpn ipsec concentrator
memory
router info bgp
memory filter log
memory global setting log
memory setting log
metric
msn-user imp2p
MSS TCP
mtu
router ospf ospf-interface
system interface
mtu-ignore
router ospf ospf-interface
Multi Exit Discriminator (MED)
Multi Protocol Label Switching (MPLS)
multicast
BSR, Cisco
dense mode
IGMP 258
router
RP 261
system global
multicast memberships
multicast-forward
system global
multicast-policy firewall
multicast-routing
multi-report
USLA setting
log USLA setting
N
name
firewall ipmacbinding table
log report summary-layout
system session-helper
system snmp community
Netscape
network
router info bgp
network address translation (NAT)
Network Layer Reachability Information (NLRI)
neighbor
router info ospf
neighbors
router info bgp
neighbour-filter
router multicast interface
NetBIOS
netbios-forward
system interface
netgrp
access group for system accprofile
system accprofile
netmask
firewall dnstranslation
system dhcp server
obfuscated
obfuscate-user
log report scope
offset
router rip offset-list
old-version imp2p
onlink-flag
system interface config ipv6-prefix
operating mode
system settings
opmode
system settings
optimize
system global
option
system dhcp server
options
spamfilter
order
log report summary-layout
OSPF
P
p2p 134
packet size
for wireless network
padt-retry-timeout
system interface
PAP
passive
router bgp neighbor
router multicast interface
passive-interface router ospf
router rip
passphrase
system wireless settings
passwd
system modem
user local
password
system alertemail
system autoupdate tunneling
system bug-report
system ha
system interface
user ldap
PAT
virtual IPs
paths
router info bgp
pattern
execute ping-options
log filter
spamfilter bword
pattern-type
spamfilter bword
spamfilter emailbwl
spamfilter mheader
webfilter bword
peer
router ospf area virtual-link
vpn ipsec phase1
vpn ipsec phase1-interface
peergrp
vpn ipsec phase1
Q
quarantine antivirus
quarfilepattern antivirus
quar-to-USLA antivirus quarantine
query-v1-port
system snmp community
query-v1-status
system snmp community
R
RADIUS
radius
user
RADIUS authentication
radius-auth
system admin
radius-group
system admin
radius-port
system global
radius-server
system wireless settings
user local
rating
webfilter ussrv-local-rating
webfilter ussrv-ovrd
reboot, execute
recalling commands
received route, looping
receive-version
router rip interface
redial
system modem
redir-url
user group
refresh
system global
regexp
router aspath-list
router info bgp
Remote Gateway
VPN IPSec monitor field
remote IP monitoring
HA
remote-as
router bgp neighbor
remoteauthtimeout system global
remote-gw
system gre-tunnel
vpn ipsec manualkey
vpn ipsec manualkey-interface
vpn ipsec phase1
vpn ipsec phase1-interface
remotegw-ddns
vpn ipsec phase1
vpn ipsec phase1-interface
remote-ip
system interface
remote-spi
vpn ipsec manualkey-interface
remotespi
vpn ipsec manualkey
remove-private-as
router bgp neighbor
rename
Rendezvous Point (RP)
repeat-count
execute ping-options
replacemsg auth
replacemsg Usservice-wf system
replacemsg ftp system replacemsg http system
replacemsg im sytem replacemsg mail system
RFC 1112
RFC 1583
RFC 1700
RFC 1771
RFC 1966
RFC 1997
RFC 1997, BGP community-list
RFC 2132
RFC 2236
RFC 2328
RFC 2453
RFC 2616
RFC 3065
RFC 3376
RFC 3509
RFC 3513
RFC 791
rfc1583-compatible router ospf
RIP
split horizon
rip
router
router info routing-table
rolled_number
roll-schedule
disk setting
log disk setting
roll-time
log disk setting
route
router info ospf
route, suppressed
route-flap
routegrp
access group for system accprofile
system accprofile
route-ttl
system ha
route-wait
system ha
routing
authentication
blackhole
enhanced packet-matching
routing failover
routing table priority
routing table, displaying entries in
routing, administrative distance
routing, flap
routing, inter-VDOM
rp-candidate
router multicast interface
rp-candidate-group
router multicast interface
rp-candidate-interval
rp-candidate-priority
rsa-certificate
vpn ipsec phase1
vpn ipsec phase1-interface
RST out-of-window checking
rule
log trafficfilter
Runtime-only config mode
runtime-only configuration mode
S
SACK
scan
router info bgp
scan-bzip2
antivirus service
scan-time
spamfilter DNSBL
syslogd setting
system alertemail
system bug-report
user fsae
user ldap
user radius
webtrends setting
servercert
vpn ssl settings
server-type
system dhcp server
service antivirus
firewall policy
log trafficfilter rule
service custom firewall
service group firewall
service predefined firewall
Service Set ID (SSID)
session synchronization
between two standalone ZXSEC US units
session table
session-helper system
session-pickup
system ha
session-sync system
session-ttl
RFC 1700
system
set
set-aggregator-as
router route-map rule
set-aggregator-ip
router route-map rule
set-aspath
router route-map rule
log filter
SFP interfaces
SGMII (Serial Gigabit Media Independent Interface)
shortcut
router ospf area
shortest path first (SPF)
shutdown
router bgp neighbor
shutdown, execute
signature
ips custom
log filter
signature reporting
single-source
vpn ipsec phase2
vpn ipsec phase2-interface
sip
vpn l2tp
vpn pptp
Skinny Client Call protocol (SCCP)
skype
smtp
SMTP server
SMTP, blocked email
smtpoversizelimit
smtp-spamaction
smtp-spamhdrip
smtp-spamtagmsg
smtp-spamtagtype
SNMP
v1
v2c
snmp community system
snmp sysinfo system
socket-size
soft-reconfiguration
status (continued)
Usservice service
HA
hardware
log disk setting
log USLA setting
log Usservice setting
log memory setting
log syslogd setting
log webtrends setting
router bgp redistribute
router info ospf
router ospf ospf-interface
router ospf redistribute
router rip distribute-list
router rip offset-list
router rip redistribute
spamfilter bword
spamfilter DNSBL
spamfilter emailbwl
spamfilter mheader
syslogd setting
system autoupdate clientoverride
system autoupdate override
system autoupdate push-update
system autoupdate schedule
system autoupdate tunneling
system cmdb
system USLA
system interface
system modem
system performance
system snmp community
system snmp sysinfo
system wireless mac-filter
user local
summary-column
log report summary-layout
summary-only
router bgp aggregate-address
summary-reports
log report summary-layout
SYN packets
sync-config
system ha
synchronization router bgp
sessions between two standalone ZXSEC US units
TCP sessions between two standalone ZXSEC US units
syncinterval
system global
sysgrp
access group for system accprofile
system accprofile
syslogd filter log
syslogd setting log
syslogd2 setting log
syslogd3 setting log
system admin list
system admin status
system checksum
system cmdb status
system dashboard
system USLA-connectivity
system Usservice-log-service status
system Usservice-service status
system ha status
system info admin ssh
system info admin status
system performance status
T
tag
router ospf redistribute
topology, gui
tos
execute ping-options
tos-based-priority system
tp-mc-skip-policy system global
traceroute, execute
traffic
log filter
Traffic Indication Messages (TIM)
system wireless settings
traffic shaping
trafficfilter log
trafficshaping
firewall policy
transmit-delay
router ospf area virtual-link
router ospf interface
transparent mode, changing
trap-v1-lport
system snmp community
trap-v1-rport
system snmp community
trap-v1-status
system snmp community
trap-v2c-lport
system snmp community
trap-v2c-rport
system snmp community
trap-v2c-status
system snmp community
troubleshooting memory low
trusthost1, trusthost2, trusthost3
system admin
ttl
execute ping-options
ttl-threshold
U
UDP
udp-portrange
firewall service custom
uncompnestlimit antivirus service
uncompsizelimit antivirus service
undefinedhost
firewall ipmacbinding setting
unicast
uninterruptable-upgrade system ha
unset
unsuppress-map
router bgp neighbor
update index
system cmdb status
update-av, execute
updategrp
system accprofile
update-ips, execute
update-now, execute
update-source
router bgp neighbor
update-timer router rip
updgrp
access group for system accprofile
upd-vd-license, execute
upload
log disk setting
log report output
upload-delete
log report output
upload-delete-files
log disk setting
upload-destination
log disk setting
upload-dir
log report output
uploaddir
log disk setting
upload-gzipped
log report output
upload-ip
log report output
uploadip
log disk setting
uploadpass
log disk setting
upload-password
log report output
system bug-repor
using the CLI
usrgrp
vpn ipsec phase1
vpn l2tp
vpn pptp
V
validate-reply
execute ping-options
valid-life-time
system interface config ipv6-prefix
vcluster2
system ha
VDOM
management
vdom 368
configure VDOMs
system admin
system ha
system interface
vdom-link system
ver-1
system USLA
version
IGMP
router multicast interface igmp
router rip
system cmdb status
view-settings
execute ping-options
violation
log filter
vip
firewall
vip group, grouping vip, vipgrp
W
web
log filter
web browser support
web filtering, blocked pages
web-content
log filter
webfilter
webfilter configuration
web-filter-activex log filter
web-filter-applet log filter
webfilter-cache
system Usservice
webfilter-cache-ttl
system Usservice
web-filter-cookie log filte
webfilter-status
system Usservice
webfilter-timeout
system Usservice
webgrp
access group for system accprofile
system accprofile
weblists
execute ha synchronize
webtrends filter log
webtrends setting log
webwordthreshold
weight
router bgp neighbor
system ha
WEP key
where
spamfilter bword
wifi-acl
system interface
wifi-broadcast_ssid system interface
wifi-fragment_threshold
system interface
wifi-key
system interface
wifi-mac-filter
X
xauthtype
vpn ipsec phase1
vpn ipsec phase1-interface
Y
yahoo
firewall profile
imp2p old-version
imp2p policy
yahoo-user imp2p
Z
zone, system