| To: | nv-l@lists.us.ibm.com | 
|---|---|
| Subject: | RE: [nv-l] Events Workspace in NV 7.1.3 | 
| From: | "Stringfellow, William" <William.Stringfellow@bankofamerica.com> | 
| Date: | Tue, 06 Apr 2004 11:27:44 -0700 | 
| Delivery-date: | Wed, 07 Apr 2004 00:20:34 +0100 | 
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk | 
| Reply-to: | nv-l@lists.us.ibm.com | 
| Sender: | owner-nv-l@lists.us.ibm.com | 
| Thread-index: | AcQb6NSd0emSSPa0TkG011E7o0PmlQAGYf4g | 
| Thread-topic: | [nv-l] Events Workspace in NV 7.1.3 | 
| Meyos,     All of this can be done with a smartset.  If you use Cisco as 
an example, the basic breakdown of their devices is: Cisco = 
1.3.6.1.4.1.9 routers = 
1.3.6.1.4.1.9.1 switches = 
1.3.6.1.4.1.9.5     Because of acquisitions, there are other OIDs 
that belong to them, but you can expand this example to include whatever you 
want Question 1 
-  Make a  smartset who's membership rule is sysObjectId = <your 
desired targets OID> Question 2 - 
Make a ruleset that blocks all events except those coming from members of your 
smartset in #1.  Then when you open your event window, create a dynamic 
workspace that uses this ruleset.  Or use this ruleset as the default for 
the event window itself.  Jane's last message told you how to save those 
for your customer. Question 3 - 
The sysObjectId and the EnterpriseId are related but different.  If you 
look at my Cisco example, the OID that stops at 4.1.9 is the Enterprise Id, and 
as you can see, they add subsets to it by adding additional numbers, 4.1.9.1 for 
routers, 4.1.9.5 for switches.  Then they add additional numbers to each of 
these to identify specific router and switch types.  For examples look in 
/usr/OV/conf/C/oid_to_sym file Here are some 
examples.  These are sysObjectIds. 1.3.6.1.4.1.9.1.122:Cisco 
Router:cisco-Rtr3620Family 1.3.6.1.4.1.9.1.123:Cisco Router:CPA3600 # cpa3620 1.3.6.1.4.1.9.1.124:Cisco Router:CPA3600 # cpa3640 1.3.6.1.4.1.9.1.125:Cisco Router:cisco-C7200 1.3.6.1.4.1.9.1.126:Cisco Router:cisco-Rtr700Family 1.3.6.1.4.1.9.1.127:Cisco Router:cisco-Rtr700Family 1.3.6.1.4.1.9.1.128:Cisco Router:cisco-Rtr700Family Question 4 - Just make your smartset stop at the Enterprise 
id.  If a vendor uses more then 1 Enterprise id, just include all of them 
in the qualifying rule for the smartset.  Again in the case of Cisco, you 
would just say  "anything whose sysObjectId included 1.3.6.1.4.1.9 AND 
<Any Other sysObjectId They Own>"     Hope this helps, Good 
luck!         
Bill Bill Stringfellow 
 | 
| <Prev in Thread] | Current Thread | [Next in Thread> | 
|---|---|---|
| 
 | ||
| Previous by Date: | Re: [nv-l] Events Workspace in NV 7.1.3, James Shanks | 
|---|---|
| Next by Date: | [nv-l] Holger Scheibe/Germany/IBM is out of the office., Holger Scheibe | 
| Previous by Thread: | Re: [nv-l] Events Workspace in NV 7.1.3, James Shanks | 
| Next by Thread: | RE: [nv-l] Events Workspace in NV 7.1.3, Meyos Yemveng | 
| Indexes: | [Date] [Thread] [Top] [All Lists] | 
Archive operated by Skills 1st Ltd
See also: The NetView Web