--begin ciscomoderator note-- The following post has been edited to remove potentially confidential information. Please refrain from posting confidential information on the site to reduce security risks to your network. -- end ciscomoderator note --
Can anyone help, I am having problems with the isdn on a 1603 router. The config below is one i took straight out of a cisco manual so i assume it is ok, but i stll cant get the bri port to dial. I have checked the isdn line with other equipment and they are fine. i am trying to dial an adtran over isdn. All i want to see at this stage is that the cisco has dialled.
please find attached a copy of the config i have on the 1603, and an output when i try to ping ( with debug q921,931, and dialer switched on):
router config :
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
username cisco-b xxxxxxxx0 xxxxxxxx
isdn switch-type basic-net3
no ip address
ip address 10.170.0.1 255.255.0.0
dialer idle-timeout 300
dialer map ip 10.170.0.2 name cisco-b xxxxxxxxxxxxxxxx
ppp authentication chap
ip route 192.168.1.0 255.255.255.0 10.170.0.2
dialer-list 1 protocol ip permit
line con 0
line vty 0 4
and here is the output from a ping :
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
00:35:59: BRI0: Dialing cause ip (s=10.170.0.1, d=192.168.1.1)
00:35:59: BRI0: Attempting to dial --moderator edit-- xxxxxxxxxxxx
00:35:59: ISDN BR0: TX -> IDREQ ri = 48769 ai = 127 .
00:36:01: ISDN BR0: TX -> IDREQ ri = 42642 ai = 127 .
00:36:03: ISDN BR0: TX -> IDREQ ri = 4019 ai = 127 .
00:36:05: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 255 changed to down
00:36:07: BRI0: wait for carrier timeout, call id=0x800A.
Success rate is 0 percent (0/5)
Any suggestions would be great. By the way the sh isdn stat shows deactivated and the bri light(s) on the cisco are not /have not lit. As i say thought the lines are good.
"sh isdn stat" should indicate "ACTIVE" in Layer 1 and "MULTIPLE_FRAME_ESTABLISHED" in Layer 2. If either if these antries aren't there, don't bother attempting to dial, as it will definitely fail.
Also, try to clear up the BRI interface by issuing the "clear int bri0". You can also do a "shut" and "no shut" on the BRI interface to try to reset the link. Sometimes, rebooting also helps.
If that didn't work, check with your provider if you're using the correct ISDN switch-type. Also, if you're in a region that requires you to put in some SPIDs (also provided by your provider), you will need to do so using the following commands under the BRI interface config:
In the end, your "sh isdn stat" should look something like the following example output: (Taken from a 2600 router)
sh isdn stat
Global ISDN Switchtype = basic-ni
ISDN BRI0/0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
Layer 2 Status:
TEI = 111, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 112, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...