Cisco AS5800 OAM&P Guide - Chap 2: Commissioning [Cisco AS5800 Series Universal Gateways]

Table Of Contents

Commissioning

Commissioning the Cisco AS5800 Hardware

Understanding the Basic Hardware Architecture

Cisco 7206 Router Shelf and Cisco 5814 Dial Shelf

Call-Processing Components

Task 1. Verifying Basic Setup

Analyzing the System Boot Dialog

Matching the Cisco IOS Software Images

Inspecting the Dial Shelf

DSC Troubleshooting Tips

Feature-Card Troubleshooting Tips

Using DSIP

Checking the Initial Running-Config

Exploring the Cisco IOS File System

Investigating Memory Usage

Verifying CPU Utilization

Task 2. Configuring Basic Cisco IOS Software

Configuring the Host Name, Enable Secret Password, and Time Stamps

Configuring Local AAA Security

Setting Up a Log In Banner

Configuring Basic IP

Task 3. Enabling the T3/T1 Controllers

Task 4. Configuring the Serial Interfaces

Task 5. Configuring Modems and Lines

Task 6. Enabling IP Basic Setup

Task 7. Testing Asynchronous EXEC Shell Connections

Task 8. Confirming the Final Running Configuration

Commissioning

Whether you are a corporate end user or a competitive Internet service provider (ISP), you have purchased a Cisco AS5800 network access server (NAS) to provide dialup services that facilitate accessibility for remote or roaming personnel, or Internet admission to consumers for e-mail, e-commerce, and web browsing.

This chapter details Cisco AS5800 commissioning, or the formal functional setup of the equipment, through systematic software configurations, to initially prepare the system for data/voice call processing.

In our discussion, local-based authentication is used. After the Cisco AS5800 hardware is commissioned, PPP is configured and tested as described in"Configuring PPP and Authentication" section on page 3-25.

Note A AAA RADIUS server is recommended. AAA Radius server discussions are available in the "Configuring RADIUS" section on page 4-14.

Commissioning the Cisco AS5800 Hardware

This section describes configuring the Cisco AS5800 hardware to support terminal EXEC shell services and log in prompts for client modems, and includes the following:

•Understanding the Basic Hardware Architecture

•Task 1. Verifying Basic Setup

•Task 2. Configuring Basic Cisco IOS Software

•Task 3. Enabling the T3/T1 Controllers

•Task 4. Configuring the Serial Interfaces

•Task 5. Configuring Modems and Lines

•Task 6. Enabling IP Basic Setup

•Task 7. Testing Asynchronous EXEC Shell Connections

•Task 8. Confirming the Final Running Configuration

Note For a description of terminal EXEC shell services, see the "Task 7. Testing Asynchronous EXEC Shell Connections" section.

Understanding the Basic Hardware Architecture

To build an access network using the Cisco AS5800, it is necessary to understand:

•The Cisco 7206 router shelf

•The Cisco 5814 dial shelf

•Call-processing components

Cisco 7206 Router Shelf and Cisco 5814 Dial Shelf

The Cisco AS5800 access server contains:

•A Cisco 7206 router shelf (egress interface). It connects to the IP backbone.

•A Cisco 5814 dial shelf (ingress interface). It connects to the PSTN.

Figure 2-1 shows the Cisco AS5800 system architecture.

Figure 2-1 Cisco AS5800 System Architecture

Note The Cisco IOS software uses a three-element notation to specify interface and port locations: shelf/slot/port.

•The Cisco 7206 router shelf contains the following:

–Port adapters. In the example, the Cisco 7206 uses Fast Ethernet (FE) 0/1/0 to connect to the IP backbone.

–A dial-shelf interconnect (DSI) port adapter. In the example, the adapter is located at 0/2/0.

The Cisco 7206 communicates with the Cisco 5814 dial shelf through an external dial-shelf interconnect cable. The cable connects from the DSI port adapter to the dial-shelf controller (DSC) card.

The Dial Shelf Interconnect Protocol (DSIP) enables communication between the Cisco 7206 and the Cisco 5814.

–Service adapters (for example, compression and encryption).

–By default, a shelf ID of 0 is assigned to the router shelf.

•The Cisco 5814 dial shelf contains the following:

–Dial-shelf controller (DSC) cards. They fit in slots 12 or 13 only. If you have one DSC card, slot 12 is recommended. One DSC card is used in the example.

The DSC card contains its own Cisco IOS software image. For maintenance purposes only, the card can be accessed through its console port and Ethernet interface. No IP packets originating from any trunk or modem cards go out this Ethernet interface.

–T3/T1/E3/E1 cards. They connect to the PSTN and fit in slots 0 through 5 only. Slots 0 and 1 are recommended. In the example, one T3 trunk card is located at 1/0/0.

–Modem/voice cards. They fit in slots 0 through 11. In the example, nine modem cards are installed. The first modem card is in slot 2. The line-modem range is 1/2/00 to 1/10/143.

–By default, a shelf ID of 1 is assigned to the dial shelf.

•The Cisco SC3640 system controller is an external management subsystem. It interfaces with the Cisco 7206 and provides the following functions:

–SNMP and syslog offloading

–Out-of-band console access

Call-Processing Components

As shown in Figure 2-2, the following components process a call:

•Client modems and ISDN routers dial in to the access server through the PSTN.

•Asynchronous PPP calls (analog) 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.

•Synchronous PPP calls (digital) connect to serial interface channels (for example, S1/0/0:0:0 and S1/0/0:0:1).

•Synchronous interfaces clone their configurations from a dialer interface.

Figure 2-2 Cisco AS5800 Call-Processing Components

One asynchronous PPP call requires:

•(1) T1 DS0 channel

•(1) channel in a TDM bus

•(1) integrated modem

•(1) TTY line

•(1) asynchronous interface

One synchronous PPP call requires:

•(1) T1 DS0 channel

•(1) serial interface channel

Tips 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. Verifying Basic Setup

Verify that basic system components are functioning:

•Analyzing the System Boot Dialog

•Matching the Cisco IOS Software Images

•Inspecting the Dial Shelf

•Using DSIP

•Checking the Initial Running-Config

•Exploring the Cisco IOS File System

•Investigating Memory Usage

•Verifying CPU Utilization

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.

The following boot sequence occurs. Event numbers and comments are inserted in the example to describe the boot sequence.
System Bootstrap, Version x.x
Copyright (c) 20xx by cisco Systems, Inc.
C7200 processor with 131072 Kbytes of main memory
Self decompressing the image : 
##########################################################################################
################################################# [OK]
%PA-2-UNDEFPA: Undefined Port Adaptor type 106 in bay 2
%SYS-4-CONFIG_NEWER: Configurations from version 12.x may not be correctly understood.
%OIR-3-SEATED: Insert/removal failed (slot 2), check card seating
%OIR-3-SEATED: Insert/removal failed (slot 2), check card 
seatingCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Read 7314384 bytes from file slot0:c5800-p4-mz.120-4.XL1.bin
Self decompressing the image : 
##########################################################################################
##########################################################################################
##########################################################################################
##########################################################################################
####################################################### [OK]
•In the previous segment, the NAS decompresses the system boot image, tests the NVRAM for validity, and decompresses the Cisco IOS software image.

