This section discusses the objectives, audience, organization, and conventions of the Cisco Access Connection Guide.
All Cisco technical documentation and additional literature are available UniverCD, Cisco's online library of product information. UniverCD is updated and shipped monthly, so it might be more up to date than printed documentation. UniverCD is available both as a single CD and as an annual subscription. To order UniverCD, contact your local sales representative or call Customer Service.
This publication explains how to use an access server or a router to connect to network hosts. It also describes how to manage and monitor network connections and how to change terminal parameters. For information about configuring these products, refer to the appropriate product configuration guide.
Note The term
server product is used globally throughout this publication to refer to products that support access server (Cisco 2500 and AS5100) and router functionality. Some connection features can be supported only on an access server, or only on a router. In such cases, notes are included in the descriptions to specify whether the features apply to access servers or to routers.
This publication is for network managers, system administrators, sophisticated users, and operators who perform connection and connection-management tasks.
This publication contains seven chapters and an appendix that discuss the following topics:
- Chapter 1, "Overview," describes the connection features supported on your server product to connect terminals, modems, microcomputers, and networks over serial lines to local-area networks (LANs) or wide-area networks (WANs), lists the supported transmission protocols and media, and provides a configuration overview.
- Chapter 2, "Understanding the User Interface," explains how to enter commands and how to get context-sensitive help about connection commands.
- Chapter 3, "Terminal Service Connections," explains how to connect from your host running terminal-emulation software such as Telnet, rlogin, TN3270, or Local Area Transport (LAT) through one of our server products to a host on a LAN or WAN.
- Chapter 4, "Remote Node Service Connections," describes how to use one of our server products to connect devices across a telephone network using SLIP, PPP, or XRemote (NCD's X Windows terminal protocol).
- Chapter 5, "Terminal or Remote Node Service Connections Using Protocol Translation," describes the methods you can use to connect a host running one protocol (such as Telnet with TCP/IP) to a host running another protocol (such as LAT). It also describes the two types of protocol translation connections you can make for each of the supported protocols, and describes how to make X.3 PAD connections during protocol translation sessions involving X.25.
- Chapter 6, "Monitoring and Managing Connections," contains information about managing and monitoring open connections.
- Chapter 7, "Changing Terminal Parameters," describes how to change terminal and line settings locally.
- Appendix A, "ASCII Character Set," provides an ASCII-to-decimal translation table.
This document uses the following conventions:
- In text references, "Ctrl-" represents the key labeled Control. The key combination Ctrl-D means hold down the Control key while you press the D key.
- In screen output examples showing two caret (^^) symbols together, the first caret represents the Control key, and the second caret represents the keystroke sequence Shift-6. The double caret combination (^^) means hold down the Control key while you press the Shift and the 6 key.
- A string is defined as a nonquoted set of characters. For example, when setting up a community string for SNMP to "public," do not use quotes around the string, or the string will include the quotation marks.
Command descriptions use these conventions:
- Vertical bars ( | ) separate alternative, mutually exclusive, elements.
- Square brackets [ ] indicate optional elements.
- Braces { } indicate a required choice.
- Braces within square brackets [{ }] indicate a required choice within an optional element.
- Boldface indicates commands and keywords that are entered literally as shown.
- Italics indicate arguments for which you supply values; 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 prompt router(config)# indicates global configuration mode.
- 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 access server for certain processes.
Note Means
reader take note. Notes contain helpful suggestions or references to materials not contained in the manual.
