nv-l
[Top] [All Lists]

Re: [nv-l] Simulating node/interface up/down events

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Simulating node/interface up/down events
From: Jane Curry <jane.curry@skills-1st.co.uk>
Date: Wed, 21 Jan 2004 17:17:27 +0000
Delivery-date: Wed, 21 Jan 2004 17:44:50 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <F9D492E13AF8D411B1B100B0D079F82908256022@radbuksdnt15.northwest.barclays.co.uk>
References: <F9D492E13AF8D411B1B100B0D079F82908256022@radbuksdnt15.northwest.barclays.co.uk>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Colin,
I'm a little confused by the trap generation harness script you have supplied as it doesn't seem to have enough parameters.Both Node up/down events and Interface up/down events should both have 8 varbinds.

The next question is whether your NetView can really "see" any of these nodes / interfaces? I assume not? Is this just a TRAP system that forwards events to TEC for correlation? Again, you will need all 8 varbinds on the TRAP as several of them (especially 7 and 8) are mapped into attributes on the appropriate TEC classes. If you are not forwarding to TEC but simply using NetView, how can you tell that an interface belongs on a Node??

Check the NV 7.1.3 Release Notes for info on varbinds 7 and 8 (page 13).

Cheers,
Jane

colin.walls@barclays.co.uk wrote:

We have outsourced our network to BT, but still wish to retain some elements
of network management so that we can correlate network with system and
application events.

BT have been sending us node up/down events for some while now, we import
these into Netview with no difficulty. We now want them to send us interface
up/down events. We thought that this would simply mean modifying their
script, which sends an SNMP trap, to use specific traps of 58916866/7
instead of 58916864/5. What actually happens is that NV sees parameters with
the node up/down events, but no parameters with interface up/down events.

Stripping the whole thing down we end up with the following shell script
fragment.

snmptrap nvserv101 \
 .1.3.6.1.4.1.2.6.3.1 \
 $AGENT_IP \
 6 $SPECIFIC_TRAP \
 0 \
 .1.3.6.1.4.1.2.6.3.1.1.2.0 Integer 1 \
 .1.3.6.1.4.1.2.6.3.1.1.3.0 Octetstring $AGENT \
 .1.3.6.1.4.1.2.6.3.1.1.4.0 Octetstring $DESCRIPTION

Adding data and database parameters doesn't make any difference. Any clues
as to what we are doing wrong? We are running NV 7.1.3.

--
Dr. Colin Walls
Project Services
Enable
Telephone: 01565 613705
Email: Colin.Walls@Barclays.co.uk

Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Although the Barclays Group operates anti-virus programmes, it does not
accept responsibility for any damage whatsoever that is caused by
viruses being passed.  Any views or opinions presented are solely those
of the author and do not necessarily represent those of the Barclays
Group.  Replies to this email may be monitored by the Barclays Group
for operational or business reasons.




--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry@skills-1st.co.uk>.  All rights 
reserved.



<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web