You can do "NCP SET KNOWN LOGGING ALL" and the "REPLY /ENABLE" to see all
the DECnet events. That may give you a clue (or maybe not :-)
I apparently have that turned on already. Nope, not enough of a clue.
I think I'm going to set up MultiNet on the Alpha and try using a TCP circuit between LULU and DUSTY. This will tell me whether it's a DECnet routing issue or an Ethernet packet one.
--Marc
I wonder whether it's not getting some of the multicasts.
You can do "NCP SET KNOWN LOGGING ALL" and the "REPLY /ENABLE" to see all
the DECnet events. That may give you a clue (or maybe not :-)
Bob
Must be some problem with either of the nodes then, because normally the adjacency will come up, when the end node starts receiving the router hellos.
Can you monitor the Ethernet with a protocol analyzer? You should see the hellos from both nodes.
I think I can try this. The setup is a bit more complicated than I'd like.
One more thing to check: you might have some equipment filtering multicast packets on the Ehternet. Like e.g. a routing switch. Also firewalls (software in a PC) might do that. I assume you run the Personal Alpha on a PC.
It's Personal Alpha running on a virtualized Windows XP guest running on an ESXi host. In comparison, the VAX is running on a virtualized Ubuntu guest running on the same ESXi host. Since networking seems to be working on the VAX, I'm thinking that it has something to do with the way Personal Alpha does its networking. I wonder whether it's not getting some of the multicasts.
--Marc
Marc Chametzky wrote:
Have you checked that node DUSTY is sending its router hello packets on the Ethernet circuit?
Does node LULU receive the router hellos from node DUSTY?
I do have "Hello timer = 15" on DUSTY. I do have connectivity between LULU and DUSTY, but now I wonder whether it's full connectivity. Perhaps there's a problem with Personal Alpha's network emulation. It may not be receiving all of the packets.
What does node LULU indicate as the adjacency? It should be node DUSTY unless you have another Level 1 (with higher priority) or Level 2 router on the same circuit.
When I do a "SHOW CIRC SVA-0 STAT" on LULU, I don't see any adjacent node.
--Marc
.
Must be some problem with either of the nodes then, because normally the adjacency will come up, when the end node starts receiving the router hellos.
Can you monitor the Ethernet with a protocol analyzer? You should see the hellos from both nodes.
One more thing to check: you might have some equipment filtering multicast packets on the Ehternet. Like e.g. a routing switch. Also firewalls (software in a PC) might do that. I assume you run the Personal Alpha on a PC.
Have you checked that node DUSTY is sending its router hello packets on the Ethernet circuit?
Does node LULU receive the router hellos from node DUSTY?
I do have "Hello timer = 15" on DUSTY. I do have connectivity between LULU and DUSTY, but now I wonder whether it's full connectivity. Perhaps there's a problem with Personal Alpha's network emulation. It may not be receiving all of the packets.
What does node LULU indicate as the adjacency? It should be node DUSTY unless you have another Level 1 (with higher priority) or Level 2 router on the same circuit.
When I do a "SHOW CIRC SVA-0 STAT" on LULU, I don't see any adjacent node.
--Marc
LULU, on the other hand, can only connect to DUSTY. It can't connect to
LEGATO.
Hmm. What makes you think this? I ask because LEGATO can connect to LULU
(I just tried it a minute ago), so it is working at least one way.
That is strange... I saw your connection attempt, but my attempts to contact LEGATO don't work as well:
$ set host legato
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
When I look in NCP, I see something that doesn't look right.
NCP>show node legato
Node Volatile Summary as of 6-APR-2009 12:06:19
Node State Active Delay Circuit Next node
Links
2.1 (LEGATO) SVA-0 0
I would expect that the next node should be 2.210 (DUSTY), but it doesn't know how to get there.
--Marc
Marc Chametzky wrote:
I have my new system, LULU, up and it's connected via Ethernet on the same network segment as DUSTY. LULU is a non-routing end node.
DUSTY is "TYPE ROUTING IV" and has two circuits, TCP-0-0 to LEGATO and QNA-0 for the local network. DUSTY has connectivity to both LEGATO (and the rest of HECnet) and also to LULU.
LULU, on the other hand, can only connect to DUSTY. It can't connect to LEGATO.
I thought that DUSTY, being a routing node, would route packets between its two circuits, but that appears not to be the case. I tried setting DUSTY up as an area router, thinking that making it a level 2 router would permit LULU's packets to go through DUSTY, but that didn't seem to work either.
What should I do in order to get DUSTY to route the packets from LULU to the rest of HECnet?
--Marc
.
Have you checked that node DUSTY is sending its router hello packets on the Ethernet circuit?
Does node LULU receive the router hellos from node DUSTY?
What does node LULU indicate as the adjacency? It should be node DUSTY unless you have another Level 1 (with higher priority) or Level 2 router on the same circuit.
How are you trying to connect? Do you have an up-to-date node list on LULU?
SET HOST LEGATO
or
SET HOST 2.1
Zane
On Mon, 6 Apr 2009, Marc Chametzky wrote:
LULU, on the other hand, can only connect to DUSTY. It can't connect to
LEGATO.
Hmm. What makes you think this? I ask because LEGATO can connect to LULU
(I just tried it a minute ago), so it is working at least one way.
That is strange... I saw your connection attempt, but my attempts to contact LEGATO don't work as well:
$ set host legato
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
When I look in NCP, I see something that doesn't look right.
NCP>show node legato
Node Volatile Summary as of 6-APR-2009 12:06:19
Node State Active Delay Circuit Next node
Links
2.1 (LEGATO) SVA-0 0
I would expect that the next node should be 2.210 (DUSTY), but it doesn't know how to get there.
--Marc
