|
|
Cisco 802 IDSL and Cisco 804 IDSL routers offer high-speed digital connections using an ISDN line and support line rates up to 144 kilobits per second (kbps). Integrated Services Digital Network (ISDN) Digital Subscriber Line (IDSL) expands DSL connectivity for customers who are outside the Service Provider's range for DSL or for those who are unable to qualify for DSL connections.
This document describes the setup and configuration of your routers and contains the following sections:
The following figure shows a typical setup of the Cisco 804 IDSL router.

Before you begin installing your Cisco IDSL router, read the following topics:
Before installing the router, read the following warnings:
![]() | Warning Only trained and qualified personnel should be allowed to install or replace this equipment. |
![]() | Warning Read the installation instructions before you connect the system to its power source. |
![]() | Warning Before working on a system that has a standby/off switch, turn the power to standby and unplug the power cord. |
![]() | Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals. |
![]() | Warning The IDSL connection is regarded as a source of voltage that should be inaccessible to user contact. Do not attempt to tamper with or open any public telephone operator (PTO)-provided equipment or connection hardware. Any hardwired connection (other than by a nonremovable, connect-one-time-only plug) must be made only by PTO staff or suitably trained engineers. |
![]() | Warning To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. |
![]() | Warning Ultimate disposal of this product should be handled according to all national laws and regulations. |
![]() | Warning
If the symbol of suitability with an overlaid cross ( ) appears above a port, you must not connect the port to a public network that follows the European Union standards. Connecting the port to this type of public network can cause severe injury or damage your router. |
Always use the following ESD-prevention procedures when removing and replacing components:
1. Connect the chassis to earth ground with a wire that you provide.
2. Wear an ESD-preventive wrist strap that you provide, ensuring that it makes good skin contact.
Connect the clip to an unpainted surface of the chassis frame to safely channel unwanted ESD voltages to ground. To properly guard against ESD damage and shocks, the wrist strap and cord must operate effectively. If no wrist strap is available, ground yourself by touching the metal part of the chassis. Always follow the guidelines in the preceding section, "Safety."
3. Do not touch any exposed contact pins or connector shells of interface ports that do not have a cable attached.
If cables are connected at one end only, do not touch the exposed pins at the unconnected end of the cable.
Use the following guidelines when connecting devices to your router:
) appears above a port, you can connect the port directly to a public network that follows the European Union standards.
![]() | Warning
If the symbol of suitability with an overlaid cross ( ) appears above a port, you must not connect the port to a public network that follows the European Union standards. Connecting the port to this type of public network can cause severe injury or damage your router. |
Unpack the Open Me First bag, the desktop power supply, and the black power cord. The following figure shows the contents of the Open Me First bag. However, the power supply and the power cord are in the accessory kit.

The following figures show the router ports. These ports and the cables are color-coded to help you connect the cables correctly.

For more information, see the following subsections:
This section describes how to connect a hub, server, PC, or workstation with a 10- or 10/100-Mbps network interface card (NIC).
Before connecting an Ethernet device, you need to know the following:
![]() | Caution Always connect the yellow cable or Ethernet cable to the yellow ports on the router. Do not connect the cable to an IDSL port or to a Network Termination 1 (NT1) device. Accidently connecting the cable to the wrong port can damage your router. |

Step 1 Connect the yellow cable to one of the following ports:
Step 2 Connect the other end of the cable to the hub.
Step 3 Check the LED corresponding to the connected port after router power-up:
Step 4 If the LED corresponding to the connected port is not on, do the following:

Step 1 Connect the yellow cable to one of the following ports:
Step 2 Connect the other end of the cable to the server, PC, or workstation.
Step 3 Check the LED corresponding to the connected port after router power-up:
Step 4 If the LINK or ETHERNET 1 LED is not on, try pressing the TO HUB/TO PC button.
Step 5 If the ETHERNET 2, 3, or 4 LED is not on, see the Cisco 800 Series Routers Hardware Installation Guide.
![]() | Caution Always connect the yellow cable or Ethernet cable to the yellow ports on the router. Do not connect the cable to an IDSL port or to a Network Termination 1 (NT1) device. Accidently connecting the cable to the wrong port can damage your router. |

