Cisco IOS Dial Technologies Configuration Guide Release 12.2 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S About Cisco IOS Software Documentation Documentation Objectives Audience xxxvii xxxvii xxxvii Documentation Organization xxxvii Documentation Modules xxxvii Master Indexes xl Supporting Documents and Resources New and Changed Information Document Conventions xl xli xli Obtaining Documentation xlii World Wide Web xlii Documentation CD-ROM xliii Ordering Documentation xliii Documentation Feedback xliii Obtaining Technical Assistance xliii Cisco.
Contents DIAL INTERFACES, CONTROLLERS, AND LINES Overview of Dial Interfaces, Controllers, and Lines Cisco IOS Dial Components DC-2 DC-2 Logical Constructs DC-4 Asynchronous Interfaces DC-4 Group Asynchronous Interfaces DC-5 Virtual Template Interfaces DC-5 Templates for Virtual Access Interfaces DC-6 Templates for Protocol Translation DC-6 Logical Interfaces DC-6 Dialer Interfaces DC-7 Virtual Access Interfaces DC-8 Virtual Asynchronous Interfaces DC-9 Circuit-Switched Digital Calls T1 and E1 Controlle
Contents How to Configure Other Asynchronous Line and Interface Features DC-28 Configuring the Auxiliary (AUX) Port DC-28 Establishing and Controlling the EXEC Process DC-29 Enabling Routing on Asynchronous Interfaces DC-30 Configuring Dedicated or Interactive PPP and SLIP Sessions DC-30 Conserving Network Addresses DC-31 Using Advanced Addressing Methods for Remote Devices DC-32 Assigning a Default Asynchronous Address DC-32 Allowing an Asynchronous Address to Be Assigned Dynamically DC-32 Optimizing Avai
Contents Configuring Asynchronous Serial Traffic over UDP DC-44 UDPTN Overview DC-44 How to Configure Asynchronous Serial Traffic over UDP DC-45 Preparing to Configure Asynchronous Serial Traffic over UDP Configuring a Line for UDPTN DC-45 Enabling UDPTN DC-46 Verifying UDPTN Traffic DC-46 Configuration Examples for UDPTN DC-47 Multicast UDPTN Example DC-47 Broadcast UDPTN Example DC-48 Point-to-Point UDPTN Example DC-48 MODEM CONFIGURATION AND MANAGEMENT Overview of Modem Interfaces DC-52 Cisco Modems
Contents Configuring the Modem Using a Modemcap DC-70 Configuring the Modem Circuit Interface DC-72 Comparison of NextPort SPE and MICA Modem Commands DC-72 Configuring Cisco Integrated Modems Using Modem Attention Commands DC-75 Using Modem Dial Modifiers on Cisco MICA Modems DC-75 Changing Configurations Manually in Integrated Microcom Modems DC-76 Configuring Leased-Line Support for Analog Modems DC-77 Configuring Modem Pooling DC-81 Creating a Modem Pool DC-82 Verifying Modem Pool Configuration DC-83 C
Contents Modem Performance Summary Example DC-110 Modem AT-Mode Example DC-110 Connection Speed Performance Verification Example DC-110 Configuring and Managing Cisco Access Servers and Dial Shelves Cisco AS5800 Dial Shelf Architecture and DSIP Overview Split Dial Shelves Feature DC-114 DC-113 DC-113 How to Configure Dial Shelves DC-114 Configuring the Shelf ID DC-115 Configuring Redundant DSC Cards DC-116 Synchronizing to the System Clocks DC-117 Verifying External Clock Configuration DC-118 Configur
Contents SPE Modem Statistics DC-141 Configuring and Managing External Modems DC-143 External Modems on Low-End Access Servers DC-143 Automatically Configuring an External Modem DC-144 Manually Configuring an External Modem Supporting Dial-In Modems DC-147 Testing the Modem Connection Managing Telnet Sessions DC-146 DC-149 DC-150 Modem Troubleshooting Tips DC-152 Checking Other Modem Settings Modem Signal and Line States DC-153 DC-154 Signal and Line State Diagrams DC-154 Configuring Auto
Contents ISDN CONFIGURATION Configuring ISDN BRI DC-172 ISDN Overview DC-172 Requesting BRI Line and Switch Configuration from a Telco Service Provider Interface Configuration DC-175 Dynamic Multiple Encapsulations DC-175 Interface Configuration Options DC-175 ISDN Cause Codes DC-176 How to Configure ISDN BRI DC-177 Configuring the ISDN BRI Switch DC-177 Configuring the Switch Type DC-177 Checking and Setting the Buffers DC-178 Multiple ISDN Switch Types Feature DC-179 Specifying Interface Characteristic
Contents Multilink PPP on a BRI Interface Example DC-190 Dialer Rotary Groups Example DC-191 Compression Examples DC-191 Multilink PPP and Compression Example DC-192 Voice over ISDN Examples DC-192 DNIS-plus-ISDN-Subaddress Binding Example DC-193 Screening Incoming V.110 Modem Calls Example DC-193 ISDN BRI Leased-Line Configuration Example DC-193 Configuring Virtual Asynchronous Traffic over ISDN DC-194 Recommendation V.120 Overview DC-195 How to Configure V.
Contents Configuring X.25 on ISDN Using AO/DI DC-230 AO/DI Overview DC-230 PPP over X.25 Encapsulation DC-232 Multilink PPP Bundle DC-233 MLP Encapsulation Enhancements DC-233 BACP/BAP DC-234 How to Configure an AO/DI Interface DC-234 Configuring PPP and BAP on the Client DC-234 Configuring X.25 Parameters on the Client DC-235 Configuring PPP and BAP on the Server DC-235 Configuring X.
Contents Configuration Examples for RCAPI DC-247 SIGNALING CONFIGURATION Configuring ISDN PRI DC-252 Signaling Overview DC-253 In-Band and Out-of-Band Signaling DC-253 Channelized E1 and T1 on Cisco Devices DC-253 How to Configure ISDN PRI DC-254 Requesting PRI Line and Switch Configuration from a Telco Service Provider DC-254 Configuring Channelized E1 ISDN PRI DC-255 Configuring Channelized T1 ISDN PRI DC-256 Configuring the Serial Interface DC-257 Specifying an IP Address for the Interface DC-258 Co
Contents Basic Call Processing Components DC-275 ISDN BRI Calls into T1 CAS DC-276 How to Configure Switched 56K Services DC-276 How to Configure E1 R2 Signaling DC-277 E1 R2 Signaling Overview DC-277 Configuring E1 R2 Signaling DC-280 Configuring E1 R2 Signaling for Voice DC-280 Monitoring E1 R2 Signaling DC-281 Verifying E1 R2 Signaling DC-282 Troubleshooting E1 R2 Signaling DC-283 Enabling R1 Modified Signaling in Taiwan DC-284 R1 Modified Signaling Topology DC-284 R1 Modified Signaling Configuration
Contents ISDN CAS Examples DC-302 Allocating All Channels for CAS Example DC-302 Mixing and Matching Channels—CAS and Channel Grouping Example E1 R2 Signaling Procedure DC-303 R1 Modified Signaling Using an E1 Interface Example DC-306 R1 Modified Signaling for Taiwan Configuration Example DC-307 Configuring ISDN Special Signaling DC-303 DC-308 How to Configure ISDN Special Signaling DC-308 Configuring ISDN AOC DC-309 Configuring Short-Hold Mode DC-309 Monitoring ISDN AOC Call Information DC-310 Configur
Contents ISDN Disconnect Timers DC-324 How to Configure Network Side ISDN PRI DC-324 Configuring ISDN Network Side DC-325 Configuring ISDN Network Side for the National ISDN Switch Type DC-326 Configuring ISDN Network Side for ETSI Net5 PRI DC-326 Configuring Global or Interface Trunk Groups DC-327 Configuring Classes of Restrictions DC-328 Configuring ISDN T306 and T310 Timers DC-329 Verifying Network Side ISDN PRI Signaling, Trunking, and Switching DC-329 Monitoring Network Side ISDN PRI DC-332 Monitor
Contents Associating the Protocol Access List with a Dialer Group DC-351 Configuration Examples for Legacy DDR DC-351 Point-to-Point DDR Without Authentication Examples DC-351 Point-to-Point DDR with Authentication Examples DC-353 Configuring Legacy DDR Spokes DC-355 DDR Spokes Configuration Task Flow DC-355 How to Configure DDR DC-356 Specifying the Interface DC-357 Enabling DDR on the Interface DC-358 Configuring the Interface to Place Calls DC-359 Specifying the Dial String for Synchronous Serial
Contents Local Configuration Example DC-373 AppleTalk Configuration Example DC-374 DECnet Configuration Example DC-374 ISO CLNS Configuration Example DC-375 XNS Configuration Example DC-375 Single Site Dialing Example DC-375 DTR Dialing Example DC-376 Hub-and-Spoke DDR for Asynchronous Interfaces and Authentication Example DC-377 Spoke Topology Configuration DC-377 Hub Router Configuration DC-378 Two-Way Reciprocal Client/Server DDR Without Authentication Example DC-379 Remote Configuration DC-379 Local Co
Contents Setting Dialer Interface Priority DC-395 Configuring a Dialer Hold Queue DC-395 Configuring Bandwidth on Demand DC-395 Disabling and Reenabling DDR Fast Switching DC-396 Configuring Dialer Redial Options DC-396 Sending Traffic over Frame Relay, X.25, or LAPB Networks DC-397 Configuring the Interface for Sending Traffic over a Frame Relay Network DC-397 Configuring the Interface for Sending Traffic over an X.
Contents Dialer Pool DC-416 How to Configure Dialer Profiles DC-418 Configuring a Dialer Profile DC-418 Configuring a Dialer Interface DC-418 Fancy Queueing and Traffic Shaping on Dialer Profile Interfaces Configuring a Map Class DC-419 Configuring the Physical Interfaces DC-420 Configuring Dialer Profiles for Routed Protocols DC-420 Configuring Dialer Profiles for AppleTalk DC-421 Configuring Dialer Profiles for Banyan VINES DC-421 Configuring Dialer Profiles for DECnet DC-421 Configuring Dialer Profile
Contents How to Configure Dial Backup DC-441 Specifying the Backup Interface DC-442 Defining the Traffic Load Threshold DC-442 Defining Backup Line Delays DC-443 Configuration Examples for Dial Backup for Serial Interfaces DC-443 Dial Backup Using an Asynchronous Interface Example DC-443 Dial Backup Using DDR and ISDN Example DC-444 Dial Backup Service When the Primary Line Reaches Threshold Example DC-444 Dial Backup Service When the Primary Line Exceeds Threshold Example DC-444 Dial Backup Service When t
Contents Enabling PPP/IPCP Negotiation DC-467 Defining NAT for the Dialer Interface DC-467 Configuring the Dialer Interface DC-467 Timeout Considerations DC-468 Configuration Examples for Cisco Easy IP DC-468 VIRTUAL TEMPLATES, PROFILES, AND NETWORKS Configuring Virtual Template Interfaces DC-472 Virtual Template Interface Service Overview DC-473 Features that Apply Virtual Template Interfaces DC-474 Selective Virtual Access Interface Creation DC-474 How to Configure a Virtual Template Interface DC-47
Contents Troubleshooting Virtual Profile Configurations DC-488 Configuration Examples for Virtual Profiles DC-488 Virtual Profiles Configured by Virtual Templates DC-488 Virtual Profiles Configured by AAA Configuration DC-490 Virtual Profiles Configured by Virtual Templates and AAA Configuration DC-491 Virtual Profiles Configured by AAA Plus a VPDN Virtual Template on a VPDN Home Gateway Configuring Virtual Private Networks DC-493 DC-495 VPN Technology Overview DC-495 VPDN MIB DC-496 VPN Hardware Term
Contents Configuring the Dialer on a Tunnel Server DC-517 How to Configure a VPN DC-518 Enabling a VPN DC-518 Configuring VPN Tunnel Authentication Configuration DC-518 Disabling VPN Tunnel Authentication for L2TP Tunnels DC-519 Configuring VPN Tunnel Authentication Using the Host Name or Local Name DC-520 Configuring VPN Tunnel Authentication Using the L2TP Tunnel Password DC-520 Configuring Client-Initiated Dial-In VPN DC-521 Configuring a Tunnel Server to Accept PPTP Tunnels DC-521 Configuring MPPE on
Contents Troubleshooting VPN Negotiation DC-543 Troubleshooting PPP Negotiation DC-547 Troubleshooting AAA Negotiation DC-548 Configuration Examples for VPN DC-551 Client-Initiated Dial-In Configuration Example DC-551 VPN Tunnel Authentication Examples DC-553 Tunnel Secret Configured Using the Local Name Command DC-553 Tunnel Secret Configured Using the L2TP Tunnel Password Command DC-553 Tunnel Secret Configuration Using Different Tunnel Authentication Methods DC-554 NAS Comprehensive Dial-In Configuratio
Contents Compressing TCP Packet Headers DC-571 Setting the TCP Connection Attempt Time DC-572 Compressing IPX Packet Headers over PPP DC-572 Enabling Fast Switching DC-573 Controlling Route Cache Invalidation DC-574 Customizing SLIP and PPP Banner Messages DC-574 Configuration Examples for Asynchronous SLIP and PPP DC-575 Basic PPP Configurations Examples DC-575 Remote Node NetBEUI Examples DC-576 Remote Network Access Using PPP Basic Configuration Example DC-577 Remote Network Access Using PPP and Routing
Contents Configuring MLP on Asynchronous Interfaces DC-597 Configuring MLP on a Single ISDN BRI Interface DC-597 Configuring MLP on Multiple ISDN BRI Interfaces DC-598 Configuring MLP Using Multilink Group Interfaces DC-600 Changing the Default Endpoint Discriminator DC-601 Configuring MLP Interleaving and Queueing Configuring MLP Interleaving DC-602 DC-601 Configuring MLP Inverse Multiplexer and Distributed MLP DC-603 Enabling Distributed CEF Switching DC-605 Creating a Multilink Bundle DC-605 Assigning
Contents Configuration Examples for MMP DC-624 MMP Using PRI But No Dialers DC-624 MMP with Dialers DC-625 MMP with Explicitly Defined Dialer DC-625 MMP with ISDN PRI but No Explicitly Defined Dialer MMP with Offload Server DC-626 DC-626 CALLBACK AND BANDWIDTH ALLOCATION CONFIGURATION Configuring Asynchronous Callback Asynchronous Callback Overview DC-628 DC-628 How to Configure Asynchronous Callback DC-629 Configuring Callback PPP Clients DC-629 Accepting Callback Requests from RFC-Compliant PPP Clien
Contents Configuring ISDN Caller ID Callback for Legacy DDR DC-642 Configuring ISDN Caller ID Callback for Dialer Profiles DC-643 Monitoring and Troubleshooting ISDN Caller ID Callback DC-644 Configuration Examples for ISDN Caller ID Callback DC-644 Best Match System Examples DC-644 Best Match Based on the Number of “Don’t Care” Characters Example Best Match with No Callback Configured Example DC-645 No Match Configured Example DC-645 Simple Callback Configuration Examples DC-645 ISDN Caller ID Callback
Contents Establishing the Route to the Remote Network DC-664 Enabling AAA and Static Route Download DC-664 Enabling Access to the AAA Server DC-665 Enabling Reverse DNS DC-665 Enabling SGBP Dial-Out Connection Bidding DC-665 Defining a User Profile DC-666 Monitoring and Maintaining the Large-Scale Dial-Out Network DC-671 Configuration Examples for Large-Scale Dial-Out DC-671 Stack Group and Static Route Download Configuration Example DC-671 User Profile on an Ascend RADIUS Server for NAS1 Example DC-676
Contents Resource Groups DC-706 Resource Services DC-706 VPDN Groups DC-707 VPDN Profiles DC-707 Call Treatments DC-707 Details on RPM Call Processes DC-708 Accounting Data DC-710 Data over Voice Bearer Services DC-710 Call Discriminator Profiles DC-711 Incoming Call Preauthentication DC-712 RPM Standalone Network Access Server DC-713 Call Processing DC-714 Base Session and Overflow Session Limits DC-714 VPDN Session and Overflow Session Limits DC-715 VPDN MLP Bundle and Links-per-Bundle Limits DC-716 VPDN
Contents Limiting the Number of MLP Bundles in VPDN Groups Configuring Switched 56 over CT1 and RBS DC-736 DC-735 Verifying RPM Components DC-737 Verifying Current Calls DC-737 Verifying Call Counters for a Customer Profile DC-737 Clearing Call Counters DC-738 Verifying Call Counters for a Discriminator Profile DC-738 Verifying Call Counters for a Resource Group DC-738 Verifying Call Counters for a DNIS Group DC-739 Verifying Call Counters for a VPDN Profile DC-739 Verifying Load Sharing and Backup DC-73
Contents Configuring Wholesale Dial Performance Optimization DC-758 Wholesale Dial Performance Optimization Feature Overview How to Configure Automatic Command Execution DC-758 DC-759 How to Configure TCP Clear Performance Optimization DC-759 Verifying Configuration of TCP Clear Performance Optimization DC-760 DIAL ACCESS SCENARIOS Dial Networking Business Applications DC-762 Dial Networking for Service Providers and Enterprises Common Dial Applications DC-762 DC-765 IP Address Strategies DC-
Contents Telecommuters Dialing In to a Mixed Protocol Environment Description DC-804 Enterprise Network Topology DC-806 Mixed Protocol Dial-In Scenarios DC-807 Cisco 7200 #1 Backbone Router DC-808 Cisco 7200 #2 Backbone Router DC-809 Cisco AS5300 Universal Access Server DC-810 Telco and ISP Dial Scenarios and Configurations DC-803 DC-813 Small- to Medium-Scale POPs DC-813 Individual Remote PCs Using Analog Modems DC-814 Network Topology DC-814 Running Configuration for ISDN PRI DC-814 Running Configurat
Contents PPP Calls over X.
Contents xxxvi
About Cisco IOS Software Documentation This chapter discusses the objectives, audience, organization, and conventions of Cisco IOS software documentation. It also provides sources for obtaining documentation from Cisco Systems. Documentation Objectives Cisco IOS software documentation describes the tasks and commands necessary to configure and maintain Cisco networking devices.
About Cisco IOS Software Documentation Documentation Organization Figure 1 shows the Cisco IOS software documentation modules. Note Figure 1 The abbreviations (for example, FC and FR) next to the book icons are page designators, which are defined in a key in the index of each document to help you with navigation. The bullets under each module list the major technology areas discussed in the corresponding books.
About Cisco IOS Software Documentation Documentation Organization Cisco IOS Dial Technologies Configuration Guide TC BC Cisco IOS Terminal Services Configuration Guide Cisco IOS Bridging and IBM Networking Configuration Guide B2R B1R DR Cisco IOS Dial Technologies Command Reference TR Module DC/DR: • Preparing for Dial Access • Modem and Dial Shelf Configuration and Management • ISDN Configuration • Signalling Configuration • Dial-on-Demand Routing Configuration • Dial-Backup Configuration • Dial
About Cisco IOS Software Documentation Documentation Organization Master Indexes Two master indexes provide indexing information for the Cisco IOS software documentation set: an index for the configuration guides and an index for the command references. Individual books also contain a book-specific index. The master indexes provide a quick way for you to find a command when you know the command name but not which module contains the command.
About Cisco IOS Software Documentation New and Changed Information New and Changed Information For Cisco IOS Release 12.2, two previous Release 12.1 guides, Cisco IOS Dial Services Configuration Guide: Terminal Services and Cisco IOS Dial Services Configuration Guide: Network Services, have been renamed and reorganized into a single book: Cisco IOS Dial Technologies Configuration Guide. See Figure 1 for a list of the contents. For Cisco IOS Release 12.2, the Release 12.
About Cisco IOS Software Documentation Obtaining Documentation Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example: Convention Description [x {y | z}] Braces and a vertical line within square brackets indicate a required choice within an optional element. Examples use the following conventions: Convention Description screen Examples of information displayed on the screen are set in Courier font.
About Cisco IOS Software Documentation Documentation Feedback Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
About Cisco IOS Software Documentation Obtaining Technical Assistance Cisco.com Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco. Cisco.
About Cisco IOS Software Documentation Obtaining Technical Assistance P1 and P2 level problems are defined as follows: • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available. • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
About Cisco IOS Software Documentation Obtaining Technical Assistance Cisco IOS Dial Technologies Configuration Guide xlvi
Using Cisco IOS Software This chapter provides helpful tips for understanding and configuring Cisco IOS software using the command-line interface (CLI).
Using Cisco IOS Software Getting Help Table 1 describes how to access and exit various common command modes of the Cisco IOS software. It also shows examples of the prompts displayed for each mode. Table 1 Accessing and Exiting Command Modes Command Mode Access Method Prompt Exit Method User EXEC Log in. Router> Use the logout command. Privileged EXEC From user EXEC mode, use the enable EXEC command. Router# To return to user EXEC mode, use the disable command.
Using Cisco IOS Software Getting Help Example: How to Find Command Options This section provides an example of how to display syntax for a command. The syntax can consist of optional or required keywords and arguments. To display keywords and arguments for a command, enter a question mark (?) at the configuration prompt or after entering part of a command followed by a space. The Cisco IOS software displays a list and brief description of available keywords and arguments.
Using Cisco IOS Software Getting Help Table 2 How to Find Command Options (continued) Command Comment Router(config-if)# ? Interface configuration commands: . . .
Using Cisco IOS Software Using the no and default Forms of Commands Table 2 How to Find Command Options (continued) Command Comment Router(config-if)# ip address ? A.B.C.D IP address negotiated IP Address negotiated over PPP Router(config-if)# ip address Enter the command that you want to configure for the interface. This example uses the ip address command. Enter ? to display what you must enter next on the command line. In this example, you must enter an IP address or the negotiated keyword.
Using Cisco IOS Software Saving Configuration Changes have variables set to certain default values. In these cases, the default form of the command enables the command and sets the variables to their default values. The Cisco IOS software command reference publications describe the effect of the default form of a command if the command functions differently than the no form.
Using Cisco IOS Software Identifying Supported Platforms Identifying Supported Platforms Cisco IOS software is packaged in feature sets consisting of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release.
Using Cisco IOS Software Identifying Supported Platforms Cisco IOS Dial Technologies Configuration Guide liv
Dial Interfaces, Controllers, and Lines
Overview of Dial Interfaces, Controllers, and Lines This chapter describes the different types of software constructs, interfaces, controllers, channels, and lines that are used for dial-up remote access.
Overview of Dial Interfaces, Controllers, and Lines Cisco IOS Dial Components Figure 2 Cisco IOS Dial Universe Headquarters intranet/Internet Interface virtual template Interface group-async Cloning Fast Ethernet interface Virtual access interface Interface dialer controlling the D channels Loopback interface Routing and switching engine Cloning Cloning Asynchronous interfaces Lines Interface serial channels S0:0, S0:1… (B channels) Modems AAA TDM bus Controllers Cisco IOS software inside
Overview of Dial Interfaces, Controllers, and Lines Logical Constructs Logical Constructs A logical construct stores core protocol characteristics to assign to physical interfaces. No data packets are forwarded to a logical construct. Cisco uses three types of logical constructs in its access servers and routers.
Overview of Dial Interfaces, Controllers, and Lines Logical Constructs Specifically, you configure asynchronous interfaces to support PPP connections.
Overview of Dial Interfaces, Controllers, and Lines Logical Interfaces Templates for Virtual Access Interfaces Virtual templates project configuration information to temporary virtual access interfaces triggered by multilink or virtual private dial-up network (VPDN) session events. When a virtual access interface is triggered, the configuration attributes in the virtual template are cloned and the negotiated parameters are applied to the connection.
Overview of Dial Interfaces, Controllers, and Lines Logical Interfaces Dialer Interfaces A dialer interface is a parent interface that stores and projects protocol configuration information that is common to all data (D) channels that are members of a dialer rotary group. Data packets pass through dialer interfaces, which in turn initiate dialing for inbound calls. In most cases, D channels get their core protocol intelligence from dialer interfaces.
Overview of Dial Interfaces, Controllers, and Lines Logical Interfaces Virtual Access Interfaces A virtual access interface is a temporary interface that is spawned to terminate incoming PPP streams that have no physical connections. PPP streams, Layer 2 Forwarding Protocol (L2F), and Layer 2 Tunnel Protocol (L2TP) frames that come in on multiple B channels are reassembled on virtual access interfaces. These access interfaces are constructs used to terminate packets.
Overview of Dial Interfaces, Controllers, and Lines Circuit-Switched Digital Calls Virtual Asynchronous Interfaces A virtual asynchronous interface is created on demand to support calls that enter the router through a nonphysical interface. For example, asynchronous character stream calls terminate or land on nonphysical interfaces. These types of calls include inbound Telnet, LAT, PPP over character-oriented protocols (such as V.120 or X.25), and LAPB-TA and PAD calls.
Overview of Dial Interfaces, Controllers, and Lines T1 and E1 Controllers Figure 8 Remote Office LAN Dialing In to Headquarters PC sending e-mail to headquarters PPP Hub BRI PRI Fast Ethernet PSTN/ISDN NT server Cisco 3640 headquarters gateway router 14053 Cisco 1600 remote office router PC T1 and E1 Controllers Cisco controllers negotiate the following parameters between an access server and a central office: line coding, framing, clocking, DS0/time-slot provisioning, and signaling.
Overview of Dial Interfaces, Controllers, and Lines ISDN Service The difference between traditional channelized lines (analog) and nonchannelized lines (ISDN) is that channelized lines have no built-in D channel. That is, all 24 channels on a T1 line carry only data. The signaling is in-band or associated to the data channels. Traditional channelized lines do not support digitized data calls (for example, BRI with 2B + D).
Overview of Dial Interfaces, Controllers, and Lines ISDN Service ISDN BRI ISDN BRI operates over most of the copper twisted-pair telephone wiring in place. ISDN BRI delivers a total bandwidth of a 144 kbps via three separate channels. Two of the B channels operate at 64 kbps and are used to carry voice, video, or data traffic. The third channel, the D channel, is a 16-kbps signaling channel used to tell the Public Switched Telephone Network (PSTN) how to handle each of the B channels.
Overview of Dial Interfaces, Controllers, and Lines ISDN Service Logical Relationship of ISDN PRI Components for T1 Channel Type Time Slot Number Virtual Serial Interface Number B B B B • • • • • B B B D 1 2 3 4 • • • • • 21 22 23 24 S0:0 S0:1 S0:2 S0:3 • • • • • S0:20 S0:21 S0:22 S0:23 (data channel) (data channel) (data channel) (data channel) (data channel) (data channel) (data channel) (signaling channel) Logical contents of a PRI interface S6487 Figure 10 The following example is for a Cis
Overview of Dial Interfaces, Controllers, and Lines Line Types Line Types This section describes the different line types used for dial access. It also describes the relationship between lines and interfaces. Note Cisco devices have four types of lines: console, auxiliary, asynchronous, and virtual terminal. Different routers have different numbers of these line types. Refer to the hardware and software configuration guides that shipped with your device for exact configurations.
Overview of Dial Interfaces, Controllers, and Lines Line Types Figure 11 Sample Show Line Output Showing CTY, tty, AUX, and vty Line Statistics Rotary group # Access class in/out Autoselect state Line speed This is VTY2 (3rd VTY) line 20 show line Tx/Rx 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 115200/115200 9600/9600 9600/9600 9600/9
Overview of Dial Interfaces, Controllers, and Lines Line Types For example, to enable IP resources to dial in to a network through a Cisco 2500 series access server, configure the lines and asynchronous interfaces as follows. • Configure the physical aspect of a line that leads to a port.
Overview of Dial Interfaces, Controllers, and Lines Encapsulation Types Encapsulation Types Synchronous serial interfaces default to High-Level Data Link Control (HDLC) encapsulation, and asynchronous serial interfaces default to SLIP encapsulation. Cisco IOS software provides a long list of encapsulation methods that can be set on the interface to change the default encapsulation method. See the Cisco IOS Interface Command Reference for a complete list and description of these encapsulation methods.
Configuring Asynchronous Lines and Interfaces This chapter describes how to configure asynchronous line features in the following main sections: • How to Configure Asynchronous Interfaces and Lines • How to Configure Other Asynchronous Line and Interface Features • Configuration Examples for Asynchronous Interfaces and Lines Perform these tasks, as required, for your particular network.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Configuring a Typical Asynchronous Interface To configure an asynchronous interface, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface async number Brings up a single asynchronous interface and enters interface configuration mode. Step 2 Router(config-if)# description description Provides a description for the interface.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines To monitor and maintain asynchronous activity, use the following commands in privileged EXEC mode as needed: Command Purpose Router# clear line line-number Returns a line to its idle state. Router# show async bootp Displays parameters that have been set for extended BOOTP requests. Router# show async status Displays statistics for asynchronous interface activity.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Command Purpose Step 4 Router(config-if)# async mode interactive Configures interactive mode on the asynchronous interface. Step 5 Router(config-if)# ppp authentication chap pap list-name Enables CHAP and PAP authentication on the interface. Replace the list-name variable with a specified authentication list name.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines If you are having trouble, enter one of the following debug commands and then send a call into the access server. Interpret the output and make configuration changes accordingly.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines *Mar 1 21:35:02.854: *Mar 1 21:35:02.854: *Mar 1 21:35:02.858: *Mar 1 21:35:02.858: *Mar 1 21:35:02.862: *Mar 1 21:35:02.866: *Mar 1 21:35:02.870: *Mar 1 21:35:02.870: *Mar 1 21:35:02.874: *Mar 1 21:35:03.842: *Mar 1 21:35:03.842: *Mar 1 21:35:03.846: *Mar 1 21:35:03.850: *Mar 1 21:35:03.854: *Mar 1 21:35:03.854: *Mar 1 21:35:03.858: *Mar 1 21:35:03.962: *Mar 1 21:35:03.966: *Mar 1 21:35:03.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar dant *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 21:35:06.206: 21:35:06.206: 21:35:06.314: 21:35:06.318: 21:35:07.274: 21:35:07.278: 21:35:07.282: 21:35:07.286: 21:35:07.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Connections are authenticated using the method specified for the line configurations for the asynchronous rotary group. If a connection is queued, authentication is done prior to queueing and no authentication is done when the connection is later established.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Monitoring and Maintaining Asynchronous Rotary Line Queues To display queued lines and to remove lines from the queue, use the following commands in EXEC mode as needed: Command Purpose Router# show line async-queue rotary-group Displays which lines are queued. Router# clear line async-queue rotary-group Clears all rotary queues or the specified rotary queue.
Configuring Asynchronous Lines and Interfaces How to Configure Asynchronous Interfaces and Lines Verifying Autoselect PPP The following trace appears when the debug modem and debug ppp negotiation commands are enabled. As PPP calls pass through the access server, you should see this output. When autoselect is used, “login” authentication is bypassed. If security is required, it must be performed at the protocol level (that is, ARAP or PPP authentication). SLIP does not offer protocol layer authentication.
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features 22:45:22: ARAP: ---------- ZONELISTINFO ---------22:45:22: ARAP: ---------- ZONELISTINFO ---------- The following trace is for ARA version 1.
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features You cannot use the auxiliary (AUX) port as a second console port. To use the AUX port as a console port, you must order a special cable from your technical support personnel. On an access server, you can configure any of the available asynchronous interfaces (1 through 8, 16, or 48).
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features To control the EXEC process, use the following commands in line configuration mode: Command Purpose Step 1 Router(config-line)# exec Turns on EXEC processes. Step 2 Router(config-line)# exec-timeout minutes [seconds] Sets the idle terminal timeout interval.
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features In interactive mode, a line can be used to make any type of connection, depending on the EXEC command entered by the user. For example, depending on its configuration, the line could be used for Telnet or XRemote connections, or SLIP or PPP encapsulation. The user is prompted for an EXEC command before a connection is initiated.
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features Using Advanced Addressing Methods for Remote Devices You can control whether addressing is dynamic (the user specifies the address at the EXEC level when making the connection) or whether default addressing is used (the address is forced by the system). If you specify dynamic addressing, the router must be in interactive mode and the user will enter the address at the EXEC level.
Configuring Asynchronous Lines and Interfaces How to Configure Other Asynchronous Line and Interface Features Assigning asynchronous addresses dynamically is useful when you want to assign set addresses to users. For example, an application on a personal computer that automatically dials in using Serial Line Internet Protocol (SLIP) and polls for electronic mail messages can be set up to dial in periodically and enter the required IP address and password.
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines Forcing Header Compression at the EXEC Level On SLIP interfaces, you can force header compression at the EXEC prompt on a line on which header compression has been set to passive. This option allows more efficient use of the available bandwidth and does not require entering privileged configuration mode.
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines Interface and Line Configuration Examples This section contains the following examples: • Asynchronous Interface Backup DDR Configuration Example • Passive Header Compression and Default Address Example • High-Density Dial-In Solution Using Autoselect and EXEC Control Example • Asynchronous Line Backup DDR Configuration Example Asynchronous Interface Backup DDR Configuration Example The follow
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines modem InOut transport preferred none transport input all Asynchronous Line Backup DDR Configuration Example The following example configures one asynchronous line on a Cisco AS2511-RJ access server that is used in an asynchronous backup DDR scenario: line 1 modem InOut speed 115200 transport input all flowcontrol hardware Line AUX Configuration Example In the following example, the asynchronous inte
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines The following example enables asynchronous rotary line queueing: line 1 2 rotary 1 queued The following example enables asynchronous rotary line queueing using the round-robin algorithm: line 1 2 rotary 1 queued round-robin Dedicated Asynchronous Interface Configuration Example The following example shows how to assign an IP address to an asynchronous interface and place the line in dedicated networ
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines Asynchronous Group Interface Examples The following example shows how to create an asynchronous group interface 0 with group interface members 2 through 7, beginning in global configuration mode: interface group-async 0 group-range 2 7 The following example shows how you need to configure asynchronous interfaces 1, 2, and 3 separately if you do not have a group interface configured: interface Async1
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines High-Density Dial-In Solution Using an Asynchronous Group The following example configures a Cisco AS5800 access server that is used as a high-density dial-in solution: interface group-async 0 ip unnumbered FastEthernet0/2/0 encapsulation ppp async mode interactive peer default ip address pool default no cdp enable ppp authentication chap hold-queue 10 in group-range 1/2/00 1/9/71 Asynchronous Interf
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines ip address-pool local ! This command defines the ip address pool. ! The address pool is named group1 and comprised of addresses. ! 172.30.0.1 through 172.30.0.28 inclusive ip local-pool group1 172.30.0.1 172.30.0.
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines Asynchronous Routing and Dynamic Addressing Configuration Example The following example shows a simple configuration that allows routing and dynamic addressing. With this configuration, if the user specifies /routing in the EXEC slip or ppp command, routing protocols will be sent and received.
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines Asynchronous Interface As the Only Network Interface Example The following example shows how one of the asynchronous lines can be used as the only network interface. The router is used primarily as a terminal server, but is at a remote location and dials in to the central site for its only network connection. ip default-gateway 10.11.12.
Configuring Asynchronous Lines and Interfaces Configuration Examples for Asynchronous Interfaces and Lines IGRP Configuration Example In the following example, only the Interior Gateway Routing Protocol (IGRP) TCP/IP routing protocol is running; it is assumed that the systems that are dialing in to use routing will either support IGRP or have some other method (for example, a static default route) of determining that the router is the best place to send most of its packets. router igrp 111 network 10.11.
Configuring Asynchronous Serial Traffic over UDP This chapter describes how to communicate with a modem using the Asynchronous Serial Traffic over UDP feature in the following main sections: • UDPTN Overview • How to Configure Asynchronous Serial Traffic over UDP See the “Configuration Examples for UDPTN” section for configuration examples. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.
Configuring Asynchronous Serial Traffic over UDP How to Configure Asynchronous Serial Traffic over UDP This feature is particularly useful for broadcast, multicast, and unstable point-to-point connections. This feature may not work as expected when there are multiple users on the same port number in a nonmulticast environment. The same port must be used for both receiving and sending.
Configuring Asynchronous Serial Traffic over UDP How to Configure Asynchronous Serial Traffic over UDP Enabling UDPTN There are two methods of enabling UDPTN. You can manually enable UDPTN when you want to begin transmission or reception, or you can configure the router to automatically enable UDPTN when a connection is made to the line.
Configuring Asynchronous Serial Traffic over UDP Configuration Examples for UDPTN Step 3 While the udptn command is enabled, enter the show ip socket command to verify that the socket being used for UDPTN opened correctly. Router# show ip socket Proto Remote Port 17 --listen-17 0.0.0.0 520 17 1.1.1.2 57 17 224.1.1.1 57 Local 172.21.14.90 172.21.14.90 1.1.1.1 1.2.2.
Configuring Asynchronous Serial Traffic over UDP Configuration Examples for UDPTN Broadcast UDPTN Example These configurations are for broadcast UDPTN. This is the simplest method to send to multiple receivers. The broadcasting router sends to the broadcast IP address, and any router that wants to receive the transmission simply connects to the broadcast IP address by using the udptn command. Router That Is Broadcasting interface ethernet 0 ip address 10.1.1.1 255.255.255.
Configuring Asynchronous Serial Traffic over UDP Configuration Examples for UDPTN Router B interface ethernet 0 ip address 10.54.46.2 255.255.255.192 ! line 10 no session-timeout transport output udptn dispatch-timeout 10000 dispatch-character 13 modem in autocommand udptn 10.54.46.
Configuring Asynchronous Serial Traffic over UDP Configuration Examples for UDPTN Cisco IOS Dial Technologies Configuration Guide DC-50
Modem Configuration and Management
Overview of Modem Interfaces This chapter describes modem interfaces in the following sections: • Cisco Modems and Cisco IOS Modem Features • Cisco IOS Modem Components • Logical Constructs in Modem Configurations See the chapter “Overview of Dial Interfaces, Controllers, and Lines” for more information about Cisco asynchronous serial interfaces. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.
Overview of Modem Interfaces Cisco IOS Modem Components Figure 12 Cisco AS2511-RJ Access Server Cisco AS2511-RJ 9 ASYNC 10 11 ASYNC 12 13 ASYNC 14 15 ASYNC 16 1 ASYNC 2 3 ASYNC 4 5 ASYNC 6 7 ASYNC 8 Modem Modems are outside the chassis 14479 Modem Figure 13 Cisco AS5300 Access Server Cisco AS5300 14480 Modems are inside the chassis Cisco IOS Modem Components Different components inside Cisco IOS software work together to enable remote clients to dial in and send packets.
Overview of Modem Interfaces Cisco IOS Modem Components Figure 14 Cisco IOS Modem Concepts Headquarters intranet/Internet Interface virtual template Interface group-async Cloning Fast Ethernet interface Virtual access interface Interface dialer controlling the D channels Loopback interface Routing and switching engine Cloning Cloning Asynchronous interfaces Lines Interface serial channels S0:0, S0:1… (B channels) Modems AAA TDM bus Controllers Cisco IOS software inside a Cisco AS5300 E1/T
Overview of Modem Interfaces Logical Constructs in Modem Configurations Logical Constructs in Modem Configurations A logical construct stores core protocol characteristics to assign to physical interfaces. No data packets are forwarded to a logical construct. Cisco uses three types of logical constructs in its access servers and routers.
Overview of Modem Interfaces Logical Constructs in Modem Configurations Specifically, you configure asynchronous interfaces to support PPP connections.
Overview of Modem Interfaces Logical Constructs in Modem Configurations Modem Lines and Asynchronous Interfaces Modems attach to asynchronous lines, which in turn attach to asynchronous interfaces. Depending on the type of access server you have, these components appear outside or inside the physical chassis. Figure 16 shows the logical relationships among modems, asynchronous lines, asynchronous interfaces, and group asynchronous interfaces.
Overview of Modem Interfaces Logical Constructs in Modem Configurations Modem Calls Modem calls travel through traditional telephone and ISDN lines. Regardless of the media used, these calls are initiated by a modem and terminate on another modem at the remote end. Figure 17 shows a remote laptop using a V.90 internal modem to dial in to a Cisco AS5300 access server, which is loaded with 96 internal V.90 MICA technologies modems.
Overview of Modem Interfaces Logical Constructs in Modem Configurations In the following sample display, absolute line numbers are listed at the far left. Relative line numbers are in the third column, after the line type. The second virtual terminal line, vty 1, is absolute line number 3. Compare the line numbers in this sample display to the output from the show line command. Line 0 con 1 aux 2 vty 3 vty 4 vty 5 vty 6 vty User 0 0 0 1 2 3 4 Host(s) Idle Location incoming 0 SERVER.COMPANY.
Overview of Modem Interfaces Logical Constructs in Modem Configurations Table 5 tty Lines Associated with Cisco AS5200 Modems tty Line Slot/Modem Number tty Line Slot/Modem Number 1 1/0 25 2/0 2 1/1 26 2/1 3 1/2 27 2/2 4 1/3 28 2/3 5 1/4 29 2/4 6 1/5 30 2/5 7 1/6 31 2/6 8 1/7 32 2/7 9 1/8 33 2/8 10 1/9 34 2/9 11 1/10 35 2/10 12 1/11 36 2/11 13 1/12 37 2/12 14 1/13 38 2/13 15 1/14 39 2/14 16 1/15 40 2/15 17 1/16 41 2/16 18 1/17 42 2
Overview of Modem Interfaces Logical Constructs in Modem Configurations For example, a laser printer is attached to line 10 of a Cisco 2511 router. Such a printer usually uses XON/XOFF software flow control. Because the Cisco IOS software cannot receive an incoming connection if the line already has a process, you must ensure that an EXEC session is not accidentally started.
Configuring and Managing Integrated Modems The Cisco IOS software provides commands that manage modems that reside inside access servers or routers in the form of modem cards. This chapter describes the modem management tasks.
Configuring and Managing Integrated Modems Modems and Modem Feature Support Table 6 Cisco IOS Modems and Modem Feature Support Cisco 2600/3600 Series Routers Device Support Cisco AS5300 Cisco AS5350 Cisco AS5400 Cisco AS5800 Integrated modems 6- and 12-port MICA 60-port NextPort CSM v6DFC 108-port NextPort CSM v6DFC 6-port, 12-port, 72- and 144-port MICA 18-port, 24-port, or 324-port 30-port MICA NextPort CSM NM-DM v6DFC 8- and 16-port analog NM-AM V.90 Yes Yes Yes Yes Yes with NM-DM V.
Configuring and Managing Integrated Modems Modems and Modem Feature Support to an ISDN B channel allowing the remote station or terminal adapter to use the fast call setup times offered by ISDN. This feature allows V.110 calls to be originated and terminated over ISDN. It also enables GSM wireless connectivity. V.110, as an alternative to V.120, provides DTE with V-series type interfaces with access to ISDN network by bit stuffing. Many V.110 devices are used in Europe and Japan.
Configuring and Managing Integrated Modems Managing Modems V.120 Bit Rate Adaptation Standard ITU-T Recommendation V.120 revised by the ITU-T Study Group 14. V.120 describes a standard that can be used for adapting terminals with non-ISDN standard network interfaces to an ISDN.
Configuring and Managing Integrated Modems Managing Modems • Displaying Local Disconnect Reasons • Removing Inoperable Modems • Busying Out a Modem Card • Monitoring Resources on Cisco High-End Access Servers Managing SPE Firmware You can upgrade your modem firmware to the latest NextPort Service Processing Element (SPE) firmware image available from Cisco. The SPE firmware image is usually retrieved from Cisco.com.
Configuring and Managing Integrated Modems Managing Modems Step 4 Command Purpose Router(config-spe)# firmware location [IFS:[/]]filename Specifies the SPE firmware file in flash memory to use for the selected SPEs. Allows you to upgrade firmware for SPEs after the new SPE firmware image is copied to your flash memory. The Cisco IOS file specification (IFS) can be any valid IFS on any local file system. Use the dir all-filesystems EXEC command to display legal IFSs.
Configuring and Managing Integrated Modems Managing Modems SPE# 7/00 7/01 7/02 7/03 . . .
Configuring and Managing Integrated Modems Managing Modems Command Purpose Step 3 Router(config-line)# transport {input | output} {all | none} Specifies that connection protocols can be used when connecting to the line. For outgoing calls, choose the output option. For incoming calls, choose the input option. If you do not intend to dial out, choose the none option.
Configuring and Managing Integrated Modems Managing Modems Troubleshooting the Dial-In Connection Depending upon the problems you experience, take the appropriate action: • If you are having problems making or receiving calls, make sure that you turned on the protocols for connecting to the lines and configured for incoming and outgoing calls. • If the calls are not coming up at all, turn on modem debugging.
Configuring and Managing Integrated Modems Managing Modems • microcom_mimic—Cisco (Microcom) internal analog modem (NM-AM–2600/3600) • microcom_server—Cisco (Microcom) V.34/56K internal digital modem (AS5200) Enter these modemcap names with the modem autoconfigure type command. For more information on creating and using modemcaps refer to the TAC Tech Notes documentation, Recommended Modemcaps for Internal Digital and Analog Modems on Cisco Access Servers, at the following URL: http://www.cisco.
Configuring and Managing Integrated Modems Managing Modems Using the Modem Autoconfigure Discovery Feature If you prefer that the modem software use its autoconfigure mechanism to configure the modem, use the modem autoconfigure discovery command. The following example shows how to configure modem autoconfigure discovery mode: Router# terminal monitor Router# debug confmodem Modem Configuration Database debugging is on Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z.
Configuring and Managing Integrated Modems Managing Modems Table 7 EXEC Commands: NextPort to MICA Command Comparison (continued) NextPort SPE Commands Purpose MICA Modem Commands clear spe Reboots all specified SPEs. All calls will be torn down. none clear spe counters Clears all statistics. clear modem counters clear spe log Clears all log entries for specified SPEs. clear modem log show port config Displays configuration parameters for the current active session.
Configuring and Managing Integrated Modems Managing Modems Table 8 SPE Configuration Commands: NextPort to MICA Command Comparison NextPort SPE Commands Purpose MICA Modem Commands busyout Busies out active calls. modem busyout firmware location filename Specifies the firmware file to be upgraded. Already implemented on the Cisco AS5300 and Cisco AS5800 platforms. firmware upgrade Specifies the upgrade method. Already implemented on the Cisco AS5300 platform.
Configuring and Managing Integrated Modems Managing Modems Configuring Cisco Integrated Modems Using Modem Attention Commands This section provides information about using modem attention (AT) command sets to modify modem configuration.
Configuring and Managing Integrated Modems Managing Modems Changing Configurations Manually in Integrated Microcom Modems You can change the running configuration of an integrated modem by sending individual modem AT commands. Manageable Microcom modems have an out-of-band feature, which is used to poll modem statistics and send AT commands. The Cisco IOS software uses a direct connect session to transfer information through this out-of-band feature.
Configuring and Managing Integrated Modems Managing Modems SPT BPS ADJ. ANSWER MESSGS SERIAL FLOW PASS XON/XOFF PARITY 0 ON BHW OFF 8N AT\W0 ATQ0 AT\Q3 AT\X0 AT The modem responds with “OK” when the AT command you send is received.
Configuring and Managing Integrated Modems Managing Modems To configure a modem for leased-line operation, use the following commands in global configuration mode: Command Purpose Step 1 Router(config)# modemcap entry modem-type-name:AA=S0=0&L2 Sets the modemcap for leased-line operation for the originating modem. Step 2 Router(config)# modemcap entry modem-type-name:AA=S0=1&L2 Sets the modemcap for leased-line operation for the answering modem.
Configuring and Managing Integrated Modems Managing Modems Note When Multilink PPP (MLP) is configured on a dialer interface, the dialer configuration has a default value of 2 minutes for dialer idle timeout. For leased-line connections, set the dialer idle timeout to infinity by adding dialer idle-timeout 0 to the configuration. Verifying the Analog Leased-Line Configuration The following information is important for verifying or troubleshooting your configuration.
Configuring and Managing Integrated Modems Managing Modems modemcap entry micro_LL_orig:AA=S0=0&L2 modemcap entry micro_LL_ans:AA=S0=1&L2 ! interface Async33 no ip address encapsulation ppp no ip route-cache no ip mroute-cache dialer in-band dialer pool-member 1 async default routing async dynamic routing async mode dedicated no peer default ip address no fair-queue no cdp enable ppp direction callout ppp multilink ! interface Dialer1 ip address 10.1.24.1 255.255.255.
Configuring and Managing Integrated Modems Managing Modems dialer pool-member 1 async default routing async dynamic routing async mode dedicated no peer default ip address no fair-queue no cdp enable ppp direction callout ppp multilink ! interface Dialer1 ip address 10.1.24.2 255.255.255.
Configuring and Managing Integrated Modems Managing Modems Modem pooling offers these benefits: • A certain number of modem ports can be guaranteed per DNIS. • Maximum simultaneous connection limits can be set for each DNIS. The following restrictions apply: • Modem pooling is not a solution for large-scale dial access. It cannot be used to create virtual modem pools across multiple access servers that are connected. Modem pooling is physically restricted to one access server.
Configuring and Managing Integrated Modems Managing Modems Command Purpose Step 5 Router# show configuration Displays the running configuration to verify the modem pool settings. Make changes accordingly. Step 6 Router# copy running-config startup-config Saves the running configuration to the startup configuration. 1. The DNIS string can have an integer x to indicate a “don’t care” digit for that position, for example, 555010x.
Configuring and Managing Integrated Modems Managing Modems Table 12 show modem-pool Field Descriptions (continued) Field Description active conn Number of simultaneous active connections for the specified modem pool or called party DNIS number. no free modems in pool Number of times incoming calls were rejected because there were no more free modems in the pool to accept the call. called_party_number Specified called party DNIS number.
Configuring and Managing Integrated Modems Managing Modems Modem Pooling Using Physical Partitioning One Cisco AS5300 loaded with 96 modems Modems in Pool Assigned DNIS Number 56K modems 24 555-1111 V.34 modems 24 555-2222 Fax-capable modems 24 555-3333 POS modems 24 555-4444 13053 Figure 19 Physical partitioning can also be used to set up an access server for bidirectional dial access. (See Figure 20.
Configuring and Managing Integrated Modems Managing Modems The following hardware configuration is used on the Cisco AS5200 access server: • One 2-port T1 PRI card • One 48-port card containing four 6-port MICA 56K modem modules and two 12-port Microcom V.
Configuring and Managing Integrated Modems Managing Modems Router(config-modem-pool)# pool-range 25-48 Router(config-modem-pool)# called-number 5550202 max-conn 24 Router(config-modem-pool)# ^Z Router# show modem-pool modem-pool: System-def-Mpool modems in pool: 0 active conn: 0 0 no free modems in pool modem-pool: 56kservices modems in pool: 48 active conn: 0 0 no free modems in pool called_party_number: 5550101 max conn allowed: 48, active conn: 0 0 max-conn exceeded, 0 no free modems in pool modem-pool:
Configuring and Managing Integrated Modems Managing Modems Step 2 Create the dial-out/fax-out modem pool for the 40 local employees connected to the headquarters LAN. This modem pool contains 12 fax-capable MICA modems. No DNIS is assigned to the pool. Because lines 85 to 96 are used for the dial-out and fax-out modem services, the asynchronous lines are configured for reverse Telnet.
Configuring and Managing Integrated Modems Managing Modems You should also include the host name, timeout interval, and authentication key: Router(config)# tacacs-server host 10.4.1.10 Router(config)# tacacs-server timeout 20 Router(config)# tacacs-server key nas1 Configuring Virtual Partitioning Virtual partitioning creates one large modem pool on one access server, but assigns different DNIS numbers to different customers.
Configuring and Managing Integrated Modems Managing Modems To configure virtual partitioning, perform the following steps: Step 1 Enter global configuration mode: Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Step 2 Create the shared modem pool for the 56K MICA modem services. This modem pool is called isp56kpool, which spans sixteen 6-port MICA 56K modem modules.
Configuring and Managing Integrated Modems Managing Modems Note The calltracker command, providing Call Tracker services, is supported for dial calls but not voice. Calltracker is supported for dial calls on 5x platforms (5300, 5350, 5400, 5800, and 5850). Call Tracker is notified of applicable call events by related subsystems such as ISDN, PPP, CSM, Modem, EXEC, or TCP-Clear.
Configuring and Managing Integrated Modems Managing Modems calltracker call-record terse calltracker history max-size 50 calltracker history retain-mins 5000 ! snmp-server engineID local 0012345 snmp-server community public RW snmp-server community private RW snmp-server community wxyz123 view v1default RO snmp-server trap-source FastEthernet0 snmp-server packetsize 17940 snmp-server queue-length 200 snmp-server location SanJose snmp-server contact Bob snmp-server enable traps snmp snmp-server enable traps
Configuring and Managing Integrated Modems Managing Modems Configuring MICA In-Band Framing Mode Control Messages Dial-in Internet connections typically start in character mode to allow the user to log in and select a preferred service. When Cisco IOS software determines that the user wants a framed interface protocol during the call, such as PPP or SLIP, commands are sent to the MICA modem so that it will provide hardware assistance with the framing.
Configuring and Managing Integrated Modems Managing Modems Use the modem dtr-delay command to reduce the time that a DTR signal is held down after an asynchronous line clears and before the DTR signal is raised again to accept new calls. Incoming calls may be rejected in heavily loaded systems, even when modems are unused because the default DTR hold-down interval may be too long. The modem dtr-delay command is designed for lines used for an unframed asynchronous session such as Telnet.
Configuring and Managing Integrated Modems Managing Modems Command Purpose Router(config-line)# modem log {cts | dcd | dsr | dtr | ri | rs323 | rts | tst} Configures the types of EIA/TIA events that are stored in the modem log. The default setting stores no EIA/TIA events. or Router(config-line)# no modem log {cts | dcd | dsr | dtr | ri | rs323 | rts | tst} Turns off the logging of a specific type of EIA/TIA event.
Configuring and Managing Integrated Modems Managing Modems Router# test modem back-to-back 1/1 1/0 Repetitions (of 10-byte packets) [1]: 10 Router# %MODEM-5-B2BCONNECT: Modems (1/1) and (1/0) connected in back-to-back test: CONN ECT9600/REL-MNP %MODEM-5-B2BMODEMS: Modems (1/0) and (1/1) completed back-to-back test: success/ packets = 20/20 After you enter the test modem back-to-back command, you must define the number of packets sent between modems at the Repetitions prompt.
Configuring and Managing Integrated Modems Managing Modems Step 3 Enter line configuration mode and manually remove modem 1/3 from dial services by entering the modem bad command on line 4: Router# configure terminal Router(config)# line 4 Router(config-line)# modem bad Router(config-line)# exit Router(config)# exit Step 4 Enter the show modem EXEC command or the show modem slot/port command to display the bad modem status.
Configuring and Managing Integrated Modems Managing Modems 0 0 0 0 failed dial attempts, 0 ring no answers, 1 busied outs no dial tones, 0 dial timeouts, 0 watchdog timeouts no carriers, 0 link failures, 0 resets, 0 recover oob protocol timeouts, 0 protocol errors, 0 lost events Transmit Speed Counters: Connection Speeds # of connections Connection Speeds # of connections Connection Speeds # of connections Connection Speeds # of connections Connection Speeds # of connections Connection Speeds # of connec
Configuring and Managing Integrated Modems Managing Modems Local disconnect reasons are listed across the top of the screen display (for example, wdogTimr, compress, retrain, inacTout, linkFail, moduFail, mnpProto, and lapmProt). In the body of the screen display, the number of times each modem disconnected is displayed (see the # column).
Configuring and Managing Integrated Modems Managing Modems * * * * * * * * * * * * * * * * * 2/7 2/8 2/9 2/10 2/11 2/12 2/13 2/14 2/15 2/16 2/17 2/18 2/19 2/20 2/21 2/22 2/23 Total 5 5 4 5 5 5 5 5 4 4 5 4 3 7 5 4 5 233 2 2 1 2 2 2 2 2 1 1 2 1 1 3 2 1 2 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 59 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 1 1 1 1 2 0 5 2 1 2 3 3 9 1 2 8 1 2 2 110 0 0 1 0 4 1 0 1 2 2 8 0 1 7 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Configuring and Managing Integrated Modems Managing Modems * * * * * * * 2/17 2/18 2/19 2/20 2/21 2/22 2/23 Total 5 5 3 0 4 2 0 84 5 5 3 0 4 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Removing Inoperable Modems To manually remove inoperable modems from dialup services, use the following commands in line configuration mod
Configuring and Managing Integrated Modems Managing Modems The following example gracefully disables the modem associated with line 1 from dialing and answering calls. The modem is disabled only after all active calls on the modem are dropped. Router# configure terminal Router(config)# line 1 Router(config)# modem busyout The following example abruptly shuts down the modem associated with line 2. All active calls on the modem are dropped immediately.
Configuring and Managing Integrated Modems Managing Modems Busying Out a Modem Card To busy out a modem card in a Cisco access server, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# line shelf/slot/port Specifies the line number, by specifying the shelf, slot, and port numbers; you must type in the slashes. This command also begins line configuration mode.
Configuring and Managing Integrated Modems Managing Modems configured lines. This feature is enabled and disabled through use of the CLI and MIBs. DS0 busyout traps are disabled by default and are supported on Cisco AS5300, Cisco AS5400, and Cisco AS5800 universal access servers. • Enabling ISDN PRI Requested Channel Not Available Traps—ISDN PRI channel not available traps are generated when a requested DS0 channel is not available, or when there is no modem available to take the incoming call.
Configuring and Managing Integrated Modems Managing Modems Enabling ISDN PRI Requested Channel Not Available Traps To generate ISDN PRI requested channel not available traps, use the following command in global configuration mode: Command Purpose Router(config)# snmp-server enable traps isdn chan-not-avail Generates a trap when the NAS rejects an incoming call on an ISDN PRI interface because the channel is not available.
Configuring and Managing Integrated Modems Managing Modems Troubleshooting the Traps To troubleshoot the traps, turn on the debug switch for SNMP packets by entering the following command in privileged EXEC mode: Router# debug snmp packets Check the resulting output to see that the SNMP trap information packet is being sent. The output will vary based on the kind of packet sent or received: SNMP: Packet received via UDP from 10.5.4.
Configuring and Managing Integrated Modems Managing Modems controller T1 0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 ! controller T1 1 framing esf linecode b8zs ds0-group 0 timeslots 1-24 type e&m-fgb cas-custom 0 ! controller T1 2 shutdown clock source line secondary 2 ! controller T1 3 shutdown clock source line secondary 3 ! controller T1 4 shutdown clock source line secondary 4 ! controller T1 5 shutdown clock source line secondary 5 ! controller T1 6 shutdown clock s
Configuring and Managing Integrated Modems Managing Modems no cdp enable ! interface FastEthernet0 ip address 10.5.4.
Configuring and Managing Integrated Modems Configuration Examples for Modem Management Configuration Examples for Modem Management This section provides the following examples: • NextPort Modem Log Example • Modem Performance Summary Example • Modem AT-Mode Example • Connection Speed Performance Verification Example For additional information and examples about the commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference.
Configuring and Managing Integrated Modems Configuration Examples for Modem Management Phase Jitter Level Far End Echo Level Phase Roll Total Retrains EC Retransmission Count Characters transmitted, received Characters received BAD PPP/SLIP packets transmitted, received PPP/SLIP packets received (BAD/ABORTED) EC packets transmitted, received OK EC packets (Received BAD/ABORTED) : : : : : : : : : : : 2 degrees -90 dBm 0 degrees 0 0 0, 0 0 0, 0 0 0, 0 0 Modem Performance Summary Example You can display a
Configuring and Managing Integrated Modems Configuration Examples for Modem Management The following example displays connection speed information for modems running up to 33,600 bps: Router# show modem connect-speeds 33600 transmit connect speeds Mdm * 0/0 * 0/1 0/2 * 0/3 * 0/4 * 0/5 * 0/6 * 0/7 * 0/8 * 0/9 * 0/10 * 0/11 0/12 * 0/13 * 0/14 * 0/15 * 0/16 * 0/17 * 0/18 * 0/19 * 0/20 * 0/21 * 0/22 * 0/23 * 2/0 * 2/1 * 2/2 * 2/3 * 2/4 * 2/5 * 2/6 * 2/7 * 2/8 * 2/9 * 2/10 * 2/11 * 2/12 * 2/13 * 2/14 * 2/15 * 2
Configuring and Managing Integrated Modems Configuration Examples for Modem Management * * * * * * * * * 0/3 0/4 0/5 0/6 0/7 0/8 0/9 0/10 0/11 0/12 * 0/13 * 0/14 * 0/15 * 0/16 * 0/17 * 0/18 * 0/19 * 0/20 * 0/21 * 0/22 * 0/23 * 2/0 * 2/1 * 2/2 * 2/3 * 2/4 * 2/5 * 2/6 * 2/7 * 2/8 * 2/9 * 2/10 * 2/11 * 2/12 * 2/13 * 2/14 * 2/15 * 2/16 * 2/17 * 2/18 * 2/19 * 2/20 * 2/21 * 2/22 * 2/23 Tot Tot % 0 1 0 0 0 2 0 1 0 1 0 1 0 0 1 1 0 0 1 0 0 0 0 0 1 0 0 0 1 1 0 2 0 0 1 1 1 0 0 0 0 1 1 0 0 23 5 0 0 0 0 0 0 0 0 0 0
Configuring and Managing Cisco Access Servers and Dial Shelves This chapter describes configuration and monitoring tasks for the Cisco AS5800 and AS5400 access servers, including dial shelves and dial shelf controllers on the Cisco AS5800 access servers in the following main sections: • Cisco AS5800 Dial Shelf Architecture and DSIP Overview • How to Configure Dial Shelves • Port Management Services on Cisco Access Servers • Upgrading and Configuring SPE Firmware For further information and configura
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves The Dial Shelf Interconnect Protocol (DSIP) is used for communication between router shelf and dial shelf on an AS5800. Figure 22 diagrams the components of the architecture. The router shelf is the host for DSIP commands, which can be run remotely on the feature boards of the dial shelf using the command, execute-on. DSIP communicates over the packet backplane via the dial shelf interconnect (DSI) cable.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves • Monitoring and Maintaining the DSCs • Troubleshooting DSIP Configuring the Shelf ID The Cisco AS5800 consists of a router shelf and a dial shelf. To distinguish the slot/port number on the Cisco AS5800, you must specify the shelf number. The default shelf number is 0 for the router shelf and 1 for the dial shelf. Caution You must reload the Cisco AS5800 for the new shelf number to take effect.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves If you are booting the router shelf from Flash memory, use the following commands beginning in EXEC mode: Step 1 Command Purpose Router# copy running-config tftp Saves your current (latest) configuration to a server. or Router# copy startup-config tftp Step 2 Router# configure terminal Begins global configuration mode. Step 3 Router(config)# shelf-id number router-shelf Configures the router shelf ID.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves • Detection of component failures • Error and warning messages DSC redundancy provides maximum system availability by preventing loss of service if one of the DSCs fails. There is no load sharing between the Broadband Inter-Carrier Interfaces (BICI). One BIC is used as a backup, carrying only control traffic, such as keepalives, until there is a switchover.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves Verifying External Clock Configuration To verify that the primary clock is running, enter the show dial-shelf clocks privileged EXEC command: Router# show dial-shelf 12 clocks Slot 12: System primary is 1/2/0 of priority 202 TDM Bus Master Clock Generator State = NORMAL Backup clocks: Source Slot Port Priority Status State ------------------------------------------------------Trunk 2 1 208 Good Default Slot Type 11
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves To configure a router for split dial shelf operation, perform the following steps: Step 1 Ensure that both DSCs and both router shelves are running the same Cisco IOS image. Note Having the same version of Cisco IOS running on both DSCs and both router shelves is not mandatory; however, it is a good idea. There is no automatic checking that the versions are the same.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves Step 10 Ensure that split mode is operating properly. Enter the show dial-shelf command for each router. This command has been extended so that the response indicates that the router shelf is running in split mode and which slots the router shelf owns. The status of any cards in any owned slots is shown, just as they are in the present show dial-shelf command.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves If the other router shelf and the other DSC claim ownership of the same slot, the command adding the slot should be rejected. However, should a configuration conflict exist, error messages are sent to both routers and the card is not reset until one of the other router shelves and its DSC stop claiming ownership of the slot.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves The normal mode configuration of the Cisco AS5800 requires the dial shelf and router shelf IDs to be different. In a split system, four unique shelf IDs are desirable, one for each router shelf and one for each of the slot sets; however, a split system will function satisfactorily if the router shelf IDs are the same.
Configuring and Managing Cisco Access Servers and Dial Shelves How to Configure Dial Shelves Verifying DSC Configuration To verify that you have started the redundant DSC feature, enter the show redundancy privileged EXEC command: Router# show redundancy DSC in slot 12: Hub is in 'active' state. Clock is in 'active' state. DSC in slot 13: Hub is in 'backup' state. Clock is in 'backup' state.
Configuring and Managing Cisco Access Servers and Dial Shelves Port Management Services on Cisco Access Servers Command Purpose Router# show dsip transport Displays information about the DSIP transport statistics for the control/data and IPC packets and registered addresses. Router# show dsip version Displays DSIP version information.
Configuring and Managing Cisco Access Servers and Dial Shelves Port Management Services on Cisco Access Servers The NextPort DFC performs the following functions: • Converts pulse code modulation (PCM) bitstreams to digital packet data. • Forwards converted and packetized data to the main processor, which examines the data and forwards it to the backhaul egress interface. • Supports all modem standards (such as V.34 and V.42bis) and features, including dial-in and dial-out.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Note • Supports all modem standards (such as V.34 and V.42bis) and features, including dial-in and dial-out. • Supports online insertion and removal (OIR), a feature that allows you to remove and replace UPCs while the system is operating. A UPC can be removed without disrupting the operation of other cards and their associated calls.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Firmware Configuration Task List To complete firmware configuration once you have downloaded the SPE firmware, perform the tasks in the following sections: Note • Specifying a Country Name • Configuring Dial Split Shelves (AS5800 Only) • Configuring SPEs to Use an Upgraded Firmware File • Disabling SPEs • Rebooting SPEs • Configuring Lines • Configuring Ports • Verifying SPE Line and Port
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Step 7 When the SPE firmware is downloaded to your workstation, transfer the file to a Trivial File Transfer Protocol (TFTP) server in your LAN using a terminal emulation software application. Step 8 When the SPE firmware is downloaded to your workstation, transfer the file to a TFTP server somewhere in your LAN using a terminal emulation software application.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Step 7 Quit your terminal session: ftp> quit Goodbye. Step 8 Enter the ls -al command to verify that you successfully transferred the files to your local directory: server% ls -al total 596 -r--r--r-- 1 280208 Jul 10 18:08 np-spe-upw-10.0.1.2.bin server% pwd /auto/tftpboot Step 9 Transfer these files to a local TFTP or remote copy protocol (RCP) server that your access server or router can access.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Specifying a Country Name To set the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs to be operational for call set up, you must specify the country name. To specify the country name, use the following command in global configuration mode: Command Purpose Router(config)# spe country country name Specifies the country to set the UPC or DFC parameters (including country code and encoding).
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware The dial-shelf split slot 0 3 4 5 command must be defined for the dial-shelf split backplane-ds0 option command to be active. You may also select the user defined option to define your own split.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Step 5 Command Purpose Router(config-spe)# firmware location filename Specifies the SPE firmware file in Flash memory to use for the selected SPEs. Allows you to upgrade firmware for SPEs after the new SPE firmware image is copied to your Flash memory. Enter the no firmware location command to revert back to the default Cisco IOS bundled SPE firmware.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Step 2 Command Purpose Router(config-spe)# busyout Gracefully disables an SPE by waiting for all the active services on the specified SPE to terminate. You can perform auto-diagnostic tests and firmware upgrades when you put the SPEs in the Busy out state. Active ports on the specified SPE will change the state of the specified range of SPEs to the BusyoutPending state.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Configuring Lines To configure the lines to dial in to your network, use the following commands beginning in global configuration mode: Step 1 Command Purpose Cisco AS5400 Series Routers Enters the line configuration mode. You can specify a range of slot and port numbers to configure.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Configuring Ports This section describes how to configure Cisco AS5800 UPC or Cisco AS5400 NextPort DFC ports. You need to be in port configuration mode to configure these ports. The port configuration mode allows you to shut down or put individual ports or ranges of ports in busyout mode.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Verifying SPE Line and Port Configuration To verify your SPE line configuration, enter the show spe command to display a summary for all the lines and ports: Step 1 Enter the show spe command to display a summary for all the lines and ports: Router# show spe Step 2 Enter the show line command to display a summary for a single line.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Clearing Log Events To clear some or all of the log events relating to the SPEs as needed, use the following privileged EXEC mode commands: Command Purpose Router# clear spe log Clears all event entries in the slot history event log. Router# clear spe counters Clears statistical counters for all types of services for the specified SPE, a specified range of SPEs, or all SPEs.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Note You might need to enable this command on several different combinations of ports to determine which one is not functioning properly. A pair of operable ports successfully connects and completes transmitting data in both directions. An operable port and an inoperable port do not successfully connect with each other.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Monitoring SPE Performance Statistics This section documents various SPE performance statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs: • SPE Events and Firmware Statistics • Port Statistics • Digital SPE Statistics • SPE Modem Statistics SPE Events and Firmware Statistics To view SPE events and firmware statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use one or
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Command Purpose Cisco AS5400 series routers Displays the port history event log.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware SPE Modem Statistics To view SPE modem statistics for the Cisco AS5400 NextPort DFCs or Cisco AS5800 UPCs, use one or more of the following commands in privileged EXEC mode: Command Purpose Cisco AS5400 series routers Displays the active statistics of a specified SPE, a specified range of SPEs, or all the SPEs serving modem traffic.
Configuring and Managing Cisco Access Servers and Dial Shelves Upgrading and Configuring SPE Firmware Command Purpose Cisco AS5400 series routers Displays the total number of connections within each high modulation or codec for a specific range of SPEs.
Configuring and Managing External Modems This chapter describes how to configure externally connected modems.
Configuring and Managing External Modems Automatically Configuring an External Modem Figure 23 Cisco AS2511-RJ Access Server Cisco AS2511-RJ 9 1 ASYNC ASYNC 10 2 11 ASYNC 12 3 ASYNC 4 13 ASYNC 14 5 ASYNC 6 15 ASYNC 16 7 ASYNC 8 Modem Modems are outside the chassis 14479 Modem When you configure modems to function with your access server, you must provide initialization strings and other settings on the modem to tell it how to function with the access server.
Configuring and Managing External Modems Automatically Configuring an External Modem Enter these modemcap names with the modemcap entry command. If your modem is not on this list and if you know what modem initialization string you need to use with it, you can create your own modemcap; see the following procedure “Using the Modem Autoconfigure Type Modemcap Feature.
Configuring and Managing External Modems Manually Configuring an External Modem Jan Jan Jan Jan Jan 16 16 16 16 16 18:16:18.324: 18:16:18.324: 18:16:18.324: 18:16:18.324: 18:16:18.324: TTY33: TTY33: TTY34: TTY34: TTY34: Detected modem speed 115200 Done with modem configuration Modem configuration succeeded Detected modem speed 115200 Done with modem configuration Manually Configuring an External Modem If you cannot configure your modem automatically, you must configure it manually.
Configuring and Managing External Modems Supporting Dial-In Modems Modems differ in the method that they use to lock the EIA/TIA-232 (serial) port speed. In the modem documentation, vendors use terms such as port-rate adjust, speed conversion, or buffered mode. Enabling error correction often puts the modem in the buffered mode. Refer to your modem documentation to learn how your modem locks speed (check the settings &b, \j, &q, \n, or s-register settings).
Configuring and Managing External Modems Supporting Dial-In Modems Figure 24 EXEC Creation on a Line Configured for Modem Dial-In Idle state DTR low, watching CTS Ring transition Raise DTR Lower DTR Answer timeout Hang up DTR high, watching CTS DTR low Lower DTR close connection Ringing CTS raised Create EXEC CTS lowered or exit Ready and active Note S1001a DTR high The modem callin and modem cts-required line configuration commands are useful for SLIP operation.
Configuring and Managing External Modems Testing the Modem Connection Testing the Modem Connection To test the connection, send the modem the AT command to request its attention. The modem should respond with “OK.” For example: at OK If the modem does not reply to the at command, perform the following steps: Step 1 Enter the show users EXEC command and scan the display output. The output should not indicate that the line is in use. Also verify that the line is configured for modem inout.
Configuring and Managing External Modems Managing Telnet Sessions Step 4 The speeds of the modem and the access server are likely to be different. If so, switch off the modem, and then switch it back on. This action should change the speed of the modem to match the speed of the access server. Step 5 Check your cabling and the modem configuration (echo or result codes might be off).
Configuring and Managing External Modems Managing Telnet Sessions Suspending Telnet Sessions: When you are connected to an external modem, the direct Telnet session must be terminated before the line can accept incoming calls. If you do not terminate the session, it will be indicated in the output of the show users command and will return a modem state of ready if the line is still in use. If the line is no longer in use, the output of the show line value command will return a state of idle.
Configuring and Managing External Modems Modem Troubleshooting Tips Modem Troubleshooting Tips Table 14 contains troubleshooting tips on modem access and control. Table 14 Modem Troubleshooting Tips Problem Likely Cause Connection refused. Someone already has a connection to that port. or an EXEC is running on that port. or The modem failed to lower the carrier detect (CD) signal after a call disconnected, resulting in an EXEC that remained active after disconnect.
Configuring and Managing External Modems Checking Other Modem Settings Checking Other Modem Settings This section defines other settings that might be needed or desirable, depending on your modem. Error correction can be negotiated between two modems to ensure a reliable data link. Error correction standards include Link Access Procedure for Modems (LAPM) and MNP4. V.42 error correction allows either LAPM or MNP4 error correction to be negotiated. Modems differ in the way they enable error correction.
Modem Signal and Line States This chapter describes modem states in the following section: • Signal and Line State Diagrams 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. For more information, see the “Identifying Supported Platforms” section in the “Using Cisco IOS Software” chapter.
Modem Signal and Line States Signal and Line State Diagrams The diagrams show two processes: • The “create daemon” process creates a tty daemon that handles the incoming network connection. • The “create EXEC” process creates the process that interprets user commands. (See Figure 25 through Figure 29.) In the diagrams, the current signal state and the signal the line is watching are listed inside each box. The state of the line (as displayed by the show line EXEC command) is listed next to the box.
Modem Signal and Line States Signal and Line State Diagrams Configuring Automatic Dialing With the dialup capability, you can set a modem to dial the phone number of a remote router automatically. This feature offers cost savings because phone line connections are made only when they are needed—you pay for using the phone line only when there is data to be received or sent.
Modem Signal and Line States Signal and Line State Diagrams Figure 26 EXEC Creation on a Line Configured for a High-Speed Modem Idle state DTR low, watching CTS Ring transition Raise DTR Lower DTR Answer timeout Hang up DTR high, watching CTS DTR low Lower DTR close connection Ringing CTS raised Create EXEC CTS lowered or exit Ready and active S1001a DTR high Supporting Dial-In and Dial-Out Connections To configure a line for both incoming and outgoing calls, use the following command in lin
Modem Signal and Line States Signal and Line State Diagrams Figure 27 Note EXEC and Daemon Creation for Incoming and Outgoing Calls If your system incorporates dial-out modems, consider using access lists to prevent unauthorized use. Configuring a Line Timeout Interval To change the interval that the Cisco IOS software waits for the CTS signal after raising the DTR signal in response to the DSR (the default is 15 seconds), use the following command in line configuration mode.
Modem Signal and Line States Signal and Line State Diagrams Closing Modem Connections Note The modem cts-required command was replaced by the modem printer command in Cisco IOS Release 12.2.
Modem Signal and Line States Signal and Line State Diagrams Configuring a Line to Disconnect Automatically To configure automatic line disconnect, use the following command in line configuration mode: Command Purpose Router(config-line)# autohangup Configures automatic line disconnect. The autohangup command causes the EXEC facility to issue the exit command when the last connection closes.
Modem Signal and Line States Signal and Line State Diagrams Figure 29 Daemon Creation on a Line Configured for Modem Dial-Out Cisco IOS Dial Technologies Configuration Guide DC-161
Creating and Using Modem Chat Scripts This chapter describes how to create and use modem chat scripts. These tasks are presented in the following main sections: • Chat Script Overview • How To Configure Chat Scripts • Using Chat Scripts 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.
Creating and Using Modem Chat Scripts How To Configure Chat Scripts Note Outbound chat scripts are not supported on lines where modem control is set for inbound activity only using the modem dialin command. How To Configure Chat Scripts The following tasks must be performed before a chat script can be used: • Define the chat script in global configuration mode using the chat-script command.
Creating and Using Modem Chat Scripts How To Configure Chat Scripts To define a chat script, use the following command in global configuration mode: Command Purpose Router(config)# chat-script script-name expect send... Creates a script that will place a call on a modem, log in to a remote system, or initialize an asynchronous device on a line.
Creating and Using Modem Chat Scripts How To Configure Chat Scripts This part of the script specifies that, after the connection is established, you want ssword to be displayed. If it is not displayed, you must press Return again after the timeout passes. (For more information about expressing characters in chat scripts, see the “Regular Expressions” appendix in the Cisco IOS Terminal Services Configuration Guide.
Creating and Using Modem Chat Scripts Using Chat Scripts Note Outbound chat scripts are not supported on lines where modem control is set for inbound activity only (using the modem dialin command). Manually Testing a Chat Script on an Asynchronous Line To test a chat script on any line that is currently not active, use the following commands in privileged EXEC mode: Command Purpose Step 1 Router# debug chat line number Starts detailed debugging on the specified line.
Creating and Using Modem Chat Scripts Using Chat Scripts Modem-Specific Chat Script Examples The following example shows line chat scripts being specified for lines connected to Telebit and US Robotics modems: ! Some lines have Telebit modems. line 1 6 script dialer telebit.* ! Some lines have US Robotics modems. line 7 12 script dialer usr.
Creating and Using Modem Chat Scripts Using Chat Scripts Table 17 Example Modem Script Execution Expect and Send Pair Implementation ABORT ERROR Ends the script execution if the text “ERROR” is found. (You can have as many active abort entries as you like.) “ ” “AT Z” Without expecting anything, sends an “AT Z” command to the modem. (Note the use of quotation marks to allow a space in the send string.) OK “ATDT \T Waits to see “OK.” Sends “ATDT 96837890.
Creating and Using Modem Chat Scripts Using Chat Scripts ! Script for logging into a Cisco access server and starting up TCP header compression: chat-script cisco-compressed... ! line 15 script dialer usrobotics-* ! interface async 15 dialer map ip 10.2.3.4 system-script *-v32 system-script cisco-compressed 91800 dialer map ip 10.3.2.
Creating and Using Modem Chat Scripts Using Chat Scripts Cisco IOS Dial Technologies Configuration Guide DC-170
Configuring Dial Backup with Dialer Profiles This chapter describes how to configure dialer interfaces, which can be configured as the logical intermediary between one or more physical interfaces and another physical interface that is to function as backup.
Configuring Dial Backup with Dialer Profiles How to Configure Dial Backup with Dialer Profiles Configuring a Dialer Interface To configure the dialer interface that will be used as an intermediary between a physical interface that will function as backup interface and the interfaces that will use the backup, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# interface dialer number Creates a dialer interface and begins interface configuration mode.
Configuring Dial Backup with Dialer Profiles Configuration Example of Dialer Profile for ISDN BRI Backing Up Two Leased Lines Command Purpose Step 3 Router(config-if)# backup interface dialer number Specifies the backup interface and begins interface configuration mode.
Dial Access Specialized Features
Configuring per-User Configuration This chapter describes per-user configuration, a large-scale dial solution. It includes the following main sections: • Per-User Configuration Overview • How to Configure a AAA Server for Per-User Configuration • Monitoring and Debugging Per-User Configuration Settings • Configuration Examples for Per-User Configuration This set of features is supported on all platforms that support Multilink PPP (MLP).
Configuring per-User Configuration Per-User Configuration Overview • Virtual profiles, which can use either or both of the two sources of information listed in the previous bullets for virtual interface configuration. When a user dials in, virtual profiles can apply the generic interface configuration and then apply the per-user configuration to create a unique virtual access interface for that user. This configuration is described in the chapter “Configuring Virtual Profiles” in this publication.
Configuring per-User Configuration Per-User Configuration Overview Figure 98 3. Per-User Configuration Authentication and Authorization A virtual access interface is created for this user. a. The router finds the virtual template that is set up for virtual profiles, if any, and applies the commands to the virtual access interface. b. The router looks for the AV pairs to apply to this virtual access interface to configure it for the dial-in user. c.
Configuring per-User Configuration Per-User Configuration Overview On a TACACS+ server, the entries for an IP address pool and a user of the pool might be as follows: user = nas1-pools { service = ppp protocol = ip { pool-def#1 = "aaa 10.0.0.1 10.0.0.3" pool-def#2 = "bbb 10.1.0.1 10.1.0.10" pool-def#3 = "ccc 10.2.0.1 10.2.0.
Configuring per-User Configuration Per-User Configuration Overview Supported Attributes for AV Pairs Table 37 provides a partial list of the Cisco-specific supported attributes for AV pairs that can be used for per-user virtual interface configuration. For complete lists of Cisco-specific, vendor-specific, and TACACS+ supported attributes, see the Cisco IOS Security Configuration Guide and Cisco IOS Security Command Reference.
Configuring per-User Configuration Per-User Configuration Overview Table 38 provides examples for each attribute on an AAA TACACS+ server. Table 38 TACACS+ Server AV Pair Examples for Each Attribute Attribute TACACS+ Server Examples inacl# IP: inacl#3="permit ip any any precedence immediate" inacl#4="deny igrp 10.0.1.2 255.255.0.0 any" IPX: inacl#1="deny 3C01.0000.0000.0001" inacl#2="deny 4C01.0000.0000.0002" outacl# outacl#2="permit ip any any precedence immediate" outacl#3="deny igrp 10.0.9.
Configuring per-User Configuration How to Configure a AAA Server for Per-User Configuration Table 39 RADIUS Server AV Pair Examples for Each Attribute (continued) Attribute RADIUS Server Examples outacl# cisco-avpair = "ip:outacl#2=permit ip any any precedence immediate", cisco-avpair = "ip:outacl#3=deny igrp 10.0.9.10 255.255.0.0 any", rte-fltr-in# IP: cisco-avpair = "ip:rte-fltr-in#1=router igrp 60", cisco-avpair = "ip:rte-fltr-in#3=permit 10.0.3.4 255.255.0.
Configuring per-User Configuration How to Configure a AAA Server for Per-User Configuration Configuring a Freeware TACACS Server for Per-User Configuration On a TACACS server, the entry in the user file takes a standard form.
Configuring per-User Configuration How to Configure a AAA Server for Per-User Configuration } user = joe { # joe uses the group password. member = "staff" } user = pete { # pete has his own password. member = "staff" password = des "alkd9Ujiqp2y" } user = anita { # Use the "default" user password mechanism defined above.
Configuring per-User Configuration Monitoring and Debugging Per-User Configuration Settings Monitoring and Debugging Per-User Configuration Settings Per-user configuration information exists on AAA servers only and is configured there, as described in the “How to Configure a AAA Server for Per-User Configuration” section.
Configuring per-User Configuration Configuration Examples for Per-User Configuration IP Access Lists and Static Routes Using Virtual Profiles over ISDN BRI The following example provides configurations for the TACACS+ freeware daemon, the network access server, and the peer router named Router1. On the TACACS+ AAA server, peer router Router1 has a configuration that includes static routes and IP access lists.
Configuring per-User Configuration Configuration Examples for Per-User Configuration ip default-gateway 172.21.114.129 no ip classless ip route 0.0.0.0 0.0.0.0 172.21.114.129 ! virtual-profile virtual-template 1 dialer-list 1 protocol ip permit tacacs-server host 172.21.114.130 tacacs-server key tac123 Current Peer Configuration for Router1 version 11.3 no service pad ! hostname Router1 ! enable secret 5 $1$m1WK$RsjborN1Z.
Configuring per-User Configuration Configuration Examples for Per-User Configuration IPX Per-User SAP Filters Using IPXWAN and Virtual Profiles by a Synchronous Interface The following example provides configurations for the TACACS+ daemon and the peer router named Router1. On the TACACS+ AAA server, user ny has a configuration that includes inbound and outbound SAP filters.
Configuring per-User Configuration Configuration Examples for Per-User Configuration ip name-server 172.19.2.132 ipx routing 0000.0c47.12d3 ipx internal-network 40 ! interface Ethernet0 ip address 172.21.114.133 255.255.255.224 ! interface Virtual-Template1 no ip address ipx ipxwan 0 unnumbered nas-Router2 no cdp enable ! interface Serial1 ip unnumbered Ethernet0 encapsulation ppp ipx ipxwan 0 unnumbered nas-Router2 ppp authentication chap ! ipx sap 333 DEEP9 40.0000.0000.
Configuring per-User Configuration Configuration Examples for Per-User Configuration ! username Router1 password 7 15050E0007252621 ip host Router2 172.21.114.132 ip domain-name cisco.com ip name-server 172.19.2.132 ip name-server 192.168.30.32 isdn switch-type basic-5ess interface Ethernet0 ip address 172.21.114.132 255.255.255.
Configuring per-User Configuration Configuration Examples for Per-User Configuration ! ip default-gateway 172.21.114.129 no ip classless ip route 172.21.0.0 255.255.0.0 BRI0 dialer-list 1 protocol ip permit ! line con 0 exec-timeout 0 0 line vty 0 4 password lab login ! end Output of ping Command from Router1 Router1# ping 172.21.114.132 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.21.114.132, timeout is 2 seconds: U.U.
Configuring per-User Configuration Configuration Examples for Per-User Configuration *Apr 4 08:30:09: Channel ID i = 0x89 *Apr 4 08:30:09: Called Party Number i = 0xC1, ‘61483’ *Apr 4 08:30:09: ISDN BR0: Event: Received a call from on B1 at 64 Kb/s *Apr 4 08:30:09: ISDN BR0: Event: Accepting the call %LINK-3-UPDOWN: Interface BRI0:1, changed state to up *Apr 4 08:30:09: ISDN BR0: received HOST_CONNECT Channel ID i = 0x0101 *Apr 4 08:30:09: ------------------Channel ID i = 0x89 *Apr 4 08:30:09: IS
Configuring per-User Configuration Configuration Examples for Per-User Configuration *Apr 4 08:30:10: AAA/AUTHOR/FSM: BRI0:1: (0): send AV protocol=ip *Apr 4 08:30:10: AAA/AUTHOR/FSM: BRI0:1: (3920403585): Method=RADIUS *Apr 4 08:30:10: AAA/AUTHOR (3920403585): Post authorization status = PASS_ADD *Apr 4 08:30:10: AAA/AUTHOR/FSM: BRI0:1: we can start IPCP (0x8021) *Apr 4 08:30:10: AAA/AUTHOR/FSM: BRI0:1: (0): can we start UNKNOWN? *Apr 4 08:30:10: AAA/AUTHOR/FSM: BRI0:1: (0): user=’Router1’ *Apr 4 08:30:10
Configuring per-User Configuration Configuration Examples for Per-User Configuration Router2# show ip access-list Standard IP access list Virtual-Access1#1 (per-user) deny 10.0.0.
Configuring per-User Configuration Configuration Examples for Per-User Configuration Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is disabled Router2# debug ip packet IP packet debugging is on Router2# *Apr 4 08:30:42: IP: s=172.21.114.129 (Ethernet0), d=255.255.255.255, len 186, rcvd 2 *Apr 4 08:30:42: IP: s=10.0.0.1 (Virtual-Access1), d=172.21.114.132, len 104, a*Apr 4 08:30:42: IP: s=10.0.0.
Configuring per-User Configuration Configuration Examples for Per-User Configuration interface Serial1 no ip address encapsulation ppp ipx ipxwan 0 unnumbered peer-Router1 clockrate 4000000 ! ipx sap 444 ZEON-4 30.0000.0000.0001 444 10 ipx sap 555 ZEON-5 30.0000.0000.0001 555 10 ipx sap 666 ZEON-6 30.0000.0000.0001 666 10 ! ... version 12.
Configuring per-User Configuration Configuration Examples for Per-User Configuration [Vendor [Vendor [Vendor [Vendor 9] 9] 9] 9] cisco-avpair cisco-avpair cisco-avpair cisco-avpair = = = = “ipx:sap-fltr-out#21=deny 40 202” “ipx:sap-fltr-out#22=permit -1” “ipx:sap-fltr-in#23=permit 30 444” “ipx:sap-fltr-in#23=deny -1” Network Access Server show Command Output Router2# show ipx servers Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail 5 Total IPX Servers Table ordering is ba
Configuring Resource Pool Management This chapter describes the Cisco Resource Pool Management (RPM) feature. It includes the following main sections: • RPM Overview • How to Configure RPM • Verifying RPM Components • Troubleshooting RPM • Configuration Examples for RPM To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.
Configuring Resource Pool Management RPM Overview Note • Manage call sessions by differentiating dial customers through customer profiles. The customer profile determines where resources are allocated and is based on the incoming Dialed Number Information Service (DNIS) number or Calling Line Identification (CLID). • Efficiently use resource groups such as modems to offer differing over subscription rates and dial service-level agreements.
Configuring Resource Pool Management RPM Overview Customer Profile Types There are three types of customer profiles in Cisco RPM, which are described in the following sections: • Customer Profiles • Default Customer Profiles • Backup Customer Profiles Additionally, you can create a customer profile template and associate it with a customer profile; it is then integrated into the customer profile. Customer Profiles A customer profile defines how and when to answer a call.
Configuring Resource Pool Management RPM Overview The outgoing side of the customer profile directs the answered call to the appropriate destination: • To a local AAA server of retail dial applications and Internet/intranet access. • To a tunnel that is established between the NAS or L2TP Access Concentrator (LAC) to a wholesale VPDN home gateway of a dial customer, or L2TP Network Server (LNS) using Layer 2 Forwarding Protocol (L2F) or Layer 2 Tunneling Protocol (L2TP) technology.
Configuring Resource Pool Management RPM Overview The RPM customer profile template for the PPP command set, when used with the Cisco IOS feature, Server Groups Selected by DNIS, presents a strong single NAS solution for providers of wholesale dial services, as follows: • Call acceptance is determined by the RPM before call answering, using the configured size limits and resource availability.
Configuring Resource Pool Management RPM Overview Note Voice over IP, fax over IP, and dial-out calls are not supported in RPM. Resource Groups Cisco RPM enables you to maximize the use of available shared resources within a Cisco NAS for various resource allocation schemes to support service-level agreements. Cisco RPM allows you to combine your Cisco NAS resource groups with call types (speech, digital, V.110, and V.120) and optional resource modem services.
Configuring Resource Pool Management RPM Overview Table 41 Resource Services (continued) Service Options Comments error-correction 1apm, mn14 This is a hidden command. compression mnps, v42bis This is a hidden command. VPDN Groups The VPDN group contains the data required to build a VPDN tunnel from the RPM NAS LAC to the LNS.
Configuring Resource Pool Management RPM Overview Table 42 Call-Treatment Table Event Call-Treatment Option Results Customer profile not found No answer (default) The caller receives rings until the switch eventually times out. Implies that the NAS was appropriate, but resources were unavailable. The caller should try later. Busy The switch drops the call from the NAS and sends a busy signal back to the caller. The call is rejected based on not matching a DNIS group/call type and customer profile.
Configuring Resource Pool Management RPM Overview 5. If resources are available from the resource group defined in the customer profile, the call is answered. Otherwise, the call is rejected. 6. As sessions start and end, the session counters increase and decrease, so the customer profile call counters are kept current. See Figure 100 for a graphical illustration of the RPM call processes.
Configuring Resource Pool Management RPM Overview If a VPDN group is found within the customer profile, the VPDN group data is used to build a VPDN tunnel, as follows: • If the VPDN group limits (number of multilink bundles, number of links per bundle) have not been exceeded, a VPDN tunnel is built. • If the limits have been reached, the call is disconnected. If no VPDN profile is assigned to the customer profile and VPDN is enabled, non-RPM VPDN service is attempted.
Configuring Resource Pool Management RPM Overview Call Discriminator Profiles The Cisco RPM CLID/DNIS Call Discriminator feature lets you specify a list of calling party numbers to be rejected for inbound calls. This Cisco IOS Release 12.2 CLID/DNIS call screening feature expands previous call screening features in Cisco RPM. CLID/DNIS call screening provides an additional way to screen calls on the basis of CLID/DNIS for both local and remote RPM.
Configuring Resource Pool Management RPM Overview Figure 102 Call Discrimination DNIS groups dnis123 dnisabc dnisspeech 5267000 5267001 527 1299 5274999 Reserved keyword identifying default DNIS reaching all values Call discriminator definitions CD Name DNIS Group Call Types CD123 CDabc CDspeech CDv120 dnis123 dnisabc dnisspeech default speech digital digitalv110v120 v120 Reject calls to DNIS group dnis123 with speech call type Reject calls to DNIS group dnisabc with digital call type Reject
Configuring Resource Pool Management RPM Overview RPM Standalone Network Access Server A single NAS using Cisco RPM can provide the following: • Wholesale VPDN dial service to corporate customers • Direct remote services • Retail dial service to end users Figure 103 and Figure 104 show multiple connections to a Cisco AS5300 NAS. Incoming calls to the NAS can use ISDN PRI signaling, CAS, or the SS7 signaling protocol.
Configuring Resource Pool Management RPM Overview Figure 104 Resource Pool Management with Direct Remote Services Customer A Optional local AAA AAA DNS Modem Cisco AS5300 (NAS) Terminal adapter WAN infrastructure PSTN Router DNIS AAA DNS Remote user 28307 Customer profiles Customer B Call Processing For call processing, incoming calls are matched to a DNIS group and the customer profile associated with that DNIS group.
Configuring Resource Pool Management RPM Overview The session overflow limit determines the allowable number of sessions above the session limit. If the session overflow limit is greater than zero, overflow sessions are enabled and the maximum number of allowed sessions is the session limit plus the session overflow limit. While the session overflow limit has been reached, any new calls are rejected. Table 44 summarizes the effects of session and session overflow limits.
Configuring Resource Pool Management RPM Overview customer is having a corporate-wide program and many people are expected to request remote access, you could enable many overflow sessions and charge a premium rate for the extra bandwidth requirements. VPDN MLP Bundle and Links-per-Bundle Limits To ensure that resources are not consumed by a few users with MLP connections, Cisco RPM also enables you to specify the maximum number of MLP bundles that can open in a VPDN group.
Configuring Resource Pool Management RPM Overview Figure 105 DNIS and call type RPM Call-Processing Flowchart for a Standalone Network Access Server Call discriminator match Reject call treatment: No answer Yes No Mapped DNIS customer profile exists No Reject—No CP call treatment: No answer (default) or busy Yes Yes Has CP reached maximum connections Yes Overflow configured and maximum not exceeded No Reject—Session limit call treatment busy Yes Resources available No Reject—No resource
Configuring Resource Pool Management RPM Overview Figure 106 DNIS and call type Flowchart for a Standalone Network Access Server with RPM Direct Remote Services Call discriminator match Reject call treatment: No answer Yes No Mapped DNIS customer profile exists Reject—No CP call treatment: No answer (default) or busy No Yes No Has CP reached maximum connections Yes Overflow configured and maximum not exceeded No Reject—Session limit call treatment busy Yes Resources available No Reject—N
Configuring Resource Pool Management RPM Overview RPM Using the Cisco RPMS Figure 107 shows a typical resource pooling network scenario using RPMS.
Configuring Resource Pool Management RPM Overview Direct Remote Services Direct remote services is an enhancement to Cisco RPM implemented in Cisco IOS Release 12.0(7)T that enables service providers to implement wholesale dial services without using VPDN tunnels. A customer profile that has been preconfigured with a PPP template to define the unique PPP services for the wholesale dial customer is selected by the incoming DNIS and call type.
Configuring Resource Pool Management How to Configure RPM Additional Information About Cisco RPM For more information about Cisco RPM, see the following documents: • AAA Server Group • Cisco Access VPN Solutions Using Tunneling Technology • Cisco AS5200 Universal Access Server Software Configuration Guide • Cisco AS5300 Software Configuration Guide • Cisco AS5800 Access Server Software ICG • Cisco Resource Pool Manager Server Configuration Guide • Cisco Resource Pool Manager Server Installatio
Configuring Resource Pool Management How to Configure RPM • Accomplish initial configuration as described in the appropriate Universal Access Server Software Configuration Guide. Perform the following tasks as required. – Set your local AAA – Define your TACACS+ server for RPM – Define AAA accounting – Ensure PPP connectivity – Ensure VPDN connectivity Refer to the document Configuring the NAS for Basic Dial Access for more information.
Configuring Resource Pool Management How to Configure RPM Note If you have an RPMS, you need not define VPDN groups/profiles, customer profiles, or DNIS groups on the NAS; you need only define resource groups. Configure the remaining items by using the RPMS system. Configuring DNIS Groups This configuration task is optional.
Configuring Resource Pool Management How to Configure RPM Creating CLID Groups You can add multiple CLID groups to a discriminator profile. You can organize CLID numbers for a customer or service type into a CLID group. Add all CLID numbers into one CLID group, or subdivide the CLID numbers using criteria such as call type, geographical location, or division.
Configuring Resource Pool Management How to Configure RPM Step 3 Command Purpose Router(config-call-d)# clid group {clid-group-name | default} Optional. Associates a CLID group with the discriminator. If you do not specify a clid-group-name, the default discriminator in the RM is used. Any CLID number coming in on a call is in its respective default group unless it is specifically assigned a clid-group-name.
Configuring Resource Pool Management How to Configure RPM Configuring Resource Groups To configure resource groups, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# resource-pool group resource name Creates a resource group and assign it a name of up to 23 characters.
Configuring Resource Pool Management How to Configure RPM Configuring Customer Profiles To configure customer profiles, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# resource-pool profile customer name Creates a customer profile. Step 2 Router(config-customer-pro)# dnis group {dnis-group-name | default} Includes a group of DNIS numbers in the customer profile.
Configuring Resource Pool Management How to Configure RPM The backup customer profile can contain all of the elements defined in a standard customer profile, including base size or overflow parameters. However, when the connection between the Cisco NAS and Cisco RPMS is unavailable, session counting and session limits are not applied to incoming calls. Also, after the connection is reestablished, there is no synchronization of call counters between the Cisco NAS and Cisco RPMS.
Configuring Resource Pool Management How to Configure RPM To configure a template in RPM, use the following commands beginning in global configuration mode: Step 1 Command Purpose Router(config)# template name Creates a customer profile template and assign a unique name that relates to the customer that will be receiving it. Note Steps 2, 3, and 4 are optional. Enter multilink, peer, and ppp commands appropriate to the application requirements of the customer.
Configuring Resource Pool Management How to Configure RPM template PPP1 peer default ip address pool pool1 pool2 ppp ipcp dns 10.1.1.1 10.1.1.2 ppp ipcp wins 10.1.1.3 10.1.1.4 ppp multilink max-links 2 . . . Step 2 Ensure that your template appears in the configuration file.
Configuring Resource Pool Management How to Configure RPM Configuring AAA Server Groups To configure AAA server groups, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# aaa new-model Enables AAA on the NAS. Step 2 Router(config)# radius-server key key Set the authentication and encryption key used for all RADIUS or TACACS+ communications between the NAS and the RADIUS or TACACS+ daemon.
Configuring Resource Pool Management How to Configure RPM To configure VPDN profiles, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# resource-pool profile vpdn profile-name Creates a VPDN profile and assigns it a profile name Step 2 Router(config-vpdn-profile)# limit base-size {number | all} Specifies the maximum number of simultaneous base VPDN sessions to be allowed for this VPDN group under the terms of the service-level agreement (SLA).
Configuring Resource Pool Management How to Configure RPM Command Purpose Step 5 Router(config-vpdn)# loadsharing ip ip-address [limit number] Configures the endpoints for loadsharing. This router will share the load of IP traffic with the first router specified in Step 2. The limit keyword limits the number of simultaneous sessions that are sent to the remote endpoint (HGW/LNS). This limit can be 0 to 32767 sessions.
Configuring Resource Pool Management How to Configure RPM To configure VPDN profile session counting, use the following commands beginning in global configuration mode: Command Purpose Step 1 Router(config)# resource-pool profile vpdn name Creates a VPDN profile. Step 2 Router(config-vpdn-profile)# vpdn-group name Router(config-vpdn-profile)# exit Associates a VPDN group to the VPDN profile. VPDN sessions done within this VPDN group will be counted by the VPDN profile.
Configuring Resource Pool Management How to Configure RPM 0 calls rejected due to resource unavailable 0 overflow connections 0 overflow states entered 0 overflow connections rejected 1435 minutes since last clear command Note Use the debug vpdn event command to troubleshoot VPDN profile limits, session limits, and MLP connections. First, enable this command; then, send a call into the access server. Interpret the debug output and make configuration changes as needed.
Configuring Resource Pool Management How to Configure RPM Configuring Switched 56 over CT1 and RBS To configure switched 56 over CT1 and RBS, use the following commands beginning in global configuration mode. Perform this task on the Cisco AS5200 and Cisco AS5300 access servers only. Command Purpose Step 1 Router(config)# controller t1 number Specifies a controller and begins controller configuration mode.
Configuring Resource Pool Management Verifying RPM Components Router# show dialer dnis number List of Numbers: default 2001 2002 2003 2004 . . .
Configuring Resource Pool Management Verifying RPM Components 11 calls rejected due to profile limits 2 calls rejected due to resource unavailable 0 minutes spent with max connections 5 overflow connections 1 overflow states entered 11 overflow connections rejected 10 minutes spent in overflow 214 minutes since last clear command Clearing Call Counters The clear resource-pool command clears the call counters.
Configuring Resource Pool Management Verifying RPM Components Verifying Call Counters for a DNIS Group The following output from the show dialer dnis command shows the call counters for a given DNIS group. These counters include historical data and can be cleared.
Configuring Resource Pool Management Troubleshooting RPM domain cisco2.com dnis customer1-calledg initiate-to ip 172.21.9.67 loadsharing ip 172.21.9.68 limit 100 backup ip 172.21.9.69 priority 5 vpdn-group customer2-vpdng request dialin protocol l2tp dnis customer2-calledg domain acme.com initiate-to ip 172.22.9.5 Troubleshooting RPM Test and verify that ISDN, CAS, SS7, PPP, AAA, and VPDN are working properly before implementing RPM.
Configuring Resource Pool Management Troubleshooting RPM Resource-Pool Component The resource-pool component contains two modules—a dispatcher and a local resource-pool manager. The dispatcher interfaces with the signaling stack, resource-group manager, and AAA, and is responsible for maintaining resource-pool call state and status information. The state transitions can be displayed by enabling the resource-pool debug traces. Table 45 summarizes the resource pooling states.
Configuring Resource Pool Management Troubleshooting RPM Successful Resource Pool Connection The following sample output from the debug resource-pool command displays a successful RPM connection. The entries in bold are of particular importance. *Mar 1 02:14:57.439: *Mar 1 02:14:57.439: *Mar 1 02:14:57.443: *Mar 1 02:14:57.447: *Mar 1 02:14:57.459: *Mar 1 02:14:57.487: DS0:0:0:0:21 *Mar 1 02:14:57.487: *Mar 1 02:14:57.491: *Mar 1 02:14:57.495: DS0:0:0:0:21 *Mar 1 02:14:57.603: *Mar 1 02:15:00.
Configuring Resource Pool Management Troubleshooting RPM modem-mgmt csm debug-rbs commands are used on Cisco AS5200 and Cisco AS5300 access servers, while the debug csm and debug trunk cas port number timeslots number commands are used on the Cisco AS5800 access server.
Configuring Resource Pool Management Troubleshooting RPM Troubleshooting Call Discriminator Problems The following output from the debug resource-pool command displays an incoming call that is matched against a call discriminator profile: *Mar *Mar *Mar *Mar *Mar *Mar *Mar 1 1 1 1 1 1 1 00:35:25.995: 00:35:25.999: 00:35:25.999: 00:35:26.003: 00:35:26.135: 00:35:26.139: 00:35:26.
Configuring Resource Pool Management Troubleshooting RPM Troubleshooting RPM/VPDN Connection The following sample output from the debug resource-pool command displays a successful RPM/VPDN connection. The entries in bold are of particular importance. *Mar 1 00:15:53.639: Se0:10 RM/VPDN/rm-session-request: Allocated vpdn info for domain NULL MLP Bundle SOHO *Mar 1 00:15:53.655: RM/VPDN/ACME_VPDN: VP LIMIT/ACTIVE/RESERVED/OVERFLOW are now 6/0/0/0 *Mar 1 00:15:53.
Configuring Resource Pool Management Troubleshooting RPM *Mar 1 04:03:49.878: Se0:19 AAA/AUTHOR/RM vpdn-session (3912941997): send AV multilink-id=SOHO *Mar 1 04:03:49.878: Se0:19 AAA/AUTHOR/RM vpdn-session (3912941997): found list "default" *Mar 1 04:03:49.882: Se0:19 AAA/AUTHOR/RM vpdn-session (3912941997): Method=LOCAL *Mar 1 04:03:49.886: Se0:19 AAA/AUTHOR/RM/local (3912941997): Received AV service=resource-management *Mar 1 04:03:49.
Configuring Resource Pool Management Troubleshooting RPM Troubleshooting VPDN Endpoint Problems The following output from the debug resource-pool command displays that the IP endpoint for the VPDN group is not reachable: *Mar 1 05:12:22.330: Se0:21 RM/VPDN/rm-session-request: Allocated vpdn info for domain NULL MLP Bundle SOHO *Mar 1 05:12:22.346: RM/VPDN/ACME_VPDN: VP LIMIT/ACTIVE/RESERVED/OVERFLOW are now 5/0/0/0 *Mar 1 05:12:22.350: RM/VPDN/ACME_VPDN: Session reserved for outgoing-2 *Mar 1 05:12:22.
Configuring Resource Pool Management Configuration Examples for RPM *Mar 1 06:10:35.490: DS0:0:0:0:12 AAA/AUTHOR/RM call-accept (2784758907): found list "default" *Mar 1 06:10:35.494: DS0:0:0:0:12 AAA/AUTHOR/RM call-accept (2784758907): Method=LOCAL *Mar 1 06:10:35.498: DS0:0:0:0:12 AAA/AUTHOR/RM/local (2784758907):Received DNIS=301001 *Mar 1 06:10:35.498: DS0:0:0:0:12 AAA/AUTHOR/RM/local (2784758907):Received CLID=102 *Mar 1 06:10:35.
Configuring Resource Pool Management Configuration Examples for RPM Standard Configuration for RPM Example The following example demonstrates a basic RPM configuration: resource-pool enable resource-pool call treatment resource busy resource-pool call treatment profile no-answer ! resource-pool group resource isdn-ports range limit 46 resource-pool group resource MICA-modems range port 1/0 2/23 ! resource-pool profile customer ACME limit base-size 30 limit overflow-size 10 resource isdn-ports digital resou
Configuring Resource Pool Management Configuration Examples for RPM • The customer profile named “DEFAULT” serves as the default customer profile for speech calls only. If the solution uses an external RPMS server, this same configuration can be used for backup resource pooling if communication is lost between the NAS and the RPMS.
Configuring Resource Pool Management Configuration Examples for RPM no peer default ip address ppp authentication chap ! ! Configure DNIS groups dialer dnis group blot number 5552003 number 3456789 number 2345678 number 1234567 ! dialer dnis group ok number 89898989 number 5551003 ! dialer-list 1 protocol ip permit CLID Discriminator Profile Example The following is a sample configuration of a CLID discriminator.
Configuring Resource Pool Management Configuration Examples for RPM resource-pool profile discriminator baadaaboom call-type digital clid group splat ! ip subnet-zero ! isdn switch-type primary-5ess chat-script dial ABORT BUSY "" AT OK "ATDT \T" TIMEOUT 30 CONNECT \c ! ! mta receive maximum-recipients 0 partition flash 2 8 8 ! ! controller T1 0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 ! controller T1 1 shutdown clock source line secondary 1 ! controller T1 2 shutdown clo
Configuring Resource Pool Management Configuration Examples for RPM interface Serial0 no ip address no ip route-cache no ip mroute-cache shutdown no fair-queue clockrate 2015232 ! interface Serial1 no ip address no ip route-cache no ip mroute-cache shutdown no fair-queue clockrate 2015232 ! interface Serial2 no ip address no ip route-cache no ip mroute-cache shutdown no fair-queue clockrate 2015232 ! interface Serial3 no ip address no ip route-cache no ip mroute-cache shutdown no fair-queue clockrate 20152
Configuring Resource Pool Management Configuration Examples for RPM ! dialer dnis group ok number 89898989 number 4084442002 number 4085552002 number 5551003 ! dialer clid group splat number 12321224 ! ! Configure CLID groups dialer clid group zot number 2121212121 number 4085552002 ! dialer clid group snip number 1212121212 ! dialer clid group stompIt number 4089871234 ! dialer clid group squash number 5656456 dialer-list 1 protocol ip permit ! ! ! line con 0 exec-timeout 0 0 logging synchronous transport
Configuring Resource Pool Management Configuration Examples for RPM resource-pool profile discriminator deny_DNIS call-type digital dnis group bye-bye ! resource-pool profile service gold modem min-speed 33200 max-speed 56000 modulation v90 resource-pool profile service silver modem min-speed 19200 max-speed 33200 modulation v34 ! resource-pool aaa protocol local ! template acme_direct peer default ip address pool tahoe ppp authentication chap isdn-users ppp multilink ! dialer dnis group ACME_dnis_numbers
Configuring Resource Pool Management Configuration Examples for RPM VPDN Load Sharing and Backing Up Between Multiple HGW/LNSs Example Cisco IOS software enables you to balance and back up VPDN sessions across multiple tunnel endpoints (HGW/LNS). When a user or session comes into the NAS/LAC, a VPDN load-balancing algorithm is triggered and applied to the call. The call is then passed to an available HGW/LNS.
Configuring Resource Pool Management Configuration Examples for RPM The following is an example of VPDN load sharing between multiple HGW/LNSs: vpdn enable ! vpdn-group outgoing-2 request dialin protocol l2tp dnis ACME_dnis_numbers local name HQ-NAS initiate-to ip 172.16.1.9 loadsharing ip 172.16.1.9 limit 200 loadsharing ip 172.16.2.17 limit 50 backup ip 172.16.3.
Configuring Wholesale Dial Performance Optimization This chapter describes the Wholesale Dial Performance Optimization feature in the following sections: Note • Wholesale Dial Performance Optimization Feature Overview • How to Configure Automatic Command Execution • How to Configure TCP Clear Performance Optimization • Verifying Configuration of TCP Clear Performance Optimization This task provides inbound and outbound performance optimization for wholesale dial customers who provide ports to Amer
Configuring Wholesale Dial Performance Optimization How to Configure Automatic Command Execution has been implemented by specifying a new autocommand-options telnet-faststream command that, in conjunction with the autocommand telnet command with the /stream option, enables Telnet faststream processing. This capability is also available for TACACS/RADIUS attribute-value pair processing, because this processing uses the autocommand facility.
Configuring Wholesale Dial Performance Optimization Verifying Configuration of TCP Clear Performance Optimization Command Purpose Step 1 Router(config)# line 1/3/00 1/11/143 Selects the lines to be configured and begins line configuration mode. Step 2 Router(config-line)# autocommand telnet-faststream Enables the TCP Clear performance optimization on the selected lines. Verifying Configuration of TCP Clear Performance Optimization To check for correct configuration, use the show line command.
Modem Initialization Strings This appendix provides tables that contain modem initialization strings and sample modem initialization scripts. Table 50 lists required settings, and error compression (EC) and compression settings for specific modem types. Use this information to create your modem scripts. Table 51 lists information for setting AUX ports. SeeTable 52 for a legend of symbols used in these two tables. Sample scripts follow the tables.
Table 50 Required Settings and EC/Compression Settings (continued) Settings Required for All Modems Settings for EC/Compression Modem LOCK DTE Speed Best Error Best Comp No Error No Comp AA CD DTR RTS/CTS Flow Motorola UDS &F FastTalk II S0=1 &C1 &D3 \Q3 \J0 \N6 %C1 \N0 %C0 Multitech MT1432 MT932 &F S0=1 &C1 &D3 &E4 $BA0 &E1 &E15 &E0 &E14 Digicom Scout Plus &F S0=1 &C1 &D3 *F3 *S1 *E9 <--- *E0 <--- Digicom SoftModem &F S0=1 &C1 &D3 &K3 ---> \N5 %C1 \N0
Table 51 AUX and Platform Specific Settings Settings for Use with AUX Port Other Settings Modem No Echo No Res CAB-MDCE Write Memory Codex 3260 E0 Q1 &S1 &W USR Courieræ E0 USR Sportster Q1 *NA* &W Global Village E0 Teleport Gold Q1 *NA* &W Telebit E0 T1600/T3000/ WB Q1 &S4 &W Telebit E0 T2500 (ECM) Q1 &S1 &W All Telebit modems need to have the speed set explicitly. These examples use 38400 bps.
Sample Modem Scripts Table 51 AUX and Platform Specific Settings (continued) Settings for Use with AUX Port Other Settings Modem No Echo No Res CAB-MDCE Write Memory Intel External E0 Q1 *NA* &W Practical Peripherals E0 Q1 *NA* &W Comments Based on PC288LCD. May vary. Table 52 contains a legend of symbols used in Table 50 and Table 51. Table 52 Legend to Symbols Used in Modem Chart Symbol Meaning *NA* This option is not available on the noted modem.
Sample Modem Scripts AT&T ComSphere 3800 Series (V.42bis) Init=AT&FX6&C1&D2\N5\Q2%C1"H3S7=60S0=1&W Speed=57600 AT&T DataPort Fax Modem (V.42bis) Init=AT&FX6&C1&D2\N7\Q2%C1S7=60S0=1&W Speed=38400 Boca Modem 14.4K/V.32bis (V.
Sample Modem Scripts Everex EverFax 24/96 and 24/96E (MNP 5) Init=AT&F&C1&D3\J0\N3\Q2\V1%C1S7=60S0=1&W Speed=9600 Everex Evercom 96+ and 96E+ (V.42bis) Init=AT&FW2&C1&D3\J0\N3\Q2\V2%C1S7=60S0=1&W Speed=38400 Freedom Series V.
Sample Modem Scripts Hayes ACCURA 24 EC (V.42bis) Init=AT&FW2&C1&D3&K3&Q5S7=60S36=7S46=138S48=7S95=47S0=1&W Hayes ACCURA 96 EC (V.42bis) Init=AT&FW2&C1&D3&K3&Q5S7=60S36=7S46=138S48=7S95=47S0=1&W Speed=38400 Hayes ACCURA 144 EC (V.42bis) Init=AT&FW2&C1&D3&K3&Q5S7=60S36=7S46=138S48=7S95=47S0=1&W Speed=57600 Hayes ISDN System Adapter Init=AT&FW1&C1&D3&K3&Q0S7=60S0=1&W Speed=57600 IBM 7855 Modem Model 10 (MNP) Init=AT&F&C1&D3\N3\Q2\V1%C1S7=60S0=1&W IBM Data/Fax Modem PCMCIA (V.
Sample Modem Scripts Megahertz T324FM internal (V.42bis) Init=AT&F&C1&D3%C1\J0\N3\Q2\V1S7=60S46=138S48=7S0=1&W Speed=9600 Megahertz P2144 FAX/Modem (V.42bis) Init=AT&F&C1&D3%C1\J0\N7\Q2\V2S7=60S0=1&W Speed=38400 Megahertz T396FM internal (V.42bis) Init=AT&FW2&C1&D3%C1\J0\N7\Q2\V2S7=60S0=1&W Speed=38400 Megahertz CC3144 PCMCIA card modem (V.
Sample Modem Scripts Microcom DeskPorte FAST Init=ATX4S7=60-M1\V4\N2L1S0=1&W Speed=57600 Motorola/Codex 3220 (MNP) Init=AT&F&C1&D3*DC1*FL3*MF0*SM3*XC2S7=60S0=1&W Motorola/Codex 3220 Plus (V.42bis) Init=AT&F&C1&D3*DC1*EC0*MF0*SM3*XC2S7=60S0=1&W Speed=38400 Motorola/Codex 326X Series (V.42bis) Init=AT&F&C1&D3*FL3*MF0*SM3*TT2*XC2S7=60S0=1&W Speed=38400 MultiTech MultiModem V32EC (V.42bis) Init=AT&FX4&C1&D3$BA0&E1&E4&E15#L0S7=60S0=1&W Speed=38400 MultiTech MultiModem V32 (no MNP or V.
Sample Modem Scripts Prometheus ProModem 9600 Plus (V.42) Init=AT&F&C1&D3*E7*F3S7=60S0=1&W Prometheus ProModem Ultima (V.42bis) Init=AT&F&C1&D3*E9*F3*N6*S1S7=60S0=1&W Speed=38400 Racal Datacomm ALM 3223 (V.42bis) Init=AT&F&C1&D3\M0\N3\P2\Q1\V1S7=60S0=1&W Speed=38400 Supra FAXModem V.32bis (V.42bis) Init=AT&FN1W2&C1&D1&K3&Q5\N3%C1S7=60S36=7S48=7S95=45S0=1&W Speed=57600 Telebit T1600 (V.42bis) Init=AT&FX2&C1&D3&R3S7=60S51=6S58=0S59=15S68=2S180=2S190=1S0=1&W Speed=38400 Telebit T2500 (V.
Sample Modem Scripts Universal Data Systems V.3227 (V.42bis) Init=AT&F&C1&D2\J0\M0\N7\Q2%C1S7=60S0=1&W Speed=38400 Universal Data Systems V.3229 (V.42bis) Init=AT&F&C1&D3\J0\M0\N7\Q2%C1S7=60S0=1&W Speed=38400 US Robotics Sportster 9600 (V.42bis) Init=AT&FX4&A3&B1&D3&H1&I0&K1&M4S7=60S0=1&W Speed=38400 US Robotics Sportster 14400 (V.42bis) Init=AT&FX4&A3&B1&D3&H1&I0&K1&M4S7=60S0=1&W Speed=57600 US Robotics Sportster 14400 (V.
Sample Modem Scripts Ven-Tel PCM 9600 Plus (MNP) Init=AT&FB0&C1&D3\N3\Q3%B0%C1%F1S7=60S0=1&W ViVa 9642e (V.42bis) Init=AT&F&C1&D3&K3&Q5\N3%C3S7=60S36=7S46=138S48=7S95=47S0=1&W Speed=38400 ViVa 14.4/FAX (V.42bis) Init=AT&F&C1&D3&K3&Q5\N3%C3S7=60S36=7S46=138S48=7S95=47S0=1&W Speed=38400 ZOOM V.32 turbo (V.42bis) Init=AT&FW1&C1&D3&K3&Q5%C1\N3S7=60S36=7S46=138S48=7S95=47S0=1&W Speed=38400 ZOOM V.32bis (V.42bis) Init=AT&FW1&C1&D3&K3&Q9%C1\N3S7=60S36=7S95=47S0=1&W Speed=38400 Zyxel U-1496 (V.
Index
I N D EX outgoing calls, configuring Symbols access-list command xlix ? command DC-260, DC-361 DC-260, DC-346, DC-350 access lists xlviii DDR DECnet IP A DC-349, DC-362 DC-347 packets, interesting AAA (authentication, authorization, and accounting) large-scale dial-out network security services preauthentication overview DC-664 VINES AAA configuration (example) DC-350 DC-351 dialer profiles DC-490, DC-493 virtual template configuration (example) DC-346 DC-349 dialer groups virt
Index delimiter, configuring ISDN subscription service DC-272 ANI/DNIS Delimiter for CAS Calls on CT1 feature DC-272 See also ISDN, Advice of Charge AOL (America Online), wholesale dial performance optimization DC-758 AO/DI (Always On/Dynamic ISDN) BACP and BAP negotiation BACP default settings called number prefix AppleTalk DC-234 DDR, configuring DC-238 PPP, configuring DC-238 clients DC-237 configuring DC-240 interface configuration DC-595 appletalk client-mode command DC-567 automati
Index group and member (examples) IPX loopback interfaces DC-677 B DC-563 modem configuration (examples) monitoring DC-76 backup delay command DC-37 DC-42 routing configuration (example) DC-564 dialer profiles overview DC-41 DC-24 DC-31 async mode interactive command DC-31, DC-568 DC-289 ATCP (AppleTalk Control Protocol) autocommand command DC-527 dialer interfaces only DC-650 DC-658 autodetect encapsulation command default passive mode DC-760 DC-196, DC-198, DC-260 DC-160 autosel
Index virtual template interface (example) PPP bandwidth allocation control, configuring prerequisites authentication DC-656 DC-652 temporary dialer maps clients DC-654 DC-630 callback forced-wait command DC-651 bandwidth on demand, load threshold bandwidths, configuring optimal DC-365, DC-395 DC-58 analog robbed-bit signaling SLIP-PPP tokens DC-253 channel-associated signaling DC-574 SLIP-PPP (example) DC-630, DC-631, DC-632 calls analog modem DC-33 banners circuit-switched digital
Index common forms of cas-group command channels DC-272 ISDN 2 B + D DC-277, DC-736 cas-group timeslots command BRI DC-271 cause codes logical relationship PRI See ISDN, cause codes undefined AAA/TACACS+ list usage in text DC-12 challenge packet DC-584 DC-583 encrypted password (examples) xlii virtual template interface erroneous routing changed information in this release DC-624 PAP authentication order chat-script command xli channelized E1 DC-607 DC-584 DC-164, DC-630 chat scrip
Index TCP Clear performance optimization DC-759 Cisco Easy IP virtual access interfaces address strategy virtual profiles DC-767 async interface configuration (examples) business applications configuring DC-469 Combinet dedicated network interfaces, configuring DC-467 interactive sessions, configuring DC-767 dynamic NAT translation timeout period ISDN BRI configuration (examples) LAN interfaces, configuring DC-468 DC-468 understanding xlvii to xlviii commands default form, using dialer
Index SLIP IPX, configuring DC-570 TCP ISDN PRI configuration (example) connection attempt time, configuring controller e1 command DC-572 E1, description DC-10 T1, description DC-10 controller t1 command DC-291 DC-350 DC-660 routed protocols DC-344, DC-346, DC-357, DC-360 snapshot routing DC-433 See also snapshot routing DC-256, DC-276 CSU loopbacks AT&T specification ISO CLNS, configuring large-scale dial-out DC-255, DC-271 controllers latched DC-348 transparent bridging DC-345
Index debug trunk cas port timeslots command DC-743 ISDN channels DC-444 debug udptn command DC-46 load threshold exceeded (examples) debug vpdn commands DC-536 load threshold reached (examples) debug vpdn event command debug vpdn l2x command DC-537, DC-735 serial interfaces DC-735 debug vpdn l2x-events command debug vtemplate command primary line down (examples) DC-537, DC-538 DC-444 DC-445 DC-440 to DC-445 See also Dialer Watch dialer aaa command DC-488 DC-444 DC-665 DECnet diale
Index BRI, configuring single BRIs in rotary group idle timers physical interfaces DC-598 reserved channel DC-599 dialer load threshold command DC-234, DC-236, DC-365, DC-396, DC-597, DC-598, DC-599 DC-416, DC-434 DC-204, DC-235, DC-359, DC-636, DC-637, DC-640, DC-642, DC-651 dialer map modem-script system-script command DC-361, DC-182, DC-187, DC-260 dialer map name speed command DC-182, DC-260 dialer maps, large-scale dial-out and dialer map snapshot command DC-661 configuring IPX, config
Index bandwidth on demand load threshold interface priority DC-395, DC-426 dial-peer cor list command DC-364 interfaces dial peers, description assignment priority leader DC-323 remote configuration DC-418, DC-447 dialer string command DC-235, DC-359, DC-388, DC-391, DC-468, DC-640, DC-642 dialer wait-for-carrier-time command DC-364, DC-394, DC-419, DC-467, DC-642, DC-643, DC-653 DC-122 shelf IDs, configuring DC-115 dial-tdm-clock priority command digital modem network modules disconnect ti
Index architecture (figure) overview endpoint discriminator, changing MLP default DC-114 enterprise networks DC-114 troubleshooting DC-601 dial access scalability DC-123 DTR (data terminal ready), modem control and dynamic addressing, configuring dial access scenarios DC-156 DC-771 DC-770 to DC-809, DC-813 escape characters, modem chat strings DC-41 Dynamic Multiple Encapsulations feature DC-175 exec command DC-164 DC-30 EXEC process E disabling DC-29 enabling DC-29 exec-timeout c
Index framing crc4 command framing esf command configuration options DC-255, DC-271 configuring DC-256 DC-4, DC-55 logical constructs MLP G DC-5, DC-56 DC-597 compared to lines Germany, ISDN semipermanent connection support DC-182 DDR priority global configuration mode, summary of dialer group-range command DC-5, DC-56 DC-4, DC-55 DC-399 dial backup dialer profiles xlviii DC-38, DC-56, DC-57 DC-7, DC-416 configuring DC-418, DC-419 description of DC-7 downtime, enabling H hairpin
Index global default mechanism interfaces supported DC-590 local address pooling ip nat inside command DC-592 peer address allocation methods per-interface options precedence rules IP multicast routing, asynchronous serial traffic over UDP DC-44 DC-591 to DC-592 ip nat outside command DC-589 IP–PPP, enabling DC-592 broadcasts, asynchronous serial traffic over UDP DC-44 ip tos reflect command DC-766 remote LAN DC-766 DC-572 DC-33, DC-572 DC-572 DC-527 ip unnumbered command DC-31 ip u
Index ipx watchdog-spoof command DC-348, DC-423 ISDN dynamic multiple DC-429 interfaces 128 kbps leased-line service (example) monitoring TEI DC-193 configuring DC-261 LAPB-TA asynchronous traffic DC-188 interface characteristics Advice of Charge DC-310 leased-line service in Germany and Japan DC-188 multiple switch types DC-309 to DC-310 BRI and dialer profiles (example) DC-318 configuration (example) DC-190 DC-310 PRI interfaces, configuring destination DC-309 restrictions dia
Index special signaling overview DC-202 (examples) verifying DC-206 DC-317 troubleshooting subaddress MTU size DC-317 network address, configuring DC-360, DC-387 subaddress binding DC-178 network module DC-186 isdn all-incoming-calls-v120 command DC-196 DC-201 North American switch configuration isdn answer1 command DC-184, DC-205 point-to-multipoint service isdn answer2 command DC-184 point-to-point service isdn bchan-number-order command DC-182 DC-173 DC-173 semipermanent co
Index legacy DDR DDR configuration (example) callback actions configuring overview slot and port numbering DC-641 class of restrictions DC-642 configuring DC-641 prerequisites legacy DDR DC-642 DC-184, DC-205, DC-261 isdn disconnect-cause command isdn guard-timer command DC-205, DC-637 isdn incoming-voice modem command DC-205, DC-247, DC-262 DC-259 configuration (example) DC-200 encapsulation autodetection DC-198 DC-197 isdn leased-line bri 128 command isdn leased-line bri command D
Index isdn t306 command DC-324 reverse DNS, configuring isdn t310 command DC-324 scalable dial-out service isdn tei command DC-187 isdn x25 dchannel command DC-224 isdn x25 static-tei command DC-224 user profiles (example) ISO CLNS (ISO Connectionless Network Service), DDR configuring DC-665 stack group and static route download configuration (example) DC-671 DC-186 isdn v110 padding command access groups DC-661 SGBP dial-out connection bidding, configuring DC-183, DC-261 isdn v110 on
Index ISDN interfaces, enabling ISO CLNS (example) LAPB (example) DC-375, DC-404 multiple destinations (example) DC-407 DC-409 timers, enabling DC-392 DC-364 passive interface DC-401 DC-399 XNS (example) DC-413 DC-404 ISDN caller ID callback protocol access control spoke configuration (examples) DC-362 DC-647 DTR dialing (example) encapsulation DC-368 DC-642 ISDN NFAS primary D-channel non-V.
Index leased serial (example) looped-back MICA In-Band Framing Mode Control Messages feature DC-93 DC-428 DC-582 modem chat scripts, activating for modems, disabling MLP (Multilink Point-to-Point Protocol) DC-165 (example) DC-103 NM-8AM and NM-16AM analog modem leased line support DC-77 timeout interval, configuring tty DC-15 types, description of DC-15 load threshold, dialer rotary local name command See also BACP DC-605 caller ID authentication DC-598 configuration (example) DC-190 con
Index Stacker compression modem busyout threshold command DC-192 virtual profiles modem callin command cloning sequence (table) interoperability See modems, connections DC-601 MMP (Multichassis Multilink PPP) bundle modem country mica command call handling and bidding modem cts-required command DC-620 configuration requirements modem dialin command DC-621 dialer explicitly defined (example) DC-625 dialer not explicitly defined (example) dialer not used (example) interfaces supported DC-6
Index dial-in (example) rejecting by type (example) DC-85 dial-in and dial-out (example) network topology restrictions DC-87 inoperable DC-85 virtual partitioning DC-101 ISDN, use over DC-62, DC-75 DC-201 See also ISDN BRI DC-89 dial-in (example) DC-89 network topology DC-89 modem recovery-time command line configuration continuous CTS (figure) DC-159 incoming and outgoing calls (figure) DC-101 modems modem call-in (figure) AUX (table) chat scripts DC-103 connections data compre
Index modem shutdown command dialer interface, defining DC-101, DC-103 modem status-poll command Easy IP DC-95 modes DC-467 DC-464 LAN interface, defining See command modes NAT pool, defining Monitoring Resource Availability on Cisco AS5300, AS5400, and AS5800 Universal Access Servers feature DC-103 MPPE encryption MS Callback remote clients over PPP DC-571 alternate route index DC-498 configuring LCP callback option multicasts, asynchronous serial traffic over UDP DC-314 NTT PRI DC-
Index PAP (Password Authentication Protocol) authentication request VPN PIAFS (Personal-Handyphone-System Internet Access Forum Standard) DC-584 CHAP authentication order DC-584 peer default ip address command DC-32, DC-593 peer default ip address pool command DC-593 peer default ip address pool dhcp command peer neighbor-route command DC-526 DC-593 DC-594 configuring DC-315 description DC-314 PIAFS Wireless Data Protocol for MICA Modems feature DC-314 platforms, supported per-user confi
Index lossless data Microsoft SLIP BOOTP requests DC-586 telecommuting configuration (example) DC-587 platform support software virtual terminal lines DC-587 ppp authentication command encapsulations interfaces, configuring ppp bap call accept command DC-361, DC-392 ppp bap call request command address negotiation address pooling DC-589 ppp bap drop after-retries command DC-654 ppp bap link types analog command DC-653, DC-654 ppp bap max dialers command IPX DC-566 DC-565 header compre
Index ppp multilink group command DC-605 ppp multilink idle-link command ppp quality command R DC-233, DC-237, DC-239 R1 modified signaling, configuring DC-586 ppp reliable-link command ppp use-tacacs command R2 signaling DC-594 pptp flow-control receive-window command pptp flow-control static-rtt command pptp tunnel echo command DC-522 Preauthentication with ISDN PRI feature DC-263 DC-255, DC-257 DC-312 servers privileged EXEC mode, summary of DC-680 radius-server host command DC-682 r
Index VPDN dial rotary groups DC-765 request dialin command request-dialout command resource command configuring DC-522 dialer DC-524 DC-357 route cache invalidation, configuring DC-727 resource-pool aaa protocol command resource-pool call treatment profile command DC-727 DC-722 resource-pool call treatment resource command resource-pool enable command DC-722 dedicated dial-in (example) IGRP dial-in (example) DC-727, DC-730, DC-734 DC-43 default DC-30 DC-30 DDR, supported protocols
Index profiles line delay backup customer DC-704 default customer DC-704 resource group manager resource groups resource services server connections DC-742 PPP SLIP session limits TACACS troubleshooting DC-680 DC-684 service exec-callback command service internal command DC-705 large-scale dial VPDN groups DC-732 description DC-707 responsibility DC-743 DC-724 RMP, relationship to troubleshooting DC-780 set 2 number command DC-780 DC-780 set bridging off command RPMS (Resource
Index set remoteaccess protected command set systemname command DC-776, DC-780 DC-776 set user nas command DC-776, DC-780 sgbp dial-bids command DC-622, DC-663 DC-622 sgbp seed-bid command DC-626 sgbp seed-bid offload command DC-626 show appletalk traffic command DC-370, DC-400, DC-426 show async bootp command DC-20 show async status command DC-20 DC-178, DC-202 show caller command show controllers bri command DC-189, DC-268, DC-333 show controllers e1 command DC-267, DC-332 show con
Index show resource-pool vpdn group command DC-734 show resource-pool vpdn profile command show run command show sgbp command robbed-bit DC-436 defined DC-140 show spe digital summary command DC-123, DC-124, DC-141 show spe modem speed command show spe version command DC-142 DC-370, DC-400, DC-426 DC-574 server connections DC-735 DC-535 DC-370, DC-400, DC-426 telecommuting configuration (example) snapshot client command monitoring overview signaling DC-433 to DC-437 DC-253 E1 R2 DC-43
Index source template command SPE (Service Processing Element) country code 56K and modem calls (example) call processing components DC-140 download maintenance configuration (example) DC-138 description DC-66, DC-126, DC-131 country name, specifying firmware statistics prerequisites DC-139 verifying restrictions viewing reboot ISDN NFAS DC-178 DC-256 North American ISDN DC-139 voice systems DC-133 troubleshooting verifying DC-173, DC-254 DC-177 T DC-137 DC-136 T1 voice channels
Index tcpdump interfaces, configuring DC-106 TCP header compression legacy DDR, access (example) transport command See TCP/IP, header compression TEI (terminal endpoint identifier), ISDN interfaces transport input command DC-183 transport output command (example) DC-290 traps (example) defaults DC-261 DC-103 (example) DC-106 telecommuting configuration (example) DC-563 Telnet connection, queued request trunk group (global) command DC-327 DC-327 (example) configuring DC-24 DC-15 nu
Index interoperations, legacy DDR V DC-479 MLP V.110 modem calls, selective filtering of incoming DC-186 V.120 Modem Standard cloning sequence (table) configuration requirements DC-65 interoperations V.
Index VPN, configuring Virtual Template Interface Service feature DC-473 topology voluntary tunneling configuration (example) See VPDN groups; VPDN profiles; VPN dialers, configuring vpdn enable command DC-518 vpdn-group command DC-522, DC-734, DC-735 VPDN groups, description vpdn history failure table-size command vpdn profile command L2TP DC-707 DC-530 DC-538 hardware terminology DC-496 vpdn session-limit command DC-528 DC-527 debug output definition DC-496, DC-564 (example) AAA
Index definition mapping protocol address to remote host DC-496 dial-in, configuring networks, PPP calls over DC-523 (example) x25 address command DC-557 x25 aodi command tunnel session limit, configuring tunnel shutdown DC-528 x25 htc command DC-528 x25 map command tunnel soft shutdown, configuring verifying DC-529 x25 win command DC-523 x25 wout command VPDN MIB and Syslog Facility event logging, configuring supported objects DDR, configuring DC-496 DC-530 DC-511 VPN subgroup comman
