Table of Contents

About This Guide

Document Objectives
Audience
Document Organization
Document Conventions
Getting More Information

About This Guide

This section describes the objectives, audience, organization, and conventions of the Cisco AS5200 Universal Access Server Software Configuration Guide.

Cisco documentation and additional literature are available on a CD-ROM called Cisco Connection Documentation, Enterprise Series. The CD is updated and shipped monthly, so it might be more current than printed documentation. To order the CD, contact your local sales representative or call Cisco Customer Service. The documentation CD is available both as a single CD and as an annual subscription. You can also access Cisco technical documentation on the World Wide Web URL http://www.cisco.com.

Document Objectives

This software configuration guide explains how to configure your access server for the most common scenarios. It does not cover every feature, but does describe in detail those tasks most commonly required to configure the access server. This guide also references detailed features described in the Cisco IOS configuration guides and command references. Refer to these other books for additional information.

Audience

This guide is intended primarily for the following audiences:

• Customers who know one networking protocol (such as IP) and one LAN protocol (such as Ethernet), but have no additional networking background or experience
  

• Customers who support dial in users, but who have little experience with router-based networks
  

• System administrators who are familiar with the fundamentals of router-based internetworking and who are responsible for installing and configuring internetworking equipment, but who might not be familiar with the specifics of Cisco products or the routing protocols supported by Cisco products
  

Document Organization

This guide has four chapters, as follows:

• Chapter 1, "Starting Up Your Access Server for the First Time"
  

• Chapter 2 "Working with Your Access Server for the First Time"
  

• Chapter 3, "Configuring for ISDN and Analog Calls"
  

• Chapter 4, "Configuring Access Service Security"
  

Document Conventions

Software and hardware documentation uses the following conventions:

• The caret character (^) represents the Control key.
  

For example, the key combinations ^D and Ctrl-D are equivalent: Both mean hold down the Control key while you press the D key. Keys are indicated in capitals, but are not case sensitive.

• A string is a nonquoted set of characters.
  

For example, when setting an SNMP community string to "public," do not use quotation marks around the string or the string will include the quotation marks.

Command descriptions use these conventions:

• Vertical bars ( | ) separate alternative, mutually exclusive, elements.
  

• Elements in square brackets ([ ]) are optional elements.
  

• Braces ({ }) indicate a required choice.
  

• Braces within square brackets ([{ }]) indicate a required choice within an optional element.
  

• Commands and keywords in boldface font.
  

• Variables for which you supply values are in italic font; in contexts that do not allow italics, arguments are enclosed in angle brackets (< >).
  

Examples use these conventions:

• Examples that contain system prompts denote interactive sessions, indicating that the user enters commands at the prompt. The system prompt indicates the current command mode. For example, the following prompt indicates global configuration mode:
  

Router(config)#

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

• Information you enter is in boldface screen font.
  

• Nonprinting characters, such as passwords, are in angle brackets (< >).
  

• Default responses to system prompts are in square brackets ([ ]).
  

• Exclamation points (!) at the beginning of a line indicate a comment line. They are also displayed by the Cisco IOS software for certain processes.
  

Interactive examples showing prompts ( 5200(config-line)# ) are used in procedures to show exactly what the prompt should look like when you enter a command and exactly what happens after you enter a command. Examples showing only sample output from a show running-config or show startup-config (without prompts) are shown at the end of each chapter in the configuration example sections.