Administration Guide vA3(1.0), Cisco ACE 4700 Series Application Control Engine Appliance
Preface
Downloads: This chapterpdf (PDF - 159.0KB) The complete bookPDF (PDF - 5.01MB) | Feedback

Preface

Table Of Contents

Preface

Audience

How to Use This Guide

Related Documentation

Symbols and Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Preface


This guide provides instructions for the administration of the Cisco 4700 Series Application Control Engine (ACE) appliance. It describes how to perform administration tasks on the ACE, including initial setup, establish remote access, manage software licenses, configure class maps and policy maps, manage the ACE software, configure SNMP, configure redundancy, configure the XML interface, and upgrade your ACE software.

You can configure the ACE by using the following interfaces:

The command-line interface (CLI), a line-oriented user interface that provides commands for configuring, managing, and monitoring the ACE.

Device Manager graphic user interface (GUI), a Web browser-based GUI interface that provides a graphical user interface for configuring, managing, and monitoring the ACE.

This preface contains the following major sections:

Audience

How to Use This Guide

Related Documentation

Symbols and Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

Audience

This guide is intended for the following trained and qualified service personnel who are responsible for configuring the ACE:

System administrator

System operator

How to Use This Guide

This guide is organized as follows:

Chapter
Description

Chapter 1, Setting Up the ACE

Describes how to configure basic settings on the ACE, including topics such as how to session and log in to the ACE, change the administrative username and password, assign a name to the ACE, configure a message-of-the-day banner, configure date and time, configure terminal settings, modify the boot configuration, and restart the ACE.

Chapter 2, Enabling Remote Access to the ACE

Describes how to configure remote access to the Cisco 4700 Series Application Control Engine (ACE) appliance by establishing a remote connection using the Secure Shell (SSH) or Telnet protocols. It also describes how to configure the ACE to provide direct access to a user context from SSH. This chapter also covers how to configure the ACE to receive ICMP messages from a host.

Chapter 3, Managing ACE Software Licenses

Describes how to manage the software licenses for your ACE.

Chapter 4, Managing the ACE Software

Describes how to save and download configuration files, use the file system, view and copy core dumps, capture and copy packet information, use the configuration checkpoint and rollback service, display configuration information, and display technical support information.

Chapter 5, Viewing ACE Hardware and Software Configuration Information

Describes how to display ACE hardware and software configuration information, and display technical support information.

Chapter 6, Configuring Redundant ACE Appliances

Describes how to configure the ACE for redundancy, which provides fault tolerance for the stateful failover of flows.

Chapter 7, Configuring SNMP

Describes how to configure Simple Network Management Protocol (SNMP) to query the ACE for Cisco Management Information Bases (MIBs) and to send event notifications to a network management system (NMS).

Chapter 8, Configuring the XML Interface

Describes how to provide a mechanism using XML to transfer, configure, and monitor objects in the ACE. This XML capability allows you to easily shape or extend the CLI query and reply data in XML format to meet different specific business needs.

Appendix A, Upgrading or Downgrading Your ACE Software

Describes how to upgrade or downgrade the software on your ACE.


Related Documentation

In addition to this document, the ACE documentation set includes the following:

Document Title
Description

Release Note for the Cisco 4700 Series Application Control Engine Appliance

Provides information about operating considerations, caveats, and command-line interface (CLI) commands for the ACE.

Cisco Application Control Engine Appliance
Hardware Installation Guide

Provides information for installing the ACE appliance.

Regulatory Compliance and Safety Information for the Cisco Application Control Engine Appliance

Regulatory compliance and safety information for the ACE appliance.

Cisco 4700 Series Application Control Engine Appliance Quick Start Guide

Describes how to use the ACE appliance Device Manager and CLI to perform the initial setup and VIP load-balancing configuration tasks.

Cisco 4700 Series Application Control Engine Appliance Virtualization Configuration Guide

Describes how to operate your ACE in a single context or in multiple contexts.

Cisco 4700 Series Application Control Engine Appliance Routing and Bridging Configuration Guide

Describes how to perform the following routing and bridging tasks on the ACE:

Configuring Ethernet ports

Configuring VLAN interfaces

Configuring routing

Configuring bridging

Configuring Dynamic Host Configuration Protocol (DHCP)

Cisco 4700 Series Application Control Engine Appliance Server Load-Balancing Configuration Guide

Describes how to configure the following server load-balancing tasks on the ACE:

Real servers and server farms

Class maps and policy maps to load-balance traffic to real servers in server farms

Server health monitoring (probes)

Stickiness

Firewall load balancing

TCL scripts

Cisco 4700 Series Application Control Engine Appliance Application Acceleration and Optimization Configuration Guide

Describes the configuration of the application acceleration and optimization features of the ACE. It also provides an overview and description of those features.

Cisco 4700 Series Application Control Engine Appliance Security Configuration Guide

Describes how to perform following ACE security configuration tasks:

Security access control lists (ACLs)

User authentication and accounting using a Terminal Access Controller Access Control System Plus (TACACS+), Remote Authentication Dial-In User Service (RADIUS), or Lightweight Directory Access Protocol (LDAP) server

Application protocol and HTTP deep packet inspection

TCP/IP normalization and termination parameters

Network address translation (NAT)

Cisco 4700 Series Application Control Engine Appliance SSL Configuration Guide

Describes how to configure the following Secure Sockets Layer (SSL) tasks on the ACE:

SSL certificates and keys

SSL initiation

SSL termination

End-to-end SSL

Cisco 4700 Series Application Control Engine Appliance System Message Guide

Describes how to configure system message logging on the ACE. This guide also lists and describes the system log (syslog) messages generated by the ACE.

Cisco 4700 Series Application Control Engine Appliance Command Reference

Provides an alphabetical list and descriptions of all CLI commands by mode, including syntax, options, and related commands.

Cisco 4700 Series Application Control Engine Appliance Device Manager Configuration Guide

Describes how to use the Device Manager GUI, which resides in flash memory on the ACE, to provide a browser-based interface for configuring and managing the appliance.

Cisco CSS-to-ACE Conversion Tool User Guide

Describes how to use the CSS-to-ACE conversion tool to migrate Cisco Content Services Switches (CSS) running-configuration or startup-configuration files to the ACE.


Symbols and Conventions

This publication uses the following conventions:

Convention
Description

boldface font

Commands, command options, and keywords are in boldface. Bold text also indicates a command in a paragraph.

italic font

Arguments for which you supply values are in italics. Italic text also indicates the first occurrence of a new term, book title, emphasized text.

{   }

Encloses required arguments and keywords.

[   ]

Encloses optional arguments and keywords.

{x | y | z}

Required alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

screen font

Terminal sessions and information the system displays are in screen font.

boldface screen font

Information you must enter in a command line is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

^

The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key.

<   >

Nonprinting characters, such as passwords are in angle brackets.


Notes use the following conventions:


Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication.


Cautions use the following conventions:


Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Warnings use the following conventions:


Warning Means possible physical harm or equipment damage. A warning describes an action that could cause you physical harm or damage the equipment.


For additional information about CLI syntax formatting, see the Cisco 4700 Series Application Control Engine Appliance Command Reference.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Open Source License Acknowledgements

The following acknowledgements pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

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 openssl-core@openssl.org.

OpenSSL License:

© 1998-1999 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 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 acknowledgment: "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 openssl-core@openssl.org.

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 (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

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 adhered 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 (tjh@cryptsoft.com).

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.

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 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 cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

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 license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].