- Posts: 8
- Thank you received: 0
My Cisco Lab Woes
17 years 9 months ago #19812
by surfer
Well i configured PPP using the 'encap ppp' command on all the interfaces. Saved and reload just to make sure... still no luck... Any ideas?
Replied by surfer on topic Re: My Cisco Lab Woes
Done all of that and still no joy. Think i'll try configuring an alternative to HDLC and see how that works.
Well i configured PPP using the 'encap ppp' command on all the interfaces. Saved and reload just to make sure... still no luck... Any ideas?
17 years 9 months ago #19813
by Dove
Dove
Replied by Dove on topic Re: My Cisco Lab Woes
A Cisco router is a DTE by default, but directly connecting two DTEs with a DCE/DTE cable is not enough.
The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds. The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. By using the following
show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The router with the DCE end of the cable needs to supply a clock rate to the DTE,
The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds. The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. By using the following
show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The router with the DCE end of the cable needs to supply a clock rate to the DTE,
Dove
17 years 9 months ago #19814
by Dove
Dove
Replied by Dove on topic Re: My Cisco Lab Woes
A Cisco router is a DTE by default, but directly connecting two DTEs with a DCE/DTE cable is not enough.
The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds. The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. By using the following
show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The router with the DCE end of the cable needs to supply a clock rate to the DTE,
The line goes up briefly after being opened, but the line protocol goes down after about 30 seconds. The problem is that one of the routers needs to act as the DCE in order for the line protocol to come up and stay up. you could just go over and look at the DTE/DCE cable to see which router had the DCE end of the cable attached. By using the following
show controller serial 1
HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8
buffer size 1524 HD unit 1, V.35 DCE cable
The router with the DCE end of the cable needs to supply a clock rate to the DTE,
Dove
17 years 9 months ago #19819
by surfer
Replied by surfer on topic Re: My Cisco Lab Woes
Each router has the DCE end of the cable in it's serial 0 port, and i'm pretty sure the configuration reflects that correctly.
Matt:[code:1]matt#sh cont se 0
HD unit 0, idb = 0x2484F8, driver structure at 0x249910
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
matt#sh cont se 1
HD unit 1, idb = 0x275E40, driver structure at 0x27D358
buffer size 1524 HD unit 1, V.35 DTE cable
matt#sh run int se 0
Building configuration...
Current configuration : 134 bytes
!
interface Serial0
ip address 192.168.0.254 255.255.255.252
encapsulation ppp
keepalive 10 3
clock rate 9600
no fair-queue
end
matt#sh run int se 1
Building configuration...
Current configuration : 102 bytes
!
interface Serial1
ip address 192.168.0.249 255.255.255.252
encapsulation ppp
keepalive 10 3
end[/code:1]
James:[code:1]james#sh cont se 0
HD unit 0, idb = 0x122390, driver structure at 0x129810
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
james#sh cont se 1
HD unit 1, idb = 0x12E914, driver structure at 0x135D90
buffer size 1524 HD unit 1, V.35 DTE cable
james#sh run int se 0
Building configuration...
Current configuration:
!
interface Serial0
ip address 192.168.0.250 255.255.255.252
encapsulation ppp
no fair-queue
clockrate 9600
end
james#sh run int se 1
Building configuration...
Current configuration:
!
interface Serial1
ip address 192.168.0.245 255.255.255.252
encapsulation ppp
end[/code:1]
Charlie:[code:1]charlie#sh cont se 0
HD unit 0, idb = 0x2484F8, driver structure at 0x249910
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
charlie#sh cont se 1
HD unit 1, idb = 0x261684, driver structure at 0x268B98
buffer size 1524 HD unit 1, V.35 DTE cable
charlie#sh run int se 0
Building configuration...
Current configuration : 134 bytes
!
interface Serial0
ip address 192.168.0.246 255.255.255.252
encapsulation ppp
keepalive 10 3
clock rate 9600
no fair-queue
end
charlie#sh run int se 1
Building configuration...
Current configuration : 102 bytes
!
interface Serial1
ip address 192.168.0.253 255.255.255.252
encapsulation ppp
keepalive 10 3
end[/code:1]
Matt:[code:1]matt#sh cont se 0
HD unit 0, idb = 0x2484F8, driver structure at 0x249910
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
matt#sh cont se 1
HD unit 1, idb = 0x275E40, driver structure at 0x27D358
buffer size 1524 HD unit 1, V.35 DTE cable
matt#sh run int se 0
Building configuration...
Current configuration : 134 bytes
!
interface Serial0
ip address 192.168.0.254 255.255.255.252
encapsulation ppp
keepalive 10 3
clock rate 9600
no fair-queue
end
matt#sh run int se 1
Building configuration...
Current configuration : 102 bytes
!
interface Serial1
ip address 192.168.0.249 255.255.255.252
encapsulation ppp
keepalive 10 3
end[/code:1]
James:[code:1]james#sh cont se 0
HD unit 0, idb = 0x122390, driver structure at 0x129810
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
james#sh cont se 1
HD unit 1, idb = 0x12E914, driver structure at 0x135D90
buffer size 1524 HD unit 1, V.35 DTE cable
james#sh run int se 0
Building configuration...
Current configuration:
!
interface Serial0
ip address 192.168.0.250 255.255.255.252
encapsulation ppp
no fair-queue
clockrate 9600
end
james#sh run int se 1
Building configuration...
Current configuration:
!
interface Serial1
ip address 192.168.0.245 255.255.255.252
encapsulation ppp
end[/code:1]
Charlie:[code:1]charlie#sh cont se 0
HD unit 0, idb = 0x2484F8, driver structure at 0x249910
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 9600
charlie#sh cont se 1
HD unit 1, idb = 0x261684, driver structure at 0x268B98
buffer size 1524 HD unit 1, V.35 DTE cable
charlie#sh run int se 0
Building configuration...
Current configuration : 134 bytes
!
interface Serial0
ip address 192.168.0.246 255.255.255.252
encapsulation ppp
keepalive 10 3
clock rate 9600
no fair-queue
end
charlie#sh run int se 1
Building configuration...
Current configuration : 102 bytes
!
interface Serial1
ip address 192.168.0.253 255.255.255.252
encapsulation ppp
keepalive 10 3
end[/code:1]
17 years 9 months ago #19820
by Dove
Dove
Replied by Dove on topic Re: My Cisco Lab Woes
As fas as my understanding....this kind of problem will occer if the clock signal is not passed to DTE device...in your's the router configuration seems to be ok..
Can u check the hadware i.e cables... :
Can u check the hadware i.e cables... :
Dove
- smitherton
- Offline
- Junior Member
Less
More
- Posts: 60
- Thank you received: 0
17 years 9 months ago #19840
by smitherton
Replied by smitherton on topic Re: My Cisco Lab Woes
We may be shooting the smae dead horse, but it sure sounds like a bad cable. Have you done extensive testing on the cable. i.e. finding a cable that works 100% and testing each port on all routers??
Time to create page: 0.134 seconds