Sometimes boot images do not support hardware cards. Sample error messages look like this:
%PA-2-UNDEFPA: Undefined Port Adapter
%OIR-3-SEATED: Insert/removal failed
Ignore these messages and do not ignore error messages that appear after the Cisco IOS software image decompresses.
              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.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco Internetwork Operating System Software IOS (tm) 5800 Software (C5800-P4-M), 
Version 12.x
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 12-Aug-99 13:16 by ayeh
Image text-base: 0x60008900, data-base: 0x611A6000
cisco 7206 (NPE400) processor with 114688K/16384K bytes of memory.
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
6 slot midplane, Version x
Last reset from power-on
X.25 software, Version 3.0.0.
Bridging software.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
1 FastEthernet/IEEE 802.3 interface(s)
1296 terminal line(s)
1 Channelized T3 port(s)
125K bytes of non-volatile configuration memory.
4096K bytes of packet SRAM memory.
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
4096K bytes of Flash internal SIMM (Sector size 256K).
•The following components are detected:

–Cisco IOS release

–Available memory

–Available interfaces

Note If a hardware card is not recognized, verify that you are running the optimum version of Cisco IOS software. Refer to the hardware-software compatibility matrix available online at
http://cco-sj-1.cisco.com/cgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi

The following system message and prompt appears.
--- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]: no
•Because the NAS has never been configured, the Cisco IOS software cannot find a startup-config file. In this example, the Cisco IOS software is configured manually. The automatic setup script is not used.
00:00:52: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 12 Succeeded
00:00:53: %DSC_REDUNDANCY-3-BICLINK: Switching to DSC 12
00:00:56: %DSC_REDUNDANCY-3-BICLINK: Link to active DSC up
00:02:05: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 0 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 2 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 3 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 4 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 5 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 6 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 7 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 8 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 9 Succeeded
00:02:06: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 10 Succeeded
Press RETURN to get started!
5800>
•By using DSIP, the router shelf detects the state of each card in the dial shelf.

Depending on the number of cards in the dial shelf, there is a delay of 60 to 120 seconds before the "DSIP Hello" messages are displayed on your terminal session.

After powering up the Cisco AS5800, enter the show environment command. Verify that there are no critical grounding, heating, or power problems. The following shows an operating environment.
5800-NAS> show environment
All measured values are normal
5800-NAS> show environment all
Power Supplies:
        Power supply 1 is empty.
        Power supply 2 is Zytek AC Power Supply. Unit is on.
Temperature readings:
        chassis inlet    measured at 25C/77F 
        chassis outlet 1 measured at 27C/80F 
        chassis outlet 2 measured at 33C/91F 
        chassis outlet 3 measured at 41C/105F 
Voltage readings:
        +3.45 V measured at +3.49 V 
        +5.15 V measured at +5.21 V 
        +12.15  measured at +12.34 V 
        -11.95  measured at -11.81 V 
Envm stats saved 1 time(s) since reload
5800-NAS>
Matching the Cisco IOS Software Images

The dial shelf and router shelf run separate Cisco IOS software images:

•Both images must be from the same Cisco IOS release. They must match. Cisco IOS Release 12.0(4)XL1 is used in this example.

•The router shelf's image is in the Cisco 7206s Flash memory. It begins with "c5800." The dial shelf's image is in the DSC card. It begins with "dsc."

On the router shelf, check the Cisco IOS software image, uptime, and restart reason:
5800# show version
Cisco Internetwork Operating System Software IOS (tm) 5800 Software (C5800-P4-M), Version 
12.x
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 12-Aug-99 13:16 by ayeh
Image text-base: 0x60008900, data-base: 0x611A6000
ROM: System Bootstrap, Version xCA, 
BOOTFLASH: 7200 Software (C7200-BOOT-M), Version x
Router uptime is 2 minutes
System returned to ROM by reload
System image file is "slot0:c5800-p4-mz.120-4.XL1.bin"
cisco 7206 (NPE400) processor with 114688K/16384K bytes of memory.
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
6 slot midplane, Version x
Last reset from power-on
X.25 software, Version 3.0.0.
Bridging software.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
1 FastEthernet/IEEE 802.3 interface(s)
1296 terminal line(s)
1 Channelized T3 port(s)
125K bytes of non-volatile configuration memory.
4096K bytes of packet SRAM memory.
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
4096K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2102
Table 2-1 describes the significant output fields in the previous display:
Table 2-1 Show Version Command Field Descriptions
Field

Description
5800 Software (C5800-P4-M), 
Version 12.x
Cisco IOS software 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. If the field displays "power-on," a power interruption caused the reload.
System image file is 
"slot0:c5800-p4-mz.120-4.XL1
.bin"
The Cisco 7206 router shelf booted from the external PCMCIA Flash card at slot 0.

The router shelf does not have internal Flash memory. If the PCMCIA Flash card is missing, the router shelf will not boot.
On the dial shelf, check the Cisco IOS software image, uptime, and restart reason. If you do not have a physical console connection to the dial shelf, enter the execute-on slot [12 | 13] show version command. The DSC can be in slot 12 or 13.
5800# execute-on slot 12 show version
DA-Slot12>
Cisco Internetwork Operating System Software IOS (tm) 5800 Software (C5800-DSC-M), Version 
12.x
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 12-Aug-99 18:48 by ayeh
Image text-base: 0x600088F0, data-base: 0x60520000
ROM: System Bootstrap, Version xAA
ROM: 5800 Software (C5800-DSC-M), Version xAA2
DA-Slot12 uptime is 20 hours, 38 minutes
System returned to ROM by reload
System image file is "slot0:dsc-c5800-mz.120-4.XL1.bin"
cisco c5800 (R4K) processor with 24576K/8192K bytes of memory.
R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache
Last reset from power-on
1 Ethernet/IEEE 802.3 interface(s)
2 Dial Shelf Interconnect(DSI) FE interface(s)
123K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
4096K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2102
Inspecting the Dial Shelf

Verify that feature cards are up (T3, T1, E3, E1, modem, or voice):
5800# show dial-shelf
Slot    Board     CPU       DRAM          I/O Memory   State         Elapsed
         Type     Util    Total (free)   Total (free)                Time
 0        CT3    0%/0%  21598976( 81%)  8388608( 41%)  Up            00:01:35
 2 Modem(DMM)  20%/20%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 3 Modem(DMM)    0%/0%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 4 Modem(DMM)  20%/20%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 5 Modem(DMM)  20%/20%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 6 Modem(DMM)  40%/40%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 7 Modem(DMM)  40%/40%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 8 Modem(DMM)  35%/35%  46764800( 86%) 16777216( 74%)  Up            00:01:35
 9 Modem(DMM)    0%/0%  46764800( 86%) 16777216( 74%)  Up            00:01:35
