AlteonOS 30 5 11 Troubleshooting Guide

Alteon
TROUBLSHOOTING GUIDE
Software Version 30.5.11

Document ID: RDWR-ALOS-V30511-TSG1901 January, 2019
Alteon Troubleshooting Guide
2 Document ID: RDWR-ALOS-V30511-TSG1901

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:
HiddenComment: The following text is for AppShape++ [Output attr=AS++].
The AppShape++ Script Files provided by Radware Ltd. are subject to the Special License Terms
included in each of the electronic AppShape++ Script Files and are also subject to Radware’s End
User License Agreement, a copy of which (as may be amended from time to time) can be found at
the end of this document or at http://www.radware.com/Resources/eula.html.
Please note that if you create your own scripts using any AppShape++ Scripts provided by Radware,
such self-created scripts are not controlled by Radware and therefore Radware will not be liable for
any malfunctions resulting from such self-created scripts.
Copyright Radware Ltd. 2019. 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 suivantes:
Les applications AppShape++ Script Files fournies par Radware Ltd. sont soumises aux termes de la
Licence Spéciale (“Special License Terms”) incluse dans chaque fichier électronique “AppShape++
Script Files” mais aussi au Contrat de Licence d’Utilisateur Final de Radware qui peut être modifié de
temps en temps et dont une copie est disponible à la fin du présent document ou à l’adresse
suivante: http://www.radware.com/Resources/eula.html.
Nous attirons votre attention sur le fait que si vous créez vos propres fichiers de commande (fichiers
“script”) en utilisant l’application “AppShape++ Script Files” fournie par Radware, ces fichiers
“script” ne sont pas contrôlés par Radware et Radware ne pourra en aucun cas être tenue
responsable des dysfonctionnements résultant des fichiers “script” ainsi créés.
Copyright Radware Ltd. 2019. 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.
Document ID: RDWR-ALOS-V30511-TSG1901 3

Wichtige Anmerkung
Dieses Handbuch wird vorbehaltlich folgender Bedingungen und Einschränkungen ausgeliefert:
Die von Radware Ltd bereitgestellten AppShape++ Scriptdateien unterliegen den in jeder
elektronischen AppShape++ Scriptdatei enthalten besonderen Lizenzbedingungen sowie Radware’s
Endbenutzer-Lizenzvertrag (von welchem eine Kopie in der jeweils geltenden Fassung am Ende
dieses Dokuments oder unter http://www.radware.com/Resources/eula.html erhältlich ist).
Bitte beachten Sie, dass wenn Sie Ihre eigenen Skripte mit Hilfe eines von Radware bereitgestellten
AppShape++ Skripts erstellen, diese selbsterstellten Skripte nicht von Radware kontrolliert werden
und Radware daher keine Haftung für Funktionsfehler übernimmt, welche von diesen selbsterstellten
Skripten verursacht werden.
Copyright Radware Ltd. 2019. 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.
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.
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and
the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both
licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL,
please contact [email protected].
OpenSSL License
Copyright (c) 1998-2011 The OpenSSL Project. 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. All advertising materials mentioning features or use of this software must display the following
acknowledgement:
This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit. (http://www.openssl.org/)
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote
products derived from this software without prior written permission. For written permission,
please contact [email protected].

5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in
their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
“This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR 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) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young ([email protected]). This
product includes software written by Tim Hudson ([email protected]).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young ([email protected])
All rights reserved.
This package is an SSL implementation written by Eric Young ([email protected]).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are
aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution
is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be
removed.
If this package is used in a product, Eric Young should be given attribution as the author of the parts
of the library used.
This can be in the form of a textual message at program startup or in documentation (online or
textual) provided with the package.
1. Redistributions of source code must retain the copyright notice, this list of conditions and the
following disclaimer.
distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement:
"This product includes cryptographic software written by Eric Young ([email protected])"
The word 'cryptographic' can be left out if the rouines from the library being used are not
cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory
(application code) you must include an acknowledgment:
"This product includes software written by Tim Hudson ([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “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. IN NO EVENT
SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR 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) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
The licence and distribution terms for any publically available version or derivative of this code
cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence
[including the GNU Public Licence.]
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.
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

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.
HiddenComment: The following text, which is yet to be translated into French and German, April
2015, from Hanna Mordichai, was added for APM. Vision only [Output attr=Vision_OLH Vision_UG].
This product includes the DB2 Express-C database, the copyrights of which are owned IBM.
HiddenComment: The following text is for AppWall [Output attr=appwall], which is yet to be
translated into French and German. 26 January 2012 from Hanna Mordichai and Gadi M.
This product contains a Access Protocol API developed by The OpenLDAP Foundation titled
“OpenLDAP Lightweight Directory Access Protocol API”. Copyright 1999-2003 The OpenLDAP
Foundation, Redwood City, California, USA. All Rights Reserved.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
The following license terms apply to the openLDAP Access Protocol API, including, without
limitations, the below list of conditions and disclaimer:
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation (“Software”), with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions in source form must retain copyright statements and notices,
2. Redistributions in binary form must reproduce applicable copyright statements and notices, this
list of conditions, and the following disclaimer in the documentation and/or other materials
provided with the distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished
by a version number. You may use this Software under terms of this license revision or under the
terms of any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS “AS IS”
AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR
OWNER(S) OF THE SOFTWARE BE LIABLE FOR 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) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The names of the authors and copyright holders must not be used in advertising or otherwise to
promote the sale, use or other dealing in this Software without specific, written prior permission.
Title to copyright in this Software shall at all times remain with copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation. Copyright 1999-2003 The
OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission to copy and
distribute verbatim copies of this document is granted.

This product contains the ACE RADIUS library developed by Mr. Alex Agranov. Copyright ©2004-
2009, Alex Agranov <[email protected]> All rights reserved.
The ACE RADIUS library is licensed under BSD License, which allows its use both in open-source and
commercial projects.
The license terms are as follows:
• Redistributions of source code must retain the above copyright notice, this list of conditions, and
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions,
distribution.
• Neither the name of ace-radius nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR 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) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software includes the SNMP++v3.2.25 library Copyright ©2001-2010 Jochen Katz, Frank Fock
The SNMP++v3.2.25 library is based on SNMP++2.6 from Hewlett Packard: Copyright ©1996
Hewlett-Packard Company
ATTENTION: USE OF THIS SOFTWARE IS SUBJECT TO THE FOLLOWING TERMS.
Permission to use, copy, modify, distribute and/or sell this software and/or its documentation is
hereby granted without fee. User agrees to display the above copyright notice and this license notice
in all copies of the software and any documentation of the software. User agrees to assume all
liability for the use of the software; Hewlett-Packard and Jochen Katz make no representations
about the suitability of this software for any purpose. It is provided “AS-IS” without warranty of any
kind, either express or implied. User hereby grants a royalty-free license to any and all derivatives
based upon this software code base.
Stuttgart, Germany, Thu Sep 2 00:07:47 CEST 2010
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.
Ce produit renferme des codes développés dans le cadre du projet OpenSSL.
Ce produit inclut un logiciel développé dans le cadre du projet OpenSSL. Pour un usage dans la boîte
à outils OpenSSL (http://www.openssl.org/).
Copyright ©1998-2005 Le projet OpenSSL. Tous droits réservés. Ce produit inclut la catégorie de
chiffre Rijndael.
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.
Dieses Produkt enthält einen vom OpenSSL-Projekt entwickelten Code
Dieses Produkt enthält vom OpenSSL-Projekt entwickelte Software. Zur Verwendung im OpenSSL
Toolkit (http://www.openssl.org/).
Copyright ©1998-2005 The OpenSSL Project. Alle Rechte vorbehalten. Dieses Produkt enthält die
Rijndael cipher.
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.
The service provided by Radware is warranted solely pursuant to the provisions of the Service Level
Agreement between Radware and you.
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.

EXCEPT AS SET FORTH ABOVE, ALL RADWARE PRODUCTS AND SERVICES ARE PROVIDED “AS IS”
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
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.
Les seules garanties pour le service fourni par Radware sont celles stipulées dans le Contrat de
Niveau de Service conclu entre Radware et vous.
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’ADÉQUATION À UNE UTILISATION PARTICULIÈRE.
SAUF STIPULATION CONTRAIRE SUSMENTIONNÉE, TOUS LES PRODUITS ET SERVICES RADWARE
SONT FOURNIS “EN L'ÉTAT” ET TOUTE GARANTIE, QU’ELLE SOIT EXPRESSE OU IMPLICITE, EN CE
COMPRIS NOTAMMENT, LA GARANTIE IMPLICITE DE VALEUR MARCHANDE ET D'ADÉQUATION À UN
USAGE PARTICULIER, EST EXCLUE.

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.
Für die von Radware zu erbringende Leistung wird lediglich eine Gewährleistung anhand der
Bestimmungen im Dienstleistungsvertrag, der zwischen Radware und Ihnen abgeschlossen wurde,
übernommen.
übernommen.
übernommen.
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.
SOFERN WEITER OBEN NICHTS ANDERES VEREINBART WURDE, WERDEN DIE VON RADWARE ZU
LIEFERNDEN PRODUKTE UND ZU ERBRINGENDEN LEISTUNGEN “WIE BESEHEN” GELIEFERT/
ERBRACHT. AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNGEN,
EINSCHLIESSLICH, JEDOCH NICHT NUR, DIE STILLSCHWEIGENDE GEWÄHRLEISTUNG DER
MARKTGÄNGIGKEIT UND EIGNUNG FÜR EINEN SPEZIELLEN ZWECK, SIND 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 changedMar12],
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 changedMar12], 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
changedMar12], 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

HiddenComment: Added “Statement For Class A KCC-certified Equipment in Korean” per instruction
from Yaniv Ben Dor 26 Jan. 2012, in SG_Changed KCC Guide.pdf. Note that copying the Korean text
from the PDF into this FM doc was fine and distilled using print-to-file and distillation, but the built-in
File>Print As PDF did not work. Here is the text in Korean from the PDF:
이 기기는 업무용 (A 급 ) 전자파적합기기로서 판
매자 또는 사용자는 이 점을 주의하시기 바라
며 , 가정외의 지역에서 사용하는 것을 목적으로
합니다 .
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:
Can use IPv6 (128-bit Peut utiliser IPv6 Kann sowohl IPv6 (128-
addresses) as well as (adresses 128-bit,) ainsi Bit Adressen) als auch
IPv4 (32-bit addresses) que IPv4 (adresses 32- IPv4 (32-Bit Adressen)
IPv6 Ready bit) verwenden


Table of Contents
Table of Contents
Important Notices .......................................................................................................... 3
Copyright Notices .......................................................................................................... 4
Standard Warranty ...................................................................................................... 11
Limitations on Warranty and Liability ........................................................................... 13
Safety Instructions ....................................................................................................... 14
Electromagnetic-Interference Statements ................................................................... 24
Altitude and Climate Warning ...................................................................................... 28
Document Conventions ............................................................................................... 29
Chapter 1 – Introduction......................................................................................... 35
Alteon Platforms and Versions .................................................................................... 35
Reference Documents ................................................................................................. 35
When Requesting Technical Support .......................................................................... 35
Network Topology Diagram ................................................................................................. 35
Changes to Your System or Network .................................................................................. 36
Acronyms .................................................................................................................... 36
Chapter 2 – Gathering Troubleshooting Information .......................................... 39

