nv-l

RE: [nv-l] question about modifying objects in netview 7.1.3

2004-09-21 13:08:12
Subject: RE: [nv-l] question about modifying objects in netview 7.1.3
From: Francois Le Hir <flehir AT ca.ibm DOT com>
To: nv-l AT lists.us.ibm DOT com
Date: Tue, 21 Sep 2004 12:57:24 -0400


talking about changing status of objects ....
is the a reason why nvmaputil.sh doesn't allow managing/unmanaging a subnet
?
is there any easy way to do it ? or is the API the only solution ?

Thanks,
Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145


                                                                           
             James Shanks                                                  
             <jshanks AT us DOT ibm.c                                           
  
             om>                                                        To 
             Sent by:                  nv-l AT lists.us.ibm DOT com             
  
             [email protected]                                          cc 
             us.ibm.com                                                    
                                                                   Subject 
                                       RE: [nv-l] question about modifying 
             09/21/2004 12:41          objects in netview 7.1.3            
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
                   nv-l                                                    
                                                                           
                                                                           





or is there an easier way?

Have you tried adjusting the time out and retry parameters for these nodes
in xnmsnmpconf?

If netmon polls a node and issues an Interface Down/ Node Down event, and
then the operator does a demand poll and the device is changed to up, the
reason is that the node did not respond in a timely fashion the first time.
In both cases it is netmon which did the actual polling.  Your operator
just told him to do it again. So the source of the problem is that the node
doesn't respond like it is expected to.   And you can adjust the time
netmon is willing to wait and the number or (re)tries he is willing to  do
before he issues the Interface Down /Node Down to take care of that.   No
code required.

Generally speaking it is a very bad idea to try to change the status on a
node netmon is managing.  You are more likely to cause more harm than good.


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group