nv-l
[Top] [All Lists]

RE: Segment discovery

To: nv-l@lists.tivoli.com
Subject: RE: Segment discovery
From: "Chance, Larry" <lchance@sfbcic.com>
Date: Mon, 12 Jun 2000 09:03:07 -0500
Thanks Leslie.  I understand it better now.
And yes I was referring to subnets when I used
the term 'segments'.  

I recognize the problem now as a configuration
issue on the router and it's IP table.

Thanks again.

Larry

>> -----Original Message-----
>> From: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
>> Sent: Monday, June 12, 2000 8:33 AM
>> To: NV-L@tkg.com
>> Subject: Re: [NV-L] Segment discovery
>> 
>> 
>> 
>> 
>> It sounds like you are talking about subnets, as opposed to 
>> what Netview
>> calls segments and creates under subnets, right?  The 
>> networks it draws
>> (or subnets) are based solely on IP address with masks applied. Some
>> customers do not administer subnet masks on certain types of devices,
>> depending on whether their routing protocols require them, and are
>> surprised at the subnet addresses that Netview decides on in those
>> cases. If you select a device on the map and do 'Monitor... Network
>> Configuration... Addresses' (the wording may be different on NT) you
>> will see the addresses and masks of each interface. These are
>> pulled directly from the device via snmp. They come from the IP
>> Address table. Funny ones are useful for finding configuration errors
>> on the devices. If they are wrong, you can either correct the config
>> on the device and delete and rediscover it, or you can force it to be
>> loaded where you want it with the loadhost command, a messy
>> administrative task but sometimes the only solution.
>> 
>> What Netview calls Segments (Segment1, Segment2, etc) under each
>> subnet are just groupings based on the interface type as returned by
>> the device via snmp, eg TokenRing, FDDI, Ethernet, Other, etc.
>> 
>> Hope this helps. If not, ask with more words......
>> 
>> Cordially,
>> 
>> Leslie A. Clark
>> IBM Global Services - Systems Mgmt & Networking
>> Detroit
>> ---------------------- Forwarded by Leslie Clark/Southfield/IBM on
>> 06/12/2000 09:24 AM ---------------------------
>> 
>> 
>> 
>> "Chance, Larry" <lchance@sfbcic.com>@tkg.com on 06/09/2000 
>> 10:40:38 AM
>> 
>> 
>> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>> 
>> Sent by:  owner-nv-l@tkg.com
>> 
>> 
>> To:   "'NetviewListSERVERUsers nv-l@tkg.com'" <nv-l@tkg.com>
>> cc:
>> 
>> Subject:  [NV-L] Segment discovery
>> 
>> 
>> 
>> 
>> How does Netview determine the Network SEGMENTs when it
>> does an autodiscovery of the routers throughout the network?
>> 
>> I have users at a remote site that question the SEGMENT numbers
>> on their map, which was assigned by Netview.
>> 
>> It looks to me that Netview reads the route table entries 
>> after gathering
>> the router's interfaces and masks and calculates the SEGMENT number.
>> I would think those entries come from the 'routing' 
>> protocols used and
>> configured on the router, along with the 'network' number 
>> for the 'routing'
>> protocol, such as IGRP.  More or less, Is it the configuration of the
>> router
>> that causes the SEGMENT number.  Am I even close?
>> 
>> Thanks,
>> Larry
>> 
>> 
>> 
>> _____________________________________________________________
>> ____________
>> NV-L List information and Archives: http://www.tkg.com/nv-l
>> 
>> 
>> _____________________________________________________________
>> ____________


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

Archive operated by Skills 1st Ltd

See also: The NetView Web