- Posts: 8
- Thank you received: 0
My Cisco Lab Woes
17 years 9 months ago #19747
by surfer
That's what i thought, and show ip route only knows about the subnets that they are directly connected to. Plus there are no other subnets in the network so far. Anyway...
Charlie:
[code:1]charlie#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Ethernet0 unassigned YES NVRAM administratively down down
Serial0 192.168.0.246 YES NVRAM up down
Serial1 192.168.0.253 YES NVRAM up up
charlie#ping 192.168.0.254
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/40 ms
charlie#ping 192.168.0.245
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.245, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)[/code:1]
This router seems to have the most idea what is going on. The link that is Up&Up actually pings, and the one that isn't doesn't. Not for any reason i can see, but that's better than the other 2...
Matt:
[code:1]matt#sh ip int brief
Interface IP-Address OK? Method Status Protocol
BRI0 unassigned YES NVRAM administratively down down
BRI0:1 unassigned YES unset administratively down down
BRI0:2 unassigned YES unset administratively down down
Ethernet0 unassigned YES NVRAM administratively down down
Serial0 192.168.0.254 YES NVRAM up up
Serial1 192.168.0.249 YES NVRAM up up
matt#
*Mar 1 00:03:24.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:03:34.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
*Mar 1 00:03:54.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:04:04.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
*Mar 1 00:04:24.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:04:34.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
matt#ping 192.168.0.253
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.253, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/36 ms
matt#ping 192.168.0.250
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.250, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)[/code:1]
Note the error messages every 30 seconds. These generally go on forever. Obviously doing a sh ip int brief after it changes to up&down reports the link as so, but the ping command NEVER works, no matter what the interface status thinks.
James:
[code:1]james#sh ip int brief
Interface IP-Address OK? Method Status Protocol
BRI0 unassigned YES NVRAM administratively down down
BRI0:1 unassigned YES unset administratively down down
BRI0:2 unassigned YES unset administratively down down
Serial0 192.168.0.250 YES NVRAM up up
Serial1 192.168.0.245 YES NVRAM up up
TokenRing0 unassigned YES NVRAM administratively down down
james#
00:20:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:20:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:20:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:20:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:20:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:20:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:20:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:20:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
james#ping 192.168.0.249
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.249, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
james#ping 192.168.0.246
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.246, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
[/code:1]
This router doesn't have a clue what's going on.
It would probably be quite easy to deduce that 'james' is broken, but have a look at the table in my first post. The link between Matt and James works if Matt is providing the clocking (and if i swap the cable ends around obviously).
Similarly the link between Matt and Charlie will stop working if charlie is configured to provide the clocking and the DCE / DTE ends swapped around.
Also, sh int se 0 and sh int se 1 report that HDLC is set on all interfaces, so i don't know where this layer 2 problem is.
Replied by surfer on topic Re: My Cisco Lab Woes
Can you post the output of some example pings from router to router.
Since you have a ring here, You only need a routing protocol if you are pinging an interface that is on the third link that is not connected directly to the pinger router.
Otherwise, if you are pinging an interface on a directly connected link, it should work.
Can you also post the "show ip interface brief" output.
That's what i thought, and show ip route only knows about the subnets that they are directly connected to. Plus there are no other subnets in the network so far. Anyway...
Charlie:
[code:1]charlie#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Ethernet0 unassigned YES NVRAM administratively down down
Serial0 192.168.0.246 YES NVRAM up down
Serial1 192.168.0.253 YES NVRAM up up
charlie#ping 192.168.0.254
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.254, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/40 ms
charlie#ping 192.168.0.245
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.245, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)[/code:1]
This router seems to have the most idea what is going on. The link that is Up&Up actually pings, and the one that isn't doesn't. Not for any reason i can see, but that's better than the other 2...
Matt:
[code:1]matt#sh ip int brief
Interface IP-Address OK? Method Status Protocol
BRI0 unassigned YES NVRAM administratively down down
BRI0:1 unassigned YES unset administratively down down
BRI0:2 unassigned YES unset administratively down down
Ethernet0 unassigned YES NVRAM administratively down down
Serial0 192.168.0.254 YES NVRAM up up
Serial1 192.168.0.249 YES NVRAM up up
matt#
*Mar 1 00:03:24.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:03:34.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
*Mar 1 00:03:54.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:04:04.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
*Mar 1 00:04:24.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 1 00:04:34.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
matt#ping 192.168.0.253
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.253, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/36 ms
matt#ping 192.168.0.250
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.250, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)[/code:1]
Note the error messages every 30 seconds. These generally go on forever. Obviously doing a sh ip int brief after it changes to up&down reports the link as so, but the ping command NEVER works, no matter what the interface status thinks.
James:
[code:1]james#sh ip int brief
Interface IP-Address OK? Method Status Protocol
BRI0 unassigned YES NVRAM administratively down down
BRI0:1 unassigned YES unset administratively down down
BRI0:2 unassigned YES unset administratively down down
Serial0 192.168.0.250 YES NVRAM up up
Serial1 192.168.0.245 YES NVRAM up up
TokenRing0 unassigned YES NVRAM administratively down down
james#
00:20:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:20:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:20:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:20:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:20:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:20:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:20:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:20:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
james#ping 192.168.0.249
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.249, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
james#ping 192.168.0.246
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.246, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
[/code:1]
This router doesn't have a clue what's going on.
It would probably be quite easy to deduce that 'james' is broken, but have a look at the table in my first post. The link between Matt and James works if Matt is providing the clocking (and if i swap the cable ends around obviously).
Similarly the link between Matt and Charlie will stop working if charlie is configured to provide the clocking and the DCE / DTE ends swapped around.
Also, sh int se 0 and sh int se 1 report that HDLC is set on all interfaces, so i don't know where this layer 2 problem is.
17 years 9 months ago #19750
by Dove
Dove
Replied by Dove on topic Re: My Cisco Lab Woes
Have u changed the routing protocol version to RIP 2?
Checke the interface type which is acting as DCE and DTE. In you scenario..
DCE interfaces
============
Charlie - S0
Matt - S0
James - S0
try after changing the clock rate to 64000 on all three router.
if its ok, please post the Debug RIP & sh ip route
Checke the interface type which is acting as DCE and DTE. In you scenario..
DCE interfaces
============
Charlie - S0
Matt - S0
James - S0
try after changing the clock rate to 64000 on all three router.
if its ok, please post the Debug RIP & sh ip route
Dove
17 years 9 months ago #19765
by S0lo
Yes, that it is not a routing problem since the interfaces are clearly flaping up and down.
Ok, I'd suggest narrowing down the problem. here is what I'd do: disconnect your network totally. find one of those serial cables (that you are sure is working fine). Connect just Charlie and Matt together via Se0 to Se0 while charlie is clocking. If all works fine try Se0 to Se0 while Matt is clocking. If all works fine try the same scenario on Se1 to Se1 on the same two router.
If all works fine then you know that the two routers are A OK. However if one of the sitiuations fail you know thats it's either of the serials that has the problem, Try then Se1 to Se0 and vise versa.
Sure you can do the same thing with the 3rd router.
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
Replied by S0lo on topic Re: My Cisco Lab Woes
so i don't know where this layer 2 problem is.
Yes, that it is not a routing problem since the interfaces are clearly flaping up and down.
Ok, I'd suggest narrowing down the problem. here is what I'd do: disconnect your network totally. find one of those serial cables (that you are sure is working fine). Connect just Charlie and Matt together via Se0 to Se0 while charlie is clocking. If all works fine try Se0 to Se0 while Matt is clocking. If all works fine try the same scenario on Se1 to Se1 on the same two router.
If all works fine then you know that the two routers are A OK. However if one of the sitiuations fail you know thats it's either of the serials that has the problem, Try then Se1 to Se0 and vise versa.
Sure you can do the same thing with the 3rd router.
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
17 years 9 months ago #19778
by surfer
That's what i did. The results were very stange...
[code:1]Clocking Receiving Works?
James Se 0 Matt Se 0 NO
James Se 0 Matt Se 1 NO
James Se 1 Matt Se 0 NO
James Se 1 Matt Se 1 NO
Matt Se 0 James Se 0 YES
Matt Se 0 James Se 1 NO
Matt Se 1 James Se 0 YES
Matt Se 1 James Se 1 NO
Matt Se 0 Charlie Se 0 NO
Matt Se 0 Charlie Se 1 YES
Matt Se 1 Charlie Se 0 NO
Matt Se 1 Charlie Se 1 YES
Charlie Se 0 Matt Se 0 NO
Charlie Se 0 Matt Se 1 NO
Charlie Se 1 Matt Se 0 NO
Charlie Se 1 Matt Se 1 NO
Charlie Se 0 James Se 0 NO
Charlie Se 0 James Se 1 NO
Charlie Se 1 James Se 0 NO
Charlie Se 1 James Se 1 NO
James Se 0 Charlie Se 0 NO
James Se 0 Charlie Se 1 NO
James Se 1 Charlie Se 0 NO
James Se 1 Charlie Se 1 NO[/code:1]
I've now run a 'debug all' on james and it's given alot of HDLC stuff which is the L2 protocol. Here's the output i got for about a minute. Sorry for the length, it was difficult to decide what was important and not:
[code:1]
All possible debugging has been turned on
james#
00:36:02: Serial0: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:03: Serial1: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:04: HD(0): got an interrupt state = 0x8057
00:36:04: HD(0): New serial state = 0x0055
00:36:04: HD(0): DTR is down.
00:36:04: HD(1): New serial state = 0x015F
00:36:04: HD(1): DCD is up.
00:36:04: HD(0): got an interrupt state = 0x805F
00:36:04: HD(0): New serial state = 0x005F
00:36:04: HD(0): DTR is up.
00:36:04: HD(1): New serial state = 0x015F
00:36:04: HD(1): DCD is up.
00:36:07: is_up: 1 state: 4 sub state: 1 line: 0
00:36:12: HD(0): Deasserting DSR, CTS and DCD
00:36:12: HD(0): Reset from 0x3048F0E
00:36:12: HD(0): Asserting DSR
00:36:12: HD(0): Asserting DCD and CTS
00:36:12: HD(0): Deasserting LTST
00:36:12: HD(0): Asserting DTR and RTS
00:36:12: Serial0: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:13: HD(1): Deasserting DTR and RTS
00:36:13: HD(1): Reset from 0x3048F0E
00:36:13: HD(1): Asserting DTR
00:36:13: HD(1): Deasserting LTST
00:36:13: HD(1): Asserting DTR and RTS
00:36:13: Serial1: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:15: is_up: 1 state: 4 sub state: 1 line: 0
00:36:16: is_up: 1 state: 4 sub state: 1 line: 0
00:36:22: RIP-TIMER: periodic timer expired
00:36:22: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.0.250)
00:36:22: RIP: build update entries
00:36:22: 192.168.0.244/30 via 0.0.0.0, metric 1, tag 0
00:36:22: RIP: Update contains 1 routes
00:36:22: RIP: Update queued
00:36:22: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.0.245)
00:36:22: RIP: build update entries
00:36:22: 192.168.0.248/30 via 0.0.0.0, metric 1, tag 0
00:36:22: RIP: Update contains 1 routes
00:36:22: RIP: Update queued
00:36:22: RIP: Update sent via Serial0
00:36:22: IP: s=192.168.0.250 (local), d=224.0.0.9 (Serial0), len 52, sending broad/multicast
00:36:22: RIP: Update sent via Serial1
00:36:22: IP: s=192.168.0.245 (local), d=224.0.0.9 (Serial1), len 52, sending broad/multicast
00:36:22: HD(0): Deasserting DSR, CTS and DCD
00:36:22: HD(0): Reset from 0x3048F0E
00:36:22: HD(0): Asserting DSR
00:36:22: HD(0): Asserting DCD and CTS
00:36:22: HD(0): Deasserting LTST
00:36:22: HD(0): Asserting DTR and RTS
00:36:22: Serial0: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:23: HD(1): Deasserting DTR and RTS
00:36:23: HD(1): Reset from 0x3048F0E
00:36:23: HD(1): Asserting DTR
00:36:23: HD(1): Deasserting LTST
00:36:23: HD(1): Asserting DTR and RTS
00:36:23: Serial1: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:36:24: HD(0): New serial state = 0x005F
00:36:24: HD(0): DTR is up.
00:36:24: HD(1): got an interrupt state = 0x815F
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:36:24: HD(0): got an interrupt state = 0x8057
00:36:24: HD(0): New serial state = 0x0055
00:36:24: HD(0): DTR is down.
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: HD(0): got an interrupt state = 0x805F
00:36:24: HD(0): New serial state = 0x005F
00:36:24: HD(0): DTR is up.
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: is_up: 1 state: 4 sub state: 1 line: 0
00:36:24: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:36:26: is_up: 1 state: 4 sub state: 1 line: 0
00:36:32: Serial0: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:33: Serial1: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:34: HD(0): got an interrupt state = 0x8055
00:36:34: HD(0): New serial state = 0x0055
00:36:34: HD(0): DTR is down.
00:36:34: HD(1): New serial state = 0x015F
00:36:34: HD(1): DCD is up.
00:36:34: HD(0): got an interrupt state = 0x805F
00:36:34: HD(0): New serial state = 0x005F
00:36:34: HD(0): DTR is up.
00:36:34: HD(1): New serial state = 0x015F
00:36:34: HD(1): DCD is up.
00:36:37: DHCPD: checking for expired leases.
00:36:37: is_up: 1 state: 4 sub state: 1 line: 0
00:36:37: CDP-PA: version 2 packet sent out on Serial0
00:36:37: CDP-PA: version 2 packet sent out on Serial1
00:36:42: HD(0): Deasserting DSR, CTS and DCD
00:36:42: HD(0): Reset from 0x3048F0E
00:36:42: HD(0): Asserting DSR
00:36:42: HD(0): Asserting DCD and CTS
00:36:42: HD(0): Deasserting LTST
00:36:42: HD(0): Asserting DTR and RTS
00:36:42: Serial0: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:43: HD(1): Deasserting DTR and RTS
00:36:43: HD(1): Reset from 0x3048F0E
00:36:43: HD(1): Asserting DTR
00:36:43: HD(1): Deasserting LTST
00:36:43: HD(1): Asserting DTR and RTS
00:36:43: Serial1: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:45: is_up: 1 state: 4 sub state: 1 line: 0
00:36:46: is_up: 1 state: 4 sub state: 1 line: 0
00:36:50: RIP-TIMER: periodic timer expired
00:36:50: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.0.250)
00:36:50: RIP: build update entries
00:36:50: 192.168.0.244/30 via 0.0.0.0, metric 1, tag 0
00:36:50: RIP: Update contains 1 routes
00:36:50: RIP: Update queued
00:36:50: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.0.245)
00:36:50: RIP: build update entries
00:36:50: 192.168.0.248/30 via 0.0.0.0, metric 1, tag 0
00:36:50: RIP: Update contains 1 routes
00:36:50: RIP: Update queued
00:36:50: RIP: Update sent via Serial0
00:36:50: IP: s=192.168.0.250 (local), d=224.0.0.9 (Serial0), len 52, sending broad/multicast
00:36:50: RIP: Update sent via Serial1
00:36:50: IP: s=192.168.0.245 (local), d=224.0.0.9 (Serial1), len 52, sending broad/multicast
00:36:52: HD(0): Deasserting DSR, CTS and DCD
00:36:52: HD(0): Reset from 0x3048F0E
00:36:52: HD(0): Asserting DSR
00:36:52: HD(0): Asserting DCD and CTS
00:36:52: HD(0): Deasserting LTST
00:36:52: HD(0): Asserting DTR and RTS
00:36:52: Serial0: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:53: HD(1): Deasserting DTR and RTS
00:36:53: HD(1): Reset from 0x3048F0E
00:36:53: HD(1): Asserting DTR
00:36:53: HD(1): Deasserting LTST
00:36:53: HD(1): Asserting DTR and RTS
00:36:53: Serial1: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:36:54: HD(0): New serial state = 0x005F
00:36:54: HD(0): DTR is up.
00:36:54: HD(1): got an interrupt state = 0x815F
00:36:54: HD(1): New serial state = 0x015F
00:36:54: HD(1): DCD is up.
00:36:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:36:54: is_up: 1 state: 4 sub state: 1 line: 0
00:36:54: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:36:56: is_up: 1 state: 4 sub state: 1 line: 0[/code:1]
Cheers!
Replied by surfer on topic Re: My Cisco Lab Woes
so i don't know where this layer 2 problem is.
Yes, that it is not a routing problem since the interfaces are clearly flaping up and down.
Ok, I'd suggest narrowing down the problem. here is what I'd do: disconnect your network totally. find one of those serial cables (that you are sure is working fine). Connect just Charlie and Matt together via Se0 to Se0 while charlie is clocking. If all works fine try Se0 to Se0 while Matt is clocking. If all works fine try the same scenario on Se1 to Se1 on the same two router.
If all works fine then you know that the two routers are A OK. However if one of the sitiuations fail you know thats it's either of the serials that has the problem, Try then Se1 to Se0 and vise versa.
Sure you can do the same thing with the 3rd router.
That's what i did. The results were very stange...
[code:1]Clocking Receiving Works?
James Se 0 Matt Se 0 NO
James Se 0 Matt Se 1 NO
James Se 1 Matt Se 0 NO
James Se 1 Matt Se 1 NO
Matt Se 0 James Se 0 YES
Matt Se 0 James Se 1 NO
Matt Se 1 James Se 0 YES
Matt Se 1 James Se 1 NO
Matt Se 0 Charlie Se 0 NO
Matt Se 0 Charlie Se 1 YES
Matt Se 1 Charlie Se 0 NO
Matt Se 1 Charlie Se 1 YES
Charlie Se 0 Matt Se 0 NO
Charlie Se 0 Matt Se 1 NO
Charlie Se 1 Matt Se 0 NO
Charlie Se 1 Matt Se 1 NO
Charlie Se 0 James Se 0 NO
Charlie Se 0 James Se 1 NO
Charlie Se 1 James Se 0 NO
Charlie Se 1 James Se 1 NO
James Se 0 Charlie Se 0 NO
James Se 0 Charlie Se 1 NO
James Se 1 Charlie Se 0 NO
James Se 1 Charlie Se 1 NO[/code:1]
I've now run a 'debug all' on james and it's given alot of HDLC stuff which is the L2 protocol. Here's the output i got for about a minute. Sorry for the length, it was difficult to decide what was important and not:
[code:1]
All possible debugging has been turned on
james#
00:36:02: Serial0: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:03: Serial1: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:04: HD(0): got an interrupt state = 0x8057
00:36:04: HD(0): New serial state = 0x0055
00:36:04: HD(0): DTR is down.
00:36:04: HD(1): New serial state = 0x015F
00:36:04: HD(1): DCD is up.
00:36:04: HD(0): got an interrupt state = 0x805F
00:36:04: HD(0): New serial state = 0x005F
00:36:04: HD(0): DTR is up.
00:36:04: HD(1): New serial state = 0x015F
00:36:04: HD(1): DCD is up.
00:36:07: is_up: 1 state: 4 sub state: 1 line: 0
00:36:12: HD(0): Deasserting DSR, CTS and DCD
00:36:12: HD(0): Reset from 0x3048F0E
00:36:12: HD(0): Asserting DSR
00:36:12: HD(0): Asserting DCD and CTS
00:36:12: HD(0): Deasserting LTST
00:36:12: HD(0): Asserting DTR and RTS
00:36:12: Serial0: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:13: HD(1): Deasserting DTR and RTS
00:36:13: HD(1): Reset from 0x3048F0E
00:36:13: HD(1): Asserting DTR
00:36:13: HD(1): Deasserting LTST
00:36:13: HD(1): Asserting DTR and RTS
00:36:13: Serial1: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:15: is_up: 1 state: 4 sub state: 1 line: 0
00:36:16: is_up: 1 state: 4 sub state: 1 line: 0
00:36:22: RIP-TIMER: periodic timer expired
00:36:22: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.0.250)
00:36:22: RIP: build update entries
00:36:22: 192.168.0.244/30 via 0.0.0.0, metric 1, tag 0
00:36:22: RIP: Update contains 1 routes
00:36:22: RIP: Update queued
00:36:22: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.0.245)
00:36:22: RIP: build update entries
00:36:22: 192.168.0.248/30 via 0.0.0.0, metric 1, tag 0
00:36:22: RIP: Update contains 1 routes
00:36:22: RIP: Update queued
00:36:22: RIP: Update sent via Serial0
00:36:22: IP: s=192.168.0.250 (local), d=224.0.0.9 (Serial0), len 52, sending broad/multicast
00:36:22: RIP: Update sent via Serial1
00:36:22: IP: s=192.168.0.245 (local), d=224.0.0.9 (Serial1), len 52, sending broad/multicast
00:36:22: HD(0): Deasserting DSR, CTS and DCD
00:36:22: HD(0): Reset from 0x3048F0E
00:36:22: HD(0): Asserting DSR
00:36:22: HD(0): Asserting DCD and CTS
00:36:22: HD(0): Deasserting LTST
00:36:22: HD(0): Asserting DTR and RTS
00:36:22: Serial0: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:23: HD(1): Deasserting DTR and RTS
00:36:23: HD(1): Reset from 0x3048F0E
00:36:23: HD(1): Asserting DTR
00:36:23: HD(1): Deasserting LTST
00:36:23: HD(1): Asserting DTR and RTS
00:36:23: Serial1: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:36:24: HD(0): New serial state = 0x005F
00:36:24: HD(0): DTR is up.
00:36:24: HD(1): got an interrupt state = 0x815F
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:36:24: HD(0): got an interrupt state = 0x8057
00:36:24: HD(0): New serial state = 0x0055
00:36:24: HD(0): DTR is down.
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: HD(0): got an interrupt state = 0x805F
00:36:24: HD(0): New serial state = 0x005F
00:36:24: HD(0): DTR is up.
00:36:24: HD(1): New serial state = 0x015F
00:36:24: HD(1): DCD is up.
00:36:24: is_up: 1 state: 4 sub state: 1 line: 0
00:36:24: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:36:25: is_up: 1 state: 4 sub state: 1 line: 0
00:36:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:36:26: is_up: 1 state: 4 sub state: 1 line: 0
00:36:32: Serial0: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:33: Serial1: HDLC myseq 0, mineseen 0, yourseen 0, line up
00:36:34: HD(0): got an interrupt state = 0x8055
00:36:34: HD(0): New serial state = 0x0055
00:36:34: HD(0): DTR is down.
00:36:34: HD(1): New serial state = 0x015F
00:36:34: HD(1): DCD is up.
00:36:34: HD(0): got an interrupt state = 0x805F
00:36:34: HD(0): New serial state = 0x005F
00:36:34: HD(0): DTR is up.
00:36:34: HD(1): New serial state = 0x015F
00:36:34: HD(1): DCD is up.
00:36:37: DHCPD: checking for expired leases.
00:36:37: is_up: 1 state: 4 sub state: 1 line: 0
00:36:37: CDP-PA: version 2 packet sent out on Serial0
00:36:37: CDP-PA: version 2 packet sent out on Serial1
00:36:42: HD(0): Deasserting DSR, CTS and DCD
00:36:42: HD(0): Reset from 0x3048F0E
00:36:42: HD(0): Asserting DSR
00:36:42: HD(0): Asserting DCD and CTS
00:36:42: HD(0): Deasserting LTST
00:36:42: HD(0): Asserting DTR and RTS
00:36:42: Serial0: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:43: HD(1): Deasserting DTR and RTS
00:36:43: HD(1): Reset from 0x3048F0E
00:36:43: HD(1): Asserting DTR
00:36:43: HD(1): Deasserting LTST
00:36:43: HD(1): Asserting DTR and RTS
00:36:43: Serial1: HDLC myseq 1, mineseen 0, yourseen 0, line up
00:36:45: is_up: 1 state: 4 sub state: 1 line: 0
00:36:46: is_up: 1 state: 4 sub state: 1 line: 0
00:36:50: RIP-TIMER: periodic timer expired
00:36:50: RIP: sending v2 update to 224.0.0.9 via Serial0 (192.168.0.250)
00:36:50: RIP: build update entries
00:36:50: 192.168.0.244/30 via 0.0.0.0, metric 1, tag 0
00:36:50: RIP: Update contains 1 routes
00:36:50: RIP: Update queued
00:36:50: RIP: sending v2 update to 224.0.0.9 via Serial1 (192.168.0.245)
00:36:50: RIP: build update entries
00:36:50: 192.168.0.248/30 via 0.0.0.0, metric 1, tag 0
00:36:50: RIP: Update contains 1 routes
00:36:50: RIP: Update queued
00:36:50: RIP: Update sent via Serial0
00:36:50: IP: s=192.168.0.250 (local), d=224.0.0.9 (Serial0), len 52, sending broad/multicast
00:36:50: RIP: Update sent via Serial1
00:36:50: IP: s=192.168.0.245 (local), d=224.0.0.9 (Serial1), len 52, sending broad/multicast
00:36:52: HD(0): Deasserting DSR, CTS and DCD
00:36:52: HD(0): Reset from 0x3048F0E
00:36:52: HD(0): Asserting DSR
00:36:52: HD(0): Asserting DCD and CTS
00:36:52: HD(0): Deasserting LTST
00:36:52: HD(0): Asserting DTR and RTS
00:36:52: Serial0: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:53: HD(1): Deasserting DTR and RTS
00:36:53: HD(1): Reset from 0x3048F0E
00:36:53: HD(1): Asserting DTR
00:36:53: HD(1): Deasserting LTST
00:36:53: HD(1): Asserting DTR and RTS
00:36:53: Serial1: HDLC myseq 2, mineseen 0, yourseen 0, line down
00:36:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
00:36:54: HD(0): New serial state = 0x005F
00:36:54: HD(0): DTR is up.
00:36:54: HD(1): got an interrupt state = 0x815F
00:36:54: HD(1): New serial state = 0x015F
00:36:54: HD(1): DCD is up.
00:36:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
00:36:54: is_up: 1 state: 4 sub state: 1 line: 0
00:36:54: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
00:36:55: is_up: 1 state: 4 sub state: 1 line: 0
00:36:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
00:36:56: is_up: 1 state: 4 sub state: 1 line: 0[/code:1]
Cheers!
17 years 9 months ago #19796
by S0lo
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
Replied by S0lo on topic Re: My Cisco Lab Woes
hmmm.. that is puzzeling 
Have you tried checking the "keepalive" value on the interfaces. As far as I know, different keepalives can't work. they have to be the same.
Did you erase NVRAM when you first configured the routers?
Just, as a last hope, try setting those clock rates to the minimum 9600.
Have you tried checking the "keepalive" value on the interfaces. As far as I know, different keepalives can't work. they have to be the same.
Did you erase NVRAM when you first configured the routers?
Just, as a last hope, try setting those clock rates to the minimum 9600.
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
17 years 9 months ago #19811
by surfer
Done all of that and still no joy. Think i'll try configuring an alternative to HDLC and see how that works.
Replied by surfer on topic Re: My Cisco Lab Woes
hmmm.. that is puzzeling
Have you tried checking the "keepalive" value on the interfaces. As far as I know, different keepalives can't work. they have to be the same.
Did you erase NVRAM when you first configured the routers?
Just, as a last hope, try setting those clock rates to the minimum 9600.
Done all of that and still no joy. Think i'll try configuring an alternative to HDLC and see how that works.
Time to create page: 0.137 seconds