On 1/10/2013 3:49 PM, Cory Smelosky wrote:
On 10 Jan 2013, at 15:48, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router. ;)
I got a different error though when that happened.
-brian
On 10 Jan 2013, at 15:48, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
Yeah. Turns out the multi net tunnel didn't go down and that was still behaving as my router. ;)
On 1/10/2013 3:46 PM, Cory Smelosky wrote:
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
Now pings just drop on the floor:
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds :
.....
Success rate is 0 percent (0/5)
On 10 Jan 2013, at 10:00, Cory Smelosky <b4 at gewt.net> wrote:
On 10 Jan 2013, at 09:47, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
There used to be, but I removed the multinet tunnel connection and removed it from the VPN.
What I'm getting at is do you have a split area with no link between the "halves"?
There shouldn't be anymore. Unless SG1 is still trying to link me despite that link being down.
The link was still up I just now remembered that deleting a tunnel does not bring it down in multi net.
-brian
On 10 Jan 2013, at 09:47, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
There used to be, but I removed the multinet tunnel connection and removed it from the VPN.
What I'm getting at is do you have a split area with no link between the "halves"?
There shouldn't be anymore. Unless SG1 is still trying to link me despite that link being down.
-brian
On 1/10/2013 9:43 AM, Cory Smelosky wrote:
What does show decnet route show as the router for area 9?
bart#show decnet route | inc ^\*9
*9 13 4 Tunnel2 -> 59.60
Dave isn't my preferred path to you.
I have a question for you. This node on 9 that's connected to the cisco, is there another path to it?
What I'm getting at is do you have a split area with no link between the "halves"?
-brian
On 10 Jan 2013, at 09:38, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/9/2013 10:29 PM, Cory Smelosky wrote:
However! Despite this tunnel being identical to the other tunnels, I am unable to reach the rest of HECnet via the tunnel to him.
Just to throw my own data out there for you, from 52.1:
bart#ping 61.1
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 61.1, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/25/28 ms
bart#ping 1.13
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 1.13, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 144/220/260 ms
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds:
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Success rate is 0 percent (0/5)
bart#
What does show decnet route show as the router for area 9?
On 1/9/2013 10:29 PM, Cory Smelosky wrote:
However! Despite this tunnel being identical to the other tunnels, I am unable to reach the rest of HECnet via the tunnel to him.
Just to throw my own data out there for you, from 52.1:
bart#ping 61.1
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 61.1, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/25/28 ms
bart#ping 1.13
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 1.13, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 144/220/260 ms
bart#ping 9.1023
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 9.1023, timeout is 5 seconds:
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Success rate is 0 percent (0/5)
bart#
Hi Peter,
thanks for your offer, but currently I'm using the GSR as a pedestal for my AlphaServer DS20, so there
is no need for the PSU.
I'll check out the AGS+ next time I'll visit my "lab".
I think there are also some Cisco 1003's lying around, what would be the right ios version to run for decnet?
--Saku
On Wed, Jan 9, 2013 at 10:44 PM, Peter Lothberg <roll at stupi.se> wrote:
> It's 12008.
I can find you a AC PS.
> I'm not seriously considering running it just for my vaxen :)
Humm, negative waves.. But seriously there is no IOS that speaks
DECnet on the GSR. (In theory E0 cards can do it, but OC3 pos and OC12
POS are the only interfaces..)
> I do have one AGS+, I wonder if it has decnet..
It has DECnet. But maybe only switched by the RP (csc) say 1.5Mbit/s.
> I'm in Espoo, Finland. We did meet once in the Funet/Nordunet conference at
> the Technical University in Otaniemi, Espoo.
That's to many years ago for me to remember -:)
-P
On 9 Jan 2013, at 23:10, Dave McGuire <mcguire at neurotica.com> wrote:
On 01/09/2013 11:05 PM, Cory Smelosky wrote:
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?
I can in a little while, but I'll have to find a way to do some filtering on that output.
DEBUG DECNET ?
Will list all the options. I turned on unneeded ones so I could get more info than I needed.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