Information Menus ....................................................................................................... 39
System Information Menu .................................................................................................... 40
SNMPv3 Information Menu .................................................................................................. 40
Layer 2 Information Menu .................................................................................................... 41
Layer 3 Information Menu .................................................................................................... 41
SLB (Layers 4 through 7) Information Menu ........................................................................ 41
Bandwidth Management Information Menu ......................................................................... 42
Security Information Menu ................................................................................................... 42
Maintenance Menus .................................................................................................... 43
Forwarding Database (FDB) Manipulation Menu ................................................................ 43
ARP Menu ........................................................................................................................... 44
IP Route Manipulation Menu ............................................................................................... 45
Application Services Trace Log (Applog) Menu ................................................................... 46
Statistics Menus .......................................................................................................... 46
Viewing General System Information .......................................................................... 47
Initial Screen for Alteon Platforms ....................................................................................... 47
Viewing the Software Version ...................................................................................... 48
Viewing Software Keys and License Information ........................................................ 48
Viewing System Capacity ............................................................................................ 49
Collecting Management Processor Statistics .............................................................. 50
CPU Usage ......................................................................................................................... 50

Table of Contents
Memory Statistics ................................................................................................................ 51

MP Packet Statistics ........................................................................................................... 51
Collecting Switch Processor Statistics ........................................................................ 51
SP Statistics ........................................................................................................................ 52
SP Maintenance Statistics .................................................................................................. 52
Viewing Port Information and Statistics ..................................................................... 53
Viewing GSLB Information ........................................................................................ 54
Determining the Master and Backup .......................................................................... 55
Events Notification ...................................................................................................... 55
Syslog Messaging ............................................................................................................... 56
Syslog Log File .................................................................................................................... 56
SNMP Traps ........................................................................................................................ 56
E-mail .................................................................................................................................. 57
Console ............................................................................................................................... 57
Session Table ............................................................................................................ 57
Chapter 3 – Troubleshooting Tools ...................................................................... 59

Port Mirroring .............................................................................................................. 59
Mirroring Individual Ports ..................................................................................................... 59
Mirroring VLANs on a Port .................................................................................................. 60
Dumps ........................................................................................................................ 62
TS Dump ............................................................................................................................. 62
TCP Dump (Packet Capture) .............................................................................................. 63
SSL Dump ........................................................................................................................... 64
Panic Dumps ....................................................................................................................... 64
Uploading the Dumps .......................................................................................................... 66
Filtering the Session Dump ................................................................................................. 66
Application Log ........................................................................................................... 67
Exporting Applog Files ........................................................................................................ 68
Loading an Alternate Configuration ............................................................................ 68
Trace Buffers ............................................................................................................. 69
Chapter 4 – Troubleshooting Fundamentals and Techniques ........................... 71

Diagnosing Link (Layer 1) Issues ............................................................................... 71
Diagnosing Connectivity Issues .................................................................................. 72
Diagnosing Layer 2 Issues ......................................................................................... 72
Diagnosing Network (Layer 3) Issues ......................................................................... 74
Diagnosing SLB (Layer 4) Issues ............................................................................... 76
Diagnosing Layer 7 Issues ......................................................................................... 77
Chapter 5 – Troubleshooting Hardware Issues ................................................... 79

LED Indicators ........................................................................................................... 79

Table of Contents
CPU Temperature ...................................................................................................... 79

Fan Failure ................................................................................................................. 79
Alteon 10000 Hardware Issues ................................................................................... 80
Alteon 10000 LED Indicators ............................................................................................... 81
IPMI Connectivity ................................................................................................................. 82
Fan Tray .............................................................................................................................. 82
Power Supply ...................................................................................................................... 82
Switch Blade ........................................................................................................................ 83
Switch Extension ................................................................................................................. 83
Payload Blades .................................................................................................................... 83
Chapter 6 – Troubleshooting Scenarios ............................................................... 85

Troubleshooting Table ................................................................................................. 85
Chapter 7 – Emergency Recovery Tree ................................................................ 87

Cannot Access AlteonOS for Management ................................................................. 87
VIP is Not Working ...................................................................................................... 88
Interface is Down ......................................................................................................... 94
VRRP is Flapping ........................................................................................................ 95
High MP CPU Utilization .............................................................................................. 99
Gateway Failure ....................................................................................................... 100
Panic ........................................................................................................................ 101
Real Server Down .................................................................................................... 102
Radware Ltd. End User License Agreement ............................................................ 107

Table of Contents

Chapter 1 – Introduction
This guide is intended for network administrators operating an Alteon system. It provides a synopsis
of troubleshooting guidelines and fundamentals associated with the Alteon system. It details the
troubleshooting tools available with the Alteon system.
Alteon Platforms and Versions

Alteon is a flexible and multi-functional ADC platform. It supports a diverse range of network
architectures and protocols. This guide provides information on troubleshooting and isolating
problems you may encounter using the various Alteon platforms and versions, and describes the
diagnostic tools available.
Reference Documents
As part of initial troubleshooting, Radware recommends that you ensure that you are familiar with
the operation of the Alteon system and that all commands and operations were activated properly.
Refer to the following Alteon documents for the applicable version and platform:
• Alteon Application Switch Operating System Release Notes
• Alteon Application Switch Operating System Application Guide
• Alteon Application Switch Operating System Command Reference
• Alteon Application Switch Operating System Web Based Management Quick Start
• Alteon Application Switch Operating System AppShape++ Reference Guide
• Radware Alteon Installation and Maintenance Guide
In addition, Radware recommends that you check the online Knowledge Base for known issues and
solutions related to the problem you are experiencing.
Radware’s Knowledge Base can be found at http://kb.radware.com/.
When Requesting Technical Support

When requesting technical support, you will be asked to provide some basic information regarding
your Alteon system (version and platform), network topology, and the problem details.
You may be asked to gather and provide system information and dumps, sniffer traces, as well as
any feature-specific information, depending on the specific problem.
Network Topology Diagram

You should always have a detailed and accurate topology diagram of your network maintained,
showing all the nodes and connections. This visual depiction of your network is very helpful to
Radware Technical Support personnel when they assess your problem.

Introduction
Changes to Your System or Network

When troubleshooting a problem, verify if anything has been recently changed in your network. The
following are a few questions that can help you analyze and document any changes to your system
network:
• Is this an existing installation or a new installation (that is, did it ever work)?
• When did the problem begin?
• Is the problem intermittent or does it happen every time?
• Have you recently changed or upgraded your system, your network, or a custom application?
For example, has any configuration or code been changed?
• What events can be identified prior to the trouble occurring?
For example, was there an upgrade, a LAN change, increased traffic, or new hardware?
Acronyms
This guide uses the following acronyms:
Table 1: Acronyms
Acronym Definition
ASOS Application Switch Operating System
BWM Bandwidth Management
CLI Command Line Interface
CPU Central Processing Unit
DAM Direct Access Mode
DNS Domain Name Server
DoS Denial of Service
DSSP Distributed Site State Protocol
ERT Emergency Recovery Tree
FDB Forwarding Database
FPI Fast Packet Inspection
FTP File Transfer Protocol
GSLB Global Server Load balancing
GUI Graphical User Interface
IDS Intrusion Detection System
INP Intelligent Network Protection
LED Light Emitting Diode
LDAP Lightweight Directory Access Protocol
MAC Media Access Control
MSTP Multiple Spanning Tree Protocol
MP Management Processor
NAT Network Address Translation
OSI Open Systems Interconnection
PVID Port LAN ID

Introduction
Table 1: Acronyms (cont.)
Acronym Definition
RSTP Rapid Spanning Tree Protocol
SNMP Simple Network Management Protocol
SP Switch Processor
SSH Secure Shell
STG Spanning Tree Group
TCP Transmission Control Protocol
TFTP Trivial File Transfer Protocol
TSDMP Technical Support Dump
UDP User Datagram Protocol
WBM Web Based Management
VLAN Virtual Local Area Network
VMA Virtual Matrix Architecture
VR Virtual Router
VRRP Virtual Router Redundancy Protocol

Introduction

Chapter 2 – Gathering Troubleshooting
Information
Before contacting Radware Technical Support, you should gather information that can help support
personnel when troubleshooting.
This chapter includes the following sections:
• Information Menus, page 39
• Maintenance Menus, page 43
• Statistics Menus, page 46
• Viewing General System Information, page 47
• Viewing the Software Version, page 48
• Viewing Software Keys and License Information, page 48
• Viewing System Capacity, page 49
• Collecting Management Processor Statistics, page 50
• Collecting Switch Processor Statistics, page 51
• Viewing Port Information and Statistics, page 53
• Viewing GSLB Information, page 54
• Determining the Master and Backup, page 55
• Events Notification, page 55
Information Menus
The information menus provide system and feature-specific information that can assist you in
troubleshooting.
To access the main Information menu
Enter info at the CLI root prompt.
>> ADC -Main# info

-------------------------------------------------
[Information Menu]
sys - System Information Menu
l2 - Layer 2 Information Menu
l3 - Layer 3 Information Menu
slb - Layer 4-7 Information Menu
bwm - Bandwidth Management Information Menu
security - Security Information Menu
link - Show link status
port - Show port information
swkey - Show enabled software features
dump - Dump all information

Gathering Troubleshooting Information
System Information Menu

The system information menus provide system information that can assist you in troubleshooting.
To access the System Information menu
Enter sys in the Information Menu prompt.
>> ADC - Information# sys

------------------------------------------------------------
[System Menu]
snmpv3 - SNMPv3 Information Menu
general - Show general system information
ps - Show power supply information
fan - Show system fan information
temp - Show system temperature information
sslchip - Show SSL chip information
time - Show date and time
log - Show last n (or 500) syslog messages
mgmt - Show management port information
capacity - Show switch capacity information
encrypt - Show switch encryption licenses
user - Show current user status
dump - Dump all system information
SNMPv3 Information Menu

The SNMPv3 information menus provide SNMP-specific information that can assist you in
troubleshooting.
To access the SNMP3 Information menu
Enter snmpv3 in the System Menu prompt.
>> ADC - System# snmpv3

------------------------------------------------------------
[SNMPv3 Information Menu]
usm - Show usmUser table information
view - Show vacmViewTreeFamily table information
access - Show vacmAccess table information
group - Show vacmSecurityToGroup table information
comm - Show community table information
taddr - Show targetAddr table information
tparam - Show targetParams table information
notify - Show notify table information
dump - Show all SNMPv3 information

Layer 2 Information Menu

The Layer 2 information menus provide Layer 2-specific information that can assist you in
troubleshooting.
To access the Layer 2 Information menu
Enter l2 in the Information Menu prompt.
>> ADC - Information# l2

