Basic Configuration

This chapter describes how to use the Cisco IOS software command-line interface (CLI) to configure basic access server functionality, including:

LAN and WAN configuration (including Integrated Services Digital Network [ISDN] Primary Rate Interface [PRI] and channelized T1 and E1).
Modem configuration.

Follow the procedures in this chapter to configure the access server manually or if you want to change the configuration after you have run the setup script (described in the chapter "First-Time Configuration").

This chapter does not describe every configuration possible--only a small portion of the most commonly used configuration procedures. For new and changed IOS commands, refer to the New and Changed Cisco IOS Commands for the Cisco AS5300 publication, which ships with your access server. For advanced configuration topics, refer to the Cisco IOS configuration guide and command reference publications. These publications are available on the Documentation CD-ROM that came with your access server, on the World Wide Web from Cisco's home page, or you can order printed copies separately.

If you are experienced using the Cisco IOS software, you might find the "Comprehensive Configuration Example" section at the end of this chapter a useful reference for configuration.

Note If you skipped the previous chapter, "Cisco IOS Software Survival Skills," and you have never configured a Cisco access server, go back to that chapter and read it now. This chapter provides important information you will need to succeed with the configuration.

Configuring the Host Name and Password

One of the first configuration tasks you might want to do is configure the host name and set an encrypted password. Configuring a host name allows you to distinguish multiple Cisco access servers from each other. Setting an encrypted password allows you to prevent unauthorized configuration changes.

Configure

**Table 3-1: Configuring the Host Name and Passwords**
Step	Command	Purpose
1	`Router>` `enable` `Password:` <*password*> `Router#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`Router#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `Router(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `Router(config)#.`
3	`Router(config)#` `hostname 5300` `5300(config)#`	Change the name of the access server to a meaningful name. Substitute your host name for `5300`.
4	`5300(config)#` `enable secret guessme`	Enter an enable secret password. This password provides access to privileged EXEC mode. When a user types enable at the EXEC prompt (`5300>` ), they must enter the enable secret password to gain access to configuration mode. Substitute your enable secret for guessme.
5	`5300(config)#` `line con 0` `5300(config-line)#` `exec-timeout 0 0` `5300(config-line)#` `exit` `5300(config)#`	Enter line configuration mode to configure the console port. When you enter line configuration mode, the prompt changes to `5300(config-line)#`. Prevent the access server's EXEC facility from timing out if you do not type any information on the console screen for an extended period. Exit back to global configuration mode.

Verify

To verify that you configured the right host name and passwords:

Enter the show config command:

5300(config)# show config
Using 1888 out of 126968 bytes
!
version XX.X
.
.
.
!
hostname 5300
!
enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/
.
.
.

: Check the host name and encrypted password displayed near the top of the command output.

Exit global configuration mode and attempt to re-enter it using the new enable password:

5300# exit
.
.
.
5300 con0 is now available
Press RETURN to get started.
5300> enable
Password: guessme
5300#

Tips

If you are having trouble:

Make sure Caps Lock is off.
Make sure you entered the correct passwords. Passwords are case sensitive.

Configuring Ethernet 10BaseT

Assign an IP address to the Ethernet 10BaseT interface of your access server so that it can be recognized as a device on the Ethernet LAN.

Configure

**Table 3-2: Configuring Ethernet 10BaseT**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered the global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `interface ethernet 0` `5300(config-if)#`	Enter Ethernet interface configuration mode.
4	`5300(config-if)#` `ip address 172.16.254.254 255.255.255.0`	Assign an IP address and subnet mask to the interface.
5	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by` `console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify you have assigned the correct IP address:

Enter the show arp command:

5300# show arp
Protocol  Address          Age (min)  Hardware Addr    Type   Interface
Internet 172.16.254.254           _   0800.207e.bead   ARPA   Ethernet0
5300#

Tips

If you are having trouble:

Make sure the cable connections are not loose or disconnected.
Make sure you are using the correct IP address.

Configuring Ethernet 100BaseT

Assign an IP address to the Ethernet 100BaseT interface of your access server so that it can be recognized as a device on the Ethernet LAN. The Fast Ethernet interface supports 10- and 100-Mbps speeds with the 100BaseT and 10BaseT routers, hubs, and switches.

Configure

**Table 3-3: Configuring Ethernet 100BaseT**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `interface fastethernet 0` `5300(config-if)#`	Enter Ethernet interface configuration mode.
4	`5300(config-if)#` `ip address 172.16.254.250 255.255.255.0`	Assign an IP address and subnet mask to the interface.
5	5300(config)# `interface fastethernet 0` 5300(config-if)# `speed 100` [or] 5300(config-if)# `speed 10` [or] 5300(config-if)# `speed auto`	Assigns speed 100 Mbps to Fast Ethernet. This is the default value. Assigns speed 10 Mbps to Fast Ethernet. Assigns speed auto and negotiates speed automatically based on the peer router, hub, or switch media and speed. See Table 3-4 for details on using different combinations of speed and duplex options.
6	5300(config)# `interface fastethernet 0` 5300(config)# `duplex full` [or] 5300(config)# `duplex half` [or] 5300(config)# `duplex auto`	Sets Fast Ethernet to operate at full duplex. Sets Fast Ethernet to operate at half duplex. This is the default value. Sets Fast Ethernet to operate at half or full duplex based on the peer duplex operation. See the following table for details on using different combinations of duplex and speed.
7	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by` `console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Note To use the auto-negotiation capability (that is, detect speed and duplex modes automatically), you must set both speed and duplex to auto. Setting speed to auto negotiates speed only, and setting duplex to auto negotiates duplex only.

**Table 3-4: Using Different Speed and Duplex Options**
Duplex Mode	Speed Mode	Action
auto	auto	Auto negotiates speed and duplex modes.
auto	100/10	Auto negotiates duplex mode.
half/full	auto	Auto negotiates speed mode.
half	10	Sets 10 Mbps for speed and half-duplex for duplex.
full	10	Sets 10 Mbps for speed and full-duplex for duplex.
half	100	Sets 100 Mbps for speed and half-duplex for duplex.
full	100	Sets 100 Mbps for speed and full-duplex for duplex.

Verify

To verify the IP address, configured and actual speed, and configured and actual duplex operations:

Enter the show arp command to verify the IP address:

5300# show arp
Protocol  Address      Age (min)  Hardware Addr    Type    Interface
Internet 172.16.254.250      _    0800.207e.bead   ARPA    FastEthernet0

Enter the show interface fastethernet 0 command to verify the configured speed:

5300# show interface fastethernet 0
FastEthernet0 is up, line protocol
Hardware is DEC21140, address is 00e0.1e3e.c125 (bia 00e0.1e3e.c125)
Internet address is 2.2.2.2/8
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 2/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec), auto duplex, 100BaseTX/FX,  100Mb/s

Enter the show controller fastethernet 0 command to verify actual speed or duplex if speed or duplex are configured as auto:

Router# show controller fastethernet 0
DEC21140
Setup Frame
(0) 00e0.1e3e.c125
(1) 0100.0ccc.cccc
dec21140_ds=0x606A0078, registers=0x3C210000, ib=0x4002F75C, ring entries=128
rxring=0x4002F844, rxr shadow=0x606F5168, rx_head=47, rx_tail=47
txring=0x4003006C, txr shadow=0x606F5388, tx_head=63, tx_tail=63, tx_count=0
tx_size=128, rx_size=128
PHY link up
Duplex mode sensed by auto-negotiation is half-duplex and
Fast Ethernet speed is 100 Mbps.

Enter the show interface fastethernet 0 command to verify the configured duplex operation:

Router# show interface fastethernet 0
FastEthernet0 is up, line protocol is up
Hardware is DEC21140, address is 00e0.1e3e.c125 (bia 00e0.1e3e.c125)
Internet address is 2.2.2.2/8
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 2/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec), auto duplex, 100BaseTX/FX, auto speed                                      ^^^^^^^^^^^

Tips

If you are having trouble:

Make sure the cable connections are not loose or disconnected.
Make sure you are using the correct IP address.

Configuring ISL for VLAN Routing

Use the Inter-Switch Link (ISL) to connect multiple Virtual LANs (VLANs) using the Ethernet Media Access Control (MAC) and Ethernet media.

Configure

