Cisco AS5x00 Case Study for Basic IP Modem Services 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 SECTION 1 Network Design and Case Study Overview Introduction 1-1 1-1 Scenario Description 1-1 Dial Planning Questionnaire Network Service Definition 1-3 1-5 Network Topology, Hardware, and Software Selection Configuration Design Parameters 1-8 Deployment and Operation Task Strategy SECTION 2 1-12 Commissioning the Cisco AS5300 Hardware In this Section 1-7 2-1 2-1 Understanding the Basic Hardware Architecture Task 1. Verifying Basic Setup 2-1 2-3 1.
Contents SECTION 3 Commissioning the Cisco AS5800 Hardware In this Section 3-1 3-1 Understanding the Basic Hardware Architecture 3-1 The Cisco 7206 Router Shelf and the Cisco DS5814 Dial Shelf Call-Processing Components Task 1. Verifying Basic Setup 3-2 3-3 3-5 1.1 Analyzing the System Boot Dialog 1.2 Matching the Cisco IOS Images 1.3 Inspecting the Dial Shelf 3-6 3-9 3-11 DSC Troubleshooting Tips 3-11 Feature Board Troubleshooting Tips 1.4 Understanding DSIP Commands 3-13 3-14 1.
Contents SECTION 4 Verifying Modem Performance In this Section 4-1 4-1 Background on Asynchronous Data Communications Async DataComm Model 4-1 4-2 Logical Packet and Circuit Components of a NAS RS-232 in Cisco IOS 4-4 Cisco IOS Line-Side Inspection 4-6 Understanding Modem Modulation Standards V.34 Basic Rules 4-8 V.90 Basic Rules 4-9 4-8 Task 1. Initiating a Modem Loopback Test Call 4-10 Task 2. Initiating and Inspecting a V.
Contents SECTION 6 Modem Management Operations In this Section 6-1 6-1 Task 1. Managing Modem Firmware 6-2 1.1 Inspecting Modem Firmware 6-2 1.2 Upgrading Modem Firmware 6-6 Task 2. Configuring Modems Using Modem Autoconfigure 2.1 Basic Rules for Modem Autoconfigure 6-11 2.2 Modem Autoconfigure K56Flex Example Task 3. Gathering and Viewing Call Statistics 3.1 Using the Cisco IOS EXEC (CLI) 3.2 Using Modem Call-Record Terse 3.
S E C T I O N 1 Network Design and Case Study Overview Introduction This case study describes how two companies set up basic modem IP services by using Cisco AS5x00 network access servers. The two companies Plan and design a basic IP modem dial-up network. Deploy networking equipment by configuring, verifying, and troubleshooting the Cisco IOS. Prepare for operations by inspecting modem call statistics and enabling basic management protocols.
Section 1 Scenario Description Network Design and Case Study Overview Both companies Enable remote modem users to access IP backbone resources through the public switched telephone network (PSTN). Build an access network foundation that scales to support larger dial implementations for the future. Have almost identical technology requirements and business applications. Therefore, one business scenario diagram is shown for both companies. Figure 1-1 shows the business scenario.
Section 1 Network Design and Case Study Overview Dial Planning Questionnaire Dial Planning Questionnaire Both companies answer a planning questionnaire. Based on their design choices, both companies create a network-service definition.
Section 1 Dial Planning Questionnaire Table 1-1 Network Design and Case Study Overview Dial Services Questionnaire (continued) Design Questions Design Options Maui Onions Design Choices THEnets Design Choices Yes Yes Yes Yes No No EXEC shell sessions PPP sessions SLIP sessions Will you support multilink? If yes, will you scale to a stacked multi-chassis solution? Yes or No No Yes. A stacked solution.
Section 1 Network Design and Case Study Overview Network Service Definition Network Service Definition Based on the design choices in Table 1-1, each company creates its own network-to-user service definition. Table 1-2 provides the definition for each company.
Section 1 Network Service Definition Network Design and Case Study Overview The network service definition for each company is different: 1-6 Maui Onions’ scaling projections are much smaller than THEnet’s projections. For this reason, THEnet requires higher density network access servers (that is, THEnet requires a Cisco AS5800 instead of a Cisco AS5300). Maui Onions cares more about security and less about billing. THEnet cares more about billing and less about security.
Section 1 Network Design and Case Study Overview Network Topology, Hardware, and Software Selection Network Topology, Hardware, and Software Selection Figure 1-3 shows the devices that are used to build both dial-up access environments. One recommended topology is used for both companies.
Section 1 Configuration Design Parameters Table 1-1 Network Design and Case Study Overview Hardware Elements (continued) Element Purpose Maui Onions THEnet Default gateway To forward packets to the IP intranet and Internet. Router Router Internet firewall To protect the IP intranet from intruders and hackers. Cisco PIX Cisco PIX Edge router To provide connectivity between the access subnet and the IP backbone. Router Router 1. Network Time Protocol 2. System logs (logging) 3.
Section 1 Network Design and Case Study Overview Figure 1-4 Configuration Design Parameters IP Subnetting Diagram Hq-access 172.22.66.0/26 PSTN NAS loopbacks 172.22.90.0/24 172.22.99.0/24 Clients IP intranet Modems Internet Note This case study uses private RFC 1918 IP addresses. For more information, refer to the following URL: http://www.ietf.org/rfc/rfc1918.
Section 1 Configuration Design Parameters Table 1-5 Network Design and Case Study Overview IP Subnetting Plan Network Name Assigned Subnet Description NAS loopback 0 172.22.99.0/24 Identifies the router with a unique and stable IP address for network management purposes. One IP address from a common address block is assigned to each network device. This technique enables the network operations center (NOC) to more easily perform security filtering.
Section 1 Network Design and Case Study Overview Table 1-6 Configuration Design Parameters Device Parameters Device Parameters Router host names 5300-NAS 5800-NAS Interface ethernet 0 172.22.66.23 255.255.255.0 Interface loopback 0 172.22.99.1 255.255.255.255 Interface loopback 1 172.22.90.1 255.255.255.0 IP local address pool 5300-NAS = 172.22.90.2 through 172.22.90.97 5800-NAS = 172.22.90.2 through 172.22.90.254 Primary and secondary name servers 172.22.11.10 172.22.12.
Section 1 Deployment and Operation Task Strategy Table 1-7 Network Design and Case Study Overview Dial Plan (continued) Item Value Description Test call login username = dude password = dude-pw Username password for sending test calls into the NAS. Deployment and Operation Task Strategy Table 1-8 describes the deployment and operation task strategy used in this case study. Maui Onions and THEnet use a common strategy.
Section 1 Network Design and Case Study Overview Table 1-8 Deployment and Operation Task Strategy Deployment and Operation Task Strategy (continued) Section Task Description 7 Enabling Management Protocols: NTP, SNMP, and Syslog Enabling the following management protocols as part of commissioning a dial access service: 8 NTP SNMP Syslog Inspecting the Final Running Configuration Referencing and editing full-function for the Cisco AS5300 and AS5800 Cisco IOS NAS configurations.
Deployment and Operation Task Strategy 1-14 Section 1 Network Design and Case Study Overview Cisco AS5x00 Case Study for Basic IP Modem Services 11/24/1999
S E C T I O N 2 Commissioning the Cisco AS5300 Hardware In this Section This section describes how to configure Cisco AS5300 to support terminal EXEC shell services and login prompts for client modems. The following sub sections are provided: Understanding the Basic Hardware Architecture Task 1. Verifying Basic Setup Task 2. Configuring Cisco IOS Basics Task 3. Enabling the T1 Controllers Task 4. Configuring the Serial Interfaces Task 5. Configuring Modems and Lines Task 6.
Section 2 Understanding the Basic Hardware Architecture Figure 2-1 Commissioning the Cisco AS5300 Hardware Cisco AS5300 Basic System Architecture Inside a Cisco network access server IP network Routing and switching engine Group-async interface Dialer interface controlling the D channels Cloning Asynchronous interfaces Cloning TTY lines Serial interface channels S0:1, S0:2… Modems TDM bus T1 controllers PRI lines PSTN POTS line Client PC BRI line Client modem ISDN router Client PC Lege
Section 2 Commissioning the Cisco AS5300 Hardware Verifying Basic Setup Figure 2-1 shows the following: Client modems and ISDN routers dial into the access server through the PSTN. Analog PPP calls connect to modems inside the access server. Each modem inside the access server provides a corresponding TTY line and asynchronous interface for terminating character and packet mode services. Asynchronous interfaces clone their configurations from a group-async interface.
Section 2 Verifying Basic Setup Commissioning the Cisco AS5300 Hardware program load complete, entry point: 0x80008000, size: 0x45497c Self decompressing the image : ################################################# ################################################################################ ################################################################################ ################################################################################ ##################################################
Section 2 Commissioning the Cisco AS5300 Hardware Verifying Basic Setup http://cco-sj-1.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi --- System Configuration Dialog --Would you like to enter the initial configuration dialog? [yes/no]: no Event 3—Because the NAS has never been configured, the NAS cannot find a startup-config file. Therefore, the software asks, “Would you like to enter the initial configuration dialog? [yes/no]:” Enter no.
Section 2 Verifying Basic Setup Commissioning the Cisco AS5300 Hardware Primary Rate ISDN software, Version 1.1. Backplane revision 2 Manufacture Cookie Info: EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30, Board Hardware Version 1.64, Item Number 800-2544-2, Board Revision B0, Serial Number 11811596, PLD/ISP Version 0.0, Manufacture Date 9-Dec-1998. 1 Ethernet/IEEE 802.3 interface(s) 1 FastEthernet/IEEE 802.
Section 2 Commissioning the Cisco AS5300 Hardware Verifying Basic Setup ! controller T1 2 clock source internal ! controller T1 3 clock source internal ! interface Ethernet0 no ip address shutdown ! interface FastEthernet0 no ip address shutdown ! ip classless ! line con 0 transport input none line 1 96 line aux 0 line vty 0 4 ! end 1.3 Exploring the Cisco IOS File System Get familiar with the file system and memory storage areas.
Section 2 Verifying Basic Setup Commissioning the Cisco AS5300 Hardware Figure 2-2 shows the memory locations inside the Cisco AS5300. Figure 2-2 AS5300 Memory Locations CPU (R4700) System Flash memory Processor memory Boot Flash memory Pocket I/O memory NVRAM memory 23817 Inside a Cisco network access server Table 2-2 describes the memory locations shown in Figure 2-2. Table 2-2 Memory Location Descriptions Component Description R4700 CPU RISC 4700 central processing unit.
Section 2 Commissioning the Cisco AS5300 Hardware Verifying Basic Setup To inspect the file system, enter the show file systems command and dir comand as shown in the following bullet list: View the different file storage areas and file management functions: Router#show file systems File Systems: Size(b) 16777216 8388608 126968 - * Free(b) 12236072 7382416 126968 - Type opaque opaque opaque network flash flash nvram opaque network network Flags wo rw rw rw rw rw rw wo rw rw Prefixes modem: null:
Section 2 Verifying Basic Setup Commissioning the Cisco AS5300 Hardware Inspect the NVRAM directory: Router#dir nvram: Directory of nvram:/ 1 2 -rw---- 0 0 startup-config private-config 126968 bytes total (126968 bytes free) In the example, two files are present: startup-config and private-config. The private-config is a secure file that is part of the startup configuration. It supports encryption technologies, but it is not user accessible. 1.
Section 2 Commissioning the Cisco AS5300 Hardware Verifying Basic Setup 1.5 Inspecting CPU Utilization Enter the show processes cpu command to investigate high CPU utilization. High utilization causes network performance problems. For example, knowing when the router is running at over 50% utilization is critical. The router might start dropping packets if an unexpected traffic burst comes through or if OSPF gets recalculated. Fast switching reduces CPU utilization.
Section 2 Configuring Cisco IOS Basics Commissioning the Cisco AS5300 Hardware Task 2. Configuring Cisco IOS Basics The following subsections detail the tasks required to apply a basic-running configuration to the NAS: Tech Tip 2.1 Configuring the Host Name, Enable Secret, and Time Stamps 2.2 Configuring Local AAA Security 2.3 Setting Up a Login Banner 2.4 Configuring the Loopback Interfaces, Ethernet Interface, and IP Route 2.
Section 2 Commissioning the Cisco AS5300 Hardware Configuring Cisco IOS Basics 2.2 Configuring Local AAA Security Configure authentication, authorization, and accounting (AAA) to perform login authentication by using the local username database. The login keyword authenticates EXEC shell users. Additionally, configure PPP authentication to use the local database if the session was not already authenticated by login. AAA (called triple A) is the Cisco IOS security model used on all Cisco devices.
Configuring Cisco IOS Basics Step 3 Section 2 Commissioning the Cisco AS5300 Hardware Log in with your username and password: 5300-NAS#login User Access Verification Username:admin Password: 5300-NAS# Successfully logging in means that your local username will work on any TTY or VTY line. Do not disconnect your session until you can log in. 2.3 Setting Up a Login Banner Create a login banner.
Section 2 Commissioning the Cisco AS5300 Hardware Configuring Cisco IOS Basics 2.4 Configuring the Loopback Interfaces, Ethernet Interface, and IP Route To commission a basic dial access service: Step 1 Create two loopback interfaces Bring up the ethernet interface Add an IP route to the default gateway Assign the IP addresses, and create an IP route to the default gateway: ! interface Loopback0 ip address 172.22.99.1 255.255.255.255 ! interface Loopback1 ip address 172.22.90.1 255.255.255.
Section 2 Configuring Cisco IOS Basics Commissioning the Cisco AS5300 Hardware 2.5 Upgrading to a New Cisco IOS Release Obtain new Cisco IOS features and more stable code by upgrading to a new Cisco IOS release. Step 1 Display the contents of Flash memory: 5300-NAS#cd flash: 5300-NAS#dir Directory of flash:/ 1 -rw- 4541080 c5300-is-mz.113-7.AA 16777216 bytes total (12236072 bytes free) 5300-NAS# Step 2 Timesaver Copy the new image from the remote TFTP server into Flash memory.
Section 2 Commissioning the Cisco AS5300 Hardware Warning Step 3 Configuring Cisco IOS Basics Occasionally TFTP errors will occur. Make sure the verifying checksum reports OK. Do not reload the access server if the checksum reports errors. Verify that the old image was erased and the new image was downloaded. In this example, notice that the 12.0(5)T image is larger than the old 11.3(7)AA image. 5300-NAS#dir flash: Directory of flash:/ 1 -rw- 5633184 c5300-is-mz.120-5.
Section 2 Enabling the T1 Controllers Commissioning the Cisco AS5300 Hardware Task 3. Enabling the T1 Controllers Specify the settings for the T1 controllers. T1 controller settings must match the settings on the telephone switch side. Mismatched settings cause problems that may not be detected for a long time.
Section 2 Commissioning the Cisco AS5300 Hardware Enabling the T1 Controllers ! controller T1 3 framing esf linecode b8zs pri-group timeslots 1-24 ! Table 2-4 describes some of the T1-controller concepts that are applied in the previous example. Table 2-4 T1 Controller Concepts and Descriptions Concept Description Framing type Defines the control bits and data bits. Cisco supports super frame (SF) and extended super frame (ESF) for T1s. ESF—Extended super frame.
Section 2 Enabling the T1 Controllers Step 3 Commissioning the Cisco AS5300 Hardware Verify that the controllers are up and no alarms or errors are detected. Error counters are recorded over a 24-hour period in 15-minute intervals. In the display output, focus on the data in the current interval. 5300-NAS#show controller t1 T1 0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db No alarms detected.
Section 2 Commissioning the Cisco AS5300 Hardware Table 2-6 Enabling the T1 Controllers Alarm Conditions Alarm Description CRC Errors Occurs only in ESF format when a CRC bit has an error. Excessive CRC Error Indication (ECRCEI) Reported in ESF format when 32 of any 33 consecutive CRCs are in error. Out of Frame (OOF) Occurs when the framing pattern for a T1 line has been lost, and data cannot be extracted. This is a red alarm.
Section 2 Configuring the Serial Interfaces Serial0:11 Serial0:12 Serial0:13 Serial0:14 Serial0:15 Serial0:16 Serial0:17 Serial0:18 Serial0:19 Serial0:20 Serial0:21 Serial0:22 Serial0:23 unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned YES YES YES YES YES YES YES YES YES YES YES YES YES unset unset unset unset unset unset unset unset unset unset unset unset unset Commissioning the Cisco AS5300 Hardware down
Section 2 Commissioning the Cisco AS5300 Hardware Configuring the Serial Interfaces ! interface Serial3:23 isdn incoming-voice modem ! Different versions of Cisco IOS enables different default commands. Release 12.0(5)T enables the commands in Table 2-8. Table 2-8 Release 12.0(5)T Default Commands Command Purpose no ip directed-broadcast Enhances security by preventing broadcasts to this subnet from unauthorized sources.
Section 2 Configuring Modems and Lines Step 3 Commissioning the Cisco AS5300 Hardware Test the configuration by sending a standard telephone (POTS) call into the NAS. The configuration works if the modem answers (that is, you hear modem squelch), the configuration works. Figure 2-5 shows how this step works.
Section 2 Commissioning the Cisco AS5300 Hardware Step 2 Configuring Modems and Lines Verify that the asynchronous TTY lines support incoming and outgoing calls. These lines are simulated R2-232 ports.
Section 2 Enabling IP Basic Setup Commissioning the Cisco AS5300 Hardware Task 6. Enabling IP Basic Setup Fine tune the IP routing functions and domain-name services for EXEC shell users. Step 1 Optimize IP routing functions in global configuration mode: ip subnet-zero no ip source-route ip classless Table 2-9 describes the previous commands. Table 2-9 Step 2 IP Routing Commands Command Purpose ip subnet-zero Specifies that 172.22.0.0 is a legal subnet.
Section 2 Commissioning the Cisco AS5300 Hardware Testing Asynchronous-Shell Connections Task 7. Testing Asynchronous-Shell Connections This task verifies that the following components are working: The physical asynchronous data path Basic modem links Basic IP functionality to support shell sessions The Cisco IOS provides a command-line interface (CLI) called the EXEC.
Section 2 Testing Asynchronous-Shell Connections Step 4 Commissioning the Cisco AS5300 Hardware Log into the EXEC session: This is a secured device. Unauthorized use is prohibited by law. User Access Verification Username: dude Password: 5300-NAS> Step 5 Identify the line where the call landed. The following example shows that line TTY 1 accepted the call. The call has been up and active for 48 seconds.
Section 2 Commissioning the Cisco AS5300 Hardware Confirming the Final Running-Config login: dude Password: Last login: Wed Oct 6 08:57:46 from dhcp-aus-163-236 Sun Microsystems Inc. SunOS 5.6 Generic August 1997 /cms/resource/.cmsrc: No such file or directory people% Task 8. Confirming the Final Running-Config The final running configuration looks like this: 5300-NAS#show running-config Building configuration... Current configuration: ! version 12.
Confirming the Final Running-Config Section 2 Commissioning the Cisco AS5300 Hardware pri-group timeslots 1-24 ! controller T1 2 framing esf linecode b8zs pri-group timeslots 1-24 ! controller T1 3 framing esf linecode b8zs pri-group timeslots 1-24 ! process-max-time 200 ! interface Loopback0 ip address 172.22.99.1 255.255.255.255 no ip directed-broadcast ! interface Loopback1 ip address 172.22.90.1 255.255.255.0 no ip directed-broadcast ! interface Ethernet0 ip address 172.22.66.23 255.255.255.
Section 2 Commissioning the Cisco AS5300 Hardware What to do Next ip classless ip route 0.0.0.0 0.0.0.0 172.22.66.1 ! banner login ^C This is a secured device. Unauthorized use is prohibited by law. ^C ! line con 0 transport input none line 1 96 modem InOut line aux 0 line vty 0 4 ! end What to do Next Perform the tasks in the section “Verifying Modem Performance.
What to do Next 2-32 Section 2 Commissioning the Cisco AS5300 Hardware Cisco AS5x00 Case Study for Basic IP Modem Services 11/24/1999
S E C T I O N 3 Commissioning the Cisco AS5800 Hardware In this Section This section describes how to configure the Cisco AS5800 to support terminal EXEC shell services and login prompts for client modems. The following subsections are provided: Understanding the Basic Hardware Architecture Task 1. Verifying Basic Setup Task 2. Configuring Cisco IOS Basics Task 3. Enabling the T3/T1 Controllers Task 4. Configuring the Serial Interfaces Task 5.
Section 3 Understanding the Basic Hardware Architecture Commissioning the Cisco AS5800 Hardware The Cisco 7206 Router Shelf and the Cisco DS5814 Dial Shelf The Cisco AS5800 access server contains: A Cisco 7206 router shelf (egress). It connects to the IP backbone. A Cisco DS5814 dial shelf (ingress). It connects to the PSTN.
Section 3 Commissioning the Cisco AS5800 Hardware Understanding the Basic Hardware Architecture The Cisco 7206 router shelf contains the following: ` Port adapters. In this case study, the Cisco 7206 uses Fast Ethernet (FE) 0/1/0 to connect to the IP backbone. ` A dial shelf interconnect (DSI) port adapter. In this case study, the adapter is located at 0/2/0. The Cisco 7206 communicates with the Cisco DS5814 dial shelf through an external dial shelf interconnect cable.
Section 3 Understanding the Basic Hardware Architecture Figure 3-2 Commissioning the Cisco AS5800 Hardware Cisco AS5800 Call-Processing Components Inside a Cisco network access server IP network Routing and switching engine Group-async interface Dialer interface controlling the D channels Cloning Asynchronous interfaces Cloning TTY lines Serial interface channels S1/0/0:0:0, S1/0/0:0:1...
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup One asynchronous PPP call consumes: One T1 DS0 channel One channel in a TDM bus One integrated modem One TTY line One asynchronous interface One synchronous PPP call consumes: Tech Tip One T1 DS0 channel One serial interface channel Synchronous PPP calls require HDLC resources. Each T3 trunk card is limited to 256 HDLC resources. T1 trunk cards do not have HDLC resource limitations. Task 1.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware 1.1 Analyzing the System Boot Dialog To view the boot sequence through a terminal session, you must have a console connection to the access server before it powers up. Caution Always power up the dial shelf before the router shelf. The DSC card checks the dial shelf’s inventory, which requires extra time. After two minutes, power up the router shelf. The router shelf depends on the DSC card for the dial shelf’s inventory report.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. cisco Systems, Inc.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware --- System Configuration Dialog --Would you like to enter the initial configuration dialog? [yes/no]: no 3. Because the NAS has never been configured, the Cisco IOS cannot find a startup-config file. Abort the configuration dialog. In this case study, the Cisco IOS is configured manually. The automatic setup script is not used. Manually configuring the Cisco IOS develops your expertise.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup 1.2 Matching the Cisco IOS Images The dial shelf and router shelf run separate Cisco IOS images: Both images must be from the same Cisco IOS Release. They must match. In this case study, the Cisco IOS release is 12.0(4)XL1. The router shelf’s image is in the Cisco 7206’s Flash memory. It begins with “c5800.” The dial shelf’s image is in the DSC card. It begins with “dsc.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware Table 3-1 describes the significant output fields in the previous display: Table 3-1 Show Version Command Field Descriptions Field Description 5800 Software (C5800-P4-M), Version 12.0(4)XL1 Cisco IOS version. Router uptime is 2 minutes Reports the router’s uptime. Watch for unscheduled reloads. System returned to ROM by reload Describes why the access server last reloaded.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup 1.
Section 3 Verifying Basic Setup Step 4 Commissioning the Cisco AS5800 Hardware From the Cisco 7206, verify that the DSI-Fast Ethernet interface and line protocol are up: Router>show dsi DSI-Fastethernet0/2/0 is up, line protocol is up Hardware is DEC21140A, address is 0030.f2f5.1438 (bia 0030.f2f5.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup 04:45:02: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 2 Succeeded 04:45:03: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 3 Succeeded Router> The following boot sequence occurs in the previous example: 1. The DSC card takes 32 seconds to boot up. Afterwards, the card checks the dial shelf’s inventory. 2. The dial shelf exchanges hardware inventory information with the router shelf.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware 1.4 Understanding DSIP Commands The router shelf communicates with the dial shelf by using: A Fast Ethernet interconnect cable The Dial Shelf Interconnect Protocol (DSIP) For the DSIP command reference and other system management functions, refer to the document Dial and System Management Commands for the Cisco AS5800 at the following URL: http://www.cisco.
Section 3 Commissioning the Cisco AS5800 Hardware Shelf1 Shelf1 Shelf1 Shelf1 Shelf1 Shelf1 Shelf1 Router# : : : : : : : Slot5 : Slot6 : Slot7 : Slot8 : Slot9 : Slot10: Slot12: Verifying Basic Setup 0090.bf52.4e28, 0090.bf52.4e30, 0090.bf52.4e38, 0090.bf52.4e40, 0090.bf52.4e48, 0090.bf52.4e50, 0090.bf52.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware 1.5 Checking the Initial Running-Config The Cisco IOS creates an initial running configuration. To get familiar with the default settings, inspect the configuration. Step 1 Display the configuration on the Cisco 7206 router shelf: Router#show running-config Building configuration... Current configuration: ! version 12.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup ! line con 0 transport input none line aux 0 line vty 0 4 line 1/2/00 1/10/143 modem InOut no modem log rs232 ! end Step 2 Without connecting to the DSC card, display the configuration on the Cisco DS5814 dial shelf: Router#execute-on slot 12 show running-config DA-Slot12# Building configuration... Current configuration: ! version 12.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware 1.6 Exploring the Cisco IOS File System Get familiar with the file system and memory storage areas. The Cisco IOS File System (IFS) provides a consolidated interface to: The Flash memory file system The network file system (TFTP, rcp, and FTP) Any other endpoint for reading or writing data (such as NVRAM, modem firmware, the running configuration, ROM, raw system memory, Xmodem, and Flash load helper log).
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup Table 3-2 describes the memory locations shown in Figure 3-3. Table 3-2 Memory Location Descriptions Component Description CPU (NPE200) Central processing unit. Processor memory The Cisco IOS image is initially read out of Flash memory, decompressed, and loaded into processor memory (also known as main memory). Routing tables, call control blocks, and other data structures are also stored here.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware Display the objects in the system memory directory: Router#dir system: Directory of system:/ 2 1 dr-x -rw- 0 787 memory running-config No space information available Router# Remember to include the trailing colon (:) in the dir commands. Inspect the Flash memory on the router shelf and dial shelf. Both images must have a matching Cisco IOS Release number.
Section 3 Commissioning the Cisco AS5800 Hardware Verifying Basic Setup The squeeze command is required to remove deleted files: 5800-NAS#pwd dsc12-bootflash:/ 5800-NAS#delete dsc-c5800-mz.113-9.AA2 Delete filename [dsc-c5800-mz.113-9.AA2]? Delete dsc12-bootflash:dsc-c5800-mz.113-9.AA2? [confirm] 5800-NAS#squeeze dsc12-bootflash: All deleted files will be removed. Continue? [confirm] Squeeze operation may take a while. Continue? [confirm] DA-Slot12# All deleted files will be removed.
Section 3 Verifying Basic Setup Commissioning the Cisco AS5800 Hardware The following exercise explains how to inspect and calculate memory usage: Step 1 Display the memory status report. Note that the largest-memory block is close to the free-memory block, which is good. There is no fragmentation.
Section 3 Commissioning the Cisco AS5800 Hardware Step 3 Verifying Basic Setup Perform some useful memory calculations: Total processor = total RAM minus the IOS image size (use the show version command to get the MB assigned for all of IOS + processor) cisco 7206 (NPE200) processor with 114688K/16384K bytes of memory. 114688 KB / (1024 KB / MB) = 112.0 MB 16384 KB = 16 MB 112 MB + 16 MB = 128 MB (what you purchased). Note that 112.0 MB - 89.7 MB = 22.3 MB. This means that 22.
Section 3 Configuring Cisco IOS Basics Commissioning the Cisco AS5800 Hardware Whenever memory cannot be allocated to a process request (a memory leak), a console error message appears: Sep 14 11:30:33.
Section 3 Commissioning the Cisco AS5800 Hardware Note Step 2 Configuring Cisco IOS Basics The enable password command is an obsolete command. Do not use it. Log in with the enable secret password. The show privilege command shows the current security privilege level. 5800-NAS#disable 5800-NAS>enable Password: 5800-NAS#show privilege Current privilege level is 15 5800-NAS# 2.2 Configuring Local AAA Security Configure AAA to perform login authentication by using the local username database.
Section 3 Configuring Cisco IOS Basics Commissioning the Cisco AS5800 Hardware Table 3-5 describes the previous configuration fragment: Table 3-5 Step 3 Local AAA Commands Command Purpose aaa new-model Initiates the AAA access control system. This command immediately locks down login and PPP authentication. aaa authentication login default local Configures AAA to perform login authentication by using the local username database. The login keyword authenticates EXEC shell users.
Section 3 Commissioning the Cisco AS5800 Hardware Step 2 Configuring Cisco IOS Basics Test the banner: 5800-NAS# 5800-NAS#login This is a secured device. Unauthorized use is prohibited by law. User Access Verification Username: admin Password: 5800-NAS# 2.4 Configuring Basic IP To commission a basic dial access service: Step 1 Configure two loopback interfaces. Bring up one Fast Ethernet interface. Add an IP route to the default gateway.
Section 3 Configuring Cisco IOS Basics Step 2 Commissioning the Cisco AS5800 Hardware Verify that the Fast Ethernet interface is up. Ping the default gateway. 5800-NAS#ping 172.22.66.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.22.66.1, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms 5800-NAS# This step verifies that you have IP connectivity with another device on the subnet.
Section 3 Commissioning the Cisco AS5800 Hardware Enabling the T3/T1 Controllers Task 3. Enabling the T3/T1 Controllers Configure the settings for the T3/T1 controllers. They must match the telco’s settings on the telephone switch. Mismatched settings cause problems; sometimes these problems are not detected for a long time. Figure 3-4 shows the logical controller components inside a Cisco AS5800. It shows that a T3 trunk card requires T1 and T3 controller configuration settings.
Section 3 Enabling the T3/T1 Controllers Note Step 2 Commissioning the Cisco AS5800 Hardware For T1 CAS trunks, no ISDN switch type is configured. Configure the T3 controller. There are 28 T1 controllers in one T3. In this example, only the fourth controller is configured. The t1 4 controller command automatically creates the logical T1 controller 1/0/0:4. The number of logical T1 controllers should match the number of TI PRI lines coming into the T3.
Section 3 Commissioning the Cisco AS5800 Hardware Table 3-6 Enabling the T3/T1 Controllers Controller Terms and Descriptions Concept Description Framing type Defines the control bits and data bits. For T3s, Cisco supports: M23—M23 multiplexer framing (default) C-bit—C-bit parity framing For T1s, Cisco supports: ESF—Extended super frame. Required for 64 kb operation on DS0s. ESF requires 2k-framing bits for synchronization.
Enabling the T3/T1 Controllers Step 4 Section 3 Commissioning the Cisco AS5800 Hardware Verify that the controllers are up and no alarms or errors are detected. Error counters are recorded over a 24-hour period in 15-minute intervals. In the display output, focus on the data in the current interval. 5800-NAS#show controller t3 T3 1/0/0 is up. Applique type is Channelized T3 No alarms detected.
Section 3 Commissioning the Cisco AS5800 Hardware Enabling the T3/T1 Controllers From the reference point of the NAS, Table 3-7 provides a list of T1 alarm conditions and descriptions. Table 3-7 Alarm Conditions Alarm Description CRC Errors Occur only in ESF format when a CRC bit has an error. Excessive CRC Error Indication (ECRCEI) Reported in ESF format when 32 of any 33 consecutive CRCs are in error.
Section 3 Configuring the Serial Interfaces Commissioning the Cisco AS5800 Hardware Task 4. Configuring the Serial Interfaces Configure the serial D channels to route incoming voice calls from the PSTN to the integrated modems. The behavior of the B channels is controlled by the D channels’ configuration instructions. The D channel is the signaling channel. Table 3-8 describes the relationship between T1 controllers and serial interfaces.
Section 3 Commissioning the Cisco AS5800 Hardware Configuring the Serial Interfaces Look at the status of the DS0 channels. In this example, 23 DS0s are idle. The 24th channel is reserved for PRI D-channel signaling.
Section 3 Configuring Modems and Lines Commissioning the Cisco AS5800 Hardware Task 5. Configuring Modems and Lines Modems and lines are configured after: The serial channels are operational POTS telephone calls are successfully routed to the modems Each modem is mapped to a dedicated asynchronous line inside the NAS. After the modem inout command is applied to the lines, the NAS is ready to accept modem calls.
Section 3 Commissioning the Cisco AS5800 Hardware Step 3 Enabling IP Basic Setup Choose a specific modem and inspect the modem-to-TTY line association. TTY lines are simulated RS-232 ports. In this example, TTY 432 is associated with modem 1/2/00. TTY line numbers map to specific slots. Each slot is hard coded with 144 TTY lines. In this case study, the first modem card is in slot 2 (slot 0 and slot 1 do not contain modem cards).
Section 3 Testing Asynchronous EXEC Shell Connections Step 2 Commissioning the Cisco AS5800 Hardware Enter domain-name service global configuration commands to support EXEC shell users: ip ip ip ip ip domain-lookup host dirt 172.22.100.9 domain-name the.net name-server 172.22.11.10 name-server 172.22.12.10 Table 3-10 describes the previous commands: Table 3-10 Domain-Name Commands Command Purpose ip domain-lookup Enables IP domain-name lookups. ip host dirt 172.22.100.
Commissioning the Cisco AS5800 Hardware Step 1 Testing Asynchronous EXEC Shell Connections Locate a client PC, client modem, and analog line. From the client PC, open a terminal emulation program (such as Hyper Terminal, not Dial-Up Networking) and connect to the client modem. The following figure shows the network environment for this test.
Testing Asynchronous EXEC Shell Connections Section 3 Commissioning the Cisco AS5800 Hardware 5800-NAS#show caller user dude User: dude, line tty 436, service TTY Active time 00:00:34, Idle time 00:00:09 Timeouts: Absolute Idle Idle Session Exec Limits: 00:10:00 Disconnect in: 00:09:50 TTY: Line 1/2/04 DS0: (slot/unit/channel)=0/4/2 Status: Ready, Active, No Exit Banner Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol Out Modem Callout, Modem RI is CD Modem State: Ready 5800-NAS# Note Step 6
Section 3 Commissioning the Cisco AS5800 Hardware Confirming the Final Running-Config Task 8. Confirming the Final Running-Config After completing the tasks in this section, the final running configuration looks like this: 5800-NAS#show running-config Building configuration... Current configuration: ! version 12.
Section 3 What to do Next Commissioning the Cisco AS5800 Hardware voice-port 1/0/0:4:D ! ! process-max-time 200 ! interface Loopback0 ip address 172.22.99.1 255.255.255.255 no ip directed-broadcast ! interface Loopback1 ip address 172.22.90.1 255.255.255.0 no ip directed-broadcast ! interface FastEthernet0/1/0 ip address 172.22.66.23 255.255.255.
S E C T I O N 4 Verifying Modem Performance In this Section This section describes how to verify and test modem performance on a Cisco AS5300 and AS5800 by using an EXEC terminal shell service. The following sections are provided: Background on Asynchronous Data Communications Understanding Modem Modulation Standards Task 1. Initiating a Modem Loopback Test Call Task 2. Initiating and Inspecting a V.
Section 4 Background on Asynchronous Data Communications Verifying Modem Performance Async DataComm Model Figure 4-1 shows how traditional DTE-to-DCE relationships map to a Cisco network access server (NAS). Data terminal equipment (DTE) uses data communication equipment (DCE) to send data over the PSTN. In the context of RS-232 and Cisco IOS: The DTE is the client PC and the Cisco IOS TTY lines. The DCE is the client modem and the modem inside the NAS.
Section 4 Verifying Modem Performance Background on Asynchronous Data Communications Logical Packet and Circuit Components of a NAS The NAS functions as a gateway between two different networks: A circuit-switched network (for example, the PSTN) A packet-switched network (for example, the Internet) The NAS is half a circuit switch and half a packet switch (router). RS-232 signaling on the line is displayed by the show line command and debug modem command.
Section 4 Background on Asynchronous Data Communications Verifying Modem Performance To understand the general call-processing sequence, match the following numbered list with the numbers shown in Figure 4-2: 1. 64K DS0 circuits extend from the NAS modems, through the internal TDM CSM bus, and through the circuit network (PSTN). 2. The NAS modems demodulate digital streams into analog-voiceband modulation. The virtual RS-232 interface connects the modems (DCE) to the TTY lines. 3.
Section 4 Verifying Modem Performance Background on Asynchronous Data Communications Table 4-1 describes how Cisco uses it’s RS-232 pins. The signal direction in the table is from the perspective of the DTE (IOS line): Data signals (TxD, RxD) Hardware flow control signals (RTS, CTS) Modem signals (DTR, DSR, DCD, RI) Table 4-1 RS-232 Signal State Behavior Signal Signal Direction Purpose Transmit Data (TxD) ——> (Output) DTE transmits data to DCE.
Section 4 Background on Asynchronous Data Communications Verifying Modem Performance Cisco IOS Line-Side Inspection To display the current modem-hardware states applied to a specific Cisco IOS line, enter the show line tty number command. The states of each logical RS-232 pin change according to line conditions and modem events.
Section 4 Verifying Modem Performance Background on Asynchronous Data Communications Table 4-2 describes some of the significant fields shown in the previous example: Table 4-2 Show TTY Line Field Descriptions Field Description Capabilities Describes different aspects of the line: Modem state The flowcontrol hardware command displays as “Hardware Flowcontrol In, Hardware Flowcontrol Out.” The modem inout command displays as “modem callout.
Understanding Modem Modulation Standards Section 4 Verifying Modem Performance Understanding Modem Modulation Standards To optimize modem connect speeds, you must understand the basic modem modulation standards. This section provides the basic rules for achieving maximum V.34 and V.90 modulation speeds: V.34 Basic Rules V.90 Basic Rules V.34 Basic Rules V.34 modulation should work on any land-line voiceband circuit. V.34 supports speeds ranging from 2400 to 33600 bps.
Section 4 Verifying Modem Performance Understanding Modem Modulation Standards V.90 Basic Rules Many circuit components work together to deliver V.90 modulation. See Figure 4-4. Figure 4-4 V.90 Network Components 27168 PSTN Client DTE Client DCE Local loop House wiring DS0 circuit through PSTN Digital line NAS Digital modem Here are the V.90 basic rules: Select recommended modem code. The following are reliable V.90 releases at the time of this publication: ` MICA portware version 2.6.2.
Section 4 Initiating a Modem Loopback Test Call Verifying Modem Performance Exactly one digital to analog conversion must exist in the circuit. The digital line must connect into a digital switch, not a channel bank. V.90 requires PRI (64k clear-channel DS0s). Channel banks destroy V.90 by adding additional analog-to-digital conversions. Telcos occasionally refer to channel banks as line-side services. Digital switches are sometimes referred to as trunk-side services. Figure 4-5 shows this.
Section 4 Verifying Modem Performance Step 1 Initiating a Modem Loopback Test Call From a workstation, open two telnet sessions into the NAS. One telnet session is used to simulate the client. The other session is used to administer and run the debugs. In this way, the debug messages will not be scrambled into the loopback screen display. Figure 4-7 shows an example of this.
Section 4 Initiating a Modem Loopback Test Call Verifying Modem Performance Modem Management: Modem Management Call Switching Module debugging is on 5300-NAS# Tech Tip For channel associated signaling (CAS), robbed bit signaling (RBS), and R2, use the debug cas command. If this command is not included in your software, use the modem-mgmt csm debug-rbs command; however, the service internal command is required.
Section 4 Verifying Modem Performance Step 6 Initiating a Modem Loopback Test Call Log in from the client telnet session. The Cisco IOS sends out a username-password prompt. This is a secured device. Unauthorized use is prohibited by law. User Access Verification Username:admin Password: Sep Sep Sep Sep Step 7 23 23 23 23 05:04:58.047: 05:04:58.051: 05:04:58.051: 05:05:03.
Section 4 Initiating a Modem Loopback Test Call Verifying Modem Performance *Jan 1 00:34:47.867:csm_connect_pri_vdev:tdm_allocate_bp_ts() call. BP TS allocated at bp_stream0, bp_Ch5,vdev_common 0x610378B0 *Jan 1 00:34:47.883:ISDN Se0:23:RX <- ALERTING pd = 8 callref = 0x8004 *Jan 1 00:34:47.883: Progress Ind i = 0x8288 - In-band info or appropriate now available *Jan 1 00:34:48.019:Mica Modem(1/2):State Transition to Call Setup *Jan 1 00:34:48.019:Mica Modem(1/2):Went offhook *Jan 1 00:34:48.
Section 4 Verifying Modem Performance Initiating a Modem Loopback Test Call Type 10 is the login timer. The timeout is 30 seconds. The user’s EXEC-shell login password is suppressed. Step 10 Identify who is logged in. TTY line 3 corresponds to modem 1/2. Use the show terminal command to see which modem is assigned to the TTY line. 5300-NAS>show user Line User 3 tty 3 admin * 98 vty 0 joe Interface Step 11 User Host(s) idle 172.22.66.1 Idle Location 0 0 leftfield.mauionions.
Initiating a Modem Loopback Test Call Section 4 Verifying Modem Performance Parameter #15 TX,RX Trellis Coding: 16, 16 Parameter #16 TX,RX Preemphasis Index: 0, 0 Parameter #17 TX,RX Constellation Shaping: Off, Off Parameter #18 TX,RX Nonlinear Encoding: Off, Off Parameter #19 TX,RX Precoding: Off, Off Parameter #20 TX,RX Xmit Level Reduction: 0, 0 dBm Parameter #21 Signal Noise Ratio: 41 dB Parameter #22 Receive Level: -12 dBm Parameter #23 Frequency Offset: 0 Hz Parameter #24 Phase Jitter Frequency: 0
Section 4 Verifying Modem Performance Initiating a Modem Loopback Test Call Table 4-4 describes the significant parameters in the previous example. For a complete command reference description, refer to the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/dial_r/drprt1/drmodmgt.ht m Table 4-4 Operational Parameter Descriptions for a Loopback Test Call Parameter Description Parameter #1 Connect Protocol: LAP-M LapM is the connection protocol.
Section 4 Initiating and Inspecting a V.90 Test Call Table 4-4 Operational Parameter Descriptions for a Loopback Test Call (continued) Parameter Description Line shape: A line shape is the frequency-response graph of the channel. ..............................* ................................* .................................* ................................* ................................* .................................* .................................* .................................
Section 4 Verifying Modem Performance Step 3 Initiating and Inspecting a V.90 Test Call Verify that the modem is running the recommended firmware version. The following example shows a U.S. Robotics 56K fax external modem running V.4.11.2. Compare the firmware version with the version that is posted on the modem vendor’s web site. The Ati3 and ati7 modem firmware commands are commonly used and are shown below: ati3 U.S. Robotics 56K FAX EXT V4.11.2 OK ati7 Configuration Profile...
Section 4 Initiating and Inspecting a V.90 Test Call Step 5 Verifying Modem Performance Dial the access server’s telephone number, log in, and access the EXEC shell. The client modem is connected at 48000 bps in this example. atdt14085551234 CONNECT 48000/ARQ This is a secured device. Unauthorized use is prohibited by law. User Access Verification Username:dude Password: 5300-NAS> Step 6 Inspect your call on the access server. In the example, the call landed on TTY line 1.
Section 4 Verifying Modem Performance Initiating and Inspecting a V.90 Test Call Full user help is disabled Allowed transports are pad telnet rlogin udptn v120 lapb-ta. elnet rlogin udptn v120 lapb-ta. No output characters are padded No special data dispatching characters Step 8 Preferred is pad t Program the display window so it does not pause in the middle of a screen display: 5300-NAS>terminal length 0 Step 9 Generate traffic across the modem link.
Section 4 Initiating and Inspecting a V.90 Test Call Verifying Modem Performance Parameter #33 PPP/SLIP packets transmitted, received: 0, 0 Parameter #35 PPP/SLIP packets received (BAD/ABORTED): 0 Parameter #36 EC packets transmitted, received OK: 565, 43 Parameter #38 EC packets (Received BAD/ABORTED): 2 Parameter #39 Robbed Bit Signalling (RBS) pattern: 0 Parameter #40 Digital Pad: 6.0 dB, Digital Pad Compensation:None Line Shape: .........................* ................................* ...........
Section 4 Verifying Modem Performance Table 4-5 Initiating and Inspecting a V.90 Test Call Show Modem Operational-Status Field Descriptions (continued) Parameter Description Parameter #21 Signal Noise Ratio: 36 dB The signal to noise ratio (SNR) is 36 dB. (40 dB is a perfect SNR. MICA measures the SNR in the signal band. The SNR value ranges from 0 to 70 dB, and it changes in 1 dB steps. A 28.8 kbps connection requires a SNR of about 37 dB. SNRs lower than 37 dB reduce the quality of the connection.
Section 4 Initiating and Inspecting a V.90 Test Call Figure 4-8 Verifying Modem Performance Using Modem-Escape Mode to View Client-Side Modem Statistics +++ enables the client PC to communicate directly to the client modem Client PC Client modem The connection to the NAS is still up Step 12 28054 PSTN NAS Enter the ati6 command to display, among other things, the receive and transmit-carrier speeds. Compare the displayed information with the output from the show modem operational-status command.
Section 4 Verifying Modem Performance Step 13 Initiating and Inspecting a V.90 Test Call Inspect frequency levels (dB) and other diagnostic functions. The following AT commands display the client modem’s view of the frequency response. The display is a companion to the output of the show modem operational-status command (see Step 9).
Section 4 What to do Next Step 14 Verifying Modem Performance (Optional) To return to online mode and the router prompt, enter the ato command. After your enter this command, however, the +++ escape sequence is still in the EXEC session’s input buffer. If you press the carriage return (), you will receive an error about +++ being an unknown command. To clear the input buffer, type Ctrl U after the ato command.
S E C T I O N 5 Configuring PPP and Authentication In this Section This section describes how to configure the Cisco AS5300 and AS5800 for PPP and local authentication. The following sections are provided: Task 1. Configuring PPP Authentication for Local AAA Task 2. Configuring IPCP Options Task 3. Configuring LCP Options Task 4. Enabling PPP Autoselect Task 5. Testing Asynchronous PPP Connections Task 6. Inspecting Active Call States Task 7.
Section 5 Configuring IPCP Options Step 2 Configuring PPP and Authentication Configure local AAA security in global configuration mode. You must enter the aaa new-model command before the other two authentication commands. ! aaa new-model aaa authentication login default local aaa authentication ppp default if-needed local ! Step 3 Log in with your username and password: 5800-NAS#login This is a secured device. Unauthorized use is prohibited by law.
Section 5 Configuring PPP and Authentication Step 2 Configuring LCP Options Verify that the IP address pool was created: 5800-NAS#show ip local pool Pool Begin addr-pool 172.22.90.2 5800-NAS# End 172.22.90.254 Free 253 In use 0 Task 3. Configuring LCP Options The group-async interface is a template that controls the configuration of all the asynchronous interfaces in the NAS.
Section 5 Enabling PPP Autoselect Table 5-1 Configuring PPP and Authentication Interface Group Async Command Descriptions (continued) Command Purpose async mode interactive Configures interactive mode on the asynchronous interfaces. Interactive means that users can dial in and get to a shell or PPP session on that line. ppp authentication chap pap Enables CHAP and PAP authentication on the interface during LCP negotiation. The NAS first requests to authenticate with CHAP.
Section 5 Configuring PPP and Authentication Testing Asynchronous PPP Connections Task 5. Testing Asynchronous PPP Connections Before you troubleshoot PPP negotiation or AAA authentication, you need to understand what a successful PPP and AAA debug sequence looks like. In this way, you can save time and effort when comparing a successful debug session against a faulty completed debug sequence. 5.
Testing Asynchronous PPP Connections Step 4 Section 5 Configuring PPP and Authentication Go to the NAS terminal screen to observe and interpret the debug output messages. As the call enters the NAS, debug output is created. When examining PPP between two remote peers: a. First check to see if DSR came up. b. Verify that both sides get through LCP negotiation. If they do, move on to check authentication. c. After authentication succeeds, check IPCP negotiation. d.
Section 5 Configuring PPP and Authentication Testing Asynchronous PPP Connections 5.2 Failed PPP Negotiation Debug and Troubleshooting Failed authentication is a common occurrence. Misconfigured or mismatched usernames and passwords create error messages in debug output. The following example shows that the username maddog does not have permission to dial into the NAS. The NAS does not have a local username configured for this user.
Section 5 Testing Asynchronous PPP Connections Figure 5-3 Configuring PPP and Authentication Troubleshooting Flow Chart for PPP and Authentication User dials in Do the modems connect? No debug modem debug modem csm show modem log Physical layer Yes LCP negotiation Did it succeed? No debug ppp error debug ppp negotiation No debug ppp authentication debug aaa authentication Yes Authentication negotiation Did it succeed? LCP layer Yes NCP layer Network layer configuration (IPCP) Did it succ
Section 5 Configuring PPP and Authentication Testing Asynchronous PPP Connections LCP negotiation is a series of LCP packets exchanged between PPP peers to negotiate a set of options and option values when sending data. The LCP negotiation is actually two separate dialogs between two PPP peers (Peer1 and Peer 2): Peer 1 and Peer 2 do not have to use the same set of LCP options.
Section 5 Inspecting Active Call States Configuring PPP and Authentication Task 6. Inspecting Active Call States After a basic PPP modem call comes into the NAS, you should use some show commands to inspect several active call statistics. If you try to use the client’s web browser after the modems connect, you will test DNS, IP, and other functions. If your test fails, try pinging the DNS server from the device that dialed in. 6.
Section 5 Configuring PPP and Authentication Inspecting Active Call States Timeouts: Absolute Idle Limits: Disconnect in: PPP: LCP Open, PAP (<- AAA), IPCP IP: Local 172.22.66.23, remote 172.22.90.
Section 5 Inspecting Active Call States Configuring PPP and Authentication 6.2 Fast Switching and Route Caching Statistics Inspect fast-switching and route-caching performance statistics for the call. Incoming asynchronous calls can be fast switched. However, some features disable fast switching. Inspect the queueing characteristics of the asynchronous interface. Notice that the queueing strategy is first-in-first-out (fifo).
Section 5 Configuring PPP and Authentication Confirming the Final Running-Config Probe proxy name replies are disabled Gateway Discovery is disabled Policy routing is disabled Network address translation is disabled 5800-NAS# Look at the fast-switching cache in action. Notice that only packets destined to the Fast Ethernet interface are currently cached.
Confirming the Final Running-Config Section 5 Configuring PPP and Authentication ! ! ! ! ! shelf-id 0 router-shelf shelf-id 1 dial-shelf ! ! ! resource-pool disable ! modem-pool Default pool-range 1/2/0-1/10/143 ! ! spe 1/2/0 1/10/11 firmware ios-bundled default modem recovery action none ip subnet-zero no ip source-route ip host dirt 172.22.100.9 ip domain-name the.net ip name-server 172.22.11.10 ip name-server 172.22.12.11 ! async-bootp dns-server 172.30.10.1 172.30.10.
Section 5 Configuring PPP and Authentication What to do Next ! interface Group-Async0 ip unnumbered FastEthernet0/1/0 no ip directed-broadcast encapsulation ppp async mode interactive peer default ip address pool addr-pool no cdp enable ppp authentication chap pap group-range 1/2/00 1/10/143 ! ip local pool addr-pool 172.22.90.2 172.22.90.254 ip classless ip route 0.0.0.0 0.0.0.0 172.22.66.
What to do Next 5-16 Section 5 Configuring PPP and Authentication Cisco AS5x00 Case Study for Basic IP Modem Services 11/24/1999
S E C T I O N 6 Modem Management Operations In this Section This section describes how to manage the modems on a Cisco AS5300 and AS5800 by using the Cisco IOS. The following sections are provided: Task 1. Managing Modem Firmware Task 2. Configuring Modems Using Modem Autoconfigure Task 3. Gathering and Viewing Call Statistics In this case study, Maui Onions and THEnet perform these same tasks to manage modem operations of their network access servers (NAS).
Section 6 Managing Modem Firmware Modem Management Operations The following documents are related to modem management operations: Dial Solutions Configuration Guide, Managing Modems, Release 12.0 http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/ dial_c/dcmodmgt.htm Dial Solutions Command Reference, Modem Management Commands, Release 12.0 http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/ dial_r/drprt1/drmodmgt.
Section 6 Modem Management Operations 1/13 1/14 1/15 1/16 1/17 Managing Modem Firmware 2 2 2 2 2 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 ... Snip Find the version of firmware that is bundled with the Cisco IOS. The show modem map command displays the region of NVRAM that identifies where the modems get their firmware from at bootup. The field “IOS-Default” indicates that the modem gets its firmware from the bundled IOS image.
Section 6 Managing Modem Firmware Modem Management Operations The Cisco AS5800 does not support the show modem map command. Use show modem bundled-firmware command instead: as5800-RS-1#show modem bundled-firmware List of bundled modem firmware images by slot Slot 4 2.6.2.0 Slot 5 2.6.2.0 Slot 6 2.6.2.0 Slot 7 2.6.2.0 Slot 8 2.6.2.0 Inspect the directory that stores the bundled firmware files. The files are loaded into the system main memory through the ucode directory.
Section 6 Modem Management Operations Managing Modem Firmware The commands show flash and show bootflash are supported in all versions of Cisco IOS. The commands dir flash: and dir bootflash: are supported in Release 12.0T. AS5300-1#show flash System flash directory: File Length Name/status 1 6436752 c5300-is-mz.120-5.5.T 2 392241 mica-modem-pw.2.7.1.0.
Section 6 Managing Modem Firmware Modem Management Operations 1.2 Upgrading Modem Firmware Cisco regularly enhances modem DSP code to improve modem performance. To obtain the latest DSP code, upgrade the NAS modem firmware. Figure 6-1 summarizes the firmware upgrade procedure. Figure 6-1 Modem Firmware Download Operation Example Internet CCO 1 Mica-modem-pw.x.x.x.x. (portware file) Legend TFTP server 2 1 Download the portware from CCO to a TFTP server or directly into the NAS.
Section 6 Modem Management Operations Managing Modem Firmware The following example uses the copy ftp command. The file mica-modem-pw.2.7.1.0.bin is copied from ftp.cisco.com to the bootFlash. Be sure to specify your own CCO username and password in the command line (as indicated in the example). 5300-NAS#ping ftp.cisco.com Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.31.7.
Section 6 Managing Modem Firmware Modem Management Operations Depending on which Cisco IOS Release is loaded in the NAS, there are two commands that you can use. Table 6-3 describes these two commands. Table 6-3 Modem Mapping Commands Cisco IOS Command Notes 12.0(5)T and later spe An SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem. For MICA, an SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density.
Section 6 Modem Management Operations Managing Modem Firmware In the previous example, the specified SPE range gets updated with new firmware in batches of six modems at a time. If double density modems were installed, batches of 12 modems would be updated. Note below that the SPE range 1/0 to 1/7 is mapped to firmware 2.7.1.0. However, SPE range 2/0 through 2/7 is still mapped to the firmware that is bundled with the Cisco IOS. ! spe 1/0 1/7 firmware location flash:mica-modem-pw.2.7.1.0.
Section 6 Configuring Modems Using Modem Autoconfigure Modem Management Operations Slot 2 has Mica Carrier card. Modem Module Numbers 0 2/0 - 2/5 1 2/6 - 2/11 2 2/12 - 2/17 3 2/18 - 2/23 4 2/24 - 2/29 5 2/30 - 2/35 6 2/36 - 2/41 7 2/42 - 2/47 Firmware Rev 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.0 2.6.2.
Section 6 Modem Management Operations Configuring Modems Using Modem Autoconfigure 2.1 Basic Rules for Modem Autoconfigure The following list describes the basic rules: 1. Never use the modem autoconfigure discovery command. Applying specific modemcaps reduces the risk of error. 2. Always use the modem autoconfigure type modem-name command. This command improves your modem’s performance. See CSCdk15302 for an explanation.
Gathering and Viewing Call Statistics Note Section 6 Modem Management Operations The MICA and Microcom AT command references are posted at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_inf o/at/index.htm Step 4 Apply the new entry to the specified lines. Re-enter the modem autoconfigure command each time you change a modemcap. Modem-autoconfigure strings are not applied to busy modems. Modem strings are applied after modems disconnect.
Section 6 Modem Management Operations Gathering and Viewing Call Statistics 3.1 Using the Cisco IOS EXEC (CLI) The Cisco IOS command line interface (CLI) contains many modem management show commands. Use these commands to gather and view modem statistics. This section provides a bulleted list detailing some of the most useful commands.
Section 6 Gathering and Viewing Call Statistics Modem Management Operations Display the disconnect reasons for the modems that trained up: 5300-NAS#show modem call-stats 0 dial-in/dial-out call statistics Mdm Total compress # % 237 retrain lostCarr userHgup rmtLink trainup hostDrop wdogTimr # % # % # % # % # % # % # % 916 413 124 9999 1064 8496 0 dial-out call statistics noCarr noDitone Mdm # % # % Total 1715 0 busy # % 0 abort dialStrg autoLgon dialTout # % # % # % # % 0 0 0 0 rmtHgup # % 0 T
Section 6 Modem Management Operations * 1/8 1/9 1/10 1/11 * 1/12 1/13 Gathering and Viewing Call Statistics 5 3 1 2 7 6 2 1 0 0 2 2 21 10 29 27 21 21 2 1 3 2 2 2 7 8 9 9 10 10 1 1 2 2 2 2 2 2 1 4 5 1 1 1019 1 939 0 918 3 981 4 966 0 977 2 2 2 2 2 2 28 22 28 27 24 32 2 2 2 2 2 3 159 191 194 174 182 168 1 2 2 2 2 1 0 0 0 0 0 0 0 0 0 0 0 0 Display a summary of the range of connect speeds. Specify the top speed of interest followed by a 0.
Section 6 Gathering and Viewing Call Statistics 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 pri pri pri pri pri pri pri pri pri pri pri pri pri pri pri pri pri 4525 4401 4096 3961 3320 3138 2912 2486 2042 1644 1413 1071 884 675 507 380 263 Modem Management Operations 6w1d 5w3d 4w4d 3w3d 3w0d 1w3d 4d05h 6w4d 5w5d 4w5d 4w1d 3w3d 2w4d 2w0d 1w3d 1w1d 5d17h T1 1: DS0's Active: 9 DS0's Active High Water Mark: 23 TimeSlot Type TotalCalls TotalDuration 1 pri 8985 3w2d 2 pri 8650 2w4d 3 pri 8594 1w3d 4 pr
Section 6 Modem Management Operations Gathering and Viewing Call Statistics 3.2 Using Modem Call-Record Terse Starting with Cisco IOS Releases 11.3AA and 12.0T, modem call records can be sent to syslog and examined to perform statistical analysis. For example, you can monitor: Modulation trends such as V.90 verses V.
Section 6 Gathering and Viewing Call Statistics Modem Management Operations 3.3 Using SNMP Modem connect speeds can be graphed using SNMP MIBs. The graph shown in Figure 6-2 was created with Cisco Access Manager (CAM). The graph describes the modem connect-speed performance activity of one NAS for one month. The following connect speeds are transmitted by the NAS and received by the client modem. Most of the calls performed between 28000 and 31200 bps. This NAS is one member of an access stack.
S E C T I O N 7 Enabling Management Protocols: NTP, SNMP, and Syslog In this Section This section describes how to enable basic management protocols on a Cisco AS5800 and Cisco AS5300 as part of a dial access service. The following sub sections are provided: Understanding Network Management Basics Task 1. Enabling the Network Time Protocol Task 2. Enabling Syslog Task 3. Enabling SNMP Task 4. Disabling the Logging of Access Interfaces Task 5.
Section 7 Understanding Network Management Basics Enabling Management Protocols: NTP, SNMP, and Syslog Understanding Network Management Basics Figure 7-1 shows a logical view of how management protocols interact between the Cisco IOS (client) and the network element management server. The dashed lines indicated different protocols and functions. NTP synchronizes time between network devices. The SNMP element manager (EM) receives SNMP traps from the Cisco IOS.
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Enabling the Network Time Protocol For more information about system management, refer to Release 12.0 Configuration Fundamentals Configuration Guide and Command Reference at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/index.htm Task 1. Enabling the Network Time Protocol The Network Time Protocol (NTP) provides a common time base for networked routers, servers, and other devices.
Section 7 Enabling Syslog Enabling Management Protocols: NTP, SNMP, and Syslog The following command identifies how often the NAS is polling and updating to the stratum clock. An asterisk (*) next to the NTP server’s IP address indicates successful synchronization with the stratum clock. 5300-NAS#show ntp association address ref clock st when poll reach delay offset disp *~172.22.66.18 172.60.8.1 16 46 64 377 1.0 0.53 0.
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Step 1 Enabling Syslog Enable debug timestamps and include the date, time, and milliseconds relative to the local time zone: ! service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone ! Step 2 Verify that console logging is disabled. If it is enabled, the NAS will intermittently freeze up as soon as the console port is overloaded with log messages. See the field “1 flushes.
Section 7 Enabling SNMP Enabling Management Protocols: NTP, SNMP, and Syslog If you are working with multiple network access servers, assign a different logging facility tag to each server. Syslog information can be collected and sorted into different files on the syslog server.
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Figure 7-3 Enabling SNMP SNMP Event Interaction and Timing Get request Reply Get next Reply Set request Trap 26095 EM (SNMP manager) NAS (SNMP agent) Note For a listing of all SNMP traps supported by Cisco, refer to the following URL: http://www.cisco.com/public/mibs/traps/ Step 1 Configure the Cisco IOS to support basic SNMP functions.
Section 7 Enabling SNMP Table 7-3 Enabling Management Protocols: NTP, SNMP, and Syslog SNMP Commands Command Purpose snmp-server contact admin dude@mauionions.com Specifies a contact name to notify whenever a MIB problems occurs. snmp-server location 5300-NAS-Maui Specifies a geographic location name for the router. snmp-server community poptarts RO 8 Assigns a read only (RO) community string. Only queries and get requests can be performed.
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Step 2 Disabling the Logging of Access Interfaces Monitor SNMP input and output statistics. For example, display a real-time view of who is polling the NAS for statistics and how often. Excessive polling will: Consume much of the CPU resources Cause packets to be dropped Crash the NAS 5300-NAS#show snmp Chassis: 11811596 Contact: admin dude@mauionions.
Confirming the Final Running-Config Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog interface Serial 2:23 no logging event link-status no snmp trap link-status ! interface Serial 3:23 no logging event link-status no snmp trap link-status ! interface Group-Async 1 no logging event link-status no snmp trap link-status ! Task 5.
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Confirming the Final Running-Config framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 ! controller T1 1 framing esf clock source line secondary 1 linecode b8zs pri-group timeslots 1-24 ! controller T1 2 framing esf linecode b8zs pri-group timeslots 1-24 ! controller T1 3 framing esf linecode b8zs pri-group timeslots 1-24 ! process-max-time 200 ! interface Loopback0 ip address 172.22.99.1 255.255.255.
Confirming the Final Running-Config Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog ! interface Serial3:23 no ip address no ip directed-broadcast no logging event link-status no snmp trap link-status isdn switch-type primary-5ess isdn incoming-voice modem fair-queue 64 256 0 no cdp enable ! interface FastEthernet0 no ip address no ip directed-broadcast shutdown ! interface Group-Async1 ip unnumbered Ethernet0 no ip directed-broadcast encapsulation ppp no logging event link-status async mod
Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog What to do Next Unauthorized use is prohibited by law. ^C ! line con 0 transport input none line 1 96 autoselect during-login autoselect ppp modem InOut line aux 0 line vty 0 4 ! ntp clock-period 17179891 ntp update-calendar ntp server 172.22.66.18 prefer ! end What to do Next Inspect the final-running configuration as described in the section “Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800.
What to do Next 7-14 Section 7 Enabling Management Protocols: NTP, SNMP, and Syslog Cisco AS5x00 Case Study for Basic IP Modem Services 11/24/1999
S E C T I O N 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 In this Section This section provides the final running configuration files for the Cisco AS5300 and AS5800 used in this case study. These configuration files can be used as templates for configuring basic IP modem services. To do this: 1. Copy the configuration file into a text editor. 2. Replace the command variables with your own network parameters. 3. Copy the modified configuration files into Flash memory.
Cisco AS5300 Configuration Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 username admin password 7 045802150C2E username dude password 7 070C285F4D06 spe 1/0 1/7 firmware location bootflash:mica-modem-pw.2.7.1.0.bin spe 2/0 2/7 firmware location bootflash:mica-modem-pw.2.7.1.0.bin ! resource-pool disable ! ip subnet-zero no ip source-route ip host dirt 172.22.100.9 ip domain-name mauionions.com ip name-server 172.22.11.10 ip name-server 172.22.12.
Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 Cisco AS5300 Configuration isdn switch-type primary-5ess isdn incoming-voice modem fair-queue 64 256 0 no cdp enable ! interface Serial1:23 no ip address no ip directed-broadcast no logging event link-status no snmp trap link-status isdn switch-type primary-5ess isdn incoming-voice modem fair-queue 64 256 0 no cdp enable ! interface Serial2:23 no ip address no ip directed-broadcast no logging event link-status no snmp tr
Cisco AS5800 Configuration Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 snmp-server community poptarts RO 8 snmp-server community pixysticks RW 5 snmp-server community maddog view v1default RO snmp-server trap-source Loopback0 snmp-server location 5300-NAS-Maui snmp-server contact admin dude@mauionions.
Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 Cisco AS5800 Configuration aaa authentication ppp default if-needed local enable secret 5 $1$LKgL$tgi19XvWn7fld7JGt55p01 ! username dude password 7 045802150C2E username admin password 7 044E1F050024 ! ! ! ! ! ! shelf-id 0 router-shelf shelf-id 1 dial-shelf ! ! ! resource-pool disable ! modem-pool Default pool-range 1/2/0-1/10/143 ! ! spe 1/2/0 1/10/11 firmware ios-bundled default modem recovery action none ip subnet-zer
Cisco AS5800 Configuration Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 interface Serial1/0/0:4:23 no ip address no ip directed-broadcast no snmp trap link-status isdn switch-type primary-ni isdn incoming-voice modem no cdp enable ! interface Group-Async0 ip unnumbered FastEthernet0/1/0 no ip directed-broadcast encapsulation ppp async mode interactive no snmp trap link-status peer default ip address pool addr-pool no cdp enable ppp authentication chap pap group-ran
Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 Cisco AS5800 Configuration autoselect during-login autoselect ppp modem InOut no modem log rs232 ! ntp update-calendar ntp server 172.22.66.
Cisco AS5800 Configuration 8-8 Section 8 Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 Cisco AS5x00 Case Study for Basic IP Modem Services 11/24/1999
I N D E X ARP A 2-15 asynchronous-shell AAA connections Cisco AS5300 testing 2-13 configuring async mode interactive command Cisco AS5800 at commands 3-25 configuring dial plan PPP 2-13 local security server types 5-7 autoselect during-login command requirements 1-5 5-7 5-4 5-1 configuring servers 4-13 troubleshooting PPP authentication 1-5 5-4 authentication 1-4 design 2-27 B banner 1-4 login aaa authentication login default local 3-26 aaa authentication login default l
Index call-processing Cisco IOS 3-3 components Cisco AS5300 5-10 inspecting Cisco AS5800 6-12 gathering file system 6-12 2-7, 3-18 exploring CAM images graph 3-9 matching modem connect-speed 6-18 line-side inspection CCO release 6-6 downloading 4-6 4-14 packet sampling modem firmware 2-16 upgrading 2-16 cd flash command 4-9 V.90 support CDP release 12.
Index 6-6 copy ftp command DRAM 6-8 copy modem command DSC copy running-config startup-config 3-24 2-12 DSIP 6-6 card state detection CPU utilization inspecting 3-11, 3-13 troubleshooting copy running-config startup-config command copy tftp command 3-11, 3-20 2-11, 3-23 Cisco 7206 3-3 description 3-14 3-8 dsip console slave command 4-12 D E datacomm 4-2 async model enable password command 2-22 configuring enable secret debug aaa authentication command 5-5 6-11 encapsulation
Index F I fast switching I/O statistics 5-12 memory usage firmware 2-10 2-7, 3-18 IFS interface modems managing 6-2 unbundled 6-7 upgrading 6-6 serial 1-8 address strategy 3-22 basic setup enabling framing types 2-19 T1 controllers 2-26, 3-37 Cisco AS5800 2-10, 3-21 FreeMem 2-3 IP fragmentation memory 2-3 asynchronous 3-27 configuring commands routing G 2-26, 3-37 2-15 configuring route group async command 5-3 domain-name commands group-range command 5-4 subnet a
Index K device parameters K56Flex IP domain name 1-3 dial planning autoconfigure example 6-11 1-11 1-11 1-12 operation strategy configuration design parameters L modems LCP network management 6-1 managing 5-9 configure-request 1-8 7-1 enabling plan options 5-3 configuring 1-9 IP subnetting projections line codes 2-19 T1 controllers scaling 1-5 selections lines Cisco AS5300 2-24 configuring service definition Cisco AS5800 memory logging 3-22 calculations cards commands
Index modem at-mode command 4-15, 4-21 modem autoconfigure command 6-12 modem autoconfigure discovery command 6-11 6-11 modem autoconfigure type command modem autoconfigure type mica command 6-7 upgrading 6-6 6-11 4-18 line shape 4-12 4-25 4-10 initiating management 6-2 firmware modems 4-23 +++ command related documents ati3 and ati7 commands 4-19 modulation standards 6-11 basic rules 6-11 performance call-record terse SPE call statistics speed 6-12 gathering 6-1 2-24 su
Index network topology autoselect 1-7 selections enabling 1-7 network topology elements NOC 5-4 call-processing 3-27 3-3 Cisco AS5800 no cdp enable command 2-23, 5-4 no ip directed-broadcast command no ip source-route command call states 2-23, 5-4 2-26 no ip tcp header-compression command no modem log command 5-10 inspecting configure-request 5-12 configuring 3-36 5-1 5-3 dialup framing NTP 5-9 flow diagrams enabling 7-1, 7-3 troubleshooting 7-2 RFC 1305 HDLC NVRAM inspecti
Index show dial-shelf R 3-11 4-12 show dial shelf command 4-12 reverse telnet RFC 1877 show dsi 5-2 3-14 show dsip transport route caching statistics 3-14 show dsip version 5-12 3-15 3-8 show environment command 1-11 router host names show file systems router shelf 3-19 2-9 show file systems command 3-2, 3-3 Cisco 7206 RS-232 pin configuration 4-5 6-5 show interface async 5-12 5-11 show interface async command 4-5 signal state behavior show flash command 5-13 show ip cache com
Index 3-40, 4-15, 4-20 show user command show version command T 2-5, 3-9 2-6 description T1 controllers SNMP 7-8 commands 1-11 event interaction 7-7 6-18 snmp-server contact admin snmp-server host command 7-8 snmp-server location command snmp-server trap-source 2-19 line codes 2-19 7-8 controller-to channel 3-34 controller-to-channel 2-22 settings matching 7-8 6-8 2-18 2-19 timeslot assignment T3/T1 controllers enabling SPE 3-29 telnet 3-21 squeeze command reverse 4-12 t
Index network management enabling 7-1 1-7 5-13 switch commands plan system images and microcode 1-9 IP subnetting projections scaling time synchronization 7-3 updated modem code 4-9 2-17 1-5 service definition V 1-5 user-to-network timeslot assignment V.34 2-19 T1 controllers 4-8 basic rules time stamps V.
