- Terminal Services Overview
- Configuring Terminal Operating Characteristics for Dial-In Sessions
- Configuring Dial-In Terminal Services
- Cisco IOS Software Feature Removal
- Configuring AppleTalk Remote Access
- Configuring the Cisco PAD Facility for X.25 Connections
- PAD Subaddress Formatting Option
- Configuring Protocol Translation and Virtual Asynchronous Devices
- Authorization for Protocol Translation
- End-of-Record Function for DCNs
- Protocol Translation Ruleset
- Regular Expressions
- X.3 PAD Parameters
- ARA Overview
- ARA Configuration Task List
- Making ARA Connections
- Monitoring an ARA Server
- Monitoring the AppleTalk Network
- Troubleshooting ARA Connections
- ARA Configuration and Connection Examples
- ARA Server Configuration Procedure
- Dedicated ARA Line with User Authentication Example
- Autostart Multiple ARA Lines with User Authentication Example
- Telebit T-3000 Modem Setup Procedure
- Modified and Unmodified CCL Scripts Sample Commands
- ARA Router Support Example
- Extended AppleTalk Network Example
- Cable Range Expansion Example
- Extended Network in Discovery Mode Example
- TACACS Username Authentication Example
- TACACS Enabled for ARA Authentication Example
- AppleTalk Network Connection over a Foreign Protocol Example
Configuring AppleTalk Remote Access
This chapter describes how to configure your router to act as an AppleTalk Remote Access (ARA) server. It includes the following main sections:
- ARA Overview
- ARA Configuration Task List
- Making ARA Connections
- Monitoring an ARA Server
- Monitoring the AppleTalk Network
- Troubleshooting ARA Connections
- ARA Configuration and Connection Examples
This chapter does not describe how to configure or use the client Macintosh. Refer to the Apple Computer, Inc. Apple Remote Access Client User’s Guide and the Apple Remote Access Personal Server User’s Guide for information about how to set up and use the ARA software on your Macintosh.
For a complete description of the commands in this chapter, refer to the Cisco IOS Terminal Services Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release.
ARA Overview
The Cisco implementation of ARA gives Macintosh users direct access to information and resources in remote AppleTalk networks over standard telephone lines. For example, if you have a PowerBook at home and need to get a file from your Macintosh at the office, ARA software can make the connection between your home and office computers over telephone lines.
You can configure your router to act as an ARA server by enabling AppleTalk and ARA protocol on physical terminal (TTY) or virtual terminal lines. Configuring your router to act as an ARA server allows remote Macintosh users to dial in, become a network node, and connect to devices on other networks. ARA protocol support is transparent to the Macintosh end user. Macintosh users can also use Serial Line Internet Protocol (SLIP) to access remote IP network resources and PPP to access both AppleTalk and IP resources.
The following Macintosh and Cisco IOS software support is required for ARA connectivity:
- Macintosh running ARA software and a connection control language (CCL) script.
- Router configured as an ARA server.
Figure 1 shows how your router can act as an ARA server between remote Macintosh computers (in Figure 1, a Power Macintosh and a PowerBook) and devices on another network.
Figure 1 ARA Configuration Overview
ARA Configuration Task List
To set up the Cisco IOS software to act as an ARA server, perform the tasks described in the following sections:
- Connecting Cables (Required)
- Configuring the Line and the Modem (Required)
- Configuring ARA (Required)
- Configuring ARA to Start Up Automatically (Optional)
- Configuring ARA Security (Optional)
- Connecting to an AppleTalk Network from a Client Running a Different Virtual Terminal Protocol (Optional)
To enable remote clients running PPP to dial in and access AppleTalk resources on a network, you must configure AppleTalk Control Protocol (ATCP). To configure ATCP, refer to “ Configuring Asynchronous SLIP and PPP ” in the Cisco IOS Dial Technologies Configuration Guide.
The section “Making ARA Connections” later in this chapter provides connection information. Refer to the “Monitoring an ARA Server,” “Monitoring the AppleTalk Network,” and “Troubleshooting ARA Connections” sections for information about maintaining and troubleshooting the ARA server and AppleTalk network. The section “ARA Configuration and Connection Examples” provides configuration examples.
Connecting Cables
Figure 2 shows how to connect a Macintosh using internal and external modems.
Figure 2 ARA Server Cabling and Connections
Use the MMOD version of the RJ-45-to-DB-25 adapter (labeled “Modem” if the adapter is from Cisco) to connect a “rolled” RJ-45 cable from the router to the modem. Use a high-speed modem cable with hardware flow control to connect a modem to your Macintosh (see the user documentation for your modem for more specific information).
Some Cisco access servers such as the Cisco AS5800 and Cisco AS5300 have internal modems. Therefore there are no modem cables for you to connect.
For more information about connecting cables, see the installation and configuration or product user guide that came with your router.
Configuring the Line and the Modem
To configure the line, perform the following steps:
Step 1
Specify the maximum common line speed for the modem and the access server. The access server supports 4-fold compression of data, so you can use the speeds shown in the following list:
- 115,200 bits per second (bps) for use with modems that support a transmission rate of 28,800
- 57,600 bps for use with modems that support a transmission rate of 14,400
- 38,400 bps for use with modems that support a transmission rate of 9,600
Note See your modem guide to ensure that the modem can support these maximum line speeds.
Step 2 Set hardware flow control. Use the flowcontrol hardware command to enable hardware flow control.
Note The Cisco IOS software does not support modems that do not support hardware flow control.
Step 3 Specify your modem control parameters. Use the modem inout command to configure the line for both incoming and outgoing calls, or use the modem dialin command to configure the line for incoming calls only.
Step 4 Configure security on your dial-in lines. Use the aaa new-model command to enable the authentication, authorization, and accounting (AAA) process on the router, the aaa authentication arap command to create an authentication list, and the arap authentication command to apply the authentication list to a line or set of lines configured for ARA.
For more information about configuring lines and modem control, refer to Cisco IOS Dial Technologies Configuration Guide. For information about configuring security, refer to Cisco IOS Security Configuration Guide.
Note The autobaud command is not supported with ARA and should never be used.
Configuring ARA
To allow ARA connections to pass through the access server or router, use the following commands beginning in global configuration mode:
|
|
|
|
|---|---|---|
Enables AppleTalk.1 |
||
Router(config)# arap network [ network-number ] [ zone-name ] |
Creates a new network or zone for ARA clients when they dial in. The network-number argument must be a unique network number. |
|
In interface configuration mode, ensures that a new internal network is advertised by enabling the Routing Table Maintenance Protocol (RTMP). You need to configure an AppleTalk interface using the discovery mode in the Cisco IOS software. To do so, an interface on the router must be connected to a network that has at least one other router configured for AppleTalk. |
||
Returns to global configuration mode and turns on AppleTalk routing. |
||
Router(config)# line [ tty | aux | vty ] line-number [ ending-line-number ] |
||
|
1.For more information about configuring AppleTalk, refer to Cisco IOS AppleTalk and Novell IPX Configuration Guide. |
If you discover that an AppleTalk network already exists, the zone and cable range must match the existing configuration. To identify existing cable ranges and zone names, configure the Cisco IOS software for discovery mode. You must manually configure an AppleTalk interface on a segment for which there are no AppleTalk routers. For more information, refer to Cisco IOS AppleTalk and Novell IPX Configuration Guide.
Configuring ARA to Start Up Automatically
Refer to this section after you have configured AppleTalk routing, created an internal ARA network or zone, and enabled ARA. At this point, you can enable optional tasks.
To configure the Cisco IOS software to allow an ARA session to start automatically, use the following commands beginning in global configuration mode:
The autoselect command permits the router to start an ARA session automatically when it detects the start character for an Appletalk Remote Accesses Protocol (ARAP) packet. The Cisco IOS software detects either a Return character, which is the start character for an EXEC session, or the start character for the ARA protocol. By entering the autoselect command with the during-login keyword, you can display the username or password prompt without pressing the Return key. While the username or password prompts are displayed, you can choose to answer these prompts or to start sending packets from an autoselected protocol.
Normally a router avoids line and modem noise by clearing the initial data received within the first few seconds. However, when the autoselect PPP feature is configured, the router flushes characters initially received and then waits for more traffic. This flush causes timeout problems with applications that send only one carriage return. To ensure that the input data sent by a modem or other asynchronous device is not lost after line activation, enter the flush-at-activation line configuration command.
For information about using ARA with TACACS, Extended TACACS, and AAA/TACACS+, refer to Cisco IOS Security Configuration Guide.
Note When you use the autoselect function, the activation character should be set to the default, Return, and exec-character-bits to 7. If you change these defaults, the application cannot recognize the activation request.
To customize the AppleTalk configuration even further, you can perform the following additional tasks:
For more information about these and other tasks you can perform to customize your AppleTalk configuration, refer to Cisco IOS AppleTalk and Novell IPX Configuration Guide.
Configuring ARA Security
The following three types of security can be used with ARA:
- ARA Server Security, including required manual password entry, limited network visibility, and no guest access.
- Local or Remote Security Database, including username and password authentication and access lists.
- TACACS and TACACS+ Security for ARA, including TACACS, AAA/TACACS+, and Kerberos.
The following sections describe these tasks. Refer to Cisco IOS Security Command Reference for information about commands listed in these tasks.
ARA Server Security
Security features that are specific to the ARA protocol are described in the following sections:
Requiring Manual Password Entry
You can control access by requiring users to enter their password manually at the time they log in. To force manual password entry, use the following command in line configuration mode:
|
|
|
|---|---|
Limiting Network Visibility
You can control Macintosh access to zones and networks by using arap commands to reference access control lists configured using AppleTalk access-list commands.
To control which zones the Macintosh user can see, use the following command in line configuration mode:
|
|
|
|---|---|
To control traffic from the Macintosh to networks, use the following command in line configuration mode:
|
|
|
|---|---|
|
Disallowing Guests
A guest is a user that connects to the network without the need to give a name or a password. To prohibit Macintosh guests from logging in through the router, use the following command in line configuration mode. Use the optional if-needed argument to allow users to log in as guests if they are already authenticated with a username or password.
|
|
|
|---|---|
Note Do not use the arap noguest command if you are using modified CCL scripts and the login tacacs command.
Local or Remote Security Database
To prevent unauthenticated users from accessing your network resources, you configure a username and password database. This database can be local on the router or can be stored on a remote security server (a PC or UNIX computer set up with a security database). To configure the Cisco IOS software to support either local or remote authentication, perform the tasks described in the following sections:
- Configuring Local Username Authentication (As Required)
- Enabling Remote TACACS or TACACS+ Server Authentication (As Required)
Configuring Local Username Authentication
To configure internal username authentication, use the following command in global configuration mode. Enter this information for each supported user.
When users try to log in to the access server, username and password prompts require them to authenticate themselves before they can have access to the router or the network.
Enabling Remote TACACS or TACACS+ Server Authentication
To enable the Cisco IOS software to use a remote TACACS or TACACS+ authentication database, use the following commands in global configuration mode:
After you specify these commands in the Cisco IOS software, you must populate the remote username database to all users to whom you want to provide network access. When users try to log in to the router, username and password prompts require them to authenticate themselves before they can have access to the router or the network.
TACACS and TACACS+ Security for ARA
You can prevent unauthenticated users from accessing your network resources using the following security mechanisms:
- TACACS and AAA/TACACS+ user authentication, with username and password information stored on a TACACS or TACACS+ server
- Kerberos, which is configured through the AAA facility
For more information about each of these security mechanisms, refer to Cisco IOS Security Configuration Guide.
To configure TACACS and TACACS+ security to authenticate clients that are using ARA to dial in, perform the tasks described in the following sections:
- Enabling Standard and Extended TACACS for ARA Authentication (Required)
- Enabling AAA/TACACS+ for ARA Authentication (Required)
- Modifying Scripts to Support a Standard EXEC Security Dialog (Optional)—This modification is only necessary if you are running standard TACACS on both your router and your TACACS server.
Enabling Standard and Extended TACACS for ARA Authentication
To use extended TACACS, you must already have set up an extended TACACS server using the Cisco extended TACACS server software, available from the ftp.cisco.com directory. Refer to the README file in this directory for more information. The following two authentication methods are used with standard TACACS:
- You issue the arap use-tacacs command. The remote user logs in by entering the appropriate username at the ARA username prompt and password at the password prompt.
- You issue the arap use-tacacs command and the single-line keyword. The remote user logs in by entering username*password at the ARA username prompt, and arap at the password prompt.
Note The arap use-tacacs command provides TACACS security without the need to modify CCL scripts and respond to dialog boxes. The use of scripts is still a supported feature, and is described in the section “Modifying Scripts to Support a Standard EXEC Security Dialog” later in this chapter.
To configure the router to authenticate using TACACS, use the following commands in line configuration mode:
|
|
|
|
|---|---|---|
For an example of enabling TACACS for ARA authentication, refer to the section “ARA Configuration and Connection Examples” later in this chapter.
Enabling AAA/TACACS+ for ARA Authentication
To enable TACACS+ authentication for ARA sessions, use the following commands beginning in global configuration mode:
Modifying Scripts to Support a Standard EXEC Security Dialog
This section describes how to modify your CCL script to work with TACACS security and how to configure a line to use a TACACS server for user authentication.
Because of the underlying structure of the ARA protocol, modem-layer error control is disabled during the exchange of username and password. This condition makes the exchange highly susceptible to line noise, especially at higher baud rates enabled by V.34 modems. For this reason, we do not recommend the use of modified scripts and encourage users to either upgrade to later versions of TACACS or to use the
arap use-tacacs single-line command.
For information on how to use TACACS without modifying scripts, refer to the section “Enabling Standard and Extended TACACS for ARA Authentication” earlier in this chapter. For information about the arap commands, refer to Cisco IOS Terminal Services Command Reference.
If you are currently using modified CCL scripts and want to migrate to nonmodified scripts, refer to the section “Modified and Unmodified CCL Scripts Sample Commands” later in this chapter for information on how to use both in the same environment.
For several popular modems, Cisco provides CCL files that you can use as examples to modify your CCL scripts to support TACACS security. This section explains how to use the CCL files provided by Cisco with TACACS security.
For more information about creating modem initialization scripts, use the ARA Modem Toolkit provided through the AppleTalk Programmers and Developers Association (APDA); it provides both syntax checking and a script tester.
The Macintosh client uses ARA CCL scripts to establish point-to-point links with the modem to the AppleTalk network. When the connection has been established, the script ends and ARA is activated. TACACS authentication occurs after the connection is established and the ARA script ends, but before the ARAP protocol becomes active.
Insert TACACS logic just before the end of a script. The CCL TACACS logic performs the following user authentication tasks:
1. When the “Username:” prompt is received from the router, the TACACS server queries the user for a username, as shown in Figure 3.
Figure 3 TACACS Login Screen on the Macintosh Computer
2. When the “Password:” prompt is received from the router, the TACACS server queries the user for a password, as shown in Figure 4.
Figure 4 TACACS Password Screen on the Macintosh Computer
3. After a successful login, indicated by an EXEC prompt, the arap EXEC command is executed.
4. The script ends and ARA is activated on the client.
CCL scripts control logical flow by jumping to labels. The labels are the numbers 1 through 128 and are not necessarily in sequential order in script files. The TACACS logic in the Cisco IOS software CCL files has label numbers from 100 through 127. In most environments, you can copy the complete TACACS logic from a sample file.
To create a new TACACS CCL file, perform the following steps:
Step 1 Copy the TACACS logic from a sample CCL script into the new CCL script.
In most cases, you can insert the TACACS logic at the appropriate place in your CCL script. The one case that requires extra attention is when the original CCL script has labels that conflict with the logic in the new file. The labels must be resolved on a case-by-case basis, usually by changing the label numbers used in the original CCL script. Be sure to read the manual that comes with the ARA Modem Toolkit before beginning.
Step 2 Locate the logical end of the CCL script and insert the jump 100 command.
You can locate the logical end of the script by following its flow. Most scripts have the following basic structure:
The characteristic logical end of the script is as follows:
It is common in this case to replace “pause 30” with “jump 100.” In fact, this replacement is usually the only change made to the logic of the original CCL script.
Refer to Cisco IOS Dial Technologies Configuration Guide for information about configuring a line to support your modem.
Enabling Kerberos Security for ARA Authentication
You can use Kerberos as an authentication method within ARA sessions. To do so, you configure Kerberos using the AAA/TACACS+ facility in the Cisco IOS software.
To enable Kerberos security, use the following commands beginning in global configuration mode:
For more information about Kerberos authentication, refer to the Cisco IOS Security Configuration Guide.
Using Access Lists to Control Access to AppleTalk Networks
An access list is a list of AppleTalk network numbers or zones that is maintained by the Cisco IOS software and used to control access to or from specific zones or networks. For more information about AppleTalk access lists, refer to Cisco IOS AppleTalk and Novell IPX Configuration Guide.
Connecting to an AppleTalk Network from a Client Running a Different Virtual Terminal Protocol
ARA can run on any point-to-point link, such as a Public Switched Telephone Network (PSTN) or an X.25 WAN. This capability permits remote Macintosh users to dial in to a remote network and access AppleTalk services (such as file sharing and printing). For example, you can enable a Macintosh client on the remote side of an X.25 WAN to connect to an AppleTalk network through the router. To do so, you configure a vty on the router so that the client sees one of two scenarios:
- A client clicks Connect in an ARA application dialog box and connects to a vty on the router. ARA automatically starts up on the outgoing vty, and the client is connected to the AppleTalk network. This section describes how to configure the Cisco IOS software for this process.
- A client clicks Connect in an ARA application dialog box and connects directly through the router to the AppleTalk network. This process is described in the section “Configuring Tunneling of SLIP, PPP, or ARA” in the chapter “Configuring Protocol Translation and Virtual Asynchronous Devices” in this publication.
To enable ARA on virtual terminal lines and enable clients running different virtual terminal protocols to connect to an AppleTalk network through the router, use the following commands beginning in global configuration mode. The first four steps are required. The next eight steps are optional.
|
|
|
|
|---|---|---|
Router(config)# arap network [ network-number ] [ zone-name ] |
||
|
Making ARA Connections
If you are a Macintosh user, you can use ARA to connect to an AppleTalk network through a Cisco access server. The Cisco IOS Release 10.2 and later release software support ARA 2.0 and ARA 1.0 so that you can remotely dial in through asynchronous network devices using ARA to access AppleTalk services (such as file sharing and printing) elsewhere on the network. For example, you can dial in from an X.25 network and connect to an AppleTalk network through a router. To enable ARA and dial-in access, configure a vty on the router. You can also configure ARA on TTY lines.
Because there are no user commands for connecting to the network from your Macintosh client, the process is not described in this publication. To start a connection in most ARA client packages, you click the Connect button from within the client software.
Monitoring an ARA Server
To display information about a running ARA connection, use the following command in privileged EXEC mode (reached by entering the enable command and a password at the EXEC prompt):
|
|
|
|---|---|
The show arap command with no arguments displays a summary of ARA traffic since the router was last booted. The show arap command with a specified line number displays information about the connection on that line.
Monitoring the AppleTalk Network
The Cisco IOS software provides several commands that you can use to monitor an AppleTalk network. In addition, you can use Inter-Poll from Apple Computer, which is a tool to verify that a device is configured and operating properly. Use the commands described in this section to monitor an AppleTalk network using both Cisco IOS software commands and Inter-Poll.
To monitor the AppleTalk network, use any of the the following commands in EXEC mode:
|
|
|
|---|---|
Displays the statistics about AppleTalk protocol traffic, including MacIP traffic. |
|
Troubleshooting ARA Connections
Use ARA debugging enhancements to troubleshoot one or more asynchronous lines on an access server. These enhancements are supported on all Macintosh terminals and all Cisco routers and access servers that support the AppleTalk software feature set.
Allowing users to specify a single line via an additional parameter for troubleshooting produces the following benefits:
- Focused results—Users get only the information they need.
- Reduced server load—Heavily loaded servers are subject to developing ARAP problems which need to be fixed by debugging. However, debugging itself increases the server work load. By focusing on specific lines, the impact of debugging activity on the server is minimized.
- Targeting flexibility—By being able to debug on just the lines in a group of lines, users can solve problems in rotary groups in which there is no way to specify which line or group of lines a remote user will be assigned.
To enable ARAP debugging, use the following commands beginning in EXEC mode:
To verify if the debug level and target are set correctly, enter the show debug command:
Router# show debugARAP Debugging Examples
The following example sets ARAP debugging in memory mode on line 7. The show debug command confirms the configuration.
Note You can debug several lines (for example, lines in a rotary), but you must turn on debugging one line at a time.
The following example sets ARAP debugging in internal mode on line 6, memory mode on line 10, and V.42 bis compression mode on line 6. The show debug command confirms the configuration.
The following example sets ARAP debugging for each mode in succession and for all lines. The show debug command confirms the configuration.
The following example sets all debugging (including ARAP debugging) for all modes and for all lines. The show debug command confirms the configuration. Note that turning on all debugging utilities can slow down performance.
The following example turns off ARAP debugging. The show debug command confirms the configuration.
The following example shows debug output for two lines, 2 and 4. The boldfaced portion of this example shows that for line 2, LA is the MNP4 acknowledge frame, 31 is the sequence number of the last frame, and 08 is the window size.
ARA Configuration and Connection Examples
This section contains the following examples of and procedures for ARA configuration:
- ARA Server Configuration Procedure
- Dedicated ARA Line with User Authentication Example
- Autostart Multiple ARA Lines with User Authentication Example
- Telebit T-3000 Modem Setup Procedure
- Modified and Unmodified CCL Scripts Sample Commands
- ARA Router Support Example
- Extended AppleTalk Network Example
- Cable Range Expansion Example
- Extended Network in Discovery Mode Example
- TACACS Username Authentication Example
- TACACS Enabled for ARA Authentication Example
- AppleTalk Network Connection over a Foreign Protocol Example
ARA Server Configuration Procedure
The following sample procedure shows how to set up ARA functionality.
Log in to the router, use the enable command to enter your password if one is set, use the configure command to enter configuration mode, and add the following commands to your configuration:
If you already know the cable range and the zone names you need, include the information in the configuration file. If you do not know this information, perform the following steps to use the discovery mode to allow the Cisco IOS software to learn about the AppleTalk network:
Step 1 Permit the Cisco IOS software to monitor the line for a few minutes.
Step 2 Log in and enter configuration mode.
Step 3 Display the configuration again (using the more nvram:startup-config command).
Step 4 Note the appletalk cable-range and appletalk zone variables.
Step 5 Manually add the information in those two entries and add any user accounts:
Step 6 Save the configuration.
Step 7 Display the configuration again (using the more nvram:startup-config command) to make sure the configuration is correct.
Dedicated ARA Line with User Authentication Example
The following example configures line 2 as a dedicated ARA line with user authentication information on the ARA server; guests are not allowed to make ARA sessions:
Autostart Multiple ARA Lines with User Authentication Example
The following example enables ARA on lines 2 through 16. Username authentication is configured on the ARA server, and the lines are configured to automatically start an ARA session when an ARA user on a Macintosh attempts a connection.
Telebit T-3000 Modem Setup Procedure
To set up a Telebit T-3000 modem that attaches to a router, which supports hardware flow control, perform the following steps. The Macintosh will use a CCL script to configure the attached modem.
When you configure modems for ARA, turn off MNP4 error correction because it can cause connection failures for ARA 1.0 clients. For dedicated ARA lines, it is sufficient to turn off error correction completely in the modem; for multiuse lines it is preferable to leave all forms of non-MNP4 error correction enabled so that users of other protocols can achieve error-corrected connections. This restriction does not apply to installations that only receive calls from ARAP 2.0 clients.
Step 1 Start with the modem at factory defaults. (The preferred configuration for hardware flow control is AT&F9.) Use the direct command if you have a terminal attached to the modem, or use the T/D Reset sequence described in the Telebit T-3000 manual to reset the modem to the &F9 defaults.
Step 2 Attach a hardware flow control-capable cable between the modem and the device with which you are configuring the modem. (At this point, the modem is in hardware flow control mode, with autobaud-rate-recognition, and can detect your speed from 300 to 38,400 bps at 8-N-1. However, the modem must receive the flow control signals from the device to which you have the modem attached.)
Step 3 Send the modem the following AT commands:
ATS51=6 E0 Q1 S0=2 &D3 &R3 S58=2 &W
This sequence directs the modem to perform the following tasks:
- Lock your DTE interface speed to 38,400 bps.
- Turn “command echo” off.
- Do not send any result codes.
- Auto-answer on the second ring (Germany requires this setting, but elsewhere you can set it to answer on the first ring with “s0=1”).
- When data terminal ready (DTR) is toggled, reset to the settings in NVRAM.
- Clear To Send (CTS) is always enabled if hardware flow control is disabled.
- Use full-duplex request to send/clear to send (RTS/CTS) flow control.
- Write these settings to NVRAM.
Step 4 At this point, if you press the Return key or enter characters, no characters appear on your screen because the result codes are turned off. You can determine whether the modem is working by getting a list of its configuration registers using the AT command AT&V.
Step 5 After the modem is configured, connect it to the router with a modem-to-RJ-45 adapter and an RJ-45 cable to the lines that you plan to use.
The following Cisco IOS commands are compatible with the Telebit 3000 settings described in this section:
Modified and Unmodified CCL Scripts Sample Commands
If you are using modified CCL scripts and want to migrate to nonmodified scripts, you can set your system to accept logins using both modified CCL and unmodified scripts. Use the following commands in line configuration mode:
ARA Router Support Example
The following example configures the router for ARA support, as described in the comments (lines beginning with an exclamation point [!]):
! assign zone name “Marketing Lab” to the interface. Assign a zone name if
! this example is 103.1.
username jake password sesame
! to automatically start an EXEC session or enable AppleTalk, AppleTalk Remote
! Access Protocol is enabled, the modem speed is specified as 38400 bps, and
! hardware flow control is enabled.
Note You must set your terminal emulator to match the speed that you set for the line.
Extended AppleTalk Network Example
The following example configures the interface for an extended AppleTalk network. It defines the zones named Orange and Brown. The cable range of 1 allows compatibility with nonextended AppleTalk networks.
Cable Range Expansion Example
The following example changes the cable range and reenters the zone name. The initial configuration is as follows:
The cable range is expanded as follows:
At this point, you must reenter the zone name as follows:
Extended Network in Discovery Mode Example
The following example configures an extended network in discovery mode. In Figure 5, the access server named Server A provides the zone and network number information to the interface when it starts.
The following example configures an extended network in discovery mode:
TACACS Username Authentication Example
The following example for TACACS and Extended TACACS configures line 1 for ARA and username authentication on a TACACS server:
The following example configures AAA/TACACS+ on line 1 for ARA and username authentication on a TACACS server:
TACACS Enabled for ARA Authentication Example
The following example shows regular TACACS enabled for ARA authentication:
The following example shows AAA/TACACS+ enabled for ARA authentication:
AppleTalk Network Connection over a Foreign Protocol Example
The following example enables a Macintosh client running ARA on a remote network to connect across an X.25 network, through the router, to an AppleTalk network. In this example, virtual terminal lines 0 through 19 are configured for ARA:
The Macintosh client connects to any vty from 0 through 19. When the EXEC prompt appears, ARA begins automatically on the line (because of the autocommand arap command). The virtual terminal lines 0 through 19 are dedicated to ARA dial-in clients, and those clients have a 45-minute time limit. Five minutes before the line is disconnected, a warning message appears indicating that the session will be disconnected. Guest access is denied, and manual password entry is required. The AppleTalk access list 611 has been applied to the virtual terminal lines, meaning that access to other networks through these virtual terminal lines has been limited.
Feedback