10 Modem(DMM)  20%/20%  46764800( 86%) 16777216( 74%)  Up            00:01:34
12        DSC    0%/0%  19097792( 79%)  8388608( 66%)  Up            00:02:49
Dial shelf set for auto boot
5800#
•Always power up the dial shelf before the router shelf. Allow two to three minutes for the DSC card to take an inventory of the dial shelf.

•If the DSC card goes down after the feature cards are up, the system will still function properly. This event will not bring down the system. However, online insertion and removal (OIR) will not work.

•Possible dial-shelf states include: unknown, down, resetting, booting, and up. The "Up" state means that the card can communicate with the router shelf.

•Each modem card contains its own DRAM memory. Double-density modem modules (DMM) require at least 64 MB of memory with Cisco IOS Release 12.0. Hex modem modules (HMM) require at least 32 MB with Cisco IOS Release 11.3. Each card performs its own call processing.

•A fully populated DMM card contains 144 modems. The dial shelf in the example contains 1296 modems.

•A normal CPU utilization range for modem cards is between 20 to 40 percent.

DSC Troubleshooting Tips

If the DSC card does not come up, perform the following troubleshooting steps. If the DSC card never comes up, the feature cards in the dial shelf cannot communicate with the router shelf.

Step 1 Look for LED lights on the DSC card. If the lights are off, try reseating the card.

Step 2 Verify that the DSI port adapter on the Cisco 7206 is inserted correctly.

Step 3 Verify that the cable between the DSI port adapter and the DSC card is connected correctly.

Step 4 From the Cisco 7206, verify that the DSI-Fast Ethernet interface and line protocol are up:
5800> show dsi
DSI-Fastethernet0/2/0 is up, line protocol is up 
  Hardware is DEC21140A, address is 0030.f2f5.1438 (bia 0030.f2f5.1438)
  MTU 0 bytes, BW 100000 Kbit, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
Note The following example shows a dial-shelf interconnection that changes state to up after the DSC card reloads. Loss of DSIP Keepalive messages indicate no communication between the router shelf and dial shelf. After DSIP Hello messages succeed, the Fast Ethernet DSI-Tx 0 and DSI-Rx 1 change their state to up. Until these interfaces are up, the router shelf and dial shelf cannot communicate. No debug commands are used to create these console messages; however, the terminal monitor command is required to view messages.
5800#
00:04:29: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from shelf 1 slot 12
00:05:12: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 12 Succeeded
00:05:18: %DIAL12-3-MSG: 
00:00:03: %LINK-3-UPDOWN: Interface DSI-Tx-FastEthernet0, changed state to up
00:00:03: %LINK-3-UPDOWN: Interface DSI-Rx-FastEthernet1, changed state to up
00:00:03: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up
5800#
Note Verify that console logging is disabled. Enter the show logging command. If logging is enabled, the access server might intermittently freeze up as soon as the console port gets overloaded with log messages. Enter the no logging console command.

The following messages appear on the console-terminal session after the DSC card is physically removed from slot 12 and re-inserted. Approximately 120 seconds elapse before all these messages appear.
5800>
04:41:42: %DSC_REDUNDANCY-3-BICLINK: Link to active DSC down
04:42:13: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se1/0/0:4:23, TEI 0 changed to down
04:42:14: %DSC_REDUNDANCY-3-BICLINK: Link to active DSC up
04:42:36: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from shelf 1 slot 2
04:42:36: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from shelf 1 slot 3
04:42:46: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from shelf 1 slot 0
04:42:46: %DSIPPF-5-DS_KEEPALIVE_LOSS: DSIP Keepalive Loss from shelf 1 slot 12
04:42:53: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 12 Succeeded
04:44:59: %DSIPPF-5-DS_HELLO: DSIP Hello from shelf 1 slot 0 Succeeded
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
5800>
The following boot sequence occurs in the previous example:

a. The DSC card takes 32 seconds to boot up. Afterwards, the card checks the dial shelf's inventory.

b. The dial shelf exchanges hardware inventory information with the router shelf. After the exchange, the router shelf instructs the DSC card to load the appropriate boot images into the feature cards.

c. More than two minutes elapse before the DSC card detects the first "DSIP Hello" message from the first feature card (in shelf 1 slot 0). If the DSC card never comes up, the feature cards in the dial shelf cannot communicate with the router shelf.

d. The router shelf gives the feature cards the appropriate images.

Step 5 If the DSC card is still down, the card might have an incorrect Cisco IOS software image, or the Flash card is missing (ROM monitor mode). Open a physical console connection to the DSC card, copy an image into boot Flash memory, and re-initialize the system.

Step 6 For advanced troubleshooting measures after the DSC card is up, open a virtual-console session to the DSC card (DA-Slot12). To end the session, enter Ctrl C three times:
5800# dsip console slave 12
Trying Dial shelf slot 12 ...
Entering CONSOLE for slot 12
Type "^C^C^C" to end this session
DA-Slot12>
DA-Slot12#
DA-Slot12#
DA-Slot12#
Terminate NIP IO session? [confirm]
[Connection to Dial shelf slot 12 closed by local host]
5800#
Caution The router shelf provides the DSC card with the required configuration. Do not change the DSIP settings in the DSC card configuration.

Feature-Card Troubleshooting Tips

If the show dial-shelf command reports that feature cards are booting for extended periods of time, start debugging from the router shelf by using the following commands:
debug dsip transport
debug dsip trace
show dsi
•Debug dsip transport shows the registered MAC address sent from each feature board.

•Debug dsip trace displays detailed DSIP Hello and Keepalive messages.

•Debug dsip boot shows if the router shelf is sending the boot image to the feature cards.

Using DSIP

The router shelf communicates with the dial shelf using:

•Fast Ethernet interconnect cable

•Dial Shelf Interconnect Protocol (DSIP)

For the DSIP command reference and other system management functions, refer to Dial and System Management Commands for the Cisco AS5800, available online at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113aa/113aa_2/58cfeats/c5800uas.htm

To understand how DSIP functions, enter commands from the following bullet list:

•Verify that the connection between the router shelf and dial shelf is up. The DSI-Fast Ethernet interface is located at 0/2/0 in the Cisco 7206. Note that the output from the show dsi command is different from the show dsip command.
5800-NAS# show dsi
DSI-Fastethernet0/2/0 is up, line protocol is up 
  Hardware is DEC21140A, address is 00d0.d342.4c38 (bia 00d0.d342.4c38)
  MTU 0 bytes, BW 100000 Kbit, DLY 100 usec,
        reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
•Verify that each feature card's MAC address is registered by DSIP. Unregistered cards cannot communicate with the system. Shelf 0 is the router shelf (master). Shelf 1 is the dial shelf (slave).
5800# show dsip transport 
DSIP transport statistics:
 IPC  : input msgs=4309, bytes=509139; output msgs=4308, bytes=291468
        total consumed ipc msgs=2133;  total freed ipc msgs = 2133
        transmit contexts in use = 13, free = 243, zombie = 0, invalid = 0
        ipc getmsg failures = 0, ipc timeouts=0
        core getbuffer failures=0, api getbuffer failures=0
        dsip test msgs rcvd = 0, sent = 0
 CNTL : input msgs=20927, bytes=738902; output msgs=20350, bytes=29816080
        getbuffer failures=0
 DATA : input msgs=1076, bytes=38736; output msgs=0, bytes=0