**Table 3-5: Configuring VLAN Routing**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `interface fastethernet 0`	Enter Ethernet interface configuration mode.
4	`5300(config-if)#` `no shut`	Enable Fast Ethernet.
5	5300(config)# `interface fastethernet0.x`	Enter the Fast Ethernet subinterface x, where x is an integer value.
6	5300(config-subif)# `encapsulation isl <1-1000>`	Set ISL encapsulation to the VLAN identifier (a value between 1 and 1000).
7	5300(config-subif)# `ipx network <1-fffffffd>`	Set the virtual IPX¹ network number for the VLAN ID.
8	`5300(config-subif)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by` `console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

¹ IPX = Internetwork Packet Exchange.

Verify

To verify the VLAN setup (VLAN ID, network address, protocol, and packets received and transmitted):

Enter the show vlan command:

5300# show vlan
 Virtual LAN ID:  10 (Inter Switch Link Encapsulation)
 vLAN Trunk Interface:   FastEthernet0.10      
 Protocols Configured:   Address:              Received:        Transmitted:
          X           10.00e0.1e6b.2f03         3                   5

Tips

If packets are not being routed:

Enter the debug vlan packets command. When you finish viewing the messages, enter the no debug vlan packets command to turn off the messages.

5300# debug vlan packets
Virtual LAN packet information debugging is on
 
vLAN: ISL packet received bearing colour ID 16 on FastEthernet0
      which has no subinterface configured to route or bridge ID 16.

Configuring ISDN PRI

Configure the access server interfaces for ISDN PRI lines.

Configure

**Table 3-6: Configuring ISDN PRI**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `isdn switch-type` `[primary-4ess` `\|` `primary-5ess` `\|` `primary-dms100` `\|` `primary-net5` `\|` `primary-ntt` `\|` `primary-ts014]`	Enter your telco's switch type.
4	`5300(config)#` `controller` `[t1` `\|` `e1]` `[0` `\|` `1` `\|` `2` `\|` `3]` `5300(config-controller)#`	Enter controller configuration mode to configure your controller port. The controller ports are labeled 0 through 3 on the quad T1/PRI and quad E1/PRI cards.
5	`5300(config-controller)#` `framing` `[esf` `\|` `sf` `\|` `crc4` `\|` `nocrc4]`	Enter your telco's framing type.
6	`5300(config-controller)#` `linecode` `[ami` `\|` `b8zs` `\|` `hdb3]`	Enter your telco's line code type.
7	`5300(config-controller)#` `clock source line primary`	Enter the clock source for the line. Configure other lines as clock source secondary or clock source internal. Note that only one PRI can be clock source primary and only one PRI can be clock source secondary.
8	`5300(config-controller)#` `pri-group timeslots` `[1-24` `\|` `1-31]`	Configure all channels for ISDN. Enter pri-group timeslots 1-24 for T1. If E1, enter pri-group timeslots 1-31.
9	`5300(config-controller)#` `controller t1 1` `5300(config-controller)#` `framing esf` `5300(config-controller)#` `linecode b8zs` `5300(config-controller)#` `clock source line secondary` `5300(config-controller)#` `pri-group timeslots 1-24`	Repeats steps 2 to 8 to configure each additional controller (there are four). In this example, note that the controller number is 1, instead of 0. And the clock source is secondary, instead of primary.
10	`5300(config-controller)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify you have configured the interfaces correctly:

Enter the show controller t1 or show controller e1 command and specify the port number:

5300# show controller t1 0
T1 0 is up.
  No alarms detected.
  Framing is ESF, Line Code is B8ZS, Clock Source is Line Primary.
  Version info of slot 2:  HW: 2, Firmware: 14, NEAT PLD: 13, NR Bus PLD: 19
  Data in current interval (476 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
  Total Data (last 24 hours)
     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

Note the following:

The controller must report being up.
No errors should be reported.

Enter the show isdn status command to view layer status information.

5300# show isdn status
The current ISDN Switchtype = primary-5ess
ISDN Serial0:23 interface
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        No Active Layer 3 Call(s)
    Activated dsl 0 CCBs = 0
    Total Allocated ISDN CCBs = 0
ISDN Serial1:23 interface
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        No Active Layer 3 Call(s)
    Activated dsl 0 CCBs = 0
    Total Allocated ISDN CCBs = 0

Note the following information for Serial 0:23 (the first half of the messages):

Layer 1 Status should be "Active."
Layer 2 Status should be "Multiple_Frame_Established." (It might take several seconds for Layer 2 status to appear.)
Layer 3 Status should be "No Active Layer 3 Call(s)."

The second half of the messages display information for Serial 1:23.

Tips

If you are having trouble:

Make sure the cable connection is not loose or disconnected if the Layer 1 Status is "Deactivated." This status message indicates a problem at the physical layer.
There may be a problem with your telco or the framing and line code types you entered may not match your telco's. A Layer 2 error indicates that the access server cannot communicate with the telco. There is a problem at the data link layer.

Configuring Channelized T1 or E1

Configure the access server for channelized T1 or E1 lines.

Configure

**Table 3-7: Configuring Channelized T1 or E1**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `controller` `[t1` `\|` `e1]` `[0` `\|` `1` `\|` `2` `\|` `3]` `5300(config-controller)#`	Enter controller configuration mode to configure your controller port. The controller ports are labeled 0 through 3 on the Quad T1/PRI and E1/PRI cards.
4	`5300(config-controller)#` `framing` `[esf` `\|` `sf` `\|` `crc4` `\|` `nocrc4]`	Enter your telco's framing type.
5	`5300(config-controller)#` `linecode` `[ami` `\|` `b8zs` `\|` `hdb3]`	Enter your telco's line code type.
6	`5300(config-controller)#` `clock source line primary`	Enter the clock source for the line. Configure other lines as clock source secondary or internal. Note that only one PRI can be clock source primary and one PRI can be clock source secondary.
7	`5300(config-controller)#` `cas-group 1 timeslots` `[1-24` `\|` `1-31] <type> [[ mf \| dtmf ] dnis ]`	Configure all channels for E&M, FXS, and SAS analog signaling. Enter 1-24 for T1. If E1, enter 1-31. Signaling types: e&m-fgb, e&m-fgd, e&m-immediate-start, fxs-ground-start, fxs-loop-start, sas-ground-start, and sas-loop-start. You must use the same type of signaling that your central office uses. For E1 using the Anadigicom converter, use cas e&m-fgb signaling. To support modem pooling for cas e&m-fgb signaling, the tone type (mf or dtmf) must be specified. If the address information is provisioned for incoming calls, the DNIS parameter also needs to be configured.
8	`5300(config-controller)#` `controller t1 1` `5300(config-controller)#` `framing crc4` `5300(config-controller)#` `linecode hdb3` `5300(config-controller)#` `clock source line secondary` `5300(config-controller)#` `cas-group 2 timeslots 1-24` `type e&m-fgb`	Repeats steps 3 to 7 to configure each additional controller (there are four). In this example, note that the controller number is 1, instead of 0. The clock source is secondary, instead of primary. And the cas-group is 2, instead of 1.
9	`5300(config-controller)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify your controller is up and running and no alarms have been reported:

Enter the show controller t1 or show controller e1 command and specify the port number:

5300# show controller t1 0
T1 0 is up.
  No alarms detected.
  Framing is ESF, Line Code is B8ZS, Clock Source is Line Primary.
  Version info of slot 2:  HW: 2, Firmware: 14, NEAT PLD: 13, NR Bus PLD: 19
  Data in current interval (476 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
  Total Data (last 24 hours)
     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

Note the following:

The controller must report being up.
No errors should be reported.

Tips

If you are having trouble:

Make sure the show controller t1 or show controller e1 output is not reporting alarms or violations.

Configuring the D Channels for Modem Signaling

Configure the ISDN D channels, which carry the control and signaling information for ISDN calls, for each ISDN PRI line.

Configure

**Table 3-8: Configuring the D Channels for Modem Signaling**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `interface serial` [`0:15` \| `0:23`] `5300(config-if)#`	Enter serial interface configuration mode. After you have configured the controller, a corresponding D channel serial interface is created instantly. For example, serial interface 0:23 is the D channel for controller 0. You must configure each serial interface to receive incoming and send outgoing modem signaling.
4	`5300(config-if)#` `ip address 172.16.253.254 255.255.255.0`	Assign an IP address and subnet mask to the interface.
5	`5300(config-if)#` `isdn incoming-voice modem`	Configure all incoming voice calls to go to the modems.
6	`5300(config-if)#` `dialer-group 1`	Assign the serial interface to dialer group 1. The dialer group number is used with the dialer-list command to determine which packets will be meet the criteria specified by the dialer-list command and activate the ISDN connection.
7	`5300(config-if)#` encapsulation `ppp`	Changes the default to encapsulation ppp so you can enter ppp commands.
8	`5300(config-if)#` `ppp multilink`	Enable PPP¹ multilink on the serial interface.
9	`5300(config-if)#` `ppp authentication chap pap`	Enable CHAP² and PAP³ authentication on the serial interface.
10	`5300(config-if)#` `peer default ip address pool default`	Support dial-in PC clients.
11	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

