RE: [nv-l] origin=212.252.18.0

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

$AGENT_ADDR will usually give you the hostname of the trap sender.  Try it and see.   

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

Brian Kraftchick <Brian.Kraftchick@odfl.com> 09/03/2003 09:24 AM

To:        "NVList (E-mail)" <nv-l@lists.tivoli.com>         cc:                 Subject:        RE: [nv-l] origin=212.252.18.0

James,
 
I wanted to take a minute to thank you for the info....that is the first solid explanation that I've heard.  And the first time that it's been stated that it was at least a known issue.  The reason that I pushed the issue as far as I did was that I had a very necessary reason to use the value of the origin slot to filter Event Consoles in TEC.  With what you've suggested....using the $AGENT_ADDR in it's place....what will that populate the origin slot with then....meaning that if I have a device (Contivity Extranet Switch) with multiple interfaces...basically a router....that produces a trap to NetView...that then produces an Event in TEC....what would expect the value of $AGENT_ADDR to be ?  Maybe we could still benefit from using the origin slot.
 
Thanks !!!
Brian
-----Original Message-----
From: James Shanks [mailto:jshanks@us.ibm.com]
Sent: Wednesday, September 03, 2003 9:19 AM
To: nv-l@lists.tivoli.com
Subject: RE: [nv-l] origin=212.252.18.0


The origin field from the NetView for Windows TEC adapter, when mapped to  the default value of $SOURCE_ADDR in the tecad_nv6k.cds, is broken. 
It has been for some time. 

There is an APAR for this, PJ29055, and it will be fixed in 7.1.4.  I don't know to whom in Level 3 you consulted, Brian, but it was not me, and such issues are usually mine.    I am sorry that your call was not properly routed nor resolved.   

As a workaround, I would alter your default mapping to  $AGENT_ADDR, which is a better match in most cases, until a fix is available.  In those cases where $AGENT_ADDR does not work, you will have to live without an origin value.   It may that in the future the 7.1.4 fix will be ported retroactively to the next FixPack for 7.1.3, but that remains to be seen.  For now you will just have to accept the fact that it is broken and work around it. 

Hope this helps

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

Brian Kraftchick <Brian.Kraftchick@odfl.com> 09/03/2003 08:15 AM

To:        "NVList (E-mail)" <nv-l@lists.tivoli.com>        cc:                Subject:        RE: [nv-l] origin=212.252.18.0

Lucian,

I have had the exact same issue since our installation of Netview by IBM
Global Services, and it has yet been resolved.  We have a different IP
address show up than yours, but still it has nothing to do with our network,
nor any configured device on our network.  I have actually taken this all
the way to Level 3 with Tech Support, but still no solution.  We were able
to determine that it does come directly from NetView....when we check the
TEC reception log...the IP address is already there, so we know that TEC
isn't generating it.  Something within TEC is....but as I said, we still
don't have any solution whatsoever....please let me know if you find
anything out.

Brian

-----Original Message-----
From: tivoli [mailto:tivoli@bu.brauunion.ro]
Sent: Wednesday, September 03, 2003 6:01 AM
Cc: Netview List
Subject: [nv-l] origin=212.252.18.0


hi there list!

I have some events from NetView that appear in TEC with origin 
212.252.18.0  
what this could be? (I have a second NIC on netview server without an 
address... )

thanks
Lucian




-