On 9 Jan 2013, at 23:01, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:55, Cory Smelosky wrote:
On 9 Jan 2013, at 22:54, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Any node in area 61 I can reach. Seems any node in area 61 can reach my area, too.
Ok. I just know too little about how to check things on a Cisco. I would probably start by trying to verify where the packets are going both when pinging something in area 61, and pinging something else.
Are they using that tunnel, or are they in fact being routed some other way. DECnet is tricky in that way, since it will find other ways if you misconfigure some stuff, so packets might not be travelling as you believe.
I've got some debugging info here:
marianne#debug decnet packets
DECnet packet forwarding debugging is on
marianne#debug decnet events
DECnet packets (errors) debugging is on
marianne#debug decnet adjacencies
DECnet adjacencies debugging is on
marianne#debug decnet adjacencie
*Jan 9 23:03:31.615: DNET-ADJ: Endnode hello from 9.10
*Jan 9 23:03:31.707: DNET-ADJ: Endnode hello fr
*Jan 9 23:03:32.747: DNET-ADJ: Endnode hello from 9.23
*Jan 9 23:03:33.879: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel0, blksize 1498
*Jan 9 23:03:33.879: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel0, blksize 1498
*Jan 9 23:03:33.883: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel1, blksize 1498
*Jan 9 23:03:33.887: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel1, blksize 1498
*Jan 9 23:03:33.891: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Ethernet1/0, blksize 1498
*Jan 9 23:03:33.891: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Ethernet1/0, blksize 149
DECnet adjacencies debugging is on
marianne#
*Jan 9 23:03:33.895: DNET-ADJ: Sending version 2.0 hellos to all end nodes on int Ethernet1/0, blksize 1498
*Jan 9 23:03:34.091: DNET-ADJ: Endnode hello from 9.8
*Jan 9 23:03:36.675: DNET-ADJ: Endnode hello from 9.2
*Jan 9 23:03:37.663: DNET-ADJ: Endnode hello from 9.22
*Jan 9 23:03:37.691: DNET-ADJ: Level 2 hello from 61.1
*Jan 9 23:03:37.723: DNET-ADJ: Level 2 (IV+) hello from 61.1
*Jan 9 23:03:38.579: DNET-ADJ: Level 2 hello from 9.1
marianne#
*Jan 9 23:03:38.883: DNET-ADJ: Endnode hello from 9.11
*Jan 9 23:03:39.547: DNET-ADJ: Level 2 hello from 9.1
marianne#ping
*Jan 9 23:03:42.959: DNET-ADJ: Endnode hello from 9.141.13
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 1.13, timeout is 5 seconds:
*Jan 9 23:03:45.131: DNET-PKT: Packet fwded from 9.1023 to 1.13, via 61.1, snpa 0000.0000.0000, Tunnel0
*Jan 9 23:03:46.575: DNET-ADJ: Endnode hello from 9.10
*Jan 9 23:03:46.995: DNET-ADJ: Endnode hello from 9.12
*Jan 9 23:03:47.743: DNET-ADJ: Endnode hello from 9.23
*Jan 9 23:03:48.879: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel0, blksize 1498
*Jan 9 23:03:48.883: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel0, blksize 1498
*Jan 9 23:03:48.887: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel1, blksize 1498
*Jan 9 23:03:48.887: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel1, blksize 1498
*Jan 9 23:03:48.891: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Ethernet1/0, blksize 1498
*Jan 9 23:03:48.891: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Ethernet1/0, blksize 1498.
*Jan 9 23:03:48.891: DNET-ADJ: Sending version 2.0 hellos to all end nodes on int Ethernet1/0, blksize 1498
*Jan 9 23:03:50.131: DNET-PKT: Packet fwded from 9.1023 to 1.13, via 61.1, snpa 0000.0000.0000, Tunnel0
*Jan 9 23:03:51.863: DNET-ADJ: Endnode hello from 9.2
*Jan 9 23:03:52.663: DNET-ADJ: Endnode hello from 9.22
*Jan 9 23:03:52.719: DNET-ADJ: Level 2 hello from 61.1
*Jan 9 23:03:52.723: DNET-ADJ: Level 2 (IV+) hello from 61.1.
*Jan 9 23:03:54.079: DNET-ADJ: Endnode hello from 9.11
*Jan 9 23:03:54.543: DNET-ADJ: Level 2 hello from 9.1
*Jan 9 23:03:55.131: DNET-PKT: Packet fwded from 9.1023 to 1.13, via 61.1, snpa 0000.0000.0000, Tunnel0
*Jan 9 23:03:55.543: DNET-ADJ: Level 2 hello from 9.1
*Jan 9 23:03:57.955: DNET-ADJ: Endnode hello from 9.14
*Jan 9 23:03:58.503: DNET: Sending level 2 routing updates on interface Tunnel0
*Jan 9 23:03:58.503: DNET: Sending level 1 routing updates on interface Ethernet1/0
*Jan 9 23:03:58.507: DNET: Sending level 2 routing updates on interface Ethernet1/0.
*Jan 9 23:04:00.131: DNET-PKT: Packet fwded from 9.1023 to 1.13, via 61.1, snpa 0000.0000.0000, Tunnel0
*Jan 9 23:04:01.583: DNET-ADJ: Endnode hello from 9.10
*Jan 9 23:04:02.087: DNET-ADJ: Endnode hello from 9.12
*Jan 9 23:04:02.723: DNET-ADJ: Endnode hello from 9.23
*Jan 9 23:04:03.879: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel0, blksize 1498
*Jan 9 23:04:03.879: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel0, blksize 1498
*Jan 9 23:04:03.887: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Tunnel1, blksize 1498
*Jan 9 23:04:03.887: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Tunnel1, blksize 1498
*Jan 9 23:04:03.891: DNET-ADJ: Sending version 2.0 hellos to all PhaseIV routers on int Ethernet1/0, blksize 1498
*Jan 9 23:04:03.895: DNET-ADJ: Sending version 2.1 hellos to all PhaseIV+ routers on int Ethernet1/0, blksize 1498.
*Jan 9 23:04:03.895: DNET-ADJ: Sending version 2.0 hellos to all end nodes on int Ethernet1/0, blksize 1498
*Jan 9 23:04:04.103: DNET-ADJ: Endnode hello from 9.8
*Jan 9 23:04:05.131: DNET-PKT: Packet fwded from 9.1023 to 1.13, via 61.1, snpa 0000.0000.0000, Tunnel0
*Jan 9 23:04:07.043: DNET-ADJ: Endnode hello from 9.2
*Jan 9 23:04:07.699: DNET-ADJ: Endnode hello from 9.22
*Jan 9 23:04:07.703: DNET-ADJ: Level 2 hello from 61.1
*Jan 9 23:04:07.723: DNET-ADJ: Level 2 (IV+) hello from 61.1.
Success rate is 0 percent (0/5)
That might help can you do the same Dave?
A traceroute would have been very useful in DECnet, but the only thing like that I've seen is something Peter have on TOPS-10...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:55, Cory Smelosky wrote:
On 9 Jan 2013, at 22:54, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Any node in area 61 I can reach. Seems any node in area 61 can reach my area, too.
Ok. I just know too little about how to check things on a Cisco. I would probably start by trying to verify where the packets are going both when pinging something in area 61, and pinging something else.
Are they using that tunnel, or are they in fact being routed some other way. DECnet is tricky in that way, since it will find other ways if you misconfigure some stuff, so packets might not be travelling as you believe.
A traceroute would have been very useful in DECnet, but the only thing like that I've seen is something Peter have on TOPS-10...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 9 Jan 2013, at 22:54, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Any node in area 61 I can reach. Seems any node in area 61 can reach my area, too.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:51, Cory Smelosky wrote:
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
61.1, or any node in area 61? Have you tried 61.3 for example?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-10 04:44, Dave McGuire wrote:
On 01/09/2013 10:40 PM, Johnny Billquist wrote:
In that case, the next question is obviously how the DECnet routing
table at 61.1 looks like.
Area Cost Hops Next Hop to Node Expires Prio
*1 11 2 Tunnel5 -> 59.11
*2 11 2 Tunnel5 -> 59.11
*3 14 3 Tunnel5 -> 59.11
*4 11 2 Tunnel5 -> 59.11
*5 11 2 Tunnel5 -> 59.11
*6 11 2 Tunnel5 -> 59.11
*7 12 3 Tunnel5 -> 59.11
*8 11 2 Tunnel5 -> 59.11
*9 10 1 Tunnel6 -> 9.1023 38 64 A+
*11 11 2 Tunnel5 -> 59.11
*12 11 2 Tunnel5 -> 59.11
*18 12 3 Tunnel5 -> 59.11
*19 11 2 Tunnel5 -> 59.11
*20 12 3 Tunnel5 -> 59.11
*28 11 2 Tunnel5 -> 59.11
*33 12 3 Tunnel5 -> 59.11
*42 10 1 Tunnel4 -> 42.1023 35 64 A+
*44 11 2 Tunnel5 -> 59.11
*47 13 3 Tunnel5 -> 59.11
*51 13 3 Tunnel5 -> 59.11
*52 10 1 Tunnel1 -> 52.1 37 64 A+
*59 10 1 Tunnel5 -> 59.11 41 64 A+
Can you get any kind of statistics show how many packets are being routed, and possibly over which tunnels? Or atleast how many packets are sent/received on each tunnel?
Actually, why don't you have an entry for area 61 in your routing table?
That's a damn good question.
I also notice that you don't seem to have an area 61 yourself here, Dave. That might explain why Cory don't get one. But the setup looks weird because of this.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 9 Jan 2013, at 22:48, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Correct. Only I have issues.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Amusingly enough, packets to 61.x get there fine.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:42, Cory Smelosky wrote:
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Might be a red herring, though. I would perhaps assume that 61.1 is routing things for other networks just fine, and only you have issues?
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
I don't know enough about Cisco to say, but it seems *very* weird to me that you don't have area 61 in there. How would you expect packets to 61.x find their way anywhere?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 9 Jan 2013, at 22:40, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
I'm curious as to what the table on 61.1 is as well.
Actually, why don't you have an entry for area 61 in your routing table?
I have absolutely no clue does it need to be added manually?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 2013-01-10 04:37, Cory Smelosky wrote:
On 9 Jan 2013, at 22:35, Johnny Billquist <bqt at softjar.se> wrote:
His end has other functioning links, and his tunnel to me is the inverse.
Any ideas?
I hope 61.1 is an area router
It is. Which is what makes this so confusing
In that case, the next question is obviously how the DECnet routing table at 61.1 looks like.
Actually, why don't you have an entry for area 61 in your routing table?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