DSIP Private  Buffer Pool Hits  = 0
DSIP registered addresses:
 Shelf0 : Master: 00d0.d342.4c38, Status=local
 Shelf1 : Slot0 : 0090.bf52.4e00, Status=remote
 Shelf1 : Slot2 : 0090.bf52.4e10, Status=remote
 Shelf1 : Slot3 : 0090.bf52.4e18, Status=remote
 Shelf1 : Slot4 : 0090.bf52.4e20, Status=remote
 Shelf1 : Slot5 : 0090.bf52.4e28, Status=remote
 Shelf1 : Slot6 : 0090.bf52.4e30, Status=remote
 Shelf1 : Slot7 : 0090.bf52.4e38, Status=remote
 Shelf1 : Slot8 : 0090.bf52.4e40, Status=remote
 Shelf1 : Slot9 : 0090.bf52.4e48, Status=remote
 Shelf1 : Slot10: 0090.bf52.4e50, Status=remote
 Shelf1 : Slot12: 0090.bf52.4e60, Status=remote
5800#
•Verify that all feature cards are running DSIP versions that are compatible with the router shelf:
5800# show dsip version
DSIP version information:
------------------------
Local DSIP major version =  5,   minor version = 2
All feature cards are running DSIP versions compatible with router shelf
Local clients registered versions:
------------------------------------
Client Name      Major Version   Minor Version
Console          5               2            
Clock            2               1            
Modem            0               0            
Logger           No version      No version   
TDM              No version      No version   
Trunk            No version      No version   
Async data       No version      No version   
VOICE            0               0            
Dial shelf       1               1            
Environment      No version      No version   
FILESYS          No version      No version   
DSC Red. UI      0               1            
Split DS         No version      No version   
DSIP Test        No version      No version   
Mismatched  remote client versions:
-----------------------------------
5800#
Note This command also reports mismatched Cisco IOS software versions. No mismatches exist in this example.

Checking the Initial Running-Config

The Cisco IOS software creates an initial running configuration. To familiarize yourself with default settings, inspect the software configuration as follows:

Step 1 Display the configuration on the Cisco 7206 router shelf:
5800# show running-config
Building configuration...
Current configuration:
!
version 12.x
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
!
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
!
isdn voice-call-failure 0
!
!
controller T3 1/0/0
 cablelength 224
!
!
process-max-time 200
!
interface FastEthernet0/1/0
 no ip address
 no ip directed-broadcast
 shutdown 
!
interface Group-Async0
 no ip address
 no ip directed-broadcast
 group-range 1/2/00 1/10/143
!
ip classless
no ip http server
!
!
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, display the configuration on the Cisco 5814 dial shelf:
5800# execute-on slot 12 show running-config 
DA-Slot12#
Building configuration...
Current configuration:
!
version 12.x
service config
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname DA-Slot12
!
!
ip subnet-zero
!
!
process-max-time 200
!
interface Ethernet0
 no ip address
 no ip directed-broadcast
 shutdown
!
no ip http server
ip classless
!
!
line con 0
 transport input none
line vty 0 4
!
end
Exploring the Cisco IOS File System

Familiarize yourself with the file system and memory storage areas. The Cisco IOS file system 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).

Figure 2-3 shows the memory locations inside the Cisco AS5800.

Figure 2-3 Cisco AS5800 Memory Locations

Table 2-2 describes the memory locations shown in Figure 2-3.

Table 2-2 Memory Location Descriptions

Component

Description

CPU (NPE400)

Central processing unit.

Processor memory

The Cisco IOS software 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.

Packet I/O memory

Packets are temporarily stored in I/O memory.

slot0: flash:
slot1:

PCMCIA Flash memory cards in the router shelf. They store Cisco IOS software images, modem firmware/portware, and custom web pages.

bootflash:

Flash memory on the Cisco 7206's motherboard.

nvram:

Nonvolatile configuration memory.

dsc12-slot0:
dsc12-slot1:

PCMCIA Flash memory cards in the DSC card.

dsc12-bootflash:

Flash memory on DSC card's motherboard.

dsc12-nvram:

Nonvolatile configuration memory in the DSC card.

To verify the file system, enter commands from the following bullet list:

•View the different file storage areas and file management functions. Additionally, verify that you have everything you ordered from manufacturing, such as Flash memory. The asterisk (*) indicates the current directory.
5800# show file systems
File Systems:
     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -     flash     rw   disk0:
           -           -     flash     rw   disk1:
           -           -    opaque     rw   null:
           -           -    opaque     rw   system:
           -           -   network     rw   tftp:
      129016      128277     nvram     rw   nvram:
*   20578304    13263792     flash     rw   slot0: flash:
           -           -     flash     rw   slot1:
     3407872     1286636     flash     rw   bootflash:
           -           -    opaque     wo   lex:
           -           -   network     rw   rcp:
           -           -   network     rw   pram:
           -           -   network     rw   ftp:
     7995392     5825440     flash     rw   dsc12-slot0:
           -           -     flash     rw   dsc12-slot1:
     3407872     1575412     flash     rw   dsc12-bootflash:
      126968      126968     nvram     rw   dsc12-nvram:
5800#
•Display the objects in the system memory directory:
5800# dir system:
Directory of system:/
  2  dr-x           0              <no date>  memory
  1  -rw-         787              <no date>  running-config
No space information available
5800#
Tips Remember to include the trailing colon (:) in the dir commands.

•Inspect the Flash memory on the router and dial shelves. Both images must have matching Cisco IOS release number. In this example, both images are from Cisco IOS Release 12.0(4)XL1. As the chassis boots up, the images are copied, decompressed, and loaded into DRAM memory.
5800# pwd
slot0:
5800# dir
Directory of slot0:/
  1  -rw-     7314384   Sep 13 1999 20:03:41  c5800-p4-mz.120-4.XL1.bin
20578304 bytes total (13263792 bytes free)
5800#
5800# dir dsc12-slot0:
Directory of dsc12-slot0:/
  1  -rw-     2169824   Sep 13 1999 20:28:53  dsc-c5800-mz.120-4.XL1.bin
7995392 bytes total (5825440 bytes free)
5800#
•Inspect the bootFlash on both shelves:
5800# dir bootflash:
Directory of bootflash:/
  1  -rw-     2121108   Jan 01 2000 00:00:48  c7200-boot-mz.111-24.CC
3407872 bytes total (1286636 bytes free)
Router
5800# dir dsc12-bootflash:
Directory of dsc12-bootflash:/
  1  -rw-     2169824   Nov 18 1999 22:18:30  dsc-c5800-mz.120-4.XL1.bin
3407872 bytes total (1237920 bytes free)
Tips Keep a backup copy of the dial shelf's image in boot Flash. Someone may take PCMCIA Flash cards without notification. The dial shelf does not have its own connection to the IP backbone for image upgrade purposes.

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. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Squeeze of dsc12-bootflash complete
5800-NAS#
•Inspect the NVRAM memory on the router and dial shelves. Three files are present:

