On Sat, Jan 3, 2015 at 1:34 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
I am running DEChub 90's. Does the brouter work there or require the '900 platform? Actually I have extra power supplies come to think of it. Does the brouter require any special cabling? Thanks!
DEChub90s are perfect. It is not a DEChub900 module.
There is no special cabling. It has serial interfaces, but they won't be used. They have either a 10Base2 coaxial connection on top, or a 10baseT port on the front. Obviously, if they are in a DEChub, then they connect into the backplane like all the other modules.
Did you see my reply over DECnet?
Regards, Tim.
On 2015-01-02 18:28, Hans Vlems wrote:
Is there an advantage if you use a tunnel in stead of Johnny's bridge
program which I use?
It scales better and use less network bandwidth, if that is a concern.
But it won't pass through LAT or MOP. Pick your poison. :-)
Johnny
Hans
Verzonden vanaf mijn BlackBerry 10-smartphone.
*Van: *Tim Sneddon
*Verzonden: *vrijdag 2 januari 2015 18:24
*Aan: *hecnet at update.uu.se
*Beantwoorden: *hecnet at Update.UU.SE
*Onderwerp: *Re: [HECnet] Hecnet Peering
On Sat, Jan 3, 2015 at 1:17 AM, Steve Davidson <steve at davidson.net
<mailto:steve at davidson.net>> wrote:
Tim,
The short form... DEChubs are us. I have both the backplanes and
the MultiStacks. They currently have hubs, LAT servers, and
dedicated LAT printer modules. I even have the Packet Probe module
with software...
That should work nicely.
Regards, Tim.
--
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
Tim,
I am running DEChub 90's. Does the brouter work there or require the '900 platform? Actually I have extra power supplies come to think of it. Does the brouter require any special cabling? Thanks!
-Steve
On Jan 2, 2015, at 12:28, Hans Vlems <hvlems at zonnet.nl> wrote:
Is there an advantage if you use a tunnel in stead of Johnny's bridge program which I use?
Hans
Verzonden vanaf mijn BlackBerry 10-smartphone.
Van: Tim Sneddon
Verzonden: vrijdag 2 januari 2015 18:24
Aan: hecnet at update.uu.se
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Hecnet Peering
On Sat, Jan 3, 2015 at 1:17 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
The short form... DEChubs are us. I have both the backplanes and the MultiStacks. They currently have hubs, LAT servers, and dedicated LAT printer modules. I even have the Packet Probe module with software...
That should work nicely.
Regards, Tim.
On Sat, Jan 3, 2015 at 1:28 AM, Hans Vlems <hvlems at zonnet.nl> wrote:
Is there an advantage if you use a tunnel in stead of Johnny's bridge program which I use?
Hi Hans,
Not really. I think it was Brian Hechinger that started it. I joined in almost straight away as I had an old DECbrouter 90T2a and a long history of working with them.
Regards, Tim.
Is there an advantage if you use a tunnel in stead of Johnny's bridge program which I use?
Hans
Verzonden vanaf mijn BlackBerry 10-smartphone.
Van: Tim Sneddon
Verzonden: vrijdag 2 januari 2015 18:24
Aan: hecnet at update.uu.se
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Hecnet Peering
On Sat, Jan 3, 2015 at 1:17 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
The short form... DEChubs are us. I have both the backplanes and the MultiStacks. They currently have hubs, LAT servers, and dedicated LAT printer modules. I even have the Packet Probe module with software...
That should work nicely.
Regards, Tim.
On Sat, Jan 3, 2015 at 1:17 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
The short form... DEChubs are us. I have both the backplanes and the MultiStacks. They currently have hubs, LAT servers, and dedicated LAT printer modules. I even have the Packet Probe module with software...
That should work nicely.
Regards, Tim.
Tim,
The short form... DEChubs are us. I have both the backplanes and the MultiStacks. They currently have hubs, LAT servers, and dedicated LAT printer modules. I even have the Packet Probe module with software...
-Steve
On Jan 2, 2015, at 12:09, Tim Sneddon <tim at sneddon.id.au> wrote:
On Sat, Jan 3, 2015 at 12:58 AM, Steve Davidson <steve at davidson.net> wrote:
How much should I expect to pay for one of these units?
It depends. A Cisco 1841 with nothing in it (just Ethernet interfaces) can be as cheap as $50. The DECbrouters can be as low as $20. The only killer about the DECbrouter is that unless you have a DEChub or MultiStack, finding one with a power supply is a pain. If you have a DEChub (or MultiStack), then I can ship you one for free in a few weeks. I have appropriate versions of software for all.
Regards, Tim.
On Sat, Jan 3, 2015 at 12:58 AM, Steve Davidson <steve at davidson.net> wrote:
How much should I expect to pay for one of these units?
It depends. A Cisco 1841 with nothing in it (just Ethernet interfaces) can be as cheap as $50. The DECbrouters can be as low as $20. The only killer about the DECbrouter is that unless you have a DEChub or MultiStack, finding one with a power supply is a pain. If you have a DEChub (or MultiStack), then I can ship you one for free in a few weeks. I have appropriate versions of software for all.
Regards, Tim.
How much should I expect to pay for one of these units?
-Steve
On Jan 2, 2015, at 11:52, Tim Sneddon <tim at sneddon.id.au> wrote:
On Sat, Jan 3, 2015 at 12:42 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
What are the hardware/software requirements for these tunnels?
Hi Steve,
They are just Cisco (or DEC-branded Cisco) routers that are connected via a mesh of GRE tunnels. The tunnels themselves only run DECnet over them (Phase IV, although OSI could be done). I now use a Cisco 1841. However, I previously used a DECbrouter 90T2a. I know that others use various other models of Cisco routers 3000 and 7000 series, I believe.
Regards, Tim.
-Steve
Hollis, NH (US)
On Jan 2, 2015, at 11:34, Tim Sneddon <tim at sneddon.id.au> wrote:
On Fri, Jan 2, 2015 at 10:25 PM, Peter Lothberg <roll at stupi.se> wrote:
> Think that the config below wouldn=E2=80=99t work s the decent node-type =
> is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
Hi Peter,
I would love to get tunnels up and running to your part of the world. We did talk about it about 6 months back, but nothing ever came of it. Are you still interested? My endpoint is 120.146.225.243.
Regards, Tim.
On Sat, Jan 3, 2015 at 12:42 AM, Steve Davidson <steve at davidson.net> wrote:
Tim,
What are the hardware/software requirements for these tunnels?
Hi Steve,
They are just Cisco (or DEC-branded Cisco) routers that are connected via a mesh of GRE tunnels. The tunnels themselves only run DECnet over them (Phase IV, although OSI could be done). I now use a Cisco 1841. However, I previously used a DECbrouter 90T2a. I know that others use various other models of Cisco routers 3000 and 7000 series, I believe.
Regards, Tim.
-Steve
Hollis, NH (US)
On Jan 2, 2015, at 11:34, Tim Sneddon <tim at sneddon.id.au> wrote:
On Fri, Jan 2, 2015 at 10:25 PM, Peter Lothberg <roll at stupi.se> wrote:
> Think that the config below wouldn=E2=80=99t work s the decent node-type =
> is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
Hi Peter,
I would love to get tunnels up and running to your part of the world. We did talk about it about 6 months back, but nothing ever came of it. Are you still interested? My endpoint is 120.146.225.243.
Regards, Tim.
On 2015-01-02 17:42, Steve Davidson wrote:
Tim,
What are the hardware/software requirements for these tunnels?
Cisco routers with the DECnet routing software installed.
Johnny
-Steve
Hollis, NH (US)
On Jan 2, 2015, at 11:34, Tim Sneddon <tim at sneddon.id.au
<mailto:tim at sneddon.id.au>> wrote:
On Fri, Jan 2, 2015 at 10:25 PM, Peter Lothberg <roll at stupi.se
<mailto:roll at stupi.se>> wrote:
> Think that the config below wouldn=E2=80=99t work s the decent
node-type =
> is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
Hi Peter,
I would love to get tunnels up and running to your part of the world.
We did talk about it about 6 months back, but nothing ever came of
it. Are you still interested? My endpoint is 120.146.225.243.
Regards, Tim.
--
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
Tim,
What are the hardware/software requirements for these tunnels?
-Steve
Hollis, NH (US)
On Jan 2, 2015, at 11:34, Tim Sneddon <tim at sneddon.id.au> wrote:
On Fri, Jan 2, 2015 at 10:25 PM, Peter Lothberg <roll at stupi.se> wrote:
> Think that the config below wouldn=E2=80=99t work s the decent node-type =
> is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
Hi Peter,
I would love to get tunnels up and running to your part of the world. We did talk about it about 6 months back, but nothing ever came of it. Are you still interested? My endpoint is 120.146.225.243.
Regards, Tim.
On Fri, Jan 2, 2015 at 10:25 PM, Peter Lothberg <roll at stupi.se> wrote:
> Think that the config below wouldn=E2=80=99t work s the decent node-type =
> is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
Hi Peter,
I would love to get tunnels up and running to your part of the world. We did talk about it about 6 months back, but nothing ever came of it. Are you still interested? My endpoint is 120.146.225.243.
Regards, Tim.
On Sat, Jan 3, 2015 at 12:11 AM, Johnny Billquist <bqt at softjar.se> wrote:
I just checked some more. I can reach BENDER:: (12,2), so based on that, HUB:: would appear to run correctly.
(HUB:: is supposedly my next hop going to BENDER::)
BENDER:: seems to be running Phase V (I suspect), as I can't really speak NICE to it, but PHONE worked fine.
You are correct, BENDER:: is Phase V.
Not sure what the problem going to area 22 would be then...
Sometimes I have noticed dodgy routing. For a while there was a node on the network advertising bad routes to the 12 network. I think it was a Linux box doing it. I never figured out what was doing it as by the time I got home and started looking at it, everything seemed to work just fine :-)
Regards, Tim.
Think that the config below wouldn=E2=80=99t work s the decent node-type =
is routing-iv which is a L1 router?
My fault. If you talk to dimma in area 59 it should say;
decnet node-type area
-P
I just checked some more. I can reach BENDER:: (12,2), so based on that, HUB:: would appear to run correctly.
(HUB:: is supposedly my next hop going to BENDER::)
BENDER:: seems to be running Phase V (I suspect), as I can't really speak NICE to it, but PHONE worked fine.
Not sure what the problem going to area 22 would be then...
Johnny
On 2015-01-02 16:32, Mark Darvill wrote:
Hi Tim,
DECnet on this test system is just Decnet IV running on VMS 7.3.
I can t do a loop node to 12.1023 but not sure that would work anyway if
it is a cisco.
Also can t seem to get to 12.2. Have just rebooted 22.10 as SIMH may
have crashed.
Mark
On 2 Jan 2015, at 15:15, Tim Sneddon <tim at sneddon.id.au
<mailto:tim at sneddon.id.au>> wrote:
On Fri, Jan 2, 2015 at 6:16 PM, Mark Darvill<mark.darvill at mac.com
<mailto:mark.darvill at mac.com>>wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the
break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44
64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45
64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38
64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33
64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is
22.10 and router 22.100
Can anyone see area 22 as I don t seem to be able to communicate
elsewhere.
Hi Mark,
My network is 12, your Tunnel57 hooks into my router. From my router
I am able to ping 22.100, but I cannot reach 22.10. Are you able to
hit my router (12.1023) or my VAX (12.2)? Which version of DECnet are
you running on 22.10?
I am happy to help you figure out what might be going on.
Regards, Tim.
--
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
Tim,
Just discovered the ping decnet command in IOS
Can ping you 12.1023 and 12.2 from the router which is good; can ping 22.10 from the router which is also good; but for some reason i cannot connect from VAX (22.10) on FastEthernet0/1 to 12.2.
This must be a local issue.
Is there anything else I need to setup above what I have for FE0/1 and decnet on my router?
decnet routing 22.100
decnet node-type area
interface FastEthernet0/1
ip address 10.22.1.254 255.255.255.0
speed auto
full-duplex
lat enabled
decnet cost 4
and my tunnel to you which I don t think is the problem
interface Tunnel57
description HECnet tunnel for Tim Sneddon (Area 12) [Version:274]
no ip address
decnet cost 20
tunnel source FastEthernet0/1
tunnel destination 120.146.225.243
tunnel path-mtu-discovery
Mark
On 2 Jan 2015, at 15:32, Mark Darvill <mark.darvill at mac.com> wrote:
Hi Tim,
DECnet on this test system is just Decnet IV running on VMS 7.3.
I can t do a loop node to 12.1023 but not sure that would work anyway if it is a cisco.
Also can t seem to get to 12.2. Have just rebooted 22.10 as SIMH may have crashed.
Mark
On 2 Jan 2015, at 15:15, Tim Sneddon <tim at sneddon.id.au> wrote:
On Fri, Jan 2, 2015 at 6:16 PM, Mark Darvill <mark.darvill at mac.com> wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44 64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45 64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38 64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33 64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and router 22.100
Can anyone see area 22 as I don t seem to be able to communicate elsewhere.
Hi Mark,
My network is 12, your Tunnel57 hooks into my router. From my router I am able to ping 22.100, but I cannot reach 22.10. Are you able to hit my router (12.1023) or my VAX (12.2)? Which version of DECnet are you running on 22.10?
I am happy to help you figure out what might be going on.
Regards, Tim.
Hi Peter,
Similar to the tunnel defs I have already that were pushed by Brian.
Think that the config below wouldn t work s the decent node-type is routing-iv which is a L1 router?
I am trying few things but I may take you up on the tunnel offer later.
Thanks, Mark
On 2 Jan 2015, at 15:36, Peter Lothberg <roll at Stupi.SE> wrote:
I'm happy to add a tunnel to Dimma if you would like to try that?
Config hints:
decnet routing 22.10
decnet node-type routing-iv
!
interface Tunnel4000
description tunnel to Stockholm 59.60
no ip address
decnet cost 10
tunnel source your-ip
tunnel destination 130.238.19.60
!
interface FastEthernet0/0
decnet cost 10
-P
Hi Paul,
VAX is a L1 router and cisco is an Area L2 router
I get an adjacency up between VAX and cisco when I bring the router up. I can see Area 22 from VAX with the next node to Area being 22.100, so things look OK locally.
The router must be using the tunnels to see neighbours.
Mark
On 2 Jan 2015, at 15:37, Paul_Koning at Dell.com wrote:
On Jan 2, 2015, at 5:16 AM, Mark Darvill <mark.darvill at mac.com> wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
...
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and router 22.100
What node type is your VAX? L1 router? What does it report as reachable? What events do you get when you bring up the connection to the router?
paul
On Jan 2, 2015, at 5:16 AM, Mark Darvill <mark.darvill at mac.com> wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
...
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and router 22.100
What node type is your VAX? L1 router? What does it report as reachable? What events do you get when you bring up the connection to the router?
paul
I'm happy to add a tunnel to Dimma if you would like to try that?
Config hints:
decnet routing 22.10
decnet node-type routing-iv
!
interface Tunnel4000
description tunnel to Stockholm 59.60
no ip address
decnet cost 10
tunnel source your-ip
tunnel destination 130.238.19.60
!
interface FastEthernet0/0
decnet cost 10
-P
Hi Tim,
DECnet on this test system is just Decnet IV running on VMS 7.3.
I can t do a loop node to 12.1023 but not sure that would work anyway if it is a cisco.
Also can t seem to get to 12.2. Have just rebooted 22.10 as SIMH may have crashed.
Mark
On 2 Jan 2015, at 15:15, Tim Sneddon <tim at sneddon.id.au> wrote:
On Fri, Jan 2, 2015 at 6:16 PM, Mark Darvill <mark.darvill at mac.com> wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44 64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45 64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38 64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33 64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and router 22.100
Can anyone see area 22 as I don t seem to be able to communicate elsewhere.
Hi Mark,
My network is 12, your Tunnel57 hooks into my router. From my router I am able to ping 22.100, but I cannot reach 22.10. Are you able to hit my router (12.1023) or my VAX (12.2)? Which version of DECnet are you running on 22.10?
I am happy to help you figure out what might be going on.
Regards, Tim.
On Fri, Jan 2, 2015 at 6:16 PM, Mark Darvill <mark.darvill at mac.com> wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44 64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45 64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38 64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33 64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and router 22.100
Can anyone see area 22 as I don t seem to be able to communicate elsewhere.
Hi Mark,
My network is 12, your Tunnel57 hooks into my router. From my router I am able to ping 22.100, but I cannot reach 22.10. Are you able to hit my router (12.1023) or my VAX (12.2)? Which version of DECnet are you running on 22.10?
I am happy to help you figure out what might be going on.
Regards, Tim.
Thanks Johnny,
I did look via the web on MIM, there definitely seems to be an issue somewhere in-between as it seems as though I am exchanging L2 Hellos OK.
Ian are you online, have you got adjacency and can you connect elsewhere?
Anyone else any ideas?
Thanks, Mark
On 2 Jan 2015, at 12:34, Johnny Billquist <bqt at softjar.se> wrote:
Hmm. Looking from MIM (you know, you could do this yourself as well), it seems as if area 22 would be reachable. Next hop is HUB:: (42.1022).
However, I HUB:: is a Cisco, so I cannot extract any information from it.
I tried talking to 22.10, but no success. I don't know what the problem is. Hard to diagnose.
I tried several places that goes through HUB:: but cannot find any I can talk to.
I also tried some nodes that runs through DIMMA::, and they work fine.
(Both HUB:: and DIMMA:: are Cisco boxes).
So it's not a generic problem with the Ciscos, but something more specific to HUB:: I suspect.
Johnny
On 2015-01-02 11:16, Mark Darvill wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44 64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45 64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38 64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33 64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and
router 22.100
Can anyone see area 22 as I don t seem to be able to communicate elsewhere.
Thanks, Mark
--
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
Hmm. Looking from MIM (you know, you could do this yourself as well), it seems as if area 22 would be reachable. Next hop is HUB:: (42.1022).
However, I HUB:: is a Cisco, so I cannot extract any information from it.
I tried talking to 22.10, but no success. I don't know what the problem is. Hard to diagnose.
I tried several places that goes through HUB:: but cannot find any I can talk to.
I also tried some nodes that runs through DIMMA::, and they work fine.
(Both HUB:: and DIMMA:: are Cisco boxes).
So it's not a generic problem with the Ciscos, but something more specific to HUB:: I suspect.
Johnny
On 2015-01-02 11:16, Mark Darvill wrote:
HI,
I have been playing with my cisco router and a SIMH Vax over the break.
from my router I can see the following neighbours
cmrtr01#show decnet nei
Net Node Interface MAC address Flags
0 12.1023 Tunnel57 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 22.10 FastEthernet0/1 aa00.0400.0a58 V
and the following routes
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 50 2 Tunnel51 -> 42.1022
*2 52 4 Tunnel51 -> 42.1022
*3 51 3 Tunnel51 -> 42.1022
*7 50 2 Tunnel51 -> 42.1022
*8 50 2 Tunnel51 -> 42.1022
*9 40 2 Tunnel57 -> 12.1023
*11 50 2 Tunnel51 -> 42.1022
*12 20 1 Tunnel57 -> 12.1023 44 64 A+
*18 51 3 Tunnel51 -> 42.1022
*19 50 2 Tunnel51 -> 42.1022
*22 0 0 (Local) -> 22.100
*23 40 2 Tunnel53 -> 61.1023
*28 50 2 Tunnel51 -> 42.1022
*33 51 3 Tunnel51 -> 42.1022
*39 51 3 Tunnel51 -> 42.1022
*42 20 1 Tunnel51 -> 42.1022 45 64 A+
*47 50 2 Tunnel51 -> 42.1022
*59 50 2 Tunnel51 -> 42.1022
*61 20 1 Tunnel53 -> 61.1023 38 64 A+
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.10 4 1 FastEthernet0/1 -> 22.10 33 64 V
*22.100 0 0 (Local) -> 22.100
My SIMH Vax can see my router and has an adjacency. My node is 22.10 and
router 22.100
Can anyone see area 22 as I don t seem to be able to communicate elsewhere.
Thanks, Mark
--
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
