nv-l
[Top] [All Lists]

Re: [nv-l] discovery problems

To: Bill Evans <wvevans@prodigy.net>
Subject: Re: [nv-l] discovery problems
From: jason.ctr.alburger@faa.gov
Date: Thu, 3 Apr 2003 15:48:20 -0500
Cc: nv-l@lists.tivoli.com
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Fri, 04 Apr 2003 08:17:21 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm
Bill,

Thanks for the help...after your suggestions I checked a few things.
There is not a negative entry in the seed file to block discovery.  I also
checked to make sure the comm. strings match - they do.  I was able to view
MIBs on the box with the MIB browser.

I added the box with "loadhosts" and it popped up, but was immediately
deleted from the map upon a "nmdemandpoll"

Any further suggestions would be appreciated!!



                                                                                
                                                       
                      Bill Evans                                                
                                                       
                      <wvevans@prodigy.        To:       Jason CTR 
Alburger/ACT/CNTR/FAA@FAA                                           
                      net>                     cc:       nv-l@lists.tivoli.com  
                                                       
                                               Subject:  Re: [nv-l] discovery 
problems                                                 
                      04/03/2003 01:28                                          
                                                       
                      PM                                                        
                                                       
                                                                                
                                                       
                                                                                
                                                       




You're finding the object.  You can't get it into the database as a fully
discovered object.  Possible:
      You have a negative entry in the seed file blocking its discovery.
      You know its community name for snmpwalk but NetView doesn't.
Possible debug actions:
      Try using the NetView MIB Browser to look at the device.  If snmpwalk
      works and the MIB browser doesn't it's probably a community name
      problem.
      Do a manual demand poll on the device; you may need to do loadhosts
      first to force it into the database as more than a hint.
No guarantee if these will work.  They're just the obvious ones that get
overlooked.  I'm also suspicious of your name resolution since you're
getting TWO hints for each device; one by name and one by address.  Check
out the resolution is good both forward and backward.

Bill Evans, ESM Consultant


jason.ctr.alburger@faa.gov wrote:
      Scott,

      Most of these I tried already.  I was afraid that old interfaces
      could be a
      problem, so I tried  /usr/OV/bin/ovwdbdmap -d <object number>.  I
      then
      pinged the boxes and got the same results.

      "ovtopofix -A" deleted everything about the 2 nodes (these object
      numbers
      are diff. now, due to the nodes being deleted and re-added multiple
      times)

      deleting object 2531 (HINT).
      deleting object 2526 (HINT).
      2 objects removed from ovwdb (2 hints, 0 old hints, 0 still valid)
      deleting object 2527 (INCOMPLETE NODE).
      deleting object 2532 (INCOMPLETE NODE).
      2 node objects removed from ovwdb.

      But, again, the same results after pinging to 2 boxes.

      Is there anything else to try?

      Thanks in advance!




                            "Barr, Scott"

                            <Scott_Barr@csgsy        To:       Jason CTR
      Alburger/ACT/CNTR/FAA@FAA, <nv-l@lists.tivoli.com>
                            stems.com>               cc:

                                                     Subject:  RE: [nv-l]
      discovery problems
                            04/03/2003 11:01

                            AM







      Make sure using ovobjprint -s | grep <interface address> that you do
      not
      have old interfaces in the discovery that are preventing the
      interfaces
      from being added properly. You might have to use the unsupported
      utility
      ovwdbdmap to delete the interface objects OR try doing an ovtopofix
      -A to
      clear 'em out.

      -----Original Message-----
      From: jason.ctr.alburger@faa.gov [mailto:jason.ctr.alburger@faa.gov]
      Sent: Thursday, April 03, 2003 9:40 AM
      To: nv-l@lists.tivoli.com
      Subject: [nv-l] discovery problems


      Hello list,

      I am running AIX 4.3.3, Netview 5.1

      Onto our one of our sub-networks, I added 2 new boxes (compaq Tru64
      V4.0G)
      on which I have installed net-snmp.  Everything else on this
      subnetwork has
      been discovered once the subnetwork is managed and the boxes are
      pinged (or
      if I just wait long enough) --- except for these 2 boxes.  I can
      snmpwalk,
      snmpget, snmpset, etc... to these 2 boxes.  When I pinged these 2
      boxes,
      this was inserted in the object database:

      OBJECT: 1014

          FIELD ID    FIELD NAME          FIELD VALUE
          10          Selection Name
      "Interface:XXX.XXX.XX.221"
          17          IP Address                      "XXX.XXX.XX.221"


      OBJECT: 1015

          FIELD ID    FIELD NAME          FIELD VALUE
          10          Selection Name           "box1"
          11          IP Hostname                 "box1"

      OBJECT: 1016

          FIELD ID    FIELD NAME          FIELD VALUE
          10          Selection Name
      "Interface:XXX.XXX.XX.222"
          17          IP Address                      "XXX.XXX.XX.222"


      OBJECT: 1017

          FIELD ID    FIELD NAME          FIELD VALUE
          10          Selection Name           "box2"
          11          IP Hostname                 "box2"

      box1's IP is XXX.XXX.XX.221 and box2's IP is XXX.XXX.XX.222.   This
      shows
      me that Netview knows about these 2 boxes, but is not managing them.
      Can
      anybody tell me why these 2 nodes might not be managed by Netview?

      Thanks in advance.



      ---------------------------------------------------------------------
      To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
      For additional commands, e-mail: nv-l-help@lists.tivoli.com

      *NOTE*
      This is not an Offical Tivoli Support forum. If you need immediate
      assistance from Tivoli please call the IBM Tivoli Software Group
      help line at 1-800-TIVOLI8(848-6548)







      ---------------------------------------------------------------------
      To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
      For additional commands, e-mail: nv-l-help@lists.tivoli.com

      *NOTE*
      This is not an Offical Tivoli Support forum. If you need immediate
      assistance from Tivoli please call the IBM Tivoli Software Group
      help line at 1-800-TIVOLI8(848-6548)









---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)


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

Archive operated by Skills 1st Ltd

See also: The NetView Web