¹ PPP = Point-to-Point Protocol.
² CHAP = Challenge Handshake Authentication Protocol.
³ PAP = Password Authentication Protocol.

Verify

To verify your D-channel configuration:

Enter the show interface command:

5300# show interface 1:23
Serial1:23 is up, line protocol is up 
  Hardware is DSX1
  Interface is unnumbered.  Using address of FastEthernet0 (15.0.0.60)
  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation PPP, loopback not set
  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
     54 packets input, 214 bytes, 0 no buffer
     Received 0 broadcasts, 10 runts, 0 giants, 0 throttles
     10 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     53 packets output, 211 bytes, 0 underruns
     0 output errors, 0 collisions, 10 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
  Timeslot(s) Used:24, Transmitter delay is 0 flags

Tips

If you are having trouble:

Make sure the serial interface and protocol are up by entering the show interface serial command:

5300(config)# show interface serial 0:23
Serial0:23 is up, line protocol is up
  Hardware is DSX1
  Internet address is 61.0.0.2/8
  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
  Encapsulation PPP, loopback not set
  Last input 00:00:02, output 00:00:02, 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
     6442 packets input, 25855 bytes, 0 no buffer
     Received 0 broadcasts, 8 runts, 0 giants, 0 throttles
     8 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     6439 packets output, 25875 bytes, 0 underruns
     0 output errors, 0 collisions, 8 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier trnsitions
  Timeslot(s) Used:24, Transmitter delay is 0 flags

Enter the debug dialer command to view the error messages. You can also use the debug dialer events or debug dialer packets messages to view event or packet messages. When you finish viewing the messages, enter the no debug dialer command to turn off the messages. See Table 3-9 for explanations of the error messages.

5300# debug dialer PRI0: Dialing cause: PRI0: ip PERMIT PRI0: No dialer string defined. Dialing cannot occur.. PRI0: Dialing cause: PRI0: ip PERMIT

**Table 3-9: Debug Dialer Messages**
Message	Description
`PRI0: No dialer string defined. Dialing cannot occur`	Displayed when a packet is received that should cause a call to be placed. However, there is no dialer string configured, so dialing cannot occur. This message usually indicates a configuration problem. Re-enter the dialer string command in step 4 in the "Configure" section.
`PRI0: Attempting to dial xxxxxxxxxx`	Indicates that a packet has been received that passes the dial-on-demand access lists. That packet causes dialing of a phone number. The xxxxxxxxxx variable is the number being called.
`PRI0: Unable to dial xxxxxxxxxx`	Displayed if the phone call could not be placed. This can be due to a lack of memory, full output queues, or other problems.
`PRI0: disconnecting call`	Displayed when the Cisco AS5300 attempts to hang up a call.
`PRI0: idle timeout` `PRI0: re-enable timeout` `PRI0: wait for carrier timeout`	One of these three messages is displayed when their corresponding dialer timer expires. They are mostly informational, but are useful when debugging a disconnected call or call failure.

If dialing cannot occur, check the configuration by entering the debug isdn q931 command. When you finish viewing the messages, enter no debug isdn q931 to turn off the messages. See the following table for explanations of the error messages.

5300# debug isdn q931
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:22, changed state to up
ISDN Event: Call to 9086154535 dsl 3 at 64 Kb/s
TX ->  SETUP dsl = 3 pd = 8  callref = 0x188C
          Bearer Capability i = 0x8890
          Channel ID i = 0xE1808397
          Called Party Number i = 0xA1, '95163287448'
RX <-  RELEASE_COMP dsl = 3 pd = 8  callref = 0x988C
          Cause i = 0x83E020 - Mandatory IE missing
ISDN PRI 3: entering process_rxstate, CALL_CLEARED
ISDN PRI 3: received message 1F
ISDN Event: Hangup call to call id 0xCE2 on dsl 2

**Table 3-10: Debug ISDN Messages**
Message	Description
`TX ->`	Indicates this message is being transmitted from the local router (user side) to the network side of the ISDN interface.
`RX <-`	Indicates this message is being received by the user side of the ISDN interface from the network side.
`SETUP`	Indicates the SETUP message has been sent to initiate call establishment between peer network layers. The message can be sent from the local router or network.
`pd`	Indicates the protocol discriminator. The protocol discriminator distinguishes messages for call control over the user-network ISDN interface from other ITU-T1¹-defined messages, including other Q.931 messages. The protocol discriminator is 8 for call control messages such as SETUP.
`callref`	Indicates the call reference number in hexadecimal. The field value indicates the number of calls made from the router (outgoing calls) or the network (incoming calls). Note that the originator of the SETUP message sets the high-order bit of the call reference number to 0. The destination of the connection sets the high-order bit to 1 in subsequent call control messages, such as the CONNECT message. For example, callref = 0x04 in the request becomes callref = 0x84 in the response.
`Bearer Capability`	Indicates the requested bearer service to be provided by the network.
`i=`	Indicates the Information Element Identifier. The value depends on the field it is associated with. Refer to the ITU-T Q.931 specification for details about the possible values associated with each field for which this identifier is relevant.
`Channel ID`	Indicates the Channel Identifier. The value 83 indicates any channel, 89 indicates the B1 channel, and 8A indicates the B2 channel. For more information about the Channel Identifier, refer to ITU-T Recommendation Q.931.
`Called Party Number`	Identifies the called party. This field is only present in outgoing SETUP messages. It can be replaced by the Keypad facility field. This field uses the IA5 character set.
`RELEASE`	Indicates that the sending equipment will release the channel and call reference. The recipient of this message should prepare to release the call reference and channel.
`RELEASE_COMP`	Indicates that the sending equipment has received a RELEASE message and has now released the call reference and channel.

¹ ITU-T1 = International Telecommunication Union Telecommunication Standarization Sector.

Configuring R2 Signaling

R2 signaling is an international signaling standard that is common to channelized E1 networks. You can configure a channelized E1 interface to support different types of R2 signaling, which is used in older analog telephone networks.

Configure

**Table 3-11: Configuring R2 Signaling**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `configure terminal` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `controller e1` `[0` `\|` `1` `\|` `2` `\|` `3]` `5300(config-controller)#`	Enter controller configuration mode to configure your E1 controller port. The E1 controller ports are labeled 0-3 on the quad E1/PRI cards.
4	5300 (config-controller)# framing crc4 [or] 5300 (config-controller)# framing no-crc4	Configures framing to E1 with CRC¹. Configures framing to E1 only.
5	5300 (config-controller)# linecode ami [or] 5300 (config-controller)# linecode hdb3	Configures line code to AMI² encoding. Configures line code to HDB3 encoding.
6	5300 (config-controller)# clock source internal [or] 5300 (config-controller)# clock source line primary [or] 5300 (config-controller)# clock source line secondary	Configures the clock source to the internal clock. Configures the clock source to the primary recovered clock. Configures the clock source to the secondary recovered clock.
7	`5300(config-controller)#` `cas-group 1 timeslots 1-30 type r2-analog r2-digital ani`	Configure the timeslots that belong to each E1 circuit for R2 signaling. Sets R2 signaling to R2 ITU Q411, the tone signal to R2 Compelled Register Signaling, and the ANI addr info provisioned option. R2 line signaling options include r2-analog, r2-digital, and r2-pulse. Tone signaling options include dtmf (default), r2-compelled, r2-non-compelled, and r2-semi-compelled. You can also set ani (ANI addr info provisioned) for any of the above options.
8	`5300(config-controller-cas)#` `cas-custom 1`	Enter the channel number to customize.
9	`5300(config-ctrl-cas)#` `country` `country use-default`	Use defaults for the specified country. Note: To view the parameters for the country (if the country defaults are the same as ITU defaults), enter write term.
10	`5300(config-ctrl-cas)#` `answer-signal group-b 6` [or] `5300(config-ctrl-cas)#` `default` `answer-signal group-b 6` [or] `5300(config-ctrl-cas)#` `no` `answer-signal group-b 6` `controller E1 0 clock source line primary cas-group 0 timeslots 1-15,17-31 type r2-analog r2-compelled cas-custom 0 country singapore use-defaults category 2 <--- default category for singapore answer-signal group-b 6 <--- default bxfree for singapore` `5300(config-ctrl-cas)#` `exit`	Set up the selected channel using cas custom commands, such as caller-digits, category, country, unused-abcd, invert-abcd, metering, ka, kd, dnis-digits, answer-signal, and nc-congestion. Sets the cas custom command answer-signal to group-b to 6. Sets answer-signal group-b to the default ITU value. Reset answer-signal group-b 6 to the default value. Note: The parameters you do not set are automatically set to the ITU default by the Cisco AS5300. After you configure a country with default settings, the Cisco AS5300 displays a write term, similar to the one displayed here. Exits the cas-custom mode.
11	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

