Connect to SG1:: on the East Coast as the primary, LEGATO:: on the West
Coast as the secondary.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Cory Smelosky
Sent: Tuesday, December 25, 2012 2:06 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] Getting a virtual cluster connected
Hello everyone!
I've decided to bring up the random virtual cluster I was running on a
friend's server, and I want to get it connected to HECnet. ;)
The IP is static so connecting it should be easier, the server is in
North Carolina. It's looking like i'll need to go install multinet on
one of the cluster members as that'll be easier than bringing up a linux
VM to run Johnny''s bridge. ;)
What areas are available? I'll go renumber to one of the free
areas...once I either remember or reset the SYSTEM password.
Thanks.
How is this:
http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=vax780
Will that work?
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of sampsa at mac.com
Sent: 25 December 2012 22:53
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet mapping project
Well, I think we should leave the format alone and just add LAT= and LONG=
to the location field.
It's not hard to parse :)
Sampsa
On 26 Dec 2012, at 00:50, Rob Jarratt <robert.jarratt at ntlworld.com> wrote:
I think LAT/LONG is unambiguous and also gives you the opportunity to
be more precise if you want to. We can keep "location" as a more
informal description though.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE]
On Behalf Of Bob Armstrong
Sent: 25 December 2012 22:25
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] HECnet mapping project
I'd just add a LAT/LONG field before the notes one
FWIW, the existing INFO.TXT format already has a "location" field -
it's
City
and Country, but you can just geolocate the city center.
Bob
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
