Mark, this might be an issue with name resolution. You say
"When I look at the ip properties of the router in Netview, it's
ip address is 203.41.116.254" but ip address is not a property of a node,
only
interface cards have ip addresses. You forced discovery by one address,
then Netview
found the other addresses and made cards for each of them. If you want
references to
the node name "xlwr01" to always use address 203.41.116.254, then you have
to
arrange that in your name resolution. If you are using /etc/hosts, it is
easy - just put it first,
before the records for the other addresses (which should also resolve to
"xlwr01").
If you are using a DNS, it may well be returning different addresses at
different times,
for the same name. Check it out. I have heard that some do that,
round-robin style. This
gives Netview problems, and I usually end up overriding the DNS with
/etc/hosts when
it does. The snmpCollect daemon will take the name or address in
snmpCol.conf and
adjust it for name resolution vagaries, and you can see it doing this in
snmpCol.trace
in the log directory.
Next, I wonder what kind of data you are collecting that the data would be
different when
retrieved via one address over another. If those addresses are all truly on
the same
node, then the results should be the same. The only problem would be the
name
resolution, and that's why it is important to Netview to have all addresses
on the node
resolve to the exact same name, and have the name always resolve to the
same
address.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on
01/28/2000 07:22 AM ---------------------------
Mark van Kerkwyk <kerkwyk@COMTECH.COM.AU>@UCSBVM.UCSB.EDU> on 01/28/2000
12:01:18 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
Sent by: Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc:
Subject: Collecting SNMP stats from the wrong IP address
Hi,
I thought I had this one beat but it has come back to bite me again.
I have a seedfile for all nodes in Netview, I am collecting various SNMP
stats
from these devices, the problem I am haiving is that sometimes the data
comes
back with different ipaddress values which then causes reporting problems
as I
report using select statements based on the device's IP address.
eg.
- In the seed file I have a node address of 203.41.116.254
- This ipaddress also has a hostname mapping which maps to the object name
in
Netview eg. "xlwr01"
- Router has 3 interfaces, 203.41.116.254, 203.41.113.24 & 139.47.22.56
- However, the data being stored in the database for the ipaddress value is
the
139.47.22.56 even though the seed file specified the 203.41.116.254
address.
When I look at the ip properties of the router in Netview, it's ip address
is
203.41.116.254
So, why would Netview be collecting data on the 139.x.x.x address ????
Has anyone else had this problem, all I want to do is collect snmp stats
and
make sure the ipaddress stored in the database is always consistent.
Mark
======================================================================
This email message has been swept by MIMEsweeper.
|