¹ CRC = Cyclic Redundancy Check.
² AMI = Alternate Mark Inversion.

Verify

To verify your R2 signaling configuration:

Enter the show controller e1 command to view the status for all controllers, or enter the show controller e1 # to view the status for a particular controller. Make sure the status indicates the controller is up (line 2 in the following example) and no alarms (line 4 in the following example) or errors (lines 9 and 10 in the following example) have been reported.

5300# show controller e1 0
E1 0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  Version info of Slot 0:  HW: 2, Firmware: 4, PLD Rev: 2
 
Manufacture Cookie is not programmed.
 
  Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.
  Data in current interval (785 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
  Total Data (last 13 15 minute intervals):
     0 Line Code Violations, 0 Path Code Violations,
     0 Slip Secs, 12 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 12 Unavail Secs

Enter the show modem csm [slot/modem-port] command to view status for a specific modem:

5300# show modem csm 1/0
MODEM_INFO: slot 1, port 0, unit 0, tone r2-compelled, modem_mask=0x0000, modem_port_offset=0
tty_hwidb=0x60E63E4C, modem_tty=0x60C16F04, oobp_info=0x00000000, modem_pool=0x60BC60CC
modem_status(0x0002): VDEV_STATUS_ACTIVE_CALL.
csm_state(0x0205)=CSM_IC5_CONNECTED, csm_event_proc=0x600CFF70, current call thru CAS line
invalid_event_count=0, wdt_timeout_count=0
wdt_timestamp_started is not activated
wait_for_dialing:False, wait_for_bchan:False
pri_chnl=TDM_PRI_STREAM(s0, u3, c7), modem_chnl=TDM_MODEM_STREAM(s1, c0)
dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0239, bchan_num=6
csm_event=CSM_EVENT_DSX0_CONNECTED, cause=0x0000
ring_no_answer=0, ic_failure=0, ic_complete=3
dial_failure=0, oc_failure=0, oc_complete=0
oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
remote_link_disc=2, stat_busyout=2, stat_modem_reset=0
oobp_failure=0
call_duration_started=00:04:56, call_duration_ended=00:00:00, total_call_duration=00:01:43
The calling party phone number = 
The called party phone number  = 9993003
total_free_rbs_timeslot = 0, total_busy_rbs_timeslot = 0, total_dynamic_busy_rbs_timeslot = 0, total_static_busy_rbs_timeslot = 0, min_free_modem_threshold = 0

Tips

If you are having trouble, enable the modem management Call Switching Module (CSM) debug mode using the following command.

Enter the debug modem csm command.

: This is the output of debug modem csm for an incoming call:

5300# debug modem csm 1/0
*May 15 04:05:46.675: VDEV_ALLOCATE: slot 2 and port 39 is allocated.
 
*May 15 04:05:46.675: CSM_RX_CAS_EVENT_FROM_NEAT:(04BF):  EVENT_CALL_DIAL_IN at slot 2 and port 39
 
*May 15 04:05:46.675: CSM_PROC_IDLE: CSM_EVENT_DSX0_CALL at slot 2, port 39
 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x0) 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x3) 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x6) 
*May 15 04:05:46.675: Mica Modem(2/39): Call Setup
*May 15 04:05:46.891: Mica Modem(2/39): State Transition to Call Setup
*May 15 04:05:46.891: Mica Modem(2/39): Went offhook
*May 15 04:05:46.891: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 2, port 39
.
.
.

When the E1 controller comes up, you will see the following messages:

%CONTROLLER-3-UPDOWN: Controller E1 0, changed state to up
It also shows these messages for individual timeslots:
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up
.
.
.

Configuring the Asynchronous Group Interface

You can assign the asynchronous interfaces to a group so that you can configure them as a group, instead of individually.

Time Saver Because there are so many asynchronous interfaces on the access server, configuring them as a group will save you time.

Configure

**Table 3-12: Configuring the Asynchronous Group Interface**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `interface group-async 1` `5300(config-if)#`	Place all asynchronous interfaces in a single group, so that you configure the same parameters quickly on all interfaces at one time.
4	`5300(config-if)#` `ip unnumbered ethernet 0`	To conserve IP addresses, configure the asynchronous interfaces as unnumbered, and assign the IP address of the Ethernet interface to them.
5	`5300(config-if)#` `encapsulation ppp`	Enable PPP to run on the set of interfaces in the group.
6	`5300(config-if)#` `async mode interactive`	Configure interactive mode on the asynchronous interface.
7	`5300(config-if)#` `ppp authentication chap pap`	Enable CHAP and PAP authentication on the interface.
	`5300(config-if)#` `peer default ip address pool default`	Support dial-in PC clients. At the global level, define the pool of addresses.
8	`5300(config-if)#` `group-range 1 48` `Building configuration...` `5300(config-if)#`	Define the group range of the interface. The number you use with the group-range command depends on the number of asynchronous interfaces you have on your access server. That is, if your access server has 48 asynchronous interfaces, you can specify group-range 1 48. If 60, specify group-range 1 60.
9	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify your group interface configuration:

Enter the show interface async command to check if the protocol is up:

5300# show interface async 1
Async1 is up, line protocol is up 
modem(slot/port)=1/0, csm_state(0x00000204)=CSM_IC4_CONNECTED, bchan_num=18
modem_status(0x0002): VDEV_STATUS_ACTIVE_CALL.
 
  Hardware is Async Serial
  Interface is unnumbered.  Using address of FastEthernet0 (15.0.0.60)
  MTU 1500 bytes, BW 115 Kbit, DLY 100000 usec, rely 255/255, load 1/255
  Encapsulation PPP, loopback not set, keepalive not set
  DTR is pulsed for 5 seconds on reset
  LCP Open
  Open: IPCP
  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/5, 0 drops; input queue 1/5, 0 drops
  5 minute input rate 37000 bits/sec, 87 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     31063 packets input, 1459806 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     33 packets output, 1998 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Enter the show dialer map command to make sure the dialer map is up:

5300# show dialer maps
Dynamic dialer map ip 10.10.10.2 name remote-isdn on Serial1

Tips

If you are having trouble:

Enter the show async status maps command to check for errors and local and remote addresses:

5300# show async status maps
Async protocol statistics:
  Rcvd: 27887 packets, 1294133 bytes
        0 format errors, 0 checksum errors, 0 overrun, 0 no buffer
  Sent: 2141 packets, 117673 bytes, 0 dropped
 
 Int           Local          Remote Qd     InPack     OutPac Inerr  Drops  MTU
*  1       15.0.0.60        50.2.8.1  0        542         35     0      0 1500
*  2       15.0.0.60        50.3.8.1  0        544         35     0      0 1500
*  3       15.0.0.60       100.2.1.1  0        542         35     0      0 1500
*  4       15.0.0.60        50.1.1.1  0        544         35     0      0 1500
*  5       15.0.0.60        99.2.7.1  0        542         34     0      0 1500
*  6       15.0.0.60        99.1.4.1  0        543         34     0      0 1500
*  7       15.0.0.60       100.2.3.1  0        451         34     0      0 1500
*  8       15.0.0.60       100.2.5.1  0        451         34     0      0 1500
*  9       15.0.0.60       100.2.6.1  0        452         34     0      0 1500
* 10       15.0.0.60       100.2.8.1  0        452         34     0      0 1500
* 11       15.0.0.60        30.2.6.1  0        449         34     0      0 1500
* 12       15.0.0.60        30.3.5.1  0        450         34     0      0 1500
* 13       15.0.0.60        30.2.4.1  0        450         34     0      0 1500
* 14       15.0.0.60        30.2.8.1  0        450         34     0      0 1500
  15       15.0.0.60            None  0          0          0     0      0 1500
* 16       15.0.0.60        50.3.5.1  0        355         27     0      0 1500
.
.
.

You can also view debug messages for PPP negotiation and authentication using the debug ppp negotiation and debug ppp authentication commands. When you finish viewing the messages, turn off the messages by entering no debug ppp negotiation and no debug ppp authentication commands.

5300# debug ppp negot