------------------------------------------------------------
[Layer 2 Menu]
fdb - Forwarding Database Information Menu
lacp - Link Aggregation Control Protocol Menu
stg - Show STG information
cist - Show CIST information
trunk - Show Trunk Group information
vlan - Show VLAN information
team - Show port team information
dump - Dump all Layer 2 information
Layer 3 Information Menu

The Layer 3 information menus provide Layer 3-specific information that can assist you in
troubleshooting.
To access the Layer 3 Information menu
Enter l3 in the Information Menu prompt.
>> ADC - Information# l3

------------------------------------------------------------
[Layer 3 Menu]
route - IP Routing Information Menu
route6 - IP6 Routing Information Menu
arp - ARP Information Menu
nbrcache - IP6 Neighbor Cache Information Menu
bgp - BGP Information Menu
ospf - OSPF Routing Information Menu
ospfv3 - OSPFv3 Routing Information Menu
rip - RIP Routing Information Menu
ip - Show IP information
vrrp - Show Virtual Router Redundancy Protocol information
dump - Dump all layer 3 information
SLB (Layers 4 through 7) Information Menu

The SLB information menus provide SLB-specific information that can assist you in troubleshooting.

To access the SLB Information menu
Enter slb in the Information Menu prompt.
>> ADC - Information# slb

------------------------------------------------------------
[Server Load Balancing Information Menu]
sess - Session Table Information Menu
gslb - Global SLB Information Menu
ddstore - Dynamic Data Store Information Menu
real - Show real server information
group - Show real server group information
virt - Show virtual server information
filt - Show filter information
port - Show port information
wlm - Show Workload Manager information
idshash - Show IDS server selected by hash or minmisses metric
bind - Show real server selected by hash, phash, or minmisses metric
bind6 - Show IPv6 real server selected by hash, phash, or minmisses
metric
cookie - Decode the HEX value to get CIP, VIP, RIP and Rport
synatk - Show SYN attack detection information
dump - Show all layer 4 information
Bandwidth Management Information Menu

The BWM information menus provide bandwidth management-specific information that can assist
you in troubleshooting.
To access the bandwidth management Information menu
Enter bwm in the Information Menu prompt.
>> ADC - Information# bwm

------------------------------------------------------------
[Bandwidth Management Information Menu]
ipuser - BWM IP User Entries Information Menu
cont - Show Bandwidth Management Contract information
Security Information Menu

The Security information menus provide security-specific information that can assist you in
troubleshooting.
To access the Security Information menu
Enter security in the Information Menu prompt.

>> ADC - Information# security

------------------------------------------------------------
[Security Information Menu]
appwall - Show appwall webapp information
port - Show port security information
ipacl - Show IP ACL information
udpblast - Show UDP blast protection information
dos - Show protocol anomaly and DoS attack prevention information
dump - Show all security information
Maintenance Menus
The Maintenance information menus provide maintenance operation-specific information that can
assist you in troubleshooting.
To access the Maintenance menu
Enter maint in the CLI root prompt.
>> ADC - Main# maint

-------------------------------------------------------
[Maintenance Menu]
sys - System Maintenance Menu
fdb - Forwarding Database Manipulation Menu
arp - ARP Cache Manipulation Menu
route - IP Route Manipulation Menu
ip6 - IP6 Manipulation Menu
applog - Application Services Trace Log Menu
pktcap - Packet Capture Menu
cachcont - Export cache content list
lsdmp - List FLASH dump
ptdmp - Upload FLASH dump via FTP/TFTP/SCP
cldmp - Clear FLASH dump
tsdmp - Tech support dump
pttsdmp - Upload tech support dump via FTP/TFTP/SCP
Forwarding Database (FDB) Manipulation Menu

The FDB information menus provide forwarding database-specific information that can assist you in
troubleshooting.
To access the FDB Manipulation menu
Enter fdb in the Maintenance Menu prompt.

>> ADC - Maintenance# fdb

------------------------------------------------------------
[FDB Manipulation Menu]
find - Show a single FDB entry by MAC address
port - Show FDB entries for a single port
trunk - Show FDB entries for a single trunk
vlan - Show FDB entries for a single VLAN
refpt - Show FDB entries referenced by a single SP
dump - Show all FDB entries
del - Delete an FDB entry
clear - Clear entire FDB
FDB Dump
The FDB dump provides a list of all FDB entries.
To access the FDB dump
Enter dump in the FDB Manipulation Menu prompt.
MAC address VLANPortTrunkAge State ReferencedLearnedReferenced

SPs Port ports
--------------------------------------------------------------
00:0c:29:07:80:d3130 1 TRK 2 24
00:11:0a:ea:ea:f3130 1 TRK 1 2 24
00:14:5e:33:99:e8130 1 TRK 1 2 9
ARP Menu
The ARP (Address Resolution Protocol) menu provides ARP cache manipulation operations.
To access the ARP menu
Enter arp in the Maintenance Menu prompt.
>> ADC - Maintenance# arp

------------------------------------------------------------
[Address Resolution Protocol Menu]
find - Show a single ARP entry by IP address
port - Show ARP entries on a single port
vlan - Show ARP entries on a single VLAN
refpt - Show ARP entries referenced by a single SP
dump - Show all ARP entries
clear - Clear ARP cache
addr - Show ARP address list
ARP Dump
The ARP dump provides a list of all ARP entries.

To access the ARP dump
Enter dump in the ARP Menu prompt.
>> ADC - Address Resolution Protocol# dump

IP address Flags MAC address VLAN Age Port Referenced SPs
--------------- ----- ----------------- ---- --- ---- -----------------
10.237.25.66 P 00:14:0e:f5:f2:00 6 1-4
10.239.232.66 P 00:14:0e:f5:f2:00 6 1-4
10.239.232.100 P 4 00:14:0e:f5:f2:01 5 1-4
IP Route Manipulation Menu

The IP Route information menus provide IP routing-specific information that can assist you in
troubleshooting.
To access the IP Routing menu
Enter route in the Maintenance Menu prompt.
>> ADC - Maintenance# route

------------------------------------------------------------
[IP Routing Menu]
find - Show a single route by destination IP address
gw - Show routes to a single gateway
type - Show routes of a single type
tag - Show routes of a single tag
if - Show routes on a single interface
dump - Show all routes
clear - Clear route table
IP Routing Dump
The IP Routing dump provides a list of all IP routes.
To access the IP Routing dump
Enter dump in the IP Routing Menu prompt.
>> ADC - IP Routing# dump

Status code: * - best
Destination Mask Gateway Type Tag Metr If
--------------- ---------- --------- --------- --------- ---- --
* 127.0.0.0 255.0.0.0 0.0.0.0 martian martian
* 224.0.0.0 224.0.0.0 0.0.0.0 martian martian
* 224.0.0.5 255.255.255.255 0.0.0.0 multicast addr
* 224.0.0.6 255.255.255.255 0.0.0.0 multicast addr
* 255.255.255.255 255.255.255.255 255.255.255.255 broadcast broadcast

Application Services Trace Log (Applog) Menu

The Applog information menus provide application service trace log information that can assist you
in troubleshooting.
To access the Applog menu
Enter applog in the Maintenance Menu prompt.
>> ADC - Maintenance# applog

------------------------------------------------------------
[Application Services Trace Log Menu]
export - Export application services trace log via FTP/TFTP/SCP
showlog - Show application services trace log
clearlog - Clear application services trace log
getlevel - Get log level set in AX for all or specific modules
setlevel - Set the log level in AX for all or specific modules
tcp - Enable/disable log tcp activities
compress - Enable/disable log compression activities
caching - Enable/disable log caching activities
ssl - Enable/disable log ssl activities
http - Enable/disable log http activities
contclss - Enable/disable log content class activities
httpmod - Enable/disable log http modifications activities
appshape - Enable/disable log Appshape++ activities
dtable - Enable/disable log DataTable activities
dump - Dump application services trace log configurationt
Statistics Menus
The statistics menus provide system statistical information that can assist you in troubleshooting.
To access the Statistics menu
Enter stats in the CLI root prompt.

>> ADC - Main# stats

------------------------------------------------------------
[Statistics Menu]
sys - System Stats Menu
port - Port Stats Menu
pmirr - Port Mirroring Stats Menu
l2 - Layer 2 Stats Menu
l3 - Layer 3 Stats Menu
slb - Server Load Balancing (Layer 4-7) Stats Menu
bwm - Bandwidth Management Stats Menu
security - Security Stats Menu
mp - MP-specific Stats Menu
sp - SP-specific Stats Menu
dump - Dump all stats
Viewing General System Information

When a connection has been established with the Alteon platform, the initial screen is displayed.
The Alteon initial screen provides general details about the system.
In addition, you can run the /info/sys/general command to display this screen. It includes
system statistics for the hardware and operating system.
Initial Screen for Alteon Platforms

The following is an example of an initial screen for an Alteon Application Switch hardware platform.
System Information at 11:39:49 Mon Feb 2, 2015

Time zone: No timezone configured (GMT offset -8:00)
Memory profile is Default
Alteon Application Switch xxxx
Switch is up 7 days, 4 hours, 3 minutes and 17 seconds.

Last boot: 11:39:32 Sun Feb 1, 2015 (reset from console)
Last apply: 11:21:07 Mon Feb 2, 2015
Last save: 11:35:29 Sun Feb 1, 2015
MAC Address :
Hardware MainBoard No|Rev :
Hardware DB No :
Hardware Serial Number :
Note - When the measured temperature inside the switch EXCEEDs the anomaly
threshold at 65 degree Celsius or the critical temperature at 73 degree
Celsius different syslog messages will be generated.
Software Version xx.x.x.x, active configuration.
The following is example text of the initial screen for Alteon VA.

System Information at 11:39:49 Mon Feb 2, 2015

Time zone: No timezone configured (GMT offset -8:00)
vADC 1
vADC 1 is up 1 day, 2 hours, 23 minutes and 48 seconds.

Last boot: 11:39:32 Sun Feb 1, 2015 (reset from console)
Last apply: 11:21:07 Mon Feb 2, 2015
Last save: 11:35:29 Sun Feb 1, 2015
MAC Address :
Software Version x.x.x.x (FLASH image1), active configuration.
Viewing the Software Version

You can view the details of the current boot option and the software version.
To view the current boot options and system software version
Enter /boot/cur in the CLI root prompt.
/boot/cur
Currently set to boot image2, active config block.
Current FLASH software:
image1: Alteon-x.x.x.x, downloaded 11:23:56 Sun May 3, 2015
image2: Alteon-x.x.x.x, downloaded 9:08:39 Mon May 4, 2015
Memory profile is Default
Management port is enabled
Enhanced Log Size: Disabled
Viewing Software Keys and License Information

Some features require keys to be installed to enable the feature (for example, Global Server Load
balancing (GSLB)). Demo versions cannot be reused after expiration.
To view the license information and software keys installed
Enter /info/swkey in the CLI root prompt.

>> Main# info/swkey

