nv-l
[Top] [All Lists]

Re: [nv-l] SNMP MIB variables for Configuration Poll

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] SNMP MIB variables for Configuration Poll
From: Jane Curry <jane.curry@skills-1st.co.uk>
Date: Tue, 20 Apr 2004 14:57:07 +0100
Delivery-date: Tue, 20 Apr 2004 15:21:15 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <20D410241D54BC47A0F6F4FAA0C39182650A86@concernres01.zwolle.unive.nl>
References: <20D410241D54BC47A0F6F4FAA0C39182650A86@concernres01.zwolle.unive.nl>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
The easy request to your network supplier would be for read-Only access to all MIB-2 variables. That should at least get the routers discovered automatically. You can almost certainly restrict it further than that though I have never seen a comprehensive list and have not traced netmon to the extent of checking all the variables asked for in a discovery poll. My guess is that Mib-2 system, interface, arp and ip tables would probably suffice. The Cisco CDP Cache table is polled for unnumbered serial devices but the default route table will be used if there is no access to CDP cache.

Here is an entry from the Tivoli Support site:

page 152 of the Version 7 Administrator's Guide:
-------------------------------------------------------------------------
Information Retrieved When a new node is discovered, it is added to the topology database and also to the list of nodes that is being monitored. If the newly discovered node supports an SNMP agent, information about its system configuration is retrieved and stored in the database. Table 13 on page 152 shows the information that is retrieved:

Table 13. Configuration Information Retrieved From Nodes During Discovery

Information     MIB Variable    Description
System description sysDescr Includes the full name and version of the system’s hardware type, software operating system, and networking software. System object ID sysObjectID Identifies the network object’s place in the MIB hierarchy. Forwarding status ipForwarding Indicates whether this entity is acting as an IP gateway to forward datagrams received by, but not addressed to, this entity IP address table ipAddrTable Lists addressing information relevant to this entity’s IP addresses. Interface table ifTable, ifNumber, ifSpeed Lists interface entries by number.
System location         sysLocation     Indicates the physical location
of this network object.
System contact sysContact Lists the person to contact for this network object and tells how to contact that person.


Cheers,
Jane


R.Veenstra@Unive.nl wrote:

Hi list members

Our company has a WAN to connect four main offices and over 150 regional
sales offices. Our WAN is managed by an independend Network Carrier. In
Netview we now have a WAN composed of over 150 isolated LANs since Netview
can't see any router. We are struggeling with our WAN provider to get at
least minimal access to their routers to be able to automatically build a
decent network overview in NetView. We are trying to get rid of manually
maintained IP maps with over 150 manually configured routers (and a netmon
deamon that keeps complaining that it can see lots of remote networks but
can't figure out why it can see them).

We are trying to define what part of the MIB we need to access to have
Netview recognize the routers as routers and discover our own networks
behind it. In the end this means that our carrier requires us to fully
specify an SNMP view ourselves ;-( The routers are all of the Cisco 2900 and 3600 series and connect LANs in
the 10.0.0.0 network over MPLS. Our carrier does not allow us to find any
information over the MPLS cloud. So my question is: What is the best way of finding out what parts of the MIB are accessed
during a configuration and/or discovery poll?

With Kind regards

Rick Veenstra
ICT Specialist Midrange

        Univé Verzekeringen
        Beheer & Exploitatie
        team Infrastructuur Ontwikkeling en Beheer
        Bezoekadres:    Hanzeplein 1, Zwolle - kamer B515
        Postadres:      Postbus 607, 8000 AP  Zwolle
        Telefoon:               (038) 427 8943
        Email:          r DOT veenstra AT unive.nl



============================================

Toelichting bij dit e-mail bericht:
Dit bericht is slechts bestemd voor de geadresseerde en kan informatie bevatten die 
persoonlijk en/of vertrouwelijk is en die niet openbaar mag worden gemaakt. Indien u niet zelf 
de geadresseerde bent, wordt u erop gewezen dat verdere verspreiding, openbaarmaking of 
vermenigvuldiging van dit bericht verboden is. Indien u dit bericht per vergissing hebt 
ontvangen, verzoek ik u mij zo snel mogelijk op de hoogte te stellen en het originele bericht 
en eventuele kopieën ervan, te verwijderen. Dank voor uw medewerking. Hoe Univé het 
medium internet beschouwt als informatiedrager kunt u lezen op deze pagina. Univé kan 
niet garanderen dat een verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten 
worden overgebracht zonder inbreuk door of tussenkomst van onbevoegde derden.

============================================
De woorden [deze pagina] in de voorlaatste regel zijn de verwijzing naar de 
tekst op de website:
http://www.unive.nl/index.asp?jumpurl=/sgeneralpage.asp?strType=vast&strDescription=Unive+en+Internet




--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry@skills-1st.co.uk>.  All rights 
reserved.



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

Archive operated by Skills 1st Ltd

See also: The NetView Web