nv-l
[Top] [All Lists]

Re: [NV-L] servmon status only

To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Subject: Re: [NV-L] servmon status only
From: James Shanks <jshanks@us.ibm.com>
Date: Mon, 14 Apr 2008 14:06:13 -0400
Delivery-date: Mon, 14 Apr 2008 19:05:52 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <899acca10804141045xd6e9709sea690e834848dea3@mail.gmail.com>
List-help: <mailto:nv-l-request@lists.ca.ibm.com?subject=help>
List-id: Tivoli NetView Discussions <nv-l.lists.ca.ibm.com>
List-post: <mailto:nv-l@lists.ca.ibm.com>
List-subscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=subscribe>
List-unsubscribe: <http://lists.ca.ibm.com/mailman/listinfo/nv-l>, <mailto:nv-l-request@lists.ca.ibm.com?subject=unsubscribe>
Reply-to: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Sender: nv-l-bounces@lists.ca.ibm.com
Life is tough.  What you want to do -- ignore ping status and SNMP status
-- and only consider servmon status -- is not and never has been part of
the NetView architecture.   So there is no simple way to accomplish what
you are doing using NetView.

If you want to exclude service up/ service down traps from going to TEC
then you will have to modify the ruleset for that too.


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


                                                                           
             "Michael                                                      
             Brunelle"                                                     
             <michael.brunelle                                          To 
             @gmail.com>               "Tivoli NetView Discussions"        
             Sent by:                  <nv-l@lists.ca.ibm.com>             
             nv-l-bounces@list                                          cc 
             s.ca.ibm.com                                                  
                                                                   Subject 
                                       Re: [NV-L] servmon status only      
             04/14/2008 01:45                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
              Tivoli NetView                                               
                Discussions                                                
             <nv-l@lists.ca.ib                                             
                  m.com>                                                   
                                                                           
                                                                           




The thing is that the host is pingable and has been already discovered by
Netview, but I don't care about the ping status, I only want to know if my
servmon custom script returns a good or a bad value.
If I unmanage the node, servmon do not perform its status check on the
node...
If I modify the ruleset to avoid the node down/up events to be forwarded to
the TEC, I still have the service down/up events who gets forwarded to the
TEC when the node ping status goes down...
I have tried to manually add an object which is not having an ip address
and I have been trying to have this node checked by servmon, but it didn't
work so far.


Michael
2008/4/11 Leslie Clark <lclark@us.ibm.com>:

  A couple of thoughts on this subject.
  1) To discover the node to begin with, you either have to be able to ping
  it, or you have to add it manually, eg with the loadhosts command. You
  have probably figure that out. :)
  2) I believe that the service status check, and probably the discovery
  check as well,  will skip any nodes that have an IP status of Critical.
  I'm not sure, but perhaps they will work on nodes that have a status of
  'Unamanged'. Maybe, maybe not.
  3) You only get a Down event for the IP status when the state changes. So
  you won't get that many of them if the thing is always unpingable, even
  if it is managed.
  4) You can modify the ruleset that passes events to the TEC to exclude
  Node/Interface Down for certain nodes. As long as you are only checking
  attributes of the event, this is not expensive.
  5) If you unmanage something that is down, and it one day gets managed,
  it will probably get deleted based on the Node Down Delete interval set
  in xnmxnmpconf, so be sure to set that value very high, like 12 months or
  something.

  Cordially,

  Leslie A. Clark
  IT Services Specialist, Network Mgmt
  Information Technology Services Americas
  IBM Global Services
  (248) 552-4968 Voicemail, Fax, Pager


                                                                           
 "Michael Brunelle" <?                                                     
 michael.brunelle@gmail.com>                                               
 Sent by: nv-l-bounces@lists.ca.ibm.com                                    
                                                                      To   
                                                        nv-l@lists.ca.ib   
 04/10/2008 03:40 PM                                    m.com              
                                                                      cc   
                                                                           
               Please respond to                                 Subject   
         Tivoli NetView Discussions <?                  [NV-L] servmon     
            nv-l@lists.ca.ibm.com>                      status only        
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           







  Hi,

  I am wondering if there is a way with Netview not to monitor the ping
  status of a node, but only the status given by servmon with a custom
  script. The reason is that I don't want alerts to be forwarded to the TEC
  when the node do not answer to a ping request. Is there a way to have
  that kind of setup with Netview?


  I know that I can enable SNMP status polling for a node in the seed file,
  but the node is not configured SNMP....


  Any other suggestions?


  Michaël_______________________________________________
  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)



_______________________________________________
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)

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

Archive operated by Skills 1st Ltd

See also: The NetView Web