Feature License: aas-slb-Fwheyia9
Throughput License: 20Gbps-1B23yfHp
SSL License: aas-ssl-1000-k5PCAbd6
Compression License: aas-compression-100-Zu3Xyala
FastView License: aas-fv-600-01APR2013-30MAR2014-vQlLmjdB
APM License: aas-apm-100-01APR2013-30MAR2014-vQlLmjdB
WAF License: Default
Authentication License: Default
Software feature Status

---------------- ------
itm Permanent
GSLB Temporary, 23 days left
bwm Permanent
llb Expired
cookie Permanent
Capacity License License Peak Usage Current Usage

---------------- --------- -------------- --------------
Throughput8Gbps 4.39 Kbps 1.33 Kbps
SSL1000 CPS 0 CPS 0 CPS
CompressionUnlimited 0 Mbps 0 Mbps
FastView 0 PgPS 0 PgPS
APM 10 PgPM 0 PgPM
WAF 0 Mbps 0 Mbps
Authentication 0 Users 0 Users
Viewing System Capacity

You can display information about the maximum and currently enabled platform capacity for various
services and applications from Layer 2 to Layer 7.
To view the system capacity information
Enter /info/sys/capacity in the CLI root prompt.

>> Main# /info/sys/capacity

Maximum Current (Enabled)
LAYER 2
FDB 16384 9
FDB per SP 8132
2048 3 (2)
VLANs
12 1 (1)
Static Trunk Groups
28
LACP Trunk Groups
8
Trunks per Trunk Group
16 16 (2)
Spanning Tree Groups
8 8 (0)
Port Teams
1
Monitor Ports
LAYER 3
255 1 (1)
IP Interfaces
4+255 1+0 (1+0)
IP Gateways
4096 12
IP Routes
128 0
Static Routes
8092 10
ARP Entries
128 0
Static ARP Entries
15 0
Local Nets
2 1
DNS Servers
2 0
BOOTP Servers
255 2
RIP Interfaces
Collecting Management Processor Statistics

You can capture Management Processor (MP) CPU usage and memory statistics for troubleshooting.
You can also trace the reasons for high MP CPU usage that can be due to the high volume of traffic
from Switch Processors (SPs). This topic includes the following sub-topics:
• CPU Usage, page 50
• Memory Statistics, page 51
• MP Packet Statistics, page 51
CPU Usage
To view the CPU usage
Enter /stat/mp/cpu in the CLI root prompt.
>> Main# stats/mp/cpu

--------------------------------------------------------------------
CPU utilization:
cpuUtil1Second: 19%
cpuUtil4Seconds: 23%

Memory Statistics
To view the memory statistics
Enter /stat/mp/mem in the CLI root prompt.
>> Main# /stat/mp/mem

Memory stats:
Total: 130088960 bytes
Used: 103170048 bytes
Free: 269918912 bytes
LowFree: 269918912 bytes
MP Packet Statistics
MP packet statistics are used to trace the reasons for high CPU utilization.
To view the MP packet statistics
Enter /stat/mp/pkt in the CLI root prompt.
>> Main# /stat/mp/pkt

-----------------------------------------------------------------------
Packet counts:
allocs: 5743873 frees: 5743873
mediums: 0 mediums hi-watermark: 0
smalls: 0 smalls hi-watermark: 56
alloc fails: 0 packet discards: 0
TCP counts:
allocs: 64139 frees: 64052
current: 87 current hi watermark: 89
alloc fails: 0 alloc discards: 0
TCP6 counts:
allocs: 0 frees: 0
Collecting Switch Processor Statistics

The SP CPU is the main data-path processor for Alteon. Depending on the Alteon platform, there can
be two or four SPs.
High SP CPU usage can be due one or more of the following reasons:
• High traffic volume or Denial of Service (DoS) attacks to SP ingress ports. Check the port
interfaces.
• Layer 2 flooding on the SP ingress port. Check unknown Forwarding Database (FDB) entries or
Spanning Tree Group (STG) states if they are in forwarding and stable.
• Broadcast and/or multicast on the SP ingress port. Check port interface statistics for broadcast
and/or multicast traffic.

This topic includes the following sub-topics:

• SP Statistics, page 52
• SP Maintenance Statistics, page 52
SP Statistics
The SP statistics can be displayed for a particular SP or for all SPs using the command
To display SP statistics for a particular SP
Enter /stat/sp <SP number>/cpu in the CLI root prompt.
>> Main# /stat/sp 1/cpu

---------------------------------------------------------------------
CPU utilization for SP1:
cpuUtil1Second: 42%
To display SP statistics for all SPs
Enter /stat/sp 1/cpu/../sp2/cpu/../sp3/cpu/..sp4/cpu in the CLI root prompt.
>> Main# /st/sp 1/cpu/../sp2/cpu/../sp3/cpu/..sp4/cpu

---------------------------------------------------------------------
cpuUtil1Second: 5%
cpuUtil4Seconds: 5%
---------------------------------------------------------------------
cpuUtil1Second: 5%
cpuUtil4Seconds: 5%
---------------------------------------------------------------------
cpuUtil1Second: 2%
cpuUtil4Seconds: 2%
---------------------------------------------------------------------
cpuUtil1Second: 2%
cpuUtil4Seconds: 2%
SP Maintenance Statistics

To display SP maintenance statistics
Enter /stat/sp <SP number>/cpu/maint in the CLI root prompt.
Maintenance statistics for SP 1:

Receive Letter success from MP: 154401332
Receive Letter success from SP 2: 0
Receive Letter success from SP 3: 0
Receive Letter errors from MP: 0
Receive Letter errors from SP 2: 0
Receive Letter errors from SP 3: 0
Send Letter success to MP: 118587797
Send Letter success to SP 2: 0
Send Letter success to SP 3: 0
Send Letter failures to MP: 0
Send Letter failures to SP 2: 0
Send Letter failures to SP 3: 0
learnErrNoddw: 0 resolveErrNoddw: 0
ageMPNoddw: 0 deleteMiss: 0
pfdbFreeEmpty: 0
arpDiscards: 0 icmpDiscards: 0
tcpDiscards: 0 udpDiscards: 0
Sp - Application Services Engine Statistics

-----------------------------------------------------
Client frames sent : Success: 0
Client frames sent : Failed: 0
Server frames sent : Success: 0
Server frames sent : Failed: 0
Packets received: 0
Packets dropped: 0
Invalid frames received: 0
Invalid Session index: 0
Memory allocation failures: 0
Letter sent to sp success: 0
Letter sent to sp failed: 0
Packet buffers allocated: 0
Packet buffers freed: 0
Packet allocation failures: 0
------------------------------------------------------------------
CPU utilization for SP 1:
cpuUtil1Second: 9%
cpuUtil4Seconds: 8%
Viewing Port Information and Statistics

The port statistics commands let you display information on received and transmitted packets at the
ports. The ingress and egress counts are taken at the Media Access Control (MAC) layer. These
counts are updated once every second.
The following are commands for displaying port information and statistics.

To display port information
Enter the command: /info/port
To display port statistics
Enter the command: /stats/port <port number>
To clear port statistics
Enter the command: /stats/port <port number>/clear
To display the port link state
Enter the command: /info/link
To display IP interface statistics
Enter the command: /stats/l3/if
To display port teams
Enter the command: /info/l2/team
To clear port numbers with management access
Enter the command: /cfg/sys/access/port/cur
Viewing GSLB Information

View GSLB information as follows:
To view general GSLB information
Enter the command: /info/slb/gslb

To view the current GSLB configuration
Enter the command: /cfg/slb/gslb/cur
To view GSLB statistics
Enter the command: /stats/slb/gslb
Determining the Master and Backup

You can determine if the Alteon platform is the master or the backup.
To determine the master and backup
Enter the command: /info/l3/vrrp

The following examples display the Alteon platform as the master or backup, respectively.
Master
/info/l3/vrrp
VRRP information:
1:vrid 1, 172.21.16.187,if 4, renter, prio 109, master, server
3:vrid 3, 192.168.1.30, if 2, renter, prio 109, master
5:vrid 5, 172.21.16.10, if 4, renter, prio 109, master
Backup
/info/l3/vrrp
VRRP information:
1:vrid 1, 172.21.16.187,if 1, renter, prio 104, backup, server
3:vrid 3, 192.168.1.30, if 3, renter, prio 104, backup
5:vrid 5, 172.21.16.10, if 1, renter, prio 104, backup
Events Notification
Alteon sends notifications about different events that occur (such as, server down/up, temperature
exceeded, or VRRP state change).
Alteon provides a choice of event notification methods including:
• Syslog messaging
• Syslog log file
• SNMP traps
• E-mails
• Console

Every event has a level associated with it. The levels supported are:
• EMERG—Indicates the system is unusable.
• ALERT—Indicates that action should be taken immediately.
• CRIT—Indicates a critical condition.
• ERR—Indicates an error condition or error operation.
• WARNING—Indicates a warning condition.
• NOTICE—Indicates a normal but significant condition.
• INFO—Indicates an information message.
• DEBUG—Indicates a debug-level message.
You can also select to only send event notifications belonging to certain modules (for example, SLB,
GSLB, or STP). By default, event notification is enabled for all modules.
For example, a list of event messages will look as follows:
>> vADC 1 - Information# /inf/sys/log

Feb 25 06:25:28 INFO appsvc: Warning: Maximum licensed compression
throughput has been exceeded. Only licensed compression throughput will be
compressed
Feb 25 06:26:28 INFO appsvc: The device has reached 90% of its Compression
Throughput license limit
Feb 25 06:31:28 INFO appsvc: Warning: Maximum licensed compression
throughput has been exceeded.
Syslog Messaging
You can use the system log (syslog) messaging feature to log events on up to five servers running a
syslogd service for troubleshooting. You can configure up to five hosts to capture syslog messages
using the following command:
/cfg/sys/syslog/hst(1..5) <ip address> <severity>
Syslog Log File

The last 500 event notifications are kept in the syslog log file and can be viewed using the following
commands:
/info/sys/log - Show last n (or 500) syslog messages.
SNMP Traps
Alteon can send all events to management workstations using SNMP traps. See the Alteon
Application Guide and Alteon Command Reference Guide for details on configuring Alteon to send
SNMP traps.

E-mail
You can also send the event messages to multiple e-mail addresses. In order to minimize the
amount of e-mails sent you can select from which severity (and above) to send notifications via e-
mail.
To configure events notification via e-mail:
/cfg/sys/syslog/email <enable|disable> severity=<0-7> <to=email address>

