Array Network - Webui
Array Network - Webui
Array Network - Webui
4
WebUI Handbook
Copyright Statement
Copyright Statement
Copyright©2014 Array Networks, Inc., 1371 McCarthy Blvd, Milpitas, California 95035, USA.
All rights reserved.
This document is protected by copyright and distributed under licenses restricting its use, copying,
distribution, and compilation. No part of this document may be reproduced in any form by any
means without prior written authorization of Array Networks, Inc. Documentation is provided “as
is” without warranty of any kind, either express or implied, including any kind of implied or
express warranty of non-infringement or the implied warranties of merchantability or fitness for a
particular purpose.
Array Networks, Inc., reserves the right to change any products described herein at any time, and
without notice. Array Networks, Inc. assumes no responsibility or liability arising from the use of
products described herein, except as expressly agreed to in writing by Array Networks, Inc. The
use and purchase of this product does not convey a license to any patent copyright, or trademark
rights, or any other intellectual property rights of Array Networks, Inc.
Warning: Modifications made to the Array Networks unit, unless expressly approved by
Array Networks, Inc., could void the user’s authority to operate the equipment.
Declaration of Conformity
We, Array Networks, Inc., 1371 McCarthy Blvd, Milpitas, CA 95035, 1-866-992-7729; declare
under our sole responsibility that the product(s) Array Networks, Inc., Array Appliance complies
with Part 15 of FCC Rules. Operation is subject to the following two conditions: (1) this device
may not cause harmful interference, and (2) this device must accept any interference received,
including interference that may cause undesired operation.
Warning: This is a Class A digital device, pursuant to Part 15 of the FCC rules. These limits
are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and
can radiate radio frequency energy, and if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. In a
residential area, operation of this equipment is likely to cause harmful interference in which
case the user may be required to take adequate measures or product. In a domestic
environment this product may cause radio interference in which case the user may be
required to take adequate measures.
Engineered for the modern data center, Array Networks application, desktop and cloud service
delivery solutions support the scalability, price-performance, software agility and leading-edge
feature innovation essential for successfully transforming today's challenges in mobile and cloud
computing into opportunities for mobilizing and accelerating business.
Website:
http://www.arraynetworks.com/
Telephone:
1-866-MY-ARRAY
877-992-7729 (Support)
408-240-8700
408-240-8753 (Fax)
Telephone access to Array Networks, Inc. is available Monday through Friday, 9 A.M. to 5 P.M.
PST.
E-mail:
Address:
Revision History
Date Description
April 26, 2013 GA release.
June 27, 2013 Added revision history.
Table of Contents
Copyright Statement ......................................................................................................................... I
6.5 Associating the Virtual Service With a Group and Defining a Policy .............................. 20
11.2 Applying for a Certificate for the SSL Virtual Host ....................................................... 32
11.3 Importing a Key and Certificate for the SSL Virtual Host.............................................. 34
17.3 Associating the Virtual Service with the Setting Script .................................................. 52
1.1 Overview
The APV Web User Interface (WebUI) is designed to maximize the functionality and performance
of the APV appliance by allowing administrators to configure and control key functions of the
APV appliance.
This chapter describes basic WebUI operations, including how to enable and access the WebUI,
register the product, log in to the WebUI, and perform initial configurations for the APV
appliance.
Setting Value
Emulation VT 100
Baud 9600
Number of Bits 8
Parity No
Stop Bits 1
Flow Control No
In the CLI interface, you will be first prompted for the user name and password (default to array
and admin). After you log in successfully, the “AN>” prompt will be displayed. Enter the
“enable” command to go to the Enable mode, and the “AN#” prompt will be displayed. Continue
to enter the “configure terminal” command to go to the Config mode, and the “AN(config)#”
prompt will be displayed.
Then, execute the following commands to complete necessary network settings and enable the
WebUI function:
Command Description
ip address Sets the IP address and netmask of the system
{system_ifname|mnet_ifname|vlan_ifname interface, MNET interface, VLAN interface or bond
|bond_ifname} <ip_address> <netmask> interface.
webui ip <ip_address> Sets the WebUI IP address.
ip route default <gateway_ip> Sets the default gateway IP address.
webui {on|off} Enables or disables the WebUI function.
Example:
AN>enable
AN#config terminal
To access the WebUI, enter the address in the format of “https://WebUI IP address:port number”
in the address bar of the browser, for example, https://10.10.0.2:8888. Then, press Enter.
In the pop-up dialog box, enter the user name and password, which are array and admin by default.
Click the OK button. Next, Array Networks will invite you to register your Array product.
IE (Recommended)
Firefox
Chrome
It is recommended that you register your product immediately. To do so, click the Register Now
button in the pop-up message box. A short questionnaire will be displayed. Fill in the
questionnaire and click the Register button to complete registration.
If you click the Register Later or Never Register button, you will skip the registration step and
go to the login step, which is described in the following section. You can register your product in
the future by selecting Home > Basic Information and clicking the Register Now action link in
the System Information area.
The WebUI consists of three parts: top bar, side bar, and configuration window.
The top bar displays information such as user name and APV appliance host name, and several
commonly used action links. The side bar is on the left of the WebUI and displays the user access
mode and features organized into groups. The configuration window displays the detailed
configuration options, results, and statistics of a specific feature.
Note:
Only one user can be in Config mode at the same time. If the user shuts down the
browser or changes the system time, the user may be unable to enter the Config mode
before the Config mode session exceeds the timeout value. If the user needs to enter the
Config mode by force, select Admin Tools > System Management > Access Control
and click Reset in the Config Mode Settings area.
Note: To save the configurations you have made into system memory, click the Save
Config action link in the top bar, which is available only when you are in Config mode.
By default, Greenwich Mean Time (GMT) is adopted. To use another time zone, clear the GMT
check box and set the time zone from the Continent, Country, and Timezone drop-down lists.
To add an NTP server, select System Configuration > General Settings > NTP in Config mode
and click the Add action link, as shown in the figure below.
On the page that is displayed, enter the IP address of the NTP server and select the NTP server
version from the drop-down list. Click the Save action link. The added NTP server will be
displayed in the NTP Servers table.
Select the Enable NTP check box. Click the Save Changes button. A system warning will be
displayed. Read the warning carefully and perform operations accordingly.
For APV4600, you can select System Configuration > Basic Networking > Switch to configure
the switch web link of the APV appliance.
Basic network configurations also include other items such as ARP, DNS, and name resolution
host. For more configuration examples, refer to the APV User Guide.
In Config mode, select System Configuration > NAT. Click the Add NAT Port action link in
the NAT Port Configuration area. The page for configuring port-level NAT becomes available,
as shown in the figure below.
Note:
To configure port-level NAT, do not select the Destination Based NAT check box.
In port-level NAT, parameter Network IP is the source IP address, that is, the IP
address of the real server. In addition, the value of parameter Netmask/Prefix
Length should be that of the source IP address.
The default gateway value is 0.0.0.0, which is valid only when the virtual IP address
and the route gateway are in the same network segment. If not, the gateway value
must be configured as the route gateway.
Click the Save action link. The added NAT entry will be displayed in the NAT Port
Configuration table.
In Config mode, select System Configuration > Advanced Networking > IP Region. In the IP
Region Table area, select the import mode and specify the required parameters. Click the Import
action link. The imported IP region table will be displayed in the adjacent table, as shown in the
figure below.
In Config mode, select System Configuration > Advanced Networking > IP Pool. In the Add
IP Pool area, specify the Pool Name, Start IP, and End IP parameters and click the Add action
link. The added IP pool will be displayed in the IP Pools List table.
Specify the parameters as required and click the Save action link. The added entry will be
displayed in the table of the TCP Port Forwarding area.
Then, select System Configuration > NAT > Port Forwarding > Mode to configure the port
forwarding mode. The default mode is transparent, in which the APV appliance uses the IP
address of the client as the source IP address for port forwarding. The APV appliance also
supports the non-transparent mode, in which the APV appliance uses its own management IP
address as the source IP address for port forwarding.
Advanced network configuration items may be required by a specific feature such as Server Load
Balancing (SLB). Therefore, you need to configure the items according to the actual networking
environment. For more configuration examples, refer to the APV User Guide.
In the Interface Settings area, select a bond ID from the Bond ID drop-down list, specify the
Name and MTU parameters, and configure either the Static IP Address (v4) + Static Netmask
or Static IP Address (v6) + Prefix Length parameters. Click the Save Changes button to save
the configurations.
Select an interface from the Interface Name drop-down link and specify the interface type. Click
the Save action link. The added interface will be displayed in the table of the Interface Settings
area. Continue this step to add more interfaces to the bond interface as required.
Chapter 4 Clustering
Two kinds of clusters are available on the APV appliance: the cluster of inside interfaces and the
cluster of virtual IP addresses (VIPs) of Server Load Balancing (SLB). Each kind can work in
either Active-Standby or Active-Active mode. Regardless of the working mode, the configuration
procedures of clusters are similar. Therefore, the following takes how to cluster SLB VIPs in
Active-Standby mode as an example to describe the configuration procedure.
Two APVs (APV1 and APV2) work in Active-Standby mode to form a cluster.
APV1 has a higher priority than APV2 and therefore is the master that uses the VIP to
process traffic.
APV2 is the backup that listens to advertisements from the master and will become the
master if APV1 stops sending advertisements.
Note:
Unless otherwise specified, parameters should be set to identical values on APV1 and
APV2.
Specify the Virtual Cluster ID (VCID) and Interface Name parameters. Click the Save action
link. The added cluster will be displayed in the Virtual Cluster List table.
Specify the parameters properly in the Virtual Cluster General Settings area.
On APV1, select the Enable Preemption check box so that APV1, the initial master, will preempt
the VIP when it returns to working state.
For other parameters, the configurations must be consistent on APV1 and APV2. After the
configuration is complete, click the Save Changes button.
In the Virtual Cluster VIP Configuration area, click the Add VIP Entry action link. The page
for adding a VIP will be displayed. Specify the Virtual IP (VIP) parameter and click the Save
action link. The added VIP will be displayed in the table of the Virtual Cluster VIP
Configuration area.
This completes the configuration of clustering SLB VIPs in Active-Standby mode. For more
clustering configuration examples, refer to the APV User Guide.
The HA domain contains two HA units, and the same floating IP group is enabled on both
units.
Unit1 provides the service and unit2 serves as the backup of unit1.
Note:
In Config mode, select Server Load Balance > Groups > Groups IP Pool. In the IP Pools List
area, specify the Group Name and All IP Pools parameters and click the Add action link, as
shown in the figure below.
On the page that is displayed, specify the Unit Name, IP Address, and UDP Port parameters and
click the Save action link, as shown in the figure below.
The added units will be displayed in the Unit area. You need to add both unit1 and unit2 on unit1.
In the HA Reliable Link area, click the on radio button to enable the HA network link, including
the primary link and the secondary link(s) and click the Save Changes button, as shown in the
figure below.
In the HA Reliable FFO area, click the on radio button to enable the HA FFO link and click the
Save Changes button, as shown in the figure below.
The added group will be displayed in the table of the Groups List area. Double-click the group. In
the Group Floating IP area, click the Add action link. On the page that is displayed, specify the
IP and Port parameters and click the Save action link, as shown in the figure below.
In the Group Priority area, click the Add action link. The page for configuring unit priority will
be displayed, as shown in the figure below.
Specify the Unit Name and Priority parameters and click the Save action link. You need to
configure the priority of both unit1 and unit2 on unit1. The priority of unit1 should be higher than
that of unit2.
In the Groups Edit area, click the on radio button for the parameter Preempt and click the Save
action link, as shown in the figure below.
In the Groups Edit area, click the Enable radio button for the parameter Enable Mode and click
the Save action link, as shown in Figure 5-8 Configuring the Group Preempt Mode.
Memory
In Config mode, select System Configuration > High Availability > HA > General Config. In
the HA General Settings area, select the Enable check box and click the Save Changes button.
To save the configurations you have made into system memory, click the Save Config action link
in the top bar.
5.2.4 Enabling HA
In Config mode, select System Configuration > High Availability > HA > General Config. In
the HA General Settings area, select the Enable check box and click the Save Changes button.
Note:
In Config mode, select Server Load Balance > Real Services > Real Services. Click the Add
Real Service Entry action link. Specify parameters in the Add Real Service Entry area and
click the Save action link, as shown in the figure below.
The added real service will be displayed in the SLB Real Services Configuration table.
In Config mode, select Server Load Balance > Virtual Services > Virtual Services. Specify
parameters in the Add Virtual Service area and click the Add action link, as shown in the figure
below.
The added virtual service will be displayed in the Virtual Service List table.
Groups drop-down list, select a policy from the Eligible Policies drop-down list, specify other
parameters properly, and click the Add action link, as shown in the figure below.
The binding relationship will be displayed in the table of the Associate Groups area.
To check the configuration you have made, select Server Load Balance > Monitoring >
Summary. You can click the Open All action link to check the detailed configuration.
Note: Some parameters in the above steps may vary with the real service type, virtual
service type, health check type, group method, or policy type. For detailed parameter
descriptions, refer to the APV CLI Handbook.
This completes the basic configuration of SLB. For more configuration examples, refer to the
APV User Guide.
Note:
parameters, and click the Add action link. The added filter rule will be displayed in the table of
the Cache Filter Rule area, as shown in the figure below.
Note:
For descriptions of the parameters Host Name, Regular Expression, TTL, Cache
and URL Query, refer to the command “cache filter rule” in the APV CLI
Handbook.
This completes the configuration of Reverse Proxy Cache. For more configuration examples, refer
to the APV User Guide.
A real server whose IP address is “10.3.129.1” is placed behind the APV appliance, and its
corresponding virtual service is “v1”, whose IP address is “172.16.85.74”.
The end user can only access the IP address of the virtual service “vs1” because the real
server is hidden by the APV appliance.
To enable the access of the end user to Web resource “a.xml” on the real server by clicking a link
on the Web page, the APV appliance should rewrite URL address of the Web resource on the Web
page from “http://10.3.129.1/a.xml” into “http://172.16.85.74/a.xml”.
Note:
In Config mode, select Proxy > Caching Proxy > Content Rewrite > General Setting. In the
Content Rewrite Setting area, select the Enable Content Rewrite check box and click the Save
Changes button, as shown in the figure below.
Note:
If the Type parameter is specified as “Substitute”, the APV appliance rewrites URLs
both inside and outside the HTML tags.
For descriptions of the Type, From Pattern, To Pattern, and Flags parameters,
refer to the “http rewrite body rule” command in the APV CLI Handbook.
Click the Save action link. The added rewrite rule will be displayed in the table of the Rule List
area.
Select “xml” from the MIME Type drop-down list and click the Save action link. The newly
added MIME type will be displayed in the table of the MIME Type area. Repeat this step to add
more MIME types.
Specify the Status code parameter and click the Save action link.
This completes the configuration of HTTP Content Rewrite. The end user should be able to access
the Web resource “a.xml” on the real server by clicking a link on the Web page because the APV
appliance will rewrite the URL address “http://10.3.129.1/a.xml” in the HTML tag of the response
into “http://172.16.85.74/a.xml” according to the HTTP Content Rewrite rule.
Note:
After preceding configurations, DNS Cache is enabled on the APV appliance. You can also add a
static DNS Cache entry to manually specify a host to be cached.
This completes the configuration of DNS Cache. For more configuration examples, refer to the
APV User Guide.
Note:
Text (text/plain)
HTML (text/HTML)
XML (text/XML)
In Config mode, select Proxy > Compression > Compression Type. In the Compression
MIME Types area, specify the User Agent and MIME Types parameters as required. Click the
Add MIME Type action link. The added user agent and MIME type pair will be displayed in the
Supported Compression MIME Types table, as shown in the figure below.
A URL-exclude HTTP Compression rule determines the scenario where HTTP Compression is
not applied. For example, when the “v1“ and “ghi.txt$” pair is configured, as shown in the above
figure, and the URL of a client request to the virtual service “v1” ends with the string “ghi.txt”,
the textual contents in the response will not be compressed even if HTTP Compression is enabled.
This completes the configuration of HTTP Compression. For more configuration examples, refer
to the APV User Guide.
Note:
An SSL virtual host is associated with an SLB virtual service and acts as an SSL server in the
communication between the browser and the APV appliance. To create an SSL virtual host, do as
follows:
In Config mode, select Proxy > SSL > Virtual Hosts. In the SSL Virtual Hosts area, click the
Add action link, and the page for adding an SSL virtual host will be displayed, as shown in the
figure below.
Specify the parameters as required and click the Save action link. The added SSL virtual host will
be displayed in the table of the SSL Virtual Hosts area.
In Config mode, select Proxy > SSL > Virtual Hosts. In the SSL Virtual Hosts area,
double-click the SSL virtual host, and the page for generating a CSR for the SSL virtual host will
be displayed, as shown in the figure below.
Note: You must select “Yes” for the Private Key Exportable parameter and configure a
password to export the private key.
Specify other parameters properly and click the Apply action link. The APV will create a CSR
and display the private key for the SSL virtual host, as shown in the figure below.
This CSR uses the public key of the public-private key pair generated when the CSR is created.
You need to send the entire text in the Existing CSR area to a CA for signing. The CA needs
these lines to expedite your request for a certificate.
Select Virtual Host CSR/Cert/Key > Import Cert/Key. In the SSL Key area, select Manual
Input and paste the copy into the SSL Key text box and specify the Key Passphase parameter.
Click the Import action link to import the key.
After a certificate is successfully imported, the certificate status will be displayed as Inactive in
the table of the SSL Certificate area. To enable the certificate, click the Activate action link, as
shown in the figure below.
An SSL real host is associated with an SLB real service and acts as an SSL client in the
communication between the APV appliance and the backend server. To create an SSL real host,
do as follows:
In Config mode, select Proxy > SSL > Real Hosts. In the SSL Real Hosts area, click the Add
action link, and the page for adding an SSL real host will be displayed, as shown in the figure
below.
Specify the parameters as required and click the Save action link. The added SSL real host will be
displayed in the table of the SSL Real Hosts area.
This completes the basic configuration of SSL acceleration. For more configuration examples,
refer to the APV User Guide.
Note:
Select “interface” from the QoS Entry Type drop-down list. The page for specifying the QoS
interface will be displayed, as shown in the figure below.
Specify the required parameters properly. Click the Save action link. The QoS Configuration >
QoS > QoS Entries page will be displayed to illustrate QoS configurations in a tree structure, as
shown in the figure below.
Specify the parameters properly. Click the Save action link. The QoS Configuration > QoS >
QoS Entries page will be displayed to illustrate QoS configurations in a tree structure, as shown
in Figure 12-3 QoS Configurations.
Note:
You can repeat this step to add a sub-queue to the root queue as required.
Specify the required parameters properly. Click the Save action link. The QoS Configuration >
QoS > QoS Entries page will be displayed to illustrate QoS configurations in a tree structure, as
shown in Figure 12-3 QoS Configurations.
In Config mode, select QoS Configuration > QoS > Interfaces. The interfaces on which QoS is
configured will be displayed in the QoS Interface Operation table, as shown in the figure below.
To enable QoS in the specific direction on an interface, select the corresponding Enabled check
box and click the Save Changes button. You can check the QoS enabling status on the QoS
Configuration > QoS > QoS Entries page.
This completes the configuration of QoS. For more configuration examples, refer to the APV User
Guide.
The configuration example in this chapter is based on the following network environment:
An APV appliance is placed between two Internet Service Providers (ISPs) and the internal
network.
The APV appliance balances load bound to the Internet between ISPs (ISP1 and ISP2).
Eroutes are configured to transmit traffic along dedicated links to specific gateways.
You need to assign an IP address on the same network segment with ISP1 to port1, and an IP
address on the same network segment with the internal network to port2. For the detailed
procedure, refer to Section 1.7.1 “Configuring the Network Interface”.
In Config mode, select System Configuration > Basic Networking > Interface > Port. In the
MNET Configuration area, click the Add MNET action link. The page for configuring MNET
will be displayed, as shown in the figure below.
Set the Static IP Address parameter to an IP address on the same network segment with ISP2 and
specify other parameters properly. Click the Save action link. The added MNET entry will be
displayed in the table of the MNET Configuration area.
Specify the parameters properly to configure an LLB link bound to ISP1 and click the Save &
Add Another action link to add an LLB link bound to ISP2.
Note:
To configure an LLB link to ISP1/ISP2, set the source IP address to the one using
which the APV appliance is connected to ISP1/ISP2 through port1, and set the
gateway IP address to the gateway of ISP1/ISP2.
The Bandwidth Threshold parameter indicates the maximum bandwidth allowed for
the gateway specified by the Gateway IP parameter. This threshold takes effect if the
priority of the corresponding Eroute, which is configured in Section 13.4
“Configuring Eroutes”, is lower than the bandwidth priority configured in Section
13.3.5 “Configuring Bandwidth Priority”.
Specify the parameters properly to add Eroutes to specify links for traffic from the internal
network to the Internet through ISP1 or ISP2.
In addition, you must add an Eroute to transmit traffic that does not match any other Eroute. For
this Eroute, its source IP address, source netmask/prefix length, source port, destination IP address,
destination netmask/prefix length, and destination port are all 0s. In addition, its protocol should
be “any” and gateway should be the gateway of either ISP1 or ISP2.
This completes the LLB configuration on an APV appliance balancing outbound traffic between
two ISPs. For more configuration examples, refer to the APV User Guide.
The configuration example in this chapter is based on the following network environment:
Two APVs and two DPS detectors are deployed on the network to form an SDNS DPS.
Two Content Distribution Network (CDN) sites are available, each of which uses an APV
appliance or other qualified server as its DPS detector.
Note:
For every parameter mentioned in this section, its values on APV1 and APV2 must
be identical.
Specify the parameters properly to add CDN site1. Click the Save & Add Another action link to
add CDN site2.
Specify the parameters properly to add DPS detector1. Click the Save & Add Another action link
to add DPS detector2.
In Config mode, select Advance Load Balance > Global Load Balance > General Settings. In
the General Settings area, select the SDNS Status check box and specify the SDNS Report
Interval, and SDNS Heart Beat Interval parameters. Click the Save Changes button.
In Config mode, select Advance Load Balance > Global Load Balance > DPS > SDNS DPS
Settings. In the SDNS DPS Settings area, specify the Query Interval, Send Interval, and
History Scale parameters, and select the SDNS DPS check box. Click the Save Changes button.
In Config mode, select Advance Load Balance > Global Load Balance > General Settings. In
the General Settings area, select the SDNS Statistics and SDNS Local Statistics check boxes.
Click the Save Changes button.
In Config mode, select Advance Load Balance > Global Load Balance > DPS > SDNS DPS
Settings. In the SDNS DPS Settings area, select the SDNS DPS Master check box. Click the
Save Changes button.
In Config mode, select Advance Load Balance > Global Load Balance > DPS > Local
Detectors. In the Add an SDNS DPS Local Detector area, specify the parameters properly. Click
the Add action link.
This completes the SDNS DPS configuration on the APV appliance. For more configuration
examples, refer to the APV User Guide.
Specify the parameters properly. Click the Save action link. The added ACL rule will be displayed
in the table of the Access List Configuration area.
Repeat this step to add more ACL rules according to the actual situation.
For the configurations shown in the preceding figure, ACL rules whose ID is 100 are all applied
on port1 and rules whose ID is 200 are all applied on port2.
This completes the basic WebWall configuration on the APV appliance. For more configuration
examples, refer to the APV User Guide.
Note:
In Config mode, select Server Load Balance > Groups > Groups. In the Add Group area,
specify the required parameters and click the Add action link. In Groups List, double-click the
newly added group. In the Group Members area of the displayed page, click the Add action link.
In the Add Group Member area of the displayed page, specify the required parameters and click
Save to save the configuration.
In Config mode, select Server Load Balance > Virtual Services > Virtual Services. In the Add
Virtual Service area, specify the required parameters and click the Add action link. In Virtual
Service List, double-click the newly added virtual service. In the Associate Groups area of the
displayed page, associate the virtual service with the “default” or “backup” policy and click the
Add action link.
This completes the DNS64 and NAT64 configurations on the APV appliance. For more
configuration examples, refer to the APV User Guide.
Chapter 17 ePolicy
This chapter describes a basic configuration example of ePolicy. The following sections describe
the detailed configuration procedure.
Note:
In Config mode, select Server Load Balance > Virtual Services > Virtual Services. In the
Virtual Service List table, double-click the virtual service. More configurations about the virtual
service will become available. Select the ePolicy Scripts tab, and the page for configuring ePolicy
will be displayed, as shown in the figure below.
In the Import ePolicy Setting Scripts area, choose to import the setting script from local file, by
HTTP, or by FTP, specify the Local File Path/HTTP URL/FTP URL and Setting Scripts Name
parameters, and click the Import action link to import the setting script.
Local File Path/HTTP URL/FTP URL and Setting Scripts Name parameters, and click the
Import action link to import the runtime script.
Chapter 18 Logging
This section describes how to configure the basic Logging function on the APV appliance.
Note: For the Level parameter, logs whose levels are lower than the specified level will
not be transmitted to the log server.
Specify the parameters properly. Click the Save action link. The added syslog server will be
displayed in the table of the Remote Syslog Server Configuration area.
Specify the parameters properly. Click the Save action link. The added log filter will be displayed
in the table of the HTTP Log Filter Configuration area.
Note:
This completes the basic Logging configuration on the APV appliance. For more configuration
examples, refer to the APV User Guide.
In the System Statistics area, the real-time system statistics about server health, request rate,
concurrent connections, cache hit ratio, and system usage are displayed.
In the Graph 1 and Graph 2 areas, two configurable graphs are provided for real-time monitoring
on the running statistics of the APV appliance.
To view statistics in the graphs, you must enable SNMP by selecting the SNMP Enable check
box at Home > Basic Information or by specifying the Enable SNMP parameter in the General
Settings area at Admin Tools > Graph > SNMP > General.
For security reason, it is strongly recommended to modify the default SNMP community string to
avoid system information interception. To modify the default SNMP community string, specify
the new Community String parameter in the General Settings area at Admin Tools > Graph >
SNMP > General.
Note: “Gateway” is an optional parameter. When it is specified, the ping packets are sent
to the host through the LLB link determined by this parameter.
For more configuration examples about administrative tools, refer to the APV User Guide.
Appendix I Abbreviations
Acronym Full Spelling
AAA Authentication, Authorization & Accounting
ACL Access Control List
CA Certificate Authority
CDN Content Distribution Network
CLI Command Line Interface
CPU Central Processing Unit
CRL Certificate Revocation List
CSR Certificate Signing Request
DNS Domain Name Service
DPS Dynamic Proximity System
FTP File Transfer Protocol
GMT Greenwich Mean Time
GSLB Global Server Load Balance (also known as SDNS)
HC Health Check
HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
HTTPS HyperText Transfer Protocol over Secure Sockets Layer
ICMP Internet Control Message Protocol
IP Internet Protocol
ISP Internet Service Provider
LLB Link Load Balancing
Local DNS Local Domain Name Service
MIME Multipurpose Internet Mail Extensions
MNET Multi-Netting
MTU Maximum Transmission Unit
NAT Network Address Translation
QoS Quality of Service
SDNS Smart DNS (SDNS, also known as GSLB)
SLB Server Load Balancing
SSH Secure Shell Protocol
SSL Secure Sockets Layer
TCP Transmission Control Protocol
TCPS TCP with SSL
TELNET Terminal Emulation Protocol in a TCP/IP Environment
TTL Time to Live
UDP User Datagram Protocol
URL Uniform Resource Locator
VCID Virtual Cluster ID
VIP Virtual IP