– The initial boot or startup-config.

–The private-config is a secure file that supports encryption technologies. It is not user accessible.

–The underlying-config is the version of the startup-config that is stored in NVRAM.
5800# dir nvram:
Directory of nvram:/
  1  -rw-         739              <no date>  startup-config
  2  ----          24              <no date>  private-config
  3  -rw-         739              <no date>  underlying-config
129016 bytes total (128277 bytes free)
5800#
5800# dir dsc12-nvram:
Directory of dsc12-nvram:/
  1  -rw-           0              <no date>  startup-config
  2  ----           0              <no date>  private-config
  3  -rw-           0              <no date>  underlying-config
126968 bytes total (126968 bytes free)
5800#
Investigating Memory Usage

Use the show memory summary command to:

•Determine how memory is used for different processor and I/O memory processes.

•Identify memory fragmentation and memory leaks.

–Memory leaks—Memory that is not released back to the processor. Memory leaks are indicated by steady decreases of free memory. However, the preferred way to track memory leaks is to monitor the FreeMem variable in the OID MIB.

–Memory fragmentation—Indicated by the largest block of memory not being equal to the free block. Fragmentation increases as the numbers grow further apart.

To inspect and calculate memory usage complete the following steps:

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.
5800-NAS# show memory summmary
                Head   Total(b)    Used(b)    Free(b)  Lowest(b) Largest(b)
 Processor  6164D4E0   94055200   42346480   51708720   50435436   51592056
       I/O   7000000   16777216    6433400   10343816   10343816   10343772
       PCI  4B000000    4194304     618584    3575720    3575720    3575676
Caution If you enter the show memory summary command with the terminal length 0 command enabled you will produce many screens of output which might interrupt your session.

Table 2-3 describes the significant fields in the previous display:

Table 2-3 Show Memory Summary Output Field Descriptions

Field

Description

Processor

Processor memory. The Cisco IOS software image is initially read out of Flash memory, decompressed, and placed in main memory. Routing tables and call control blocks are also stored in main memory.

I/O

Packets are temporarily stored in I/O memory.

Head

Hexadecimal address of the head of the memory allocation chain.

Total(b)

Summary of used bytes plus free bytes.

Used(b)

Total number of bytes currently used for routing tables and call-processing components.

Free(b)

Total number of free bytes. The free memory size should be close to the largest block available.

Lowest(b)

Smallest amount of free memory since last boot.

Largest(b)

Size of largest available free block. Whenever the largest available block is equal to the free block, there is no fragmentation.

Step 2 Convert bytes to megabytes (MB):

•Total processor memory = 9,4055,200 bytes = 89.7 MB

•Used processor memory = 42,346,480 bytes = 40.4 MB

•Free processor memory = 51,708,720 bytes = 49.3 MB

Total memory (89.7 MB) = Used memory (40.4 MB) + free memory (49.3 MB)

Step 3 Do some useful memory calculations:

Total Processor = Total RAM - Cisco IOS software (use the show version command to get the MB assigned for all of Cisco IOS software + Processor)
cisco 7206 (NPE400) 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 112.0 MB - 89.7 MB = 22.3 MB. This means that 22.3 MB are not available for processor memory.

Verifying CPU Utilization

High utilization causes network performance problems. Knowing when the router is running at over 50% utilization is critical because the router might start dropping packets if an unexpected traffic burst comes through or if OSPF gets recalculated. Fast switching reduces CPU utilization.
5800# show processes cpu
CPU utilization for five seconds: 20%/6%; one minute: 31%; five minutes: 19%
 PID  Runtime(ms)  Invoked  uSecs    5Sec   1Min   5Min TTY Process 
   1      144208   1526300     94   0.00%  0.00%  0.00%   0 Load Meter 
   2      118732  19749060      6   0.24%  0.12%  0.08%   0 OSPF Hello 
   3    42752544   2699659  15836   3.75%  0.87%  0.62%   0 Check heaps 
   4        7260     30062    241   0.00%  0.00%  0.00%   0 Pool Manager 
   5           0         2      0   0.00%  0.00%  0.00%   0 Timers 
   6        1472    494101      2   0.00%  0.00%  0.00%   0 Serial Background 
   7       49424   7631216      6   0.00%  0.00%  0.00%   0 EnvMon 
   8           0         1      0   0.00%  0.00%  0.00%   0 OIR Handler 
   9    13368616   3217631   4154   0.32%  0.57%  0.42%   0 ARP Input 
  10       18932    533419     35   0.00%  0.00%  0.00%   0 DDR Timers 
  11         116         4  29000   0.00%  0.00%  0.00%   0 Entity MIB API 
Look at the top line of the output. If you see utilization at the top of the display over 50%, inspect the columns 5Sec, 1Min, and 5Min. Find the process that uses the most CPU power. For an idle chassis, numbers larger than two percent indicate a problem.

Table 2-4 describes the significant output fields in the previous example:
Table 2-4 CPU Utilization Display Fields
Field

Description
CPU utilization for five seconds: 
2%/0%; 
The first % number is the CPU utilization for the last 5.0 seconds. The second % number is the percentage of CPU time spent at the packet-based interrupt level.
one minute: 1%; 
CPU utilization for the last minute.
five minutes: 14%
CPU utilization for the last 5.0 minutes.
Whenever memory cannot be allocated to a process request (a memory leak), a console error message appears:
Sep 14 11:30:33.339 EDT: %SYS-2-MALLOCFAIL: Memory allocation of 19960
bytes failed from 0x603D530C, pool Processor, alignment 0
 -Process= "Exec", ipl= 0, pid= 48
 -Traceback= 603D8610 603DAA70 603D5314 603D5AF0 60373054 60371474 603C33DC
603C3538 603C4378 60371934 603586B8 60358A10 6037C12C 6037C1E4 60372E9C
6037EDEC
To identify the problem, inspect the first few output lines of the show memory summary command and show processor memory command.

Task 2. Configuring Basic Cisco IOS Software

Apply a basic-running configuration to the NAS:

•Configuring the Host Name, Enable Secret Password, and Time Stamps

•Configuring Local AAA Security

•Setting Up a Log In Banner

•Configuring Basic IP

Tips Periodically save the configuration by using the copy running-config startup-config command.

Configuring the Host Name, Enable Secret Password, and Time Stamps

Assign a host name to the NAS, specify an enable secret password, and turn on time stamps:

•A host name allows you to distinguish between different network devices.

•A secret enable password allows you to prevent unauthorized configuration changes.

•Encrypted passwords in the configuration file add greater security to the NAS.

•Time stamps help you trace debug output for testing connections. Not knowing exactly when an event occurs prevents you from tracing debug output for testing conditions.

Step 1 Enter the following commands in global configuration mode:
hostname 5800-NAS
enable secret yourpassword
service password-encryption
service timestamps debug datetime msec
service timestamps log datetime msec
Note Do not use the enable password command.

Step 2 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#
Configuring Local AAA Security

Configure 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 is the Cisco IOS software security model used on all Cisco devices. AAA provides the primary framework through which you set up access control on the NAS.