<from=email address>
Console
All events that are sent via syslog are sent to the console as well. This can be disabled or enabled
(enabled by default) using the following command:
/cfg/sys/syslog/console enable|disable
You can also receive event notifications when connected to Alteon via Telnet or SSH. To enable it,
use the following command:
/oper/displog disable|enable
Session Table
The session table is a very important troubleshooting tool in real-time. You can filter the session
entries according to any of the fields included in the entry such as source IP, source port, destination
IP, destination port, real server, etc. To view session table:
/info/slb/sess
For auditing and compliance purposes the session entries can be logged on syslog servers.
The following parameters are recorded for each entry:
• Client IP (CIP)—source where the connection is coming from.
• Source Port (CP)—The source port on the session request
• Destination IP (DIP)—destination where the connection is going to (VIP or filter destination)
• Service (DP)—What port/service was requested (i.e. HTTP, FTP etc)
• Protocol (PT)—TCP or UDP
• Start Time (ST)—marks the entry of the start of the client session.
The format will be: [Date – DD/MM/YEAR] – [Time – HH:MM:SS 24hours format]
• End Time (ET)—marks the entry of the last activity of the entry.
The format will be: [Date – DD/MM/YEAR] – [Time – HH:MM:SS 24 hours format]
• Real Server IP (RIP)—which server IP was the session forwarded to
• Real Server Port (RP)—to which port on the server the session was forwarded
• NAT Address/PIP (PIP)—The NAT address given
• NAT Port (PP)—The source port after address translation is performed
In order to minimize amount of data sent you can disable logging of NAT and/or Real Server
information if it is not relevant to your environment.
Since log message structure can change the syslog message will start with a description of the
reported fields: CIP CP DIP DP PT ST ET RIP RP PIP PP.

For increased performance, multiple sessions are aggregated in one syslog message, separated by a
“|” symbol.
Logging the session entries can have impact on performance. For that reason you can control for
which virtual services or filters to perform session logging (by default session logging is disabled for
all virtual services and filters).
To enable logging of session table
Enter the command: /cfg/sys/syslog/sesslog on
To enable session logging for a specific virtual service
Enter the command: /cfg/slb/virt 1/service 80/sesslog enable
To enable session logging for a specific filter
Enter the command: /cfg/slb/filt 1/adv/sesslog enable

Chapter 3 – Troubleshooting Tools
This chapter describes some tools to help you troubleshoot common problems you may encounter
with Alteon.
The types of problems that typically occur with networks are connectivity and performance. Alteon
supports a diverse range of network architectures and protocols, some of which are used to maintain
and monitor connectivity and isolate connectivity faults.
This chapter includes the following topics:
• Port Mirroring, page 59
• Dumps, page 62
• Application Log, page 67
• Loading an Alternate Configuration, page 68
• Trace Buffers, page 69
Port Mirroring
Use port mirroring to monitor and analyze network traffic flowing on a port. You can use port
mirroring to specify a destination port on which you want to see mirrored traffic, and to specify the
source ports from which traffic is mirrored. You configure one mirroring port (destination port) for
each mirrored port.
Alteon lets you mirror port traffic for all layers (Layers 2 through 7). This is done by attaching a
sniffer to a monitoring port that is configured to receive a copy of all packets that are forwarded
from the mirrored port. Port mirroring can be used as a troubleshooting tool or to enhance the
security of your network. For example, an Intrusion Detection System (IDS) server can be
connected to the monitor port to detect intruders attacking the network.
For more information on configuring port mirroring, refer to the Alteon Application Switch Operating
System Application Guide.
This section describes troubleshooting of port mirroring, including:
• Mirroring Individual Ports, page 59
• Mirroring VLANs on a Port, page 60
Mirroring Individual Ports

As shown in Figure 1 - Monitoring Ports Example, page 60, port 9 monitors ingress traffic (traffic
entering the platform) on port 3, and egress traffic (traffic leaving the platform) on port 11. You can
attach a monitoring device to port 9 to monitor the traffic on ports 3 and 11.
This example shows two mirrored ports monitored by a single port.
Note: The example in the figure below is for illustration purposes. The actual platform and ports
may be different for your particular Alteon platform.

Troubleshooting Tools
Figure 1: Monitoring Ports Example
The following combinations can be used for mirroring individual ports:

• Mirrored ports to a monitored port.
• Many mirrored ports to one monitored port.
• Mirrored port on one or more VLANs to a monitored port.
• Many mirrored ports on one or more VLANs to one monitored port (see Mirroring VLANs on a
Port, page 60).
Note: Alteon does not support a single port being monitored by multiple ports.
Ingress traffic is duplicated and sent to the mirrored ports before processing, and egress traffic is
duplicated and sent to the mirrored ports after processing.
Note: Radware recommends that you disable port mirroring when not in use to reduce the load on
the Alteon platform.
Mirroring VLANs on a Port

VLAN-based port mirroring enables you to monitor traffic based on VLANs associated with a port. If
a mirrored port is configured as a member of more than one VLAN, you may want to monitor only
traffic entering that port on a specific VLAN. You can add specific VLANs to be mirrored, even if there
are multiple VLANs associated with that port. If you do not specify a VLAN, all traffic on the port will
be mirrored.
To configure port mirroring

Specify the monitoring port connected to the recording device.
/cfg/pmirr/monport <num>
To monitor the traffic

1. Select the ports that you want to mirror <num>.
2. Select the monitoring mode. Values:

— in-ingress
— out-egress
— both-ingress and egress
3. Enable port mirroring.
/cfg/pmirr/monport/add <num> in|out|both

/cfg/pmirr/mirr ena
To display the current port mirroring settings
/cfg/pmirr/monport <num>/cur
To apply and save the port mirroring configuration

Enter the following commands:
/cfg/pmirr/mirr apply
/cfg/pmirr/mirr save
Configuring VLAN Mirroring on a Port

Use the following commands to monitor or mirror traffic based on a specific VLAN associated with a
port, where
• <num> is the monitoring or mirroring port number. Values: 1–28.
• <x> is the mirrored port (port to mirror from).
• <y> is the VLAN index (use carriage return for all VLANs).
To select port for monitoring
Enter /cfg/pmirr/monport <num>
To monitor ingress traffic on port
Enter /cfg/pmirr/monport/add <x> in <y>
To monitor egress traffic on port
Enter /cfg/pmirr/monport/add <x> out <y>
To display the current port mirroring settings
Enter /cfg/pmirr/monport <num>/cur

Dumps
If you open a support call with Radware Technical Support, you may be asked to provide any of the
following files (dumps) for troubleshooting purposes:
• TS Dump, page 62
• TCP Dump (Packet Capture), page 63
• SSL Dump, page 64
• Panic Dumps, page 64
TS Dump
The Technical Support (TS) dump is the main dump file used for system troubleshooting. A TS dump
is often required when opening a ticket in case of a failure. It contains device information, statistics,
and configuration. It contains all pertinent information that can be used by Radware Technical
Support.
The output of the TS dump is directed to the console screen. Use a Telnet client or terminal emulator
application (for example, SecureCRT) that allows you to capture the screen output and save it to a
file in order to send it to Radware Technical Support for debugging purposes.
In addition, you can transfer/upload the TS dump using an FTP/TFTP/SCP file server.
To operate and save a TS dump

1. Enable console logging to capture the TS dump to a file.
2. Enter /maint/tsdmp in the CLI root prompt to direct the output to the console screen. After
the output begins, wait until the dump finishes (you cannot stop it in the middle).
>> Maintenance# tsdmp

Confirm dumping all information, statistics, and configuration [y/n]:
3. To transfer the tsdmp to an FTP/TFTP/SCP server, enter /maint/pttsdmp.

4. Enter the hostname or IP address of the FTP/TFTP/SCP server, the name of the file, and a
username and password for the FTP/SCP server when requested.

>> Main# maint/pttsdmp

Enter hostname or IP address of FTP/TFTP/SCP server: 1.1.1.1
Enter name of file on FTP/TFTP/SCP server: tsdmp.txt
Enter username for FTP/SCP server or hit return for TFTP server: anonymous
Enter password for username on FTP/SCP server:
Include private keys? [y/n]: y
Enter passphrase:
Reconfirm passphrase:
Enter "scp" or hit return for FTP server:
Connecting to 1.1.1.1...
….
Starting upload…
125 Using existing data connection
Note: This downloaded file has only LF (Line Feed) characters and no CR (Carriage Return)
characters, so you need to use an appropriate text editor to view it.
If there is an unscheduled system dump to flash memory, the following message displays when you
log on to Alteon:
Note: A system dump exists in FLASH. The dump was saved

at 19:15:23 Thu Jan 9, 2003. Use /maint/uudmp to
extract the dump for analysis and /maint/cldmp to
clear the FLASH region. The region must be cleared
before another dump can be saved.
TCP Dump (Packet Capture)

TCP dump is a packet capture tool that enhances Alteon troubleshooting techniques. It lets you
intercept TCP/IP and other packets being transmitted or received over the network to which Alteon
is attached.
Note: Service interruptions may occur when using packet capture in certain situations, for example,
with high traffic volume and only one CU allocated for the vADC.
Radware recommends that you use packet capture sparingly (for troubleshooting purposes), during
a maintenance window, or only in periods of low traffic volume.
To configure packet capture options
Enter /maint/pktcap in the CLI root prompt.

>> Main# maint/pktcap

------------------------------------------------------------
[Packet Capture Menu]
capture - Capture packets
stop - Stop capturing packets
decrypt - Set the key and decrypt SSL capture
dumpcap - Display captured packets
snaplen - Set the packet snap length
count - Set the max number of captured packets
putcap - Upload capture buffer via FTP/TFTP/SCP
clearcap - Clear capture buffer
cur - Display current packet capture options
Note: Packet capture is not enabled when you are connected using a serial connection.
To display the captured packets
Enter /maint/pktcap/dumpcap in the CLI root prompt.
Note: You may have to use an external tool (such as Wireshark) to decode and view the captured
data.
SSL Dump
SSL dump is an extension of the TCP dump capabilities (enter /decrypt in the Packet Capture
menu). It lets you decrypt captured SSL traffic using a user-selected key. Using SSL dump saves you
the need to export the key from the Alteon platform to decrypt the SSL dump file using third-party
software.
Notes
• Radware recommends handling the decrypted capture in a secure manner. View it in a screen
using SSH and export it to a remote server using SCP.
• Decryption of the SSL dump capture is only allowed for users with certificate management
privileges.
Panic Dumps
Dump information contains internal device state data that is written to flash memory after any one
of the following occurs:
• The administrator forces a panic. The panic option, found in the Maintenance menu, causes
Alteon to dump state information to flash memory and then reboot.
• The watchdog timer forces a reset. The watchdog timer reboots the Alteon platform if the
software freezes.
• Alteon detects a hardware or software problem that requires a reboot.

When you log in, check if there is an unscheduled system panic dump in flash memory, and export it
for decoding. Alteon only holds two panic dumps at one time, so after it is exported and decoded by
Alteon, you should clear the dump to make room for any future panics.
To display a panic dump
Enter /maint/lsdmp in the CLI root prompt.
/maint/lsdmp
The main dump was saved at 12:47:22 Fri Oct 7, 2011.
A backup dump was saved at 15:36:01 Fri Oct 7, 2011.
To export a panic dump
Enter /maint/ptdmp in the CLI root prompt.
/maint/ptdmp
Enter hostname or IP address of FTP/TFTP server:
47.81.19.16
Enter name of file on FTP/TFTP server:panic-dump
Enter username for FTP server or hit return for TFTP
server:anonymous
Enter password for username on FTP server: Enter region to dump [main/bkp]:
main
Dumping main region: Connecting to 47.81.19.16... Connected to 47.81.19.16.
Escape character is '^]'.
220 3Com 3CDaemon FTP Server Version 2.0
331 User name ok, need password
230 User logged in 200 Type set to I.
227 Entering passive mode (47,81,19,16,6,28) Starting upload...
125 Using existing data connection Upload in
progress.......226 Closing data connection; File transfer successful.
221 Service closing control connection
Connection closed by remote host.
FLASH dump successfully transferred to 47.81.19.16:pa nic-dump
To clear a panic dump
Enter /maint/cldmp in the CLI root prompt.
/maint/cldmp
Confirm clearing main FLASH dump [y/n]: y
main FLASH dump region cleared.
Confirm clearing backup FLASH dump [y/n]: y
backup FLASH dump region cleared.

