nv-l
[Top] [All Lists]

Re: [NV-L] NV 7.1.4 AIX--advice on ksh nmdemandpoll script--coprocessing

To: Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
Subject: Re: [NV-L] NV 7.1.4 AIX--advice on ksh nmdemandpoll script--coprocessing
From: Francois Le Hir <flehir@ca.ibm.com>
Date: Thu, 19 Oct 2006 08:52:19 -0400
Delivery-date: Thu, 19 Oct 2006 14:05:44 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <714EFC7999B7A640A33F0A9E5D889512028141A4@uscnt0495.us.deloitte.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
Hi Drew,

I would use quicktest instead of nmdemandpoll. quicktest does a status
polling exactly as netmon would do it: using either ping or snmp depending
how it is configured. nmdemandpoll takes a lot longer because of all the
configuration polling it does.

quicktest has to be executed for each node. For each interface of the node,
it will tell you either "Interface xx.xx.xx.xx(en9) is UP Responded to
ping" or "Interface xx.xx.xx.xx is Up: Admin Status=Up Oper Status=Up"

Salutations, / Regards,

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


                                                                           
             "Van Order, Drew                                              
             \(US -                                                        
             Hermitage\)"                                               To 
             <dvanorder@deloit         "Tivoli NetView Discussions"        
             te.com>                   <nv-l@lists.ca.ibm.com>             
             Sent by:                                                   cc 
             nv-l-bounces@list                                             
             s.ca.ibm.com                                          Subject 
                                       [NV-L] NV 7.1.4 AIX--advice on ksh  
                                       nmdemandpoll script--coprocessing   
             10/19/2006 08:13                                              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
              Tivoli NetView                                               
                Discussions                                                
             <nv-l@lists.ca.ib                                             
                  m.com>                                                   
                                                                           
                                                                           




Hi all,


Our DNOC needs a report that shows what IP addresses are managed via SNMP
query versus ping. I searched the archives and it appears one can't get
this report using nvdbformat--isSNMPSupported is not an accurate indicator.
So, I'm getting the list of IP's that match isSNMPSupported=TRUE from
nvdbformat, then feeding the list into `ndmdemandpoll $hostname |grep "Get
SNMP status"`. This will do the job, but we all know nmdemandpoll kills CPU
if it takes any time at all to run. I have 1500 addresses to cycle through.


So, I figure I can kill nmdemandpoll if it's going to take longer than 15
seconds to finish, log the IP address that needed to be killed, then go
back to the loop. No problem, except I'm a novice ksh scripter, and having
trouble with co-processes (required to watch the nmdemandpoll PID because
nothing will occur until nmdemandpoll finishes, right?). If someone can
help me with the logic, I'll post the whole smash for everyone to use when
it's finished.


This works fine, just takes forever, and sends uptime values skyward. It
sets off NetIQ alerts for CPU utilization.


# Read in IP address list from NVout.report
# nv_getSNMPquerystatus.sh < NVout.report


while read ipAddress
do
       nmdemandpoll $ipAddress | grep "Get SNMP status"
       if [[ $? -eq 0 ]]
       then
       echo "$ipAddress is currently monitored using SNMP query"
       else
       echo "$ipAddress is currently NOT monitored using SNMP query"
       fi
done


Many thanks in advance to anyone with advice on how to finish this one off.
--Drew






Drew Van Order
Information Technology Services
Deloitte Services LP
Tel: +1 615 882 7836
www.deloitte.com




This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.
If you are not the intended recipient, you should delete this message.

Any disclosure, copying, or distribution of this message, or the taking of
any action based on it, is strictly prohibited. [v.E.1]
_______________________________________________
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