In this basic discussion, the same authentication method is used on all interfaces. AAA is set up to use the local database configured on the NAS. This local database is created with the username configuration commands.

Step 1 Create a local login username database in global configuration mode. In this example, the administrator's username is admin. The remote client's login username is dude.
!
username admin password adminpasshere
username dude password passhere
!
Caution This prevents you from getting locked out of the NAS. If you get locked out, you must reboot the device and perform password recovery.

Step 2 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
!
Table 2-5 describes the configuration:

Table 2-5 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.

aaa authentication ppp default if-needed local

Configures PPP authentication to use the local database if the session was not already authenticated by login.

Step 3 Log in with your username and password:
5800-NAS# login
User Access Verification
Username:admin
Password:
5800-NAS#
A successful login means that your local username works on any TTY or VTY line. Do not disconnect your session until you can log in.

Setting Up a Log In Banner

Create a login banner. However, do not tell users what device they are connecting to until after they log in. Providing device sensitive information can tempt unauthorized users to hack into the system.

Step 1 Create the banner:
5800-NAS(config)# banner login |
Enter TEXT message.  End with the character '|'.
This is a secured device. 
Unauthorized use is prohibited by law.
|
5800-NAS(config)#^Z
5800-NAS#
Step 2 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#
Configuring Basic IP

To configure a basic dial access service:

•Configure two loopback interfaces.

•Bring up one Fast Ethernet interface.

•Add an IP route to the default gateway.

Follow this procedure:

Step 1 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.0
!
interface FastEthernet0/1/0
 ip address 172.22.66.23 255.255.255.0
!
ip route 0.0.0.0 0.0.0.0 172.22.66.1
!
The loopback interfaces are used for the following reasons:

•Interface loopback 0: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. One class C subnet, that was used to identify devices, can support 254 distinct nodes with unique loopback IP addresses.

•Interface loopback 1:Hosts a pool of IP addresses for the remote nodes. In this way, one route is summarized and propagated to the backbone instead of 254 host routes.

Step 2 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. If the ping succeeds to the default gateway, try pinging the DNS server in your backbone. Make sure the backbone is configured to get to the access server; otherwise, the ping will not work. Configure the backbone routers to support the routes to the networks you are using.

Note An 80% ping-success rate is normal for the first time you ping an external device. The NAS does not yet have an address resolution protocol (ARP) entry for the external device. A 100% success rate is achieved the next time you ping the device.

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 2-4 displays the logical controller components inside a Cisco AS5800. The figure shows that a T3 trunk card requires T1 and T3 controller configuration settings. In the figure, only the fourth controller is configured. There are a total of 28 T1 controllers to configure.

Figure 2-4 Matching Controller Settings

Step 1 Define the ISDN PRI switch type. In the example, the T1 trunks are not using channel associated signaling (CAS).
!
isdn switch-type primary-ni
!
There are two ways to define the switch type:

•Under the individual serial-D channels. A different switch type can be defined for each PRI trunk. See the "Task 4. Configuring the Serial Interfaces" section.

•Globally across all PRI trunks. All trunks use the same switch type.

Note For T1 CAS trunks, no ISDN switch type is configured.

Step 2 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 controllers controller t1 1/0/0:4. The number of logical T1 controllers should match the number of TI PRI lines coming into your T3.
!
controller T3 1/0/0
 framing m23
 cablelength 0
 t1 4 controller
!
Step 3 Configure the corresponding T1 controllers:
!
controller t1 1/0/0:4
 framing esf
 pri-group timeslots 1-24
!
After the controllers are correctly configured, the following cards and interfaces change state:
00:01:59: %CONTROLLER-5-UPDOWN: Controller T3 1/0/0, changed state to up
00:02:01: %CONTROLLER-5-UPDOWN: Controller T1 1/0/0:4, changed state to up
00:02:02: %DIAL12-3-MSG:
07:08:54: %DSCCLOCK-3-SWITCH3: Clock moving to NORMAL from HOLDOVER, selected clock is on 
slot 0 port 4 line 0
00:02:05: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se1/0/0:4:23, TEI 0 changedto down
00:02:21: %ISDN-6-LAYER2UP: Layer 2 for Interface Se1/0/0:4:23, TEI 0 changed to up
5800-NAS> 
Table 2-6 describes some of the T3 and T1-controller concepts that are applied in the previous steps.

Table 2-6 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. The remaining 6k is used for error detection, CRC, and data link monitoring. ESF is recommended for PRI configurations.

•SF—Super frame. SF (D4) is used in channel bank robbed bit signalling (RBS) configurations. The in-band signaling occurs within the 6th and 12th frames. SF uses the framing bit for frame synchronization. SF is not recommended for PRI configurations.

Line code type

An encoding method used to allow synchronous data to be transmitted in a compatible format. Common line codes are RZ (return to zero), NRZ (non-return to zero), B8ZS, AMI, and HDB3.

•AMI—Alternate mark inversion. Signal transitions are referenced by a binary 1 (mark). AMI is used on older T1 circuits. B8ZS is more reliable than AMI.

•B8ZS—Most popular line-code scheme used in North America. To maintain clock synchronization, B8ZS replaces string 8 binary 0s with variations. B8ZS is more reliable than AMI, and it should be used with PRI configurations.

Clock source

Refers to both timing and synchronization of the T1 carrier. Timing is encoded within the transmitted data signal, and it ensures synchronization throughout the network.

Clocks are prioritized by slot number (slot 0 to slot 5). The highest priority clock is selected from the card in slot 0. If this clock fails, the highest priority clock from the card in slot 1 becomes the default clock, and so forth.

Timeslot assignment

Timeslots are assigned to channels. For T1 PRI scenarios, all 24 T1 timeslots are assigned as ISDN PRI channels. After timeslots are assigned by the pri-group command, D-channel serial interfaces are automatically created in the configuration file (for example S1/0/0:0:23, S1/0/0:1:23, and so on).

Step 4 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.
  FEAC code received: No code is being received
  Framing is M23, Line Code is B3ZS, Clock Source is Internal
  Data in current interval (201 seconds elapsed):
     0 Line Code Violations, 0 P-bit Coding Violation
     0 C-bit Coding Violation, 0 P-bit Err Secs
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs
     0 Unavailable Secs, 0 Line Errored Secs
     0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
  Total Data (last 1 15 minute intervals):
     30664 Line Code Violations, 49191 P-bit Coding Violation,
     47967 C-bit Coding Violation, 0 P-bit Err Secs,
     0 P-bit Severely Err Secs, 0 Severely Err Framing Secs,
     2 Unavailable Secs, 0 Line Errored Secs,
     10 C-bit Errored Secs, 10 C-bit Severely Errored Secs