Uploading the Dumps

On OnDemand Switch platforms, you can collect and upload all the dumps, logs, and configurations
to an FTP server to send to Radware Technical Support for debugging purposes.
To upload all the dumps
1. Enter /maint/putdumps in the CLI root prompt.

2. Enter the hostname or IP address of the FTP server.
3. Enter the name of the .tar file.
4. Enter the username and password for the FTP server.
All the dumps, logs, and configurations will be uploaded to the specified file on the FTP server.
Filtering the Session Dump

Typically, session dumps are long and unwieldy. Alteon provides a tool to filter session dumps based
on any one of the following attributes:
• Client IP address
• Source port
• Destination IP address
• Destination port
• Proxy IP address
• Proxy port
• Matching filter
• Matching flag
• Ingress port
• Real IP address
• Switch Processor (SP)
Only one attribute can be used at a time to filter the session dump.
To filter a session dump
Enter /info/slb/sess in the CLI root prompt.

Refer to the Radware Alteon Application Switch Operating System Command Reference for a detailed
list of all the filtering options available.
For example, if you want to filter a session dump based on client IP address 10.10.10.1, use the
command /info/slb/sess/cip 10.10.10.1.

>> # /info/slb/sess/cip 10.10.10.1

Printing Sessions for SP 1
1,01: 10.10.10.1 137, 205.178.13.100 137
ALLOW age 2 f:100 E
1,01: 10.10.10.1 2592,172.21.31.100 http -> 14291
10.20.1.2 http age 0
1,01: 10.10.10.1 2593, 172.21.31.100 http -> 14292
10.20.1.3 http age 0
1,01: 10.10.10.1 2594, 172.21.31.100 http -> 14307
10.20.1.2 http age 0
1,01: 10.10.10.1 2599, 172.21.31.100 http -> 14339
10.20.1.3 http age 0
1,01: 10.10.10.1 2600, 172.21.31.100 http -> 14340
10.20.1.4 http age 0
1,01: 10.10.10.1 2601, 172.21.31.100 http -> 14367
10.20.1.3 http age 0
1,01: 10.10.10.1 2602, 172.21.31.100 http -> 14384
10.20.1.2 http age 10
1,01: 10.10.10.1 2603, 172.21.31.100 http -> 14385
10.20.1.3 http age 10
1,01: 10.10.10.1 2604, 172.21.31.100 http -> 14414
10.20.1.2 http age 10
>>Session Table Information
Application Log
The application log (applog) enables logging and tracking all Application Services Engine activities
and includes a log message with all Layer 4 session information at the beginning of every new
session. This log provides easy mapping between sessions as they appear in the session table (by
Layer 4 information) and the session ID that appears in the application log.
The applog also allows logging of the TCP data of each session. The TCP data is automatically added
whenever any other logging subject is enabled to allow correlation with the Alteon session table
data, but can also be enabled individually using /maint/applog/tcp enable, thus providing TCP
logging facilitates.
Note: Application log files are created per SP and are rotated when the log file size reaches 15 MB.
Up to 20 generations of files are saved, but only 3 generations of files are exported externally. You
can use the -internal flag to export all 10 generations of files.
On a vADC, the size and number of files depends on the number of SPs allocated to the vADC (15
MB and 20 generations of files per SP).
To enable or view the application log
Enter applog in the Maintenance Menu prompt.

>> ADC - Maintenance# applog

------------------------------------------------------------
Application Services Trace Log Menu]
export - Export application services trace log via FTP/TFTP/SCP
showlog - Show application services trace log
clearlog - Clear application services trace log
getlevel - Get log level set in AX for all or specific modules
setlevel - Set the log level in AX for all or specific modules
tcp - Enable/disable log tcp activities
compress - Enable/disable log compression activities
caching - Enable/disable log caching activities
ssl - Enable/disable log ssl activities
http - Enable/disable log http activities
contclss - Enable/disable log content class activities
httpmod - Enable/disable log http modifications activities
appshape - Enable/disable log Appshape++ activities
dtable - Enable/disable log DataTable activities
xwp - Enable/disable log Appwall activities
memory - Enable/disable log memory activities
dump - Dump application services trace log configuration
Exporting Applog Files

You export applog files as the admin user from the applog menu, using the following syntax:
export <hostname> <-tftp|username password> [-mgmt|-data] [-scp] [-internal]
Normal export (without the -internal option) exports the logs in a readable format, but includes
only the error level. This is regardless of the log level set (including debug).
Internal export, using the -internal option, exports the raw data, including all logs that have been
written to the log file.
Loading an Alternate Configuration

This section describes how to load an alternate configuration.
When you make configuration changes, you must save the changes so that they are retained the
next time the Alteon platform is reset. When you run save at any time, your new configuration
changes are placed in the active configuration block. The previous configuration is copied into the
backup configuration block.
There is also a factory configuration block. This holds the default configuration set by the factory
when your Alteon platform was manufactured. Under certain circumstances, you may want to reset
the configuration to the factory settings. This can be useful when a custom-configured Alteon is
moved to a network environment where it will be re-configured for a different purpose.
To set which configuration block to load the next time it is reset
1. Enter /boot/conf at the prompt:

2. Enter the name of the configuration block you want the Alteon platform to use:
A message is displayed indicating which configuration block is currently set to be loaded at the
next reset, and prompts you to enter a new choice:

/boot/conf
Currently set to use active configuration block on next reset.
Specify new block to use ["active"/"backup"/"factory"]:
3. If you select factory settings, you are prompted to keep management port connectivity:
Next boot will use factory default config block instead of active.
Confirm : Do you want to keep management port connectivity? [y/n]: y
4. You are prompted to keep SSH keys:
Confirm : Do you want to keep SSH keys? [y/n]: n

deleting SSH keys from FLASH
SSH keys deleted
Trace Buffers
Trace buffers are used to selectively track activities that the management processor (MP) and switch
processors (SPs) perform while the switch is in operation.
To extract the MP trace buffer
Enter /maint/debug/tbuf in the CLI root prompt.
>> ADC - Miscellaneous Debug# tbuf

MP trace buffer at 12:17:04 Thu Jul 12, 2012 (DST); mask: 0x00000000
cfg_diff 060001dd a8542465 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc a854245d 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dd 97461c99 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc 97461c92 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dd 3f699fc2 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc c7e1cc3f 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dd 97d71aca 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc 97d71ac2 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dd 6a6c5d6c 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc 6a6c5d64 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dd 721cb43d 031ffff0 aaeaaeaa 00000000 00000001
cfg_diff 060001dc 721cb434 031ffff0 aaeaaeaa 00000000 00000001
ActiveTB 0f000001 07a9512b 00000001 00000001 00000002 00000002
slb.c 0f0020d4 07a8ddb3 0002a000 aaeaaeaa 00000000 00000001
slb.c 0f0020cb 07a8d4eb 00075800 aaeaaeaa 00000000 00000001
slb.c 0f00247a 07a7a312 00010800 aaeaaeaa 00000000 00000001
Note: Output is binary. Format varies with software version.

To extract the SP trace buffer
Enter /maint/debug/sptb <SP #> in the CLI root prompt.
>> ADC - Miscellaneous Debug# sptb

Enter SP number: (1-7) 1
SP 1 trace buffer at 12:19:49 Thu Jul 12, 2012 (DST); mask: 0x00000000
SLB_TABL 07a910e7 00020219 09a6bf60 00000002 00000001 00000000

PMG 07a8ecc8 08b48520 00000000 00000000 00000000 00000000
SRVBPON 07a1e8e1 00000001 00000000 00000000 00000000 00000000
VRRPON 07a1e8de 00000000 00000000 00000000 00000000 00000000
SymErr 05eb09d7 00000000 00000000 00000001 00000000 00000002
256m_SP 05eb09d7 00000000 00000000 00000000 00000000 00000000
stBwmTbl 05eafda1 00000001 b4d09a20 b4d09a20 b4d09a8c b4d19a8c
Heap_ini 05eabc06 8ec228a0 02000000 00000000 00000000 00000000
urlMinit 05eabbc1 00000000 00000000 00000000 8ec228a0 02000000
IP INIT 05e43f8e 00000000 00000000 00000000 00002000 00001000
the_DAWN 05e436d5 00000001 00000000 00000000 00000000 00000000
Note: Output is binary. Format varies with software version.

Chapter 4 – Troubleshooting Fundamentals and
Techniques
A fundamental method of network troubleshooting is to use the Open Systems Interconnection
(OSI) model to systematically identify and rule out problems. This step-by-step approach helps you
to maximize your time by minimizing the chance that the problem you are attempting to resolve
resides in a different layer of the OSI than the layer you are currently analyzing.
This section includes the following topics:
• Diagnosing Link (Layer 1) Issues, page 71
• Diagnosing Connectivity Issues, page 72
• Diagnosing Layer 2 Issues, page 72
• Diagnosing Network (Layer 3) Issues, page 74
• Diagnosing SLB (Layer 4) Issues, page 76
• Diagnosing Layer 7 Issues, page 77
Diagnosing Link (Layer 1) Issues

This section describes how to diagnose link (Layer 1) issues.
To diagnose link issues

1. Check the cable for the wrong type or if it is bad.
2. Check the link negotiation, especially for gigabit connections.
3. Check for port configuration mismatches on either end of the connection (speed/mode/fact).
4. Check the LED status.
Use the following commands to verify the port status and link information. They indicate if a port has
a physical link and how many times the link state has changed. Enter:
/info/link
/stats/port #/link
Note:

Troubleshooting Fundamentals and Techniques
>> Main# /info/link

------------------------------------------------------------------------
Alias Port Speed Duplex Flow _Ctrl Link
------- ----- ------- -------- -TX--- -RX--- -----
1 1 10/100 any yes yes disabled
9 9 100 full yes yes up
10 10 100 full yes yes up
11 11 10/100 any yes yes
Diagnosing Connectivity Issues

This section describes how to diagnose connectivity issues (non-stable port connections).
To diagnose connectivity issues

1. Check port error statistics and look for error counters. Enter:
/stats/port <#>/ether
/stats/port <#>/if
2. Check the link on either end (see Diagnosing Link (Layer 1) Issues)
3. Check the STP states. Enter:
/info/l2/stg
4. Note changes after connecting or disconnecting the cable and/or resetting the switch.
Diagnosing Layer 2 Issues

This section describes how to verify VLAN, STG, and trunk configuration.
Note: By default, all ports are part of VLAN 1.

