To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Smart sets question |
From: | Leslie Clark <lclark@us.ibm.com> |
Date: | Tue, 25 Oct 2005 00:21:57 -0400 |
Delivery-date: | Tue, 25 Oct 2005 05:22:25 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OFC95D89C1.1024CE92-ON852570A4.007DCEE8-852570A4.007E5CF0@us.ibm.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
I could not come up with the right search words to find the description of this in the archives. So here it is again. This is a pretty good training exercise. You have to learn about each of these capabilities to implement it. The 'how to' for each of this is in the manuals as well as the archives of this list. 1) Define one or more new fields in your own file in /usr/OV/fields/C. Include one called something like New_node. (Run ovw -fields after adding them.) 2) Create a script (like newnode_update.sh) that can set that field to True, or as I prefer, a timestamp. It can use 'nvdbimport' to set the value. 3) Create a ruleset that listens for the Node Added event, and calls that newnode_update.sh script as an Action. 4) Define a Smartset based on the value of that field. If it is not OK (or False), then it is a new node. 5) Create a second script (like newnode_ok.sh) that can set the field to OK (or False). 6) Create a little script in /usr/OV/reports/C to call the clearing script. That will be on the menu Monitor...Reports..Site-Provided. Now you can select nodes in the smartset and OK them, and they will leave that smartset. You will end up with a smartset that shows things that were recently discovered. When you are satisfied with the node, you can use your menu function (Monitor...Reports..Site Provided) function to call the script that clears the field, and it will leave the smartset. Once you have this working, you can extend the newnode_update.sh script to populate more custom fields on nodes as they are discovered. It becomes analogous to a custom demandpoll. You can add fields for anything that you can look up at discovery time, based on what is already known when the node is discovered. It can use nvUtil n <nodename> '%field%,%field,%field%' to retrieve the existing fields. I like to pick up the sysname for all snmp-capable devices, since Netview only stores it for routers. I like to pick up the serial number, model, and code version of certain equipment. If you do that, you should make sure the script can tell whether it was called from the ruleset or operator-initiated, so it can skip setting the newnode field when it is operator initiated. To make it capable of being operator-initiated rather then just event-initiated, add it to the Reports menu. Cordially, Leslie A. Clark IT Services Specialist, Network Mgmt Information Technology Services Americas IBM Global Services (248) 552-4968 Voicemail, Fax, Pager
I do this with some custom work that leverages several of the integration points of Netview. Jane, is that described somewhere on the group website? Cordially, Leslie A. Clark IT Services Specialist, Network Mgmt Information Technology Services Americas IBM Global Services (248) 552-4968 Voicemail, Fax, Pager
Hi List- Solaris 8 Netview 7.1.3 Is there a means to have interfaces/nodes that are discovered by Netview on the network go into a smartset by default as say a new node. What I am after is if a new device is connected to the network I want to see it and move it into a smartset that is separated from the rest. Even if it is say a Cisco device that I have a smartset for, I would still like to see it in the "New Nodes" smartset? Regards, Mike Noonkesser Office 651-662-1012 Fax 651-662-2279 ---------------------------- Important news about email communications: If our business rules identify sensitive information, you will receive a ZixMail Secure Message with a link to view your message. First-time recipients will be asked to create a password before they are granted access. To learn more about ZixMail, ZixCorp Secure Email Message Center, and other ZixCorp offerings, please go to http://userawareness.zixcorp.com/secure4/index.php ---------------------------- The information contained in this communication may be confidential, and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. Unencrypted, unauthenticated Internet e-mail is inherently insecure. Internet messages may be corrupted or incomplete, or may incorrectly identify the sender. |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] some daemons not running with a "never run", Brett |
---|---|
Next by Date: | Re: [nv-l] some daemons not running with a "never run", Paul Stroud |
Previous by Thread: | Re: [nv-l] Smart sets question, Leslie Clark |
Next by Thread: | Re: [nv-l] Smart sets question, Michael_Noonkesser |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web