5300# debug ppp authen

Aug 28 15:40:40.963: ppp: sending CONFREQ, type = 2 (CI_ASYNCMAP), value = 0xA0000

Aug 28 15:40:40.967: ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = 0xC023

Aug 28 15:40:40.967: ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 0xC9BAE6A0

Aug 28 15:40:41.091: PPP Async1: state = REQsent fsm_rconfack(0xC021): rcvd id 3

Aug 28 15:40:41.095: ppp: config ACK received, type = 2 (CI_ASYNCMAP), value = 0xA0000

Aug 28 15:40:41.099: ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = 0xC023

Aug 28 15:40:41.099: ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 0xC9BAE6A0

Aug 28 15:40:41.103: ppp: config ACK received, type = 7 (CI_PCOMPRESSION)

Aug 28 15:40:41.103: ppp: config ACK received, type = 8 (CI_ACCOMPRESSION)

Aug 28 15:40:42.271: PPP Async1: received config for type = 2 (ASYNCMAP) value = 0xA0000 acked

Aug 28 15:40:42.275: PPP Async1: received config for type = 5 (MAGICNUMBER) value = 0xA0149 acked

Aug 28 15:40:42.275: PPP Async1: received config for type = 7 (PCOMPRESSION) acked

Aug 28 15:40:42.279: PPP Async1: received config for type = 8 (ACCOMPRESSION) acked

Aug 28 15:40:42.283: PPP Async1: received config for type = 13 (CALLBACK) rejected

Aug 28 15:40:42.391: PPP Async1: received config for type = 2 (ASYNCMAP) value = 0xA0000 acked

Aug 28 15:40:42.395: PPP Async1: received config for type = 5 (MAGICNUMBER) value = 0xA0149 acked

Aug 28 15:40:42.399: PPP Async1: received config for type = 7 (PCOMPRESSION) acked

Aug 28 15:40:42.399: PPP Async1: received config for type = 8 (ACCOMPRESSION) acked

Aug 28 15:40:42.515: PPP Async1: PAP receive authenticate request poolme

Aug 28 15:40:42.523: PPP Async1: PAP authenticating peer poolme

Aug 28 15:40:42.575: PPP Async1: Remote passed PAP authentication sending Auth-Ack.

.

Configuring the Modems

Configure the modems to allow users to dial in to your network.

Configure

**Table 3-13: Configuring the Modems**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	`5300(config)#` `modem country micacountry name` [or] `5300(config)#modem country microcom_hdms <country name>`	Specify the country to set the modem parameters (including encoding) for MICA modems. The default is usa if the access server is configured with T1 interfaces and e1-default if the access server has E1 interfaces. Specify the country to set the modem parameters (including encoding) for Microcom modems. The default is usa. Note that the access server will reset the Microcom modems for the command to take effect.
3	`5300(config-if)#` `line 1 48` `5300(config-line)#`	Enter the number of modem lines to configure. If you have 48 modems, enter line 1 48. If 60, enter line 1 60. Note: There are 12 modems on each 12-port module, and 6 modems on each MICA 6-port module.
4	`5300(config-line)#` `transport input all`	Allow all protocols to be used when connecting to the line.
5	`5300(config-line)#` `autoselect ppp`	Enable remote IP users running a PPP application to dial in, bypass the EXEC facility, and connect directly to the network.
6	`5300(config-line)#` `modem inout`	Enable incoming and outgoing calls.
7	`5300(config-line)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify your modem configuration:

Enter the show line command to display a summary for all the lines:

5300# show line
 Tty Typ     Tx/Rx     A Modem  Roty AccO AccI  Uses    Noise   Overruns
*  0 CTY               -    -      -    -    -     0        0        0/0
I  1 TTY 115200/115200 - inout     -    -    -     0        0        0/0
I  2 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   3 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   4 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   5 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   6 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   7 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   8 TTY 115200/115200 - inout     -    -    -     0        0        0/0
   9 TTY 115200/115200 - inout     -    -    -     0        0        0/0
  10 TTY 115200/115200 - inout     -    -    -     0        0        0/0
.
.
.
  90 VTY               -    -      -    -    -     0        0        0/0

Enter the show line # command to display a summary for a single line:

5300# show line 1
 Tty Typ     Tx/Rx     A Modem  Roty AccO AccI  Uses    Noise   Overruns
I  1 TTY 115200/115200 - inout     -    -    -     0        0        0/0
 
Line 1, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 115200/115200, no parity, 1 stopbits, 8 databits
Status: none
Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol Out
  Modem Callout, Modem RI is CD, Line usable as async interface
Modem state: Idle
Special Chars: Escape  Hold  Stop  Start  Disconnect  Activation
                ^^x    none   -     -       none         
Timeouts:      Idle EXEC    Idle Session   Modem Answer  Session   Dispatch
               00:10:00        never                        none     not set
                            Idle Session Disconnect Warning
                              never 
Modem type is unknown.
Session limit is not set.
Time since activation: never
Editing is enabled.
History is enabled, history size is 10.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed transports are pad telnet rlogin.  Preferred is telnet.
No output characters are padded
No special data dispatching characters
modem(slot/port)=1/0, csm_state(0x00000100)=CSM_IDLE_STATE, bchan_num=-1
modem_status(0x0000): VDEV_STATUS_UNLOCKED
 
Modem hardware state: CTS noDSR  DTR RTS

Tips

If you are having trouble:

If you are having problems with making or receiving calls, make sure you turned on the protocols for connecting to the lines (step 4 in the previous configuration table) and configured for incoming and outgoing calls (step 6 in the previous configuration table).
If the calls are not coming up at all, turn on the debug modem, debug modem csm, and debug isdn q931 commands to check for problems. When you finish viewing the messages, turn off the messages by entering the no debug modem command.

5300# debug modem
5300# debug modem csm
5300# debug isdn q931

: The following is the sample output for a MICA modem for an outgoing ISDN voice call:

5300# 1.17.30.12 2004
Trying 1.17.30.12, 2004 ... Open
 
TTY4: asserting DTRatdt1000
Mica Modem(2/3): Rcvd Dial String(1000)
CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 2, port 3
 
CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS at slot 2, port 3
 
CSM_PROC_OC3_COLLECT_ALL_DIGIT: called party num: (1000) at slot 2, port 3
ISDN Se0:23: TX ->  SETUP pd = 8  callref = 0x0001
        Bearer Capability i = 0x8090A2
        Channel ID i = 0xE1808397
        Called Party Number i = 0xA1, '1000'
ISDN Se0:23: RX <-  CALL_PROC pd = 8  callref = 0x8001
        Channel ID i = 0xA98397
EVENT_FROM_ISDN::dchan_idb=0x60DD2D74, call_id=0xA001, ces=0x1
   bchan=0x16, event=0x3, cause=0x0
 
EVENT_FROM_ISDN:(A001): DEV_CALL_PROC at slot 2 and port 3
 
CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 2, port 3
 
Mica Modem(2/3): Configure(0x1) 
Mica Modem(2/3): Configure(0x0) 
Mica Modem(2/3): Configure(0x6) 
Mica Modem(2/3): Call Setup
ISDN Se0:23: RX <-  ALERTING pd = 8  callref = 0x8001
Mica Modem(2/3): State Transition to Call Setup
ISDN Se0:23: RX <-  CONNECT pd = 8  callref = 0x8001
EVENT_FROM_ISDN::dchan_idb=0x60DD2D74, call_id=0xA001, ces=0x1
   bchan=0x16, event=0x4, cause=0x0
 
EVENT_FROM_ISDN:(A001): DEV_CONNECTED at slot 2 and port 3
 
CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 2, port 3
 
Mica Modem(2/3): Link Initiate
ISDN Se0:23: TX ->  CONNECT_ACK pd = 8  callref = 0x0001
Mica Modem(2/3): State Transition to Connect
Mica Modem(2/3): State Transition to Link
Mica Modem(2/3): State Transition to Trainup
CONNECT 16800 /V.42/V.42bis
 
Mica Modem(2/3): State Transition to EC Negotiating
Mica Modem(2/3): State Transition to Steady State


: This is the sample output for an incoming ISDN voice call on a MICA modem:

ISDN Se0:23: RX <-  SETUP pd = 8  callref = 0x0065
        Bearer Capability i = 0x8090A2
        Channel ID i = 0xE1808381
        Called Party Number i = 0xA1, '1000'
ISDN Se0:23: Incoming call id = 0x3
EVENT_FROM_ISDN::dchan_idb=0x60DD2D74, call_id=0x3, ces=0x1
   bchan=0x0, event=0x1, cause=0x0
 
VDEV_ALLOCATE: slot 2 and port 2 is allocated.
 
EVENT_FROM_ISDN:(0003): DEV_INCALL at slot 2 and port 2
 
CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 2, port 2
 
Mica Modem(2/2): Configure(0x0) 
Mica Modem(2/2): Configure(0x0) 
Mica Modem(2/2): Configure(0x6) 
Mica Modem(2/2): Call Setup
ISDN Se0:23: TX ->  CALL_PROC pd = 8  callref = 0x8065
        Channel ID i = 0xA98381
ISDN Se0:23: TX ->  ALERTING pd = 8  callref = 0x8065
Mica Modem(2/2): State Transition to Call Setup
Mica Modem(2/2): Went offhook
CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 2, port 2
 
ISDN Se0:23: TX ->  CONNECT pd = 8  callref = 0x8065
ISDN Se0:23: RX <-  CONNECT_ACK pd = 8  callref = 0x0065
EVENT_FROM_ISDN::dchan_idb=0x60DD2D74, call_id=0x3, ces=0x1
   bchan=0x0, event=0x4, cause=0x0
.
.
.

Enter the debug modem ? command for list of additional modem debugging commands:

5300# debug modem ?
  b2b          Modem Special B2B
  csm          CSM activity
  maintenance  Modem maintenance activity
  mica         MICA Async driver debugging
  oob          Modem out of band activity
  tdm          B2B Modem/PRI TDM
  trace        Call Trace Upload

Configuring Modem Pooling

Use modem pooling to define, select, and use separate pools of modems within a single access server to enable different dialin services for different customers. The primary application is to allocate specific modems based on called party numbers and a predetermined number of modem ports based on Dialed Number Information Service (DNIS).

If you do not configure any modem pools, all the modems are placed into a single pool. There is no restriction on the number of modem pools that you can configure. A pool can contain a minimum of one modem and a maximum equal to all the modems in the system.

This section briefly shows how to set up a minimum configuration. For detailed information on using this feature, refer to the command reference documents shipped with your access server.

**Table 3-14: Configuring Modem Pooling**
Step	Command	Purpose
1	`5300#` `configure terminal` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
2	`5300(config)#` `modem-pool` name	Enter the name of the modem to configure for pooling.
3	`5300(config-modem-pool)#` `pool-range` `number-number`	Defines the range of the modems in the pool. A dash is required between the two numbers.
4	`5300(config-modem-pool)#` `called number` phone # `max-conn` number	Specifies the DNIS to be used for this modem pool. The DNIS string can have an integer x to indicate a don't care digit for that position. The max-conn option specifies the maximum number of connections allowed for this DNIS. If you do not specify a max-conn value, the default (total number of modems in the pool) is used. The max-conn values can range from one to the total number of modems in the pool.
5	`5300(config-modem-pool)#` `end`	Return to privileged EXEC mode.