To verify VLAN, STG, and trunk configuration

1. Ensure that VLAN tagging is enabled if there are multiple VLANs running over a single link.
2. Verify that VLANs are correctly set.
>> Main# /info/l2/vlan

VLAN Name Status BWC Learn Ports
---- --------------------- ------ -- ----- -----
1 Default VLAN dis 1024 dis 1-8, 11-23, 25-28
130 130 subnet ena 1024 ena 9 10 24
4090 SSL VLAN ena 1024 ena empty
3. Verify that VLAN tagging is enabled.
/info/port
Alias Port Tag RMON PVID BWC NAME VLAN(s)
---- ---- --- ---- ---- --- ------------------- -------------
1 1 n d 1 3 1
2 2 n d 1 3 1
3 3 n d 1 4 1
4 4 n d 1 4 1
5 5 n d 1 1024 1
6 6 n d 1 1024 1
7 7 n d 1 1024 1
8 8 n d 1 1024 1
9 9 n d 130 1024 OCS Server 1 130
10 10 n d 130 1024 OCS Server 2 130
11 11 n d 1 1024 1
12 12 n d 1 1024 1
13 13 n d 1 1024 1
14 14 n d 1 1024 1
15 15 n d 1 1024 1
16 16 n d 1 1024 1
Caution: If there is any ingress traffic seen without tagged frames, it is isolated to VLAN 2 and
results in loss of service.

1. Verify the spanning tree status. If an incorrect port state is indicated, correct the STP issue by
modifying the bridging priorities or by disabling STP if not needed.
>> Main# info/l2/stg

-----------------------------------------------------------------
Spanning Tree Group 2: Off (STP/PVST), FDB aging timer 300
VLAN(s): 130
Port Priority Cost State Designated Bridge Des Port
----- -------- ---- ------ ----------------- ----------------
9 0 0 FORWARDING *
10 0 0 FORWARDING *
24 0 0 FORWARDING *
* = STP turned off for this port.
-----------------------------------------------------------------
Spanning Tree Group 3: On (STP/PVST)
VLAN(s): 1
Current Root Path-Cost Port Hello MaxAge FwdDel Aging

8000:00:01:81:2e:bc:50 0 (null) 2 20 15 15
Parameters: Priority Hello MaxAge FwdDel Aging

32768 2 20 15 300
2. Check the mode of the STP (PVST/MSTP/RSTP) running on the Alteon platform and on the
network. If it is MSTP mode, ensure that the VLAN to STG association is consistent.
3. Check that the MAC address appears on the correct port. For example:
>> Main# /maint/fdb/dump

MAC address VLAN Port Trunk State Referenced SPs Learned port
-------------- ---- ---- ----- ----- -------------- ----------
--
00:0e:62:77:60:82 130 1 TRK 1 2 24
00:11:0a:ea:ea:f3 130 1 TRK 1 2 24
00:11:85:d3:17:72 130 1 TRK 2 24
00:14:5e:6b:8a:bd 130 1 TRK 2 24
4. Verify the physical address of an Alteon platform and to rule out IP conflict.
/maint/arp/dump
Diagnosing Network (Layer 3) Issues

This section describes how to diagnose network (Layer 3) issues.

To diagnose Layer 3 issues

1. Verify the following:
— The interfaces are up and assigned to the correct VLAN.
— The multiple gateways are up, and the metric used for the gateways is appropriate.
— The local networks are defined for any route or interface. Verify that they are defined for all
interfaces and each static route. Otherwise, all non-local network-defined traffic is sent to
the default gateway.
— The IP forwarding is on.
For example:
>> Main# info/l3/ip

IP information:
AS number 0
Interface information:
1: IP4 192.168.0.45 255.255.255.0 192.168.0.34, vlan 130, up
Default gateway information: metric strict

1: 192.168.0.1 vlan any, up
Current IP forwarding settings: ON, dirbr disabled, noicmprd disabled,

rtcache enabled
Current local networks:

None
------------------------------------------------------------------
Current IPv6 local networks:
Current IP port settings:

All other ports have forwarding ON
Current network filter settings:

none
2. Verify that the routing table is using the correct next hops and interfaces. Also, ensure that local
networks are defined for each static route, and that the routes for dynamic networks appear in
the routing table.
For example:
>> Main# /info/l3/route/dump

Status code: * - best
Destination Mask Gateway Type Tag Metr If

------------ -------------- ---------- ------- ------ ---- --
0.0.0.0 0.0.0.0 192.168.0.1 indirect static 1
127.0.0.0 255.0.0.0 0.0.0.0 martian martian
192.168.130.45 255.255.255.0 192.168.130.45 direct vip
3. Verify that a Virtual Router (VR) is set up as the master for all VRs to ensure that routing occurs
through the same Alteon platform.

4. To display VRRP information, enter /info/l3/vrrp
Note: You do not need to verify a VR if Direct Access Mode (DAM) and Virtual Matrix
Architecture (VMA) are disabled, and sharing is enabled for the VR. The backup Alteon platform
can perform dumb server processing where all RIP traffic for a load-balanced service is RIP to
VIP translated.
5. To view ARP Information, use the following syntax:
/info/l3/arp/find|port|vlan|addr|dump
6. To view the OSPF Routing Information, use the following syntax:
/info/l3/odpf/general|aindex|…|dump
7. To dump all Layer 3 Information, enter /info/l3/dump
Diagnosing SLB (Layer 4) Issues

This section describes how to diagnose SLB and other Layer 4 issues.

1. Verify that SLB is turned on.
>> Main# /cfg/slb/on

Current status: ON
New status: ON
2. Verify the following:

— Real servers are enabled.
— Which services are failed or blocked. Blocked services indicate that another real service is
failing a health check within the same group.
— Real servers for redir filters are up.
— The correct Layer 4 process (client, server, proxy, hot-standby, Interswitch, and filtering) is
enabled for the port, and the correct filters are added, including allow filters for health
checks.
— Service status. If a service is down, ensure that its associated real server status is up and
functioning.
— Real servers are passing health checks. If a health check fails, do the following:
• Confirm the appropriate gateway on the real server. The gateway needs to be the device
interface or the next hop towards the Alteon platform.
• Confirm that health check replies are forwarded out to the appropriate interface for a
multi-homed real server.
• Confirm that there are no routing loops between the real server and the Alteon platform.
• Confirm that the health check replies are not redirected by an application redirection
filter.

>> Main# /info/slb/dump

Real server state:
1: OCSfrontend1, 00:14:5e:95:a4:ad, vlan 130, port 9, health 4, up
Real server group 1, Workload Manager none
Virtual Services:
5061: vport 5061, rtspslb none
virtual server: 1, IP4, 192.168.130.45
Virtual server state:

1: IP4, 192.168.130.45, 00:01:81:2e:bc:5e, cont 1024
virtual ports:
5061: rport 5061, group 1, OCS2007Pool, backup none, rtspslb none
real servers:
1: OCSfrontend1, backup none, 162 ms, group ena, up
Diagnosing Layer 7 Issues

This section describes how to diagnose Layer 7 issues.

1. Check SSL ID persistency.
Sniff the connection and check the server logs for the SSL IDs. Correlate this information. For
example, if a client sends traffic to Alteon, check the initial request to the real server coming on
a 0-valued session ID. The server issues an SSL ID back to the client. As long as the client uses
the same SSL ID for incoming connections, the session is bound to the same real server. If there
is a change to the SSL ID (due to a client or server issue), it is easily captured in the sniffer
traces.
2. Check URL parsing.
Configure strings. Map the requests and verify them using a sniffer to ensure that the correct
content is specified.
3. Run script and content-based health checks.
Check if there is any configuration error in the script or content. Verify the script using a Telnet
client to ensure that you are getting a 200 ok (or the expected response in the script) back from
the server.
4. Check DNS-based load balancing.
Verify the string associated with the DNS specified name.
5. Check URL hashing and header hash load balancing.
Verify if the server is overloaded and if it is required to increase the number of servers in the
pool.


Chapter 5 – Troubleshooting Hardware Issues
This chapter describes how to troubleshoot hardware issues. It includes the following topics:
• LED Indicators, page 79
• CPU Temperature, page 79
• Fan Failure, page 79
• Alteon 10000 Hardware Issues, page 80
For hardware component replacement procedures and system recovery procedures, see the Alteon
Installation and Maintenance Guide.
LED Indicators
The following describes the LED indicators found on the front panel of the Alteon platforms.
• PWR (on platforms with dual power supplies: PWR 1 and PWR 2) )— Green indicates normal
operation. Red indicates a failure in the power supply (or in one of the dual power supplies, 1 or
2, respectively) or in the power supply cables or power source.
Note: In an Alteon 4408 carrying dual power supplies, the PWR indicator remains green as
long as one of the power supplies remains working, even if the second power supply fails.
• FAN — Green indicates normal operation. Red indicates that one or more fans are not operating.
Note: There is no FAN indicator on the Alteon 4408 platform.

• SYS OK— Green indicates normal operation. Red indicates that the Alteon platform is booting.
Red or alternating red and green indicates a warning.
CPU Temperature
Alteon sends a warning message if any of the temperature sensors exceeds the temperature
threshold. The Alteon platform shuts down if the power supply overheats and the temperature gets
to the critical temperature of the platform.
Fan Failure
There are a number of internal fans within the Alteon platform. Some fans are defined as critical and
others as non-critical.
• If a non-critical fan fails, the platform will continue to work as normal and no action is needed.
• If a critical fan fails, it is recommended to contact Radware Support as soon as possible.
The number of fans and the fan ID numbers are different per platform.
All fans in the platform are polled periodically and a trap/syslog message is sent if a fan fails or
returns to operational state.
If a critical fan fails, critical trap message is sent periodically until the fan is back and operational.

Troubleshooting Hardware Issues
For example:
<Date and Time> CRITICAL system: critical fan <n> is not operational
<Date and Time> NOTICE system: critical fan <n> is now operational
The operational status of the fans can also be viewed using the CLI command info/sys/fan.
This command displays a table listing all the fans on the platform, indicating if the fans are critical or
non-critical, and the fan status is displayed as either operational or failed.
In addition, the red fan LED on the front panel of the Alteon platform indicates if a fan is not
operating.
Alteon 10000 Hardware Issues

For details on configuring and monitoring the Alteon Application Switch 10000 components, refer to
the dedicated appendix for the Alteon Application Switch 10000 in the Radware Alteon Application
Switch Operating System Command Reference.
This section includes the following topics:
• Alteon 10000 LED Indicators, page 81
• IPMI Connectivity, page 82
• Fan Tray, page 82
• Power Supply, page 82
• Switch Blade, page 83
• Switch Extension, page 83
• Payload Blades, page 83

Alteon 10000 LED Indicators

The following LED indicators are on the front panels of the Alteon 10000 modules.
Status LEDs on the switch, switch extension and payload blades:

