Re: problem with segments

1998-07-22 12:21:24
Subject: Re: problem with segments
From: "S. John Banner" <jbanner AT UVIC DOT CA>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 22 Jul 1998 09:21:24 -0700
> -----Original Message-----
> From: Discussion of IBM NetView and POLYCENTER Manager on NetView et
> alia [mailto:NV-L AT UCSBVM.UCSB DOT EDU]On Behalf Of Leslie Clark
> Sent: Tuesday, July 21, 1998 8:47 PM
> Subject: Re: problem with segments
> Uwe, you are almost right. Netview draws one segment per protocol per
> network.
> It does NOT
> attempt to show relationships between nodes and hubs and bridges, other
> than
> the fact that they
> share a network address, and it shows this by putting them in the same
> segment,
> if they are of
> the same protocol, or in different segments in the same network submap
> ('network' here meaning
> 'subnet' as defined by the subnet mask.) The only devices drawn as
> Connectors
> are routers.
> Routers are anything with multiple interfaces and ipforwarding turned on.
> This
> is on the IP Internet
> submap (to map).  Desgnating things as H or B only gets them promoted from
> the
> Segment level
> submap to the Network level submap.
   Well, actually, that isn't right either.  I won't claim to know what is
right, but NetView recognizes some models of HP repeaters, and draws
multiple segments for each segment within the repeater, getting the right
hosts on each segment (these HP repeaters have ports split accross several
internal segments).  There are also cases where unnumbered serial links get
recognized as a separate segment within a subnet, and it seems to do a
similar thing with FDDI, but we don't have enough of that at our site to say
anything more than that it recognizes it.
   Given that NetView is smart enough to deal with the HP hubs, I would love
to get NetView recognizing more of the segments created by bridges, switches
and repeaters, but I have no idea what it is actually looking for.


<Prev in Thread] Current Thread [Next in Thread>