Re: [NV-L] NV sending FQDN to TEC in IP address field ???

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

TEC forwarding is not a simple thing, and it is accomplished in radically different ways on Windows and UNIX.

On UNIX, the event formatting parameters which are not defaulted are specified in trapd.conf, which is read by the internal adapter code in nvserverd.

On Windows, TEC event formatting parameters are given in the tecad_nv6k.cds, even the default ones, which is read by the tecad_nv6k daemon. That daemon is based on code from the TEC OpenView adapter. It couldn't be more different from UNIX's nvserverd and still be a TEC adaptor, which is why it is important to know what platform you are on.

Without looking deep into code, I'd wager that the tecad adapter is using gethostbyname and gethostbyaddr to find that origin address, or possibly just to confirm it, and if he cannot get the same result both ways that may be why you see the FQDN. So I would look to your name resolution, forward and especially backward.

If that doesn't do it, then you'd have to talk to Support.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
Michael D Schleif <mds@helices.org>

Michael D Schleif <mds@helices.org>
Sent by: nv-l-bounces@lists.ca.ibm.com

03/20/2007 10:54 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	nv-l@lists.ca.ibm.com
cc
Subject	Re: [NV-L] NV sending FQDN to TEC in IP address field ???

* James Shanks <jshanks@us.ibm.com> [2007:03:20:07:53:48-0400] scribed:
> Offhand, I have no idea.  What platform?  What level of NetView code? 

MS Windows Server 2003; SP1
NV v7.1.4; FP 4


> Does this occur for all traps regarding this device or just some of
> them? 

That is difficult, and problematic, to answer definitively.  When we
first setup this NV/TEC integration, we saw some of this; and we have
TEC rules that log this behaviour.  I have been meaning to chase this
down, and fix it for quite awhile; but, NOW our NOC users have
complained about this, and I need to resolve it.

Clearly, most of these nodes DO repeat this errant behaviour.  Whether
or not they ever send properly configured events to TEC, I cannot say ;<


> NetView traps or vendor traps?

Netview.

Notice, these SAME Netview events ARE properly formatted for >99% of
nodes.


> Any formatting differences in trapd.conf (UNIX) or tecad_nv6k.cds
> (Windows).

Differences between what and what?

Thank you, for your participation in this matter.


> James Shanks
> Level 3 Support  for Tivoli NetView for UNIX and Windows
> Network Availability Management
> Network Management - Development
> Tivoli Software, IBM Corp
> 
> 
> 
> Michael D Schleif <mds@helices.org> 
> Sent by: nv-l-bounces@lists.ca.ibm.com
> 03/19/2007 10:41 AM
> Please respond to
> Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>
> 
> 
> To nv-l mailing list <nv-l@lists.ca.ibm.com>
> 
> Subject [NV-L] NV sending FQDN to TEC in IP address field ???
> 
> [1] What can cause Netview to send either FQDN, or Selection Name in the
> origin (IP address) slot, when forwarding events to TEC?
> 
> [2] Out of ~9,000 nodes, this anomaly occurs <1% of nodes.
> 
> [3] How can we correct this condition?
> 
> 
> Examples:
> =========
> 
> [A]
>     d:\>ovobjprint -s host.example.org
>                     OBJECTID                SELECTION NAME
> 
>     OBJECT: 901159
> 
>             FIELD ID        FIELD NAME                      FIELD VALUE
>             10              Selection Name "host.example.org"
>             11              IP Hostname "host.example.org"
>             14              OVW Maps Exists                 1
>             15              OVW Maps Managed                1
>             75              IP Status                       Normal(2)
>             78              isIPRouter                      FALSE
>             101             IP Name "host.example.org"
>             105             vendor                          IBM(28)
>             117             isNode                          TRUE
>             119             isComputer                      TRUE
>             120             isConnector                     FALSE
>             122             isBridge                        FALSE
>             123             isRouter                        FALSE
>             124             isHub                           FALSE
>             129             isWorkstation                   TRUE
>             145             isDHCPClient                    FALSE
>             146             hasBadOID                       FALSE
>             147             hasInconsistentSubnetMask       FALSE
>             149             isMLM                           FALSE
>             151             isIP                            TRUE
>             174             isSNMPSupported                 TRUE
>             176             SNMP sysDescr                   "IBM PowerPC 
> CHRP Computer
>                                                              Machine Type: 
> 0x0800004c Processor id: 00CAD51E4C00
>                                                              Base 
> Operating System Runtime AIX version: 05.03.0000.0050
>                                                              TCP/IP Client 
> Support version: 05.03.0000.0053"
>             177             SNMP sysLocation                ""
>             178             SNMP sysContact                 ""
>             179             SNMP sysObjectID "1.3.6.1.4.1.2.3.1.2.1.1.3"
>             180             SNMPAgent                       IBM RS/6000 
> 4.1(200)
>             186             SNMP ipAddress "9.8.106.106"
>             219             TopM Interface Count            2
>             225             TopM Interface List             "en1; Up  
> 9.8.106.106  255.255.254.0   0x00145EC63299  ieee 802.3 csmacd   "
>                                                             "en0; Up  
> 192.168.88.171  255.255.252.0   0x00145EC63298  ieee 802.3 csmacd   "
>             248             XXMAP Protocol List             "IP"
> 
> 
> [B]
>     d:\>ovobjprint -s S10B2DBD
>                     OBJECTID                SELECTION NAME
> 
>     OBJECT: 899899
> 
>             FIELD ID        FIELD NAME                      FIELD VALUE
>             10              Selection Name                  "S10B2DBD"
>             11              IP Hostname                     "S10B2DBD"
>             14              OVW Maps Exists                 1
>             15              OVW Maps Managed                1
>             75              IP Status                       Normal(2)
>             78              isIPRouter                      FALSE
>             101             IP Name                         "S10B2DBD"
>             105             vendor                          IBM(28)
>             117             isNode                          TRUE
>             119             isComputer                      TRUE
>             120             isConnector                     FALSE
>             122             isBridge                        FALSE
>             123             isRouter                        FALSE
>             124             isHub                           FALSE
>             130             isMini                          TRUE
>             145             isDHCPClient                    FALSE
>             146             hasBadOID                       FALSE
>             147             hasInconsistentSubnetMask       FALSE
>             149             isMLM                           FALSE
>             151             isIP                            TRUE
>             174             isSNMPSupported                 TRUE
>             176             SNMP sysDescr                   "IBM OS/400 
> V5R3M0"
>             177             SNMP sysLocation                ""
>             178             SNMP sysContact                 ""
>             179             SNMP sysObjectID "1.3.6.1.4.1.2.6.11"
>             180             SNMPAgent                       IBM 
> AS/400(193)
>             186             SNMP ipAddress "9.8.44.139"
>             219             TopM Interface Count            1
>             225             TopM Interface List             "ETHLINE1 Up   
>    9.8.44.139   255.255.255.0   0x00096B6529BF  ethernet csmacd     "
>             248             XXMAP Protocol List             "IP"


-- 
Best Regards,

mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
--
(See attached file: signature.asc)_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

signature.asc
Description: Binary data

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)