[HECnet] DECnet et al

Johnny Billquist bqt at softjar.se
Sat Jul 16 22:52:42 PDT 2011


On 2011-07-16 23:46, Paul Koning wrote:

On Jul 16, 2011, at 5:40 PM,<hvlems at zonnet.nl>   wrote:

Ok, so the convention that the output of the SHO NET command always lists the area router with the highest address is just a display rule. It has nothing to do with an "active" area router then?

I can't find the rule for what L2 adjacent router to pick if you're an L1 router going out of area.   It may be that this is where "highest" kicks in.

For non-adjacent L2 routers, the L1 router doesn't have any idea which router is represented by the "nearest L2 router" pseudo-address zero.   It can't know that.

I don't know all the details here, and instead of starting to read through documentation, perhaps you know, Paul, if L1 routers knows *which* nodes in the area are L2 routers?

Because L1 routers knows the shortest paths to all nodes within it's area, if I don't remember wrong.

However, an L1 router can never know which L2 router is the better for reaching a specific area, since L1 routers have no idea of the area topology.

But I *think* that L1 routers knows the type of nodes of all nodes in the local area, so they should easily be able to figure out where the closest L2 router is. But that is based on the assumption that they know the type of each node in the area.

	Johnny


	paul

------Origineel bericht------
Van: Paul Koning
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] DECnet et al
Verzonden: 16 juli 2011 23:25


On Jul 16, 2011, at 3:42 PM, Johnny Billquist wrote:

On 2011-07-16 19.18, hvlems at zonnet.nl wrote:
I'm not sure what the router rules are. There are 63 areas, each with
one actove area router. There may be more routers configured as an area
router in one area; the one with the highest (?) DECnet address is
selected as the active one.

As far as I know, there can be more than one active area router. Just look at what the next hop are for different nodes in your node list... :-)

The way it works is that address 0 in the level 1 routing data corresponds to "nearest L2 router".   Any L2 router contributes to that.   The L1 routers don't know or care who is the nearest L2 router, they only care which direction to send to get there.

	paul


Verzonden vanaf mijn draadloze BlackBerry  -toestel



-- 
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



More information about the Hecnet-list mailing list