• OOS— Out of Service. Red indicates that the platform is booting.
• IS— In service. Green indicates normal operation.
• ATTN— Attention. Warning indicator.
• H/S — Hot Swap:
— Blue — ready to be removed from the shelf.
— Long blink — activating.
— Short blink — deactivation requested.
Alteon 10000 NEBS Shelf Manager LED indicators:
• CRIT — Critical alarm (red).
• MAJ — Major alarm (red).
• MIN — Minor alarm (yellow).
• OOS — Out of Service (red).
• IS — In Service (green).
Alteon 10000 Shelf Manager status LED indicators:

• PWR — Power.
• ACT —Alarm Cut-Off.
• MNR — Minor alarm (yellow).
• MJR — Major alarm (red).
• CRT — Critical alarm (red).
Status LEDs on the Switch Module rear panel:
• OOS—Out of Service (red).
• IS—In service (green).
• ATTN— Attention (yellow).
On the Alteon 10000 model only.
FAN STATUS—Green indicates normal operation. Red indicates that
one or more fans is not operating.

IPMI Connectivity
In some cases, the system might experience broadcast storms and network loops as a result of
software malfunctions and/or poor administration. The system, in these cases, experiences
instability and the loss of Intelligent Platform Management Interface (IPMI) connectivity, resulting in
payload blade disconnect. By default, if for any reason a payload blade disconnects from the system
it will not be re-introduced into service unless specifically added by the user (because of the default
preemption settings). This behavior is a way to protect and limit the effect the hash function has on
the service.
An IMPI disconnect is not due to either poor maintenance or payload blade failure, and therefore
performs a self-recovery procedure independent of preemption, as follows:
1. IPMI connectivity loss is treated as a network loop.
2. As a result, the system is operationally disables all external ports.
3. The system issues the following message to all available outlets:
"Feb 15 11:27:37 System: Due to a network loop, critical components are
experiencing loss of connectivity. All external links are temporarily
disabled"
4. External connectivity is now restored after five minutes, or manually restored by the
administrator, (also see the /oper/reconn command in the Alteon Application Switch
Operating System Command Reference) and the following occurs:
— If the issue is yet to be resolved, the ports shut down once again.
— If the issue is resolved, the payload blades are re-introduced into service regardless of the
preemption settings.
Fan Tray
If the fan tray fails, traffic is not affected. Failover to the secondary system does not occur unless
the system overheats and fails.
The following message is issued to both the console and system log every 30 seconds:
Warning: Fan Tray # Failed and is out of order, system temperature is # degrees.
If the system temperature crosses the safe range, the following warning message is issued:
Warning: Fan Tray # Failed and is out of order, system temperature is # degrees and above the
system's safe temperature.
Power Supply
If a power supply fails, and if all blades are being used, the system performs a failover if the
available power supplies cannot carry the system.
The following error message is issued to both the console and system log:
Error: "System Name" PS # failed causing a system failover
If a power supply fails without causing a failover, the following warning message is issued to both
console and system log:
Warning: "System Name" PS # failed.
In this scenario, the system does not shut down, but rather shuts down all non-essential payload
blades in order for the system to operate with minimal power consumption and for the administrator
to monitor the system and troubleshoot the failure.

Switch Blade
Failure of a switch blade causes a system failure and immediately leads to a failover all services to
the secondary system.
Switch Extension
A switch extension failure causes a 50% drop in system total throughput capacity.
An error message is sent to both the console and the system log.
Removing the switch extension causes failure only for the connected links, so that if a connected
network device multiple links failure does not occur, there is failover instead to the secondary or
shared link.
Note: In some cases, removing or inserting a switch extension blade may result in an “empty”
status of the payload blade. If this occurs, extract and re-insert the payload blade.
Note:
Payload Blades
Introducing a new payload blade into an active system does not automatically introduce the blade
into service unless specifically activated by the administrator.
To activate a new payload blade

Enter the following commands:
/cfg/pblade/ena
apply
save
If a payload blade fails, the remaining payload blades continue to function without causing a
complete system failure. New connections are distributed based on the available blades.
Open connections are disturbed as little as possible by re-arranging the hash function to maintain
the previous connections with the previous SPs.
No configuration is required to achieve redundancy with the payload blades. VRRP perceives the
payload blades as transparent.
Hot Swapping Payload Blades

The Alteon 10000 uses a star architecture, letting you introduce processing resources without
physical wiring, where you can add or remove a payload blade without affecting connected
applications. This is achieved by taking advantage of multiple and concurrent payload blade
distribution tables, letting you control the time the tables will be merged and to maintain a single
distribution table, optimizing system resources.


Chapter 6 – Troubleshooting Scenarios
This chapter describes some common troubleshooting scenarios including their possible causes and
solutions.
Troubleshooting Table
Table 2: Troubleshooting Table
Problem Possible Cause Solution

The CLI command prompt The operating system may Recover the Alteon software.
does not appear after the have been damaged.
establishment of a
connection through the
console, Telnet, or SSH.
Alteon is unable to contact There may be a problem with Ensure that the network connection and
the specified FTP/TFTP the network connection, the FTP/TFTP server are functioning
server and download files. FTP/TFTP server, or with the properly. The FTP/TFTP server can fail if
software. a network connection is tried through a
data port but they can also be reached
through the management port.
If the problem is with the software,
perform a serial upgrade of the
software.
Alteon cannot install an Either there is no valid Remove the TAR files from the USB
application, an error application found, the TAR file device. Add a new TAR file to the USB
message is issued, and the on the USB device includes an and reboot.
Alteon platform powers invalid application, or there is If the error persists, it is a hardware
off. a hardware problem. issue. Contact Radware Technical
Support.
Alteon tries to run an Either there is an invalid BIOS Remove the TAR files from the USB
application, but resets. or there is a hardware device. Add a new TAR file to the USB
problem. and reboot.
If the error persists, it is a hardware
issue. Contact Radware Technical
Support.
The application started, There is a minor mismatch in Restart the Alteon platform.
but a warning was printed. configuration. An ordinary upgrade process is also
available.
Poor performance. The same core is used for Reconnect the cables to dedicated cores
uplink and downlink. for uplinks and downlinks.

Troubleshooting Scenarios

Chapter 7 – Emergency Recovery Tree
This chapter includes a set of work-flows to assist in emergency field support issues:
• Cannot Access AlteonOS for Management, page 87
• VIP is Not Working, page 88
• Interface is Down, page 94
• VRRP is Flapping, page 95
• High MP CPU Utilization, page 99
• Gateway Failure, page 100
• Panic, page 101
• Real Server Down, page 102
Cannot Access AlteonOS for Management

The following is the emergency recovery workflow when the operating system is not available for
management.

Emergency Recovery Tree
VIP is Not Working

The following is the emergency recovery workflow when a VIP is not working.






Interface is Down
The following is the emergency workflow for when an interface goes down.

VRRP is Flapping
The following is the emergency workflow for diagnosing VRRP issues.




High MP CPU Utilization

The following is the emergency work flow for high MP CPU usage.

Gateway Failure
The following is the emergency recovery tree for gateway failure.

Panic
The following is the emergency workflow for panics.

Real Server Down

The following is the emergency workflow for when a real server becomes unavailable.





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. Lab/Development License. Notwithstanding anything to the contrary in this License
Agreement, if the Software is provided to you for use in your lab or for development
purposes, as indicated in your purchase order, sales receipt, the part number description for the
Software, the Web page from which you download the Software, or otherwise, then You may use
the Software only in your lab and only in connection with Radware Products that you purchased
or will purchase (in case of a lab license) or for internal testing and development purposes (in
case of a development license) but not for any production use purposes.
4. 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.
5. 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 5 will survive
the termination or expiration of this Agreement.
6. 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,
except and only to the extent: (i) applicable law expressly permits any such action despite this
limitation, in which case 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 (ii) required to
debug changes to any third party LGPL-libraries linked to by the Software; 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 the
foregoing, 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. Human readable Software to which this prohibition applies includes
(without limitation) “Radware AppShape++ Script Files” that contain “Special License Terms”. It
is acknowledged that examples provided in a human readable form may be modified by a user.
7. 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.
8. 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.
9. 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.
10. 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 6 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 6 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.
11. 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 5-15
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 unbundled
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.
12. 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.
13. 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 Software is subject to the terms of this License Agreement.
14. Federal Acquisition Regulation (FAR)/Data Rights Notice. Radware's commercial
computer software is created solely at private expense and is subject to Radware's commercial
license rights.

15. Governing Law. This License Agreement shall be construed and governed in accordance with
the laws of the State of Israel.
16. 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 IMMEDIATELY CEASE USING THE
SOFTWARE.
COPYRIGHT © 2019, Radware Ltd. All Rights Reserved.

AlteonOS 30 5 11 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

AlteonOS 30 5 11 Troubleshooting Guide

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

AlteonOS 30 5 11 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

Alteon

Software Version 30.5.11

2 Document ID: RDWR-ALOS-V30511-TSG1901

Document ID: RDWR-ALOS-V30511-TSG1901 3

4 Document ID: RDWR-ALOS-V30511-TSG1901

Document ID: RDWR-ALOS-V30511-TSG1901 5

6 Document ID: RDWR-ALOS-V30511-TSG1901

This product includes software developed by Simon Wilkinson

Document ID: RDWR-ALOS-V30511-TSG1901 7

Notice traitant du copyright

8 Document ID: RDWR-ALOS-V30511-TSG1901

@author Paulo Barreto <[email protected]>.

Document ID: RDWR-ALOS-V30511-TSG1901 9

10 Document ID: RDWR-ALOS-V30511-TSG1901

Document ID: RDWR-ALOS-V30511-TSG1901 11

12 Document ID: RDWR-ALOS-V30511-TSG1901

Limitations on Warranty and Liability

Document ID: RDWR-ALOS-V30511-TSG1901 13

Limitations on Warranty and Liability

Limitations de la Garantie et Responsabilité

Haftungs- und Gewährleistungsausschluss

14 Document ID: RDWR-ALOS-V30511-TSG1901

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:

Document ID: RDWR-ALOS-V30511-TSG1901 15

This marking or statement includes the following text warning:

16 Document ID: RDWR-ALOS-V30511-TSG1901

Caution – To Reduce the Risk of Electrical Shock and Fire

To connect the power connection:

Document ID: RDWR-ALOS-V30511-TSG1901 17

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

18 Document ID: RDWR-ALOS-V30511-TSG1901

Cette marque ou remarque inclut l’avertissement textuel suivant:

Document ID: RDWR-ALOS-V30511-TSG1901 19

Attention - Pour réduire les risques de chocs électriques et d’incendie

Pour brancher à l’alimentation électrique:

20 Document ID: RDWR-ALOS-V30511-TSG1901

Figure 5: Warnetikett Stromschlaggefahr

SICHERHEITSHINWEIS IN CHINESISCHER SPRACHE FÜR SYSTEME MIT DOPPELSPEISUNG

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

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

Document ID: RDWR-ALOS-V30511-TSG1901 21

22 Document ID: RDWR-ALOS-V30511-TSG1901

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

Anschluss des Stromkabels:

Document ID: RDWR-ALOS-V30511-TSG1901 23

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

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

24 Document ID: RDWR-ALOS-V30511-TSG1901

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: