Good information, a clarification may be in order.....
1) Create a new icon inside the node icon of the relevant devices. I
like to use the APM and MLM to do this as you can then use a SmartSet to
specify which nodes get the new icon.
===> When you say "create an icon" do you mean "add an object" from the GUI? We
do not have MLM and I'm not sure what APM would be used for here. Can you
expand a little?
The MIB variable you use in the
APM setup is a dummy - I generally use something like sysuptime > 1.
===> This is the part that I'm not sure what you mean. I have no APM experience
so I will go read the book a bit.
2) Customise your specific TRAP so that it generates a new NetView
Change Status TRAP (58916871) on the Selection Name that you create by
catenating the Node name from the original TRAP with the new icon name
that you supplied when you created the icon with APM. For example, if
your original TRAP came from node fred and your APM icon is called
myService, your Selection Name needs to be fred:myService. I generally
change status to User1 or User2, depending on whether I want the new
icon status to propagate up to the Node level.
===> I assume you use the SNMPTRAP command to do this? Another new thing for me
to work with but it's pretty straightforward.
3) This way, you get an icon that represents your service, that changes
colour and, if you use User2 as your "bad news on the service colour",
you can get a marginal colour on your node icon, which seems an accurate
representation to me. Of course, if the interface of the node also goes
down, then the whole node will go Critical.
Does that help?
Cheers,
Jane
Barr, Scott wrote:
> Greetings listers
>
> Netview V7.1.3
> Solaris 2.8
>
> We currently receive and process traps froma cisco content switch.
> They are syslog traps that contain only the name of the service and
> the state:
>
>
> Web Application Event: Service Transition -* **Service:lexlw5se
> State:alive* @ Tue Apr 22 03:33:06 2003
>
> The section in red is the part that is stripped out of the syslog trap
> and used for notification. What I want to do however, is have a "node"
> in NetView that turns red when the service is down and then green
> again when the service is active. I have a perl script that can
> execute the necessary functions but I'm unclear on what those
> functions would be.
>
> My original thought was to add a node to the map with that service
> name and then use the "event" command to mark it down but that does
> not work (I think because status events have to come through netmon
> and the event command really doesn't change the status on a node.)
>
> In my environment I don't need to use nvsniffer or any other tool to
> check the status, I merely need to handle the incoming traps and
> change the status of the "node" based on the trap. Anyone have
> recommendations on how to go about this?
>
> Scott Barr
>
> CSG Systems Inc.
>
> Network Systems Engineer
>
> Phone: 402-431-7939
>
> Fax: 402-431-7413
>
> Mail: scott_barr@csgsystems.com
>
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2003 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|