Hi All,
Virgin have been mucking me about a bit. I will be upgraded to a new
cable modem next week which will mean I'll get a new IP address for ZAPHOD.
However, in the mean time they've mistakenly disconnected me and
reconnected me to a different IP!
Zaphod's current IP address is 82.8.17.191, but that WILL change next
Wednesday afternoon (GMT) so it's up to you if you change the multinet
connection in the meantime ... I won't be offended if I'm off HECnet for
a week, I'm far too busy doing other things anyway :S
I'll post the new IP address next week,
Sorry for the outage ... but it's not my fault :-(
Chrissie
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.
Well, with a DECnet-over-IP circuit instead, it's working just fine with both nodes seeing each other's adjacency, and from LULU I can connect to LEGATO.
So, some sort of Personal Alpha networking glitch. That's surprising since I do have the two nodes clustered, so that's working. I wonder what's not working right with DECnet routing multicasts.
Well, this may be suboptimal, but it works well enough and that's all that matters.
--Marc
Are your nodes on?
As of right now, DUSTY's the only one that is.
CALHAN is down pending me figuring a new host for it since it didn't work right on Ubuntu JeOS (some VMware networking issue). LULU is disconnected while I install MultiNet and get a TCP circuit up between it and DUSTY for testing.
--Marc
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.