5800-NAS# 
5800-NAS# show controller T1 1/0/0:4
T1 1/0/0:4 is up.
  Applique type is Channelized T1
  Cablelength is short
  No alarms detected.
  Framing is ESF, Line Code is AMI, Clock Source is Line.
  Data in current interval (240 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 1:
     0 Line Code Violations, 8 Path Code Violations
     11 Slip Secs, 26 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 26 Unavail Secs
  Total Data (last 1 15 minute intervals):
     0 Line Code Violations, 8 Path Code Violations,
     11 Slip Secs, 26 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 26 Unavail Secs
5800-NAS#
After each controller is correctly set up, clear the counters and look for ongoing line violations and errors. To do this, enter the clear counters command followed by the show counters command:
clear counters t1 1/0/0:4
show counters t1 1/0/0:4
Step 5 In the display output, focus on the data in the current interval. Error counters stop increasing when the controller is configured correctly.

Tips The clear counters command does not reset or bring down the controller. The T1 stays up. Only the counters are cleared.

From the reference point of the NAS, Table 2-7 provides a list of T1 alarm conditions and descriptions.

Table 2-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.

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. In SF and ESF formats, OOF occurs when any two of four consecutive frame-synchronization bits are in error.

Loss of Signal (LOS)

Occurs when 175 consecutive 0s are detected in the MC. This is a red alarm. The signal is recovered if the density of 1s reaches 12.5%. The recovery happens when four 1s are received within a 32-bit period.

Remote Frame Alarm (RHEA)

Indicates that an OOF framing pattern occurred at the remote end. This is a yellow alarm.

Alarm Indication Signal (AIS)

Indicates to the remote end a loss of the received signal. This is a blue alarm. AIS occurs when a stream of 1s is received.

Loopback

Indicates that a remotely initiated loopback (from the network) is in progress.

Errored Seconds

Depending on the framing format, indicates OOF conditions, frame slip conditions, or error events.

For SF, errored seconds reports the number of seconds the frame was in the OOF or slip condition. For ESF, errored seconds reports error events in seconds.

Bursty Errored Seconds

Reports CRC error conditions in seconds (ESF format only).

Severely Errored Seconds

Reports error events or frame slip conditions in seconds.

For more information about controllers, see the information on channelized E1 and channelized T1 setup commands in Dial-In Port Setup, available online at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/dial_r/drprt1/index.htm

Step 6 Verify that individual serial D channels are created. B channels S1/0/0:4:0 through S1/0/0:4:22 are rotary members (dialers) of the signaling D channel S1/0/0:4:23.
5800-NAS# show ip interface brief | inc :23
Serial1/0/0:4:23           unassigned      YES NVRAM  up       up
5800-NAS#
Step 7 Additionally, enter the show interface S1/0/0:4:23 command to verify the serial interface.

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 2-8 describes the relationship between T1 controllers and serial interfaces.

•After timeslots are assigned by the pri-group command, D-channel serial interfaces are automatically created in the configuration file (for example, S1/0/0:0:23, S1/0/0:1:23, and so on).

•Individual B-channel serial interfaces are created as rotary members (dialers) of their signaling D-channels (for example, S1/0/0:0:0 through S1/0/0:0:22). The D-channel interface functions like a dialer for all the 23 B-channels using the controller.

•An ISDN switch type defined on the global level is automatically propagated to the serial D-channel interface level. However, a switch type defined on the serial-interface level overrides a switch type defined on the global level.

Table 2-8 Controller-to-Channel Relationships

T1 Controllers

D Channels

B Channels

Controller T1 1/0/0:0

Interface serial 1/0/0:0:23

S1/0/0:0:0 through S1/0/0:0:22

Controller T1 1/0/0:1

Interface serial 1/0/0:1:23

S1/0/0:1:0 through S1/0/0:1:22

Controller T1 1/0/0:2

Interface serial 1/0/0:2:23

S1/0/0:2:0 through S1/0/0:2:22

Controller T1 1/0/0:3

Interface serial 1/0/0:3:23

S1/0/0:3:0 through S1/0/0:3:22

Controller T1 1/0/0:4

Interface serial 1/0/0:4:23

S1/0/0:4:0 through S1/0/0:4:22

...

...

...

Step 1 Apply the isdn incoming-voice modem command to each D-channel serial interface. In this example, one interface is configured.
!
interface Serial1/0/0:4:23
 isdn incoming-voice modem
!
Step 2 Verify that ISDN is functioning properly, and the serial channels are up:

•Check the ISDN status. Confirm that Layer 1 reports ACTIVE, and the display field MULTIPLE_FRAME_ESTABLISHED appears at Layer 2. For PRI lines, the terminal endpoint identifier (TEI) is always 0. The Layer 3 status reports no active calls.
5800-NAS# show isdn status
Global ISDN Switchtype = primary-ni
ISDN Serial1/0/0:4:23 interface
        dsl 0, interface ISDN Switchtype = primary-ni
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Activated dsl 0 CCBs = 0
    The Free Channel Mask:  0x807FFFFF
    Total Allocated ISDN CCBs = 0
•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.
5800-NAS# show isdn service
PRI Channel Statistics:
ISDN Se1/0/0:4:23, Channel [1-24]
  Configured Isdn Interface (dsl) 0
  Channel State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 
  Service State (0=Inservice 1=Maint 2=Outofservice)
  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
5800-NAS# 
Step 3 Test the configuration by sending a POTS call into the Cisco AS5800 network access server (NAS). If the modem answers (you hear modem squelch), the configuration works. In Figure 2-5, a different telephone number is associated with each end of the connection.

Figure 2-5 Sending a POTs Telephone Call to a NAS

Note The debug ISDN q931 command (with logging console enabled) displays incoming call information on the monitor.

•In the called party number is the dial number identification service (DNIS). It identifies the directory number assigned to the Cisco AS5800's PRI trunks. In Figure 2-5, the telephone dialed 555-1234.

•In the calling part number is the automatic identification number (ANI). It identifies the directory number assigned to the device that initiates the call. In this example, the telephone line is assigned 444-1234.

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.

AAA security is applied to the lines by the aaa new-model command and aaa authentication login default local command. AAA performs login authentication by using the local username database. The login keyword authenticates EXEC shell users.

Note The modem speed (115200 bps) and hardware flow control are the defaults for integrated modems.

Step 1 Configure modem control (DCD/DTR) for incoming and outgoing modem calls:
!
line 1/2/00 1/10/143
 modem InOut
!
Note The no modem log rs232 command limits the size of the show modem log command's output.

Step 2 Familiarize yourself with the modem-numbering scheme for the Cisco AS5800. Modems use the shelf/slot/port notation.
5800-NAS# show modem 
  Codes:
  * - Modem has an active call
  T - Back-to-Back test in progress
  R - Modem is being Reset
  p - Download request is pending and modem cannot be used for taking calls
  D - Download in progress
  B - Modem is marked bad and cannot be used for taking calls
  b - Modem is either busied out or shut-down
  d - DSP software download is required for achieving K56flex connections
  ! - Upgrade request is pending
            Avg Hold     Inc calls     Out calls   Busied   Failed     No   Succ
    Mdm       Time      Succ   Fail   Succ   Fail   Out      Dial    Answer  Pct
    1/2/00  00:00:00       0      0      0      0       0        0       0    0%
    1/2/01  00:00:00       0      0      0      0       0        0       0    0%
    1/2/02  00:00:00       0      0      0      0       0        0       0    0%
    1/2/03  00:00:00       0      0      0      0       0        0       0    0%
    1/2/04  00:00:00       0      0      0      0       0        0       0    0%
Step 3 Choose a specific modem and inspect the modem-to-TTY line association. TTY lines are simulated EIA/TIA-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 the example, the first modem card is in slot—that is, slot 0 and slot 1 do not contain modem cards.
5800-NAS# show modem 1/2/00
     Mdm  Typ     Status     Tx/Rx     G  Duration  RTS   CTS   DCD   DTR
     ---  ---     ------     -----     -  --------  ---   ---   ---   ---
   1/2/00 (n/a)   Idle        0/0      1  00:00:00  RTS   CTS   noDCD DTR  
Modem 1/2/00, Cisco MICA modem (Managed), Async1/2/00, TTY432
Firmware Rev: 2.6.2.0
Modem config: Incoming and Outgoing
Protocol: (n/a), Compression: (n/a)
Management config: Status polling
RX signals: 0 dBm
  Last clearing of "show modem" counters never
    0 incoming completes, 0 incoming failures
    0 outgoing completes, 0 outgoing failures
    0 failed dial attempts, 0 ring no answers, 0 busied outs
    0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
    0 no carriers, 0 link failures, 0 resets, 0 recover oob
    0 recover modem, 0 current fail count
    0 protocol timeouts, 0 protocol errors, 0 lost events
Task 6. Enabling IP Basic Setup

Tune IP routing behavior and domain-name services for EXEC shell users by completing the following steps:

Step 1 Optimize IP routing functions. Enter the following commands in global configuration mode:
ip subnet-zero
no ip source-route
ip classless
Table 2-9 describes the previous commands:

Table 2-9 IP Routing Commands

Command

Purpose

ip subnet-zero

Specifies that 172.22.0.0 is a valid subnet.

no ip source-route

Tightens security by ensuring that IP-header packets cannot define their own paths through the access server.

ip classless

Turns off traditional IP network class distinctions in the router [Class-A, Class-B, Class-C].

Step 2 Enter domain-name service global configuration commands to support EXEC shell users:
ip domain-lookup
ip host aurora 172.22.100.9
ip domain-name the.doc
ip name-server 172.22.11.10
ip name-server 172.22.12.10
Table 2-10 describes the previous commands:

Table 2-10 Domain-Name Commands

Command

Purpose

ip domain-lookup

Enables IP domain-name lookups.

ip host aurora 172.22.100.9

Creates a local name-to-address map. This map is useful when the NAS is not entered in a DNS server.

ip domain-name the.doc

Tells the NAS how to qualify DNS look ups. In this example, the.doc is appended to the end of each name that is looked up.

ip name-server 172.22.11.10

ip name-server 172.22.12.10

Specifies the primary and secondary name servers. They are used for mapping names to IP addresses.

Task 7. Testing Asynchronous EXEC Shell Connections

This task verifies that the following components are working:

•Physical asynchronous data path

•Basic modem links

•Basic IP functionality to support EXEC shell sessions

The Cisco IOS software provides a command-line interface (CLI) called the EXEC.

The EXEC:

•Can be accessed by dialing in with a modem

•Provides access to terminal EXEC shell services (no PPP) to do the following:

–Modify configuration files

–Change passwords

–Troubleshoot possible problems including modem connections

–Access other network resources by using Telnet

During this task, some administrators try to make complex services function such as PPP-based Web browsing. Do not jump ahead. Many other elements still need to be configured (for example, PPP and IPCP). The asynchronous-shell test ensures that the EXECs log in prompt can be accessed by a client modem. Taking a layered approach to building a network isolates problems and saves time.

Note The Cisco AS5800 is designed to process PPP sessions. To support high ratios of EXEC-shell users or V.120 users, work with your support team.

Step 1 Locate a client PC, client modem, and analog line. From the client PC, open a terminal emulation program (such as Hyper Terminal, not dialup networking) and connect to the client modem. Figure 2-6 shows the network environment for this test.

Figure 2-6 Test Environment

Step 2 From a terminal-emulation program, test the EIA/TIA-232 connection to the client modem. Enter the at command. The modem sends an OK return message.
at
OK
Step 3 Dial the PRI telephone number assigned to the NAS (5551234). After the modem successfully connects, a connect message appears.
atdt5551234
CONNECT 28800 V42bis
Tips Many modems support the a/ command, which recalls the last AT command. The ath command hangs up a modem call. The atdl command dials the last telephone number.

Step 4 Log into the EXEC session:
This is a secured device. 
Unauthorized use is prohibited by law.
User Access Verification
Username: theuser
Password:
5800-NAS>
Step 5 Determine upon which line the call landed. The following example shows that TTY line 436 accepted the call. The call has been up and active for 20 seconds.
5800-NAS# show caller
                                                Active    Idle
  Line         User               Service       Time      Time
  con 0        admin              TTY           00:13:43  00:00:00 
  tty 436      theuser            TTY           00:00:20  00:00:08  
5800-NAS# show caller user theuser
  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 The show caller command is added to Cisco IOS Release 11.3 AA and 12.0 T. If your software release does not support this command, use the show user command.

Step 6 Test the IP functionality to support shell sessions. From the NAS, Telnet to another device in your network.
5800-NAS> telnet 172.22.66.26
Trying 172.22.66.26 ... Open
User Access Verification
Username: admin
Password: 
5800-NAS>
5800-NAS> telnet aurora
Translating "aurora"...domain server (172.22.11.10) [OK]
Trying aurora.cisco.com (172.22.2.2)... Open
SunOS 5.6
login: theuser
Password:
Last login: Wed Oct  6 08:57:46 from dhcp-aus-163-236
Sun Microsystems Inc.   SunOS 5.6       Generic August 1997
aurora%
Task 8. Confirming the Final Running Configuration

After you complete the tasks in this section, the final running configuration looks like this:
5800-NAS# show running-config
Building configuration...
Current configuration:
!
version 12.x
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname 5800-NAS
!
aaa new-model
aaa authentication login default local
aaa authentication ppp default if-needed local
enable secret 5 $1$gq.d$nZwr.ElnV/O0nE9U.wZ3D/
!
username admin password 7 105B1D1A0A12
username dude password 7 111C0D061817
!
!
!
!
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 aurora 172.22.100.9
ip domain-name the.doc
ip name-server 172.22.11.10
ip name-server 172.22.12.11
!
isdn switch-type primary-ni
isdn voice-call-failure 0
!         
!
controller T3 1/0/0
 framing m23
 cablelength 0
 t1 4 controller
!
controller T1 1/0/0:4
 framing esf
 pri-group timeslots 1-24
!
!
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.0
 no ip directed-broadcast
!
interface Serial1/0/0:4:23
 no ip address
 no ip directed-broadcast
 isdn switch-type primary-ni
 isdn incoming-voice modem
 no cdp enable
!
interface Group-Async0
 no ip address
 no ip directed-broadcast
 group-range 1/2/00 1/10/143
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.22.66.1
no ip http server
!
!         
banner login ^C
This is a secured device. 
Unauthorized use is prohibited by law.
^C
!
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