Verify

To verify your modem pooling configuration:

Enter the show modem-pool command to view information for all modem pools. To view information for a specific modem pool, enter the show modem-pool name command.

5300# show modem-pool
modem-pool: System-def-Mpool
modems in pool: 119 active conn: 0
 0 no free modems in pool
modem-pool: test
modems in pool: 1 active conn: 0
 0 no free modems in pool
called_party_number: 1000
  0 max-conn exceeded, 0 no free modems in pool

Tips

If you are having trouble:

Make sure you have not configured the same called party number for multiple pools.
Make sure you have not placed modems in multiple pools.

Configuring IPX Networks

Configure the IPX networks for dial-in remote IPX users.

Configure

**Table 3-15: Configuring IPX Networks**
Step	Command	Purpose
1	5300(config)# ipx routing 5300(config)# interface loopback 0 5300(config-if)# ipx network FEFEFE 5300(config-if)# exit 5300(config)# interface ethernet 0 5300(config-if)# ipx network 123ABCD encapsulation SAP 5300(config-if)# exit 5300(config)# interface group-Async 1 5300(config-if)# group-range 1 48 [or] for E1 PRI 5300(config-if)# group-range 1 60 Building configuration... 5300(config-if)# ipx ppp-client Loopback 0 5300(config-if)# exit	Enable IPX clients to access network resources by dialing through the access server over ISDN.
2	5300(config)# interface dialer 1 5300(config-if)# `ipx ppp-client Loopback 0`	Create a dialer interface. This is the parent interface for all of the ISDN interfaces (this was set using the dialer rotary-group 1 command in the IP configuration).
3	5300(config-if)# dialer map ipx FEFEFE.0000.0c00.1234 name jordan 5300(config-if)# dialer map ipx FEFEFE.0000.0c00.4567 name rodman 5300(config-if)# dialer map ipx FEFEFE.0000.0c00.89AB name kemp 5300(config-if)# exit	Create a dialer map for the single IPX network address that contains all the dial-in users (for example, FEFEFE). The map for each IPX address differs and is activated by each dial-in user's login sessions. For IP configurations, dialer mapping is automatically constructed when the access server receives a user's name and address. However, when you use IPX configuration, you must statically configure each user name's IPX address.
4	5300(config)# dialer-list 1 protocol ipx permit 5300(config)# exit	Enable IPX packets to reset the idle timer.
5	5300# copy running-config startup-config #########[OK]	This completes the configuration for IPX. Save the running configuration to the start-up configuration: The access server will boot with your configuration at the next power up.

Verify

To verify the IPX routing is enabled:

Enter the show ipx interface serial command:

5300(config)# show ipx interface serial 1:23
Serial1:23 is up, line protocol is up
  IPX address is 2A.00e0.1e6b.2f6e [up]
  Delay of this IPX network, in ticks is 6 throughput 0 link delay 0
  IPXWAN processing not enabled on this interface.
  IPX SAP update interval is 1 minute(s)
  IPX type 20 propagation packet forwarding is disabled
  Incoming access list is not set
  Outgoing access list is not set
  IPX helper access list is not set
  SAP GNS processing enabled, delay 0 ms, output filter list is not set
  SAP Input filter list is not set
  SAP Output filter list is not set
  SAP Router filter list is not set
  Input filter list is not set
  Output filter list is not set
  Router filter list is not set
  Netbios Input host access list is not set
  Netbios Input bytes access list is not set
  Netbios Output host access list is not set
  Netbios Output bytes access list is not set
  Updates each 60 seconds, aging multiples RIP: 3 SAP: 3 
  SAP interpacket delay is 55 ms, maximum size is 480 bytes
  RIP interpacket delay is 55 ms, maximum size is 432 bytes
  Watchdog spoofing is disabled, SPX spoofing is disabled, idle time 60
  IPX accounting is disabled
  IPX fast switching is configured (disabled)
  RIP packets received 0, RIP packets sent 1
  SAP packets received 0, SAP packets sent 0

Tips

If you are having trouble:

Check for compression errors, events, packet activity errors, and IPX activity by using the debug ipx commands:
- Enter the debug ipx ? command to see a list of IPX debug options available:

    5300(config)# debug ipx ?
      compression     IPX compression
      eigrp           IPX EIGRP packets
      ipxwan          Novell IPXWAN events
      nasi            NASI server functionality
      nlsp            IPX NLSP activity
      packet          IPX activity
      redistribution  IPX route redistribution
      routing         IPX RIP routing information
      sap             IPX Service Advertisement information
      spoof           IPX and SPX Spoofing activity
      spx             Sequenced Packet Exchange Protocol

Enter a debug command from the above list to view the debug information.

Configuring AppleTalk

Configure AppleTalk to enable Macintosh clients to access network resources by dialing through the access server over ISDN.

Configure

**Table 3-16: Accessing AppleTalk Networks**
Step	Command	Purpose
1	`5300# configure terminal` `Enter configuration commands, one per line. End with CNTL/Z.` `5300(config)# appletalk routing` 5300(config)# `appletalk virtual-net 2 ATCP Zone`	Enable AppleTalk routing and set the AppleTalk zone ATCP¹ on network 2 (your network number and zones may differ). All users that dialin to the system will belong to the AppleTalk network 2 in the AppleTalk zone ATCP Zone. All the dial-in users will look as though they are on a single network. Links will not have their own network numbers. This applies to configurations using PPP instead of ARAP² encapsulation.
2	`5300(config)# appletalk cable-range 1-1 1.120` `5300(config-if)# appletalk zone Ethernet` `5300(config-if)# exit` 5300(config)# `exit`	Set the AppleTalk cable range and the AppleTalk zone on the Ethernet.
3	5300# `copy running-config startup-config` #########[OK]	Completes configuration for AppleTalk operation. Save the running configuration to the startup configuration.

