Re: [NV-L] servmon discovery problem

[James Shanks <jshanks@us.ibm.com>]

I'm not the sermon expert but I doubt that it is as dynamic as you want it
to be.  My guess is that because the 3ComWEB smartset exists and is
populated, that servmon thinks he has no discovery to do and is only
monitoring.  That's what you are seeing in the log, isn't it?

My advice would be to change the conf to create a new smartset or do
something like this
1. ovstop servmon
2. nvUtil D 3ComWEB  (which is your service smartset)
3. ovstop / ovstart nvcold  (make him re-evaluate all smartsets)
4. ovstart servmon


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp


                                                                           
             Jeff Fitzwater                                                
             <jfitz@Princeton.                                             
             EDU>                                                       To 
             Sent by:                  nv-l@lists.ca.ibm.com               
             nv-l-bounces@list                                          cc 
             s.ca.ibm.com                                                  
                                                                   Subject 
                                       [NV-L] servmon discovery problem    
             04/15/2008 03:39                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
              Tivoli NetView                                               
                Discussions                                                
             <nv-l@lists.ca.ib                                             
                  m.com>                                                   
                                                                           
                                                                           




7.1.5 FP1
Sol 9

I have  servmon running and am using it to monitor port 80 on an
existing SMARTSET called OLD3Com and place the result in new smartset
called 3ComWEB.
The nodes in the smartset now have field called "isport80"

So it has been working fine and created the smartset and monitors the
set every 5 min.


PROBLEM

I needed  change the SMARTSET that it looks at for discovery, so I
edited the servmon.conf and changed the discovery smartset name to
NEW3Com.   This also is an existing smartset but with different 3Com
devices that are not monitored yet for port 80.


I save the file and restarted servmon but it never rediscovers the new
nodes in the new smartset.  It just adds the existing ones that have
field "isport80" to the new smartset.


I have enabled debuging for servmon but it is not clear from the log
that anything is broken.   I just see it polling the existing nodes
from old discovery.


The snmpconf has the SERVICE DISCOVERY interval set to 12 hours and
SERVICE DOWN set to 7 days


I even restarted netview with no change.



Stumped??


Thanks for any help in advance.




Jeff Fitzwater
OIT Network Systems
Princeton University
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)


_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)