On 2013-01-12 16:38, sampsa at
mac.com wrote:
OK what do you suggest?
Ah. Now, that is the trickier question. The only working solution I can think of is to
have the information manually provided.
In order to not put too much burden on one individual, it would be easier if we had an
agreed on format, and then a bunch of known places where to fetch those files, and then
aggregate it. The aggregation can be done in multiple places, if wanted. Once we have the
basic structure in place, we can deal with this in all kind of ways.
I'm not too fond of the solution, since it is bound to be out of date sooner or later,
but I don't see any other solution that is any better. But I'm also open to
suggestions...
Johnny
sampsa
On 12 Jan 2013, at 17:33, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 16:30, sampsa at
mac.com wrote:
On 12 Jan 2013, at 17:28, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 16:23, sampsa at
mac.com wrote:
I already do SHOW ADJ NODES on the router nodes, so that should have most non-CISCO stuff
covered no?
But they show up as gazillion ptp links unless you somehow start to figure out that this
is actually a bus. And then (not that I'm aware of any such links on HECnet right now)
the multidrop links, which connects several machines, but which actually are lots of ptp
connections...
Again NCP can't tell me that - a simple bit of metainfo in FAL could :)
Yes. Which is my point. NCP falls severely short if you want to use it for mapping.
Something else is needed, so let's do that something else instead, and do that
properly.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic
trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" -
B. Idol
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic
trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" -
B. Idol