[OT]Ispmap / isp locations / core routers
Hey guys, I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz . 1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice. To gather this info, simply fire up http://status.fast.co.nz/metric.html , zoom in to the closest location to your office/router as possible, center it in the screen and mail me the details of latitude and longitude. http://status.fast.co.nz will soon become apart of ispmap, if you go directly to this URL you will see what my aim is, to have a country map (with the ability to filter by ISP) with the status of each ISP's network. Please mail back (Off list) in the following format: ISP: Contact: Logitude: Latitude: IP Address: Services effected: (optional, but would be nice to see what parts of the country and what services would be effected) Equipment: (optional, but eg cisco, I may add logos to the map later) Thanks. Barry
Barry Murphy wrote:
Hey guys,
I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz .
1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice.
*sigh* Far, FAR too much free time. /me points Barry at the pub Take five of these, and repeat, daily. -Richard
It's beer that makes me do things like this :) Either that or red wine, maybe I should stop? Barry
-----Original Message----- From: Richard Patterson [mailto:richard(a)helix.net.nz] Sent: Monday, 18 July 2005 6:44 p.m. To: Barry Murphy Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] [OT]Ispmap / isp locations / core routers
Barry Murphy wrote:
Hey guys,
I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz .
1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice.
*sigh*
Far, FAR too much free time.
/me points Barry at the pub
Take five of these, and repeat, daily.
-Richard
Hey guys,
I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz .
1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice.
OK, I'll bite. Why? What does this gain me, other than an outdated map of the NZ Internet that is relied apon by "knowledgable" users to diagnose problems? (The user calling the helpdesk to complain about said 'problems', and other associated whinging is implied.) -- Nathan Ward
On Tue, 19 Jul 2005, Nathan Ward wrote:
1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice.
OK, I'll bite. Why?
Adding to this a little, what's a "main core router"? Most of the big players have networks with geographical diversity, as well as big enough networks that I'm not sure you could class any one or two routers as "the core". --David
Hey David,
The idea is to ascertain where an issue may lie. I understand the network
will most likely heal its' self, however it's still nice to know where the
issue lies.
I'm guessing customers connect directly to the erx's, thus if the erxcrash's
and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss.
Let's just see what happens when the next big network fault happens.
Barry
----- Original Message -----
From: "David Robb"
On Tue, 19 Jul 2005, Nathan Ward wrote:
1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice.
OK, I'll bite. Why?
Adding to this a little, what's a "main core router"? Most of the big players have networks with geographical diversity, as well as big enough networks that I'm not sure you could class any one or two routers as "the core".
--David
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Hey David,
The idea is to ascertain where an issue may lie. I understand the network will most likely heal its' self, however it's still nice to know where the issue lies. I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
What will happen, is that individuals responsible for networks will troubleshoot _their own networks_ and establish who _they_ can communicate with. They'll then liase with those with whom they cannot connect with (or through) in the normal fashion. Not only does this already 'work' but it doesn't rely on third-hand and questionably-out-of-date information found on a website that might not even be accessible in said 'big network fault'. Further, this uses existing business relationships - eg, a provider talks to its upstream, who talks to its upstream and various downstreams, etc etc. Where X routes to Z via Y then B then C, theres little point in X and Z talking to eachother and adding to the noise when what they should both be talking to their upstreams (Y and C) who will both then be liasing with B as appropriate. ? I dont disagree that 'power users' will find the info useful - I question the value of giving these people more information than is useful to them. An ISP guages outage impact on reports that it receives from end users. End user should simply be reporting the symptoms to their helpdesk, and the ISP employees do the faultfinding. Not the customers... Mark.
On Tue, 19 Jul 2005, Barry Murphy wrote:
The idea is to ascertain where an issue may lie. I understand the network will most likely heal its' self, however it's still nice to know where the issue lies.
I'd be careful how much value you put in real world geographical data and hence topology, vs network topology. As I think we're all aware, networks can be complicated beasties depending on which way you try and draw them.
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
Well yes, if a customer's single homed off of any device and it dies for some reason they'll lose service. But in most networks there are many more devices than just the routers, and I doubt you'll get anyone telling you their complete network layout.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
--David
Nice one David - network topology gets funky when one starts playing with tunnels. Given the fact that the router next to me gets its public address space through an L2TP tunnel back to WIX, there's no way for you to know if latency to my network is due to a broken router, a bounce off a satellite, a network of bongo drums, or because I've decided to take my entire network on vacation to Nizhneangarsk. JB -----Original Message----- From: David Robb [mailto:ender(a)paradise.gen.nz] Sent: Tuesday, 19 July 2005 10:33 a.m. To: Barry Murphy Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] [OT]Ispmap / isp locations / core routers On Tue, 19 Jul 2005, Barry Murphy wrote:
The idea is to ascertain where an issue may lie. I understand the network will most likely heal its' self, however it's still nice to know where the issue lies.
I'd be careful how much value you put in real world geographical data and hence topology, vs network topology. As I think we're all aware, networks can be complicated beasties depending on which way you try and draw them.
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
Well yes, if a customer's single homed off of any device and it dies for some reason they'll lose service. But in most networks there are many more devices than just the routers, and I doubt you'll get anyone telling you their complete network layout.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
--David _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On Tue, 19 Jul 2005, Barry Murphy wrote:
Hey David,
The idea is to ascertain where an issue may lie. I understand the network will most likely heal its' self, however it's still nice to know where the issue lies. I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations. Any information gathered through probing networks will most certainly be inaccurate and could lead (as pointed out earlier) to increased frustration in helpdesks when some clueless customer rings up to report an ERX crash because they saw it on your intarwebnet page. -- Steve.
Steve Phillips wrote:
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations.
Lord forbid any terroristic rats got ahold of said commercially sensitive geographical information. Just think how many outages would happen then!!!11one Full scale tactical rodent attack, thats just like giving them a map saying "Please bomb here! with a giant fluorescent arrow sign pointing down" s/bomb/chew/ /me twitches and goes back to his coffee
On Mon, 18 Jul 2005, Barry Murphy wrote:
Please mail back (Off list) in the following format:
ISP: Logitude: Latitude: IP Address:
Lat/Long? I'm not really sure that this is terrifically useful info. Who cares where they physically are, below a level of granularity like "Auckland" or "Wellington" or _maybe_ "The Sky Tower" or something. What you really need, and what most places will be using internally anyway, is a dependency tree for network services. And I'm pretty sure that most companies won't want to part with that. JSR
participants (8)
-
Barry Murphy -
David Robb -
John S Russell -
Jonathan Brewer -
Mark Foster -
Nathan Ward -
Richard Patterson -
Steve Phillips