nv-l

RE: Collection Group Problem

2000-03-28 22:04:10
Subject: RE: Collection Group Problem
From: lclark AT us.ibm DOT com
To: nv-l AT lists.tivoli DOT com
Date: Tue, 28 Mar 2000 22:04:10 -0500
So you have established that the devices are capable of returning data
via the mib browser. FYI, the mib browser treats the name you enter
as an IP thing, that is, it resolves it. It does not care if it is in
the database by that name.

>The sites that are having problems is taking quite a while to return the
>data where as sites that are collecting ok are returning data in seconds.

To see if the requests from snmpCollect are timing out, view the
snmpCol.conf
file (in its entirety). There will be entries complaining that it timed
out and will retry in xx minutes unless you tell it to try sooner.
Increasing
the snmp timeout in Netview's snmp configuration may help. Don't count on
all
Netview functions using those timeout setting in the same way.

>5) What I have noticed is when I locate and select the object, then run
the
>MIB browser my data is returned faster then when I type in an IP address
and
>I received information via graph format.

By 'received information via graph format' I'm guessing that you mean you
press the 'Graph' button on the mib browser. Keep in mind that for this
realtime graphing it has to wait at least one polling cycle to start
drawing
the line. The polling cycle in the realtime graphing utilities defaults to
10 seconds. Pulling the mib variables via 'Start Query' just pulls the
current
value, so it is always faster.

> If I type in the ip address for the
>same site, do the same MIB then I receive information back.

As I mentioned above, the mib browser will try to talk to any ip address,
or
name that it can resolve to an address. It is uncomplicated.

>Select graph and receive error 'Nothing to graph. Verify SNMP Agents are
>running on requested nodes and that the  MB variables requested are
>supported by that agent. Use MIB Browser or snmpwalk(1) command to
verify'.

I'm guessing that by this you mean you are using the 'Graph collected data'
function for the selected node. This function is not a realtime tool. It
can
only report on any data previously collected by snmpCollect. So it won't
work
until you figure out why you are not collecting with snmpCollect.

>Grapher Message 'Ignore invalid hostname PortlandDTCDMV-W.

Where exactly do you get this message?

>Now, if I can
>receive data back when I query the selected MIB doesn't that mean that the
>agent is running and the MIB variables are supported on the node and
>returning information.

Yes, it means the agents are capable of returning the data. The question is
why snmpCollect is unable to get it. I'm leaning towards the name
resolution
cause. snmpCollect, especially when it involves nvcold, has different name
dependencies than does the mib browser. If you mysteriously lost your
entries
in /etc/hosts, I suspect that the nodes were discovered with one name and
now
resolve to something slightly differently when snmpCollect looks them up.
Like
a short-name vs long-name problem. If you look through the whole
snmpCol.trace,
I suspect you will find some clues. Try deleting and rediscovering one of
the
problem nodes with your current name resolution, and trying again.

Can anybody else see what it is that Jean is telling us but that I am
missing?
I'm out of ideas....

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

---------------------- Forwarded by Leslie Clark/Southfield/IBM on
03/28/2000 09:07 PM ---------------------------

Jean.M.SCHMIDT AT odot.state.or DOT [email protected] on 03/28/2000 02:17:41 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   nv-l AT tkg DOT com
cc:
Subject:  RE: [NV-L] Collection Group Problem



Thanks for the suggestions. This is what I found.

1) Ran snmpCollect 'ipaddress'. Response: sent collection configuration
check event for 'ipaddress'.

Ran tail snmpCol.trace. Received: Tue Mar 28 02:15:53 2000 : Beginning data
collection...Tue Mar 28 08:53:51 2000 : Next object after diskutil
        (.1.3.6.1.4.1.2.6.4.4.2.1.2) is not supported by agent on
167.131.30.2.
        Use snmpwalk or MIB browser to verify the object exists on this
node.
2) Ran snmpwalk 'ipaddress'. ???????????????????
3) Ran snmpCollect 'ipaddress'. Response: sent collection configuration
check event for 'ipaddress'.
4) Object information matches the description in the seedfile, nslookup,
named.rev all show correct description and addresses for sites. However ALL
site addresses are missing out of my etc/hosts file for an unknown reason.
5) Walked the MIB, queried and received:
     locIfInBitsSec
     1:0 - Serial 0 - Admin down
     2:580000  - Serial 1 - Active
     3:41000   - Token Ring - Active
     IfInOctets
     1:0  - Serial 0 - Admin down
     2:992702626    - Serial 1 - Active
     3:326972767    -    Token Ring - Active.
The sites that are having problems is taking quite a while to return the
data where as sites that are collecting ok are returning data in seconds.

5) What I have noticed is when I locate and select the object, then run the
MIB browser my data is returned faster then when I type in an IP address
and
I received information via graph format. If I type in the ip address for
the
same site, do the same MIB then I receive information back, (noted above).
Select graph and receive error 'Nothing to graph. Verify SNMP Agents are
running on requested nodes and that the  MB variables requested are
supported by that agent. Use MIB Browser or snmpwalk(1) command to verify'.
Grapher Message 'Ignore invalid hostname PortlandDTCDMV-W. Now, if I can
receive data back when I query the selected MIB doesn't that mean that the
agent is running and the MIB variables are supported on the node and
returning information.

I'm still fighting to set up another collection. Again your help is very
much appreciated. Any suggestions on how to proceed?

-----Original Message-----
From: lclark AT us.ibm DOT com [mailto:lclark AT us.ibm DOT com]
Sent: Monday, March 27, 2000 7:44 PM
To: NV-L AT tkg DOT com
Subject: Re:[NV-L] Collection Group Problem




Another thing to check on this is your name resolution. Make
sure you have reverse-lookup on these nodes, and that it returns
the exact same name as your Selection Name as displayed in
Tools..Display Object Info. A mismatch can cause snmpCollect
to not recognize these nodes.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit


_________________________________________________________________________

NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
_________________________________________________________________________

NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l


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