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...
Johnny
sampsa
On 12 Jan 2013, at 17:21, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 16:11, sampsa at mac.com wrote:
I won't - which is why I thought the bridge users could add some meta-info to their INFO.TXTs to help me map how they are connected, for example.
And all other ethernets?
Johnny
sampsa
On 12 Jan 2013, at 17:02, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 15:53, sampsa at mac.com wrote:
Johnny,
That's a graphic error, not a data collection one..
Ok. Since I don't know details on your implementation I'll have to take your word on that.
However, I still totally fail to see how you will ever be able to get the required information out from NCP, since NCP don't know (apart from not all nodes even talking NICE).
Johnny
sampsa
On 12 Jan 2013, at 16:35, Johnny Billquist <bqt at softjar.se> wrote:
Yes. That is one additional complication. However, looking at the current output from sampsa, it looks as if ethernet and multinet links are mixed on the same segment as well.
--
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
--
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
On 2013-01-12 16:10, Peter Lothberg wrote:
If you ask me, I think this idea is dead. You cannot get a good
representation of how the topology really is from trying to walk nodes
using NCP.
(remove bridged ethernet that are not point-to-point with only 2
nodes).
Walk through the "known cir" and then "cir char" and build your own
connectivity tree with the metrics.
Plot all links
Apply DECnet routing rules and Colour the links that carry traffic
with the current metrics and/up/down condition, use two colours, one
for transmitt one for receive (as links can end up being simplex).
Well, it all depends on what you want to know. If you want to properly
understand the topology you also want to represent the topology of
bridged ethernet segments, as well as ethernets in general. NCP don't
have any clue about this.
Sure, if you want to only have Multinet ptp links, then it's easy. But
that would a rather severe restriction on the network technology.
We have ethernets (both bridged and local), as well as Cisco tunnels.
Both of which walking with NCP fails on.
NCP don't fail on DECboxes on ethernets.
The plotting thing would do the right thing even on the ethernet, even
with the ethernet it ended up being a simplex path for some
multi-homed sites.
There are two ways of represnting the the Ethernet,
1 You draw it as a bus ignore that the links to it have
different characteristics.
2 You drow it as all the point-to-point links it represents.
Look how IP handles Ethernet, it builds simplex TX only point
to point links using ARP and a dest-ip address to MAC address
mapping.
-P
On 2013-01-12 16:21, Johnny Billquist wrote:
On 2013-01-12 16:10, Peter Lothberg wrote:
If you ask me, I think this idea is dead. You cannot get a good
representation of how the topology really is from trying to walk nodes
using NCP.
(remove bridged ethernet that are not point-to-point with only 2
nodes).
Walk through the "known cir" and then "cir char" and build your own
connectivity tree with the metrics.
Plot all links
Apply DECnet routing rules and Colour the links that carry traffic
with the current metrics and/up/down condition, use two colours, one
for transmitt one for receive (as links can end up being simplex).
Well, it all depends on what you want to know. If you want to properly
understand the topology you also want to represent the topology of
bridged ethernet segments, as well as ethernets in general. NCP don't
have any clue about this.
Sure, if you want to only have Multinet ptp links, then it's easy. But
that would a rather severe restriction on the network technology.
We have ethernets (both bridged and local), as well as Cisco tunnels.
Both of which walking with NCP fails on.
By the way. One thing I have not even touched on yet is that another "restriction" in all this is that not all nodes who even talk NICE will allow random other machines to query them.
Take WXP for example...
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
Brian H is working on the CISCO stuff and maybe the bridge users could provide some meta-info about their connections say in a BRIDGE.INFO file or something?
sampsa
On 12 Jan 2013, at 17:21, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 16:10, Peter Lothberg wrote:
If you ask me, I think this idea is dead. You cannot get a good
representation of how the topology really is from trying to walk nodes
using NCP.
(remove bridged ethernet that are not point-to-point with only 2
nodes).
Walk through the "known cir" and then "cir char" and build your own
connectivity tree with the metrics.
Plot all links
Apply DECnet routing rules and Colour the links that carry traffic
with the current metrics and/up/down condition, use two colours, one
for transmitt one for receive (as links can end up being simplex).
Well, it all depends on what you want to know. If you want to properly understand the topology you also want to represent the topology of bridged ethernet segments, as well as ethernets in general. NCP don't have any clue about this.
Sure, if you want to only have Multinet ptp links, then it's easy. But that would a rather severe restriction on the network technology.
We have ethernets (both bridged and local), as well as Cisco tunnels. Both of which walking with NCP fails on.
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
On 2013-01-12 16:11, sampsa at mac.com wrote:
I won't - which is why I thought the bridge users could add some meta-info to their INFO.TXTs to help me map how they are connected, for example.
And all other ethernets?
Johnny
sampsa
On 12 Jan 2013, at 17:02, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-01-12 15:53, sampsa at mac.com wrote:
Johnny,
That's a graphic error, not a data collection one..
Ok. Since I don't know details on your implementation I'll have to take your word on that.
However, I still totally fail to see how you will ever be able to get the required information out from NCP, since NCP don't know (apart from not all nodes even talking NICE).
Johnny
sampsa
On 12 Jan 2013, at 16:35, Johnny Billquist <bqt at softjar.se> wrote:
Yes. That is one additional complication. However, looking at the current output from sampsa, it looks as if ethernet and multinet links are mixed on the same segment as well.
--
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
On 2013-01-12 16:10, Peter Lothberg wrote:
If you ask me, I think this idea is dead. You cannot get a good
representation of how the topology really is from trying to walk nodes
using NCP.
(remove bridged ethernet that are not point-to-point with only 2
nodes).
Walk through the "known cir" and then "cir char" and build your own
connectivity tree with the metrics.
Plot all links
Apply DECnet routing rules and Colour the links that carry traffic
with the current metrics and/up/down condition, use two colours, one
for transmitt one for receive (as links can end up being simplex).
Well, it all depends on what you want to know. If you want to properly understand the topology you also want to represent the topology of bridged ethernet segments, as well as ethernets in general. NCP don't have any clue about this.
Sure, if you want to only have Multinet ptp links, then it's easy. But that would a rather severe restriction on the network technology.
We have ethernets (both bridged and local), as well as Cisco tunnels. Both of which walking with NCP fails on.
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
If you ask me, I think this idea is dead. You cannot get a good
representation of how the topology really is from trying to walk nodes
using NCP.
(remove bridged ethernet that are not point-to-point with only 2
nodes).
Walk through the "known cir" and then "cir char" and build your own
connectivity tree with the metrics.
Plot all links
Apply DECnet routing rules and Colour the links that carry traffic
with the current metrics and/up/down condition, use two colours, one
for transmitt one for receive (as links can end up being simplex).
..-P
I'm concurrently attacking it from three different directions: ssh,
snmp and mop remote console.
First one done wins. :)
You only have one alternative that works across all the cisco boxes in
HECnet, SNMP.
As I made a a image that works on 2500 with 8M flash and 16M ram,
there is not room for SSH....
-P
On 2013-01-12 15:53, sampsa at mac.com wrote:
Johnny,
That's a graphic error, not a data collection one..
Ok. Since I don't know details on your implementation I'll have to take your word on that.
However, I still totally fail to see how you will ever be able to get the required information out from NCP, since NCP don't know (apart from not all nodes even talking NICE).
Johnny
sampsa
On 12 Jan 2013, at 16:35, Johnny Billquist <bqt at softjar.se> wrote:
Yes. That is one additional complication. However, looking at the current output from sampsa, it looks as if ethernet and multinet links are mixed on the same segment as well.
--
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,
That's a graphic error, not a data collection one..
sampsa
On 12 Jan 2013, at 16:35, Johnny Billquist <bqt at softjar.se> wrote:
Yes. That is one additional complication. However, looking at the current output from sampsa, it looks as if ethernet and multinet links are mixed on the same segment as well.
