RE: [nv-l] Events Workspace in NV 7.1.3

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

Let's answer your last question first.
>- Should I include
my ruleset names in the ESE.automation file?
NO!  Absolutely not.  Rulesets
in ESE.automation do not affect the display.  They are for background
processing only, and if you put your ruleset with it's Forward node in
ESE.automation, you will cause a performance problem that will eventually
hang your entire NetView system.

Your first question requires clarification,
because it matters where the files are.  It would seem that you and
your client do not have the same options set in /usr/OV/app-defaults/Nvevents.
 Does he have his own Nvevents file?  Do you?   If by "client'
you mean that he is on a real NetView client machine (not telnet'd to the
server) then you have to edit the Nvevents Xdefaults file there.

Basically your user needs to have his
own copy of /usr/OV/app-defaults/Nvevents  or else the global default
must be set so that loadEnvOnInit=TRUE is set.  And then the next
time the user logs and starts events, he must open all the windows he wants
to reopen automatically, and then use Options on the main event window
to save the environment.  Only then will it reload automatically

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

Meyos Yemveng <yemveng@yahoo.ca>
Sent by: owner-nv-l@lists.us.ibm.com

04/07/2004 10:19 AM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	RE: [nv-l] Events Workspace in NV 7.1.3

NV 7.1.3 FP2, SOLARIS
Thanks William, James and Jane ..
I did succesfully create a Dynamic Workspace displaying
Events and Traps from a given type of devices using the Ruleset.
 
I have name one Workspace "CISCO_EVENTS"
But now, when Closing and re-opening the Clients GUI,
I notice the following:
1- Some Workspace Do not re-open with their original name
(CISCO_EVENTS for Example), instead the have the name "events"
at the end you have more than one "events" workspace
beside the default "events" workspace
 
2- Should I include my ruleset names in the ESE.automation
file?
 


"Stringfellow, William" <William.Stringfellow@bankofamerica.com>
wrote:
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
EDS - Bank of America Account Team
Network Management Support
CA4-704-02-03
2000 Clayton Road, Building D
Concord, CA 94520

Office:     925.692.7283
Fax:        925.675.1763
Email:     william.stringfellow@eds.com
Cell:       925.765.2648

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Meyos Yemveng
Sent: Tuesday, April 06, 2004 8:04 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Events Workspace in NV 7.1.3

Thanks Jane,
I am having a problem about the event matching configuration.
 
1- I want to create a workspace for a specific device type with sysObjectID = 1.3.6.1.4.1.xx.yy.zz for example
2- I want All events (Treshold, Node UP, Node Down, etc ..) and All Traps from that Device type to be displayed on that Workspace
 
3- What Attributes represents  the sysObjectID? is it the EntrepriseID?
 
4- What about when  you want to display events from all Devices from the same vendor, can youu use "Greater or equal to" selection?
 
5- Any suggestions
 
6- any *.rs file sample would help.
 
 
 


Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"

---

Post your free ad now! Yahoo!
Canada Personals

Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"

---

Post your free ad now! Yahoo!
Canada Personals