Re: problem with segments

1998-07-22 13:10:15
Subject: Re: problem with segments
To: nv-l AT lists.tivoli DOT com
Date: Wed, 22 Jul 1998 19:10:15 +0200
     You are right James. Early versions of OpenView Network Node Manager
     (4.11 and some versions before) used private HP MIB's to display the
     level-2 topology of HP hubs, bridges and switches. In version 5.0 and
     onwards NNM is using standard IETF MIB's (Bridge, repeater and MAU
     MIB) to do this job making it more generic. Since NetView 5.0 isn't
     based on NNM 5.0 and earlier version was based on private HP MIB's is
     there no easy way to make NetView do this level-2 discovery and layout
     for non-HP devices.

     - Michael.

______________________________ Reply Separator _________________________________
Subject: Re: problem with segments
Author:  Non-HP-James-Shanks (James_Shanks AT TIVOLI DOT COM) at 
Date:    22-07-98 18:37

I think that the answer here is that HP devices are a special case.  The
base code for NetView is from HP's OpenView and there are all sorts of
special exits and processing embedded in the code for HP devices.  The
problem is that these are not easily generalized to fit other cases.
Leslie's description is an accurate account of the more usual and general
situation.  If you are running NetView, rather than OpenView,  in a network
with a lot of HP hardware, then you have a very unique situation indeed.

James Shanks
Tivoli (NetView for UNIX) L3 Support

"S. John Banner" <jbanner AT UVIC DOT CA> on 07/22/98 12:21:24 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView et alia <NV-L AT UCSBVM.UCSB DOT EDU>

cc:    (bcc: James Shanks)
Subject:  Re: problem with segments

> -----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
> 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
anything more than that it recognizes it.
   Given that NetView is smart enough to deal with the HP hubs, I would
to get NetView recognizing more of the segments created by bridges,
and repeaters, but I have no idea what it is actually looking for.


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