Step 1 Connect the red cable to the red IDSL port.
Step 2 Connect the other end of the cable to the IDSL wall jack. If your wall jack has an RJ-11 connector, attach the RJ-45-to-RJ-11 adapter cable to the red cable, and then connect the RJ-11 connector to the IDSL wall jack.

Step 1 Make sure the router power is off. Press the power switch to standby (
).
Step 2 Connect the power supply cable to the 8-pin connector on the router.
Step 3 Connect the power cord to the desktop power supply.
Step 4 Connect the other end of the power cord to an electrical outlet.
Step 5 Turn on the router. Press the power switch to on (|).
Verify the power connection and all other connections (links) by checking the LEDs in the table below. If the LEDs are not on, see the troubleshooting information in the Cisco 800 Series Routers Hardware Installation Guide.
| Power/Link | LEDs To Check | Normal Patterns |
|---|---|---|
Power | OK | On |
To hub, server, PC, or workstation | Cisco 802 IDSL back panel: LINK LED Cisco 804 IDSL front panel: ETHERNET 1, 2, 3, and 4 LEDs | On |
To IDSL network using IDSL port | NT1, LINE, CH1, or CH2 | On (CH1 or CH2 is on only when the router has an active data connection. With a 64 kbps connection, only CH1 is on. With a 128 or 144 kbps connection, both CH1 and CH2 are on). |
You can configure your Cisco IDSL router using the Cisco IOS command-line interface or the Cisco 800 Fast Step application. For information about using Cisco 800 Fast Step, refer to the Cisco 800 DSL Connection Kit document in the product accessory kit or on Cisco Connection Online (CCO).
The following procedures are examples of how to configure the Cisco IDSL router using Cisco IOS commands. For more information about Cisco IOS commands, refer to the Cisco IOS documentation set on the Documentation CD-ROM or CCO.
The following is an example of a typical IDSL configuration.
Step 1 In global configuration mode, specify a name for the router. For example:
router(config)# hostname 802
Step 2 Specify a username and password. The username is the destination router's hostname. The password must be the same for both the host and destination routers. For example:
router(config)# username isp password cisco
Step 3 Set the switch type. For example:
router(config)# isdn switch-type basic-5ess
Step 4 Set the BRI interface to use the ISDN physical connection as a leased-line service. The following example sets the line speed at 128 kbps:
router(config)# isdn leased-line bri0 128
Step 5 Configure DHCP relay pool name. For example:
router(config)# ip dhcp pool DHCPpoolLAN_0
Step 6 Set the DHCP pool of addresses. For example:
router(dhcp-config)# network 192.168.1.0 255.255.255.0
Step 7 Set the IP addresses of the DNS servers. For example:
router(dhcp-config)# dns-server 172.29.20.41 172.29.20.51
Step 8 Set the NetBIOS servers. For example:
router(dhcp-config)# netbios-name-server 172.29.20.41 172.29.20.51
Step 9 Set the Ethernet 0 IP address as the default gateway. For example:
router(dhcp-config)# default-router 192.168.1.1
Step 10 Exit to global configuration mode.
router(dhcp-config)# exit router(config)#
Step 11 Define the IP addresses of the DNS servers. For example:
router(config)# ip name-server 172.29.20.41 router(config)# ip name-server 172.29.20.51
Step 12 Change to interface command mode. For example:
router(config)# interface ethernet0 router(config-if)#
Step 13 Enter the IP address and subnet mask for the LAN. For example:
router(config-if)# ip address 192.168.1.1 255.255.255.0
Step 14 Enable Network Address Translation (NAT) on your LAN. The inside network address is not directly routed to the Internet but is subject to translation to a routable address outside the LAN.
router(config-if)# ip nat inside
Step 15 Set the BRI interface IP address. In the following example, IP addresses are dynamically assigned:
router(config-if)# interface bri0 router(config-if)# ip address negotiated
Step 16 Enable PPP.
router(config-if)# encapsulation ppp
Step 17 Configure CHAP authentication.
router(config-if)# ppp authentication chap
Step 18 Configure a valid Internet address to which the inside network address will be translated.
router(config-if)# ip nat outside
Step 19 Define the router hostname and password to authenticate. For example:
router(config-if)# ppp chap hostname 802 router(config-if)# ppp chap password cisco
Step 20 Exit to global configuration mode. Add default route and interface. For example:
router(config-if)# exit router(config)# ip route 0.0.0.0 0.0.0.0 bri0
Step 21 End configuration mode.
router(config)# end router#
Step 22 In user mode, set global NAT commands. In the following example, all inside network addresses assigned to interface BRI0 are configured for translation, and the access list that contains the inside network addresses is defined.
router# ip nat inside source list 1 interface bri0 overload router# access-list 1 permit 192.168.1.0 0.0.0.255
Step 23 Save your configuration.
router# copy running-config startup-config
Current configuration: ! version 12.0 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname cisco802 ! ! ! ! ip subnet-zero ! isdn switch-type basic-5ess isdn leased-line BRI0 128 ip dhcp pool DHCPoolLAN_0 network 192.168.1.0 255.255.255.0 dns-server 172.29.20.41 172.29.20.51 netbios-name-server 172.29.20.41 172.29.20.51 default-router 192.168.1.1 ip name-server 172.29.20.41 ip name-server 172.29.20.51 ! ! interface Ethernet0 ip address 192.168.1.1 255.255.255.0 no ip directed-broadcast ip nat inside ! interface BRI0 ip unnumbered negotiated no ip directed-broadcast encapsulation ppp ppp authentication chap ip nat outside ppp chap hostname 802 ppp chap password cisco ! ip classless ip route 0.0.0.0 0.0.0.0 bri 0 ! ip nat inside source list 1 interface bri0 overload access-list 1 permit 192.168.1.0 0.0.0.255 ! line con 0 transport input none stopbits 1 line vty 0 4 end cisco802#
The following procedure is an example of how to configure IDSL with Frame Relay.
Step 1 In global configuration mode, specify a name for the router. For example:
router(config)# hostname 802
Step 2 Specify a username and password. The username is the destination router's hostname. The password must be the same for both the host and destination routers. For example:
router(config)# username isp password cisco
Step 3 Set the switch type. For example:
router(config)# isdn switch-type basic-5ess
Step 4 Set the BRI interfaces to use the ISDN physical connection as a leased-line service. The following example sets the line speed at 144 kbps:
router(config)# isdn leased-line bri0 144 router(config)# isdn leased-line bri0.1 144
Step 5 Change to interface command mode. For example:
router(config)# interface ethernet0
Step 6 Enter an IP address. For example:
router(config-if)# ip address 192.168.2.1 255.255.255.0
Step 7 Enable Network Address Translation (NAT) on your LAN. The inside network address is not directly routed to the Internet but is subject to translation to a routable address outside the LAN.
router(config-if)# ip nat inside
Step 8 Change to BRI interface.
router(config-if)# interface bri0
Step 9 Configure interface with no IP address.
router(config-if)# no ip address
Step 10 Configure NAT so that the inside network address will be translated to a valid Internet address.
router(config-if)# ip nat outside
Step 11 Specify the encapsulation type. In the following example, IETF is used to connect to non-Cisco routers.
router(config-if)# encapsulation frame-relay ietf
Step 12 Specify the Local Management Interface (LMI) type used by the Frame Relay switch. For example:
router(config-if)# frame-relay lmi-type ansi
Step 13 Specify the subinterface point-to-point. For example:
router(config-if)# interface bri0:1 point-to-point
Step 14 Specify the IP address on the subinterface. For example:
router(config-if)# ip address 209.188.2.2 255.255.255.0
Step 15 Specify a DLCI number that is used to connect to the Internet service provider. For example:
router(config)# frame-relay interface dlci 16 ieft
Step 16 End configuration mode.
router(config)# end router#
Step 17 In user mode, set global NAT commands. In the following example, all inside network addresses assigned to interface BRI0 are configured for translation, and the access list that contains the inside network addresses is defined.
router# ip nat inside source list 1 interface bri0 overload router# access-list 1 permit 192.168.1.0 0.0.0.255
Step 18 Save your configuration.
router# copy running-config startup-config
Current configuration: ! ! version 12.0 service timestamps debug uptime service timestamps log uptime ! hostname c802idsl username isp password 0 cisco ! ! ip subnet-zero ! isdn switch-type basic-5ess isdn leased-line BRI0 144 isdn leased-line BRI0.1 144 ! ! interface Ethernet0 ip address 192.168.2.1 255.255.255.0 ip nat inside ! interface BRI0 no ip address encapsulation frame-relay IETF frame-relay lmi-type ansi ! interface BRI0.1 point-to-point ip address 209.188.2.2 255.255.255.0 frame-relay interface-dlci 16 IETF ip nat outside ! ip nat inside source list 1 interface bri0:1 overload access-list 1 permit 192.168.2.0 0.0.0.255 ip classless ip route 0.0.0.0 0.0.0.0 209.188.2.1 ! ! line con 0 exec-timeout 0 0 transport input none stopbits 1 line vty 0 4 ! end
In general, Cisco recommends that you use these commands with the direction of your technical support representative. Using the debug commands can disrupt operation of the router when your internetwork is experiencing a high-load condition.
When you finish using a debug command, remember to disable it with the specific no debug command or with the no debug all command.
To minimize the impact of using debug commands, use the following procedure:
Step 1 Enter the following command from global configuration mode:
router (config)# no logging console
This command disables all logging to the terminal or PC that you are troubleshooting the software from. (To reenable logging, enter the global configuration mode logging console enable command.)
Step 2 To use the debug commands, do the following:
(a) Access any router port remotely using Telnet, and enter the following command while in user EXEC mode:
router> enable
(b) To show debug command output and error messages, enter the following command:
router> terminal monitor
To disable logging on the virtual terminal, enter the following command:
router> terminal no monitor
(c) Enter the desired debug commands.
Performing this procedure minimizes the load created because the console port no longer needs to generate character-by-character processor interrupts.
The following table describes debug commands, problems your router might be experiencing, and solutions to the problems. An output example from each command appears after the table.
| Command | Possible Problem | Solution |
show isdn status See output 1 example following this table. |
|
|
|
|
|
|
|
|
|
| If the problem continues after these steps, call your Cisco reseller. |
|
|
|
debug ppp negotiation, debug ppp authentication See output 2 example following this table. |
|
|
The current ISDN Switchtype = basic-ni1
ISDN BRI0 interface
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
Total Allocated ISDN CCBs = 0
isdn#
ISDN BR0:TX -> RRp sapi = 0 tei = 80 nr = 1
ISDN BR0:RX <- RRf sapi = 0 tei = 80 nr = 1
isdn#
ISDN BR0:TX -> RRp sapi = 0 tei = 81 nr = 1
ISDN BR0:RX <- RRf sapi = 0 tei = 81 nr = 1
ISDN BR0:TX -> RRp sapi = 0 tei = 80 nr = 1
ISDN BR0:RX <- RRf sapi = 0 tei = 80 nr = 1
isdn#und all
isdn#show isdn st
The current ISDN Switchtype = basic-dms100
ISDN BRI0 interface
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 80, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 81, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
No Active Layer 3 Call(s)
Activated dsl 0 CCBs = 0
pico#ping 192.9.198.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.9.198.1, timeout is 2 seconds: %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEF99 ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 acked ppp: received config for type = 5 (MAGICNUMBER) value = 1E23F5C acked PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E4 ppp: config ACK received, type. = 3 (CI_AUTHTYPE), value = C223 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEEF99 BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 82 len = 16 BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 95 len = 28 BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 82 len = 21 BRI0: B-Channel 1: Failed CHAP authentication with remote. Remote message is: MD compare failed ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEEFDB %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up ppp: sending CONFREQ, type = 3 (CI_AUTHTYPE), value = C223/5 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 28CEF76C ppp: received config for type = 3 (AUTHTYPE) value = C223 value = 5 acked ppp: received conf.ig for type = 5 (MAGICNUMBER) value = 1E24718 acked PPP BRI0: B-Channel 1: state = ACKSENT fsm_rconfack(C021): rcvd id E6 ppp: config ACK received, type = 3 (CI_AUTHTYPE), value = C223 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 28CEF76C BRI0: B-Channel 1: PPP AUTH CHAP input code = 1 id = 83 len = 16 BRI0: B-Channel 1: PPP AUTH CHAP input code = 2 id = 96 len = 28 BRI0: B-Channel 1: PPP AUTH CHAP input code = 4 id = 83 len = 21 BRI0: B-Channel 1: Failed CHAP authentication with remote. Remote message is: MD compare failed
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Jan 11 23:32:31 PST 2000
Copyright 1989-2000©Cisco Systems Inc.