RE: [nv-l] NVATTR

I am not certain why this should surprise you exactly. A valid trap has to have the sending agent's IP Address in it.

So when you put in a hostname which cannot be resolved, the event command code uses it's own address as a default. Would you prefer a null address, like 0.0.0.0, or 127.0.0.1 as a default instead? Using the box address allows everything to work as expected when the event is received, since the event command was designed primarily as a test tool for the flow of events from NetView daemons to trapd, not as a general user workhorse for issuing traps. That's what snmptrap is for. If you need more control over what's put in the final event, then I'd advise an snmptrap script. It's a lot easier to control all the trap fields that way.

What's surprising to me is that you have objects in the database with unresolvable hostnames. "event" isn't coded to look in the database. It does the same old gethostbyname calls that the rest of the product uses. It mimics netmon.

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

"Bursik, Scott {PBSG}" <Scott.Bursik AT pbsg DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com

01/29/2004 03:23 PM
Please respond to nv-l

To: "'nv-l AT lists.us.ibm DOT com'" <nv-l AT lists.us.ibm DOT com>
cc:
Subject: RE: [nv-l] NVATTR_#

Thanks for that tip on getting the NVATTR variables.

Here is a perfect example of what is happening here.

In the ruleset I am using the following command in the action block:
set | grep NV >> logfile

I then issue the following command with 2 different nodes. One is resolvable
in DNS and the other is not, but both objects are in the NV database so this
is not bogus information.

event -e NDWN_EV -h Q305271.corp.quakeroats.com (Not Resolvable)
event -e NDWN_EV -h pbsxst00007.fritolay.pvt (Resolvable)

This looks good:

ENV=''
NVA=pbsxst00007.fritolay.pvt
NVATTR_1=5
NVATTR_2='pbsxst00007\.fritolay\.pvt'
NVATTR_3='Node Down'
NVATTR_4=''
NVATTR_5=topo_db
NVATTR_6=3
NVATTR_7=d
NVATTR_8=4
NVATTR_COUNT=8
NVC=xxxxxx
NVCAT=3
NVE=1.3.6.1.4.1.2.6.3.1
NVENVIRONMENT=7.1
NVG=6
NVS=58916865
NVSEV=4
NVSRC=d
NVT='2004/01/29 13:57:21'
_=NVA

This does NOT:

ENV=''
NVA=pbsxsn00001.fritolay.pvt (NetView server name)
NVATTR_1=5
NVATTR_2='Q305271\.corp\.quakeroats\.com' (Actual Host Name)
NVATTR_3='Node Down'
NVATTR_4=''
NVATTR_5=topo_db
NVATTR_6=3
NVATTR_7=d
NVATTR_8=4
NVATTR_COUNT=8
NVC=xxxxxx
NVCAT=3
NVE=1.3.6.1.4.1.2.6.3.1
NVENVIRONMENT=7.1
NVG=6
NVS=58916865
NVSEV=4
NVSRC=d
NVT='2004/01/29 13:57:24'
_=NVA

Scott Bursik
Enterprise Systems Management
PepsiCo Business Solutions Group
(972) 963-1400
scott.bursik AT pbsg DOT com

-----Original Message-----
From: Francois Le Hir [mailto:flehir AT ca.ibm DOT com]
Sent: Thursday, January 29, 2004 1:03 PM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] NVATTR_#

did you try the command: set >> logfile.log ?
or maybe set | grep "NVATTR" >> logfile.log

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 205 6695

"Bursik, Scott
{PBSG}"
<Scott.Bursik@pbs To
g.com> "Nv-L (nv-l AT lists.us.ibm DOT com)"
Sent by: <nv-l AT lists.us.ibm DOT com>
owner-nv-l@lists. cc
us.ibm.com
Subject
[nv-l] NVATTR_#
01/29/2004 01:48
PM

Please respond to
nv-l

NetView 7.1.3 AIX 4.3.3

Is there a way via the ruleset using the Action block to send ALL of the
varbinds (1-50) to a log file without having to do something like

echo "NVATTR_2=$NVATTR_2" "NVATTR_3=$NVATTR_3" >> logfile.log

and so on?

Thanks,

Scott Bursik
PBSG