¹ ATCP = AppleTalk Control Protocol.
² ARAP = AppleTalk Remote Access Protocol.

Verify

To verify the AppleTalk interface is up and running:

Enter the show appletalk interface serial command:

5300# show appletalk interface serial 1:23
Serial1:23 is up, line protocol is up
  AppleTalk address is 10.1, Valid
  AppleTalk zone is "dolzone"
  AppleTalk discarded 37 packets due to output errors
  AppleTalk address gleaning is not supported by hardware
  AppleTalk route cache is disabled, Dial on Demand specified

Tips

If you are having trouble, you can troubleshoot the AppleTalk protocol by using its debug commands to view information for the errors, events, and packets and check the Gateway name, NAS name, and if the virtual access interface is up.

Enter the debug ppp negotiation command:

5300# debug ppp negot
PPP protocol negotiation debugging is on
5300#
%LINK-3-UPDOWN: Interface Async1, changed state to up
PPP Async1: treating connection as a dedicated line
ppp: sending CONFREQ, type = 2 (CI_ASYNCMAP), value = 0xA0000
ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = 0xC223/5
ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 0xAB1BAB3
PPP Async1: state = REQsent fsm_rconfack(0xC021): rcvd id 7
ppp: config ACK received, type = 2 (CI_ASYNCMAP), value = 0xA0000
ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = 0xC223
ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 0xAB1BAB3
ppp: config ACK received, type = 7 (CI_PCOMPRESSION)
ppp: config ACK received, type = 8 (CI_ACCOMPRESSION)
PPP Async1: received config for type = 1 (MRU) value = 1500 acked
PPP Async1: received config for type = 2 (ASYNCMAP) value = 0x0 acked
PPP Async1: received config for type = 5 (MAGICNUMBER) value = 0x565CFA6A acked
PPP Async1: received config for type = 7 (PCOMPRESSION) acked
PPP Async1: received config for type = 8 (ACCOMPRESSION) acked
ipcp: sending CONFREQ, type = 2 (CI_COMPRESSTYPE), slots = 15, csid = 0
ipcp: sending CONFREQ, type = 3 (CI_ADDRESS), Address = 171.60.199.193
Resetting ATCP
atcp: sending CONFREQ, type = 6 (CI_AT_SERVERINFO), values = 119132, 6
atcp: sending CONFREQ, type = 7 (CI_AT_ZONEINFO), values = 1191B3, 9
atcp: sending CONFREQ, type = 8 (CI_AT_DEFAULT_ROUTER), values = 5, C7
.
.
.

Enter the show interface async 1 command:

5300# show int async 1
Async1 is up, line protocol is up 
  Hardware is Async Serial
  Interface is unnumbered.  Using address of Ethernet0 (171.60.199.193)
  MTU 1500 bytes, BW 38 Kbit, DLY 100000 usec, rely 255/255, load 1/255
  Encapsulation PPP, loopback not set, keepalive not set
  DTR is pulsed for 5 seconds on reset
  LCP Open
  Open: IPCP, ATALKCP
  Last input 00:00:01, output 00:00:08, output hang never
  Last clearing of "show interface" counters 07:17:22
  Input queue: 1/75/0 (size/max/drops); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/64/0 (size/threshold/drops) 
     Conversations  0/9 (active/max active)
     Reserved Conversations 0/0 (allocated/max allocated)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     753 packets input, 22232 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     638 packets output, 37821 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions

Enter the show apple interface async 1 command:

5300# show apple int async 1
Async1 is up, line protocol is up
  AppleTalk port is in client-mode
  AppleTalk discarded 3 packets due to input errors
  AppleTalk address gleaning is not supported by hardware
  AppleTalk route cache is disabled, port down

You can also set the access server to display events messages for the AppleTalk interface by using the debug appletalk events command. When done troubleshooting, enter the no debug appletalk events to turn off the messages.

5300# debug appletalk events
AppleTalk Events debugging is on
*Aug 15:56:06.907: AT: RTMP GC complete (0 PDBs freed, 0 PDBs waiting)
*Aug 15:17:56:06.927: AT: Connected GC complete (0 PDBs freed, 0 PDBs waiting)

Enter the debug appletalk ? command for a list of the appletalk debug commands:

    5300# debug appletalk ?
      arp                   Appletalk address resolution protocol
      aurp-connection       AURP connection
      aurp-packet           AURP packets
      aurp-update           AURP routing updates
      domain                AppleTalk Domain function
      eigrp-all             All AT/EIGRP functions
      eigrp-external        AT/EIGRP external functions
      eigrp-hello           AT/EIGRP hello functions
      eigrp-packet          AT/EIGRP packet debugging
      eigrp-query           AT/EIGRP query functions
      eigrp-redistribution  AT/EIGRP route redistribution
      eigrp-request         AT/EIGRP external functions
      eigrp-target          Appletalk/EIGRP for targeting address
      eigrp-update          AT/EIGRP update functions
      errors                Information about errors
      events                Appletalk special events
      fs                    Appletalk fast-switching
      iptalk                IPTalk encapsulation and functionality
      load-balancing        AppleTalk load-balancing
      macip                 MacIP functions
      nbp                   Name Binding Protocol (NBP) functions
      packet                Per-packet debugging
      redistribution        Route Redistribution
      remap                 AppleTalk Remap function
      responder             AppleTalk responder debugging
      routing               (RTMP&EIGRP) functions
      rtmp                  (RTMP) functions
      zip                   Zone Information Protocol functions

Configuring MMP

If you have multiple access servers stacked together to provide a frontend for receiving access calls, you can configure Multichassis Multilink Point-to-Point Protocol (MMP) so that Multilink PPP (MP) call processing can be offloaded to other access servers.

MMP support on a group of access servers requires that each access server be configured to support:

Stack Group Bidding Protocol (SGBP)
Virtual templates used for cloning interface configurations to support MMP
Multilink PPP

Configure

**Table 3-17: Configuring MMP**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	5300(config)# `sgbp group stackq`	Create a stack group and assign this access server to it.
4	5300(config)# `sgbp member systemb 172.16.188.2` 5300(config)# `sgbp member systemc 172.16.189.254`	Specify the host name and IP address of the peer member of the stack group. In this example there are two peers: systemb and systemc.
5	5300(config)# `sgbp seed-bid offload`	Set the bidding level for a stack group member. Offload indicates that this access server is a relatively higher powered stack group member. The access server will function as an offload server and host the master bundle interface.
6	`5300(c`onfig)# multilink virtual-template number	Define a virtual template¹ for the stack group.
7	5300(config)# ip local pool default ip-address	Specify an IP address pool by using any pooling mechanism--for example, IP local pooling or DHCP² pooling.
8	5300(config)# `interface virtual-template` `number`	Create a virtual template interface, and enter interface configuration mode.
9	5300(config-if)# `ip unnumbered ethernet 0`	If dialers are not configured on the physical interfaces, identify the virtual template interface type and number on the LAN.
10	5300(config-if)# `encapsulation ppp`	Enable PPP encapsulation on the virtual template interface.
11	5300(config-if)# `ppp multilink`	Enable Multilink PPP on the virtual template interface.
12	5300(config-if)# `ppp authentication chap`	Enable PPP authentication on the virtual template interface.
13	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

¹ A virtual template is a serial interface configuration with no hardware association.
² DHCP = Dynamic Host Configuration Protocol.

Verify

To verify the MMP configuration on each server:

Enter the show sgbp command:

5300-7# show sgbp
Group Name: test Ref: 0x4780B252
Seed bid: default, 50, default seed bid setting
 
  Member Name: 5300-3 State: active Id: 9
  Ref: 0x4780B54D
  Address: 172.22.21.8
5300-3# show sgbp
Group Name: test Ref: 0x4780B54D
Seed bid: default, 50, default seed bid setting
 
  Member Name: 5300-7 State: active Id: 1
  Ref: 0x4780B252
  Address: 172.22.21.12

Note the following:

Check to make sure State is active. State set to idle indicates there is a misconfiguration on either side.
Check to make sure the username and password are configured for the sgbp group; otherwise the servers will not be able to talk to each other.

Tips

If you are having trouble:

Enter the debug sgbp ? command to view a list of available debugging commands:

5300# debug sgbp ?
  errors    SGBP errors
  events    SGBP events
  hellos    SGBP connection hellos
  messages  SGBP messages
  queries   SGBP mastership queries

Enter the debug sgbp errors command to view error messages. When you finish viewing the messages, enter the no debug sgbp errors to turn off the messages.

