On 26 Dec 2012, at 01:33, sampsa at mac.com wrote:
I did said quick hack from STUPI to GW, here's the new router graph:
http://www.sampsa.com/just-routers.svg
So my suggestion to those with "weird" links that we can't crawl is that they provide us with two things:
- A list of their connections to the rest of HECnet (i.e. the area routers)
- A list of the end nodes that are connected to their area routers
Formats for these will follow, they're basically CSV.
Is this OK, Dave etc with CISCO gear?
I did said quick hack from STUPI to GW, here's the new router graph:
http://www.sampsa.com/just-routers.svg
On 26 Dec 2012, at 01:21, sampsa at mac.com wrote:
Quick hack would be to have them self declare their router links, we then just add them to the output CSV :)
On 26 Dec 2012, at 01:20, Bob Armstrong <bob at jfcl.com> wrote:
So how do we find them when crawling?
Short answer - don't know. I believe the Ciscos have DECnet node numbers
and run an NML equivalent (i.e. they respond to NCP commands) but I don't
know much about them. Sorry; I don't have one.
Bob
Quick hack would be to have them self declare their router links, we then just add them to the output CSV :)
On 26 Dec 2012, at 01:20, Bob Armstrong <bob at jfcl.com> wrote:
So how do we find them when crawling?
Short answer - don't know. I believe the Ciscos have DECnet node numbers
and run an NML equivalent (i.e. they respond to NCP commands) but I don't
know much about them. Sorry; I don't have one.
Bob
So how do we find them when crawling?
Short answer - don't know. I believe the Ciscos have DECnet node numbers
and run an NML equivalent (i.e. they respond to NCP commands) but I don't
know much about them. Sorry; I don't have one.
Bob
On 26 Dec 2012, at 01:14, Bob Armstrong <bob at jfcl.com> wrote:
Found the problem, STUPI isn't listing you as a known circuit:
I think the actual connection is between their Cisco routers. STUPI has
nothing to do with it and doesn't know about it.
Bob
So how do we find them when crawling?
Found the problem, STUPI isn't listing you as a known circuit:
I think the actual connection is between their Cisco routers. STUPI has
nothing to do with it and doesn't know about it.
Bob
On 25 Dec 2012, at 18:11, sampsa at mac.com wrote:
On 26 Dec 2012, at 01:07, sampsa at mac.com wrote:
On 26 Dec 2012, at 01:04, Cory Smelosky <b4 at gewt.net> wrote:
What's the Alpha hosted on - is it getting promiscuous mode access to the Ethernet adapter?
It's running in PersonalAlpha on Windows Server 2003, so i'm not actually sure.
Check the network config.
Here's mine (running on Win2K3 on a VMware Fusion VM) and DECNET works fine:
Oooops. It's not PersonalAlpha. It's FreeAXP. ;)
http://i45.tinypic.com/apfz0i.jpg
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 26 Dec 2012, at 01:07, sampsa at mac.com wrote:
On 26 Dec 2012, at 01:04, Cory Smelosky <b4 at gewt.net> wrote:
What's the Alpha hosted on - is it getting promiscuous mode access to the Ethernet adapter?
It's running in PersonalAlpha on Windows Server 2003, so i'm not actually sure.
Check the network config.
Here's mine (running on Win2K3 on a VMware Fusion VM) and DECNET works fine:
http://i45.tinypic.com/apfz0i.jpg
On 26 Dec 2012, at 01:04, Cory Smelosky <b4 at gewt.net> wrote:
What's the Alpha hosted on - is it getting promiscuous mode access to the Ethernet adapter?
It's running in PersonalAlpha on Windows Server 2003, so i'm not actually sure.
Check the network config.
On 25 Dec 2012, at 17:59, sampsa at mac.com wrote:
On 26 Dec 2012, at 00:58, Cory Smelosky <b4 at gewt.net> wrote:
The simulated Alpha throws a bunch of errors when I try to do anything involving DECnet. I might just be starting things out of order.
What's the Alpha hosted on - is it getting promiscuous mode access to the Ethernet adapter?
It's running in PersonalAlpha on Windows Server 2003, so i'm not actually sure.
Sampsa
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
