Fastview Installation and User Guide: Software Version 6.3

FastView Installation and User Guide
Software Version 6.3

Document ID: RDWR-FW_V63_IUG1510
October 2015
2 Document ID: RDWR-FW_V63_IUG1510

Important Notices
The following important notices are presented in English, French, and German.
Important Notices
This guide is delivered subject to the following conditions and restrictions:
Copyright Radware Ltd. 2015. All rights reserved.
The copyright and all other intellectual property rights and trade secrets included in this guide are
owned by Radware Ltd.
The guide is provided to Radware customers for the sole purpose of obtaining information with
respect to the installation and use of the Radware products described in this document, and may not
be used for any other purpose.
The information contained in this guide is proprietary to Radware and must be kept in strict
confidence.
It is strictly forbidden to copy, duplicate, reproduce or disclose this guide or any part thereof without
the prior written consent of Radware.
Notice importante
Ce guide est sujet aux conditions et restrictions :
Copyright Radware Ltd. 2015. Tous droits réservés.
Le copyright ainsi que tout autre droit lié à la propriété intellectuelle et aux secrets industriels
contenus dans ce guide sont la propriété de Radware Ltd.
Ce guide d’informations est fourni à nos clients dans le cadre de l’installation et de l’usage des
produits de Radware décrits dans ce document et ne pourra être utilisé dans un but autre que celui
pour lequel il a été conçu.
Les informations répertoriées dans ce document restent la propriété de Radware et doivent être
conservées de manière confidentielle.
Il est strictement interdit de copier, reproduire ou divulguer des informations contenues dans ce
manuel sans avoir obtenu le consentement préalable écrit de Radware.
Wichtige Anmerkung
Dieses Handbuch wird vorbehaltlich folgender Bedingungen und Einschränkungen ausgeliefert:
Copyright Radware Ltd. 2015. Alle Rechte vorbehalten.
Das Urheberrecht und alle anderen in diesem Handbuch enthaltenen Eigentumsrechte und
Geschäftsgeheimnisse sind Eigentum von Radware Ltd.
Dieses Handbuch wird Kunden von Radware mit dem ausschließlichen Zweck ausgehändigt,
Informationen zu Montage und Benutzung der in diesem Dokument beschriebene Produkte von
Radware bereitzustellen. Es darf für keinen anderen Zweck verwendet werden.
Die in diesem Handbuch enthaltenen Informationen sind Eigentum von Radware und müssen streng
vertraulich behandelt werden.
Es ist streng verboten, dieses Handbuch oder Teile daraus ohne vorherige schriftliche Zustimmung
von Radware zu kopieren, vervielfältigen, reproduzieren oder offen zu legen.
Document ID: RDWR-FW_V63_IUG1510 3

Copyright Notices
The following copyright notices are presented in English, French, and German.
Copyright Notices
The programs included in this product are subject to a restricted use license and can only be used in
conjunction with this application.
This product contains the Rijndael cipher
The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers and Paulo Barreto is in the public
domain and distributed with the following license:
@version 3.0 (December 2000)
Optimized ANSI C code for the Rijndael cipher (now AES)
@author Vincent Rijmen <[email protected]>
@author Antoon Bosselaers <[email protected]>
@author Paulo Barreto <[email protected]>
The OnDemand Switch may use software components licensed under the GNU General Public
License Agreement Version 2 (GPL v.2) including LinuxBios and Filo open source projects. The
source code of the LinuxBios and Filo is available from Radware upon request. A copy of the license
can be viewed at: http://www.gnu.org/licenses/old-licenses/gpl-2.0.html.
This code is hereby placed in the public domain.
This product contains code developed by the OpenBSD Project
Copyright ©1983, 1990, 1992, 1993, 1995
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
This product includes software developed by Markus Friedl.
This product includes software developed by Theo de Raadt.
This product includes software developed by Niels Provos
This product includes software developed by Dug Song
This product includes software developed by Aaron Campbell
This product includes software developed by Damien Miller
This product includes software developed by Kevin Steves
This product includes software developed by Daniel Kouril
This product includes software developed by Wesley Griffin
This product includes software developed by Per Allansson
This product includes software developed by Nils Nordman
This product includes software developed by Simon Wilkinson

Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution.
This product contains work derived from the RSA Data Security, Inc. MD5 Message-Digest
Algorithm. RSA Data Security, Inc. makes no representations concerning either the merchantability
of the MD5 Message - Digest Algorithm or the suitability of the MD5 Message - Digest Algorithm for
any particular purpose. It is provided “as is” without express or implied warranty of any kind.
Notice traitant du copyright

Les programmes intégrés dans ce produit sont soumis à une licence d’utilisation limitée et ne
peuvent être utilisés qu’en lien avec cette application.
L’implémentation de Rijindael par Vincent Rijmen, Antoon Bosselaers et Paulo Barreto est du
domaine public et distribuée sous les termes de la licence suivante:
@version 3.0 (Décembre 2000)
Code ANSI C code pour Rijndael (actuellement AES)
@author Paulo Barreto <[email protected]>.
Le commutateur OnDemand peut utiliser les composants logiciels sous licence, en vertu des termes
de la licence GNU General Public License Agreement Version 2 (GPL v.2), y compris les projets à
source ouverte LinuxBios et Filo. Le code source de LinuxBios et Filo est disponible sur demande
auprès de Radware. Une copie de la licence est répertoriée sur: http://www.gnu.org/licenses/old-
licenses/gpl-2.0.html.
Ce code est également placé dans le domaine public.
Ce produit renferme des codes développés dans le cadre du projet OpenSSL.
Copyright ©1983, 1990, 1992, 1993, 1995
Les membres du conseil de l’Université de Californie. Tous droits réservés.
La distribution et l’usage sous une forme source et binaire, avec ou sans modifications, est autorisée
pour autant que les conditions suivantes soient remplies:
1. La distribution d’un code source doit inclure la notice de copyright mentionnée ci-dessus, cette
liste de conditions et l’avis de non-responsabilité suivant.
2. La distribution, sous une forme binaire, doit reproduire dans la documentation et/ou dans tout
autre matériel fourni la notice de copyright mentionnée ci-dessus, cette liste de conditions et
l’avis de non-responsabilité suivant.
3. Le nom de l’université, ainsi que le nom des contributeurs ne seront en aucun cas utilisés pour
approuver ou promouvoir un produit dérivé de ce programme sans l’obtention préalable d’une
autorisation écrite.
Ce produit inclut un logiciel développé par Markus Friedl.
Ce produit inclut un logiciel développé par Theo de Raadt.
Ce produit inclut un logiciel développé par Niels Provos.
Ce produit inclut un logiciel développé par Dug Song.
Ce produit inclut un logiciel développé par Aaron Campbell.
Ce produit inclut un logiciel développé par Damien Miller.
Ce produit inclut un logiciel développé par Kevin Steves.
Ce produit inclut un logiciel développé par Daniel Kouril.

Ce produit inclut un logiciel développé par Wesley Griffin.

Ce produit inclut un logiciel développé par Per Allansson.
Ce produit inclut un logiciel développé par Nils Nordman.
Ce produit inclut un logiciel développé par Simon Wilkinson.
La distribution et l’usage sous une forme source et binaire, avec ou sans modifications, est autorisée
pour autant que les conditions suivantes soient remplies:
1. La distribution d’un code source doit inclure la notice de copyright mentionnée ci-dessus, cette
liste de conditions et l’avis de non-responsabilité suivant.
2. La distribution, sous une forme binaire, doit reproduire dans la documentation et/ou dans tout
autre matériel fourni la notice de copyright mentionnée ci-dessus, cette liste de conditions et
l’avis de non-responsabilité suivant.
LE LOGICIEL MENTIONNÉ CI-DESSUS EST FOURNI TEL QUEL PAR LE DÉVELOPPEUR ET TOUTE
GARANTIE, EXPLICITE OU IMPLICITE, Y COMPRIS, MAIS SANS S’Y LIMITER, TOUTE GARANTIE
IMPLICITE DE QUALITÉ MARCHANDE ET D’ADÉQUATION À UN USAGE PARTICULIER EST EXCLUE.
EN AUCUN CAS L’AUTEUR NE POURRA ÊTRE TENU RESPONSABLE DES DOMMAGES DIRECTS,
INDIRECTS, ACCESSOIRES, SPÉCIAUX, EXEMPLAIRES OU CONSÉCUTIFS (Y COMPRIS, MAIS SANS
S’Y LIMITER, L’ACQUISITION DE BIENS OU DE SERVICES DE REMPLACEMENT, LA PERTE D’USAGE,
DE DONNÉES OU DE PROFITS OU L’INTERRUPTION DES AFFAIRES), QUELLE QU’EN SOIT LA CAUSE
ET LA THÉORIE DE RESPONSABILITÉ, QU’IL S’AGISSE D’UN CONTRAT, DE RESPONSABILITÉ
STRICTE OU D’UN ACTE DOMMAGEABLE (Y COMPRIS LA NÉGLIGENCE OU AUTRE), DÉCOULANT DE
QUELLE QUE FAÇON QUE CE SOIT DE L’USAGE DE CE LOGICIEL, MÊME S’IL A ÉTÉ AVERTI DE LA
POSSIBILITÉ D’UN TEL DOMMAGE.
Copyrightvermerke
Die in diesem Produkt enthalten Programme unterliegen einer eingeschränkten Nutzungslizenz und
können nur in Verbindung mit dieser Anwendung benutzt werden.
Die Rijndael-Implementierung von Vincent Rijndael, Anton Bosselaers und Paulo Barreto ist
öffentlich zugänglich und wird unter folgender Lizenz vertrieben:
@version 3.0 (December 2000)
Optimierter ANSI C Code für den Rijndael cipher (jetzt AES)
@author Paulo Barreto <[email protected]>
Der OnDemand Switch verwendet möglicherweise Software, die im Rahmen der DNU Allgemeine
Öffentliche Lizenzvereinbarung Version 2 (GPL v.2) lizensiert sind, einschließlich LinuxBios und Filo
Open Source-Projekte. Der Quellcode von LinuxBios und Filo ist bei Radware auf Anfrage erhältlich.
Eine Kopie dieser Lizenz kann eingesehen werden unter http://www.gnu.org/licenses/old-licenses/
gpl-2.0.html.
Dieser Code wird hiermit allgemein zugänglich gemacht.
Dieses Produkt enthält einen vom OpenBSD-Projekt entwickelten Code
Copyright ©1983, 1990, 1992, 1993, 1995
The Regents of the University of California. Alle Rechte vorbehalten.

Die Verbreitung und Verwendung in Quell- und binärem Format, mit oder ohne Veränderungen, sind
unter folgenden Bedingungen erlaubt:
1. Die Verbreitung von Quellcodes muss den voranstehenden Copyrightvermerk, diese Liste von
Bedingungen und den folgenden Haftungsausschluss beibehalten.
2. Die Verbreitung in binärem Format muss den voranstehenden Copyrightvermerk, diese Liste von
Bedingungen und den folgenden Haftungsausschluss in der Dokumentation und/oder andere
Materialien, die mit verteilt werden, reproduzieren.
3. Weder der Name der Universität noch die Namen der Beitragenden dürfen ohne ausdrückliche
vorherige schriftliche Genehmigung verwendet werden, um von dieser Software abgeleitete
Produkte zu empfehlen oder zu bewerben.
Dieses Produkt enthält von Markus Friedl entwickelte Software.
Dieses Produkt enthält von Theo de Raadt entwickelte Software.
Dieses Produkt enthält von Niels Provos entwickelte Software.
Dieses Produkt enthält von Dug Song entwickelte Software.
Dieses Produkt enthält von Aaron Campbell entwickelte Software.
Dieses Produkt enthält von Damien Miller entwickelte Software.
Dieses Produkt enthält von Kevin Steves entwickelte Software.
Dieses Produkt enthält von Daniel Kouril entwickelte Software.
Dieses Produkt enthält von Wesley Griffin entwickelte Software.
Dieses Produkt enthält von Per Allansson entwickelte Software.
Dieses Produkt enthält von Nils Nordman entwickelte Software.
Dieses Produkt enthält von Simon Wilkinson entwickelte Software.
Die Verbreitung und Verwendung in Quell- und binärem Format, mit oder ohne Veränderungen, sind
unter folgenden Bedingungen erlaubt:
1. Die Verbreitung von Quellcodes muss den voranstehenden Copyrightvermerk, diese Liste von
Bedingungen und den folgenden Haftungsausschluss beibehalten.
2. Die Verbreitung in binärem Format muss den voranstehenden Copyrightvermerk, diese Liste von
Bedingungen und den folgenden Haftungsausschluss in der Dokumentation und/oder andere
Materialien, die mit verteilt werden, reproduzieren.
SÄMTLICHE VORGENANNTE SOFTWARE WIRD VOM AUTOR IM IST-ZUSTAND (“AS IS”)
BEREITGESTELLT. JEGLICHE AUSDRÜCKLICHEN ODER IMPLIZITEN GARANTIEN, EINSCHLIESSLICH,
DOCH NICHT BESCHRÄNKT AUF DIE IMPLIZIERTEN GARANTIEN DER MARKTGÄNGIGKEIT UND DER
ANWENDBARKEIT FÜR EINEN BESTIMMTEN ZWECK, SIND AUSGESCHLOSSEN.
UNTER KEINEN UMSTÄNDEN HAFTET DER AUTOR FÜR DIREKTE ODER INDIREKTE SCHÄDEN, FÜR
BEI VERTRAGSERFÜLLUNG ENTSTANDENE SCHÄDEN, FÜR BESONDERE SCHÄDEN, FÜR
SCHADENSERSATZ MIT STRAFCHARAKTER, ODER FÜR FOLGESCHÄDEN EINSCHLIESSLICH, DOCH
NICHT BESCHRÄNKT AUF, ERWERB VON ERSATZGÜTERN ODER ERSATZLEISTUNGEN; VERLUST AN
NUTZUNG, DATEN ODER GEWINN; ODER GESCHÄFTSUNTERBRECHUNGEN) GLEICH, WIE SIE
ENTSTANDEN SIND, UND FÜR JEGLICHE ART VON HAFTUNG, SEI ES VERTRÄGE,
GEFÄHRDUNGSHAFTUNG, ODER DELIKTISCHE HAFTUNG (EINSCHLIESSLICH FAHRLÄSSIGKEIT
ODER ANDERE), DIE IN JEGLICHER FORM FOLGE DER BENUTZUNG DIESER SOFTWARE IST, SELBST
WENN AUF DIE MÖGLICHKEIT EINES SOLCHEN SCHADENS HINGEWIESEN WURDE.
Standard Warranty
The following standard warranty is presented in English, French, and German.

Standard Warranty
Radware offers a limited warranty for all its products (“Products”). Radware hardware products are
warranted against defects in material and workmanship for a period of one year from date of
shipment. Radware software carries a standard warranty that provides bug fixes for up to 90 days
after date of purchase. Should a Product unit fail anytime during the said period(s), Radware will, at
its discretion, repair or replace the Product.
For hardware warranty service or repair, the product must be returned to a service facility
designated by Radware. Customer shall pay the shipping charges to Radware and Radware shall pay
the shipping charges in returning the product to the customer. Please see specific details outlined in
the Standard Warranty section of the customer’s purchase order.
Radware shall be released from all obligations under its Standard Warranty in the event that the
Product and/or the defective component has been subjected to misuse, neglect, accident or
improper installation, or if repairs or modifications were made by persons other than Radware
authorized service personnel, unless such repairs by others were made with the written consent of
Radware.
EXCEPT AS SET FORTH ABOVE, ALL RADWARE PRODUCTS (HARDWARE AND SOFTWARE) ARE
PROVIDED BY “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED.
Garantie standard
Radware octroie une garantie limitée pour l’ensemble de ses produits (“Produits”). Le matériel
informatique (hardware) Radware est garanti contre tout défaut matériel et de fabrication pendant
une durée d’un an à compter de la date d’expédition. Les logiciels (software) Radware sont fournis
avec une garantie standard consistant en la fourniture de correctifs des dysfonctionnements du
logiciels (bugs) pendant une durée maximum de 90 jours à compter de la date d’achat. Dans
l’hypothèse où un Produit présenterait un défaut pendant ladite (lesdites) période(s), Radware
procédera, à sa discrétion, à la réparation ou à l’échange du Produit.
S’agissant de la garantie d’échange ou de réparation du matériel informatique, le Produit doit être
retourné chez un réparateur désigné par Radware. Le Client aura à sa charge les frais d’envoi du
Produit à Radware et Radware supportera les frais de retour du Produit au client. Veuillez consulter
les conditions spécifiques décrites dans la partie “Garantie Standard” du bon de commande client.
Radware est libérée de toutes obligations liées à la Garantie Standard dans l’hypothèse où le Produit
et/ou le composant défectueux a fait l’objet d’un mauvais usage, d’une négligence, d’un accident ou
d’une installation non conforme, ou si les réparations ou les modifications qu’il a subi ont été
effectuées par d’autres personnes que le personnel de maintenance autorisé par Radware, sauf si
Radware a donné son consentement écrit à ce que de telles réparations soient effectuées par ces
personnes.
SAUF DANS LES CAS PREVUS CI-DESSUS, L’ENSEMBLE DES PRODUITS RADWARE (MATERIELS ET
LOGICIELS) SONT FOURNIS “TELS QUELS” ET TOUTES GARANTIES EXPRESSES OU IMPLICITES
SONT EXCLUES, EN CE COMPRIS, MAIS SANS S’Y RESTREINDRE, LES GARANTIES IMPLICITES DE
QUALITE MARCHANDE ET D’ADEQUATION A UNE UTILISATION PARTICULIERE.
Standard Garantie
Radware bietet eine begrenzte Garantie für alle seine Produkte (“Produkte”) an. Hardware Produkte
von Radware haben eine Garantie gegen Material- und Verarbeitungsfehler für einen Zeitraum von
einem Jahr ab Lieferdatum. Radware Software verfügt über eine Standard Garantie zur
Fehlerbereinigung für einen Zeitraum von bis zu 90 Tagen nach Erwerbsdatum. Sollte ein Produkt
innerhalb des angegebenen Garantiezeitraumes einen Defekt aufweisen, wird Radware das Produkt
nach eigenem Ermessen entweder reparieren oder ersetzen.
Für den Hardware Garantieservice oder die Reparatur ist das Produkt an eine von Radware
bezeichnete Serviceeinrichtung zurückzugeben. Der Kunde hat die Versandkosten für den Transport
des Produktes zu Radware zu tragen, Radware übernimmt die Kosten der Rückversendung des
Produktes an den Kunden. Genauere Angaben entnehmen Sie bitte dem Abschnitt zur Standard
Garantie im Bestellformular für Kunden.

Radware ist von sämtlichen Verpflichtungen unter seiner Standard Garantie befreit, sofern das
Produkt oder der fehlerhafte Teil zweckentfremdet genutzt, in der Pflege vernachlässigt, einem
Unfall ausgesetzt oder unsachgemäß installiert wurde oder sofern Reparaturen oder Modifikationen
von anderen Personen als durch Radware autorisierten Kundendienstmitarbeitern vorgenommen
wurden, es sei denn, diese Reparatur durch besagte andere Personen wurden mit schriftlicher
Genehmigung seitens Radware durchgeführt.
MIT AUSNAHME DES OBEN DARGESTELLTEN, SIND ALLE RADWARE PRODUKTE (HARDWARE UND
SOFTWARE) GELIEFERT “WIE GESEHEN” UND JEGLICHE AUSDRÜCKLICHEN ODER
STILLSCHWEIGENDEN GARANTIEN, EINSCHLIESSLICH ABER NICHT BEGRENZT AUF
STILLSCHWEIGENDE GEWÄHRLEISTUNG DER MARKTFÄHIGKEIT UND EIGNUNG FÜR EINEN
BESTIMMTEN ZWECK AUSGESCHLOSSEN.
Limitations on Warranty and Liability

The following limitations on warranty and liability are presented in English, French, and German.
Limitations on Warranty and Liability

IN NO EVENT SHALL RADWARE LTD. OR ANY OF ITS AFFILIATED ENTITIES BE LIABLE FOR ANY
DAMAGES INCURRED BY THE USE OF THE PRODUCTS (INCLUDING BOTH HARDWARE AND
SOFTWARE) DESCRIBED IN THIS USER GUIDE, OR BY ANY DEFECT OR INACCURACY IN THIS USER
GUIDE ITSELF. THIS INCLUDES BUT IS NOT LIMITED TO ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION). THE ABOVE LIMITATIONS WILL APPLY EVEN IF RADWARE HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES OR LIABILITY FOR INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.
Limitations de la Garantie et Responsabilité

RADWARE LTD. OU SES ENTITIES AFFILIES NE POURRONT EN AUCUN CAS ETRE TENUES
RESPONSABLES DES DOMMAGES SUBIS DU FAIT DE L’UTILISATION DES PRODUITS (EN CE
COMPRIS LES MATERIELS ET LES LOGICIELS) DECRITS DANS CE MANUEL D’UTILISATION, OU DU
FAIT DE DEFAUT OU D’IMPRECISIONS DANS CE MANUEL D’UTILISATION, EN CE COMPRIS, SANS
TOUTEFOIS QUE CETTE ENUMERATION SOIT CONSIDEREE COMME LIMITATIVE, TOUS DOMMAGES
DIRECTS, INDIRECTS, ACCIDENTELS, SPECIAUX, EXEMPLAIRES, OU ACCESSOIRES (INCLUANT,
MAIS SANS S’Y RESTREINDRE, LA FOURNITURE DE PRODUITS OU DE SERVICES DE
REMPLACEMENT; LA PERTE D’UTILISATION, DE DONNEES OU DE PROFITS; OU L’INTERRUPTION
DES AFFAIRES). LES LIMITATIONS CI-DESSUS S’APPLIQUERONT QUAND BIEN MEME RADWARE A
ETE INFORMEE DE LA POSSIBLE EXISTENCE DE CES DOMMAGES. CERTAINES JURIDICTIONS
N’ADMETTANT PAS LES EXCLUSIONS OU LIMITATIONS DE GARANTIES IMPLICITES OU DE
RESPONSABILITE EN CAS DE DOMMAGES ACCESSOIRES OU INDIRECTS, LESDITES LIMITATIONS
OU EXCLUSIONS POURRAIENT NE PAS ETRE APPLICABLE DANS VOTRE CAS.
Haftungs- und Gewährleistungsausschluss

IN KEINEM FALL IST RADWARE LTD. ODER EIN IHR VERBUNDENES UNTERNEHMEN HAFTBAR FÜR
SCHÄDEN, WELCHE BEIM GEBRAUCH DES PRODUKTES (HARDWARE UND SOFTWARE) WIE IM
BENUTZERHANDBUCH BESCHRIEBEN, ODER AUFGRUND EINES FEHLERS ODER EINER
UNGENAUIGKEIT IN DIESEM BENUTZERHANDBUCH SELBST ENTSTANDEN SIND. DAZU GEHÖREN
UNTER ANDEREM (OHNE DARAUF BEGRENZT ZU SEIN) JEGLICHE DIREKTEN; IDIREKTEN; NEBEN;
SPEZIELLEN, BELEGTEN ODER FOLGESCHÄDEN (EINSCHLIESSLICH ABER NICHT BEGRENZT AUF
BESCHAFFUNG ODER ERSATZ VON WAREN ODER DIENSTEN, NUTZUNGSAUSFALL, DATEN- ODER
GEWINNVERLUST ODER BETRIEBSUNTERBRECHUNGEN). DIE OBEN GENANNTEN BEGRENZUNGEN
GREIFEN AUCH, SOFERN RADWARE AUF DIE MÖGLICHKEIT EINES SOLCHEN SCHADENS
HINGEWIESEN WORDEN SEIN SOLLTE. EINIGE RECHTSORDNUNGEN LASSEN EINEN AUSSCHLUSS

ODER EINE BEGRENZUNG STILLSCHWEIGENDER GARANTIEN ODER HAFTUNGEN BEZÜGLICH

NEBEN- ODER FOLGESCHÄDEN NICHT ZU, SO DASS DIE OBEN DARGESTELLTE BEGRENZUNG ODER
DER AUSSCHLUSS SIE UNTER UMSTÄNDEN NICHT BETREFFEN WIRD.
Safety Instructions
The following safety instructions are presented in English, French, and German.
Safety Instructions
CAUTION
A readily accessible disconnect device shall be incorporated in the building installation wiring.
Due to the risks of electrical shock, and energy, mechanical, and fire hazards, any procedures that
involve opening panels or changing components must be performed by qualified service personnel
only.
To reduce the risk of fire and electrical shock, disconnect the device from the power line before
removing cover or panels.
The following figure shows the caution label that is attached to Radware platforms with dual power
supplies.
Figure 1: Electrical Shock Hazard Label
DUAL-POWER-SUPPLY-SYSTEM SAFETY WARNING IN CHINESE

The following figure is the warning for Radware platforms with dual power supplies.
Figure 2: Dual-Power-Supply-System Safety Warning in Chinese
Translation of Dual-Power-Supply-System Safety Warning in Chinese:

This unit has more than one power supply. Disconnect all power supplies before maintenance to
avoid electric shock.
SERVICING
Do not perform any servicing other than that contained in the operating instructions unless you are
qualified to do so. There are no serviceable parts inside the unit.
HIGH VOLTAGE

Any adjustment, maintenance, and repair of the opened instrument under voltage must be avoided
as much as possible and, when inevitable, must be carried out only by a skilled person who is aware
of the hazard involved.
Capacitors inside the instrument may still be charged even if the instrument has been disconnected
from its source of supply.
GROUNDING
Before connecting this device to the power line, the protective earth terminal screws of this device
must be connected to the protective earth in the building installation.
LASER
This equipment is a Class 1 Laser Product in accordance with IEC60825 - 1: 1993 + A1:1997 +
A2:2001 Standard.
FUSES
Make sure that only fuses with the required rated current and of the specified type are used for
replacement. The use of repaired fuses and the short-circuiting of fuse holders must be avoided.
Whenever it is likely that the protection offered by fuses has been impaired, the instrument must be
made inoperative and be secured against any unintended operation.
LINE VOLTAGE
Before connecting this instrument to the power line, make sure the voltage of the power source
matches the requirements of the instrument. Refer to the Specifications for information about the
correct power rating for the device.
48V DC-powered platforms have an input tolerance of 36-72V DC.
SPECIFICATION CHANGES
Specifications are subject to change without notice.
Note: This equipment has been tested and found to comply with the limits for a Class A digital
device pursuant to Part 15B of the FCC Rules and EN55022 Class A, EN 55024; EN 61000-3-2; EN
61000-3-3; IEC 61000 4-2 to 4-6, IEC 61000 4-8 and IEC 61000-4-11For CE MARK Compliance.
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. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user is required to correct
the interference at his own expense.
SPECIAL NOTICE FOR NORTH AMERICAN USERS
For North American power connection, select a power supply cord that is UL Listed and CSA Certified
3 - conductor, [18 AWG], terminated in a molded on plug cap rated 125 V, [10 A], with a minimum
length of 1.5m [six feet] but no longer than 4.5m...For European connection, select a power supply
cord that is internationally harmonized and marked “<HAR>”, 3 - conductor, 0,75 mm2 minimum
mm2 wire, rated 300 V, with a PVC insulated jacket. The cord must have a molded on plug cap rated
250 V, 3 A.
RESTRICT AREA ACCESS
The DC powered equipment should only be installed in a Restricted Access Area.
INSTALLATION CODES
This device must be installed according to country national electrical codes. For North America,
equipment must be installed in accordance with the US National Electrical Code, Articles 110 - 16,
110 -17, and 110 -18 and the Canadian Electrical Code, Section 12.
INTERCONNECTION OF UNITS
Cables for connecting to the unit RS232 and Ethernet Interfaces must be UL certified type DP-1 or
DP-2. (Note- when residing in non LPS circuit)
OVERCURRENT PROTECTION

A readily accessible listed branch-circuit over current protective device rated 15 A must be
incorporated in the building wiring for each power input.
REPLACEABLE BATTERIES
If equipment is provided with a replaceable battery, and is replaced by an incorrect battery type,
then an explosion may occur. This is the case for some Lithium batteries and the following is
applicable:
• If the battery is placed in an Operator Access Area, there is a marking close to the battery or a
statement in both the operating and service instructions.
• If the battery is placed elsewhere in the equipment, there is a marking close to the battery or a
statement in the service instructions.
This marking or statement includes the following text warning:

CAUTION
RISK OF EXPLOSION IF BATTERY IS REPLACED BY AN INCORRECT BATTERY TYPE. DISPOSE OF
USED BATTERIES ACCORDING TO THE INSTRUCTIONS.
Caution – To Reduce the Risk of Electrical Shock and Fire
1. This equipment is designed to permit connection between the earthed conductor of the DC
supply circuit and the earthing conductor equipment. See Installation Instructions.
2. All servicing must be undertaken only by qualified service personnel. There are not user
serviceable parts inside the unit.
3. DO NOT plug in, turn on or attempt to operate an obviously damaged unit.
4. Ensure that the chassis ventilation openings in the unit are NOT BLOCKED.
5. Replace a blown fuse ONLY with the same type and rating as is marked on the safety label
adjacent to the power inlet, housing the fuse.
6. Do not operate the device in a location where the maximum ambient temperature exceeds
40°C/104°F.
7. Be sure to unplug the power supply cord from the wall socket BEFORE attempting to remove
and/or check the main power fuse.
CLASS 1 LASER PRODUCT AND REFERENCE TO THE MOST RECENT LASER STANDARDS IEC 60
825-1:1993 + A1:1997 + A2:2001 AND EN 60825-1:1994+A1:1996+ A2:2001
AC units for Denmark, Finland, Norway, Sweden (marked on product):
• Denmark - “Unit is class I - unit to be used with an AC cord set suitable with Denmark
deviations. The cord includes an earthing conductor. The Unit is to be plugged into a wall socket
outlet which is connected to a protective earth. Socket outlets which are not connected to earth
are not to be used!”
• Finland - (Marking label and in manual) - “Laite on liitettävä suojamaadoituskoskettimilla
varustettuun pistorasiaan”
• Norway (Marking label and in manual) - “Apparatet må tilkoples jordet stikkontakt”
• Unit is intended for connection to IT power systems for Norway only.
• Sweden (Marking label and in manual) - “Apparaten skall anslutas till jordat uttag.”
To connect the power connection:

1. Connect the power cable to the main socket, located on the rear panel of the device.
2. Connect the power cable to the grounded AC outlet.
CAUTION
Risk of electric shock and energy hazard. Disconnecting one power supply disconnects only one
power supply module. To isolate the unit completely, disconnect all power supplies.

Instructions de sécurité
AVERTISSEMENT
Un dispositif de déconnexion facilement accessible sera incorporé au câblage du bâtiment.
En raison des risques de chocs électriques et des dangers énergétiques, mécaniques et d’incendie,
chaque procédure impliquant l’ouverture des panneaux ou le remplacement de composants sera
exécutée par du personnel qualifié.
Pour réduire les risques d’incendie et de chocs électriques, déconnectez le dispositif du bloc
d’alimentation avant de retirer le couvercle ou les panneaux.
La figure suivante montre l’étiquette d’avertissement apposée sur les plateformes Radware dotées
de plus d’une source d’alimentation électrique.
Figure 3: Étiquette d’avertissement de danger de chocs électriques
AVERTISSEMENT DE SÉCURITÉ POUR LES SYSTÈMES DOTÉS DE DEUX SOURCES D’ALIMENTATION

ÉLECTRIQUE (EN CHINOIS)
La figure suivante représente l’étiquette d’avertissement pour les plateformes Radware dotées de
deux sources d’alimentation électrique.
Figure 4: Avertissement de sécurité pour les systèmes dotes de deux sources d’alimentation
électrique (en chinois)
Traduction de la Avertissement de sécurité pour les systèmes dotes de deux sources d’alimentation
électrique (en chinois):
Cette unité est dotée de plus d’une source d’alimentation électrique. Déconnectez toutes les sources
d’alimentation électrique avant d’entretenir l’appareil ceci pour éviter tout choc électrique.
ENTRETIEN
N’effectuez aucun entretien autre que ceux répertoriés dans le manuel d’instructions, à moins d’être
qualifié en la matière. Aucune pièce à l’intérieur de l’unité ne peut être remplacée ou réparée.
HAUTE TENSION
Tout réglage, opération d’entretien et réparation de l’instrument ouvert sous tension doit être évité.
Si cela s’avère indispensable, confiez cette opération à une personne qualifiée et consciente des
dangers impliqués.
Les condensateurs au sein de l’unité risquent d’être chargés même si l’unité a été déconnectée de la
source d’alimentation électrique.
MISE A LA TERRE

Avant de connecter ce dispositif à la ligne électrique, les vis de protection de la borne de terre de
cette unité doivent être reliées au système de mise à la terre du bâtiment.
LASER
Cet équipement est un produit laser de classe 1, conforme à la norme IEC60825 - 1: 1993 + A1:
1997 + A2: 2001.
FUSIBLES
Assurez-vous que, seuls les fusibles à courant nominal requis et de type spécifié sont utilisés en
remplacement. L’usage de fusibles réparés et le court-circuitage des porte-fusibles doivent être
évités. Lorsqu’il est pratiquement certain que la protection offerte par les fusibles a été détériorée,
l’instrument doit être désactivé et sécurisé contre toute opération involontaire.
TENSION DE LIGNE
Avant de connecter cet instrument à la ligne électrique, vérifiez que la tension de la source
d’alimentation correspond aux exigences de l’instrument. Consultez les spécifications propres à
l’alimentation nominale correcte du dispositif.
Les plateformes alimentées en 48 CC ont une tolérance d’entrée comprise entre 36 et 72 V CC.
MODIFICATIONS DES SPÉCIFICATIONS
Les spécifications sont sujettes à changement sans notice préalable.
Remarque: Cet équipement a été testé et déclaré conforme aux limites définies pour un appareil
numérique de classe A, conformément au paragraphe 15B de la réglementation FCC et EN55022
Classe A, EN 55024, EN 61000-3-2; EN 61000-3-3; IEC 61000 4-2 to 4-6, IEC 61000 4-8, et IEC
61000-4-11, pour la marque de conformité de la CE. Ces limites sont fixées pour fournir une
protection raisonnable contre les interférences nuisibles, lorsque l’équipement est utilisé dans un
environnement commercial. Cet équipement génère, utilise et peut émettre des fréquences radio et,
s’il n’est pas installé et utilisé conformément au manuel d’instructions, peut entraîner des
interférences nuisibles aux communications radio. Le fonctionnement de cet équipement dans une
zone résidentielle est susceptible de provoquer des interférences nuisibles, auquel cas l’utilisateur
devra corriger le problème à ses propres frais.
NOTICE SPÉCIALE POUR LES UTILISATEURS NORD-AMÉRICAINS
Pour un raccordement électrique en Amérique du Nord, sélectionnez un cordon d’alimentation
homologué UL et certifié CSA 3 - conducteur, [18 AWG], muni d’une prise moulée à son extrémité,
de 125 V, [10 A], d’une longueur minimale de 1,5 m [six pieds] et maximale de 4,5m...Pour la
connexion européenne, choisissez un cordon d’alimentation mondialement homologué et marqué
“<HAR>”, 3 - conducteur, câble de 0,75 mm2 minimum, de 300 V, avec une gaine en PVC isolée. La
prise à l’extrémité du cordon, sera dotée d’un sceau moulé indiquant: 250 V, 3 A.
ZONE A ACCÈS RESTREINT
L’équipement alimenté en CC ne pourra être installé que dans une zone à accès restreint.
CODES D’INSTALLATION
Ce dispositif doit être installé en conformité avec les codes électriques nationaux. En Amérique du
Nord, l’équipement sera installé en conformité avec le code électrique national américain, articles
110-16, 110 -17, et 110 -18 et le code électrique canadien, Section 12.
INTERCONNEXION DES UNÎTES
Les câbles de connexion à l’unité RS232 et aux interfaces Ethernet seront certifiés UL, type DP-1 ou
DP-2. (Remarque- s’ils ne résident pas dans un circuit LPS).
PROTECTION CONTRE LES SURCHARGES
Un circuit de dérivation, facilement accessible, sur le dispositif de protection du courant de 15 A doit
être intégré au câblage du bâtiment pour chaque puissance consommée.
BATTERIES REMPLAÇABLES

Si l’équipement est fourni avec une batterie, et qu’elle est remplacée par un type de batterie
incorrect, elle est susceptible d’exploser. C’est le cas pour certaines batteries au lithium, les
éléments suivants sont donc applicables:
• Si la batterie est placée dans une zone d’accès opérateur, une marque est indiquée sur la
batterie ou une remarque est insérée, aussi bien dans les instructions d’exploitation que
d’entretien.
• Si la batterie est placée ailleurs dans l’équipement, une marque est indiquée sur la batterie ou
une remarque est insérée dans les instructions d’entretien.
Cette marque ou remarque inclut l’avertissement textuel suivant:

AVERTISSEMENT
RISQUE D’EXPLOSION SI LA BATTERIE EST REMPLACÉE PAR UN MODÈLE INCORRECT. METTRE AU
REBUT LES BATTERIES CONFORMÉMENT AUX INSTRUCTIONS.
Attention - Pour réduire les risques de chocs électriques et d’incendie
1. Cet équipement est conçu pour permettre la connexion entre le conducteur de mise à la terre du
circuit électrique CC et l’équipement de mise à la terre. Voir les instructions d’installation.
2. Tout entretien sera entrepris par du personnel qualifié. Aucune pièce à l’intérieur de l’unité ne
peut être remplacée ou réparée.
3. NE branchez pas, n’allumez pas ou n’essayez pas d’utiliser une unité manifestement
endommagée.
4. Vérifiez que l’orifice de ventilation du châssis dans l’unité n’est PAS OBSTRUE.
5. Remplacez le fusible endommagé par un modèle similaire de même puissance, tel qu’indiqué sur
l’étiquette de sécurité adjacente à l’arrivée électrique hébergeant le fusible.
6. Ne faites pas fonctionner l’appareil dans un endroit, où la température ambiante dépasse la
valeur maximale autorisée. 40°C/104°F.
7. Débranchez le cordon électrique de la prise murale AVANT d’essayer de retirer et/ou de vérifier
le fusible d’alimentation principal.
PRODUIT LASER DE CLASSE 1 ET RÉFÉRENCE AUX NORMES LASER LES PLUS RÉCENTES: IEC 60
825-1: 1993 + A1: 1997 + A2: 2001 ET EN 60825-1: 1994+A1: 1996+ A2: 2001
Unités à CA pour le Danemark, la Finlande, la Norvège, la Suède (indiqué sur le produit):
• Danemark - Unité de classe 1 - qui doit être utilisée avec un cordon CA compatible avec les
déviations du Danemark. Le cordon inclut un conducteur de mise à la terre. L’unité sera
branchée à une prise murale, mise à la terre. Les prises non-mises à la terre ne seront pas
utilisées!
• Finlande (Étiquette et inscription dans le manuel) - Laite on liitettävä
suojamaadoituskoskettimilla varustettuun pistorasiaan
• Norvège (Étiquette et inscription dans le manuel) - Apparatet må tilkoples jordet stikkontakt
• L’unité peut être connectée à un système électrique IT (en Norvège uniquement).
• Suède (Étiquette et inscription dans le manuel) - Apparaten skall anslutas till jordat uttag.
Pour brancher à l’alimentation électrique:

1. Branchez le câble d’alimentation à la prise principale, située sur le panneau arrière de l’unité.
2. Connectez le câble d’alimentation à la prise CA mise à la terre.
AVERTISSEMENT
Risque de choc électrique et danger énergétique. La déconnexion d’une source d’alimentation
électrique ne débranche qu’un seul module électrique. Pour isoler complètement l’unité, débranchez
toutes les sources d’alimentation électrique.
ATTENTION

Risque de choc et de danger électriques. Le débranchement d’une seule alimentation stabilisée ne

débranche qu’un module “Alimentation Stabilisée”. Pour Isoler complètement le module en cause, il
faut débrancher toutes les alimentations stabilisées.
Attention: Pour Réduire Les Risques d’Électrocution et d’Incendie
1. Toutes les opérations d’entretien seront effectuées UNIQUEMENT par du personnel d’entretien
qualifié. Aucun composant ne peut être entretenu ou remplacée par l’utilisateur.
2. NE PAS connecter, mettre sous tension ou essayer d’utiliser une unité visiblement défectueuse.
3. Assurez-vous que les ouvertures de ventilation du châssis NE SONT PAS OBSTRUÉES.
4. Remplacez un fusible qui a sauté SEULEMENT par un fusible du même type et de même
capacité, comme indiqué sur l’étiquette de sécurité proche de l’entrée de l’alimentation qui
contient le fusible.
5. NE PAS UTILISER l’équipement dans des locaux dont la température maximale dépasse 40
degrés Centigrades.
6. Assurez vous que le cordon d’alimentation a été déconnecté AVANT d’essayer de l’enlever et/ou
vérifier le fusible de l’alimentation générale.
Sicherheitsanweisungen
VORSICHT
Die Elektroinstallation des Gebäudes muss ein unverzüglich zugängliches Stromunterbrechungsgerät
integrieren.
Aufgrund des Stromschlagrisikos und der Energie-, mechanische und Feuergefahr dürfen Vorgänge,
in deren Verlauf Abdeckungen entfernt oder Elemente ausgetauscht werden, ausschließlich von
qualifiziertem Servicepersonal durchgeführt werden.
Zur Reduzierung der Feuer- und Stromschlaggefahr muss das Gerät vor der Entfernung der
Abdeckung oder der Paneele von der Stromversorgung getrennt werden.
Folgende Abbildung zeigt das VORSICHT-Etikett, das auf die Radware-Plattformen mit
Doppelspeisung angebracht ist.
Figure 5: Warnetikett Stromschlaggefahr
SICHERHEITSHINWEIS IN CHINESISCHER SPRACHE FÜR SYSTEME MIT DOPPELSPEISUNG

Die folgende Abbildung ist die Warnung für Radware-Plattformen mit Doppelspeisung.
Figure 6: Sicherheitshinweis in chinesischer Sprache für Systeme mit Doppelspeisung

Übersetzung von Sicherheitshinweis in chinesischer Sprache für Systeme mit Doppelspeisung:

Die Einheit verfügt über mehr als eine Stromversorgungsquelle. Ziehen Sie zur Verhinderung von
Stromschlag vor Wartungsarbeiten sämtliche Stromversorgungsleitungen ab.
WARTUNG
Führen Sie keinerlei Wartungsarbeiten aus, die nicht in der Betriebsanleitung angeführt sind, es sei
denn, Sie sind dafür qualifiziert. Es gibt innerhalb des Gerätes keine wartungsfähigen Teile.
HOCHSPANNUNG
Jegliche Einstellungs-, Instandhaltungs- und Reparaturarbeiten am geöffneten Gerät unter
Spannung müssen so weit wie möglich vermieden werden. Sind sie nicht vermeidbar, dürfen sie
ausschließlich von qualifizierten Personen ausgeführt werden, die sich der Gefahr bewusst sind.
Innerhalb des Gerätes befindliche Kondensatoren können auch dann noch Ladung enthalten, wenn
das Gerät von der Stromversorgung abgeschnitten wurde.
ERDUNG
Bevor das Gerät an die Stromversorgung angeschlossen wird, müssen die Schrauben der
Erdungsleitung des Gerätes an die Erdung der Gebäudeverkabelung angeschlossen werden.
LASER
Dieses Gerät ist ein Laser-Produkt der Klasse 1 in Übereinstimmung mit IEC60825 - 1: 1993 +
A1:1997 + A2:2001 Standard.
SICHERUNGEN
Vergewissern Sie sich, dass nur Sicherungen mit der erforderlichen Stromstärke und der
angeführten Art verwendet werden. Die Verwendung reparierter Sicherungen sowie die
Kurzschließung von Sicherungsfassungen muss vermieden werden. In Fällen, in denen
wahrscheinlich ist, dass der von den Sicherungen gebotene Schutz beeinträchtigt ist, muss das
Gerät abgeschaltet und gegen unbeabsichtigten Betrieb gesichert werden.
LEITUNGSSPANNUNG
Vor Anschluss dieses Gerätes an die Stromversorgung ist zu gewährleisten, dass die Spannung der
Stromquelle den Anforderungen des Gerätes entspricht. Beachten Sie die technischen Angaben
bezüglich der korrekten elektrischen Werte des Gerätes.
Plattformen mit 48 V DC verfügen über eine Eingangstoleranz von 36-72 V DC.
ÄNDERUNGEN DER TECHNISCHEN ANGABEN
Änderungen der technischen Spezifikationen bleiben vorbehalten.
Hinweis: Dieses Gerät wurde geprüft und entspricht den Beschränkungen von digitalen Geräten der
Klasse 1 gemäß Teil 15B FCC-Vorschriften und EN55022 Klasse A, EN55024; EN 61000-3-2; EN; IEC
61000 4-2 to 4-6, IEC 61000 4-8 und IEC 61000-4- 11 für Konformität mit der CE-Bezeichnung.
Diese Beschränkungen dienen dem angemessenen Schutz vor schädlichen Interferenzen bei Betrieb
des Gerätes in kommerziellem Umfeld. Dieses Gerät erzeugt, verwendet und strahlt
elektromagnetische Hochfrequenzstrahlung aus. Wird es nicht entsprechend den Anweisungen im
Handbuch montiert und benutzt, könnte es mit dem Funkverkehr interferieren und ihn
beeinträchtigen. Der Betrieb dieses Gerätes in Wohnbereichen wird höchstwahrscheinlich zu
schädlichen Interferenzen führen. In einem solchen Fall wäre der Benutzer verpflichtet, diese
Interferenzen auf eigene Kosten zu korrigieren.
BESONDERER HINWEIS FÜR BENUTZER IN NORDAMERIKA
Wählen Sie für den Netzstromanschluss in Nordamerika ein Stromkabel, das in der UL aufgeführt
und CSA-zertifiziert ist 3 Leiter, [18 AWG], endend in einem gegossenen Stecker, für 125 V, [10 A],
mit einer Mindestlänge von 1,5 m [sechs Fuß], doch nicht länger als 4,5 m. Für europäische
Anschlüsse verwenden Sie ein international harmonisiertes, mit “<HAR>” markiertes Stromkabel,
mit 3 Leitern von mindestens 0,75 mm2, für 300 V, mit PVC-Umkleidung. Das Kabel muss in einem
gegossenen Stecker für 250 V, 3 A enden.
BEREICH MIT EINGESCHRÄNKTEM ZUGANG
Das mit Gleichstrom betriebene Gerät darf nur in einem Bereich mit eingeschränktem Zugang
montiert werden.

INSTALLATIONSCODES
Dieses Gerät muss gemäß der landesspezifischen elektrischen Codes montiert werden. In
Nordamerika müssen Geräte entsprechend dem US National Electrical Code, Artikel 110 - 16, 110 -
17 und 110 - 18, sowie dem Canadian Electrical Code, Abschnitt 12, montiert werden.
VERKOPPLUNG VON GERÄTEN Kabel für die Verbindung des Gerätes mit RS232- und Ethernet-
müssen UL-zertifiziert und vom Typ DP-1 oder DP-2 sein. (Anmerkung: bei Aufenthalt in einem
nicht-LPS-Stromkreis)
ÜBERSTROMSCHUTZ
Ein gut zugänglicher aufgeführter Überstromschutz mit Abzweigstromkreis und 15 A Stärke muss für
jede Stromeingabe in der Gebäudeverkabelung integriert sein.
AUSTAUSCHBARE BATTERIEN
Wird ein Gerät mit einer austauschbaren Batterie geliefert und für diese Batterie durch einen
falschen Batterietyp ersetzt, könnte dies zu einer Explosion führen. Dies trifft zu für manche Arten
von Lithiumsbatterien zu, und das folgende gilt es zu beachten:
• Wird die Batterie in einem Bereich für Bediener eingesetzt, findet sich in der Nähe der Batterie
eine Markierung oder Erklärung sowohl im Betriebshandbuch als auch in der Wartungsanleitung.
• Ist die Batterie an einer anderen Stelle im Gerät eingesetzt, findet sich in der Nähe der Batterie
eine Markierung oder einer Erklärung in der Wartungsanleitung.
Diese Markierung oder Erklärung enthält den folgenden Warntext:

VORSICHT
EXPLOSIONSGEFAHR, FALLS BATTERIE DURCH EINEN FALSCHEN BATTERIETYP ERSETZT WIRD.
GEBRAUCHTE BATTERIEN DEN ANWEISUNGEN ENTSPRECHEND ENTSORGEN.
• Denmark - “Unit is class I - mit Wechselstromkabel benutzen, dass für die Abweichungen in
Dänemark eingestellt ist. Das Kabel ist mit einem Erdungsdraht versehen. Das Kabel wird in eine
geerdete Wandsteckdose angeschlossen. Keine Steckdosen ohne Erdungsleitung verwenden!”
• Finland - (Markierungsetikett und im Handbuch) - Laite on liitettävä
suojamaadoituskoskettimilla varustettuun pistorasiaan
• Norway - (Markierungsetikett und im Handbuch) - Apparatet må tilkoples jordet stikkontakt
Ausschließlich für Anschluss an IT-Netzstromsysteme in Norwegen vorgesehen
• Sweden - (Markierungsetikett und im Handbuch) - Apparaten skall anslutas till jordat uttag.
Anschluss des Stromkabels:

1. Schließen Sie das Stromkabel an den Hauptanschluss auf der Rückseite des Gerätes an.
2. Schließen Sie das Stromkabel an den geerdeten Wechselstromanschluss an.
VORSICHT
Stromschlag- und Energiegefahr Die Trennung einer Stromquelle trennt nur ein
Stromversorgungsmodul von der Stromversorgung. Um das Gerät komplett zu isolieren, muss es
von der gesamten Stromversorgung getrennt werden.
Vorsicht - Zur Reduzierung der Stromschlag- und Feuergefahr
1. Dieses Gerät ist dazu ausgelegt, die Verbindung zwischen der geerdeten Leitung des
Gleichstromkreises und dem Erdungsleiter des Gerätes zu ermöglichen. Siehe
Montageanleitung.
2. Wartungsarbeiten jeglicher Art dürfen nur von qualifiziertem Servicepersonal ausgeführt
werden. Es gibt innerhalb des Gerätes keine vom Benutzer zu wartenden Teile.
3. Versuchen Sie nicht, ein offensichtlich beschädigtes Gerät an den Stromkreis anzuschließen,
einzuschalten oder zu betreiben.
4. Vergewissern Sie sich, dass sie Lüftungsöffnungen im Gehäuse des Gerätes NICHT BLOCKIERT
SIND.

5. Ersetzen Sie eine durchgebrannte Sicherung ausschließlich mit dem selben Typ und von der
selben Stärke, die auf dem Sicherheitsetikett angeführt sind, das sich neben dem
Stromkabelanschluss, am Sicherungsgehäuse.
6. Betreiben Sie das Gerät nicht an einem Standort, an dem die Höchsttemperatur der Umgebung
40°C überschreitet.
7. Vergewissern Sie sich, das Stromkabel aus dem Wandstecker zu ziehen, BEVOR Sie die
Hauptsicherung entfernen und/oder prüfen.
Electromagnetic-Interference Statements
The following statements are presented in English, French, and German.
Electromagnetic-Interference Statements
SPECIFICATION CHANGES
Specifications are subject to change without notice.
Note: This equipment has been tested and found to comply with the limits for a Class A digital
device pursuant to Part 15B of the FCC Rules and EN55022 Class A, EN 55024; EN 61000-3-2; EN
61000-3-3; IEC 61000 4-2 to 4-6, IEC 61000 4-8 and IEC 61000-4-11For CE MARK Compliance.
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. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user is required to correct
the interference at his own expense.
VCCI ELECTROMAGNETIC-INTERFERENCE STATEMENTS
Figure 7: Statement for Class A VCCI-certified Equipment
Translation of Statement for Class A VCCI-certified Equipment:

This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment,
radio disturbance may occur, in which case, the user may be required to take corrective actions.
KCC KOREA
Figure 8: KCC—Korea Communications Commission Certificate of Broadcasting and Communication

Equipment

Figure 9: Statement For Class A KCC-certified Equipment in Korean
Translation of Statement For Class A KCC-certified Equipment in Korean:

This equipment is Industrial (Class A) electromagnetic wave suitability equipment and seller or user
should take notice of it, and this equipment is to be used in the places except for home.
BSMI
Figure 10: Statement for Class A BSMI-certified Equipment

這是甲類的資訊產品，在居住的環境使用中時，可能會造成射頻
干擾，在這種情況下，使用者會被要求採取某些適當的對策。
Translation of Statement for Class A BSMI-certified Equipment:

This is a Class A product, in use in a residential environment, it may cause radio interference in
which case the user will be required to take adequate measures.
Déclarations sur les Interférences Électromagnétiques

MODIFICATIONS DES SPÉCIFICATIONS
Les spécifications sont sujettes à changement sans notice préalable.
Remarque: Cet équipement a été testé et déclaré conforme aux limites définies pour un appareil
numérique de classe A, conformément au paragraphe 15B de la réglementation FCC et EN55022
Classe A, EN 55024, EN 61000-3-2; EN 61000-3-3; IEC 61000 4-2 to 4-6, IEC 61000 4-8, et IEC
61000-4-11, pour la marque de conformité de la CE. Ces limites sont fixées pour fournir une
protection raisonnable contre les interférences nuisibles, lorsque l’équipement est utilisé dans un
environnement commercial. Cet équipement génère, utilise et peut émettre des fréquences radio et,
s’il n’est pas installé et utilisé conformément au manuel d’instructions, peut entraîner des
interférences nuisibles aux communications radio. Le fonctionnement de cet équipement dans une
zone résidentielle est susceptible de provoquer des interférences nuisibles, auquel cas l’utilisateur
devra corriger le problème à ses propres frais.
DÉCLARATIONS SUR LES INTERFÉRENCES ÉLECTROMAGNÉTIQUES VCCI
Figure 11: Déclaration pour l’équipement de classe A certifié VCCI
Traduction de la Déclaration pour l’équipement de classe A certifié VCCI:

Il s’agit d’un produit de classe A, basé sur la norme du Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). Si cet équipement est utilisé dans un environnement
domestique, des perturbations radioélectriques sont susceptibles d’apparaître. Si tel est le cas,
l’utilisateur sera tenu de prendre des mesures correctives.
KCC Corée

Figure 12: KCC—Certificat de la commission des communications de Corée pour les equipements de
radiodiffusion et communication.
Figure 13: Déclaration pour l’équipement de classe A certifié KCC en langue coréenne
Translation de la Déclaration pour l’équipement de classe A certifié KCC en langue coréenne:

Cet équipement est un matériel (classe A) en adéquation aux ondes électromagnétiques et le
vendeur ou l’utilisateur doit prendre cela en compte. Ce matériel est donc fait pour être utilisé
ailleurs qu’ á la maison.
BSMI
Figure 14: Déclaration pour l’équipement de classe A certifié BSMI

Translation de la Déclaration pour l’équipement de classe A certifié BSMI:

Il s’agit d’un produit de Classe A; utilisé dans un environnement résidentiel il peut provoquer des
interférences, l’utilisateur devra alors prendre les mesures adéquates.
Erklärungen zu Elektromagnetischer Interferenz

ÄNDERUNGEN DER TECHNISCHEN ANGABEN
Änderungen der technischen Spezifikationen bleiben vorbehalten.
Hinweis: Dieses Gerät wurde geprüft und entspricht den Beschränkungen von digitalen Geräten der
Klasse 1 gemäß Teil 15B FCC-Vorschriften und EN55022 Klasse A, EN55024; EN 61000-3-2; EN; IEC
61000 4-2 to 4-6, IEC 61000 4-8 und IEC 61000-4- 11 für Konformität mit der CE-Bezeichnung.
Diese Beschränkungen dienen dem angemessenen Schutz vor schädlichen Interferenzen bei Betrieb
des Gerätes in kommerziellem Umfeld. Dieses Gerät erzeugt, verwendet und strahlt
elektromagnetische Hochfrequenzstrahlung aus. Wird es nicht entsprechend den Anweisungen im
Handbuch montiert und benutzt, könnte es mit dem Funkverkehr interferieren und ihn
beeinträchtigen. Der Betrieb dieses Gerätes in Wohnbereichen wird höchstwahrscheinlich zu
schädlichen Interferenzen führen. In einem solchen Fall wäre der Benutzer verpflichtet, diese
Interferenzen auf eigene Kosten zu korrigieren.
ERKLÄRUNG DER VCCI ZU ELEKTROMAGNETISCHER INTERFERENZ

Figure 15: Erklärung zu VCCI-zertifizierten Geräten der Klasse A
Übersetzung von Erklärung zu VCCI-zertifizierten Geräten der Klasse A:

Dies ist ein Produkt der Klasse A gemäß den Normen des Voluntary Control Council for Interference
by Information Technology Equipment (VCCI). Wird dieses Gerät in einem Wohnbereich benutzt,
können elektromagnetische Störungen auftreten. In einem solchen Fall wäre der Benutzer
verpflichtet, korrigierend einzugreifen.
KCC KOREA
Figure 16: KCC—Korea Communications Commission Zertifikat für Rundfunk-und

Nachrichtentechnik
Figure 17: Erklärung zu KCC-zertifizierten Geräten der Klasse A
Übersetzung von Erklärung zu KCC-zertifizierten Geräten der Klasse A:

Verkäufer oder Nutzer sollten davon Kenntnis nehmen, daß dieses Gerät der Klasse A für industriell
elektromagnetische Wellen geeignete Geräten angehört und dass diese Geräte nicht für den
heimischen Gebrauch bestimmt sind.
BSMI
Figure 18: Erklärung zu BSMI-zertifizierten Geräten der Klasse A

Übersetzung von Erklärung zu BSMI-zertifizierten Geräten der Klasse A:

Dies ist ein Class A Produkt, bei Gebrauch in einer Wohnumgebung kann es zu Funkstörungen
kommen, in diesem Fall ist der Benutzer verpflichtet, angemessene Maßnahmen zu ergreifen.

Altitude and Climate Warning

This warning only applies to The People’s Republic of China.
1. 对于在非热带气候条件下运行的设备而言，Tma：为制造商规范允许的最大环境温度，或者为 25°C，采用两
者中的较大者。
2. 关于在海拔不超过 2000m 或者在非热带气候地区使用的设备，附加警告要求如下：
关于在海拔不超过 2000m 的地区使用的设备，必须在随时可见的位置处粘贴包含如下内容或者类似用语的警告标

记、或者附件 DD 中的符号。
“ 只可在海拔不超过 2000m 的位置使用。”
关于在非热带气候地区使用的设备，必须在随时可见的位置处粘贴包含如下内容的警告标记：
附件 DD：有关新安全警告标记的说明。
DD.1 海拔警告标记
标记含义：设备的评估仅基于 2000m 以下的海拔高度，因此设备只适用于该运行条件。如果在海拔超过 2000m 的

位置使用设备，可能会存在某些安全隐患。
DD.2 气候警告标记
标记含义：设备的评估仅基于温带气候条件，因此设备只适用于该运行条件。如果在热带气候地区使用设备，可能
会存在某些安全隐患。
Document Conventions
The following describes the conventions and symbols that this guide uses:

Item Description Description Beschreibung

An example scenario Un scénario d’exemple Ein Beispielszenarium
Example
Possible damage to Endommagement Mögliche Schäden an
equipment, software, or possible de l’équipement, Gerät, Software oder
Caution: data des données ou du Daten
logiciel
Additional information Informations Zusätzliche
complémentaires Informationen
Note:
A statement and Références et Eine Erklärung und
instructions instructions Anweisungen
To
A suggestion or Une suggestion ou Ein Vorschlag oder eine
workaround solution Umgehung
Tip:
Possible physical harm to Blessure possible de Verletzungsgefahr des
the operator l’opérateur Bedieners
Warning:

Table of Contents
Table of Contents
Important Notices .......................................................................................................... 3
Copyright Notices ......................................................................................................... 4
Standard Warranty ........................................................................................................ 7
Limitations on Warranty and Liability ............................................................................. 9
Safety Instructions ....................................................................................................... 10
Electromagnetic-Interference Statements ................................................................... 19
Altitude and Climate Warning ...................................................................................... 23
Document Conventions ............................................................................................... 23
Chapter 1 – Overview.............................................................................................. 33
Appliance Features ..................................................................................................... 33
Configuration Options .................................................................................................. 34
FastView Deployment .................................................................................................. 34
FastView Appliance ............................................................................................................. 34
FastView Virtual Appliance .................................................................................................. 34
FastView Cloud Service ....................................................................................................... 34
FastView as Part of Alteon NG ............................................................................................ 34
Quick Setup ................................................................................................................. 35
Understanding FastView Components ................................................................................ 35
Physical Installation ............................................................................................................. 35
Network Configuration ......................................................................................................... 35
Securing the Appliance ........................................................................................................ 35
FastView Configuration ........................................................................................................ 36
Where to Go Next ................................................................................................................ 36
Chapter 2 – Installation........................................................................................... 37
Physical Appliance Installation .................................................................................... 37
Your Network Topology ....................................................................................................... 37
Physical Installation ............................................................................................................. 38
Connecting to the CLI .......................................................................................................... 40
Initial Login and Configuration with KVM ..................................................................... 41
Accessing FastView from the KVM Console ....................................................................... 41
Accessing SharePath from the KVM Console ..................................................................... 42
FastView Initial Configuration from the KVM Console ......................................................... 42
SharePath Initial Configuration from the KVM Console ....................................................... 42
FastView VA Installation .............................................................................................. 43
VMware Installation ............................................................................................................. 43
Connecting to the CLI .......................................................................................................... 44
FastView Initial Configuration .............................................................................................. 45
SharePath Initial Configuration ............................................................................................ 46

Table of Contents
FastView Cloud Service Installation ........................................................................... 47

Cloud Service Network Topology ........................................................................................ 48
DNS Services ...................................................................................................................... 48
CDN Services ...................................................................................................................... 48
Web Monitoring Services .................................................................................................... 49
Removing FastView Services .............................................................................................. 49
FastView Initial Configuration ..................................................................................... 49
Licensing FastView ..................................................................................................... 51
Log into the Web Management Interface ............................................................................ 51
Navigate to License Management ....................................................................................... 52
Update the License ............................................................................................................. 52
Chapter 3 – Network Configuration Fine Tuning ................................................. 53

Appliance Setup ......................................................................................................... 53
Network Interface ................................................................................................................ 53
DNS Servers ....................................................................................................................... 55
NTP Servers ........................................................................................................................ 55
Appliance Name ......................................................................................................... 56
CLI Networking Options .............................................................................................. 56
Routing ....................................................................................................................... 57
Redundancy ............................................................................................................... 57
Synchronized Cluster .......................................................................................................... 57
Chapter 4 – Web Management Interface............................................................... 63

Overview ..................................................................................................................... 63
Web Management Interface Overview Page .............................................................. 63
Offload Gauge ..................................................................................................................... 63
Summary Sections .............................................................................................................. 64
Appliance Information ......................................................................................................... 65
Traffic Flow .......................................................................................................................... 65
Other Information ................................................................................................................ 66
More on Appliance Health ................................................................................................... 66
Chapter 5 – Setting up Your Virtual Servers ....................................................... 67

Virtual Servers ............................................................................................................ 67
Working with Virtual Servers ............................................................................................... 68
SSL Certificates .................................................................................................................. 72
Testing Virtual Server Traffic ............................................................................................... 76
Chapter 6 – Working with Web Applications....................................................... 79

Web Applications ........................................................................................................ 79
Defining Web Applications .................................................................................................. 79
New Web Application Wizard .............................................................................................. 81

Table of Contents
Testing Web Applications .................................................................................................... 83

Treated Domains ................................................................................................................. 83
Classification Rules ............................................................................................................. 88
Deferrals .............................................................................................................................. 94
Exclusions (Excluded Treatments) ...................................................................................... 95
Chapter 7 – Working with Treatment Sets ........................................................... 97

Defining Treatment Sets .............................................................................................. 97
Treatment Sets in Web Applications .................................................................................... 97
Treatments not Working ...................................................................................................... 98
Desktop and Mobile Treatment Sets ................................................................................... 98
Working with Treatment Sets ............................................................................................... 98
Treatments ........................................................................................................................ 101
Dynamic Browser Caching ............................................................................................... 102
Dynamic Connection Maximizer ....................................................................................... 110
Dynamic Resource Consolidation ..................................................................................... 113
Rapid Rendering ............................................................................................................... 120
Payload Reduction ............................................................................................................ 126
Search and Replace ......................................................................................................... 132
Templated Deferrals ........................................................................................................ 133
Long-Tail Site Acceleration ............................................................................................... 134
Chapter 8 – Examining Appliance Health ........................................................... 137

Status Messages ...................................................................................................... 137
Banners ............................................................................................................................ 137
System Status Messages ................................................................................................. 138
System Health .................................................................................................................. 138
CLI Banners ...................................................................................................................... 139
Web Management Interface Overview Page ............................................................ 139
Packet Capture ......................................................................................................... 139
Event Logs ............................................................................................................... 140
Selecting Individual Logs .................................................................................................. 141
Searching Logs ................................................................................................................. 141
Generating Support Packages .......................................................................................... 142
Reading the Event Logs ................................................................................................... 143
Log Rotation and Deletion ................................................................................................ 144
Diagnostic Summary ................................................................................................ 144
Optimization Status ........................................................................................................... 144
Workload Monitor .............................................................................................................. 145
Legend .............................................................................................................................. 146
Examining Appliance Treatment ............................................................................... 147
Parameters, Headers, and Cookies .................................................................................. 147
Content Headers ...................................................................................................... 149
Headers Sent to the Web Client ....................................................................................... 150

Table of Contents
Headers Sent to the Web Server ...................................................................................... 151

Cookies ..................................................................................................................... 152
SL_Audience ..................................................................................................................... 152
SL_UVId ............................................................................................................................ 152
SL_ClassKey ..................................................................................................................... 153
Treatment Files ......................................................................................................... 153
slhead.js ............................................................................................................................ 153
slpre.js ............................................................................................................................... 153
pdata.js .............................................................................................................................. 154
cdata.js .............................................................................................................................. 154
adata.js .............................................................................................................................. 154
slpir.js ................................................................................................................................ 154
x-img ................................................................................................................................. 154
x-css.css ........................................................................................................................... 154
x-js.js ................................................................................................................................. 154
i-js.js .................................................................................................................................. 154
mhtml.mhtm ...................................................................................................................... 154
?Lo0P files ........................................................................................................................ 155
Debug Pages ............................................................................................................ 155
Inserted Debug Information ............................................................................................... 155
CompileInfo Pages ............................................................................................................ 155
Instruction Pages .............................................................................................................. 156
Resources Not Treating ............................................................................................ 156
Invalidation ........................................................................................................................ 156
Exclusions ......................................................................................................................... 157
Identifying Problem Resources ......................................................................................... 158
Non-Treatable Resources ................................................................................................. 158
Instruction Lists ......................................................................................................... 159
Working with Instruction Lists ............................................................................................ 159
Instruction Details .............................................................................................................. 160
Substitution Lists ............................................................................................................... 161
Treatment Information ....................................................................................................... 161
PrintCompile Instruction .................................................................................................... 162
Resource Library ...................................................................................................... 162
ETag Volatility Report ............................................................................................... 163
Chapter 9 – Performance Analysis...................................................................... 165

Integrated APM ......................................................................................................... 165
Analyzing Treatment Performance ........................................................................... 167
Start Render ...................................................................................................................... 168
Post Render ...................................................................................................................... 168
Visual Factors ................................................................................................................... 168
Other Considerations ........................................................................................................ 168
Basic Analysis Tools ................................................................................................. 168

Table of Contents
Chapter 10 – Third Party Integration ................................................................... 171

ISAPI Modules .......................................................................................................... 171
IIS 7 or Later ..................................................................................................................... 171
IIS 6 or Earlier ................................................................................................................... 171
Other Web Servers ........................................................................................................... 171
SNMP Monitoring ..................................................................................................... 171
MIBs .................................................................................................................................. 172
CDN Integration ........................................................................................................ 172
Position of FastView ......................................................................................................... 172
Resource Caching ............................................................................................................ 173
CDN Edge HTML Caching ................................................................................................ 173
Chapter 11 – Support Assistance........................................................................ 175

Advanced Features .................................................................................................. 175
Advanced Mode ................................................................................................................ 175
XML Editor ........................................................................................................................ 175
Fine Tuning Memory ......................................................................................................... 176
Browser Client Groups ...................................................................................................... 176
Remote Diagnostics ................................................................................................. 176
Configuration .................................................................................................................... 177
Chapter 12 – Security Standards......................................................................... 179

Using FastView Security Features ........................................................................... 179
Enable PCI Mode .............................................................................................................. 179
Create User Accounts ....................................................................................................... 179
Enable Syslogs ................................................................................................................. 179
Administrative Password .................................................................................................. 180
Configuring Session Timeouts .......................................................................................... 180
Add a Certificate ............................................................................................................... 180
Secure Your Appliance ..................................................................................................... 181
Using Security Standards ................................................................................................. 181
Chapter 13 – Command Line Interface................................................................ 185

Generic Commands .................................................................................................. 185
CLI Networking Options ............................................................................................ 185
Ping ................................................................................................................................... 185
Network Settings ............................................................................................................... 186
Synchronized Cluster Management .................................................................................. 187
Certificate Settings ............................................................................................................ 188
CLI Maintenance Options ......................................................................................... 188
Startup and Shutdown Commands ................................................................................... 188
Version and Upgrade Commands .................................................................................... 189
Memory Allocation Commands ......................................................................................... 189

Table of Contents
CLI Security Options ................................................................................................. 189

Appliance Administration Ports ......................................................................................... 189
General Security Settings ................................................................................................. 190
User Management ............................................................................................................. 190
Syslog Options .................................................................................................................. 190
CLI Support Options ................................................................................................. 191
Remote Diagnostics .......................................................................................................... 191
Support Traffic Captures ................................................................................................... 191
Support Packages ............................................................................................................. 192
Support Log Rotation ........................................................................................................ 192
Powering On and Off FastView ............................................................................... 193
Physically Powering FastView ........................................................................................... 193
Restarting or Rebooting the Appliance .............................................................................. 193
Upgrading FastView ................................................................................................. 194
Upgrade FastView Using a Local File (Offline Upgrade) ................................................... 194
Upgrade FastView On Request ........................................................................................ 195
Upgrading with Redundancy ............................................................................................. 195
Backup/Restore Appliance Configuration ................................................................. 196
Backup Configuration ........................................................................................................ 197
Restore Configuration ....................................................................................................... 198
Upload Configuration ........................................................................................................ 198
Flushing Appliance Cache ........................................................................................ 198
Flushing Instructions ......................................................................................................... 199
Flushing Output Cache ..................................................................................................... 199
FastView Cloud Service .................................................................................................... 201
Front Panel ............................................................................................................... 204
Back Panel ............................................................................................................... 204
Power Supplies ......................................................................................................... 204
Power Indicators ....................................................................................................... 204
Network Interface Indicators ..................................................................................... 205
Hard Drive Indicators ................................................................................................ 206
Application Performance Monitor—Overview ......................................................... 207
Key Values of Radware’s Application Performance Monitoring ....................................... 208
APM/SharePath-Server Terminology ....................................................................... 210
How APM Works ...................................................................................................... 211
APM Configuration Requirements and Limitations ................................................... 212
APM Requirements ........................................................................................................... 213
APM Limitations ................................................................................................................ 213
SharePath Server Deployment and Initial Configuration .......................................... 213
Device Configuration and Results ............................................................................ 213
Accessing the SharePath Web Interface—APM Dashboard ................................... 214
Monitoring Results .................................................................................................... 214

Table of Contents
Using APM to Troubleshoot High Latency ................................................................ 214

1—Latency Problem ......................................................................................................... 215
2—View Status of Data Center’s Application-Level SLA ................................................ 216
3—Check Data Center’s Operation .................................................................................. 217
4—Analyze Data Center’s Transaction-Level SLA .......................................................... 217
5—Check the List of Transaction Instances ..................................................................... 218
6—Analyze the User's Transaction-Level SLA ................................................................ 219
7—Check for General Application Problem ..................................................................... 220
8—Check for User Networking Problems ........................................................................ 220
9—Check Relative Latency at User Location ................................................................... 221
10—Check for Network Problem at User's Location ........................................................ 221
11—Check Global Network State .................................................................................... 222

Table of Contents

Overview
Chapter 1 – Overview
This user guide describes the entire functionality of FastView including installation, configuration,
integration with third-party features, and analysis.
FastView is a network appliance, either virtual or physical, easily deployed in front of your Web
servers. In this position, the FastView appliance can be configured to see every request/response
pair moving between the Web servers and client browsers. By monitoring these pairs, FastView can
identify opportunities to optimize the Web application and implement specific optimizations as
appropriate.
FastView configuration includes the following:
• Definition of the servers—FastView acts as a proxy for these servers. This allows Web traffic
to flow through FastView so that it can be analyzed and accelerated appropriately.
• Definition of the Web applications—FastView treats and connects to these Web applications.
This allows FastView to define the characteristics of how it responds to clients and talks to the
back-end Web servers.
• Definition of acceleration treatments—FastView applies these acceleration treatments to
Web traffic. Treatments act upon the Web traffic flowing through FastView when they are
configured to do so. This means traffic served to the user from FastView is accelerated by
shrinking content, latency, and size, while still retaining the original look and functionality of the
page.
For complete FastView implementation, you can configure the following:

• Defining Treatment Sets, page 97—This section describes the acceleration treatments that
FastView applies to traffic. Treatments act on the Web traffic flowing through FastView when
they are configured to do so. Traffic served to the user from FastView is accelerated through
shrinking its content, latency, and size, while still retaining the original look and functionality of
the page. Alteon contains a few pre-defined treatment sets for easy configuration.
• Web Applications, page 79—This section describes the Web applications that FastView treats
and connects to. This allows FastView to define the characteristics of how it responds to clients
and talks to the back-end Web servers.
Notes
This section includes the following topics:
• Appliance Features
• Configuration Options
• FastView Deployment
• Quick Setup
Appliance Features
Besides accelerating and treating traffic, FastView must have some basic proxy functionality. This
includes:
• SSL Encryption
• Redundancy
• Ability to integrate into load balanced networks
FastView provides these features as part of the appliance package.

Overview
Configuration Options
FastView has many configuration options and provides two methods for setting up the appliance.
This includes the Web Management Interface and the Command Line Interface (CLI or shell
interface). The Web Management Interface is the standard way for configuring the appliance and
contains almost all of the required features to do so. The CLI allows for only basic configuration of
the appliance and is generally only used to configure the basic network settings to initially configure
FastView.
FastView Deployment
FastView can currently be deployed in four methods:
• FastView Appliance
• FastView Virtual Appliance
• FastView Cloud Service
• FastView as Part of Alteon NG
FastView Appliance
This is the most common deployment and enables a physical appliance to be deployed with the Web
servers for configuration of multiple sites on your site.
FastView Virtual Appliance

The FastView Virtual Appliance (FastView VA) is a complete virtual appliance for VMware Virtual
Infrastructure. It has been engineered to meet key virtualization requirements, so you can be
assured of interoperability with virtualization tools. With the exception of how it is delivered, the
virtual product is identical to the Radware FastView appliance.
FastView Cloud Service

The FastView Cloud Service gives you all the powerful performance benefits of the FastView
appliance, but within the cloud. Service packages can include health monitoring, DNS failover, and
CDN packages.
FastView as Part of Alteon NG

Alteon NG is a unique solution consisting of an Alteon platform, Application Performance Monitoring
(APM), and FastView. The Alteon NG offering is built from the ground up to ensure application SLA
employing the following technologies:
• Application SLA Assurance—Complete fault isolation with virtual ADC (vADC) per application
and service, and the ability to scale up or scale out while maintaining performance, based on
Radware's ADC-VX virtualization technology.
• Application SLA Monitoring—Real-time monitoring, proactive SLA management, and
assurance based on a simple and agent-less APM module.
• Web Performance Optimization—Accelerated Web page performance for any end-user
device or any browser, applying Radware's FastView Web performance optimization technology.
For this solution, FastView VA operates with the safe techniques of Classic acceleration.
For more information on the Alteon NG deployment, refer to the Alteon NG Deployment Guide.

Overview
Quick Setup
This section provides a high-level list of steps for installing and configuring FastView for the basic
treatment of traffic. Using these steps, FastView is installed and configured in your network showing
acceleration benefit and providing diagnostic abilities. What will not be configured using these steps
is performance tuning optimized for your site. To tune FastView for your specific needs, further
configuration of the individual treatments is required.
If you are using the FastView Cloud Service, you do not need to go through the installation and
configuration steps, but you may want to understand how the appliance fits into your network. For
more information, see FastView Cloud Service Installation, page 47.
Understanding FastView Components

The following items explain the FastView components:
• Defining Treatment Sets, page 97
• Web Management Interface, page 63 and the Command Line Interface, page 185
• Event Logs, page 140 and Performance Analysis, page 165
• Third Party Integration, page 171
Physical Installation
Use the following steps to install the FastView appliance:
1. Unpack the FastView Appliance, page 39
2. Rack-Mount the FastView Appliance, page 39
3. Connect to Power, page 39
4. Connect to Network, page 39
5. Power On, page 39
Network Configuration
Use the following steps to quickly configure the network:
1. Connecting to the CLI, page 40
2. Initial Login and Configuration with KVM, page 41 or use the CLI Networking Options, page 185
on FastView
3. Licensing FastView, page 51 if not already done in the Physical Installation step
Securing the Appliance

There is no standard way of securing FastView on a network. To find out more details, see the
chapter on Security Standards, page 179. At the very least, for each installation of FastView, you
should:
1. enable the PCI Mode. For more information, see Enable PCI Mode, page 179.
2. change the Administrator password. For more information, see Administrative Password,
page 180.
3. separate unused ports using a firewall. For more information, see Install and Maintain a Firewall
Configuration to Protect Cardholder Data, page 182.

Overview
FastView Configuration
Use these steps to quickly configure FastView:
1. Web Management Interface, page 63
2. Creating and Editing Virtual Servers, page 70
3. Defining Treatment Sets, page 97
It is not necessary to create a custom treatment set at this time. You can use one of the read-only
treatment sets for testing:
1. Web Applications, page 79
2. Testing Virtual Server Traffic, page 76
Where to Go Next
Once you complete the previous steps, traffic is now flowing through FastView. Proceed to configure
FastView for full production. Radware recommends that you start by identifying which treatments
you will require to optimize your site. The following basic sections can get you started:
• Editing a Treatment Set, page 100
• ISAPI Modules, page 171
• Support Assistance, page 175

Installation
Chapter 2 – Installation
This chapter describes FastView installation for each of the following deployments:
• Physical Appliance Installation, page 37
• Initial Login and Configuration with KVM, page 41
• FastView VA Installation, page 43
• FastView Cloud Service Installation, page 47
• FastView Initial Configuration, page 49
• Licensing FastView, page 51
Physical Appliance Installation

This section describes how to install a FastView appliance in your network, including:
• Your Network Topology, page 37
• Physical Installation, page 38
• Connecting to the CLI, page 44
• Initial Login and Configuration with KVM, page 41
Your Network Topology

The first step to setting up your environment is understanding how it will fit within your network.
The following network flows describe how the appliance works with the traffic flow of your network:
• Multiple Web Servers, page 37
• Single Web Server, page 38
• Other Configurations, page 38
Multiple Web Servers

Whether you use a single appliance or multiple appliances with appropriate redundancy, using your
front-end load balancer for appropriate traffic direction is preferred in your network topology.
Figure 1: Multiple Web Server Topology, page 38 illustrates how you can use your load balancer to
direct your Web traffic to the FastView appliances and then back to a load-balanced virtual IP (VIP),
which you can distribute to your Web servers. Using this method, you can take advantage of all of
your gateway's capabilities (such as priority grouping).

Installation
Figure 1: Multiple Web Server Topology
Single Web Server

With a single Web server configuration, Radware recommends much the same setup as with a
multiple load-balanced Web server group. However, as there is only a single Web Server in the back-
end, you can redirect your traffic to the Web server from the FastView appliance instead of
redirecting it back to a load-balanced VIP on your gateway, as illustrated in Figure 2: Single Web
Server Topology, page 38.
Figure 2: Single Web Server Topology
Other Configurations
You can plan your network accordingly for many other configurations. However, Radware strongly
recommends that you use a front-end load balancer or gateway to both secure your network and
provide proper network stability.
Physical Installation
Physical installation includes the following steps:
• Unpack the FastView Appliance, page 39
• Rack-Mount the FastView Appliance, page 39
• Connect to Power, page 39
• Connect to Network, page 39
• Power On, page 39

Installation
Unpack the FastView Appliance

Remove the FastView appliance from the shipping package and identify all the components in the
shipment. Keep all the shipping materials in case you need them later.
Rack-Mount the FastView Appliance

The FastView appliance occupies 1 rack unit (RU), which is 44.45 mm (1.75 in) high. The procedure
for rack-mounting the FastView appliance varies depending on the type of rack you are using (2-post
or 4-post) and the type of rails you are using (static or sliding).
Figure 3: FastView Front Panel
To rack-mount the FastView appliance

1. Install the mounting rails into the rack in the desired location.
2. If necessary, install rails on each side of the appliance.
3. Insert the appliance into the rack and secure it.
4. Tighten all screws with a screw driver.
Connect to Power
Connect the appliance to a grounded electrical outlet or a separate power source, such as an
uninterrupted power supply (UPS) or a power distribution unit (PDU).
Connect to Network
Connect one end of a network Ethernet cable to the Interface labeled GB1 and the other end to a
Layer 2-capable switch or router on your local network.
The default FastView IP address is 192.168.10.1. If this IP address conflicts with other devices on
your network, run Initial Login and Configuration with KVM, page 41 before completing this step, to
choose a new IP address.
Figure 4: FastView Back Panel and Connectors
Power On
Press the power button. The appliance takes approximately one and a half minutes to power up.

Installation
The front panel can be protected by a lockable bezel. After powering up the appliance, put the front
bezel in place and lock it.
Note: You can shut down the appliance by pressing the power button. This gracefully shuts down
the appliance, typically in under 30 seconds.
Connecting to the CLI

This section describes how to connect to the FastView CLI using one of the following methods:
• Connecting Using SSH
• Connecting Using Keyboard and Monitor
• Connecting Using a Serial Connection
Note: The default administrator User ID is admin.

Regardless of the connection method, when logging in for the first time, you must accept the EULA,
after which you prompted to run the First Time Setup Wizard.
Connecting Using SSH

The CLI provides access to the network using SSH. To connect using this method, the appliance
must already be configured for and connected to the network (see Licensing FastView, page 51). If
you can plug the appliance into the network using the IP address you defined, you can start using
the CLI through SSH immediately. Otherwise, you must use one of the other connection methods to
configure the network for the first time.
To connect using SSH

1. Connect to the appliance on the management IP address you have defined.
2. At the login prompt, enter the appropriate username and password.
Connecting Using Keyboard and Monitor

Use this procedure to connect to the application using a keyboard and monitor.
To connect to the CLI using a keyboard an monitor

1. Connect the keyboard to the USB port on the appliance back panel.
2. Connect the monitor to the monitor port on the appliance back panel.
Connecting Using a Serial Connection

Use this procedure to connect to the application using a serial connection.

Installation
To connect using a serial connection

1. Connect your serial terminal or PC with terminal emulation (such as HyperTerminal) to the serial
console port on the FastView appliance back panel using the 9-pin NULL-modem serial cable.
2. Set the communications parameters of the serial port on your terminal (or terminal emulation)
to the following:
Table 1: Setting the Communication Parameters of the Serial Port
Parameter Value
Bits per second (Port Speed) 19200
Data Bits 8
Parity None
Stop Bits 1
Flow Control None
Initial Login and Configuration with KVM

There is also an option to have APM SharePath server pre-installed on the FastView appliance
(supported for FastView appliance v2 only). This eliminates the need for a separate VA to host
SharePath. In this case, FastView and APM SharePath server are both pre-installed on a KVM virtual
machine. For such a configuration, FastView must be ordered together with an APM license.
The FastView device requires initial configuration which provides the basic networking information.
To use the APM, you must also configure the APM (SharePath) server.
Note: APM does not support IPv6

Initial access is to the KVM CLI console. From there you can access and configure both the FastView
device and the SharePath device.
After the system boots, the KVM console login prompt is displayed. The default username and
password is admin, admin.
From the KVM console, you can access the FastView or the SharePath console.
Accessing FastView from the KVM Console

Use this procedure to access the application using the KFM console.
To access via the KFM console
1. To access the FastView CLI console, enter fastview

2. The default FastView username and password is admin, admin.

Installation
3. To leave the FastView console and return to the KVM console, enter Ctrl + ].
Note: This does not terminate the FastView session and you can get back into FastView by
entering fastview without the need to reenter a username and password.
4. To exit the FastView console and get to the FastView login prompt, enter exit.
5. To return to the KVM console, enter Ctrl + ].
Accessing SharePath from the KVM Console

Use this procedure to access SharePath via the KVM console.
To access SharePath from the KVM Console

1. To access the SharePath CLI console, enter apm
2. The default SharePath username and password is root, radware.
3. To leave the SharePath console and return to the KVM console, enter Ctrl + ].
Note: This does not terminate the SharePath session and you can get back into SharePath by
entering apm without the need to reenter a username and password.
4. To exit the SharePath console and get to the SharePath login prompt, enter exit.
5. To return to the KVM console, enter Ctrl + ].
Note: Radware strongly recommends that you change the default management password. For
more information, see Security Standards, page 179.
FastView Initial Configuration from the KVM Console

To perform the initial FastView configuration from the KVM console, you must first access the
FastView (see Accessing FastView from the KVM Console, page 41) and then continue with the
standard FastView initial configuration as described in FastView Initial Configuration, page 49.
SharePath Initial Configuration from the KVM Console

Application Performance Monitoring (APM) enables you to view real application-performance
statistics of services configured on FastView appliances. To use APM, you must configure the
SharePath server. This section describes how to configure the SharePath application, running on the
KVM, installed on the FastView appliance.

Installation
To login and configure SharePath
1. From the KVM console prompt, enter apm.

2. Enter the FastView default username and password: root, radware
Note: Use standard Linux commands to configure the SharePath server in the VM console.
3. Enter ifconfig to view the current network settings.
4. By default, the network adapter is configured to use DHCP. To configure static IP address, use a
text editor (enter vi in the command line) to modify the following file:
- /etc/sysconfig/network-scripts/ifcfg-eth0
5. Change the bootproto parameter from “DHCP” to “none”.
6. Configure the time of the SharePath server using standard Linux commands.
7. Enter service network restart to apply the configuration of the new network settings.
8. Wait until all the services are up before trying to configure APM settings on the client.
9. To validate the configuration, enter ifconfig.
FastView VA Installation
FastView physical appliances and FastView virtual appliances (VAs) behave much the same way,
except that you run FastView VA on a larger VMHost. For more information understanding the
network topology, see Your Network Topology, page 37.
Installing FastView VA is very similar to installing a FastView appliance.
The following steps walk you through the FastView VA installation:
• VMware Installation
• Connecting to the CLI
• FastView Initial Configuration
• SharePath Initial Configuration
VMware Installation
The FastView VA is a complete virtual appliance for the VMware Virtual Infrastructure. With the
exception of how it is delivered, FastView VA is identical to the FastView appliance, delivering
identical acceleration results and applying all of the optimization technologies and treatments
supported by the FastView appliance.
Installing the FastView VA includes the following steps:
• Host Requirements, page 43
• Installing the VMware Virtual Machine (VM), page 44
Host Requirements
FastView OVA requires a fully functioning VMware infrastructure running VMware ESX 4.0. 4.1, 5.0
or 5.1 or ESXi 5.0 or 5.1, and virtual machine version 7.
In addition, ensure that the FastView VA host meets the following recommended requirements:

Installation
Table 2: Host Requirements
Component FastView 600 FastView 1800 FastView 3600

CPU cores 4 8 16
Memory 16 GB 32 GB 64 GB
Minimum HDD 120 GB 120 GB 120 GB
Recommended HDD 256 GB 512 GB 1024 GB
Installing the VMware Virtual Machine (VM)

The procedure for deploying the FastView OVA may vary depending on the VMware version. For
more information on deploying OVAs, refer to your VMware documentation.
To configure the FastView OVA for the first time

1. Download the OVA format files from the location provided to you by Radware Technical Support.
2. Log into the vSphere client and deploy the FastView OVA.
3. Accept the license agreement.
4. Click Finish to finish deploying the FastView OVA.
5. Allocate the appropriate memory and CPUs in the machine properties, and set the network
adapter to connect at Power On.
6. From the vSphere Home > Inventory drop-down list, select VMs and Templates.
7. Right-click the required FastView server from the list, and then select Power > Power On.
After the system boots, the login prompt is displayed.
Note: Reserve two IP addresses: one for management, and at least one for future use for a
virtual IP.
Connecting to the CLI

This section describes how to connect to the a FastView VA CLI using one of the following methods:
• Connecting to the CLI
• Connecting Using SSH
Connecting Using the VM Management Console

Use this procedure to connect to the application using the VM Management Console.
To connect using the VM Management Console

1. To run the First Time Setup Wizard using the VM Management Console, connect to the host's
client console. If you are using ESXi, this is the VMware vSphere client.
2. Log in with the appropriate username and password. Default: admin, admin
You are be prompted to accept the EULA and go through the Networking Setup wizard.

Installation
Connecting Using SSH

The CLI provides access to the network using SSH. To connect using this method, the appliance
must already be configured for and connected to the network. You can plug the appliance into the
network using the IP address you defined and start using the CLI through SSH. Otherwise, you must
use one of the other connection methods to configure the network for the first time.
To connect using SSH

1. Connect to the appliance on the management IP address you have defined.
FastView Initial Configuration

This section describes how to initially configure the FastView devices. Initial FastView configuration
is facilitated by the First Time Setup Wizard.
To configure the FastView device

1. Log in to the FastView device.
2. When connecting to the FastView CLI for the first time, you will be prompted by the First Time
Setup Wizard to provide the following basic networking information:
Table 3: First Time Networking Setup Information
Parameter Description
Hostname The name that the appliance is identified as on the network. This
must be unique for redundancy.
Default: fastview
Use DCHP Configure to use DCHP.
Default: no
IPAddress The IP address of the Web Management Interface. Use this IP
address to identify the appliance on the network.
Default: 192.168.10.1
Netmask The netmask of the appliance.
Default: 255.255.255.0
Gateway The gateway for the appliance to connect to the Internet.
Default: 192.168.1.1
DNS The DNS value for the appliance. Without this value, the appliance
cannot receive updates or provide support information.
Default: 0.0.0.0

Installation
Table 3: First Time Networking Setup Information (cont.)
MTU The MTU for the appliance. If you are unsure of the correct value,
leave it at the default value.
Default: 1500
Enable Auto Negotiation Enables auto-negotiation.
• Yes—Sets the Network Speed to auto and the Network Duplex
to auto.
• No—If you select no, you must enter values for the Network
Speed and Network Duplex.
Default: Yes
3. After defining these values, basic networking is complete and you can connect to FastView using
the Web Management Interface on your network (with the FastView IP address that you defined)
to continue with configuration.
4. When you now connect to the FastView CLI, you can run any of the CLI commands. For more
information on the CLI commands, see Command Line Interface, page 185.
Note: If at any time you need to re-run the First Time Setup Wizard, type network wizard at the
FastView CLI prompt.
SharePath Initial Configuration

Application Performance Monitoring (APM) enables you to view real application-performance
statistics of services configured on FastView appliances. To use APM, you must configure the
SharePath server. This section describes how to install and configure the SharePath server.
The server installation is in an Open Virtualization Appliance (OVA) file. The administrator deploys
the file in a VMware vSphere environment. The SharePath server runs on VMware vSphere 4.1,
virtual machine version 7. This procedure requires an existing VMware vSphere environment.
This procedure assumes a basic knowledge of VMware and how to install and use it.
Note: For more information on VMware installation procedures and details of OVA deployment, see
the VMware documentation.
During OVA deployment, attach the network interfaces based on the Linux configuration.
SharePath Server Requirements

To install the external SharePath server, you must have the following:
• A fully functioning VMware infrastructure running VMware ESX 4.0 or 4.1, ESXi 4.0 or 4.1,
virtual machine version 7.
• Recommended I/O speed: 9.2K IOPS (or higher) with latency averaging less than 20 ms.
• The SharePath server OVA file that Radware provided.
OVA Deployment Requirements

To deploy the SharePath OVF, you must have the following:
• 8 GB RAM
• Four vCPUs

Installation
• 400 GB hard drive

• Three defined virtual NICs
• Maximum supported events-per-second per unit: 500
• Maximum distinct URLs per application: 100
Initial Installation and Configuration of the SharePath Server

The procedure for deploying the SharePath OVA may vary depending on the VMware version. For
more information on deploying OVAs, refer to your VMware documentation.
To configure the SharePath OVA for the first time

1. Log into the vSphere client and deploy the SharePath server OVA with the following:
— For the Disk Storage parameter, choose Thick provisioned format.
— In the network mapping configuration, the destination network is typically the network for
SharePath management. This corresponds to the value in the Management IP Address
text box in the APM Settings pane.
2. Click Finish to finish deploying the SharePath server OVA.
3. From the vSphere Home > Inventory drop-down list, select VMs and Templates.
4. Right-click the required SharePath server from the list, and then select Power > Power On.
After the system boots, the login prompt is displayed.
5. At the login prompt, in the VM console, enter the default username and password: root, root
Note: Use standard Linux commands to configure the SharePath server in the VM console.
6. Enter ifconfig to view the current network settings.
7. By default, the network adapter is configured to use DHCP. To configure static IP address, use a
text editor (enter vi in the command line) to modify the following file:
- /etc/sysconfig/network-scripts/ifcfg-eth0
8. Change the bootproto parameter from “DHCP” to “none”.
9. Configure the time of the SharePath server using standard Linux commands.
10. Enter service network restart to apply the configuration of the new network settings.
11. Wait until all the services are up before trying to configure APM settings in the client.
12. To validate the configuration, enter ifconfig.
FastView Cloud Service Installation

For a FastView Cloud Service deployment, installation and maintenance of the FastView appliance is
handled entirely by Radware Technical Support.
This section describes how a FastView appliance works in a cloud service deployment, including:
• Cloud Service Network Topology
• DNS Services
• CDN Services
• Web Monitoring Services
• Removing FastView Services

Installation
Cloud Service Network Topology

When a FastView appliance is deployed in a cloud service environment, FastView is hosted on the
Internet for the end-customer. DNS Services are modified to route domains to the IP address of the
available FastView appliance, which then connects to your local data center.
Figure 5: Service Network Topology
Although there is benefit to not having to host or maintain FastView within your environment, this
deployment limits the FastView appliance to provide services for a single IP address for each
purchased FastView service.
DNS Services
What DNS changes you must make depends on if you are using FastView DNS service or not:
• Deployment Without FastView DNS Service
• Deployment With FastView DNS Service
Deployment Without FastView DNS Service

If you choose not to use the FastView DNS Service, you must create an A Record for your WWW
subdomain to point to the FastView IP address. This redirects traffic destined for the WWW portion
of your site to FastView, which then uses the origin IP address as the source for its content.
Deployment With FastView DNS Service

If you are using the FastView DNS Service, you are provided a domain name that does the following:
• Points to the IP address of the FastView appliance
• Has a failover to your original source origin IP address
With this provided domain, you can create a CNAME record for your WWW to the provided domain.
From this point, the FastView DNS Service directs traffic appropriate for the WWW location of your
domain.
CDN Services
You can use your own content delivery network (CDN) or the FastView CDN service:
• Deployment Without the FastView CDN Service
• Deployment With the FastView CDN Service
Deployment Without the FastView CDN Service

If you choose not to use the FastView CDN Service, and have a CDN service of your own, you can
work with Radware Professional Services to ensure that treated resources are directed to your CDN
rather than the FastView appliance directly. Because most CDNs fetch resources from the source

Installation
WWW back-end, this is usually sufficient. However, if your CDN is set up to pull from a place other
than WWW, you must make appropriate changes to pull treated resources from the FastView
appliance.
Deployment With the FastView CDN Service

If you choose to use the FastView CDN Services, your content is automatically stored at a CDN
location when it is treated. This includes treated images, JavaScript, and css. This is configured
automatically during configuration by the FastView CDN Services.
The domain where CDN content is stored is <domain>.slcontent.com, where <domain> is a
name that represents your Web site. The CDN Service pulls treated content from the FastView
appliance directly as needed, and therefore does not require any special end-user configuration.
Web Monitoring Services

You can use your own Web Monitoring services or the FastView Web Monitoring Service.
• Deployment Without the FastView Web Monitoring Service
• Deployment With the FastView Web Monitoring Service
Deployment Without the FastView Web Monitoring Service

If you choose not to use the FastView Web Monitoring Service, you can still set up your own HTTP
monitoring service to alert you when there is an outage. Radware recommends monitoring both the
FastView appliance and the back-end source to identify the source of an outage. With the
appropriate DNS failover a potential FastView appliance outage may automatically redirect back to
your original source Web servers, causing minimal interruption.
Deployment With the FastView Web Monitoring Service

If you choose to use the FastView Web Monitoring Services, you are automatically notified when
either your Web Server or the FastView appliance are off-line. In addition, notifications are sent to
Radware Technical Support so that they can ensure optimal uptime, and take appropriate action if
necessary.
Removing FastView Services

To permanently remove the FastView appliance from intercepting your WWW traffic, you can always
revert to the appropriate A Record or CNAME. However, if you want to temporarily disable services,
use the Dashboard menu on the Support Portal to turn off the treatment services.
FastView Initial Configuration

Initial FastView configuration is facilitated by the First Time Setup Wizard.
Note: When connecting for the first time, you are prompted to accept the EULA. You must accept
the EULA to continue, otherwise, you are returned to the login prompt.
When connecting to the FastView CLI for the first time, you will be prompted by the First Time Setup
Wizard to provide the following basic networking information:

Installation
Table 4: First Time Networking Setup Information
Hostname The name that the appliance is identified as on the network. This
must be unique for redundancy.
Default: fastview
Use DCHP Configure to use DCHP.
Default: no
IPAddress The IP address of the Web Management Interface. Use this IP
address to identify the appliance on the network.
Default: 192.168.10.1
Netmask The netmask of the appliance.
Default: 255.255.255.0
Gateway The gateway for the appliance to connect to the Internet.
Default: 192.168.1.1
DNS The DNS value for the appliance. Without this value, the appliance
cannot receive updates or provide support information.
Default: 0.0.0.0
MTU The MTU for the appliance. If you are unsure of the correct value,
leave it at the default value.
Default: 1500
Enable Auto Negotiation Enables auto-negotiation.
• Yes (default)—Sets the Network Speed to auto and the Network
Duplex to auto.
• No—If you select no, you must enter values for the Network
Speed and Network Duplex.
After defining these values, basic networking is complete and you can connect to FastView using the
Web Management Interface on your network (with the FastView IP address that you defined) to
continue with configuration.
Once you have run the First Time Setup Wizard, any time you connect to the FastView CLI, the CLI
splash screen displays. At the prompt you can run any of the CLI commands. For more information
on the CLI commands, see Command Line Interface, page 185.
Note: If at any time you need to re-run the First Time Setup Wizard, type network wizard at the
FastView CLI prompt.

Installation
Figure 6: FastView CLI Splash Screen
Licensing FastView
After the appliance is connected to the network, ensure that a valid license is applied to pass Web
traffic. A license file should have been provided to you with your purchase of FastView. Licensing
includes the following steps:
• Log into the Web Management Interface, page 51
• Navigate to License Management, page 52
• Update the License, page 52
Log into the Web Management Interface

Use this procedure to log into the Web Management Interface from a Web Browser.
To log into the Web Management Interface

1. From a Web browser, connect to the IP address you set up for your appliance on port 443.
Compatible browsers include: Internet Explorer 7 and later, FireFox 3 and later, Chrome, Safari
2. Log in with the appropriate username and password.
Notes
• If you have not changed the IP address using the First Time Setup Wizard, you can also do this
from the Web Management Interface from Network Configuration > Appliance (see
Appliance Setup, page 53).
• You can also change the IP address for your management connection, but you can only do this
through the CLI.

Installation
Navigate to License Management

Use this procedure to find License Management.
To navigate to License Management

1. Navigate to Appliance Management > Maintenance > License Management.
Figure 7: License Management
2. Expand this option to see the current license information and to update the license.
Update the License

Use this procedure to update the license.
To update the license

1. Enter the full license key in the FastView License field.
2. Copy and paste the entire support certificate contents as provided by Radware into the box.
You must copy the entire certificate contents, including the text "-----BEGIN FASTVIEW
SUPPORT CERTIFICATE-----" and "-----END FASTVIEW SUPPORT CERTIFICATE-----
" .
Note: The support certificate is neither required nor available for Alteon NG users.
3. Select Update.
Once the license is applied, any virtual servers which have been created are able to pass traffic.

Network Configuration Fine Tuning
Chapter 3 – Network Configuration Fine Tuning

This chapter describes additional fine tuning of the FastView appliance so that it runs properly on
your network. It assumes the following:
• You understand how FastView fits into your Network Topology (see Your Network Topology,
page 37).
• You have assigned the FastView appliance a Management IP address, and have reserved any
virtual IP addresses you may want to use for your Web Applications (see Initial Login and
Configuration with KVM, page 41).
Before you start creating and configuring Web applications, you should ensure that the FastView
appliance communicates on your network properly. After initial installation, you should now gather
any additional network concerns that you may have for your network flow, such as routing, or
protocol restrictions.
The following additional steps can help you fine tune your appliance's network settings:
• Appliance Setup
• Appliance Name
• CLI Networking Options
• Routing
• Redundancy
Appliance Setup
You can modify appliance networking settings using the Appliance pane.
To navigate to the Appliance pane

> Navigate to Network Configuration > Appliance.
Figure 8: Appliance Setup
The Appliance pane includes the following sections:

• Network Interface
• DNS Servers
• NTP Servers
Network Interface
The Network Interface section contains all the information you need to set the networking
information for the Web Management Interface. You first configured this using the First Time Setup
Wizard.

Figure 9: Network Interface
To modify network interface settings

1. Change any of the parameters as described in Table 5: Network Interface Parameters, page 54.
2. Click Save.
Note: Changing any of the Network Interface values can potentially cause the appliance to be
inaccessible from the location you are currently connected to it. If you make such a change, you
need to re-login back to the Web Management Interface on the newly defined location.
Table 5: Network Interface Parameters
IP Address The IP address of the Web Management Interface. Use this IP address to identify
the appliance on the network.
Note: The FastView appliance can be configured with IPv6 addresses or with
IPv4 addresses, but not with a mix of the two.
This is not the IP address that your Web applications are proxied through. This
must be a unique IP address on your network.
Network Mask A valid netmask to set your appliance’s subnet.
Default: 255.255.255.0 (Single Class C)
Gateway The IP address of your gateway.
Speed While this is typically set to Auto, in certain situations your Network Interface
may not negotiate properly with your router, and you may have to define the
network speed it supports.
Values: Auto, 1000, 100, 10
Default: Auto
Duplex While this is typically set to Auto, in certain situations your Network Interface
may not negotiate properly with your router, and you may have to define the
network duplex it supports.
Values: Auto, Full, Half
Default: Auto
MTU Most networks use an MTU value of 1500. If you use a different sized MTU, such
as for a jumbo frame network, you can configure this value.
Be careful not to configure this value to be different from your network or the
appliance may become inaccessible over the network interface.
Default: 1500

DNS Servers
The DNS Servers section contains all the information you need to set the DNS Server information for
the Web Management Interface. DNS servers are required for the following:
• Getting the latest service releases from the FastView Updates Servers
• Sending statistical data to the FastView Monitoring Services
• Using non-local Treated Domains in your Web Applications
To modify DNS server information

1. In the DNS Servers section, enter up to three DNS servers in the DNS address fields.
Note: The DNS Search String is not a required field for DNS searches unless you are using a
non-local treated domain without the full DNS string.
Figure 10: DNS Servers
2. To remove a DNS server, clear the appropriate field.

3. Click Save.
NTP Servers
The NTP Servers section contains all the information you need to set the NTP Server information. An
NTP server helps keep your FastView clock in sync with the rest of your network.
To modify NPT server information

1. In the NTP Servers section, enter up to three NTP servers in the NTP address fields by order of
priority.
You can enter NTP Server values as either IP addresses or fully qualified domain names.

Figure 11: NTP Servers
2. To remove an NTP server, clear the appropriate field.

3. Click Save.
Appliance Name
The appliance name displays on overview pages and in command prompts, providing a quick way to
identify your appliance, and a necessary tool performing any kind of redundancy functions.
To modify your appliance name

1. Navigate to Appliance Management > System Settings > Global Settings.
Figure 12: Appliance Name
2. Edit the value as required.

3. Click Save.
CLI Networking Options

Most network settings are available through the Web Management Interface. There are a number of
network settings that are also available through the CLI. For a description of these CLI commands,
see CLI Networking Options, page 185.

Routing
Under certain circumstances you need to define routes on FastView so that network traffic can flow
to servers on other subnets. Although this feature is not supported through the Web Management
Interface, you can add routes through the CLI. or a description of these CLI commands, see CLI
Networking Options, page 185.
Redundancy
To assist with network maintenance hardware needs and to enhance network reliability, networks
have been integrating various redundancy schemes. The synchronized cluster features as an active-
active redundancy option for your FastView appliance.
Note: Redundancy configuration in FastView is not supported for Alteon NG customers. However,
FastView devices in Classic configuration, as with Alteon NG, can be load balanced by Alteon to
provide redundancy. No special persistency is required.
Synchronized Cluster
This section includes:
Creating a Cluster, page 57
Joining a Cluster, page 59
Removing a Device from a Cluster, page 60
Virtual Servers and Load Balancing, page 60
Creating a Cluster
Synchronized clusters let you work with multiple FastView appliances within an Active-Active
configuration. To use a synchronized cluster, you must have the following:
• Two or more FastView appliances on the same network
• A load balancer in front of the FastView appliance
• NTP configured and time-synchronized on all appliances
A synchronized cluster maintains configuration synchronization between multiple FastView

appliances. It also lets you manage the cluster of appliances from a single appliance. In this mode,
you can specify which virtual servers an individual FastView appliance controls.

To create a synchronized cluster

1. From the FastView appliance that manages the cluster, navigate to Network Configuration >
Redundancy.
Figure 13: Redundancy
2. Click Create.
Figure 14: Create a Synchronized Cluster
3. Set the following parameters:

— Cluster Name—The name of the cluster.
— Passphrase—The password that is required to join the cluster.
4. Click Save.
Once the cluster is created, other FastView appliances join as members to the cluster.

Figure 15: Cluster Members List
Joining a Cluster
Use this procedure to join a cluster.
To join a cluster
1. After a cluster has been created, from the appliance you want to join to the cluster navigate to
Network Configuration > Redundancy.
2. Click Join.
Figure 16: Joining a Cluster
3. Enter the following parameters:

— Cluster Name—The name specified when you created the cluster.
— Passphrase—The password specified when you created the cluster.
— IP of an existing cluster member
— —The IP address of at least one active FastView appliance in the cluster.
4. Click Join Cluster.
The appliance is now a member of the cluster and appears on the cluster list.

Removing a Device from a Cluster

Use this procedure to remove a device from a cluster.
To remove a FastView appliance from a synchronized cluster

1. Log into any appliance in the cluster.
2. Navigate to Network Configuration > Redundancy.
3. Select the appliance you want to remove, and click Unjoin Selected Devices.
The removed appliance retains its configuration and any virtual servers that are associated with it
(but not virtual servers associated with other appliances). The appliance continues to treat traffic
and function as previously until reconfigured. However, it no longer synchronizes configuration
changes with other FastView appliances.
Note: Synchronized clusters fully support upgrading. However, FastView can only communicate
with other appliances with the same version. Because of this, when upgrading synchronized
appliances, you must upgrade all the appliances in a cluster before making configuration changes.
No configuration changes can be made if appliances are not using the same version. The system will
be in read-only mode until all appliances are using the same version
Virtual Servers and Load Balancing

A virtual server can only be active on one FastView appliance at a time because two appliances
cannot share the same IP address. Synchronized clusters let you to specify which FastView
appliances activate which virtual servers using a load balancer to point to those virtual servers.
For each virtual server you create (for example, one virtual server per back-end Web server), create
an additional virtual server for each FastView appliance. Each FastView virtual server should
• Have a unique IP address on the network.
• Use the same ports.
• Point to the same back-end Web server.
To create and edit the virtual server refer to Setting up Your Virtual Servers, page 67.
Note: In a synchronized cluster configuration, the Device column indicates which FastView
appliance is hosting the currently running virtual server.
Set a unique FastView appliance to each of the virtual servers that you created that point to the
same back-end Web server.
For all of your Web applications, select all of the virtual servers that point to the appropriate back-
end Web servers.
Note: In a synchronized cluster, the configuration is shared across all FastView appliances.
After each of your Web applications are associated with the appropriate virtual servers, you can use
your front-end load balancer to appropriately balance traffic to the multiple virtual servers, and
provide failover if one of the virtual servers becomes non-operational.

Figure 17: Virtual Server and Load balancing Configuration


Web Management Interface
Chapter 4 – Web Management Interface

In general, most FastView features and functions are performed through the Web Management
Interface. This chapter includes the following sections:
• Overview, page 63
• Web Management Interface Overview Page, page 63
Overview
FastView appliance and FastView VA users can connect to FastView to make configuration changes,
create new Web applications, and perform general maintenance for the FastView appliance. FastView
Cloud Service users do not have a Web Management Interface to connect to, and should instead use
the Service Dashboard that is accessible through the Support Portal.
Some of the lower level FastView functions can only be performed from the Command Line Interface
(CLI). For more information on using the CLI, see CLI Networking Options, page 185 and CLI
Security Options, page 189.
For a description of how to log into the Web Management Interface, see Log into the Web
Management Interface, page 51.
Web Management Interface Overview Page

After you have logged into the Web Management Interface, the Web Management Interface
Overview Page displays. It is a series of tabs that describe the overall FastView health.
• Offload Gauge
• Summary Sections
• Appliance Information
• Traffic Flow
• Other Information
• More on Appliance Health
Offload Gauge
The offload gauge displays the workload amount FastView has taken off your Web Server:

Figure 18: Offload Gauge
Table 6: Offload Gauge Parameters
Offload Dial The current amount of workload offloaded from your Web Server.
Average The average number of requests served directly from FastView.
Offloaded
Maximum The maximum number of requests that have been served directly from FastView
Offloaded at any one time, rather than going to the Web Server directly.
Total The number of requests that have been made to FastView. These are requests for
Transactions all resources, not just Web pages.
Summary Sections
The summary sections display a running total of bytes saved, transactions, and tokens that are
rewritten:
Figure 19: Summary Sections
Table 7: Summary Sections
Bytes Saved Displays the number of bytes that FastView has saved from sending to your client
browsers. This is identified by the page that would have been served from the
Web Server compared to the page that FastView actually provides to the client.

Table 7: Summary Sections (cont.)
Transactions Displays the current, average, and maximum transactions per second (TPS)
being served from FastView.
Tokens Displays the number of changes that have been made to your served Web page
Rewritten content every second. Each page served may contain multiple tokens for
replacement.
Appliance Information
The Appliance pane displays the status of your running appliance.
Figure 20: Appliance Information
Table 8: Appliance Information
System Status A link and warning icon are displayed if there are any system messages. For more
information, see System Status Messages, page 138.
Device Name The FastView appliance name. This can be modified at Appliance Management
> System Settings.
Version The FastView version. This is also displayed at the top left of the Web
Management Interface pane.
Date The current date set for FastView. To configure an NTP server, see NTP Servers,
page 55.
Time The current time set for FastView. To configure an NTP server, see NTP Servers,
page 55.
Uptime Amount of uptime since FastView was last rebooted.
CPU Utilization The amount of CPU FastView is currently using.
Disk Utilization The amount of disk space FastView is currently using. This warns you if space is
getting low due to large logs, too many backups, large disk-backed usage, and so
on.
Traffic Flow
The Traffic pane displays an overview of the user traffic flowing through FastView:

Figure 21: Traffic Flow
Table 9: Traffic Flow Information
Transactions The current and total number of transactions being processed by FastView.
Pages The current and total number of Web pages being processed by FastView.
Optimized Pages The current and total number of times FastView has compiled a page for
optimization. After pages have reached the optimization threshold, they should
not be compiled further until touch-up or recompile intervals.
Tokens The number of tokens that FastView has replaced in Web pages. Tokens can
Rewritten include such things as URL rewriting, name replacement, viewstate removal, and
so on.
Bandwidth The current bits per seconds (BPS) into and out of FastView. This displays the
current bandwidth consumption of your Web traffic.
Other Information
The Overview Page also contains:
• A banner message at the top of the page if any critical errors have occurred.
• A Reset Stats button to reset the Overview Dashboard statistics.
• An indication of the last time FastView was reset.
More on Appliance Health

The Overview Page provides a general indication of FastView’s status at a glance. Being able to see
traffic offloaded and watch your TPS can give you a quick indication if your appliance is running in
good health. If you require more information on the health of your system, see Examining Appliance
Health, page 137.

Setting up Your Virtual Servers
Chapter 5 – Setting up Your Virtual Servers

The primary FastView features provide accelerated Web pages by applying various acceleration
techniques to those pages and their resources. To apply the various Web acceleration techniques
available in FastView, you must configure the system’s virtual servers.
Virtual Servers
FastView sits on a local network as one of a number of network devices. To process traffic destined
for the Web server, FastView must be logically situated between the client browser and the Web
server. This is done by defining a virtual server within FastView.
For each target destination IP address (whether it is a load balancing pool on a Load Balancer, or an
individual Web server; see Your Network Topology, page 37), you create a virtual server on
FastView. The virtual server acts as a proxy for the original Web Server and treats the traffic as it
passes it along from the Web server.
Figure 22: Virtual Server Topology
Virtual servers are defined to allow Web traffic to flow through the appliance. Each virtual server
created needs to be configured with the following information:
• A front-end IP address and port assigned to the virtual server
• A back-end target for the virtual server
• Whether SSL is used on this virtual server and how it is used
After a virtual server is defined, it is added to one or more Web applications so that the Web
applications can determine if its traffic is examined and how treatments are applied to it.
• Working with Virtual Servers, page 68
• SSL Certificates, page 72
• Testing Virtual Server Traffic, page 76

Working with Virtual Servers

Defining a virtual servers consists of defining a front-end IP address for receiving traffic and a back-
end IP address to which to forward traffic. Virtual servers are accessed from the Servers > Virtual
Servers pane:
Figure 23: Virtual Servers Pane

• The Virtual Server List, page 68
• Origin Server by Fully Qualified Domain Name (FQDN), page 69
• Creating and Editing Virtual Servers, page 70
• Synchronized Configuration, page 72
• SSL Certificate List, page 73
The Virtual Server List

The Virtual Server List on the Virtual Servers pane includes the following parameters:
Table 10: Virtual Server Summary List
Name The name of the virtual server. You should provide a name that describes the
purpose or functionality of the Web Server the virtual server is associated with.
For example, “Corporate Site”.
Listen IP:Port The listening IP address and port for the virtual server.
Server IP:Port The server IP address and port to which the virtual server traffic is sent. When
FQDN is used (see Origin Server by Fully Qualified Domain Name (FQDN),
page 69), this field displays the FQDN and all the IP addresses learned through
DNS and used for back-end servers for this virtual server.
Device The appliance that is running the virtual server. If your appliance is not in a
synchronized cluster, you do not see this column.
SSL Indicates if the virtual server uses SSL.
Connections The number of connections the virtual server currently has open. The value can
be n/a if the virtual server is actually being hosted on a different appliance as
part of a synchronized cluster.

Origin Server by Fully Qualified Domain Name (FQDN)

FastView can be deployed as a service in the cloud, where the origin server is identified by a domain
name rather than by an IP address. This enables flexibility to support multiple servers
simultaneously or a server IP that is frequently changing. FastView can be configured with the FQDN
to identify origin servers. FastView constantly monitors the DNS resolution for this FQDN, spreads
traffic across the returned IP addresses, and fails over quickly as soon as IP addresses change.
FastView can use the configured DNS server, or the authoritative DNS server to check the origin
server IP addresses.
FastView respects the TTL for the DNS server that is used, which determines the frequency of the
DNS query and the IP updates for the back-end system.
The FQDN update interval is controlled by the DNS TTL. To override the DNS TTL, you can set the
FQDNMaxDNSTTLSecs XML parameter to the maximum number of seconds before FastView looks
up the DNS resolution of the origin servers FQDN. This configuration is available per virtual server,
and the default is 86400 seconds.
Note: All origin IP changes are logged in the FastView log. You can view the currently used IP
addresses, as learned by DNS, in the Virtual Servers pane (see Creating a New Virtual Server
(Advanced Display Settings), page 70).
The following diagram illustrates an example of this feature. Clients access www.site.com. The
service is accelerated with FastView, where the origin servers’ IP addresses are managed by the
DNS using the FQDN origin.host.com. FastView learns the IP addresses of the origin using DNS.
FastView uses IP1 and IP2 to handle client requests. If there is a problem with the server at IP2, the
DNS responses for origin.host.com include IP1 and IP3. FastView acts as a DNS client and learns the
change, future requests are sent to IP1 and IP3.
Figure 24: Example Origin Server by Fully Qualified Domain Name (FQDN)
For details on configuring virtual servers, see Creating and Editing Virtual Servers, page 70.

Creating and Editing Virtual Servers

Use this procedure to create or editing virtual servers.
To create or edit a virtual server

1. Do one of the following:
— To create a new virtual server, click New at the top of the Virtual Servers pane.
— To edit an existing virtual server, select a virtual server from Virtual Server list. The fields
that are displayed depends on whether you have Display Settings set to Normal or
Advanced.
Figure 25: Creating a New Virtual Server (Normal Display Settings)
Figure 26: Creating a New Virtual Server (Advanced Display Settings)

2. Set the virtual server values parameters:
Table 11: Virtual Server Options
Name The name of the virtual server. You should provide a name that describes the
purpose or functionality of the Web Server the virtual server is associated with.
For example, “Corporate Site”.
Listen IP:Port The listening IP address and port for the virtual server. When editing this value,
ensure that you are not using the same IP address and port combination that are
used elsewhere on your network.
Server Specifies the origin server IP address that is the handling traffic for this server.
(Server IP:Port, You can use static IP address, or a Fully Qualified Domain Name (FQDN), if the
FQDN:Port) back-end system IP is controlled by DNS.
Values:
• Server IP:Port—The server IP address and port to which the virtual server
traffic is sent. You can set this to a VIP listening port on your load balancer to
balance traffic to multiple back-end Web servers.
• Use FQDN:Port (available only with Advanced Display Settings)—The
Domain Name to which the virtual server traffic is sent. Specify the name
that identifies the origin server and, optionally, the port through which the
service is accessed. For example, if clients access www.mysite.com and
the origin servers are available at origin.host.com:8080, set the hostname
to origin.host.com and the port to 8080.
When using FQDN, you can select Authoritative DNS to check the
Authoritative DNS (as in the response to the host -a command) to look up
the FQDN and find the origin server IP addresses.
Device Name The appliance that is running the virtual server. If your appliance is not in a
synchronized cluster, you do not see this column. For more information on
synchronized servers, see Synchronized Cluster Management, page 187.
SSL Termination Specifies how the virtual server accepts HTTPS traffic. Virtual servers can accept
HTTPS traffic, or identify that the traffic was HTTPS traffic terminated up-front.
Values:
• None—Indicates that the virtual server accepts HTTP traffic that was always
HTTP traffic from the end-client right through to the back-end Web server.
You can associate both an HTTP virtual server and an HTTPS virtual server to
the same Web application. This allows for a single Web site to have both an
SSL and non-SSL portion to it.
• At this Virtual Server—Used when FastView itself is receiving the HTTPS
traffic. This can occur when either FastView receives the traffic directly from
the client, or the firewall or load balancer in front of FastView passes the
traffic through as HTTPS traffic (either by re-encrypting or passing the traffic
straight through unmodified). In this mode, FastView needs an SSL
certificate to accept the traffic. Ensure that you have created the valid SSL
certificates that are required. For more information, see SSL Certificates,
page 72.

Table 11: Virtual Server Options (cont.)
SSL Termination In this mode, FastView also has the option to re-encrypt the traffic and pass it on
(continued) to the Web servers as SSL traffic, or send non-encrypted traffic on to the Web
servers. To re-encrypt the traffic, select the Use Server-Side SSL option.
• Upstream—Virtual servers can also have SSL traffic terminated in front of
FastView. When you select this option, select one of the following sub-
options:
• Always HTTPS—Specifies that all traffic was originally HTTPS traffic
terminated in front of the appliance. All treated domains rewrite all non-
relative URLs to use the HTTPS protocol.
• HTTP and HTTPS—Specifies that traffic is both HTTP and HTTPS, but has been
terminated in front of FastView and passed to FastView as HTTP traffic. When
you select this option, you must define the front-end SSL settings so that the
associated Web application can determine which traffic is HTTP or HTTPS.
Treated domains rewrite all non-relative URLs to use the HTTP or HTTPS
protocol dynamically based on this condition.
Use Server Side Indicates that your back-end Web server is also expecting SSL requests, and
SSL FastView is not acting as either the terminator or that there is termination up
front. This option enables to connection to a Web Server serving HTTPS content.
3. Click Save.
Synchronized Configuration
If your appliance is configured to use synchronized clusters, when editing a virtual server, select
from a drop-down list in the editing pane which FastView to serve a virtual server. Each virtual
server can only be hosted by a single FastView in the cluster. Because you can have multiple virtual
servers pointing to the same back-end IP address and port combination, there is a lot of flexibility on
the Web servers to which you choose to run traffic. However, if you want multiple appliances to
listen for these requests, you must create a separate virtual server for each one with its own unique
IP address and port combination. This requires a load balancer in front of FastView to direct traffic
accordingly. For more information on this, see Your Network Topology, page 37.
Note: Synchronized Configuration is not supported for Alteon NG users.
SSL Certificates
FastView can act as an SSL termination point for Web traffic. This allows for the treatment of Web
traffic between FastView and the Web servers. To use of this feature, SSL Certificates need to be
inserted into FastView and then associated with a virtual server.
SSL Certificates are not required if termination of SSL traffic is performed upstream and traffic is
being passed to FastView as HTTP traffic. This is not possible when FastView is the front-end
appliance in the flow (such as with the FastView Cloud Service) or if any front-end firewall or load
balancer passes through traffic rather than performing SSL termination.
• SSL Certificate List
• Adding SSL Certificates
• Modifying an SSL Certificate
• SSL Certificates for Management
• Exporting IIS Certificates

SSL Certificate List

Use this procedure to view the SSL Certification list.
To view the SSL certificate list

1. Navigate to Network Configuration > SSL Certificates.
The SSL certificate list displays.
Figure 27: SSL Certificate List
2. Select a the certificate name to display additional details about the certificate.
Adding SSL Certificates

Use this procedure to add SSL Certificates.
To add a new SSL certificate

1. After receiving the SSL certificate, from the SSL Certificates pane, click New.
2. Enter the following information:
Table 12: Virtual Server Options
Name A name to identify the certificate.
Certificate The certificate provided.
Private Key The private key of the certificate.

Figure 28: A New, Defined SSL Certificate
3. Click Save Certificate.

The new SSL Certificate is now defined. Your configuration is updated and the new SSL
certificate is available for use by virtual servers.
Note: The certificate and private key can be read from a PEM file format of the certificate. If you
have a PFX file and need to convert it, or if your certificate is already installed on an IIS server and
you want to migrate it, see Exporting IIS Certificates, page 75.
Intermediate Certificates
Intermediate certificate bundles should be provided by your certificate provider.
To add an intermediate certificate

1. Obtain an intermediate certificate bundle that is compatible with Apache 2.
2. Paste the contents of the certificate bundle below your exported certificate. The order is
important.
3. Keep all <BEGIN CERTIFICATE> and <END CERTIFICATE> tags in the certificate bundle
provided.

Modifying an SSL Certificate

You cannot edit a certificate after it has been added, other than to change its name.
To change the name of an existing SSL certificate

1. Select the certificate name in the Certificate List.
2. Modify the name as necessary.
To modify the contents of an SSL certificate

1. Add a new certificate and define it as necessary.
2. Rebind the new certificate to the virtual servers that use the certificate.
3. Delete the old certificate that is no longer defined as needed.
SSL Certificates for Management

You can also use SSL certificates to bind to the FastView management port.
To bind an SSL certificate to FastView management:

1. Add a new certificate and define it as necessary.
2. Navigate to Appliance Management > Maintenance > Administration.
3. Bind the new certificate to FastView Web UI.
Exporting IIS Certificates

When you want to are create a certificate on FastView, it is often already available on an IIS server
in the back-end. You can export the certificates from the IIS Server and then import them into your
FastView. This creates a PKCS#12 format certificate.
• Exporting from IIS 7, page 75
• Exporting from IIS 6, page 76
• Convert the Certificate File from PFX to PEM, page 76
• Import the Certificate into FastView, page 76
Exporting from IIS 7

Use this procedure to export certificates from IIS 7.
To export certificates from IIS 7

1. In the IIS Manager, navigate to the level to which the certificate applies.
2. In the Features view, double-click Server Certificates.
3. In the Actions pane, select a certificate and click Export.
4. In the Export Certificate dialog box, set the following parameters:

— Output filename and password.

— Select Yes, export the private key.
— Only enable Include all certificates in the certification path if possible and not any of
the other checkboxes.
5. Click OK. The file you specified is created in PKCS#12 format.
Exporting from IIS 6

Use this procedure to export certificates from IIS 6.
To export certificates from IIS 6

1. In the IIS Manager, expand the local computer, then expand the Web Sites folder.
2. Right-click the Web site and select Properties.
3. In the Directory Security tab, under Secure Communications click Server Certificate.
4. In the Web Server Certificate Wizard, click Next.
5. Select Export the current certificate to a .pfx file.
6. Follow the wizard to export the certificate (including the output filename and a password), and
click Finish. The file you specified is created in PKCS#12 format.
Convert the Certificate File from PFX to PEM

The certificate that you exported from IIS is in PKCS#12 format (.pfx file), and must be converted to
a .pem file.
To convert from PFX to PEM format

> Use an open source utility such as OpenSSL to convert the .pfx file to a .pem file.
The following is an example using the openssl command:
openssl pkcs12 -in [certificate.pfx] -out [certificate.pem] -nodes
The output file contains both an RSA Private Key section and a Certificate section, both of which are
used to create the certificate in FastView.
Import the Certificate into FastView

After you have converted the certificate to PEM format, it is ready to be imported into FastView. For
details on how importing SSL certificates, see Adding SSL Certificates, page 73.
Testing Virtual Server Traffic

After you have created a virtual server, you can test that Web traffic flows through it. If you have not
yet bound the virtual server to a Web application, this test has no effect on your traffic, and the
traffic is passed directly through to your Web servers without being treated. This is a good way to
ensure that the traffic is flowing smoothly before further configuration.
If you need to check traffic that is flowing through the virtual servers after they are bound to Web
Applications, you can do so by examining the appliance treatment. For more information, see
Examining Appliance Treatment, page 147.

Note: After a virtual server is bound to a Web application, you do not no need to unbind it if you
want to take the Web application out of the traffic flow. To do this, you disable the Web application
from the Web Application list. Traffic still flows through the virtual server, but the Web application
bound to it no longer affects that traffic. For more information, see Editing a Web Application,
page 80.


Working with Web Applications
Chapter 6 – Working with Web Applications

The primary FastView features provide accelerated Web pages by applying various acceleration
techniques to those pages and their resources. Web Applications and Treatment Sets are the two
key components for performing this acceleration. This chapter outlines details about Web
Applications. For more information on Treatment Sets, see Working with Treatment Sets, page 97.
Web Applications
FastView Web applications define how traffic is treated for your Web server. There are many
configuration options either bound to or directly edited in a Web application. Because of this,
configuring a Web application to treat traffic appropriately can sometimes be difficult.
This section describes how to configure a Web application to
• bind together a Web application definition, virtual server, and treatment set
• define how SSL traffic is treated
• define which pages of the Web application should be treated
• define which resources of the Web application should be treated
• define any manual resource preloading for your Web application
• define segmentation and analytics
• define any advanced Web application configuration
• define exclusions

• Defining Web Applications, page 79
• New Web Application Wizard, page 81
Defining Web Applications

Figure 29: Web Application Pane
Web Application List

The Web Application list displays an overview of your configured Web applications and provides links
to the different areas of configuration. It includes the following parameters:

Table 13: Web Application List
Name The name of the Web Application. You should provide a name that describes the
purpose or functionality of the back-end Web Server or Web pool the Web
application is associated with. For example, “Corporate Site”.
Path The Web path for the Web application. This indicates the sub-path of the site for
which that the Web application is defined, and is the equivalent of the IIS Site
Path.
Virtual Servers The list of virtual servers that are bound to this Web application. The virtual
server names are links to the virtual server editing panes.
Enable Enables the treatments for the specific Web application.
Treatment Set Defines which treatment set is being used to treat traffic for this Web application,
for both Desktop and Mobile. The treatment set names are links to the treatment
set editing panes. For more details on Treatment Sets, see Working with
Treatment Sets, page 97.
Creating Web Applications

When you create a new Web application, you are walked through the Web Application Wizard. This
creates a Web application with a basic configuration with appropriate treated domains. After creating
the Web application, you can edit it to make further adjustments.
To create a Web application

1. To create a Web application, click New at the top of the Web Application pane.
2. Follow the instructions of the Create Web Application Wizard. For a detailed description of the
wizard, see New Web Application Wizard, page 81.
Editing a Web Application

Use the following procedure to edit a Web application.
To edit a Web application

1. In the Web Application pane, select a Web application.
2. Edit the parameters as necessary.
3. Click Save.
Copying a Web Application

Use the following procedure to copy a Web application.
To copy a Web application

1. Select the checkbox next to the name of the Web application you want to copy.
2. Click Copy Selected to create a Web application based on the copy.
3. Edit the Web application.

Removing a Web Application

Use the following procedure to remove a Web application.
To remove a Web application

1. Select the checkbox next to the name of the Web application you want to delete.
2. Click Delete.
3. At the prompt, confirm the deletion.
New Web Application Wizard

When you create a new Web application, a two-step wizard walks you through the basic Web
application configuration, including:
• Define Web Server Information and Treatment Type, page 81
• Define Treated Domain Information, page 82
• Testing Web Applications
Define Web Server Information and Treatment Type

Use this procedure to define Web Server information and treatment type.
To define Web server information and treatment type

> In the Create Web Application - Step 1 pane, set the parameters to define your Web application.
This is the same information that displays at the top of the Web Application Details pane.
Table 14: Defining Web Server and Treatment Type
Name A name that defines the Web application. This displays in the Web Application List
and elsewhere in FastView to identify the Web application currently in use.
Path When a user browses to an application, the following three items must match in
order for the Web application to treat the traffic: virtual server, host header, and
path.
If all three of these do not match, no further checking of individual treatments is
performed.
Virtual Servers The list of virtual servers to bind to the Web application. When a user browses to
an application, the following three items must match in order for the Web
application to treat the traffic: virtual server, host header, and path.
If all three of these do not match, no further checking of individual treatments is
performed.
Enable APM Select to enable application performance monitoring.
Learning Mode Enables learning mode for the Web application. In learning mode, FastView
captures and analyzes pages for acceleration without actually providing the
accelerated pages to the client.

Table 14: Defining Web Server and Treatment Type (cont.)
Treatment Set Select a treatment set to bind to this Web application. The treatment set
configuration selected is used when the Web application is selected for treating.
For more details on Treatment Sets, see Working with Treatment Sets, page 97.
Host Headers When the user browses to the Web site, they enter either a domain or IP address.
The Host Header list lets you filter your Web application based on these host
headers. Leave this list blank to allow all Host Headers.
Define Treated Domain Information

Use this procedure to define treated domain information.
To define treated domain information

1. In the Create Web Application - Step 2 pane, set the parameters for your site to automatically
create treated domains. In some cases, you may need to edit the Web Application Details to
modify these values, but the defaults are generally sufficient for most cases.
Table 15: Define Treated Domain Information
Local Resource Enter a list of all domains on your local Web servers that should be treated by
Domains this Web application.
For example, if the Web server behind FastView can have resources that are
called by www.mysite.com and www.mysite.ca, enter these two URLs now.
Although FastView always treats relative resources, it is a good idea to enter
these even if your site uses relative URLs.
Resource Enter a list of all domains for which your Web servers treat traffic that are not
Domains on physically located on the Web Servers behind FastView. By default, the treated
External domains are set up to rewrite these resources to be served by FastView in a
treated accelerated form.
For example, if you store your images on a server called images.mysite.com,
enter this here.
CDN Domain FastView can treat CDN resources and have the CDN pull resources from
FastView. If you use a CDN to host your resources and want the treated
resources to continue being served from that CDN, enter the CDN name.
FastView treats the resources that are to be served by the CDN and rewrites the
new name of the resource to the client browsers. The CDN then fetches the new
resources from FastView's served Web site.
Dynamic If you are using the DCM treatment, enter the prefixes here. Note that this
Connection automatically configures prefixes for all local and external resource domains you
Maximizer have defined. DCM prefixes are not applied to the CDN Domain as part of the
Prefixes wizard.
Note: In many cases, the only information required for Step 2 is the Local
Resource Domains. Although you can create your Web application without a
Local Resource Domain, Radware strongly recommends that you do so.
By defining DCM prefixes, you can enable or disable DCM by turning the DCM
treatment ON or OFF in the associated treatment set.
2. Click Create Web Application to create the Web application.

Testing Web Applications

After you have created a new Web application, you should test it to determine it is working the way
you expected. For more information, see Examining Appliance Treatment, page 147.
Treated Domains
Treated domains define the rewriting policies to each HTML document treated by FastView. Defining
which resources of the Web Application should be treated is the primary purpose of treated domains.
All Web Applications must have their treated domains configured correctly to optimize an application
and its resources properly. A treated domain defines what resources within a page will be treated,
not which pages will be treated.
In the Treated Domains tab, all defined treated domains are listed detailing their names and
resource domains.
You can add or delete treated domains in the Treated Domain list. If you want to temporarily
disable a treated domain from being active, clear the Enabled checkbox.
Defining treated domains includes the following steps:
• Define which resources should be treated.
• Define from where resources should be fetched.
• Define to what URL the resources should be written.
Figure 30: Treated Domains
To define treated domain information
1. Select a treated domain, and click the Edit the selected treated domain icon .
Or, click the Add a new treated domain icon .

2. Edit the selected treated domain or defined the new treated domain with the required
parameters as defined below.
3. Select the checkbox to enable the required treated domain.
4. Select if you want to enable advance resource relocation.

5. Click Submit.
Table 16: Treated Domain Parameters
Local Resource Enter a list of all domains on your local Web servers that should be treated by
Domains this Web application.
For example, if the Web server behind FastView can have resources that are
called by www.mysite.com and www.mysite.ca, enter these two URLs now.
Although FastView always treats relative resources, it is a good idea to enter
these even if your site uses relative URLs.
Resource Enter a list of all domains for which your Web servers treat traffic that are not
Domains on physically located on the Web Servers behind FastView. By default, the treated
External domains are set up to rewrite these resources to be served by FastView in a
treated accelerated form.
For example, if you store your images on a server called images.mysite.com,
enter this here.
CDN Domain FastView can treat CDN resources and have the CDN pull resources from
FastView. If you use a CDN to host your resources and want the treated
resources to continue being served from that CDN, enter the CDN name.
FastView treats the resources that are to be served by the CDN and rewrites the
new name of the resource to the client browsers. The CDN then fetches the new
resources from FastView's served Web site.
Dynamic If you are using the DCM treatment, enter the prefixes here. Note that this
Connection automatically configures prefixes for all local and external resource domains you
Maximizer have defined. DCM prefixes are not applied to the CDN Domain as part of the
Prefixes wizard.
In many cases, the only information required for Step 2 is the Local Resource
Domains. Although you can create your Web application without a Local Resource
Domain, Radware strongly recommends that you do so.
By defining DCM prefixes, you can enable or disable DCM by turning the DCM
treatment ON or OFF in the associated treatment set.
Define Domains of Resources to Treat

The source domains identify the URL of the resources in the HTML source that need to be picked up
for treatment by this treated domain. Resources that are identified by this pattern then have the
How To Fetch and URL Rewrite configuration associated with the treated domain applied to it.
For the local treated domain there are two source domains that can not be removed:
• Relative Links: Resources on the page that are relative to the location of the page. (for example,
../file.png)
• Absolute Links with the Same Domain Page: Any Resource that has an absolute link with the
same protocol://URL as the page connected to (for example, both page and resource are
referenced as http://www.theurl.com/*)
Additional domains can be added or deleted as required. For example, if your site contains resources
that have absolute URLs for both www.site.com and www.site.ca, you may wish to add both of these
to the Domains of Resources to Treat. A single treated domain will only allow one Fetch and one
Write definition, so if a resource is at a URL that needs to be fetched or written uniquely, it should be
a new treated domain.
When clicking on a treated domain name, you can edit the source.

To define which resources to treat

1. From the drop-down list, select the match type to the URL that the resource comes from. You
can select All, Exact, Contains, Starts with, Ends with, or regex.
2. Enter a URL pattern to match. Except for the non-editable local ones, these are part of the
domain URL.
3. From the drop-down list, select the type. This is the inclusion or exclusion of matching the
pattern type. Normally, inclusion is used unless you want to remove a previously matched
domain.
Figure 31: Domains of Resources to Treat
Define How to Fetch Resources to Treat

There are two definitions for how to fetch resources. If you are modifying the local treated domain,
the resources are always fetched from the back-end of the defined bound virtual server. This is
because the local treated domain is assumed to retrieve resources from your actual Web server and
the resources are expected to be at that location. If the resources are actually on different servers,
you need to define another treated domain.

Figure 32: How to Fetch Resources to Treat
To define how to fetch resources to treat

> Edit the required parameters as defined in the table below.
Note: It is possible and usually desired to create one treated domain for all the external
resources you wish to treat. However, if you define multiple URLs to capture in the Domains of
Resources to Treat, you should leave the defaults in the How to Fetch. This is because each
resource will be fetched by its actual original URL location. If you change the defaults you are
specifying that no matter what the original URL was, you want to override the actual location of
the physical resource, and all domains in this treated domain definition will have the resources
at the same location.

Table 17: Resource Parameters
Protocol The default protocol for fetching resources is to use the protocol defined by the
absolute URL of the original resource. It is possible to override this and specify
either HTTP or HTTPS. For example, if your original resource URL was at https://
server/myresource.gif, you may want to fetch it from http://server/
myresource.gif instead.
Host The default host to fetch a resource from is the one defined by the original
absolute URL. You can override this setting by specifying a host. For example if
you want http://serverA/resource.gif to come from http://serverB/resource.gif
instead.
Port The default port to fetch a resource from is the one defined by the original
absolute URL. For http and https this is port 80 and 443 respectively. However,
you can override this to fetch resources from a specific port.
IP Address Normally when resources are fetched from backend servers, they are fetched
using DNS to look up the IP of the URL. However, you can manually specify the IP
address of the backend server where the resources are held. Note that in order to
use the DNS lookup, you must have a valid DNS server defined.
Define URL of Treated Resources

The final part of a treated domain is to identify how treated resources are written out in the resulting
html page. If a resource is treated by this matching treated domain, the URLs should be rewritten in
the format specified in the table below.
Figure 33: Define URL of Treated Resources

To define the URL of treated resources

> Edit the required parameters as defined in the table below.
Table 18: URL of Treated Resources
Protocol By default the new protocol for the treated resources will match the same as the
page returned to the client. You must leave this as default for the local treated
domain if you are you are using an Upstream SSL termination method of HTTP
and HTTPS so that the resources are written out to the correct protocol for the
page. However, you can specifically set this value if you wish all resources to
either be written out as either http or https.
Dynamic If the Dynamic Connection Maximizer (DCM) Treatment is enabled for a Web App,
Connection this configures what DCM prefixes are written out for the treated domain. This
Maximizer Host needs to be configured in each treated domain configured for the Web App. If
Prefixes DCM is enabled, a randomly selected prefix will be used for each treated resource
written out. For more information regarding the DCM treatment set, refer to
Dynamic Connection Maximizer, page 110
Use Host In most cases the rewritten domain for the resources will be the same host as
used by the page. This will cause requests for the URL to come back to the
FastView where the resource may be cached, or can pass on the request as
appropriate. However, it is possible to change the host of the rewritten resource
to another location. This is especially useful if you want to redirect resources to a
CDN or resource server. It is important that if you use this functionality to
redirect resource requests to a CDN to ensure the CDN can fetch the resources
from the FastView as needed since FastView may contain treated versions of the
resources.
Port The default is to use the same port that the page uses when being written out. If
you want new specific ports used you can specify them for the available
protocols.
Classification Rules
Classification Rules define which pages of the Web Application should be treated.
Information about all defined Classification Rules including name, match type, pattern, page
classification and order are listed in the Classification Rules tab.
From this tab, you can enable a Classification Rule from the list, edit the parameters of one of the
defined Classification Rules, or add a new classification rule.

Figure 34: Classification Rules
Defining classification rules includes the following:

• Defining which pages should be treated
• Excluding pages from the treatment
• Identifying pages as unique based on query parameters or cookies
• Grouping pages together to look like the same treated page
• Defining if Landing Page optimization should be done
• Defining if the HTML pages should be cached by FastView or Client
To define classification rules information

1. Select a classification rules from the list, or click New.
2. Edit the selected classification rule or defined the new classification rule with the required
parameters as defined in the table below.
3. Click the up and down arrow to set the order of the classification rule.

Note: Classification Rules are applied on a first match basis. Therefore it is important that you
ensure your exclusions are at the top of your list, with your Include All default classification rule at
the bottom. You can sort Classification Rules once they are added.
Table 19: Classification Rules
Name Provide a name for your classification Rule. You will notice that by default there is
an Include All (Default) classification rule.
Type To define pages for treatment, set the Type to inclusion. If you want to exclude
pages from treatment see the section on exclusion.
Match Type Define a match type for identifying pages to include in this page treatment
definition. If you are unsure, “Contains” is usually a safe option if your pattern is
unique enough to identify only the pages you are looking for. The Match Type of
“RegEx” is defined in the Group Pages Together section.
Pattern Except in cases where you are using Match Type: RegEx, the pattern will be a
string match of your URL based on the Match Type you have selected. If you have
selected “All” in your Match Type, you can leave this blank. This is a full URL
string match (defined by Match Type). Therefore the full “http://yoursite.com/
pathtofile/file.html” is a full URL match, not just the “/pathtofile/file.html”.
Case Sensitive If you are using a Case Sensitive Web Server, you can select this option. This will
specify that case uniquely identifies pages in this grouping and matters for the
pattern matches. For example, selecting this option makes “page1.html” and
“Page1.html” different and unique pages for treatment. This is not required for
most configurations.
Note: Only select Case Sensitive definitions if you know your site to be case
sensitive. This is because the identification comes from the client requested
URL. In the case of a server like IIS, it will respond to both “page1.aspx” and
“Page1.aspx” with the same page, but with this option selected two completely
different compiled instructions will result.
APM Enabled If the APM Enabled checkbox is unchecked, the Application Performance
Monitoring (APM) beacon will not be inserted on pages matching the pattern. This
is useful on iFrame content and pop up pages.
Landing Page If the Landing Page Candidate checkbox is checked, pages matching the
Candidate pattern are considered Landing Page Candidates. This means that any client
visiting a matching page on the Web site for the first time will be served a
Landing Page version of the page. All subsequent pages viewed are seen as non-
Landing Pages. Landing pages are basically optimized pages for more quickly
loading the first page of a site. For more information on this topic see Landing
Page Consolidation. The Include All (default) classification rule is defined to
create Landing Pages. If you create special classification rules to identify pages
before the default classification rule, be sure to specify if you want this feature
enabled.

Table 19: Classification Rules (cont.)
Predictive Each grouping of pages you want to treat can have a unique Predictive Browser
Browser Caching Caching List. To enable this:
1. Ensure you have a Treatment Set associated to this Web Application that has
the Predictive Browser Caching Treatment enabled.
2. Create a Predictive Browser Caching List. This can be found under Defining
Web Application Predictive Browser Caching.
3. From the Drop-down Predictive Browser Caching List in Classification Rules,
select the defined Predictive Browser Caching List.
Note: Enabling the Predictive Browser Caching Treatment for a Web
Application still applies loading of the Application's Automated Predictive
Browser Caching and Landing Page Consolidation Repeat Views (if enabled)
regardless of list selections in Classification Rules. The association of the Lists
are only for the purpose of loading specified manual resources or pages.
Optimized HTML Enable and configure caching durations for Optimized HTML caching, Browser
Caching Caching and Browser Side Includes in this section.
Query Param Lists the query parameter names applicable to the Classification Rule.
Names (one per
line)
Exclude Pages from Treatment

Just as you can create a Classification Rule to specify a special way to treat a page, you can also
specify pages not be treated. To do this, create a classification rule in the same way you would an
exclusion, but set the Type to Exclusion. Remember, classification rules are applied on a first
match basis, so it is often a good idea to reorder your exclusions so they are at the top of the list.
Identify Pages as Unique

Normally a page is identified purely based on the URL of the page. Any cookies or query parameters
passed to the page have nothing to do with its uniqueness as an individual page. In some cases, this
may not be accurate.
For example, if you have a store and product pages load completely different content based on a
query parameter (such as ?product=[product]) or a user page that may look different based on a
cookie (such as SL_UserCookie=[userid]), you may want to identify that even though the URL is the
same, the page should be identified as unique.
In this case Factory Page configuration can be used.
Currently, Factory Page configuration is not available in the Web UI but only in the XML configuration
file. Please refer to Radware support for more guidance if this feature is applicable for your Web site.
Group Pages Together

Just as you can identify pages at the same URL as unique based on cookies and parameters, you can
also consolidate pages at multiple URLs to be the “same page”. This is often done for pages that are
actually very similar (such as a product page) that simply uses a different URL to identify a picture
and some text to load, or in the case where the same page may be found at different locations on a
Web site.
In these cases, you would create a Classification Rule as normal to identify the page, but specify the
following:
Match Type: RegEx

Once a RegEx Match Type is selected, you have two important fields to identify: Pattern and
Replacement. Unlike a normal string match Pattern, once you have selected RegEx, the Pattern
becomes a RegEx match. The Replacement field is the replacement variables (such as $1$2). This
documentation does not cover in-depth regex.
Landing Pages
Logically, a landing page can be considered as any Web page that a user may first arrive at when
visiting your site. In FastView, landing pages are those pages that should display to the client as
quickly as possible, while at the same time FastView is preparing the rest of the site to work quickly
and optimally with the other FastView treatments.
Landing Page Consolidation is a FastView feature where the treated page inlines as many resources
as possible so that the client does not have to download multiple resources to receive a Web page.
This is useful for pages where clients enter your site (such as login pages or home pages) as it
generally helps the page load faster.
When Landing Page Consolidation is enabled, the first page the client browses to on your Web
application is served as a landing page. All subsequent pages (including any refresh of the first
page) are displayed as a non-landing page.
Typically, Landing Page Consolidation is used in conjunction with a feature such as Predictive
Browser Caching.
• Configuration, page 92
• Landing Page Versus Non-Landing Page, page 92
• Preloading the Non-Landing Page Version Resources, page 93
Configuration
Use this procedure to configure landing page consolidation.
To enable Landing Page Consolidation

1. Navigate to Acceleration > Web Applications.
2. Click the name of the selected Web application.
3. Open the Classification Rules pane.
4. Click the name of the selected rule.
5. Check Landing Page Candidate.
By default, this is enabled for the All Pages default classification rule. The reason for this is that a
landing age is only compiled on FastView if it is the client's first visit to a page on your site. If a user
has an SL_ClassKey cookie, they have been considered to have visited the site before and will not
receive a landing page.
Landing Page Versus Non-Landing Page

The main difference between a landing page and a non-landing page is in how they affect
treatments. When trying to identify individual resources in a landing page, you may find that the
treatments have been applied differently. For example, if Image Consolidation is enabled, an image
may have been consolidated directly into the page using base 64 encoding when served as a landing
page. This causes as few resources as possible to be transferred to the client, resulting in fewer
round trips to the server to fetch resources for the first time.
A non-landing page typically affects resources as individual resources. You may see these resources
with different headers, or parameters, and in the cases where consolidation is applied, a unique
filename.

Preloading the Non-Landing Page Version Resources

A user navigating to a landing page for a second time receives the non-landing page-compiled
version of the page. Because of this, it can be helpful to have the resources on that repeat view
preloaded.
To preload non-landing pages

1. Enable Predictive Browser Caching.
2. Enable the sub-feature Preload for Landing Page Consolidation Repeat Views.
Optimized HTML Caching

By default, html pages, and all variations of these type of pages, are not cached by FastView, nor
does FastView instruct the client browsers to cache the pages. This is because most Web Sites have
dynamic html pages, and static resources.
It is possible, however, that your Website may have pages that are considered static, and you want
either FastView, the client browser, or both to cache these pages. By selecting Optimized HTML
Caching you can do this for pages matching the Classification Rule selected.
Once selected, you have some extra configuration options.
• Caching Duration—The amount of time in seconds that a page will be cached on FastView. In
this time, all requests for this page will be offloaded from your Web Server. When the time
expires the next hit will poll your Web Server for an updated version of the page once again
beginning the caching process.
• Browser-Side Includes—Selecting this option allows you to select dynamic sections of the HTML
using XPATH queries. This allows for the static portion of the HTML to be cached, and the
dynamic sections to be downloaded and inserted when returned by the origin server. We
recommend that only cache pages with dynamic content is enabled at all times.
If Optimized HTML Caching is specified for a classification rule, you still have the option to override
this caching by specifying a specific request cookie with a page request. This is defined in the
Advanced Settings of a Web Application.
Predictive Browser Caching

Predictive Browser Caching works by identifying resources that are commonly used in your Web
Site, or used on future pages. Once the resources are identified, the treatment sends these
resources to the client after pages have finished rendering; while the browser is idle. This gets
resources into the client browser's cache for use when the page that calls them is actually
requested. This causes the pages to load much faster from the perspective of the client.
The Predictive Browser Caching Treatment can be found in the Dynamic Browser Caching dialog of a
Treatment Set.
For Predictive Browser Caching configuration at the Treatment set, see Predictive Browser Caching,
page 106.
Building Preload Lists

FastView handles preloading on all treated resources. However, you can create preload lists in a Web
Application, which contain specific resources or pages. For more assistance in building a preload list,
contact Radware Technical Support.

Deferrals
The Deferrals pane has four distinct parts to it:
• Image Deferrals
• iFrame Deferrals
• External JavaScript Deferrals
• Inline JavaScript Deferrals
Deferral options, while enabled by the associated treatment set, must be configured uniquely for the
Web application.
To configure deferrals for a Web application

1. Enable the Templated Deferrals options in the Associated Treatment Set.
2. Create a Deferral.
3. Set Deferral to be Compiled or Dynamic.
4. Associate the Deferral with the appropriate Classification Rules if required.
Deferral List
Deferrals can be created, enabled, disabled and deleted. When you create a New Deferral, you need
to provide information about the image, iFrame, external JavaScript or Inline JavaScript, which you
wish to defer; select a replacement mode and select which Classification Rules it should apply to.
Image Deferrals
A text field is displayed in which a string matches on contains the src attribute of <img> and certain
<input> elements. All matching elements will be deferred.
Figure 35: Image Deferrals
iFrame Deferrals
You should configure the name of the iFrame file you want to defer. iFrame deferrals should be used
on iFrames that block start render time and are not essential to initial interaction with the page by
the user. Third party tags and social elements, such as Facebook’s “like” button, are good candidates
for iFrame deferral.

Figure 36: iFrame Deferrals
External JavaScript Deferrals

You should configure the name of the external JavaScript file you want to defer. Blocking JavaScript,
especially when it impacts start render time, is often the best candidate for deferral.
Figure 37: JavaScript Deferrals
Inline JavaScript Deferrals

The WUI presents two text boxes, the first is a “starts with” and the second is a contains match. The
user enters the exact starting string from the inline JavaScript into the “starts with” box and then
some other unique string from the JavaScript into the contains box.
Figure 38: Inline JavaScript Deferrals
Exclusions (Excluded Treatments)

In the Exclusions tab, all defined excluded treatments are listed detailing the source, condition and
value.
Exclusions are one of many ways in which a resource can become untreated on a treated page. If
you are curious as to other methods that cause resources not to be treated, view the Examining
Device Treatment Section on Invalidation and Exclusions.
You can select (enable) one of the listed exclusions, edit the parameters of one of the defined
exclusions, or create (Add) a new exclusion.

Exclusions exclude the treatment of Resources, not Web Pages. If you want a Web Page to be
excluded from treatment entirely, you must set up the appropriate Classification Rules.
To define an exclusion
1. Select an exclusion from the list, or, click New.
2. Edit the selected exclusion or defined the new exclusion with the required parameters as defined
in the table below.
Table 20: Exclusions Options
Excluded Identifies the treatment in which the exclusion is applied.
Treatment
Source Identifies the source, either a Resource or Page.
Condition The condition identifies how the resource is identified to be excluded. Most values
are substring match types; however, regex can also be chosen.
Value A string which represents the resource to be excluded. In most exclusion
conditions, this is a substring. However, this value can also support the regex
exclusion condition. Note it is possible to exclude entire folders or multiple files
using either of these methods.
Purpose of Exclusions
Sometimes certain resources are affected negatively by some treatments because the Web site
expects the files to look and behave in a certain way (usually due to custom coding). Because
Treatment Sets are defined outside of your Web Application, exclusions provide a means to indicate
that specific resources found within your application should not have certain treatments applied.
Identifying Problem Resources

If you feel that a resource is being treated incorrectly, you can add it to the exclusion list to ensure
this is the case. Some examples include:
• If a JavaScript is not being triggered correctly once it has been consolidated, exclude it from
JavaScript Consolidation or another similar treatment which may be affecting it (such as
Browser Cache Invalidation).
• If an Image is not rendering on the page after being treated, exclude it from Image
Consolidation or another similar treatment which may be affecting it (such as Image
Compression).

Working with Treatment Sets
Chapter 7 – Working with Treatment Sets

The following topics outline the details of treatment sets. Treatment sets are the actions the actions
performed upon Web traffic as it passes between the Web server and a client browser to improve
performance. When a resource passes through FastView and has an acceleration treatment applied
to it, it is considered treated performed upon Web traffic as it passes between the Web server and
a client browser to improve performance.
Defining Treatment Sets

Web application developers can often quickly and easily develop Web applications for profitable
businesses. However, fine-tuning the applications for performance and scaling for large volumes of
traffic can often be difficult. When a Web application is under load, it can dramatically reduce Web
performance. There are other features, such as output caching and browser caching, which are very
useful scaling tools but difficult to implement in code.
An application acceleration treatment processes Web traffic as it passes between a client browser
and the Web server. Each application acceleration treatment is specifically targeted to an area of
Web site development that is vulnerable to performance degradation or presents an opportunity for
acceleration. If your application can take advantage of scaling mechanisms or uses performance-
degrading features, your application can benefit from improved performance when you apply an
application acceleration treatment.
Application acceleration treatments are the heart of the FastView Application Scaling System.
Application acceleration treatments are implementations of coding optimization techniques. When a
treatment is enabled in FastView and applied to a Web application, it processes Web traffic to
provide real-time code optimization that yields performance and scalability improvements.
Using treatments creates Web pages similar in logical structure to the hand-coded, more time-
consuming manual implementations of optimized Web pages. The difference is that treatment
optimizations can be added and removed on demand, in real time.
• Treatment Sets in Web Applications, page 97
• Treatments not Working, page 98
• Desktop and Mobile Treatment Sets, page 98
• Working with Treatment Sets, page 98
• Treatments, page 101
• Long-Tail Site Acceleration, page 134
Treatment Sets in Web Applications

Treatment sets are associated with Web Applications, defining what acceleration techniques are
applied as Web traffic flows through the Web application. Treatment sets can be used by multiple
Web Applications. Often specific settings of a Web application may affect the way individual
treatments work. For example, the Predictive Browser Caching treatment requires an additional
definition in the Web application to indicate which pages should be pre-cached by the end-client
browser. In this case, it would not be logical for Web site www.site-a.com to be pre-loading pages
for Web site www.site-b.com.

Treatments not Working

Although a treatment set may be associated with your Web application, you may find that certain
treatments are not applying the way you expected. If this is the case, do the following:
1. Check that the settings for the treatment are correct.
2. Ensure that the specified resources have not met one or more special exclusion criteria.
For more information, see Resources Not Treating, page 156.
Desktop and Mobile Treatment Sets

FastView supports treatment sets for both desktop and mobile devices.
Access to and support of mobile treatment features requires an appropriate license.
Note: All descriptions following are applicable for both the desktop treatment sets and the mobile
treatment sets, unless otherwise noted.

This section describes how to add and configure treatments in preparation for use by a Web
application. It includes the following topics:
• The Treatment Set List
• Adding a Treatment Set
• Editing a Treatment Set
• Copying a Treatment Set
• Deleting a Treatment Set
The Treatment Set List

The Treatment Set list displays a summary of all the treatment sets defined and their statuses.
FastView is pre-configured with default treatment sets. They are read-only and cannot be changed.
To create your own treatment set, you can copy one of the pre-defined treatment sets and then edit.
Pre-defined treatment sets for desktop acceleration:
• None—a treatment set containing no treatments.
• Classic—for good acceleration value with safest implementation and without compromising the
installation speed. Using the Classic treatment set brings acceleration to your site using the
following:
— automated preloading to learn usage patterns and provide flow acceleration
— managing the period used for browser side caching, with minimal HTML manipulation
— landing page optimization
• Recommended—for enhanced acceleration value. To achieve this, aggressive acceleration
techniques are used. Occasionally specific pages may break, which can be avoided with careful
FastView configuration and tuning. It is highly advised to use this treatment set only when
FastView Professional services are assisting with the configuration process.

• Experimental—best acceleration for the site. This treatment set employs innovative
acceleration techniques and must be used carefully. It is highly advised to use this treatment set
only when FastView Professional services are assisting with the configuration process.
Note: Alteon NG users can use the None and Classic pre-defined treatment sets only. These
treatment sets are read-only and cannot be edited.
Pre-defined treatment sets for mobile acceleration (applicable when mobile license is used):
• None—a treatment set containing no treatments.
• Mobile Classic— for good acceleration value with safest implementation and simple
deployment. Using the Classic treatment set brings acceleration to your mobile users using the
following:
— CSS Mobile SuperCache
— Automated preloading to learn usage patterns and provide flow acceleration
— Landing Page Consolidation for CSS
— Non-Landing Page HTML size reduction
— Managing the period used for browser side caching, with minimal HTML manipulation
• Recommended—for enhanced acceleration value. To achieve this, aggressive acceleration
techniques are used. Occasionally specific pages may break, which can be avoided with careful
FastView configuration and tuning. It is highly advised to use this treatment set only when
FastView Professional services are assisting with the configuration process.
To display the treatment set list

> Navigate to Acceleration > Treatment Sets.
Figure 39: Treatment Set List
The treatment set list includes the following parameters:
Table 21: Treatment Set List Information
Name The name identifying your treatment set. You should provide a name that
describes the purpose or functionality of the treatment.
The name is a link that opens the editing page for the treatment set.
Web Displays Web applications associated with this treatment set. These are displayed
Applications as links so that you can open the editing pages for these Web applications.
Number of A summary of the number of treatments enabled in this treatment set. It does
Treatments not detail the sub-treatments of the enabled treatment sets. For example, you
only see the details for the Payload Reduction Treatment, but not its sub-
treatments View State and Compression.

Adding a Treatment Set

Use the following procedure to add a treatment set.
To add a new treatment set

1. From the Treatment Set list, click New.
2. Edit the name of the new treatment set.
3. Select Add/Remove Treatments. All the available treatments and treatments included in the
treatment set are listed. (Default includes all treatments.)
4. To define which treatments are included in the treatment set, select an available treatment and
click Add>> to add it to the included treatment list, or select an included treatment and click
Remove>> to remove it from the included treatment list, and click Apply.
5. Edit the various treatment configurations, each within its own pane. For details on each
treatment, review the relevant section in this guide.
6. On the bottom of the page, click Save.
Editing a Treatment Set

Use the following procedure to edit a treatment set.
To edit a treatment set

1. From the Treatment Set list, select the treatment set to edit.
2. Edit the treatment configuration. For details on each treatment, review the relevant section in
this guide.
3. On the bottom of the page, click Save.
Copying a Treatment Set

Use the following procedure to copy a treatment set.
To copy a treatment set

1. Select the checkbox next to the name of the treatment set to copy.
2. Click Copy Selected to create a new treatment set based on the copy.
3. Edit the new treatment set.
Tip: When copying a treatment set to create a new treatment set, you should copy a default
treatment set (marked as read-only). This way you do not need to define all of the parameters for
the treatment set, only the ones that you need.
Deleting a Treatment Set

Use the following procedure to delete a treatment set.

To delete a treatment set

1. Select the checkbox next to the name of the treatment set to delete.
2. Click Delete Selected.
3. At the prompt, confirm the deletion.
Treatments
This following topics include details on the treatments you can use for your Web applications, and
how to modify them according to your needs.
The treatment sets include:
Dynamic Browser caching:
• Browser Cache Invalidation, page 102
• Browser Cache Expiry, page 104
• Predictive Browser Caching, page 106
• Mobile Super Cache, page 109 (mobile only)
Dynamic Connection Maximizer: (not mobile)

• Dynamic Connection Maximizer, page 110.
Dynamic Resource Consolidation: (not mobile)

• CSS Consolidation, page 114
• JavaScript Consolidation, page 116
• Image Consolidation, page 118
Rapid Rendering:
• Progressive Image Rendering, page 121
• Touch Event Conversion (Mobile only), page 122 (mobile only)
Output Cache:
> Output Cache, page 123
Payload Reduction:
• ViewState Removal, page 126
• Dynamic Compression, page 127
• Image Compression, page 129
• JavaScript Minification, page 131
• CSS Minification, page 132
Search and Replace:

> Search and Replace, page 132
Templated Deferrals:
> Templated Deferrals, page 133
Note: At the top of the pane there is a drop-down Display Settings selection box from which you
can select Normal or Advanced. In many of the treatment tabs, only the basic parameters display
if set to Normal. More advanced and detailed parameters display if set to Advanced.

Dynamic Browser Caching

Dynamic Browser Caching includes the following treatment sets:
• Browser Cache Invalidation, page 102
• Browser Cache Expiry, page 104
• Predictive Browser Caching, page 106
• Mobile Super Cache, page 109
To edit the Dynamic Browser Caching treatment parameters

1. Navigate to Application Delivery > Application Services > FastView > Desktop
Treatment Sets or Mobile Treatment Sets.
2. Select one of the treatment sets.
3. Select the Dynamic Browser Caching tab.
Browser Cache Invalidation

Browser Cache Invalidation (BCI) causes the browser to cache resources for an extended period of
time. By doing this, the Browser Cache Invalidation treatment can use the browser's ability to store
resources locally. Similar to the Consolidation methods, aliasing occurs by taking the resource and
appending an MD5 value to the end of it.
Browser Cache Invalidation includes the following steps:
1. The resource is aliased and the HTML or CSS is modified to reference the new aliased resource.
If any Consolidation treatment is used, the aliased consolidation takes precedence.
2. Aliased resources are assigned header values to extend the Cache-Control and Expires header to
one year.
— Cache-Control: max-age=31536000
— Expires: <date + max-age>
The Browser Cache Invalidation treatment can provide great benefit to any site. By placing an MD5
tag on resources and setting long expiry headers, it helps to extend the cache life of resources on a
client's browsers while simultaneously ensuring that the client has the latest version of the file. This
can help with clients and servers with high latency, saves bandwidth, and uses the caching already
available to every client browser.
To configure the Browser Cache Invalidation Treatment

1. From a treatment set, select Dynamic Browser Caching.
2. Select Enable Browser Cache Invalidation to enable it. No other options are available.

Figure 40: BCI Treatment
Testing
Using a tool that can examine resource requests, you should see that resources treated with BCI
should be returned as the following:
• A BCI resource has the same URL as the original resource, except that it contains the parameter
of ?Lo0P=[MD5 Value].
• A BCI resource has a header of “Cache-Control” with a value of “max-age=31536000”.
• A BCI resource has a header of “Expires” with a value of [date + max-age].
When refreshing the page, the resources should be requested from the client browser's cache. The
result may be different depending on the browser, but you should see one of the following two
results:
• An indication that the response was from (cache).
• A 304 indicating that it only polled the server to ensure the resource has not changed. The exact
response back to the browser depends on your browser settings.
If the response headers are not applied to your resources, it is possible the content type is not
treated by default.

To change the content type

1. Navigate to Appliance Management > Edit Config XML.
Note: This option is only accessible in Advanced Display Settings, from the top of the pane.
2. Search for “ResponseCacheSettings”. There is one of these in each treatment set. Make sure you
are under the correct treatment set.
3. Edit the contentTypeList value to insert the appropriate content types.
Note: Modifying this value also affects the Output Cache Treatment. For more information, see
Output Cache, page 123.
Headers are Being Ignored by the Browser

If the response headers exist, but the resources are not coming from your browser cache, this is a
browser setting. Each browser behaves differently in how it is directed to pull from cache. Any of the
following can affect this:
• Specific browser settings indicating how to store cache.
• Closing and reopening a Web browser before trying to reload the page.
• The method of reloading the page (for example, a reload versus pressing Enter in the URL bar).
Interaction with Other Treatments

Browser Cache Invalidation takes precedence over Browser Cache Expiry in that it will create MD5
resources and place its own expires header on them. However, the CSS, Image, and JavaScript
Consolidation treatments take precedence over Browser Cache Invalidation because any resource
that is treated by both is placed inside a consolidated package if possible.
Because Radware recommends that consolidation treatments are not used for non-landing page
versions of your site, Browser Cache Invalidation is a vital method for allowing client browsers to not
request resources that have already been cached: either through landing pages, use in multiple
locations on your site, or predictive browser cache.
Browser Cache Expiry

The Browser Cache Expiry treatment lets administrators apply a global time to cache for client
browsers. The treatment monitors resources as they traverse the appliance and applies a global
cache value.
When the Browser Cache Expiry treatment is enabled, all page resources are cached by the client's
browser (such as images, underlying files, CSS files, JavaScript files). The dynamic ASPX page itself
is not cached. The next time the browser requests the page, the resources are served from the
client's browser cache instead of being fetched from the Web server.
Caching page resources eliminates many round trips from the browser. Also, setting a global time to
cache simplifies development by freeing developers from having to set a cache value per page.
Caching page resources may mean that for some resources, updates may take some time to occur.
In many application scenarios, this has little impact on the user experience but significantly reduces
the burden of Web servers under heavy load.

Browser Cache Expiry works by adding the following headers to all cacheable resources:
• Cache-Control: max-age=900
• Expires: <date + max-age>
Note: Browser Cache Invalidation functions much the same way, but works by actually
modifying the file name of the resource. Browser Cache Expiry can be used as a safety net, even
if Browser Cache Invalidation is enabled, to catch resources that are not being treated by that or
other treatments. The Browser Cache Expiry Treatment is of greatest value when relatively
static resources are on the Web site and are requested frequently. This causes the client's
requests to get the resources from the browser's local cache, rather than making a full round-
trip request to the server.
To configure the Browser Cache Expiry Treatment

2. Select Enable Browser Cache Expiry to enable it.
Figure 41: Dynamic Browser Caching
Note: To view the specific Browser Cache Expiry parameters, the Display Settings (at the top
of the pane) must be set to Advanced.
3. Modify the following options, as appropriate:
Table 22: Browser Cache Expiry Treatment Options
Cache Expiry Two response headers are put on resources treated with this treatment. This is
Time the number of seconds that are included in those response headers:
• Cache-Control: max-age=<Cache Expiry Time>
• Expires: <date + Cache Expiry Time>
Overwrite Cache By default, the Browser Cache Expiry treatment does not overwrite the Cache-
Control Headers Control or Expires headers if they already exist or are a higher value than set in
from Server Cache Expiry Time. Selecting this option causes this treatment to apply these
headers regardless of the values set by the Web server.
Respect no This option controls whether FastView respects the No Cache Directive in the
Cache Directives cache control headers set by the server. Visible only in Advanced Display
Settings.

Testing
If the Browser Cache Expiry Treatment is working, you see the Browser Cache Expiry content header
on your Web page.
Using a tool that can examine resource requests, you should see that resources with this header
returning with the following response codes:
• An indication that the response was from (cache).
• A 304 indicating that it only polled the server to ensure the resource has not changed. The exact
response back to the browser depends on your browser settings.
If the response headers are not being applied to your resources, there are a few things you can
check:
1. Ensure the treatment has the content-type defined. HTML is not Browser-Cached. This list can
be found in the Edit XML section by modifying the following:
a. Search for <CacheControlSettings>.
b. Modify the contentTypeList values.
c. Repeat for each treatment set you want to modify - Treatment Sets > Treatment
Set(ID) > CacheControlSettings: contentTypeList.
2. Browser Cache Invalidation and Consolidation Treatments overwrite the expiry times you have
chosen to set. If you want to ensure Browser Cache Expiry is working on its own, turn off these
other treatments. Note that both BCI and Consolidation provide better caching as they can
change cache settings based on modified files. However, it is a good idea to keep Browser Cache
Expiry enabled for files that end up unmodified by these treatments.
Headers are Being Ignored by the Browser

If the response headers exist, but the resources are not coming from your browser cache, this is a
browser setting. Each browser behaves differently in how it is directed to pull from cache. Any of the
following can affect this:
• Specific Browser settings indicating how to store cache.
• Closing and reopening a Web browser before trying to reload the page.
• The method of reloading the page (for example, a reload versus pressing Enter in the URL bar).

All Consolidation treatments as well as the Browser Cache Invalidation (BCI) set long expiry times
on their resources. These override the settings provided by Browser Cache Expiry.
Predictive Browser Caching

Predictive Browser Caching works by identifying resources that are commonly used in your Web site
or used on future pages. After the resources are identified, the treatment sends these resources to
the client after pages have finished rendering (while the browser is idle). This retrieves resources
into the client browser's cache for use when the page that calls them is actually requested. This is
referred to as preloading. This causes the pages to load much faster from the client perspective.
Automated Flow Acceleration

You can further enhance Predictive Browser Caching with an automated configuration based on real-
time site usage. FastView learns the Web site navigation patterns and automatically assigns preload
lists for Web pages. Automated preloading learns page transition patterns on the Web site, as well
as their frequency, to determine which objects are to be preloaded for each page. For each page in
the Web site, FastView keeps a list of target pages (pages to which the user navigates from the
original source page). Resources from the top n number of target pages are added to the preload list
of the source page.

To illustrate this feature, think of a source page called home.html, from which users can navigate
to the target pages p1.html, p2.html, and so on. FastView learns the frequency for each target
page and adds resources from the top n number of the most frequently used target pages to a
preload list for home.html. The target pages for each source page, as well as their frequency, are
updated on a regular basis according to real traffic to the site.
To define automated flow acceleration

1. From the Treatment Set page, view the Dynamic Browser Caching > Predictive Browser
Caching section.
2. Select the checkbox Automatically Preload from Page Transition Data.
3. Select Save.
4. Assign the treatment set to the Web application.
Browser Instrumentation
Browser Instrumentation (BI) allows your FastView visibility to browser rendering, which enhances
FastView’s capture capabilities.
BI also allows you to preload resources, such as JavaScript, CSS or images, that FastView would
otherwise not treat, but are part of the HTML DOM in the page. These resources are usually added
with scripts that either dynamically create them or inject HTML from an external source. Gathering
information from a real Web browser gives the compiler more information about DOM of a page and
allows for more complex treatments.
BI can also assist in loading images more efficiently. For more information, see Image Compression,
page 129.
To configure the Predictive Browser Caching Treatment

2. Select Enable Predictive Browser Caching to enable it.
Note: To view the specific Predictive Browser Caching parameters, the Display Settings (at the
top of the pane) must be set to Advanced.

Table 23: Predictive Browser Caching Configuration
Enable Enable or disable the entire treatment. When this treatment set is
associated with a Web application, it is important to configure all
the other options if this treatment is enabled.
Automatically Preload from If enabled, Automated Predictive Browser Caching monitors and
Page Transition Data learns end user site behavior, and creates preload lists based on the
most common target pages from a source page. The number of
target pages is configurable in the Max Target Pages field (available
only in Advanced Display Settings in the GUI) to define the
number of target pages whose objects are used for the preload list
for a source page. Default: 3.
Use App Defined Page Filters If enabled, the Predictive Browser Caching Pages list are used to
identify resources to preload from. This is configured by Web
application through the Predictive Browser Caching dialog.
Use App Defined Resources If enabled, the Predictive Browser Caching Resource lists is used to
identify resources from which to preload. This is configured by a
Web application through the Predictive Browser Caching dialog.
Resource to Load Each of the resource types specified here (images, CSS, JavaScript)
can be individually selected for availability by Predictive Browser
Caching. Selecting the options here only indicates that Predictive
Browser Caching preloads these resources if they are available. In
some cases (such as Global Resource Manager), you must
configure the other features to provide resources of a specific type
for Predictive Browser Caching to make use of them. For example,
if the Global Resource Manager is not configured to record CSS
files, Predictive Browser Caching does not preload CSS files from
the Global Resource Manager list even if selected here.
Note: Available only in Advanced mode in the GUI.
Predictive Browser Caching As part of the preloading definitions, you can specify any number of
Restrictions files (resources) and a maximum number of bytes to preload. This
ensures that a client's browser is not overloaded with data after a
page render is complete. Although it should not hinder page load
times or the user's interaction with the Web site, it may use up
unnecessary bandwidth.
Note: Available only in Advanced mode in the GUI.
Note: In order to keep HTML pages static for improved caching, preload lists can be
downloaded via an XHR request, instead of being embedded in the HTML. This feature is not
available in the Web UI but only in the XML configuration file. Please refer to Radware support
for more guidance if this feature is applicable for your Web site.
Testing
Predictive Browser Caching can be complicated to test as it requires configuration in multiple areas.
However, when Predictive Browser Caching is enabled, you should see one or more of the following
files being called on a compiled page:
• slpre.js
• pdata.js

• gdata.js
• cdata.js
• adata.js
All of these files and their functions are described in Treatment Files, page 153. If you are expecting
a specific file type but are not receiving it, this is because FastView has determined that this type of
preloading does not need to occur on this page.
Note: Preloading by page and Automated Preloader only occurs when the target page has already
been compiled by FastView. Until the page is compiled, Predictive Browser Cache does not preload
resources from that page even if it is defined as a page to preload in the Web application.
If the treatment is occurring, but not all resources are displayed, there are many factors that could
cause this. Check the following conditions:
• Ensure that your browser does not already have a locally cached copy of the file. Ensure that
you have not reached your resource count limit.
• Ensure that the list you expect the preloader to be getting the file from is enabled and
configured correctly.
• If using the Automated Preloader, Predictive Browser Caching by page or landing page
resources, ensure that the source page has been compiled and treated by FastView.
• If GRM resources are missing from your Predictive Browser Caching treatment, ensure that the
same resource types are set both under the GRM settings and the Predictive Browser Caching
settings.

Predictive Browser Preloading interacts with other treatments and features based on the options set.
Through the treatment itself, it can be affected by Landing Page Consolidations, Web Application
Classification Rules and Web Application Preload Lists.
However, when using the Manual or By Page preloading options, the configuration options in the
Web application enable for even further interaction. By specifying optimized resources, you can
preload resources that are already fully optimized for your site. This means that a preloaded
resource can be affected by every treatment in your treatment set and modified appropriately by the
configuration defined.
Mobile Super Cache

Mobile browser caches are much smaller than those of desktop browsers and can fill up after viewing
just a few pages of a site in a single visit. When that happens, the browser begins to remove items
from the cache, nullifying the performance benefits of caching. In addition, some mobile browsers
also flush their cache every time a user powers down their device.
FastView uses the scaffolding of HTML5 to offer a mobile browser cache that is comparable to the
desktop browser cache. It leverages an HTML5 feature called Local Storage to bypass the limitations
of mobile caches. The resulting Mobile Super Cache offers the ability to configure persistent, reliable
storage, providing faster page rendering for repeat visitors.
Note: This treatment is available only to mobile treatment sets.
Configuration
Use this procedure to configure the mobile super cache.

To configure the Mobile Super Cache Treatment

2. Select Enable Mobile Super Cache to enable it.
Figure 42: Mobile Super Cache
Table 24: Mobile Super Cache Configuration
JavaScript Resources Select the appropriate checkboxes to apply mobile super cache to
external JavaScript and/or to inline JavaScript.
Enter the maximum number of bytes of JavaScript resources.
CSS Resources Select the appropriate checkboxes to apply mobile super cache to
external CSS and/or to inline CSS.
Enter the maximum number of bytes of CSS resources.
Dynamic Connection Maximizer

Many browsers only allow a limited number of simultaneous connections. However, current Web
servers (and bandwidth) have reached a point where they can handle sending more data than the
few connections being requested. The Dynamic Connection Maximizer (DCM) rewrites your Web
pages so that the resources on the page are spread out over a number of different locations. This
causes the browser to request more resources at once. The overall effect is getting more resources
faster. This is also compounded by there being no need to have a full round of latency while a new
connection is made, as many of the connections would be made simultaneously, compressing the
latency time.
Note: This treatment is not available to mobile treatment sets.

The Dynamic Connection Maximizer works on all resources in text or HTML, or css content, under
one of the following conditions:
• The resource links in the Web page are relative.
• The resource links in the Web page are absolute, but match the local domain.
• The resource links in the Web page are absolute, but are treated with another treatment (such
as Browser Cache Invalidation) so that they are rewritten to be in the local domain.
For each resource that resides in one of these locations, the URL is rewritten to the destination
domain with a random prefix as defined by the treatment configuration.
The following waterfalls show how Dynamic Connection Maximizer would save resource loading time
on a page:
Figure 43: Dynamic Connection Maximizer Graph
The Dynamic Connection Maximizer is of benefit on pages that contain a lot of content over
networks that can support more bandwidth than is consumed. This greatly affects the download
concurrency (and therefore speed) of Web pages served to older browsers. This treatment has less
effect on newer browsers such as Internet Explorer 8 (IE8), where the maximum connections of a
default browser has been increased.
The DCM Treatment contains two configuration areas of configuration:
• Configuration in the Treatment Set, page 111
• Configuration in the Web Application, page 112
Configuration in the Treatment Set

Use this procedure to configure the dynamic connection maximizer treatment.
To configure the Dynamic Connection Maximizer Treatment

1. From a treatment set, select Dynamic Connection Maximizer.
As the Dynamic Connection Maximizer is a separate category in the treatment sets, there are no
checkbox options to enable or disable this treatment. Ensure that the pane is enabled and the
treatment is available in this set.
2. Select one of the following configuration option of applying to specific browser types:

— Legacy Browsers—Applies the Dynamic Connection Maximizer treatment only to IE6 and
IE7 browsers. These browsers by default only allow two open connections to a server at a
time, and are the browsers most affected by this treatment.
— All Browsers—Modern browsers support multiple simultaneous connections for
downloading resources. Although the Dynamic Connection Maximizer can expand this
further by enabling this option, it should not be necessary.
Figure 44: Configuration in the Treatment Set
Configuration in the Web Application

After you have enabled DCM, the next step is to set the DCM prefixes in the Web application. Each
treated domain in each Web application needs to have the DCM prefixes set.
To set the DCM prefixes for each Web application

> For each Web application, in the URL of Treated Resources pane, add a single DCM prefix per line
in the DCM Prefixes text box. Each prefix is appended directly as entered to make a new URL for
rewritten resources (for example, a value of 1. prepends to make 1.www.mysite.com).
Each treated domain in a Web application that has the same resulting URL for resources should use
the same DCM prefixes. This does not cause any damage if this configuration is not set, but Radware
recommends to set it so that all treated resources are balanced among DCM Treated Resources.
Figure 45: Dynamic Connection Maximizer Configuration in the Web Application

Notes
• It is important that resulting URLs contain DNS entries to resolve to your server, otherwise
clients are not able to find the newly rewritten resource URLs.
• If you are using host header filtering in your Web application, ensure that you allow the DNS
versions of the domains to also be picked up by the Web application. Otherwise, the rewriting of
the treatment occurs correctly, but when the resource is fetched using the DCM prefix, FastView
does not send the request to the correct Web application and the file is not found.
Testing
If the DCM Treatment is working, you see each treated resource written out with one of the DCM
prefixes specified by the treated domain.
If the DCM prefixes are not being applied to your resources, it is likely the resource is not being
treated by another treatment. DCM only applies to resources that are treated by another treatment
and therefore are being rewritten by treated domains. Ensure that the original source of the
resource matches a treated domain rule. Also ensure that the new rewritten source matches that
same rule's output. If it does not, the resource may not have been treated by the original treatment
and you will need to diagnose that.
By default, there are some files that DCM does not apply to as rewriting these resource URLs can
potentially cause issues:
• *.asmx
• *-js.slpx
• ScriptResource.axd
• *.swf
• *.htc
To remove any of these internal exclusions

2. Search for “DynamicConnectionMaximizer enabled”.
3. Remove the resource filter for each type you want to allow to be treated.
4. Repeat for each treatment set.

The Dynamic Connection Maximizer applies to resources already being treated by other treatments.
It is important that at least one other treatment is applied to a resource, or the URL does not have
an opportunity to be rewritten and DCM applied.
Dynamic Resource Consolidation

The Dynamic Resource Consolidation treatment sets include the following:
• CSS Consolidation, page 114
• JavaScript Consolidation, page 116
• Image Consolidation, page 118

To edit the Dynamic Resource Consolidation treatment parameters

3. Select the Dynamic Resource Consolidation tab.
CSS Consolidation
CSS Consolidation takes multiple .CSS files called by a page and consolidates them into fewer .CSS
files. Fewer resources from the server generally result in less latency and fewer resource requests
for the client. The .CSS files are called with an MD5 parameter and given a long expiry time. If a
.CSS file referenced by the Web page is modified, the file is excluded from the consolidated .CSS
file, and a new consolidated .CSS file is created. Using this method, changing content can occur on
the page.
Note: This treatment is not available to Mobile treatment sets.

The exact consolidation method depends on the browser calling the page and is covered in more
detail in Testing, page 115.
The CSS Consolidation treatment is beneficial when a large number of .CSS files are used on a page.
By consolidating them together, the client makes fewer calls to the server for resources, resulting in
less latency and faster response times.
Note: If the same .CSS file is used over multiple pages throughout a site, it is better to keep non-
landing page consolidation disabled, and take advantage of the Browser Cache Invalidation
treatment to cache the file on the client browser.
To configure the CSS Consolidation Treatment

1. From a treatment set, select Dynamic Resource Consolidation.
2. Select Enable CSS Consolidation to enable it.

Table 25: CSS Consolidation Configuration
Apply Consolidation to Landing Sets whether CSS Consolidation should be applied to landing
Pages pages. As a landing page is usually the first page arrived at on
a site before any other treatments or preloading can have an
effect on client page load speed, Radware recommends leaving
this option enabled when using this treatment. This allows for
fewer round trips to the server for .CSS files on first page load.
Apply Consolidation to Non-Landing Sets whether CSS Consolidation should be applied to non-
Pages landing pages. Although this option can reduce round-trips to
the server for .CSS files, it does mean that a single .CSS file
used on multiple pages must be downloaded in a consolidated
package for that page. If .CSS files are being used across
multiple pages, Radware recommends that this option not be
enabled as the file will be treated as an individual file, capable
of being cached on the client browser for the entire site
(depending on other treatments being used).
Inline CSS maximum size (bytes) The maximum size a .CSS file can be consolidated inline to a
page. CSS Consolidation is not always inline, but when it is,
this value can be set. The landing page consolidation uses this
option.
Consolidation Background Images
Testing
How CSS Consolidation works depends on the client browser requesting the page, and if the page is
a landing page or not. The following consolidation methods can occur, and if you are looking for
consolidated content, it could be in any one of these methods:
Table 26: CSS Consolidation Methods
Method Description
X-CSS The X-CSS method takes multiple .CSS files and combines them into a single x-
css file. The new file is then referenced in the HTML. This is the fallback option for
CSS consolidation if an inline consolidation method is not used. The resulting file
is called an x-css file.
MHTML The MHTML method takes multiple CSS files and combines them into a single
MHTML file. This is a multi-part file that can then be referenced by the HTML. This
is used for browsers that support this method over the creation of an X-CSS file.
The resulting file being called is an MHTML file.
DataURL This method inlines the .CSS file directly into the HTML, but does so by creating a
dataURL file instead of placing it inline as readable text. This option is used in
supported browsers only.
Inline Text The inline method takes the .CSS files and places them inline with the HTML. This
causes only the single HTML file to be downloaded. It is the preferred method if
the browser supports this type of CSS consolidation as it has the fewest client-
browser resource fetches, and is a safe, well-supported method.
If a resource is not treated using consolidation, FastView determines that it is not treatable and does
not apply the settings.


CSS Consolidation has options to apply to landing and non-landing pages. Because of this, it is
affected by the configuration of Landing Page Consolidation. In addition to the options selected in
the CSS Consolidation Treatment, landing pages must be configured separately. This is done using
Web Applications Classification Rules. For more information on landing pages, see Landing Pages,
page 92.
CSS Minification can also be used in conjunction with CSS Consolidation. This causes the resulting
file to be a consolidated version of your CSS files minified to an optimal size. Because background
images can also be treated in CSS Consolidated files, the Image Consolidation treatment must be
enabled as well to treat consolidated background images.
JavaScript Consolidation
JavaScript Consolidation involves taking multiple JavaScript files called by a page and consolidating
them into fewer JavaScript files. Fewer resources from the server generally result in less latency and
fewer resource requests for the client. The JavaScript files are then called with an MD5 parameter
and given a long expiry time. If a JavaScript file referenced by the Web page is modified, the file is
excluded from the consolidated JavaScript file and a new consolidated JavaScript file is created.
Using this method, changing content can occur on the page.

The exact method of consolidation depends on the browser calling the page and is covered in more
The JavaScript Consolidation treatment is beneficial when a large number of JavaScript files are
used on a page. By consolidating them together, the client makes fewer calls to the server for
resources, resulting in less latency and faster response times.
Note: If the same JavaScript file is used over multiple pages throughout a site, it is better to keep
non-landing page consolidation disabled and take advantage of the Browser Cache Invalidation
To configure the JavaScript Consolidation Treatment

2. Select Enable JavaScript Consolidation to enable it.

Table 27: JavaScript Consolidation Options
Apply to Landing Pages Sets whether JavaScript Consolidation should be applied to landing
pages. As a landing page is usually the first page arrived at on a site
before any other treatments or preloading can have an effect on
client page load speed, Radware recommends leaving this option
enabled when using this treatment. This allows for fewer round-trips
to the server for JavaScript files on first page load.
Apply to Non-Landing Pages Sets whether JavaScript Consolidation should be applied to non-
landing pages. Although this option can reduce round-trips to the
server for JavaScript files, it does mean that a single JavaScript file
used on multiple pages must be downloaded in a consolidated
package for that page. If JavaScript files are being used across
multiple pages, Radware recommends not to enable this option, as
the file is then treated as an individual file, capable of being cached
on the client browser for the entire site (depending on other
treatments being used).
Use Single External When the X-JS file option is used based on the client browser type,
JavaScript File generally JavaScript Consolidation packages are split up based on the
logical break of content in a page. This can result in multiple X-JS
packages, instead of a single one. This option lets you force a single
downloadable package in the event this method is used.
Note: This may cause the scripts to run in a different order than
specified by the original page source.
Inline MaximumSize If the inline dataurl or inline text consolidation techniques are used
(based on client browser capabilities), this option lets you define the
maximum size a JavaScript to be inlined directly into the text or HTML
content.
Testing
How JavaScript Consolidation works depends on the client browser requesting the page, and if the
page is a landing page or not. The following consolidation methods can occur, and if you are looking
for consolidated content, it could be in any one of these methods.
Table 28: JavaScript Testing Methods
Method Description
X-JS The X-JS method takes multiple JS files and combines them into a single X-JS file.
The new file is then referenced in the HTML file. This is the fallback option for
JavaScript consolidation if an inline consolidation method is not used. The
resulting file is called an X-JS file.
DataURL This method inlines the JavaScript file directly into the HTML file, but does so by
creating a dataURL file instead of placing it inline as readable text. This option is
used in supported browsers only.
Inline Text The inline method takes the JavaScript files and places them inline with the HTML
file. This causes only the single HTML file to be downloaded. This is the preferred
method if the browser supports this type of JavaScript consolidation, as it has the
fewest client-browser resource fetches, and is a safe, well-supported method.


JavaScript Consolidation has the options to apply to landing and non-landing pages. Because of this,
it is affected by the configuration of Landing Page Consolidation. In addition to the options selected
in the JavaScript Consolidation Treatment, landing pages must be configured separately. This is done
using the Web Application Classification Rules. For more information on landing pages, see Landing
Pages, page 92.
JavaScript Minification can also be used in conjunction with JavaScript Consolidation. This causes the
resulting file to be a consolidated version of your JavaScript files minified to an optimal size.
Image Consolidation
Image Consolidation involves taking multiple image files called by a page and consolidating them
into fewer files. Fewer resources from the server generally result in less latency and fewer resource
requests for the client. The image files are called with an MD5 parameter and given a long expiry
time. If an image file referenced by the Web page is modified, the file is excluded from the
consolidated image file and a new consolidated image file is created. In this manner, changing
content can occur on the page.

The exact method of consolidation depends on the browser calling the page and is covered in more
The Image Consolidation treatment is beneficial when a large number of image files are used on a
page. By consolidating them together, the client makes fewer calls to the server for resources,
resulting in less latency and faster response times.
Note: If the same image file is used over multiple pages throughout a site, it is better to keep non-
landing page consolidation disabled and take advantage of the Browser Cache Invalidation
To configure the Image Consolidation Treatment

2. Select Enable Image Consolidation to enable it.

Figure 46: Image Consolidation
Note: To view the specific Image Consolidation parameters, the Display Settings (at the top of
the pane) must be set to Advanced.
Table 29: Image Consolidation Configuration Options
Apply to Landing Pages Sets whether Image Consolidation should be applied to landing
pages. As a landing page is usually the first page arrived at on a site
before any other treatments or preloading can have an effect on
client page load speed, Radware recommends leaving this option
enabled when using this treatment. This allows for fewer round-
trips to the server for image files on first page load.
Apply to Non-Landing Pages Sets whether Image Consolidation should be applied to non-landing
pages. Although this option can reduce round-trips to the server for
image files, it does mean that a single image file used on multiple
pages must be downloaded in a consolidated package for that page.
If image files are being used across multiple pages, Radware
recommends that this option not be enabled, as the file is then
treated as an individual file, capable of being cached on the client
browser for the entire site (depending on other treatments being
used).
Inline MaximumSize If the inline dataurl consolidation technique is used (based on client
browser capabilities), this lets you define the maximum size of the
files to be inlined directly into the text or HTML content.
Testing
How Image Consolidation works depends on the Client Browser requesting the page, and if the page
is a landing page or not. The following consolidation methods can occur, and if you are looking for
consolidated content, it could be in any one of these methods:

Table 30: Image Consolidation Testing Methods
Method Description
X-IMG The X-IMG method takes multiple image files and combines them into a single x-
img file. This x-img file is a container of sprite images. The text or HTML is
modified to call the correct portion of the sprite file. The resulting file is called an
x-img file.
I-JS The I-JS method takes multiple image files and combines them into a single i-js
file. This i-js file base-64 encodes the images in the same method as performing
an inline dataurl, except that the images are kept in a separate file instead of
inlined directly into the text or HTML. The resulting file is called an i-js file.
MHTML The MHTML method takes multiple image files and combines them into a single
MHTML file. This is a multi-part file that can then be referenced by the HTML. This
is used for browsers that support this method over the creation of an X-IMG file.
The resulting file is called an MHTML file.
Inline Data URL The inline method takes the image files and places them inline with the HTML.
This causes only the single HTML file to be downloaded. It is the preferred
method if the browser supports this type of image consolidation as it has the
fewest client-browser resource fetches, and is a safe, well-supported method.

Image Consolidation includes the options to apply to landing and non-landing pages. Because of
this, it is affected by the configuration of Landing Page Consolidation. In addition to the options
selected in the Image Consolidation Treatment, landing pages must be configured separately. This is
done using Web Application Classification Rules. For more information on Landing Pages, see
Landing Pages, page 92.
For CSS Consolidation to consolidate background images, Image Consolidation must be enabled.
Image Compression can also be used in conjunction with Image Consolidation. This causes the
resulting file to be compressed using image compression algorithms providing a resulting file that is
smaller than the originals.
Rapid Rendering
The Rapid Rendering treatment sets include the following:
• Progressive Image Rendering, page 121
• Touch Event Conversion (Mobile only), page 122
To edit the Rapid Rendering treatment parameters

Treatment Set or Mobile Treatment Set.
3. Select the Rapid Rendering tab.

Progressive Image Rendering

The Progressive Image Rendering (PIR) technique works by compressing and serving requested
images at a reduced image quality, and after the page has finished rendering, loading in the high-
quality images on top. This enables quick page render times yet still gives your final loaded page its
full high-quality feel.
FastView provides granular configuration for using of consolidation in conjunction with PIR. The full-
sized images can be consolidated or referenced separately:
• For landing pages, the full sized images are served consolidated for the most efficient page
rendering (PirLandingPageConsolidation is enabled by default). For some pages, disabling
PIR Consolidation the page renders some of the high-quality images sooner and therefore give
the impression of the page rendering faster.
• For non-landing pages, where the browser cache is typically already populated, consolidation is
not used, letting the browser use existing resources (PirNonLandingPageConsolidation is
disabled by default).
This treatment technique is of high value on sites that have many high-quality images that slow the
page render. The value can be measured in Page Render Speed using appropriate Performance
Analysis tools and techniques.
To configure the Progressive Image Rendering Treatment

1. From a treatment set, select Rapid Rendering.
2. Select Enable Progressive Image Rendering to enable it.
Note: To view the specific Progressive Image Rendering parameters, the Display Settings (at
the top of the pane) must be set to Advanced.
Table 31: Progressive Image Rendering Options
Apply to Landing Pages Enables this feature for landing pages or non-landing pages, as
Apply to Non-Landing Pages appropriate. Each option includes the following sub-options:
• Maximum Inlined Images—The maximum number of
images to which to apply the treatment. “0” value defers all
images to load last. “-1” value treats all images on the page.
• Maximum Inlined Bytes—The maximum size an image can
be applied for treatment. Images larger than this are ignored.
• Compression Quality—Compression quality for JPEG images.
Increases this value to get higher quality images (larger load).
Defer Images Too Large to be Select to defer images that are too large to be inlined.
Inlined
Defer Secondary Images Select to defer images removed by the LCD.
(Images Removed by LCD)
Delay to onload Allows a slight delay before loading high-quality images.

Testing
This treatment can be verified as working using some of the following techniques:
• Preload Files, page 122
• Visual Representation, page 122
• Inlined Resources, page 122
Before beginning, always ensure your page is being accelerated.
Note: If you can view response headers in your Web browser, ensuring the X-SL-CompState header
has an appropriate value ensures that your page is being treated.
Preload Files
This treatment uses files that allow additional resources to download after the page render.
Identifying these files can indicate that this treatment is working:
• slhead.js—This file is the initializer for the slpir.js file.
• slpir.js—This file causes post-render actions and resource fetching to occur.
• i-js.js—This is a consolidated image file. Although used by other techniques, finding this below
the page render time indicates loading by this treatment.
• Image Files—The full quality image resource is loaded after the Page Render. Other
treatments, such as Predictive Browser Caching can also cause this to occur.
Visual Representation
The most obvious indication that this treatment is working is to notice a lower quality image
displaying on your page while it is loading, to be replaced by a higher quality image when complete.
Unfortunately, depending on many factors such as page size and network connection speed, this can
sometimes be hard to visually identify.
Inlined Resources
The Progressive Image Rendering treatment uses a dataurl technique to provide the initial images to
your page. This replaces the images on your page with an image inlined directly into your page
using base64 encoding. Seeing these replacements could mean the treatment is working. Be aware
that other treatments also use this technique.

The resources loaded after page render still have all other applicable treatments applied to them.
If the Image Consolidation treatment is enabled, this treatment loads consolidated i-js.js files if
possible instead of individual image files. This is important to note when using tools to identify the
resources loading after page render.
Image Compression can be disabled on images loaded after the page render in the Advanced
Display Settings of this treatment. This overrides the Image Compression treatment.
Other treatments and features also use the slhead.js file. This includes Performance Analytics and
Predictive Browser Caching. The slhead.js file displays when using these features even if you are not
using the Progressive Image Rendering treatment.
Touch Event Conversion (Mobile only)

This treatment automatically converts click events to touch events, which relieves the mobile
browser of the real-time overhead of the click-to-touch translation, providing faster user experience.
Note: This treatment is available only to Mobile treatment sets.

Configuration
Use this procedure to configure the touch event conversion.
To configure the Touch Event Conversion Treatment

1. From a treatment set, select Rapid Rendering.
2. Select Enable Touch Event Conversion to enable it.
Figure 47: Touch Event Conversion
Table 32: Response Headstart Options
Click Event Threshold The time (in milliseconds) needed to count a touch as a click.
Time
Output Cache
When the Output Cache treatment is enabled, FastView monitors resources being requested from
FastView. If resources are requested often and consistently, they are stored in FastView's Response
Cache. When future requests for these resources occur, FastView delivers the resources from its
cache, rather than connecting to the back-end Web server. This reduces load on the Web server and
increases response time to the client.
Note: Output Cache treatment settings are disabled for mobile treatment sets because they must
always use the same settings as the desktop settings.
Occasionally, after serving a requested resource from cache, FastView also requests the resource
separately from the back-end Web server. This is done so that FastView can verify the resource has
not changed, or invalidate it if it has.
Output Cache does not cache text or HTML by default. If you want to cache text or HTML, use the
Optimized HTML Caching feature of a Web Applications Classification Rules.
The Output Cache Treatment is of great value when the content of a site, or portions of content on a
site, are considered relatively static. The value of this benefit is determined by how much load your
Web servers have to support serving this content, as this both reduces load off the origin Web
servers and saves the potential round-trip and latency time to fetch those resources.

To configure the Output Cache Treatment

1. From a treatment set, select Output Cache.
Figure 48: Output Cache Configuration
2. As Output Cache is a separate category in the treatment sets, there are no checkbox options to
enable or disable this treatment. Ensure that this pane is enabled and the treatment is available
in this set.
Table 33: Offline Cache Configuration Options
Caching Strategy Sets default settings in the User Interface for this treatment.
Number of Identical Responses The number of times a page must be hit and seen as identical
before it is cached by the Output Cache treatment. This is affected
by the Look for Response Consistency Across Sessions
option.
Cache Expiry Timer The time in seconds that must pass before the Output Cache
Treatment expires a resource. An expired resource is fetched
directly from the Web server again on the next request. This
ensures that content is refreshed in the output cache.
Observe server's headers for Select to observe server's headers for expiration, if present.
expiration, if present

Table 33: Offline Cache Configuration Options (cont.)
Look for Response Consistency When the Output Cache treatment defines a page as being
cacheable, one of the options that it checks is that it has been
requested from multiple clients. The reason for this is that a single
page may be the same for the same client, but different for other
clients. To ensure this, enable this option so that each “identical
response” must come from a different client request.
Enable Offline Compression Causes the content cached by this treatment to be compressed.
This allows for resources that are requested from cache to respond
with a compressed version (if the request header allows for a
compressed response).
Contents compressed in cache are compressed in the background
after the original item is already cached. This can cause several
non-compressed responses to an item before the compressed
version is ready to be served from cache.
Compression Level If Offline Compression is enabled, this is the level at which
resources are compressed.
Content Types The content types that are cached using this treatment. Add or
remove content types from this list, as required.
Note: HTML should not be cached through this treatment, as you should only cache treated pages,
and this treatment caches all content flowing through FastView. To cache HTML content, use the
Optimized HTML Caching option in a Web application's Classification Rule.
Flushing
Output Cache resources can be flushed from FastView to clear out resources. Output Cache is not
the only thing that gets cached on FastView and should not be confused with Instructions (compiled
pages). An instruction identifies how a page is treated and can also remain cached on the appliance
for a short period of time. This informs the client browsers which resources to load. If you are going
to flush the output cache, ensure that you actually need to flush the resources FastView is serving,
and not the treated page informing your clients which resources to fetch.
Testing
A resource going through the Output Cache treatment receives a header of X-Strangeloop =
RCache. A resource that is served from Output Cache receives a header of X-SL-RCache = Cached.
These should help to easily identify that a file is coming from response cache, or is being examined
as a response cache potential.
You could also verify that the number of hits to your back-end origin server are also reduced.
If you suspect that dynamic resources are being cached, there are easy ways to control this with the
appropriate configuration settings:
• Change the Static Response Threshold of Output Cache to a higher value.
• Ensure Look for Response Consistency Across Sessions is enabled.
• Set up an exclusion filter to exclude the known dynamic resource.

All resources requested through FastView can be cached if they match the configuration rules. This
includes resources treated by other treatments.

In addition to being affected by other treatment, Output Cache is affected by the expiration of
Resources in the Output Cache. Resources on the Web server are polled by the Output Cache when
they are requested after a certain period (default 900 seconds). This polling helps Output Cache
ensure that the resource has not changed, and helps to update the Invalidation Mechanism for other
treatments.
Payload Reduction
The Payload Reduction treatment sets include the following:
• ViewState Removal, page 126
• Dynamic Compression, page 127
• Image Compression, page 129
• JavaScript Minification, page 131
• CSS Minification, page 132
To edit the Payload Reduction treatment parameters

3. Select the Payload Reduction tab.
ViewState Removal
Ordinary HTTP is stateless: the client requests a page and the Web server serves it without
reference to any previous interaction. ASP.NET technology is more interactive. The viewer can
change objects on a page and the page “remembers” its viewing state. For example, a shopper can
sort a list of items in a table according to the price column and have the same sort order appear
after refreshing the page. This information is recorded as View State information.
As the content of a Web site grows, View State information can become very large. In some cases, it
can comprise as much as half the data of a Web page. In situations where bandwidth is limited, this
can cause slow Web pages and can be difficult to diagnose because the amount of View State
information for the page can only be seen by inspecting the source of the ASP.NET page.
The Web server needs View State information to format the page, but the client browser does not.
The View State treatment removes the View State content in a requested Web page, and replaces it
with a token. This token is sent to the client instead of the entire original View State content. The
result is a much faster page load with lower bandwidth consumption. The actual amount of benefit
provided by View State removal depends entirely on the amount of ASP.Net controls used by your
Web application, but in complex implementations can provide substantial benefit.
The View State Removal treatment is of greatest value in low-bandwidth scenarios, such as a dial-up
modem. However, if View State has become sufficiently large, it also help in higher bandwidth
situations. The treatment itself lowers bandwidth consumption, and in turn causes pages to load
faster for the client.
Note: View State Removal is only useful for Web servers that use View state tokens. If you are not
using one of these types of servers (IIS using ASP.Net), using this treatment has no benefit.

To configure the Payload Reduction Treatment

1. From a treatment set, select Payload Reduction.
2. Select Enable ViewState to enable it.
Figure 49: ViewState Removal Configuration
Table 34: ViewState Removal Configuration Options
Expiry Timeout The time in seconds that the View State and tokens are stored in
FastView. This should be the same value as the session timeout value on
the Web server.
Treat Ajax Responses Enables treating Ajax responses.
Testing
If the View State Treatment is working, you see the View State content header on your Web page. In
addition, when looking at the source of the HTML, you see a 13-digit token in place of the original
view state.
A page must have a content type of text or HTML for this treatment to apply to it, and must have a
view state tag in the following format:
<input type= name__VIEWSTATE= id__VIEWSTATE= value= >

View state removal does not directly interact with any other treatments.
Dynamic Compression
For FastView to treat the traffic provided to it from the Web server, it must decompress any
information sent to it. The Dynamic Compression treatment instructs FastView to allow the
recompression of resources provided to the client. The exact method of compression is determined
by the client's Accept-Encoding Header.
This compression yields a smaller payload, resulting in faster download times. Dynamic compression
provides a significant benefit to any application, reducing traffic and improving performance. It can
be used whenever the browser is compression-capable.
Radware recommends that this treatment is always enabled. This acts as a replacement for the Web
server's compression options, as FastView must decompress all data coming from the Web server in
order to treat it.

The Dynamic Compression Treatment respects the Accept-Encoding header from the client, and
performs compression using one of the following methods, in order from preferred to least
preferred:
• gzip
• deflate
• no compression
The Compression Treatment is of greatest value in low-bandwidth scenarios, such as a dial-up

modem.
To configure the Compression Treatment

2. Select Enable Compression to enable it.
Figure 50: Compression Treatment
Table 35: Compression Options
Compression Level The compression level to use for this feature. Higher compression results
in a lower amount of bandwidth required for data, but also results in more
processing time by the client and server to compress or decompress
resources. This value is independent of the Compression setting for
Output Cache.
Content Types The list of content types that the Compression Treatment can be applied
to. You can add or remove content types as required.
Testing
If the Compression Treatment is working, you see a content-encoding header in your resulting
resources.

Compression may act upon any treated file.

Image Compression
Images are currently single largest factor in the size of Web pages. Image Compression is the
method of compressing images before they are sent to the client. This reduces the amount of data
transferred over the network. The image Compression Treatment automatically compresses images
using a lossless compression technique for PNG and GIF files. By this method, each image resource
is reduced as much as possible in size without losing quality. In addition to this, the Compression
Treatment is further used to provide a smaller payload, resulting in faster download times. Image
compression provides a significant benefit to any application with images that are not already
compressed, reducing traffic and improving performance for all applications. It can be used even if
the client browser is not compression-capable, as it compresses the actual image itself.
The Image Compression treatment saves bandwidth by compressing images to smaller size. This
results in faster response time to client browsers.
For mobile devices in particular, given the smaller screen size, it is unnecessary to send full-size
images to mobile users. FastView resizes images, making image files at least 20% smaller,
significantly reducing page size and payload.
To configure the Image Compression Treatment

2. Select Enable Image Compression to enable it.
Figure 51: Image Compression Configuration - for Desktop

Figure 52: Image Compression Configuration - for Mobile
Note: To view the specific Image Compression parameters, the Display Settings (at the top of
the pane) must be set to Advanced.
Table 36: Image Compression Options
Enable Lossy For most image types, lossless compression is used. For JPEGs, you must
Compression enable lossy compression.
Progressive Encoding Select the progressive encoding mode.
Values:
• Auto—Use the smallest
• On—Always interlaced JPEGs
• Off—Not interlaced

Table 36: Image Compression Options (cont.)
GIF/PNG quality Defines the quality of the GIF or PNG graphic.
• Recompress quality (%)—Percentage to re-compress GIFs or PNGs
when lossy compression to JPEGs.
• Quantization threshold—Used to reduce colors used in the image.
JPEG quality Defines the quality of the JPEG graphic.
• Reduce quality (%)—The percentage by which to reduce the JPEGs
(compression percentage).
• Maximum/Minimum quality (%)—Maximum/minimum end
percentage after compression.
Testing
To determine that the Image Compression Treatment is working, compare the file size of the original
image resources to the file size of the new image resources. The new resources should be smaller.
Not all images can be compressed, or may be compressed to larger sizes than the original. In this
case, the original file is left untouched and a non-compressed version is provided.

Image Compression works with Browser Cache Invalidated and Image Consolidated files. However,
the Progressive Image Rendering acts independently of this treatment, and provides additional
image compression regardless of enabling the Image Compression Treatment.
JavaScript Minification
JavaScript Minification acts upon JavaScript files by doing everything possible to make the file
smaller. This includes such things as removing whitespace, removing comments, and other
arrangement techniques. The resulting JavaScript file is generally much smaller, but also harder to
read. Variable obfuscation or renaming is not performed.
This treatment helps by reducing the size of the resulting JavaScript file sent to the client, reducing
bandwidth consumption, and increasing response time. The benefit is that the original file on the
Web server remains unmodified, letting Web site administrators modify the file as needed.
To configure the Java Minification Treatment

2. Select Enable JavaScript Minification to enable it. There are no other configuration options
for this treatment.
Testing
To see if the JavaScript Minification Treatment is working, view the contents of the JavaScript files on
the client. The content should be compressed into a format that wastes as little space as possible.
Occasionally, treatments such as JavaScript Consolidation and JavaScript Minification have
unpredictable results on these scripts. If a particular JavaScript is found to be producing errors after
applying these treatments, exclude the file from the treatment in the Web Application Exclusions.
This often occurs with files that have already been minified by your Web Server, meaning that any
file ending with .min.js is already excluded by default.


JavaScript Minification acts upon any previously treated JavaScript file. Consolidated JavaScript files
can be minified for additional benefit.
CSS Minification
CSS Minification acts upon CSS files by doing everything possible to make the file smaller. This
includes such things as removing whitespace, removing comments, and other arrangement
techniques. The resulting CSS file is generally much smaller, but also harder to read.
This treatment helps by reducing the size of the resulting CSS file sent to the client, reducing
bandwidth consumption, and increasing response time. The benefit of this is that the original file on
the Web server remains unmodified, letting Web site administrators modify the file as needed.
To configure the CSS Minification Treatment

2. Select Enable CSS Minification to enable it. There are no other configuration options for this
treatment.
Testing
To determine that the CSS Minification Treatment is working, view the contents of the CSS files on
the client. The content should be compressed into a format that wastes as little space as possible.
Occasionally, treatments such as CSS Consolidation and CSS Minification have unpredictable results
on these scripts. If a particular CSS is found to be producing errors after applying these treatments,
exclude the file from the treatment in the Web Application Exclusions. This often occurs with files
that have already been minified by your Web Server, meaning that any file ending with .min.js is
already excluded by default.

CSS Minification acts upon any previously treated CSS file. Consolidated CSS files can be minified for
additional benefit.
Search and Replace

You can use the Search and Replace treatment to search for content on pages and replace it with
other content. This is mostly used for the deferral of images and scripts by replacing the content
with scripts that load information post render.
This treatment technique is of high value on sites that can defer loading of data to post render. This
is especially true with blocking JavaScript that does not need to come before render, analytics
beacons, or third-party resources.
To configure the Search and Replace Treatment

> From a treatment set, select Search and Replace.
Note: Currently, you cannot configure the Search and Replace feature through the Web
Management Interface. Contact Radware Technical Support if you want to use this feature.

Figure 53: Search and Replace
Testing
You can best verify this treatment by reviewing a page waterfall using a remote testing tool. The
resources that should be deferred should come after the post render line. You can also view the
source page to see the actual replacement of the values as you set them.

This treatment is applied after consolidation. Resources that are deferred by this treatment should
be excluded from the appropriate Image, JavaScript, or CSS Consolidation treatments.
Templated Deferrals
This treatment provides a simple way to defer specific types of resources: images, iFrames, and
JavaScript (inline and external).
Note: To view the Templated Deferrals, the Display Settings (at the top of the pane) must be set to
Advanced.
To configure the Templated Deferrals Treatment

1. From a treatment set, select Templated Deferrals.
Figure 54: Template Deferrals

Table 37: Templated Deferrals Options
Enable these types of Select any of the following deferrals:
deferrals • Image Deferrals
• iFrame Deferrals
• External Script Deferrals
• Inline Script Deferrals
Enable these Select any of the following deferrals:
replacement modes • Compiled Deferrals
• Dynamic Deferrals
Note: If a more granular deferral configuration is required, you can configure individual deferrals in
the Deferrals section of the selected Web application at Acceleration > Web Applications.
Long-Tail Site Acceleration

Long-tail site acceleration provides an efficient mechanism for accelerating long-tail Web sites. A
Long-tail site is a site that has a few pages that are very frequently visited, as well as a very large
number of pages that are visited very often.
This feature ensures that the most popular pages on a site (those with the highest number of page
views) receive the best performance acceleration, while a generic fallback template is used to
accelerate pages that are rarely visited.
FastView continuously monitors visited pages to determine which pages are popular at any given
time. For the popular pages, specific instruction sets are created. For the less popular pages,
FastView automatically creates preload lists that include common elements that can be preloaded to
provide an optimized site visit.
The configuration file includes a createGenericInstruction attribute that can be enabled or
disabled, and two parameters that define the required frequency to determine if a page is popular or
not. The frequency is determined by the number of unique page views within a certain amount of
time.
These two attributes are:
• uniqueViewCaptureThreshold specifies the number of unique views required for FastView to
create a page specific acceleration. The default is 1, which means Long-tail site acceleration is
not used. Using a higher value implies FastView waits until multiple unique views are seen
during the specified timeout before it captures the response and sends it to the compiler to
create the unique instruction set.
• uniqueViewTimeoutSeconds specifies the time in seconds during which page views are
counted to meet the specified threshold. The value of this attribute defaults to 0, which disables
this check and considers all pages hits to count as unique views.
To configure long-tail site acceleration

2. In the XML file, search for “createGenericInstruction”.
3. Change the value to “true”.

4. Search for “uniqueViewCaptureThreshold”.

5. Edit to the value required for your specific site policy.
6. Search for “uniqueViewTimeoutSeconds”.
7. Edit to the value required for your specific site policy.
Note: The configuration is available only in the XML configuration file, and not in the Web GUI.


Examining Appliance Health
Chapter 8 – Examining Appliance Health

It is important to ensure that your appliance is healthy and functioning as expected. There are many
ways that you can do this. Some of these are simple notification methods that inform you what is
going on in the system and let you do further investigation if required. These include:
• Status Messages, page 137
• Web Management Interface Overview Page, page 139
Other methods require you to do a little work searching for the information you want. These include
things like recording and analyzing system traffic or reviewing logs:
• Packet Capture, page 139
• Event Logs, page 140
• Diagnostic Summary, page 144
• Examining Appliance Treatment, page 147
Along with all these investigative features you can use in FastView, there are many things you can
do to ensure that your system is running appropriately every day. These include setting up
monitoring tools for both your virtual servers and the Web Management Interface, and checking that
your pages are being treated as you expect.
Status Messages
Status messages are issued when FastView detects anything that seems out of order. This can range
from memory issues to not having the DNS configured. Each error or warning that is issued is
recorded and displayed using the following methods:
• Banners, page 137
• System Status Messages, page 138
• System Health, page 138
• CLI Banners, page 139
Banners
Banners are located on the Web Management Interface Overview Page. The System Status field
indicates if any errors or warnings may be considered critical.
Figure 55: Banners

Important messages have links to the Status Messages pane, which may provide further
information.
System Status Messages

Important system status messages are listed in the System Status Messages pane.
To access the System Status Messages pane

> Navigate to Appliance Management > Maintenance > System Status Messages.
Figure 56: System Status Messages
System Health
The System Health pane contains all information that FastView considers as warnings or errors
concerning its daily functions, but may not necessarily be important enough to notify users.
Occasionally reviewing this list may identify continuing issues with your system.
For example, if a specific virtual server is unreachable during a single ping, this may not be enough
to be considered a problem. However, if continued problems occur, some investigation may be
required. Any messages here that are considered of critical importance are also displayed in the
Status Messages pane.

To access the System Health pane

> Navigate to Appliance Management > Diagnosis > System Health.
Figure 57: System Health
CLI Banners
When you log into the Command Line Interface (CLI), if there are any important System Status
Messages, these are displayed upon login.
Figure 58: CLI Banners
Web Management Interface Overview Page

The Web Management Interface Overview Page can give you a quick overview of FastView. It is a
series of panes that provide information that represent the health of your system. For more
information, see Web Management Interface, page 63.
Packet Capture
Packet captures let you capture data, download the package to your local computer, and examine it
using proper inspection tools. This lets you inspect how traffic is flowing through your appliance on
the network and to identify any problems you may be encountering.

Note: The Packet Capture feature is unavailable if you enable the FastView PCI Compliance
features.
To start a packet capture

1. Navigate to Appliance Management > Maintenance > Packet Capture.
Figure 59: Packet Capture
2. Select either Capture all traffic, or Capture traffic on specified virtual servers. For
specified virtual servers, add them to the Virtual Servers to Capture list.
3. Click Start Capture.
Note: On high-volume Web sites, this can consume a lot of disk space. Radware recommends only
performing short captures in these cases.
When you are finished capturing traffic, click Stop Capture.
Event Logs
This feature allows you access to the event logs stored on your appliance. Event logs let you
examine the system logs to determine if there are errors occurring, and help you determine if there
are problems with fetching resources, compiling instructions, or serving pages.
Note: Event logs are not available using FastView Cloud Service.

To access the event logs

> Navigate to Appliance Management > Logging.
• Selecting Individual Logs
• Searching Logs
• Generating Support Packages
• Reading the Event Logs
• Log Rotation and Deletion
Selecting Individual Logs

Events logs are split up into two sections: individual logs, and log directories
Individual Event Logs

Selecting any of these log files loads the log into your browser for review.
Figure 60: Individual Event Logs
The following are options for navigating the log directory:

• Log Search—Searches through existing logs to look for keywords.
• Generate Support Package—Generates a support package that you can download for sending
to Radware Technical Support for assistance. A support package contains information about your
event logs and your configuration. It may takes a short while to generate. The support package
will be automatically downloaded to the default download location on your local machine.
Searching Logs
You can search through the logs using the Log Search feature.

To search the logs

> Select Log Search under the Log Directory.
Figure 61: Searching Logs
If you are searching for specific events, you can easily filter your searches. A common search would
be to select all log files in the search and search for the word “ERR”. This quickly shows if there are
any errors occurring while fetching or serving resources. Often these give detailed information about
resources being unavailable, or provide the log filename that is relaying the problem, so that you
can read it in full using the directory selection method mentioned.
Generating Support Packages

Support packages contain a consolidated version of the logs on your system, as well as configuration
and system information. The support package can be provide to Radware Technical Support when
requesting support assistance.
To generate support packages

1. Navigate to Appliance Management> Logging.
2. In the Event Logs section, click Generate support package for download.
3. The support package will be generated and download to your local default download location.
This may take a while.
Log Directories
You can navigate the appliance log directory. Individual Web applications continually rotate the
event logs on the appliance.

Figure 62: Navigating to the Log Directory
The Reset Directory Listing option takes you back to the root of the event logs directories if you
have been navigating through it.
To see logs specific to a Web application,
drill down into the appropriate WebApp_# folder associated with your Web application. The following
event log file types are listed in the log directory:
• GPG files—Support packages downloadable for e-mailing to Radware Technical Support.
• LOG files—Standard readable log files. Inspecting these opens the contents of the file to be
examined.
• GZ files—gzipped versions of older log files. These can be downloaded for extraction and
viewing.
• Folders—Folder than can be drilled-down into to inspect the various parts of the appliance.
Only critical or important information is provided in these logs and they are not complete overviews
of traffic flowing through the appliance. For that kind of HTTPS access logging, Web logging should
be used on your individual servers.
Reading the Event Logs

When you open the event logs, there is a lot of information in them that may not be not clear. If you
need assistance, contact Radware Technical Support or search the Radware Knowledge Base.

Log Rotation and Deletion

Logs automatically rotate and older log files are compressed. If you need to see older log files, you
must download and extract their contents. In addition, files in the log directory are also deleted
when they become too old. All logs are kept for 60 days before deletion. This is done as part of the
rotation.
Diagnostic Summary
The Diagnostic Summary displays an overview of the state of a selected Web application. It displays
how much traffic is flowing through FastView and how many treated pages are being served.
To access the Diagnostic Summary pane

1. Navigate to Appliance Management > Diagnosis.
This pane is split into three sections:
— Optimization Status, page 144
— Workload Monitor, page 145
— Legend, page 146
2. To refresh the Diagnostic Summary, either collapse and re-open the pane, or click Refresh.
Optimization Status
The Optimization Status displays the following information:
Figure 63: Optimization Status
• Optimization by Instruction, page 144

• Optimization by Page View, page 145
• Settings, page 145
Optimization by Instruction
This displays the various instructions that are being treated by FastView. An instruction in a unique
view of a Web page (by unique Web browser client and page compile type). For example, “/
home.aspx” viewed by Internet Explorer 7 browsers as a non-landing page would create a single
instruction.
Each instruction can be in one of the following states:
• Queued—The instruction is being served untreated. FastView is ready to process the instruction
for treating, but it is currently in a queue.
• First Compile—The instruction has been served treated, but FastView has only seen the page
once. It is still going to process the page for learning how to provide instructions.

• Learning—The instruction is being served treated, but FastView is still learning how to treat the
instruction. The next time FastView serves the page, it may be treated differently depending on
how the next few unique browsers request the instruction. This continues until the Compiled
threshold (number of same unique views) occurs.
• Compiled—The instruction has been requested enough times (defined by unique page views
that are the same) that it considers the page in a Compiled state. It will not continue to process
the page until it goes through a touch-up or recompile.
• Touchup—The percentage of instructions that are in the Touchup state. This indicates that the
instruction will still be served, but FastView will examine the next request to the instruction to
ensure that everything is still valid.
• Recompile—Instructions in the Recompile state have expired. A request to the instruction
causes it to go into a Learning state again.
The graph indicates, by percentage, where the instructions are in the system. For detailed
information on a specific instruction, see Instruction Lists, page 159.
Optimization by Page View

This displays the status of unique views rather than instruction states. It contains the following:
• Unaccelerated—The page viewed was unaccelerated.
• Learning—The page viewed showed to the client as accelerated, but FastView was still learning
the best way to treat the page.
• Accelerated—The page served to the client was accelerated by FastView.
The Optimization by Page View is a cumulative view of each unique request to a page. The following
workflow should illustrates how values would appear in this section:
1. Person A browses to home.aspx. 100% of page views should show in the Unaccelerated state.
2. This is followed by Person B and Person C to the same page. Each of these users add to the
“Learning” state. This results in 33% Unaccelerated and 66% Learning.
3. Person D now hits the same page. However, the page had a compile threshold of three unique
views which was met in the previous step. This client now adds to the Accelerated state. This
results in 25% unaccelerated, 50% learning, and 25% accelerated.
Settings
This section indicates the current FastView settings. These values are generally not configurable:
• Compile Threshold—The number of unique page views that must be requested of an
instruction before it can go into the Compiled state.
• Touch Up Interval—The number of minutes that FastView waits per compiled instruction
before it re-examines it for the next request. This value is the starting value for the Touch-Up
Interval and is on a sliding scale. The more static the instruction is found to be, the longer the
next touch-up interval takes.
• Recompile Interval—The number of minutes that FastView waits per compiled instruction
before it throws the instruction away and performs full recompile.
The Touch-Up Interval, Recompile Interval, and Invalidation help to FastView recognize changing
data on your Web server after the initial instruction compilation has occurred.
Workload Monitor
The Workload Monitor displays the amount of processing FastView is currently performing.

Figure 64: Workload Monitor
The the Peak, Current, Average, and Total values for the following rates are displayed:
• Request Rate—The number of unique pages requested through FastView. This provides a
Pages Per Second (pps) view of your traffic.
• Parse Rate—The amount of information that FastView has looked at for potential replacement
in a page. Any rewriting (such as replacement tokens, URL renaming) is considered and given in
tokens per second/minute (tkps/tkpm).
• Rewrite Rate—The amount of information that FastView actually acts upon when replacing
data in Web content served. This is also given in number of tokens per second/minute (tkps/
tkpm).
• Compile Rate—The number of instructions compiled by FastView. As pages eventually stop
being compiled after they pass the learning state, this number should increase greatly when
your site is first started or modified, and slowly as FastView learns how to provide the treated
pages.
Legend
The legend describes the various colors and acronyms used in the graph.
Figure 65: Legend

Examining Appliance Treatment

This section describes how to verify that FastView is treating resources. It includes various methods
to identify treated resources, how resources are treated, or why they are not being treated as
expected.
If you want to know the details about an individual treatment and how it is affecting your resources,
see the specific treatment under Defining Treatment Sets, page 97.
• Parameters, Headers, and Cookies, page 147
• Treatment Files, page 153
• Debug Pages, page 155
• Resources Not Treating, page 156
• Instruction Lists, page 159
• Resource Library, page 162
• ETag Volatility Report, page 163
Parameters, Headers, and Cookies

As part of the treatments that FastView provides, additional headers and cookies may be found on
resources and Web sites. In addition to this, new parameters can be used to initiate certain
functionality within FastView.
The following is a consolidated list of these parameters, headers, and cookies, and how they affect
your optimized Web Site:
• Parameters, page 147
• Content Headers, page 149
• Cookies, page 152
Parameters
The following parameters can be appended to a page URL on your treated site. Each parameter
functions in the specific way as indicated.
• L00p, page 147
• Sllp, page 148
• Slpbc, page 148
• Slpir, page 148
• Sldef, page 148
• Invalidate, page 148
• Capture, page 149
• PrintCompileInfo, page 149
• PrintInstruction, page 149
L00p
The ?l00p= parameter can be appended to your URL to force a page to display as treated or
untreated. This lets you easily compare a treated page or resource to its untreated counterpart. It is
also useful if you do not have 100% segmentation set, and want to see what different users are
receiving without being randomly set into a segmentation group.

Table 38: L00p Flags
Flag Description
?l00p=on Forces the page to be in an treated or accelerated state.
?l00p=off Forces the page to be in an untreated or unaccelerated state.
?l00p=reset Resets the cookie on your browser and fetches you a new cookie.
Setting this value manually affects your SL_Audience cookie.
Note: When using the ?l00p=on or ?l00p=off flags to manually set the segmentation cookie, this
cookie remains set until the client clears their browser's cookies. To set this back to the default, use
the ?l00p=reset flag.
Sllp
If a landing page is available for the page being requested, you can force the viewing of a landing
page or non-landing page using the ?sllp= parameter.
For this parameter to work, you must have landing pages enabled in the Classification Rules of your
Web application.
Table 39: Sllp Flags
Flag Description
?sllp=on Forces the page to be returned as a landing page. This is a one-time page setting
that does not persist without appending the flag.
?sllp=off Forces the page to be returned as a non-landing page. While this is also a one-
time page setting, unless cookies are flushed on the site, future pages viewed on
this site default to this value.
The parameter used affects your X-SL-CompState header on a page.
Slpbc
The ?slpbc=off parameter causes Predictive Browser Caching scripts not to run on the client
browser. The files to load Predictive Browser Cache files are still loaded to the client, but do not
execute.
This parameter is very useful when running tests such as Gomez that take into consideration post-
render resources that do not actually affect user experience. For this parameter to have any effect,
you must have the Predictive Browser Caching treatment enabled.
Slpir
The ?slpir=off parameter causes the high resolution images for Progressive Image Rendering not
to load.
Sldef
The ?sldef=off parameter causes that the deferred elements of the page are not executed.
Invalidate
The ?invalidate=1 parameter causes FastView to force invalidation of a Web page instruction.
This causes the page to recompile and serve any new content.

Invalidation occurs automatically within FastView unless it has been disabled in the Web application.
However, this option forces the page to become invalid without the required time to elapse, allowing
you to refresh a page immediately.
The invalidate parameter is enabled by default, but you can disable this feature.
To disable the invalidate parameter

2. Search for “ExplicitInstructionInvalidation”.
3. Set the value of enabled=”false”.
Capture
FastView typically compiles Web page instructions in the order that they are requested. However,
sometimes for testing purposes it is important that a page be pushed to the top of the compile
queue. This can be done using the ?capture=1 parameter. This parameter is enabled by default but
can be disabled so that malicious users cannot force all their pages to go to the top of the queue.
To disable the capture parameter

2. Search for “ExplicitInstructionCapture”.
3. Set the value of enabled=”false”.
PrintCompileInfo
The ?printcompileinfo=1000 parameter lets you see the individual resources and how they are
treated on a page. This is a very powerful feature that lets you drill down into resources that you
suspect are not being treated correctly.
This feature is only available if Debug Logging is enabled. For more information, see Debug Pages,
page 155.
PrintInstruction
The ?printinstruction=1000 parameter lets you see how a Web page on your site was modified
to include treated resources. This is a useful feature to determine which substitutions were made
from the original untreated page.
This feature is only available if Debug Logging is enabled. For more information, see Debug Pages,
page 155.
Content Headers
The following Content Headers can be modified or added by FastView. There are two types of
content headers:
• Headers Sent to the Web Client, page 150—These are headers that FastView appends when
sending Web page data to the client
• Headers Sent to the Web Server, page 151—These are headers that FastView appends when
sending Web page data to the back-end Web servers.

Headers Sent to the Web Client

This section describes the unique content headers that can be sent by FastView to the client They
can be seen by inspecting your resource content headers using a Web Inspection tool. They include:
• X-Strangeloop, page 150
• Cache-Control, page 150
• Expires, page 150
• X-SL-RCache, page 150
• X-SL-CompState, page 150
• Server Header, page 151
X-Strangeloop
Applies to: Resources, Pages
Treatments: Browser Cache Expiry, View State, Output Cache, Compression
This header indicates that resources have undergone certain treatments:
• CacheControl indicates Browser Cache Expiry was applied
• ViewState indicates ViewState was applied to page
• Compression indicates Compression was applied
• RCache indicates the resource was treated by output cache, although it may not have come
necessarily from the output cache on this appliance
• DCache indicates that a page has Browser Side Includes applied
Cache-Control
Treatments: Browser Cache Expiry, Optimized HTML Caching
This is a standard Expires expiry header and contains the value [date + Browser Cache Expiry time].
This value can exist on non-treated resources as defined by your Web server. However, it can also be
set by the Browser Cache Expiry or Optimized HTML Caching treatments as specified by the Cache-
Control header.
Expires
Treatments: Browser Cache Expiry, Optimized HTML Caching
This is a standard Expires expiry header and contains the value [date + Browser Cache Expiry time].
This value can exist on non-treated resources as defined by your Web server. However, it can also be
set by the Browser Cache Expiry or Optimized HTML Caching treatments as specified by the Cache-
Control header.
X-SL-RCache
Treatments: Output Cache, Optimized HTML Caching
Seeing this header with a value of cached indicates the resource or page came from FastView's
resource output cache.
X-SL-CompState
Applies to: Pages

Treatments: All
This header contains the following information about the requested page:
• A text string indicating the page has been treated by FastView treatments (at least one valid
treatment must be applied to see this header). The header indicates which state the page is in:
— Uncompiled—Indicates the page has not yet been compiled by FastView and the untreated
version is still being returned.
— First Compile—Indicates the page has been compiled and should return the treated page.
However, the page still goes through further compilations with other users to ensure that the
content is not changing and to “untreat” content that is changing.
— Learning—For each new visitor that arrives at the page, FastView continues to examine the
page until it sees enough unique visitors that it puts it in a fully compiled state.
— Compiled—Indicates the page is fully compiled and returning treated pages.
— TouchUp—Indicates the page has reached an expiry where it is being partially recompiled
to ensure resources have not changed. The treated page is still served in this state.
— Recompile—Indicates the page has reached an expiry where it is being fully recompiled to
ensure resources have not changed. This state only occurs about once a day.
• A # value indicating if the page received was a landing page or not:
— 0—Represents a non-landing page
— 1—Represents a landing page
Server Header
Applies to: Resources
Treatments: All
This header contains the following information about the requested page:
• A value of SLRS for any resource from the server, including includes ALL Aliased resources and
any unalaised PerfectImage resources.
Headers Sent to the Web Server

This section describes the unique content headers that can be sent by FastView to the Web Server.
They include:
• X-Cluster-Client-IP, page 151
• X-Forwarded-For, page 151
X-Cluster-Client-IP
Value: IPAddress
This passes to the Web server the original Client IP address. This is because FastView acts as a
proxy and masks the Client IP address. Because any proxies in front of FastView may mask the
client IP address for their own, Radware recommends that you use X-Forwarded-For instead. To use
this header on the Web server, you must install a proper ISAPI module or filter.
X-Forwarded-For
Value: IPAddress
This passes to the Web server the original Client IP address and the proxies it went through. This is
because FastView acts as a proxy and masks the Client IP address. To use this header on the Web
server, you must installed a proper ISAPI module or filter.
This option is not enabled by default.

To enable X-Forward-For
2. Search for “xForwardedForEnabled”.
3. Set the value to “true”.
Cookies
FastView also provides cookies to the client for treated Web sites. This section describes the
following cookies:
• SL_Audience, page 152
• SL_UVId, page 152
• SL_ClassKey, page 153
SL_Audience
The SL_Audience cookie is used when segmentation is turned on. It identifies which traffic segment
the client browser is on and whether the page is treated or not for the client. The values are
delimited by a | and are in the order as presented in the following table:
Table 40: SL_Audience Values
Treatment After this random value is set, if the value is equal to the segmentation value
Segment (100% = 1000), the client is accelerated.
Values: 0–999
• If the value is manually set to -1, the client is accelerated.
• If the value is manually set to -2, the client is unaccelerated. You can also do
this by passing the parameter ?l00p=on/off to the page.
Treatment A text indication of whether the page is treated.
Applied
User Segment Reserved.
Web App ID The ID associated with the Web application on FastView.
Learning Mode A 0/1 value indicating if the page is in learning mode.
If the page is in learning mode, it treats the page as normal, but provides the
unaccelerated version to the client.
SL_UVId
The SL_UVId is a hash string generated to indicate a unique visitor on a site. It is not a Session ID,
but is instead used to inform the compiler when unique users are requesting pages for compiling
purposes.

SL_ClassKey
Indicates the Client Group a Web Client has been assigned to so that it can continue to get resources
from that group:
• First Value—Not used unless using CDN Edge Side landing pages
• Second Value—Landing page client group
• Third Value—Non-landing page client group
Treatment Files
While FastView mostly modifies existing resources and pages to accelerate Web traffic, it
occasionally needs to insert extra information to accelerate these pages. The following files can be
inserted by FastView:
• slhead.js, page 153
• slpre.js, page 153
• pdata.js, page 154
• cdata.js, page 154
• adata.js, page 154
• slpir.js, page 154
• x-img, page 154
• x-css.css, page 154
• x-js.js, page 154
• i-js.js, page 154
• mhtml.mhtm, page 154
• ?Lo0P files, page 155
slhead.js
The slhead.js file is the most common file you see inserted into most pages. It is the generic file that
preps and loads objects from many treatments and performance features. These include:
• Performance Analytics
• Predictive Browser Caching
• Progressive Image Rendering
• Templated Deferrals
If none of these features are enabled, the slhead.js file does not appear.
With Progressive Image Rendering and Predictive Browser Cache, additional files are provided that
contain instructions on how to load the resources.
slpre.js
This file is loaded when Predictive Browser Caching is enabled. It instructs the client browser how to
execute the preloading scripts.

pdata.js
This file is used for Predictive Browser Caching. It contains files that the treatment must download
specific to the page when Preload for Landing Page Consolidation Repeat Views is enabled.
The pdata.js file is unique for each compiled page on your site.
cdata.js
This file is used for Predictive Browser Caching. It is a list of files that the treatment must download
specific to a Classification Rule within a Web application. It is used when there are resources to
preload using either of the Application-defined Predictive Browser Caching options. A cdata.js file
can be called by many pages within a treated Web application, but is different for each page that
falls under a uniquely defined Classification Rule.
adata.js
This file is used for Predictive Browser Caching. It contains files that the treatment must download
specific to a target page when Automatically Preload from Page Transition Data is enabled. The
adata.js file is unique for each compiled page on your site.
slpir.js
This script is inserted if Progressive Image Rendering is enabled. It specifies the images that have
been reduced during your page load and require to be reloaded at full resolution after the page
completes.
x-img
The x-img.jpg/.png/.gif file is an image sprite file used in the consolidation of images. If you are
using the Image Consolidation treatment, some browsers take advantage of this and download x-
img packages for the consolidated image files.
x-css.css
If you are using consolidation treatments, some browsers take advantage of this and download an x-
css package for consolidated css files. This file replaces any consolidated css files.
x-js.js
The x-js.js file is a unique package that contains a consolidated package of JavaScript files. It is
used by the Consolidation Treatments. the file is loaded as post-render.
i-js.js
The i-js.js file is a unique package that contains consolidated file of base-64 encoded images. It is
used by the Progressive Image Rendering Treatment, the file is loaded as post-render.
mhtml.mhtm
If you are using the MHTML feature of the consolidation treatments, some browsers take advantage
of this and download an MHTML package. This may contain a package of css or JavaScript files. The
file replaces any css or js files it consolidated.

?Lo0P files
In addition to the files added by FastView, there are many files that are modified. Whenever a file is
modified to take advantage of caching internal to FastView, it is appended with a ?Lo0P=<md5>
parameter. This ensures that if the file has been modified, a fresh copy is fetched from FastView
instead of one already seen by the client's browser cache.
Debug Pages
When you enable Debug Pages, it provides some features that verify if and how treatments are
being applied.
To enable debug pages

1. Navigate to Appliance Management > System Settings > Global Settings pane.
Figure 66: Debug Pages
2. Select the Enable Debug Logging option to enable Inserted Debug Information, page 155.
Note: Radware recommends that you only enable this feature during testing.
Inserted Debug Information

When debug logging is enabled, comments are appended to the bottom of your Web page indicating
the status of your compilation and of FastView. This can be helpful during testing to ensure that the
pages are being treated and to gather additional information about FastView, such as the version.
Caution: Inserted debug information may cause issues on pages that do not use closing tags
properly. For this reason, Radware highly recommends that you do not keep debug logging enabled
in a production environment.
CompileInfo Pages
You can view how each resource on your page has been treated using the ?printcompileinfo
parameter. This is a useful way to not only see how resources were treated, but with what they were
treated, or if they were not treated for various reasons.

Note: CompileInfo Pages are enabled by default by Web App in the XML using the
<DebugPageEnabled value="true"/> key.
Instruction Pages
You can view how the page is replacing and including treated resources. This is done using the
?printinstruction parameter.
Note: Instruction Pages are enabled by default by Web App in the XML using the
<DebugPageEnabled value="true"/> key.
Resources Not Treating

Resources on a Web site can change, and may not be compatible with all treatments. There are a
range of features in FastView that help identify and exclude these resources. In most cases this
causes the resources to be served in their original untreated form.
There are a few primary methods by which resources can be identified, and each is handled slightly
differently:
• Invalidation, page 156
• Exclusions, page 157
• Non-Treatable Resources, page 158
If you have resources that are not being treated, any one of these methods could be the reason. If
you want to stop treating certain resources, you can use Exclusions. If you want to exclude entire
domains of resources to treat, try setting up some rules using treated domains.
Invalidation
If a resource changes during the learning, touch-up, or recompiling of an instruction, it may be
marked as a volatile resource and become invalid for treatment by FastView. If this occurs, the
resource remains untreated by a variety of treatments. However, FastView continues to inspect the
resource during these phases. After a period of time, if the resource is considered to have become
static again, it is again marked as non-volatile and becomes valid for treatment. In this manner,
resources that are not static (or have just been updated through manual processes) are identified.
Changing a resource a single time (such as an update to a server) may not necessarily mark that
resource as volatile, and it could be treated the next time the page is compiled.
A resource that has changed on the server is eventually treated and served with the new content.
However, depending on the recompile and touch-up cycle, you may want to force the site to re-learn
its instructions.

To force a page instruction to recompile with the newly altered resource

> Do one of the following:
— Use the invalidation parameter on the Web page (?invalidate=1)
— Flush the Web site instructions
Notes
• Use caution when selecting Flush Instruction. This flushes the entire site and causes FastView
to re-learn how to treat the site.
• If you have disabled Automatic Invalidation, pages do not invalidate resources on their own. If
you have done so, you must use one of the above two methods to cause your page to recompile
with the correctly updates resources.
Exclusions
Exclusions are one of many ways in which a resource can become untreated on a treated page. If
you want to investigate the other methods that cause resources not to be treated, review Examining
Appliance Treatment, page 147 on invalidation, Global Resource Management, and exclusions.
Exclusions lets you specifically exclude certain resources from treatment within an Web application.
Note: Exclusions exclude the treatment of resources, not Web Pages. If you want a Web page to be
excluded from treatment entirely, you must set up the appropriate Classification Rules.
• Purpose of Exclusions, page 158
• Identifying Problem Resources, page 158
• Non-Treatable Resources, page 158
Configuration
Each Web application has its own Exclusions pane.
To access exclusions
1. Navigate to Acceleration > Web Applications.
2. Click the name of the selected Web application.
3. Open the Exclusions pane.
4. Click New.
5. Select a treatment to be excluded.
6. Select the condition and enter the value to define the exclusion, as described in the table below.

Figure 67: Exclusions
Table 41: Exclusion Configuration
Excluded Select from the drop-down list a treatment to be excluded.
Treatment
Condition Select how the resource to be excluded is identified: Contains, Exact,
StartsWith, EndsWith, or regex.
Value Enter a string which represents the resource to be excluded. In most exclusion
conditions, this is a substring.
• You can exclude entire folders or multiple files using either of these methods.
• If you selected StartsWith, you need to enter the full URI including http:/
/
(such as http://www.mycompany.com/path/path)
• If you selected Contains you can just exclude /path/path.
Purpose of Exclusions
Sometimes certain resources are affected negatively by some treatments because the Web site
expects the files to look and behave in a certain way (usually due to custom coding). Because
treatment sets are defined outside of your Web application, exclusions let you indicate that specific
resources found within your application should not have certain treatments applied.
Identifying Problem Resources

If a resource is being treated incorrectly, you can add it to the exclusion list to verify this. Some
examples include:
• If a JavaScript is not triggered correctly after it has been consolidated, exclude it from
JavaScript Consolidation or another similar treatment which may be affecting it (such as
Browser Cache Invalidation).
• If an image does not render on the page after being treated, exclude it from Image
Consolidation or another similar treatment which may be affecting it (such as Image
Compression or Progressive Image Rendering).
Non-Treatable Resources
Sometimes resources are not treatable by specific treatments. Such a resource is left unaltered by
the treatment.
If you think a resource that is incorrectly not being treated, you can investigate why the resource
was excluded.

To determine why a resource is excluded
> Display the list of treated resources on a page by appending the ?printcompileinfo=1000
parameter to the page URL.
Instruction Lists
Each time a page is optimized for a client browser, it is called an instruction. Instructions are a
representation of a treated HTML document and the manner in which it is rewritten to call treated
resources. It does not represent the treated resources themselves, except when those resources
have been in-lined into the page as part of treatment.
• Working with Instruction Lists, page 159
• Instruction Details, page 160
• Substitution Lists, page 161
• Treatment Information, page 161
• PrintCompile Instruction, page 162
Working with Instruction Lists

Use this procedure to access the instruction lists.
To access the Instruction List

2. Select Web application for which you want the Instruction List.
3. Select the Instruction List pane.
Figure 68: Instruction Lists
The Instruction List contains a list of all the compiled pages for the Web Application, including which
page URL it is for, which Client Group it is part of, and if it is a landing page or not. Each of these
individual values create a unique page instruction.


• Filters, page 160
• Flushing, page 160
Filters
Use this procedure to filter the instruction set.
To filter the Instruction Set

1. Select the filter options: URL substring, client group, landing page status
2. Click Refresh Instruction List.
Flushing
Flushing removes all compiled pages for the Web application, but does not flush the Output Cache.
Notes
• You must flush compiled pages if you have turned off Automatic Invalidation.
• If you have to remove a single instruction, use the Invalidation Option.
• All instructions are subject to auto-invalidation (unless disabled) and will occasionally recompile
themselves.
To flush all instructions for a Web application

> Click Flush Instructions.
Instruction Details
You can drill down into each instruction to get more details about it.
Parameters that indicate the health of the instruction include: Recompiling?, Requires Compile?,
and At Threshold?.

Figure 69: Instruction Details
Substitution Lists
The details page also includes both primary and secondary substitution lists. These display what was
the original text on a compiled text or HTML page, and what is now being provided to a user.
Figure 70: Substitution Lists
Treatment Information
Some types of treatment information is also provided on this page. The details of these vary
between treatments, however the common information includes:
• Is the treatment is enabled
• Has the treatment reached its threshold
• Does it require compilation?

Figure 71: Treatment Information
Note: The treatment information here does not necessarily align up with the actual FastView
treatments. These are representative of the processes that are applied to a page when they
undergo acceleration treatment.
PrintCompile Instruction
With debug logging enabled, you can view how the page is replacing and including treated resources
using the ?printinstruction parameter.
To see the how each resource is treated on the page, use the ?printcompileinfo parameter.
Resource Library
The Resource Library displays a list of all modified resources for a Web application.
Figure 72: Resource Library
By selecting any resource on the list, you can find out more details about it, including its treated
name, if it is in a preload list, and so on.

Note: It can be very difficult to find individual treated resources using the Resource Library, as the
list is not sorted by treated or untreated name, and has no indication of what page it is on. Radware
recommends using the ?printcompileinfo parameter, which specifically displays information
about treated resources for a specific page.
ETag Volatility Report

ETag Volatility Report displays statistics specific to individual Web applications and the associated
ETags.
ETag volatility reports need to be enabled in the XML for the specific Web Application by enabling the
following variable < enabled="true"/>
To enable the ETag Volatility Report:

2. Search for “VolatilityReporting”.
3. Set the value of enable=”true”/.
To access the ETag Volatility Report:

2. Select the ETag Volatility report to view details.
Figure 73: ETag Volatility Report
Note: Information in this dashboard is effected by CDN caching. The more caching that takes place
at the edge, the less data reported on the appliance.


Performance Analysis
Chapter 9 – Performance Analysis

This chapter discusses the following performance analysis topics:
• Integrated APM, page 165
• Analyzing Treatment Performance, page 167
• Basic Analysis Tools, page 168
Integrated APM
Application Performance Monitoring (APM) provides a comprehensive picture of Web applications
performance, letting the system administrator to monitor real user experience and easily
troubleshoot performance downgrades. This data can help the system administrator understand
where optimization is required in order to meet the required SLAs.
With APM, the following dashboards and historical reports are available:
• Business-need focused reporting:
— Aggregation at the application level-server IP address/port or traffic pattern
— Aggregation at the transaction level-collection of URLs per application
— Geographical-location-based pivoting
— Pivoting by real servers
— Built-in SLA-tracking mechanism
• Real-time and historical monitoring:
— SLA Watch dashboard
— Global User Experience dashboard
— Application dashboard
APM monitors the end-user experience for Web applications using dedicated collectors. The collector
is a small and efficient JavaScript that is automatically embedded into the Web application pages by
FastView. The collector gathers real-user experience measurements when running within the user's
browser. It monitors every user request and reports the related network and browser-rendering
time. FastView adds the data-center latency information and sends the consolidated report to the
SharePath server, co-located on the FastView appliance or installed as a separate virtual machine
(VM). The SharePath server processes the report, analyzes it, and displays it in the dashboards.
Notes
• APM requires a special license, and is available for FastView appliance v2 or for VA users.
• When APM is used in a synchronized cluster configuration, all devices in the cluster require APM
license.
• APM does not support IPv6.
When APM is used with FastView appliance v2, SharePath server is installed on the appliance. When
used with VA, SharePath server is installed on another VM.

To configure APM
1. Navigate to APM > Settings.
Figure 74: APM Settings
2. Select Enable APM on this device, and enter the APM Address Port. This is the IP address
and port number of the SharePath server that collects the reports. The SharePath server can
reside on the same appliance or be installed on a separate VM.
3. Click Save.
You now have to enable APM for the required Web applications. You can add granularity by
enabling APM only for specific Classification Rules within a Web application.
Note: When APM is used only for some Classification Rules, it should be enabled for the Web
application.
4. Click the SharePath Administration link to open the SharePath page for APM Maintenance.
5. Navigate to APM > Web Applications.
6. For a particular Web application, click the APM Enabled OFF button. APM Enabled changes to
ON.
Figure 75: APM Web applications

7. To view the report for a Web application, click on the link in the Report column for that
application.
Note: APM requires a separate log in with a username and password. The default username
and password is admin, correl.
Figure 76: APM Report Example
For a detailed description regarding using the APM feature, refer to Appendix C - Using the
Application Performance Monitor, page 207.
Analyzing Treatment Performance

It is very difficult to determine how much benefit a treatment is individually providing. This is
because many treatments work in combination with one another.
Some actions you can perform to determine the value of an individual treatment includes:
• Enabling or disabling individual treatments when making performance comparisons
• Taking measurements using measurement tools

• Start Render, page 168
• Post Render, page 168
• Visual Factors, page 168
• Other Considerations, page 168

Start Render
Some treatments modify the resources loading on the page so that the Start Render time
(measurable by some analysis tools) is smaller. Look for this when enabling or disabling certain
treatments and where the resources are moved to or how they are compressed to arrive at this
result.
Post Render
Some treatments modify the resources loading on the page so that more resources are loaded Post
Render. This is done to display a page complete so the user can interact with it, while still loading in
the details the user does not need immediately. This effectively makes the page load time of your
site faster. Some tools display post-render values and these should not be confused with what the
user sees.
Note: Gomez is one such tool that includes Post-Render resources when doing analysis. This can be
confusing, because while the actual load time for a user may be smaller, the analysis can actually
display slower pages due to the resources being loaded Post-Render. Contact Radware Technical
Services for information on altering Gomez Tests to exclude Post-Render functions.
Visual Factors
A good method for determining how treatments are affecting your page is to look at the visual
comparison of a ?l00p=off versus a ?l00p=on page load. WebPageTest is a good tool for this kind of
comparison as performs video comparisons for your Web site.
Other Considerations
A few treatments (such as View State Reduction and Minification) do not provide much acceleration
benefit, but instead target other benefits such as payload reduction. These types of treatments may
result in faster pages by transferring less data over the network, but as networks get faster this
often becomes harder to measure in terms of speed. Use appropriate measurement tools to identify
these resources and review their benefits as appropriate.
Some consolidation techniques also remove files and place them directly into the HTML page itself.
This is important to note as when you are trying to track down how a treatment has modified a file,
as you may not be able to find it directly. Examining the content of your HTML can help to identify
how these resources are called after being treated.
Basic Analysis Tools

One of the most important things you can do when examining performance analysis is to use a tool
that examines the flow of your traffic to the browser. This helps analyze individual treatment
functionality, as well as overall performance. Visualizing when files load, start times, waterfalls, and
other aspects of the flow of your traffic to an end-client browser help you investigate these
performance differences. There are many tools available. Below is a sample list of these tools:

Table 42: Basic Analysis Tools
Tool Description
WebPageTest WebPageTest is a public Web site dedicated to presenting your Web site
performance. Using the site, and entering your Web page address, the clients
test your Web site using actual browsers and then provide you with the details
and flow of the resources.
HTTPWatch HTTPWatch provides waterfall analysis, with the ability to drill down into
resources to retrieve information about how fast the resources load, headers,
and so on.
YSlow Similar to HTTPWatch, this tool provides waterfall analysis, with the ability to drill
drown into resources to retrieve information about how fast the resources load,
headers, and so on.
Firebug/ Many browsers have built-in tools to perform tasks similar to what external tools
WebInspector do. Firefox Firebug and Chrome/Safari WebInspector are two such built-in
inspectors.
There are many other tools available, and anything that lets you view and analyze the resources on
a Web page can assist you with your analysis.


Third Party Integration
Chapter 10 – Third Party Integration

FastView can integrate with a variety of external tools for logging access, checking overall appliance
health, and other CDN/Networking features.
This chapter includes:
• ISAPI Modules
• SNMP Monitoring
• CDN Integration
ISAPI Modules
FastView acts as a proxy for Web traffic flowing through it. As such, Web servers associated with the
configured virtual servers receive their traffic as if it came from FastView, and not from the client IP
address. For Web servers to properly recognize the client source, the header sent from FastView
must be recognized by the Web servers.
FastView includes both an X-Cluster-Client-IP and X-Forwarded-For header for such purposes. For
more information on understanding headers, see Parameters, Headers, and Cookies, page 147.
Note: Radware strongly recommended using the preferred X-Forwarded-For header if possible.
Because this header is not enabled by default, you must enable it in FastView before it can be read
by the Web Servers.
IIS 7 or Later
If you are using IIS 7 or later, you should use an appropriate HTTP module. While FastView does not
provide these modules for your Web Server, there are many free ones available for installation.
IIS 6 or Earlier
If you are using IIS 6 or earlier, an appropriate ISAPI filter is required, and you should use an
appropriate HTTP module. While FastView does not provide these filters for your Web Server, there
are many free ones available for installation.
Other Web Servers

Other Web servers provide plug-ins for reading headers sent from proxies as appropriate, and many
are built into the Web server's set of features. Use the appropriate ISAPI module for your Web
server to read the X-Forwarded-For header as the original Client IP address.
SNMP Monitoring
You can enable SNMPv2 support for FastView. This lets SNMP services to poll the appliance and
collect basic system information to ensure that it is functioning.

To enable SNMP access

> Use the CLI Network SNMP commands:
— network SNMP show —Displays your current SNMP settings.
— network SNMP reset —Resets the SNMP setting and disables it.
— network SNMP wizard —will take you through a wizard that will configure your SNMP
access, including:
• Community read string
• Administrative contact
• Location string
• Restricting access from specific IP addresses
MIBs
FastView provides most of the 1.3.6.1.2.1 MIB-2 definitions.
There are a few exclusions:
• 1.3.6.1.2.1.4.34.1.5.1.4— ipAddrTable (interfaces and OIDs to which they're mapped)
• 1.3.6.1.2.1.6.13.1— tcpConnEntry (information on TCP connections)
• 1.3.6.1.2.1.6.19.1.7— tcpConnectionState (information on TCP connections)
• 1.3.6.1.2.1.6.20— tcpLitenerTable (information on LISTEN TCP sockets)
• 1.3.6.1.2.1.7— udp
• 1.3.6.1.2.1.55— ipv6
• 1.3.6.1.2.1.88— disman
• 1.3.6.1.2.1.92— configlog
• 1.3.6.1.2.1.25— process table
A MIB is available to track FastView statistics as well. Contact Radware Technical Support for more
information.
CDN Integration
FastView works seamlessly with various CDNs by writing out the treated domains of a Web
application to that CDN location, and having the CDN pull from FastView. However, certain CDNs use
advanced caching methods that require additional configuration in FastView for proper integration.
FastView is designed to integrate into environments that use CDNs such as Akamai and Level3.
When integrating with a CDN, the following are some special design considerations:
• Position of FastView
• Resource Caching
• CDN Edge HTML Caching
Position of FastView
In a CDN environment, FastView is considered the origin for the CDN Edge Cache. FastView uses the
actual Web servers as its origin. In effect, FastView acts as the middleman between the CDN Edge
Cache and the original Web site.

Resource Caching
Because the CDN Edge caches resources that are requested from it, there is no special setup
required to have resource caching work with FastView. However, because of the retention of the
resources on both the CDN Edge Cache and the FastView Response Cache, when you want to publish
new content, it may not update right away. If you need to publish new content and cannot wait for it
to update by expiring from both caches, you need to manually flush your caches, as follows:
• Flush the Response Cache and the Instruction Cache from FastView to ensure that they
immediately fetch new resources from the back-end.
• Flush the CDN Cache to ensure that it fetches up-to-date resources from its origin (FastView).
CDN Edge HTML Caching

If the CDN is configured to cache HTML, a few additional settings are required on FastView and in
the CDN configuration to ensure only compiled pages are cached.
In FastView
In FastView, you must enable Edge Side Landing Pages:
• Enable the Edge Side Landing Page feature from Web Applications > Advanced Options.
• Ensure that all pages treated by your Classification Rules are landing page candidates.
In CDN Configuration
The configuration for HTML require special CDN rules to support FastView with Edge HTML Caching.
This is a service that must be purchased from Akamai. The following needs to be set:
• Ensure that any request that contains the text “l00p” in the query string always goes to the
origin.
• Any request for a page checks for an SL_ClassKey cookie, and if present, appends the cookie
value when creating the Cache Key Request.
Radware Technical Services can provide more details on this information, but cannot code this in the
CDN environment. This must be contracted through your CDN provider.
Flow of Traffic
When a request comes into the CDN Edge for a Web page, it should create a cache key request using
that URL, because during a first hit from a client browser there is no SL_ClassKey cookie. It can then
request the page from FastView as the origin, which provides a landing page optimized for generic
CDN front-end caches. This optimized page contains code that causes the client browser to set its
SL_ClassKey cookie appropriately. When a subsequent request comes in with the SL_ClassKey
cookie, a cache key request is created on the CDN that is a combination of the URL and the cookie
value. The request is then made to FastView as the origin, passing the full original request to get the
appropriate page from FastView.
To perform appropriate testing, you should be able to force the requests to go directly to the back-
end FastView (if configured appropriately) by using the ?l00p= parameter.
Note: Using the ?l00p=on/off parameter with the ?sllp parameter only lets you test the landing
page generated for a specific browser. However, landing pages in this environment are generated for
a generic front-end client. Use a value of ?l00p=eslp instead to bypass the CDN’s cache, but still get
the appropriate landing page from FastView.


Support Assistance
Chapter 11 – Support Assistance

There are some features in FastView that help support identify and assist with issues that may arise
on your site. Each of these have separate configuration options and should have no effect on the
functionality of your appliance.
• Advanced Features
• Remote Diagnostics
Advanced Features
FastView contains many advanced configuration options. Most of these should not be performed
without the assistance of Radware Technical Support.
This chapter describes the following topics:
• Advanced Mode
• XML Editor
• Fine Tuning Memory
• Browser Client Groups
Advanced Mode
Throughout this guide there may be references to features in the Web Management Interface that
you may not see displayed. To ensure that you can see all of the features, convert your display to
Advanced mode.
Note: Advanced Mode is not available for Alteon NG users.
XML Editor
In Advanced mode, you can directly edit the FastView configuration using the Edit Config XML pane.
Before using this editor, confer with Radware Technical Support.
The individual XML nodes are not covered in this guide as the XML configuration is very extensive.
To use the XML editor

2. After making a configuration change the XML, click Verify. This ensures that there are no errors
in the altered XML before saving.
3. Then, do one of the following:

Support Assistance
— Click Save.
— Click Save and Flush. When you make changes through the Web Management Interface,
an instruction flush occurs automatically when required. When you are modifying the XML,
you must manually flush instructions after a change that will affect the way FastView
compiles resources.
Fine Tuning Memory

Depending on the features you are using, you can tweak memory usage on your appliance.
To fine tune memory

> From the CLI, run the memory commands.
When running the memory wizard, the recommended defaults are provided, but these numbers can
be adjusted with more or less memory, as needed.
Contact Radware Technical Support if you need assistance with this feature.
Note: If you are not using IIS, you may want to adjust the memory away from the View State
feature to other features. This is because View State is an IIS feature, and other Web servers do not
take advantage of it.
Browser Client Groups

Just as a Web server or Web site respond differently to different client browsers, FastView does the
same. This is not easily configurable, as FastView is configured for optimal responses based on the
browser, and should not be changed. These browser client groups are updated with each release of
the product to be compatible with newer browsers as they are released.
To see the available client groups

1. Open Edit Config XML.
2. Search for “ClientGroups”.
Clients are identified by the User-Agent header sent by the client browser. If a client does not have a
matching User-Agent header, no treatments are applied.
The client group does not determine if a treatment is applied, but instead determines how the
treatment is applied. How the individual treatments are modified by a client browser is described for
each individual treatment in its testing section, if applicable. For more information, see Defining
Treatment Sets, page 97.
Remote Diagnostics
FastView has the potential for sending information about its runtime to Radware Technical Support
for analysis. This allows for Radware Technical Support to
• better Support Customer Cases.
• preemptively detect problems that may occur.
• make Better Decisions about how FastView is used.

Support Assistance
To access Remote Monitoring

> Navigate to Appliance Management > System Settings > Remote Monitoring.
Figure 77: Remote Monitoring
FastView sends two types of remote diagnostic data. These different types of data represent
different information. They include:
Table 43: Remote Diagnostic Data
Allow Statistics This allows statistical data about your appliance hardware to be provided back to
FastView. FastView can preemptively use this information to identify any
problems with the appliance. In order to use this feature, your appliance must
have a valid DNS Server configured and be allow ed access to the Internet
(monitoring.strangeloopnetworks.com). It is recommended that this always be
enabled.
Allow Log Files This allows logged data from your appliance to be provided back to FastView. This
includes appliance logs, hardware diagnostic output, and other appliance
configuration files. FastView can preemptively use this information to identify any
probe ms with the appliance. In order to use this feature, your appliance must
have a valid DNS Server configured and be allow ed access to the Internet
(monitoring.strangeloopnetworks.com). It is recommended that this always be
enabled as it has no performance impact on your appliance, but greatly helps
Radware Technical Support monitor and identify any problems before they can
occur.
Configuration
In order for FastView to send remote diagnostic data to FastView, it requires two pieces of
information set up. These are the same two configuration items that are required in order to do
upgrades. Any user making use of online upgrades is already configured to use remote diagnostics.
The setup required is:
• DNS Settings correctly set
• An active connection to the Internet

Support Assistance

Security Standards
Chapter 12 – Security Standards

This chapter describes how to best incorporate specific security standards in your FastView
configuration. It includes:
• Using FastView Security Features, page 179
• Using Security Standards, page 181
Using FastView Security Features

This section describes how to implement many of the FastView security features, including:
• Enable PCI Mode, page 179
• Create User Accounts, page 179
• Enable Syslogs, page 179
• Administrative Password, page 180
• Configuring Session Timeouts, page 180
• Add a Certificate, page 180
• Secure Your Appliance, page 181
• Using Security Standards, page 181
Enable PCI Mode

Use this procedure to enable PCI mode.
To enable PCI mode
1. From the Command Line Interface (CLI), run security wizard.

2. You are prompted to enable secure mode. Select Yes. The following occurs:
— The appliance enters a more secure networking mode.
— Raw packet data is never stored in any logs.
— The Packet Capture feature is disabled.
Create User Accounts

Ensure that all FastView users have unique accounts and secure passwords to administer FastView.
To do this, use the user command in the CLI.
Enable Syslogs
Enabling syslogs ensures that you can keep track of all modifications to the FastView configuration.
This can be used to audit your appliance, if necessary.

Security Standards
To enable syslogs
> From the CLI, issue the command syslog.
Administrative Password
Ensure that your administrative account does not remain with the default password. You can change
the admin password. A “strong” password should be used. If other user passwords are set by the
administrator, it is important that they follow the same practice.
To change the admin password

2. Enter the old password, a new password and confirm.
3. Click Change.
Figure 78: Administration
Configuring Session Timeouts

Ensure that your user's management sessions time out when idle as part of a standard security
precaution. The default session timeout for both the CLI and Web Management Interface is 15
minutes, but can be adjusted through the Administration pane.
Add a Certificate
It is important to secure the data transmitted to and from FastView. To do this, your should create
an SSL certificate and assign it to your virtual servers your Management IP address.

Security Standards
To add an SSL certificate

2. Select an SSL certificate (previously created) from the drop-down list.
3. Select View Certificates to jump to the SSL Certificates pane to view and create SSL
certificates.
For information regarding creating and modifying certificates, refer to SSL Certificates, page 72.
Secure Your Appliance

Ensure that you follow best practices for both physically and virtually securing your appliance.
Using Security Standards

The following sections describe how to best incorporate specific security standards in your FastView
configuration:
• PCI DSS 2.0 Compliance, page 181
PCI DSS 2.0 Compliance

PCI DSS 2.0 was released on October 28, 2010. The standard provides a baseline for technical and
operational requirements designed to protect card holder data. It applies to all entities involved in
payment card processing, including merchants, processors, acquirers, issuers and service providers,
as well as all other entities that store, process or transmit card holder account data.
There are 12 PCI DSS requirements organized into six main categories that prevent credit card fraud
through increased controls around data and its exposure to compromise. To be fully compliant, an
organization must satisfy all 12 requirements.
FastView contains options and tools to address aspects of all secure environments and provides
guidelines on how to best apply these to meet the PCI compliance guidelines.
Configuration
If FastView is in a PCI-compliant environment, certain configuration steps should be taken to ensure
the appliance fits within this type of environment. The following is a set of PCI steps and the
FastView features that help address those steps.
• Install and Maintain a Firewall Configuration to Protect Cardholder Data
• Do Not Use Vendor-Supplied Defaults for Passwords and Other Security Parameters
• Protect Stored Cardholder Data
• Encrypt Transmission of Cardholder Data Across Open, Public Networks
• Use and Regularly Update Anti-virus Software or Programs
• Develop and Maintain Secure Systems and Applications
• Restrict Access to Cardholder Data by Business Need to Know
• Assign a Unique ID to Each Person with Computer Access
• Restrict Physical Access to Cardholder Data
• Track and Monitor All Access to Network, Resources and Cardholder Data
• Regularly Test Security Systems and Processes
• Maintain a Policy that Addresses Information Security for All Personnel

Security Standards
Install and Maintain a Firewall Configuration to Protect Cardholder Data

FastView itself does not have a means to modify or maintain your firewall rules and options.
However, a list of ports are provided to help you modify your network firewall to make use of only
those ports required for FastView operation.
Do Not Use Vendor-Supplied Defaults for Passwords and Other Security Parameters
Regarding passwords, see Create User Accounts, page 179, Administrative Password, page 180
Ensure that all FastView users have unique accounts and secure passwords to administer FastView.
SNMP access can be configured and modified specifically for your environment. You also can modify
any of the public query parameters that could be used to affect the functionality of your appliance.
Protect Stored Cardholder Data

See Enable PCI Mode, page 179.
Encrypt Transmission of Cardholder Data Across Open, Public Networks

FastView lets you create virtual servers that accept and send SSL encrypted data. When Web sites
are configured appropriately, all secure traffic should use this method.
In addition, see Configuring Session Timeouts, page 180.
Use and Regularly Update Anti-virus Software or Programs

Because FastView is a closed system that passes data through it, it does not contain an anti-virus
solution. Ensure that data received or transmitted from your Web server has this functionality.
Develop and Maintain Secure Systems and Applications

As FastView should be behind your firewall on your internal network (Requirement #1), public
security issues should not be a common occurrence, but can be addressed through FastView
Updates to obtain the latest service releases for your version. Depending on your service contract,
you can obtain FastView new versions.
Restrict Access to Cardholder Data by Business Need to Know

Although cardholder data should not be available through FastView, you can ensure that FastView is
only accessible to appropriate users by having unique accounts and secure passwords to administer
FastView.
See Create User Accounts, page 179 and Enable Syslogs, page 179.
Assign a Unique ID to Each Person with Computer Access

Currently, FastView does not allow you to place manual restrictions on passwords. Ensure that you
have policies in place to address this issue.
Restrict Physical Access to Cardholder Data

See Secure Your Appliance, page 181.
Track and Monitor All Access to Network, Resources and Cardholder Data
Although FastView does not have the facilities to record customer usage, you can ensure that you do
so by enabling logging on your Web servers. Appliance Logs are also stored on the appliance that
can be reviewed as necessary.

Security Standards
Regularly Test Security Systems and Processes

FastView provides no mechanism for scanning or testing other appliances on the network. Ensure
that you test this appliance with whatever procedure you use to regularly test your network security
to ensure compliance.
Maintain a Policy that Addresses Information Security for All Personnel

Although FastView can help to address the technical aspects of meeting the PCI DSS 2.0
requirements, it cannot help to enforce or maintain policies.

Security Standards

Command Line Interface
Chapter 13 – Command Line Interface

The Command Line Interface (CLI) lets you set up FastView using CLI commands. For a description
of how to connect to the CLI, see Connecting to the CLI, page 40.
This chapter describes the following CLI commands:
• Generic Commands
• CLI Networking Options
• CLI Maintenance Options
• CLI Security Options
• CLI Support Options
Generic Commands
The following commands are available in the Command Line interface that can help you with general
navigation.
Table 44: Generic CLI Commands
Command Description
clear Clears the console.
date Enables you to manually set the date and time. This disables any active
NTP servers.
exit Logs you out of the active CLI session.
help Lists the available commands in the CLI.
history Displays the list of historical commands run through the CLI.
CLI Networking Options

Most network settings should be available through the Web Management Interface. However, the
following commands are only available on the CLI.
• Ping
• Network Settings
• Synchronized Cluster Management
• Certificate Settings
Ping
The following table shows the Ping commands available.
Table 45: Ping
Command Description
ping <target> Pings the target IP address or hostname. If you use a name instead of an
IP address, your DNS server must be configured correctly.

Network Settings
The following table shows the network setting commands.
Table 46: Network Settings
Command Description
network arp show Lists the contents of the FastView ARP table. This is useful for
diagnostics.
network dns add Adds an IP address to your DNS entries.
<ip_address>
network dns clear all Clears one or all of your DNS settings.
network dns clear
<ip_address>
network dns search Sets your DNS search name. This is not required for DNS to resolve
<name> fully qualified domain names.
network dns show Lists your DNS settings. Without your DNS settings, FastView is unable
to contact the support site for updates or provide vital remote
diagnostic data in case an issue arises.
network gb1 advertise Sets the Web Management Interface advertisement options.
on|off
network gb1 duplex Sets the duplex of your Web Management Interface. In most cases you
<duplex> should leave this set to auto. However, in some cases, a specific
network duplex needs to be set.
network gb1 gateway Sets the gateway of your Web Management Interface.
<gateway>
network gb1 IP <ip> Sets the IP address of your Web Management Interface. In addition,
[netmask] [gateway] this command can be extended to include the netmask and gateway
options rather than entering them as separate commands.
network gb1 mtu <mtu> Sets the MTU of your Web Management Interface. If you are unsure of
the MTU, leave the default value of 1500.
network gb1 netmask Sets the netmask of your Web Management Interface.
<netmask>
network gb1 speed Sets your Web Management Interface speed. In most cases you should
<speed> leave this to auto. However, in some cases a specific network speed
needs to be set.
network hostname Sets the hostname of the appliance. The current hostname displays as
<hostname> the CLI prompt. This identifies the appliance when multiple appliances
are on the network, such as when running redundancy features.
network hosts add <ip> Adds an IP/host combination to your hostfile.
<host> [host...]
network hosts clear all | Removes either all host entries, or a specific host entry line.
<ip> <host> [host...]
network hosts show Displays your hostfile entries. This lets you redirect traffic to specific IP
addresses when specified hostnames are requested. For example, you
may want all requests to www.myurl.com to go to an IP address of
192.168.1.1
network ntp add <ntp_ip> Adds an NTP server.
network ntp clear all | Removes either all NTP entries, or a specific NTP server IP address.
<ip>

Table 46: Network Settings (cont.)
Command Description
network ntp <enable | Enables or disables synchronization with the NTP Server.
disable>
network ntp show Displays all the information about your NTP configuration.
network post-up list Lists available route commands.
network post-up add Adds a route command. Each route added is appended to the list in
route add sequential order.
[destination]
[route]
network post-up Clears routes that have been added to your appliance.
clear [# | all]
network show Displays all the information about your Web Management Interface
network settings.
network snmp reset Clears the SNMP settings and disables the feature.
network snmp show Displays all the settings for polling your SNMP. To enable this feature if
it is disabled, run the SNMP wizard.
network snmp wizard Prompts for the configuration settings for enabling and/or configuring
SNMP.
network wizard Walks you through a network configuration wizard similar to the First
Time Setup wizard. This lets you reset and configure all relevant
network settings on the appliance.
Synchronized Cluster Management

Synchronized Cluster Management commands are available through the Web Management
Interface. Radware recommends that you use the Web Management Interface to configure this
feature. For more information on synchronized clusters and how they can benefit your environment,
see Synchronized Configuration, page 72.
Note: Synchronized Cluster Management is not available for Alteon NG users.
Table 47: Synchronized Cluster Management Settings
Command Description
config sync create Creates a synchronized cluster with this appliance as the primary
<name> <passphrase> appliance in the cluster. After a cluster is created, additional appliances
can be added, and traffic management configured. You must provide
both a cluster name and a passphrase for other appliances to join this
cluster.
config sync join <name> Joins this appliance to a previously defined cluster. You must provide
<passphrase> <ip> the name of the cluster, the passphrase specified during creation of
that cluster, and the Management IP address of at least one appliance
in the cluster. Once joined, your FastView's configuration is synced to
be the same as the cluster's, losing any previous settings.
config sync purge all|<ip> Any appliances in the cluster that are not online and joined are purged
from the configuration. You can specify individual IP addresses, or flush
out all invalid appliances using all.

Table 47: Synchronized Cluster Management Settings (cont.)
Command Description
config sync reset Removes all synchronized cluster configuration from your appliance.
Unlike unjoin, this forces a reset of any configuration that may have
been used in the synchronized cluster.
config sync show Displays the config sync settings of your appliance.
config sync unjoin Removes this appliance from the synchronized cluster.
Certificate Settings
Certificates can also be added through the Web Management Interface.
Table 48: Certificate Settings
Command Description
cert list Lists all certificates created on the appliance. This does not display
cert show details about the certificate and you should use the Web Management
Interface for more detailed information.
CLI Maintenance Options

The following Command Line Interface maintenance options are available. These commands are
available through options in the Web Management Interface, but are also available when working
from the Command Line Interface.
• Startup and Shutdown Commands
• Version and Upgrade Commands
• Memory Allocation Commands
Startup and Shutdown Commands

The following table shows the startup and shutdown commands available.
Table 49: Startup and Shutdown Commands
Command Description
appliance reload Forces acceleration to reread configuration. You are not required to
manually run this command when configuration changes are made as
this happens automatically. Running this command does not interrupt
Web traffic.
appliance restart Forces the appliance to perform a software restart. This command
causes a brief interruption to Web traffic.
appliance reset Resets the appliance databases, causing all acceleration techniques to
restart the learning process again and rebuilding the databases
required to run FastView treatments.
appliance reboot Reboots the appliance. Running this command causes an interruption
to network traffic.
appliance shutdown Powers down the appliance. Physical access is necessary to turn the
appliance back on.

Version and Upgrade Commands

The following table shows the version and upgrade commands available.
Table 50: Version and Upgrade Commands
Command Description
version show Displays the current FastView version and if there is a newer version
available for upgrading. This requires both an active Internet connection
that allows access to updates.strangeloopnetworks.com and an
appropriate DNS configuration.
version upgrade Starts an upgrade to the latest version released for your appliance.
Memory Allocation Commands

The following table shows the memory allocation commands available.
Table 51: Memory Allocation Commands
Command Description
memory reset Resets the appliance to its default memory configuration. The exact
values are dependent on the memory provided for your appliance model.
memory show Displays how much appliance memory is allocated to each feature or
treatment. It also displays any values that are at defaults or manually
specified.
memory wizard Runs a wizard to allocate memory to treatments or features.
Do not perform this without assistance from Radware Technical Support,
as doing so can result in insufficient memory being available to specific
features.
CLI Security Options

The CLI is the only interface from which you can change most security level settings of FastView.
Security options include:
• Appliance Administration Ports
• General Security Settings
• User Management
• Syslog Options
Appliance Administration Ports

The following table shows the appliance administration port commands available.
Table 52: Appliance Administration Ports
Command Description
admin ports <http Specifies the ports with which you can connect to the Web Management
port> <https port> Interface. The interface only functions over HTTPS, and HTTP is used
purely as a redirect.

General Security Settings

The following table shows the general security setting commands available.
Table 53: General Security Settings
Command Description
security show Displays the security settings you have put in place through the
security wizard command.
security wizard Walks you through a wizard for setting up some basic security settings.
These include settings for:
• Setting PCI compliance
• Opening firewall connections for high availability
• Setting session timeouts for users
User Management
The following table shows the user management commands available.
Note: User sessions are only on the appliance you are currently managing. If you are using a
synchronized cluster, while user accounts are synced across the cluster, the active sessions are only
visible on the appliance you are connected to.
Table 54: User Management
Command Description
user add|delete Walks you through a wizard that adds or deletes a user account. This
user account can manage the appliance through either the Web
Management Interface or the CLI.
user enable|disable Walks you through a wizard that enables or disables a user account.
This does not delete the account, but rather disables and the account is
not able to log in or make modifications.
user password Modifies a user's password to one set by the administrator.
user reset Removes all users from the configuration. It also resets the admin
password back to its default.
user session show Displays all users connected to this appliance.
user session flush Disconnects a user from the appliance and removes the user session.
all|[sessionid] This requires the user to log in again or it forces a disconnection after
the account has been disabled.
user show Displays all available user accounts and their current statuses.
Syslog Options
The following table shows the syslog commands available.

Table 55: Syslog Options
Command Description
syslog server add Adds an additional syslog sever to which your appliance send logs. While
<server>[:<port>] the appliance still logs to its own syslog, this is an additional external log
[tcp|udp] that you can use for security and maintenance.
syslog server add Removes an added syslog server.
<server>[:<port>]
[tcp|udp]
syslog server reset Removes all added syslog servers.
syslog server show Displays all syslog servers defined for this appliance.
CLI Support Options

The support options are all available for configuration within the Management User Interface.
Radware recommends that you use the Web Management Interface to make any adjustments, but
you can use the CLI if you require it.
CLI support options include:
• Remote Diagnostics
• Support Traffic Captures
• Support Packages
• Support Log Rotation
Remote Diagnostics
The remote command includes options to enable and disable the Remote Diagnostics feature.
Table 56: Remote Diagnostics
Command Description
remote diag show Displays which of the Remote Diagnostic options are enabled or disabled.
remote diag statistics Enables or disables the sending of statistic data to the FastView Remote
on|off Monitoring Server. Radware highly recommends that this is enabled.
remote diag logfiles Enables or disables the sending of log files data to the FastView Remote
on|off Monitoring Server. Radware highly recommends that this is enabled.
Support Traffic Captures

The support capture commands include options to perform a TCP Dump Traffic Packet Capture.
Note: Traffic captures are disabled if you are in a PCI Secure environment.

Table 57: Support Traffic Captures
Command Description
support capture on|off Starts or stops a traffic capture as defined through the Support
Capture Wizard.
Note: Modifications through the Web Management Interface affect
the wizard settings.
support capture reset Resets the capture options set through the Support Capture Wizard
back to capturing all traffic for the appliance.
support capture show Displays the configuration of the current support capture options.
Note: This command does not list the capture files available for
download. You should use the Web Management Interface if you
want this list.
support capture wizard Modifies what traffic on FastView is captured during the TCP Dump
Traffic Packet Capture. At the end of the wizard, if you have defined
traffic to be captured, the capture immediately begins.
Support Packages
The following table shows the commands available for support packages.
Table 58: Support Packages
Command Description
support package Generates a support package that can be download and sent to
Radware Technical Support to provide additional details while obtaining
support. Support packages can also be generated and downloaded
through the Event Logs in the Web Management Interface. For more
details, see Event Logs, page 140.
Support Log Rotation

The following table shows the commands available for support log rotation.
Table 59: Support Log Rotation
Command Description
support log rotate Rotates the log files. These logs can be read through the Event Logs in
the Web Management Interface. For more details, see Event Logs,
page 140.

Maintenance
Appendix A – Maintenance
This appendix describes FastView maintenance in an operational environment. The appendix
includes the following topics:
• Powering On and Off FastView
• Upgrading FastView
• Backup/Restore Appliance Configuration
• Flushing Appliance Cache
Powering On and Off FastView

There are two methods for powering up and down FastView:
• Physically Powering FastView
• Restarting or Rebooting the Appliance
Physically Powering FastView

You can physically power FastView up and down by pressing the power button. FastView takes a few
minutes to power up or down. When the appliance is fully powered up, any defined virtual servers
become available. To power off FastView, press the power button briefly (do not press and hold).
Restarting or Rebooting the Appliance

You can also restart the application or reboot the appliance through the Web Management Interface.
To shutdown the appliance a CLI command is used. See Startup and Shutdown Commands,
page 188.
To restart the appliance

1. Navigate to Appliance Management > Maintenance > Restart Appliance.
Figure 1: Restarting the Appliance

Maintenance
— Soft Restart—This is the preferred method as it is a fast reboot of the software, causing a
reload of configuration and a clearing anything that is cached.
— Hard Reboot—The appliance physically reboots. In most cases this is not required. It
causes more downtime as your virtual servers become unavailable for a longer period of
time than with a soft reboot.
Upgrading FastView
Upgrades can either be provided on request from Radware Technical Support, or managed manually
by the user using a local file with the new software image.
Figure 2: Upgrading the Appliance Software
Notes
• Radware does not recommend upgrading your appliance using the CLI. However, if you need to
upgrade via the CLI, use the version upgrade command in the CLI.
• Updating from older versions of Site Optimizer (the name of FastView prior to version 5.0) may
require additional steps. Contact Radware Technical Support if special upgrade information may
be required.
• Upgrade FastView Using a Local File (Offline Upgrade), page 194
• Upgrade FastView On Request, page 195
• Upgrading with Redundancy, page 195
Note: The upgrade process requires a software reboot and may require a hard restart.
Upgrade FastView Using a Local File (Offline Upgrade)

A option for offline upgrade allows you to download an upgrade package from the Radware portal,
and upload it to FastView using the Web User Interface.

Maintenance
To upgrade FastView using a local file

1. Login to the Radware customer portal (the SW status matrix) and access the FastView page:
http://portals.radware.com/Portal/Customer/ProductDetail.aspx?id=1631752&version=1
2. Click to download the required software upgrade package to your local computer.
3. In the FastView application, navigate to Appliance Management > Maintenance > Upgrade
Appliance Software.
4. In Upgrade from Local File, click Upload and Upgrade.
5. Select the file to upload and click Open.
6. When you are prompted to OK the device restart, click OK.
7. After the device is restarted with the new software image, an Upgrade completed message
appears. Click OK.
8. The browser will refresh and new version number will be displayed.
Upgrade FastView On Request

When a new release is announced, contact Radware Technical Support for the new upgrade for your
appliance. Depending on your support contract, you may also contact Radware Technical Support to
assist in the upgrade.
Initiate the upgrade process through the Web Management Interface.
Note: This option is not available for Alteon NG users.
To upload FastView on request

1. Ensure you have contacted Radware Technical Support for access to the latest release of the
software.
2. Ensure your appliance has appropriate DNS server configuration and outbound access to the
upgrade URL.
3. Navigate to Appliance Management > Maintenance > Upgrade Appliance Software.
4. Click Check for New Version.
5. When prompted with a new version to upgrade, click Click Here to Upgrade.
6. After the upgrade has finished, you receive a confirmation.
Note: If upgrading over the Internet, increase your browser timeout to more than 60 minutes
to prevent the upload from failing.
Upgrading with Redundancy

There are special considerations when upgrading appliances that are using Redundancy Mode.
Note: This option is not available for Alteon NG users.

Maintenance
Synchronized Clusters
The standard upgrade procedures work when upgrading a synchronized cluster. However, once all
FastView appliances in a cluster are not using the same version, the appliances enter a read-only
mode. This ensures the configuration cannot be changed on some appliances and not others when
versions do not match. To go back to a mode where the configuration can be modified, you must
ensure that all your appliances are upgraded to the same version.
Backup/Restore Appliance Configuration

The Backup/Restore Appliance feature lets you back up and restore appliance configuration to an
appliance.
To access the Backup/Restore Appliance pane

1. Navigate to Appliance Management > Maintenance > Backup/Restore Appliance
Configuration.
Figure 3: Backup/Restore Configuration
2. Select one of the following options:

Maintenance
— Backup Configuration, page 197

— Restore Configuration, page 198
— Upload Configuration, page 198
Backup Configuration
Backup/Restore lets you back up the current appliance configuration to the local appliance.
To backup a configuration
1. Select Backup.
Figure 4: Backup Configuration
2. In the Backup Note field, enter the name of the local appliance.
Backups contain:
• Appliance networking settings
• Virtual server definitions
• Web application definitions
• Treatment set definitions
• System settings
• Alerting settings
Backup do not contain:

• SSL certificates
• Appliance licenses
These differences are important. Because the appliance network settings and the virtual server
configuration are backed up, you must be careful not to restore a backup to a secondary appliance
while the primary is running, or there can be IP address conflicts on your network. Be sure to have
local console access in the event of an error in order to reconfigure the network if Web UI access is
lost. Also, because the appliance licensing, and certificates are not contained in the backups, this
information must be kept separate and reconfigured in the event that the appliance is factory reset
before restoring a backup configuration file.
Note: Backups do not currently backed up SSL certificates. If FastView terminates your SSL traffic
and is the only location where this certificate is used, ensure you have a backup copy of the
certificate.

Maintenance
Restore Configuration
Use this procedure to restore your configuration.
To restore a configuration from a backup stored on the appliance

1. Select Restore from server backup.
2. From the Use Backup Configuration drop-down list, select the backup configuration.
Figure 5: Restore Configuration
3. Select Restore Selected Backup.

4. In addition to restoring the backup selected, you also have the option to select Download the
selected backup to a local drive. This lets you keep a copy of the backup file. Radware highly
recommends that you do this occasionally so that if there is ever a hardware failure on the
appliance a backup copy is available to quickly restore configuration on a new appliance.
Upload Configuration
Use this procedure to upload your configuration from a local drive.
To upload a configuration from a local drive

1. Select Restore from local backup.
2. Select Upload and Restore Configuration.
Figure 6: Upload Configuration
Flushing Appliance Cache

There are two types of information that FastView caches over time:
• Flushing Instructions, page 199
• Flushing Output Cache, page 199

Maintenance
If you have FastView Cloud Service, you also need to occasionally flush your cache.
> FastView Cloud Service, page 201
Flushing Instructions
The Instruction Cache is a list of the treated pages and their compiled states. Instructions properly
update themselves as they become invalid over time. Flushing the instruction cache is only
necessary if you need to ensure that pages immediately show properly updated information.
To flush instructions
1. Navigate to Appliance Management > Diagnosis > Instruction List.
Figure 7: Flushing Instructions

— Select Flush Instructions to flush all instructions for a Web application. This removes all
compiled pages for the Web application, but will not flush the Output Cache. This is a
necessary option if you have turned off automatic invalidation.
— Select Invalidation Option to remove a single instruction. All instructions are subject to
automatic invalidation (unless disabled) and occasionally recompile themselves.
Note: Instruction lists are listed by Web application. Ensure that you have selected the proper
Web application from the top of the Diagnosis page before examining the Instruction List.
Flushing Output Cache

The Output Cache is the cache provided by FastView as part of the Output Cache treatment. These
resources are those off loaded by FastView. Generally, it is not necessary to flush the Output Cache,
as resources that are referenced by their original file names (such as HTML Caching) should update
on their own according to their defined time periods. However, you can flush the Output Cache if you
need an immediate update of resources.

Maintenance
To flush the output cache

1. Navigate to Appliance Management > Diagnosis > Flush Cache.
Figure 8: Flushing Output Cache
2. Select one of the following options:

— Flush Global Cache, page 200
— Flush Application Cache, page 200
— Flush Cached HTML Page, page 200
— Flush HTML Pages by Classification Rule, page 200
3. Select Execute Flush.
Flush Global Cache

Flush Global Cache flushes the Output Cache for all Web applications on your appliance. You can also
flush any HTML caching you may have defined for Web applications. This option is the simplest way
to clear the Output Cache for your appliance.
Flush Application Cache

Flushing Application Cache flushes the Output Cache for a single defined Web application. You can
also flush any HTML caching you may have defined for Web applications.
Note: This option flushes the selected Web application only. Ensure you have selected the correct
Web application from the top of the Diagnosis page before executing the flush.
Flush Cached HTML Page

You can flush HTML Cache for a single text or HTML age if you know the exact URL. You have to
provide the full URL, including the protocol and any parameters. This is probably most easily copied
from a Web browser's URL bar.
Flush HTML Pages by Classification Rule

You can flush HTML Cache for a Web application by a Classification Rule only. This does not flush
resources, but only HTML cached pages.

Maintenance
Note: This lets you select Classification Rules from the selected Web application only. Ensure you
have selected the proper Web application from the top of the Diagnosis page before executing the
flush.
FastView Cloud Service

If you have FastView Cloud Service, you also need to clear caches if you make modifications to your
back-end Web servers. You can flush the cache through the Support Portal after you have registered
your appliance with your account from the Dashboard Menu of the Support Portal. This flushes both
the Instruction Cache and Response Cache for the entire selected appliance.

Maintenance

Technical Specifications
Appendix B – Technical Specifications

The FastView appliance is a rack-mounted server. It has Gigabit Ethernet interfaces that support any
of 10, 100, or 1000 Mbps.
There are currently three physical appliance models in production:
• Rev A
• Rev B
• Appliance v2
Note: Virtual FastView versions may have values that vary from the physical version based on
configuration.
Table 1: FastView Technical Specifications
Component Rev A Rev B Appliance v2

Rack Space 1U 1U 1U
Power Supply Redundant 800W 90- Redundant 717W high Redundant AC Power
264VAC, 47-63HZ, output 90-264 VAC, auto- Supply, 750W, 100-240
10.0A (@90VAC) ~1.4- ranging, 47-63Hz VAC, 50-60Hz, 55A
1.5A, 2.1A peak at
BIOS load
Dimensions 42.9 x 482.6 x 762 mm 42.8 x 482.6 x 771.9 mm 42.8 x 482.6 x 701.3 mm
(h x w x d) 1.69” x 19” x 30” 1.68” x 19” x 30.39” 1.68” x 19” x 27.61”
Weight 17.69 kg / 39 lb 17.69 kg / 39 lb 18.6 kg / 41 lb
Heat 5000 BTU 2446.5 BTU 2843 BTU
Power Cables 2 2 2
Base Unit PE1950 1333MHz FSB R610 6GT/s FSB R620
Processor Quad-Core Xeon Dual/Quad Intel FastView 600:
E5345, 2x4 MB cache, XeonE5620 2.4Ghz, 6 cores, 2.00GHz
2.33 GHz 12MCache FastView 1800:
2 X 6 cores, 2.00GHz
FastView 3600:
2 x 8 cores, 2.90GHz
Memory 8-16 GB, 667 MHz; 4-16 GB, 1066 MHz; Dual FastView 600: 32GB
Buffered DR DIMMs Ranked RDIMMs (Actual FastView 1800: 32GB
(Actual amount amount depends on
depends on version) version) FastView 3600: 64GB
HDD 80 GB, SATA, 3.5" 7.2K 160GB 7.2K RPMSATA 1TB

RPM 2.5" Hot Plug Hard Drive
Network Dual Embedded 4 ports Embedded Intel Ethernet QuadPort
Interface BroadcomNetXtreme II Broadcom, GB Ethernet 1Gb Network
5708 Gigabit NICS with TOE
DVD 24x IDECD-RW/ DVD- DVD+/-RW, SATA DVD+/-RW, SATA,
ROM Internal

Front Panel
The following figure shows the front panel of the FastView appliance. This is located behind the front
bezel.
Figure 9: Front Panel
Back Panel
The following figure shows the back panel of the FastView appliance.
Figure 10: Back Panel
Power Supplies
The FastView appliance is equipped with redundant power supplies. The system is in redundant
mode when both power supplies are installed and connected to an AC power source. The system can
operated for a short period with only a single power supply installed. However, it should not
operated in this manner for an extended period, as this prevents proper cooling of the system and
increases the risk of an over-temperature condition.
Power Indicators
The power button has an indicator that displays power status:
Table 2: Power Indicators
Indicator Status
Power Button • On—Power is being supplied to the system and the system is operational.
• Off—No power is being supplied to the system.
The redundant power supplies have three indicators that provide power information:

Table 3: Redundant Power Supply Indicators
Indicator Status
Status • Off—Power supply is not operational.
• On (Green)—Power supply is operational.
Fault • Off—There is no fault.
• On (Amber)—There is a problem with the power supply.
AC Line • Off—There is no power connected to the power supply.
• On (Green)—A valid AC or DC source is connected to the power supply.
PSU Mismatch Green and yellow alternating when hot-added or swapped.
Network Interface Indicators

The FastView appliance has two embedded Ethernet interfaces: Gb1 and Gb2:
• Gb1 is labeled as the Appliance Interface (Web Management Interface)
• Gb2 is a reserved unused interface
• Gb3 is a reserved unused interface (Rev B only)
• Gb4 is a reserved unused interface (Rev C only)
Each interface has two indicators that provide information on network activity and link status:
Table 4: Network Interface Gb1 and Gb2 Indicators
Indicator Status
Link and Activity Off—The interface is not connected to the network.
Link On (Green)—The interface has an operational link to a peer.
Activity On (Amber blinking)—Network data is being sent or received.
Figure 11: Link and Activity Indicators

Hard Drive Indicators

The hard drive has two indicators. Of these, the Status indicator is always off. The Activity indicator
provides information on the status of the hard drive:
Table 5: Hard Drive Indicators
Indicator Status
Activity • Off—Drive is powered off.
• On (steady)—Drive is powered on but no data is being read or written.
• On (blinking)—Drive is powered on and data is being read or written.

Using the Application Performance Monitor
Appendix C – Using the Application

Performance Monitor
This appendix describes basic usage of the Application Performance Monitor (APM).
It contains the following main sections:
• Application Performance Monitor—Overview, page 207
• APM/SharePath-Server Terminology, page 210
• How APM Works, page 211
• APM Configuration Requirements and Limitations, page 212
• SharePath Server Deployment and Initial Configuration, page 213
• Device Configuration and Results, page 213
• Device Configuration and Results, page 213
• Accessing the SharePath Web Interface—APM Dashboard, page 214
• Monitoring Results, page 214
• Using APM to Troubleshoot High Latency, page 214
Note: For information on the deployment and initial configuration of the SharePath server, see
Initial Login and Configuration with KVM, page 41.
For information on how to configure APM in the FastView application, see Integrated APM, page 165.
Application Performance Monitor—Overview

Application Performance Monitoring (APM) provides a comprehensive picture of Web applications
performance, letting the system administrator to monitor real user experience and easily
troubleshoot performance downgrades. This data can help the system administrator understand
where optimization is required in order to meet the required SLAs.
With APM, the following dashboards and historical reports are available:
• Business-need focused reporting:
— Aggregation at the application level-server IP address/port or traffic pattern
— Aggregation at the transaction level-collection of URLs per application
— Geographical-location-based pivoting
— Pivoting by real servers
— Built-in SLA-tracking mechanism
• Real-time and historical monitoring:
— SLA Watch dashboard
— Global User Experience dashboard
— Application dashboard
APM monitors the end-user experience for Web applications using dedicated collectors. The collector
is a small and efficient JavaScript that is automatically embedded into the Web application pages by
FastView. The collector gathers real-user experience measurements when running within the user's
browser. It monitors every user request and reports the related network and browser-rendering

time. FastView adds the data-center latency information and sends the consolidated report to the
SharePath server, co-located on the FastView appliance or installed as a separate virtual machine
(VM). The SharePath server processes the report, analyzes it, and displays it in the dashboards.
Notes
• APM requires a special license, and is available for FastView appliance v2 or for VA users.
• When APM is used in a synchronized cluster configuration, all devices in the cluster require APM
license.
• APM does not support IPv6.
When APM is used with FastView appliance v2, SharePath server is installed on the appliance. When
used with VA, SharePath server is installed on another VM.
Key Values of Radware’s Application Performance Monitoring

To ensure that Web-application performance meets your customers’ expectations and consistently
delivers their business SLA, you need to attain visibility into the application performance and the
actual quality of experience (QoE) end-users are experiencing. Radware provides the Application
Performance Monitoring (APM) module, supporting an end-to-end, proactive approach to monitor
and maintain high SLAs of user-facing Web portals as well as internal Web applications.
Radware's APM provides the following key values:
• Complete visibility of Web application performance and real-user experience, managing and
tracking user-defined SLAs
• Fast Root Cause Analysis using highly granular measurement, in real time
• Monitoring of actual user traffic, with no dedicated scripts per Web application, lowering costs
Complete Application Performance Insight Based on User-Defined SLA

Radware’s APM provides a comprehensive picture of all applications, transactions, and real servers in
data centers, letting users drill down to the application and transaction level, globally or for a
particular user. In addition, the picture reflects the actual end-user QoE—wherever the real clients
are—at all times.
The performance measurements are based on user-defined SLAs. The measurements may include
the minimum average response time that the application should provide and the minimum latency at
a data center. The SLA can also be defined for a geographical location, letting administrators
determine if there is a problem with users from a specific region.

Figure 12: Application SLA Summary View
Fast Root Cause Analysis Using Highly Granular Measurement

Radware's APM enables fast, accurate troubleshooting and rapid Root Cause Analysis in cases of
high latency that results in poor user experience.
This is achieved using a detailed transaction-measurement breakdown across the following three-
stage application-delivery chain:
1. Data-center time—The time spent at the data center to prepare and serve the required Web
page
2. Network time—The time it takes for the server's response to reach the client
3. Browser-rendering time—The time it takes the browser to render the whole page
This transaction breakdown lets users efficiently pinpoint the origin of application performance
degradation, saving analysis time and effort.
Figure 13: Transaction Stage Breakdown Analysis

Monitoring Actual Transactions and Errors of Real Users

Radware's APM measurements are based on real-user transactions, as opposed to synthetic
transaction monitoring. The solution’s analytics engine captures actual user navigation behavior, and
is sensitive to real-life errors. In addition, the solution provides a realistic view of geographical
distribution of the user locations, and pinpoints issues specific to each location, time, and browser.
As a result, there is no need to write dedicated scripts for specific Web applications, or simulate
transactions, which ultimately lowers overhead, risk, and costs.
APM/SharePath-Server Terminology
The following table defines common terms in the context of APM and the SharePath server.
Table 6: APM/SharePath-Server Terminology
Term Definition
Application A collection of end-user HTTP requests that serve a business role. The
SharePath server, under the corresponding application domain, collects
and presents all performance statistics of an individual user.
The terms application and application domain are interchangeable.
By default, an application is equivalent to a virtual service for which APM
is enabled. The application is identified by its name. The name of the
application is equal to the name of the virtual service. If a virtual-service
name is not defined, the application name has the following format:
ADC_<virtual IP address>_<port>.
If more than one application has the same name, the SharePath server
combines the statistics into the same report.
Transaction A subset of end-user HTTP requests that belong to the same application
and have the same URI.
Event A performance report for a specific HTML page.
Host The real servers.
Location Where the end-user request comes from. A location is a collection of IP
addresses (or subnets). Locations are organized into areas.
SLA A metric representing the time, in milliseconds, that a normal interaction
of a specific type should take.
APM supports two SLA types:
• DC SLA—That is, the SLA on the data-center time.
• End User SLA—That is, the SLA on the total user experience time
(network time + data-center time + rendering time).
You can define an SLA per application, transaction, or location.

Figure 14: Application-Transaction-Event Diagram
How APM Works

APM monitors your Web application and end-user experience using dedicated collectors. The Page
Collector is a small and efficient JavaScript that is automatically embedded into the Web application
pages. The Page Collector gathers real-user measurements when running within the user's browser.
It monitors every user request and reports the related network and browser-rendering time. The
FastView adds the data-center latency information and sends the consolidated report to the
SharePath server. The SharePath server processes the report, analyzes it, and publishes it to the
dashboards.
One SharePath server supports the APM functionality. The SharePath server is an OVA installation in
a VMware vSphere environment.
When the APM option is enabled in the configuration of the application, the device sends application-
performance data to the SharePath server. The SharePath server traces transactions and
automatically uses the data to create an accurate, real-time representation of the environment and
true measurements of service-level performance. Then, SharePath can let you know whether any
applications require attention.
You can access the main page of the APM Web interface from the FastView GUI. Alternatively, you
can access the APM Web interface displaying the statistics of a specific application using the
configuration of the associated virtual service.
The following diagram illustrates the time statistics collected by the Radware APM solution.

Figure 15: Time Statistics Collected by the Radware APM Solution
The reporting server analyzes the data in different forms, such as:
• Aggregation on application level-server IP address/port or traffic pattern
• Aggregation on transaction level-collection of URLs per application
• Geographical-location-based pivoting
• Pivoting by real servers
• Built-in SLA tracking
APM Configuration Requirements and Limitations

APM is supported only for FastView devices version 5.0 and later.
Note: For information on the requirements, deployment, and initial configuration of the SharePath
server, see Installation, page 37.

APM Requirements
To support APM functionality, the following conditions must be met:
• The traffic received must be HTTP/HTTPS.
• The traffic that received must be clear text. That is, APM cannot work with traffic that another
network element has compressed or encrypted. To support APM functionality for compressed
traffic, the FastView device must compress the traffic (using a compression policy on the virtual
service).
• SSH must be enabled and properly configured. SSH must be enabled, and, the SSH port must be
the same as the value in the SSH Port text box in the Device Properties dialog box.
• The virtual server on which the virtual service runs must be configured with IPv4.
• In the configuration of the virtual service, the value in the Real Server Port text box must be
0 or 80.
• In the configuration of the virtual service, the Delayed Binding option must be Force Proxy.
• On an HTTPS virtual service with back-end SSL traffic:
— You must configure the SSL parameters (Server Certificate Type, Server Certificate, and
SSL Policy) on the virtual service.
— Server Certificate Type must be Certificate.
— In the configuration of the SSL policy, the value of Backend SSL Encryption must be Enable.
APM Limitations
The current version has the following limitations regarding APM:
• The rate of performance reports on a specific HTML page is limited to 500 per second.
• The number of distinct transaction (URIs) per application is limited to 100.
SharePath Server Deployment and Initial Configuration

To use the APM, you must configure the SharePath server that is customized to work with FastView
APM. The server installation is in an Open Virtualization format file. The administrator deploys the
file in a VMware vSphere environment. The SharePath server runs on VMware vSphere 4.1, virtual
machine version 7. During OVF deployment, you attach the network interfaces based on the Linux
configuration.
This SharePath server installation requires an existing VMware vSphere environment. For
information on VMware installation procedures and details of OVF deployment, see the VMware
documentation.
The configuration of the SharePath server includes a network adapter for APM management and
data traffic.
Device Configuration and Results

Authorized users can enable APM on a virtual service. Once APM is enabled on the virtual service and
the configuration is applied, FastView creates an application domain in the SharePath server.
Caution: If the instance of the SharePath server is replaced without restoring the previous
database, the system administrator must reapply the APM configuration on each virtual service.

To configure and apply APM:

• FastView requires SSH access to run CLI commands. Therefore, SSH must be enabled and
properly configured.
• A SharePath server must be already configured.
• In the configuration of the virtual service, the value in the Real Server Port text box must be
0 or 80.
Accessing the SharePath Web Interface—APM Dashboard

FastView provides users with the Administrator role a direct link to the APM dashboard. Additionally,
a user can access the SharePath Web interface using a Web browser with the following URL format:
http://<SharePath server IP address>/sharepath
The default username is admin, and the default password is correl.
To open the APM Web interface

1. In the FastView main window, select APM > Web Applications.
2. Double-click on one of the reports.
Monitoring Results
You can navigate to one of the dashboards for reports related to business requirements or real-time
and historical monitoring.
Reports related to business requirements include the following features:
• Aggregation on application level-server IP address/port or traffic pattern
• Aggregation on transaction level-collection of URLs per application
• Geographical-location-based pivoting
• Pivoting by real servers
• Built-in SLA tracking mechanism
Real-time and historical monitoring includes the following features:

• SLA Watch dashboard
• Global User Experience dashboard
• Application dashboard
Using APM to Troubleshoot High Latency

This section describes a step-by-step procedure that uses APM to troubleshoot high latency.
With APM, a good approach for troubleshooting high latency is to start looking for a generic problem.
Starting your troubleshooting from a specific user HTTP request might be misleading, at least in the
beginning, and might make the process unnecessarily longer. If you find no generic problem, move
your investigation to more specific potential problems. For example, if a user complains about the
responsiveness of an application, start checking whether the data center works as expected; and
only later, focus on the user’s location. If the problem is caused by a malfunctioning data center, this
affects many, if not all, users of that application, so solving the problem has a wide impact.

The following diagram illustrates the recommended approach for troubleshooting high latency using
APM. Each numbered shape has a corresponding detailed discussion after the diagram.
Figure 16: Troubleshooting High Latency with APM
1—Latency Problem
There are several reasons for you to start troubleshooting high latency. The application
responsiveness may be below the required SLA. Alternatively, you may receive a complaint from a
specific user or from the helpdesk.
The SLA Watch dashboard with Service Level set to End User displays the current performance of
the application from the user perspective. This will likely be your main dashboard. In many cases,
this will also be your starting point for investigating a high-latency issue.

A red %SLA value indicates that the user experience is unsatisfactory.

A green %SLA value indicates that overall, the application is behaving nominally. However, since
the value is aggregated across all user HTTP requests for the particular application, it is possible that
some transactions or specific requests are slow, causing the user to complain.
Radware recommends first checking the data-center performance for the particular application.
2—View Status of Data Center’s Application-Level SLA

The following screen displays the overall data-center performance of its applications.

If the %SLA value is red, you should drill down to data-center performance, either by going to step
3—Check Data Center’s Operation, page 217 and/or by going to step 4—Analyze Data Center’s
Transaction-Level SLA, page 217.
If the %SLA value is green, there might be some hidden problems with particular transactions or
requests. Therefore, the next troubleshooting step is 4—Analyze Data Center’s Transaction-Level
SLA, page 217.
3—Check Data Center’s Operation

You can investigate data-center performance by analyzing the Device Performance Reporting reports
and/or by moving to the Datacenter Intelligence dashboard. The most useful view in this dashboard
is Show—Processing Time with Root—Break down by Hosts.
Note: The scope of the Datacenter Intelligence dashboard should be limited to a single application.
This example shows the load of each of the hosts (real servers). The data can be correlated with the
Application Average Response Time and the Transaction Volume and Concurrency.
Using this data, you can identify which server has been running slowly and correlate the data with
the application response time and the load of the requests.
4—Analyze Data Center’s Transaction-Level SLA

You can observe data-center performance for a specific transaction in the Transactions tab of the
SLA Watch dashboard.

The red %SLA value indicates a problem with data-center performance for a specific transaction.
Because this issue was not identified at the application level, the volume of problematic requests
might be not very high (possibly due to the low volume of the transactions). Therefore, Radware
recommends that you browse the list of transaction instances (step 5—Check the List of Transaction
Instances, page 218; click the application or transaction).
When the data-center %SLA value is green for all transactions and users complain about poor
experience
, the next step is to identify the transaction with the problematic user SLA (step 6—Analyze the
User's Transaction-Level SLA, page 219).
5—Check the List of Transaction Instances

To access the list of transaction instances, from the Transactions tab of SLA Watch dashboard, click
on a particular transaction.

The Destination column indicates the real server that served that particular request.
6—Analyze the User's Transaction-Level SLA

You can see the user-experience SLA at the transaction level in the Transactions tab of the SLA
Watch dashboard.
The user-experience SLA status indicates the total user experience, which is affected by all three
components of transaction latency: data-center time, network time, and rendering time. At this
stage in the process, you should have already excluded the data-center performance problems, in
order to focus on the other two components.

Assuming that the SLA value aggregates the result of multiple requests from different locations:
• A red %SLA value indicates a general problem with the specific transaction. In this case, the
next step is step 7—Check for General Application Problem, page 220.
• A green %SLA value for the Transaction End User SLA implies that the problem is related to a
specific user condition, for example, network connectivity. In this case, the next step is step 8—
Check for User Networking Problems, page 220.
7—Check for General Application Problem

At this stage in the process, you know that although the data-center latency is within the SLA, most
if not all users are suffering from slow system responsiveness.
These causes can be related either to a generic application problem or to a general networking
problem of the site hosting the application.
A generic application problem can be caused by many factors related to the format and the content
of the Web page.
The following elements can increase the rendering time of the page:
• Sequentially loaded images
• Long-running Java scripts
• External elements such as social and advertising widgets from third parties loaded from external
sites
In parallel, Radware recommends that you check the overall network connectivity and performance
of the site (step 11—Check Global Network State, page 222).
8—Check for User Networking Problems

At this stage, you should investigate the networking problems of a specific user.
The Locations tab of the SLA Watch dashboard displays the SLAs per location.

After identifying a problematic location, you should investigate the following:

• Whether the high latency is related to the behavior of the user at that location (for example,
some pages are accessed only by users from a certain location, or pages are accessed only from
a certain location). You can validate this by investigating the list of transaction instances, as
described in step 5—Check the List of Transaction Instances, page 218.
• Whether some location has local networking problems. You can validate this by going to step 9—
Check Relative Latency at User Location, page 221.
9—Check Relative Latency at User Location

The Global User Experience dashboard displays the results of response and network time according
to user location.
Select Avg. Network Time to compare the network time in a particular location with the network
time at other locations.
This graph displays the following three average network times:

• Average network time at the selected location
• Average network time at the selected area excluding selected location
• Average network time from all locations excluding the selected area
This information helps to determine whether the network latency is specific to the location (step
10—Check for Network Problem at User's Location, page 221) or is a general problem experienced
by all users.
10—Check for Network Problem at User's Location

In this step, you should work with the remote team to identify the network bottlenecks along the
path.

11—Check Global Network State

In this step, you assume that the slow networking is experienced by all users of the system,
regardless of their location. One possible reason for this is a local spike in the load on the
application. Another possible reason is a general problem in the data-center networking, for
example, an edge firewall delaying traffic.
You can easily identify spikes by looking at the Application dashboard DataCenter %SLA and the
End User %SLA. These views display the current status of the application along with historical
baseline and activity statistics.
In addition, you can investigate reasons for high latency by looking for bottlenecks and data-center
failures in the overall networking status.

Radware Ltd. End User License Agreement
By accepting this End User License Agreement (this “License Agreement”) you agree to be contacted
by Radware Ltd.’s (“Radware”) sales personnel.
If you would like to receive license rights different from the rights granted below or if you wish to
acquire warranty or support services beyond the scope provided herein (if any), please contact
Radware’s sales team.
THIS LICENSE AGREEMENT GOVERNS YOUR USE OF ANY SOFTWARE DEVELOPED AND/OR
DISTRIBUTED BY RADWARE AND ANY UPGRADES, MODIFIED VERSIONS, UPDATES, ADDITIONS,
AND COPIES OF THE SOFTWARE FURNISHED TO YOU DURING THE TERM OF THE LICENSE
GRANTED HEREIN (THE “SOFTWARE”). THIS LICENSE AGREEMENT APPLIES REGARDLESS OF
WHETHER THE SOFTWARE IS DELIVERED TO YOU AS AN EMBEDDED COMPONENT OF A RADWARE
PRODUCT (“PRODUCT”), OR WHETHER IT IS DELIVERED AS A STANDALONE SOFTWARE PRODUCT.
FOR THE AVOIDANCE OF DOUBT IT IS HEREBY CLARIFIED THAT THIS LICENSE AGREEMENT
APPLIES TO PLUG-INS, CONNECTORS, EXTENSIONS AND SIMILAR SOFTWARE COMPONENTS
DEVELOPED BY RADWARE THAT CONNECT OR INTEGRATE A RADWARE PRODUCT WITH THE
PRODUCT OF A THIRD PARTY (COLLECTIVELY, “CONNECTORS”) FOR PROVISIONING,
DECOMMISSIONING, MANAGING, CONFIGURING OR MONITORING RADWARE PRODUCTS. THE
APPLICABILITY OF THIS LICENSE AGREEMENT TO CONNECTORS IS REGARDLESS OF WHETHER
SUCH CONNECTORS ARE DISTRIBUTED TO YOU BY RADWARE OR BY A THIRD PARTY PRODUCT
VENDOR. IN CASE A CONNECTOR IS DISTRIBUTED TO YOU BY A THIRD PARTY PRODUCT VENDOR
PURSUANT TO THE TERMS OF AN AGREEMENT BETWEEN YOU AND THE THIRD PARTY PRODUCT
VENDOR, THEN, AS BETWEEN RADWARE AND YOURSELF, TO THE EXTENT THERE IS ANY
DISCREPANCY OR INCONSISTENCY BETWEEN THE TERMS OF THIS LICENSE AGREEMENT AND THE
TERMS OF THE AGREEMENT BETWEEN YOU AND THE THIRD PARTY PRODUCT VENDOR, THE TERMS
OF THIS LICENSE AGREEMENT WILL GOVERN AND PREVAIL. PLEASE READ THE TERMS AND
CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE OPENING THE PACKAGE
CONTAINING RADWARE’S PRODUCT, OR BEFORE DOWNLOADING, INSTALLING, COPYING OR
OTHERWISE USING RADWARE’S STANDALONE SOFTWARE (AS APPLICABLE). THE SOFTWARE IS
LICENSED (NOT SOLD). BY OPENING THE PACKAGE CONTAINING RADWARE’S PRODUCT, OR BY
DOWNLOADING, INSTALLING, COPYING OR USING THE SOFTWARE (AS APPLICABLE), YOU
CONFIRM THAT YOU HAVE READ AND UNDERSTAND THIS LICENSE AGREEMENT AND YOU AGREE
TO BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT. FURTHERMORE, YOU HEREBY WAIVE
ANY CLAIM OR RIGHT THAT YOU MAY HAVE TO ASSERT THAT YOUR ACCEPTANCE AS STATED
HEREINABOVE IS NOT THE EQUIVALENT OF, OR DEEMED AS, A VALID SIGNATURE TO THIS LICENSE
AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS LICENSE
AGREEMENT, YOU SHOULD PROMPTLY RETURN THE UNOPENED PRODUCT PACKAGE OR YOU
SHOULD NOT DOWNLOAD, INSTALL, COPY OR OTHERWISE USE THE SOFTWARE (AS APPLICABLE).
THIS LICENSE AGREEMENT REPRESENTS THE ENTIRE AGREEMENT CONCERNING THE SOFTWARE
BETWEEN YOU AND RADWARE, AND SUPERSEDES ANY AND ALL PRIOR PROPOSALS,
REPRESENTATIONS, OR UNDERSTANDINGS BETWEEN THE PARTIES. “YOU” MEANS THE NATURAL
PERSON OR THE ENTITY THAT IS AGREEING TO BE BOUND BY THIS LICENSE AGREEMENT, THEIR
EMPLOYEES AND THIRD PARTY CONTRACTORS. YOU SHALL BE LIABLE FOR ANY FAILURE BY SUCH
EMPLOYEES AND THIRD PARTY CONTRACTORS TO COMPLY WITH THE TERMS OF THIS LICENSE
AGREEMENT.
1. License Grant. Subject to the terms of this Agreement, Radware hereby grants to you, and you
accept, a limited, nonexclusive, nontransferable license to install and use the Software in
machine-readable, object code form only and solely for your internal business purposes
(“Commercial License”). If the Software is distributed to you with a software development kit
(the “SDK”), then, solely with regard to the SDK, the Commercial License above also includes a
limited, nonexclusive, nontransferable license to install and use the SDK solely on computers
within your organization, and solely for your internal development of an integration or
interoperation of the Software and/or other Radware Products with software or hardware
products owned, licensed and/or controlled by you (the “SDK Purpose”). To the extent an SDK is
distributed to you together with code samples in source code format (the “Code Samples”) that
are meant to illustrate and teach you how to configure, monitor and/or control the Software
and/or any other Radware Products, the Commercial License above further includes a limited,

nonexclusive, nontransferable license to copy and modify the Code Samples and create
derivative works based thereon solely for the SDK Purpose and solely on computers within your
organization. The SDK shall be considered part of the term “Software” for all purposes of this
License Agreement. You agree that you will not sell, assign, license, sublicense, transfer, pledge,
lease, rent or share your rights under this License Agreement nor will you distribute copies of
the Software or any parts thereof. Rights not specifically granted herein, are specifically
prohibited.
2. Evaluation Use. Notwithstanding anything to the contrary in this License Agreement, if the
Software is provided to you for evaluation purposes, as indicated in your purchase order or sales
receipt, on the website from which you download the Software, as inferred from any time-
limited evaluation license keys that you are provided with to activate the Software, or otherwise,
then You may use the Software only for internal evaluation purposes (“Evaluation Use”) for a
maximum of 30 days or such other duration as may specified by Radware in writing at its sole
discretion (the “Evaluation Period”). The evaluation copy of the Software contains a feature that
will automatically disable it after expiration of the Evaluation Period. You agree not to disable,
destroy, or remove this feature of the Software, and any attempt to do so will be a material
breach of this License Agreement. During or at the end of the evaluation period, you may
contact Radware sales team to purchase a Commercial License to continue using the Software
pursuant to the terms of this License Agreement. If you elect not to purchase a Commercial
License, you agree to stop using the Software and to delete the evaluation copy received
hereunder from all computers under your possession or control at the end of the Evaluation
Period. In any event, your continued use of the Software beyond the Evaluation Period (if
possible) shall be deemed your acceptance of a Commercial License to the Software pursuant to
the terms of this License Agreement, and you agree to pay Radware any amounts due for any
applicable license fees at Radware’s then-current list prices.
3. Subscription Software. If you licensed the Software on a subscription basis, your rights to use
the Software are limited to the subscription period. You have the option to extend your
subscription. If you extend your subscription, you may continue using the Software until the end
of your extended subscription period. If you do not extend your subscription, after the expiration
of your subscription, you are legally obligated to discontinue your use of the Software and
completely remove the Software from your system.
4. Feedback. Any feedback concerning the Software including, without limitation, identifying
potential errors and improvements, recommended changes or suggestions (“Feedback”),
provided by you to Radware will be owned exclusively by Radware and considered Radware’s
confidential information. By providing Feedback to Radware, you hereby assign to Radware all of
your right, title and interest in any such Feedback, including all intellectual property rights
therein. With regard to any rights in such Feedback that cannot, under applicable law, be
assigned to Radware, you hereby irrevocably waives such rights in favor of Radware and grants
Radware under such rights in the Feedback, a worldwide, perpetual royalty-free, irrevocable,
sub-licensable and non-exclusive license, to use, reproduce, disclose, sublicense, modify, make,
have made, distribute, sell, offer for sale, display, perform, create derivative works of and
otherwise exploit the Feedback without restriction. The provisions of this Section 4 will survive
the termination or expiration of this Agreement.
5. Limitations on Use. You agree that you will not: (a) copy, modify, translate, adapt or create
any derivative works based on the Software; or (b) sublicense or transfer the Software, or
include the Software or any portion thereof in any product; or (b) reverse assemble,
disassemble, decompile, reverse engineer or otherwise attempt to derive source code (or the
underlying ideas, algorithms, structure or organization) from the Software, in whole or in part,
or in any instance where the law permits any such action, you agree to provide Radware at least
ninety (90) days advance written notice of your belief that such action is warranted and
permitted and to provide Radware with an opportunity to evaluate if the law’s requirements
necessitate such action; or (c) create, develop, license, install, use, or deploy any software or
services to circumvent, enable, modify or provide access, permissions or rights which violate the
technical restrictions of the Software; (d) in the event the Software is provided as an embedded
or bundled component of another Radware Product, you shall not use the Software other than as
part of the combined Product and for the purposes for which the combined Product is intended;
(e) remove any copyright notices, identification or any other proprietary notices from the
Software (including any notices of Third Party Software (as defined below); or (f) copy the

Software onto any public or distributed network or use the Software to operate in or as a time-
sharing, outsourcing, service bureau, application service provider, or managed service provider
environment. Notwithstanding Section 5(d), if you provide hosting or cloud computing services
to your customers, you are entitled to use and include the Software in your IT infrastructure on
which you provide your services. It is hereby clarified that the prohibitions on modifying, or
creating derivative works based on, any Software provided by Radware, apply whether the
Software is provided in a machine or in a human readable form. It is acknowledged that
examples provided in a human readable form may be modified by a user.
6. Intellectual Property Rights. You acknowledge and agree that this License Agreement does
not convey to you any interest in the Software except for the limited right to use the Software,
and that all right, title, and interest in and to the Software, including any and all associated
intellectual property rights, are and shall remain with Radware or its third party licensors. You
further acknowledge and agree that the Software is a proprietary product of Radware and/or its
licensors and is protected under applicable copyright law.
7. No Warranty. The Software, and any and all accompanying software, files, libraries, data and
materials, are distributed and provided “AS IS” by Radware or by its third party licensors (as
applicable) and with no warranty of any kind, whether express or implied, including, without
limitation, any non-infringement warranty or warranty of merchantability or fitness for a
particular purpose. Neither Radware nor any of its affiliates or licensors warrants, guarantees, or
makes any representation regarding the title in the Software, the use of, or the results of the
use of the Software. Neither Radware nor any of its affiliates or licensors warrants that the
operation of the Software will be uninterrupted or error-free, or that the use of any passwords,
license keys and/or encryption features will be effective in preventing the unintentional
disclosure of information contained in any file. You acknowledge that good data processing
procedure dictates that any program, including the Software, must be thoroughly tested with
non-critical data before there is any reliance on it, and you hereby assume the entire risk of all
use of the copies of the Software covered by this License. Radware does not make any
representation or warranty, nor does Radware assume any responsibility or liability or provide
any license or technical maintenance and support for any operating systems, databases,
migration tools or any other software component provided by a third party supplier and with
which the Software is meant to interoperate.
This disclaimer of warranty constitutes an essential and material part of this License.
In the event that, notwithstanding the disclaimer of warranty above, Radware is held liable
under any warranty provision, Radware shall be released from all such obligations in the event
that the Software shall have been subject to misuse, neglect, accident or improper installation,
or if repairs or modifications were made by persons other than by Radware’s authorized service
personnel.
8. Limitation of Liability. Except to the extent expressly prohibited by applicable statutes, in no
event shall Radware, or its principals, shareholders, officers, employees, affiliates, licensors,
contractors, subsidiaries, or parent organizations (together, the “Radware Parties”), be liable for
any direct, indirect, incidental, consequential, special, or punitive damages whatsoever relating
to the use of, or the inability to use, the Software, or to your relationship with, Radware or any
of the Radware Parties (including, without limitation, loss or disclosure of data or information,
and/or loss of profit, revenue, business opportunity or business advantage, and/or business
interruption), whether based upon a claim or action of contract, warranty, negligence, strict
liability, contribution, indemnity, or any other legal theory or cause of action, even if advised of
the possibility of such damages. If any Radware Party is found to be liable to You or to any third-
party under any applicable law despite the explicit disclaimers and limitations under these
terms, then any liability of such Radware Party, will be limited exclusively to refund of any
license or registration or subscription fees paid by you to Radware.
9. Third Party Software. The Software includes software portions developed and owned by third
parties (the “Third Party Software”). Third Party Software shall be deemed part of the Software
for all intents and purposes of this License Agreement; provided, however, that in the event that
a Third Party Software is a software for which the source code is made available under an open
source software license agreement, then, to the extent there is any discrepancy or inconsistency
between the terms of this License Agreement and the terms of any such open source license
agreement (including, for example, license rights in the open source license agreement that are

broader than the license rights set forth in Section 1 above and/or no limitation in the open
source license agreement on the actions set forth in Section 5 above), the terms of any such
open source license agreement will govern and prevail. The terms of open source license
agreements and copyright notices under which Third Party Software is being licensed to
Radware or a link thereto, are included with the Software documentation or in the header or
readme files of the Software. Third Party licensors and suppliers retain all right, title and interest
in and to the Third Party Software and all copies thereof, including all copyright and other
intellectual property associated therewith. In addition to the use limitations applicable to Third
Party Software pursuant to Section 5 above, you agree and undertake not to use the Third Party
Software as a general SQL server, as a stand-alone application or with applications other than
the Software under this License Agreement.
10. Term and Termination. This License Agreement is effective upon the first to occur of your
opening the package of the Product, purchasing, downloading, installing, copying or using the
Software or any portion thereof, and shall continue until terminated. However, sections 4-14
shall survive any termination of this License Agreement. The Licenses granted under this License
Agreement are not transferable and will terminate upon: (i) termination of this License
Agreement, or (ii) transfer of the Software, or (iii) in the event the Software is provided as an
embedded or bundled component of another Radware Product, when the Software is un-bundled
from such Product or otherwise used other than as part of such Product. If the Software is
licensed on subscription basis, this Agreement will automatically terminate upon the termination
of your subscription period if it is not extended.
11. Export. The Software or any part thereof may be subject to export or import controls under
applicable export/import control laws and regulations including such laws and regulations of the
United States and/or Israel. You agree to comply with such laws and regulations, and, agree not
to knowingly export, re-export, import or re-import, or transfer products without first obtaining
all required Government authorizations or licenses therefor. Furthermore, You hereby covenant
and agree to ensure that your use of the Software is in compliance with all other foreign,
federal, state, and local laws and regulations, including without limitation all laws and
regulations relating to privacy rights, and data protection. You shall have in place a privacy
policy and obtain all of the permissions, authorizations and consents required by applicable law
for use of cookies and processing of users’ data (including without limitation pursuant to
Directives 95/46/EC, 2002/58/EC and 2009/136/EC of the EU if applicable) for the purpose of
provision of any services.
12. US Government. To the extent you are the U.S. government or any agency or instrumentality
thereof, you acknowledge and agree that the Software is a “commercial computer software” and
“commercial computer software documentation” pursuant to applicable regulations and your use
of the is subject to the terms of this License Agreement.
13. Governing Law. This License Agreement shall be construed and governed in accordance with
the laws of the State of Israel.
14. Miscellaneous. If a judicial determination is made that any of the provisions contained in this
License Agreement is unreasonable, illegal or otherwise unenforceable, such provision or
provisions shall be rendered void or invalid only to the extent that such judicial determination
finds such provisions to be unreasonable, illegal or otherwise unenforceable, and the remainder
of this License Agreement shall remain operative and in full force and effect. In any event a
party breaches or threatens to commit a breach of this License Agreement, the other party will,
in addition to any other remedies available to, be entitled to injunction relief. This License
Agreement constitutes the entire agreement between the parties hereto and supersedes all prior
agreements between the parties hereto with respect to the subject matter hereof. The failure of
any party hereto to require the performance of any provisions of this License Agreement shall in
no manner affect the right to enforce the same. No waiver by any party hereto of any provisions
or of any breach of any provisions of this License Agreement shall be deemed or construed
either as a further or continuing waiver of any such provisions or breach waiver or as a waiver of
any other provision or breach of any other provision of this License Agreement.

IF YOU DO NOT AGREE WITH THE TERMS OF THIS LICENSE YOU MUST REMOVE THE
SOFTWARE FROM ANY DEVICE OWNED BY YOU AND IMMIDIATELY CEASE USING THE
SOFTWARE.
COPYRIGHT © 2015, Radware Ltd. All Rights Reserved.

Fastview Installation and User Guide: Software Version 6.3

Uploaded by

Copyright:

Available Formats

Fastview Installation and User Guide: Software Version 6.3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fastview Installation and User Guide: Software Version 6.3

Uploaded by

Copyright:

Available Formats

FastView Installation and User Guide

Software Version 6.3

2 Document ID: RDWR-FW_V63_IUG1510

Document ID: RDWR-FW_V63_IUG1510 3

4 Document ID: RDWR-FW_V63_IUG1510

Notice traitant du copyright

Document ID: RDWR-FW_V63_IUG1510 5

Ce produit inclut un logiciel développé par Wesley Griffin.

6 Document ID: RDWR-FW_V63_IUG1510

Document ID: RDWR-FW_V63_IUG1510 7

8 Document ID: RDWR-FW_V63_IUG1510

Limitations on Warranty and Liability

Limitations on Warranty and Liability

Limitations de la Garantie et Responsabilité

Haftungs- und Gewährleistungsausschluss

Document ID: RDWR-FW_V63_IUG1510 9

ODER EINE BEGRENZUNG STILLSCHWEIGENDER GARANTIEN ODER HAFTUNGEN BEZÜGLICH

Figure 1: Electrical Shock Hazard Label

DUAL-POWER-SUPPLY-SYSTEM SAFETY WARNING IN CHINESE

Figure 2: Dual-Power-Supply-System Safety Warning in Chinese

Translation of Dual-Power-Supply-System Safety Warning in Chinese:

10 Document ID: RDWR-FW_V63_IUG1510

Document ID: RDWR-FW_V63_IUG1510 11

This marking or statement includes the following text warning:

To connect the power connection:

12 Document ID: RDWR-FW_V63_IUG1510

Figure 3: Étiquette d’avertissement de danger de chocs électriques

AVERTISSEMENT DE SÉCURITÉ POUR LES SYSTÈMES DOTÉS DE DEUX SOURCES D’ALIMENTATION

Document ID: RDWR-FW_V63_IUG1510 13

14 Document ID: RDWR-FW_V63_IUG1510

Cette marque ou remarque inclut l’avertissement textuel suivant:

Pour brancher à l’alimentation électrique:

Document ID: RDWR-FW_V63_IUG1510 15

Risque de choc et de danger électriques. Le débranchement d’une seule alimentation stabilisée ne

Figure 5: Warnetikett Stromschlaggefahr

SICHERHEITSHINWEIS IN CHINESISCHER SPRACHE FÜR SYSTEME MIT DOPPELSPEISUNG

Figure 6: Sicherheitshinweis in chinesischer Sprache für Systeme mit Doppelspeisung

16 Document ID: RDWR-FW_V63_IUG1510

Übersetzung von Sicherheitshinweis in chinesischer Sprache für Systeme mit Doppelspeisung:

Document ID: RDWR-FW_V63_IUG1510 17

Diese Markierung oder Erklärung enthält den folgenden Warntext:

Anschluss des Stromkabels:

18 Document ID: RDWR-FW_V63_IUG1510

Figure 7: Statement for Class A VCCI-certified Equipment

Translation of Statement for Class A VCCI-certified Equipment:

Figure 8: KCC—Korea Communications Commission Certificate of Broadcasting and Communication

Document ID: RDWR-FW_V63_IUG1510 19

Figure 9: Statement For Class A KCC-certified Equipment in Korean

Translation of Statement For Class A KCC-certified Equipment in Korean:

Figure 10: Statement for Class A BSMI-certified Equipment

Translation of Statement for Class A BSMI-certified Equipment:

Déclarations sur les Interférences Électromagnétiques

Figure 11: Déclaration pour l’équipement de classe A certifié VCCI

Traduction de la Déclaration pour l’équipement de classe A certifié VCCI:

20 Document ID: RDWR-FW_V63_IUG1510

Translation de la Déclaration pour l’équipement de classe A certifié KCC en langue coréenne:

Figure 14: Déclaration pour l’équipement de classe A certifié BSMI

Translation de la Déclaration pour l’équipement de classe A certifié BSMI:

Erklärungen zu Elektromagnetischer Interferenz