5300# debug sgbp errors
*Mar  4 11:55:24.105 EST: %SGBP-1-MISSCONF: Possible misconfigured member 5300-6 using 172.22.21.11
*Mar  4 11:55:41.185 EST: %SGBP-7-NORESP: Fail to response to 5300-3 group test, may not have password

: Error messages are displayed if one server 5300-6 shows an sgbp group configured but the group is not configured for another server in the group. Error messages are also displayed if the password is not configured for the sgbp group.

Enter the debug sgbp events command to view event messages. When you finish viewing the messages, enter the no debug sgbp events to turn off the messages.

5300# debug sgbp events
*Mar  4 12:26:46.441 EST: %SGBP-7-CLOSE: Closing pipe for member 5300-3
*Mar  4 12:26:46.445 EST: %SGBP-5-LEAVING: Member 5300-3 leaving grouptest

: The above event message indicates that the sgbp connection went down and 5300-3 is no longer part of the 5300-7 sgbp group. You can check 5300-3 for the reasons why the sgbp connection went down. Possibly, the sgbp member entry for 5300-7 was removed or there is no communication between 5300-7 and 5300-3.

Creating Authentication Accounts

You can create authentication accounts for other routers in an MMP stack. If your stack name is STACK1, you need to create a user account called STACK1 on each router with the same password.

username STACK1 password cisco
sgbp group STACK1
sgbp member <other router name> <other router IP address>

Configuring VPDN

Virtual private dial-up networking (VPDN) enables users to configure secure networks that take advantage of Internet service providers (ISPs) that tunnel a company's remote access traffic through the ISP cloud.

Remote offices or mobile users can connect to their home network using local third-party dial-up services. The dial-up service provider agrees to forward the company's traffic from the ISP point of presence (POP) to a company-run home gateway. Network configuration and security remains in the control of the client. The dial-up service provider provides a virtual connection between the company's sites.

Note The MMP feature uses VPDN to connect multiple PPP sessions for which individual dial-in calls have arrived on different stack group members. VPDN provides speed and reliability for the setup and shutdown of Multilink PPP.

Configure

**Table 3-18: Configuring VPDN**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	`5300#` `config term` `Enter configuration commands, one per line. End` `with CNTL/Z.` `5300(config)#`	Enter global configuration mode. You have entered global configuration mode when the prompt changes to `5300(config)#.`
3	5300(config)# `vpdn enable`	Enable virtual private dial-up networking.
4	5300(config)# `vpdn outgoing domain1.com nas1 ip 172.21.9.18` 5300(config)# `vpdn outgoing domain2.com nas2 ip 173.22.10.19`	Specify the name and IP address of the remote host and the name to use when authenticating a tunnel for forwarding traffic to the remote host on a virtual private dial-up network. In this example, two remote hosts are specified.
5	`5300(config-line)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Verify

To verify your VPDN configuration:

Enter the show vpdn command to make sure the tunnels are active (see line 2 in the following example):

5300# show vpdn
Active L2F tunnels = 2
NAS Name        Gateway Name    NAS CLID   Gateway CLID   State
test-mmp        test-mmp          272          272        open
192.168.1.99    192.168.1.119    
 
L2F MIDs = 10
Name                       NAS Name      Interface    MID      State
rw56                       test-mmp       Vi238        1       open
rw55                       test-mmp       Vi240        3       open
rw54                       test-mmp       Vi242        4       open
rw57                       test-mmp       Vi246        7       open
rw57                       test-mmp       Vi248        8       open
rw54                       test-mmp       Vi245        13      open
rw55                       test-mmp       Vi244        14      open
rw16                       test-mmp       Vi249        97      open
rw16                       test-mmp       Vi251        98      open
rw56                       test-mmp       Vi250        100     open

Tips

If you are having trouble:

Troubleshoot the VPDN protocol by using its debug commands to view information for the errors, events, and packets and check the Gateway name, network access server (NAS) name, and if the virtual access interface is up.
- Enter debug vpdn ? command to view a list of debug vpdn commands:

    5300# debug vpdn ?
      error        VPDN Protocol errors
      event        VPDN event
      l2f-errors   L2F protocol errors
      l2f-events   L2F protocol events
      l2f-packets  L2F protocol packets
      packet       VPDN packet

Enter debug commands to view error information. When you finish viewing the messages, enter no debug vpdn command to turn off the debug messages:

: This is sample output for the debug vpdn event command:

    5300# debug vpdn event
      VPN events debugging is on
         *May 15 17:55:49.367: %LINK-3-UPDOWN: Interface Virtual-Access239,      
      changed state to down
      *May 15 17:55:49.547: Virtual-Access249 VPN reset
      *May 15 17:55:49.547: %LINK-3-UPDOWN: Interface Virtual-Access249,
      changed state to down

: This is sample output for the debug vpdn l2f-events command:

    5300# debug vpdn l2f-events
      L2F protocol events debugging is on
      *May 15 17:56:46.259: L2F_OPEN received
      *May 15 17:56:46.263: L2F Got a MID management packet
      *May 15 17:56:46.339: %LINK-3-UPDOWN: Interface Virtual-Access239,
      changed state to up

: This is sample output for the debug vpdn l2f-errors command:

    5300# debug vpdn l2f-errors
      L2F protocol errors debugging is on
      *May 15 17:57:57.827: %LINK-3-UPDOWN: Interface Virtual-Access251,
      changed state to down

Creating Authentication Accounts

You can create authentication accounts for other routers between the NAS and the HGW for VPDN.

On the NAS, an example is:

username NAS password cisco
username HGW password cisco
vpdn enable
vpdn outgoing cisco.com NAS ip X.X.X.X

On the HGW, an example is:

username NAS password cisco
username HGW password cisco
vpdn enable
vpdn incoming NAS HGW virtual-template 1

Saving Configuration Changes

To prevent from losing the access server configuration, save it to NVRAM.

Configure

**Table 3-19: Saving Configuration Changes**
Step	Command	Purpose
1	`5300>` `enable` `Password:` <*password*> `5300#`	Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to `5300#`.
2	5300# `copy running-config startup-config`	Save the configuration changes to NVRAM so that they are not lost during resets, power cycles, or power outages.
3	`5300(config-if)#` `end` `5300#` `%SYS-5-CONFIG_I: Configured from console by console`	Return to privileged EXEC mode. This message is normal and does not indicate an error.

Comprehensive Configuration Example

The following example shows the output of the show config command. If you are experienced with the Cisco IOS software, you might find this a useful reference for configuration.

5300# show config
hostname 5300
enable secret 5 $1$zOXQ$cCmcXwI/6m9Dp2D47377c.
enable password guessme
line vty 0 4
password guessagain
snmp-server community public
!
appletalk routing
no decnet routing
ip routing
no clns routing
ipx routing
no vines routing
no xns routing
no apollo routing
no bridge 1
!
! Turn off IPX to prevent network conflicts.
interface Ethernet0
no ipx network
interface FastEthernet0
no ipx network
chat-script cisco-default ABORT ERROR "" "AT Z" OK "ATDT \T" TIMEOUT 30 \c CONNECT \c
!
line 1 48
speed 9600
flowcontrol hardware
modem inout
modem chat-script cisco-default
!
arap network 1 ARA Dialins
line 1 48
arap enable
autoselect
!
interface Ethernet0
shutdown
no ip address
!
interface FastEthernet0
ip address 172.21.40.10 255.255.255.0
appletalk address 10.0
appletalk zone etherzone
ipx network 1
no mop enabled
!
Interface Async1
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async2
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async3
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async4
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async5
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async6
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async7
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async8
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async9
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async10
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async11
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async12
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async13
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async14
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async15
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async16
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async17
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async18
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async19
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async20
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async21
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async22
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async23
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async24
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async25
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async26
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async27
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async28
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async29
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async30
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async31
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async32
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async33
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async34
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async35
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async36
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async37
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async38
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async39
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async40
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async41
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async42
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async43
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async44
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async45
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async46
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async47
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
Interface Async48
ip unnumbered Ethernet0
ip tcp header-compression passive
async mode interactive
async dynamic address
!
router igrp 15
network 172.21.0.0
!
end

This concludes the basic access server configuration.

Where to Go Next

At this point you can proceed to:

The chapter "Access Service Security" to configure security on the access server.
The Cisco IOS software configuration guide and command reference publications for more advanced configuration topics. These publications are available on the documentation CD that came with your access server, on the World Wide Web from Cisco's home page, or you can order printed copies.

For troubleshooting information, refer to the System Error Messages and Debug Command Reference publications.

Table of Contents