Diba,
If you are accustomed to working with SNMP data the way the NetView
snmpCollect daemon stores it, i.e. one file for each MIB object and instance
combination, e.g. ifInOctets.3, then check out the "mlmRemoteCollect" and
"smconvert" utilities. Both of these run on the NetView server. The first
one will transfer the MLM collect log to the NetView server. The second one
converts the MLM collect log into the familiar snmpCollect format. You can
then run snmpColDump against the data files to get the statistics.
-----Original Message-----
From: Adibah Mohamed [SMTP:bmadibah@NCS.COM.SG]
Sent: Tuesday, August 18, 1998 01:24
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: Netview MLM configuration
Thanks Joel & James....
I think the problem I have with the "session to node" down is
minor
because I notice that if I don't use the Alias name (which is
defined in
the Alias Table) but use the specific IP address instead, I am able
to
collect stats.
the biggest headache I have right now is that the MLM stores all
stats
collected in one file.
Diba
Joel A. Gerber wrote:
>
> The error message mentioned in item (ii) below is an indication
that the MLM
> system has lost connectivity to a node that is collecting SNMP
data from.
> Make sure that you are running the snmpwalk from the MLM system,
and not the
> NetView system. Running snmpwalk from the NetView console only
checks that
> the NetView server has SNMP connectivity. You need to run
snmpwalk from the
> MLM server to determine if it has SNMP connectivity to the node.
Another
> possibility is that there was an intermittent timeout, and when
you ran the
> snmpwalk everything was fine. Check the SNMP configuration either
in
> NetView or MLM, and make sure that the SNMP retries and timeout
are "long
> enough" to avoid timeouts on the SNMP get requests.
>
> -----Original Message-----
> From: James_Shanks@TIVOLI.COM
[SMTP:James_Shanks@TIVOLI.COM]
> Sent: Friday, August 07, 1998 14:58
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: Re: Netview MLM configuration
>
> I don't know the answer to number ( ii ); perhaps someone
else does.
> If
> not, then please open a call with Support.
> But ( i ) is the way MLM works. It will only discover
nodes on its
> own
> subnet. You can modify the collection it creates to add
some new
> nodes or
> subnets to the polling it does, but discovery is limited
to its own
> subnet.
> Have you read all the MLM documentation?
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Adibah Mohamed <bmadibah@NCS.COM.SG> on 08/05/98 10:15:43
AM
>
> Please respond to Discussion of IBM NetView and POLYCENTER
Manager
> on
> NetView et alia <NV-L@UCSBVM.UCSB.EDU>
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks)
> Subject: Netview MLM configuration
>
> I'm having some problems with my MLM...
>
> (i) I'm only able to discover nodes in the segment which
my MLM is
> in.
> (ii) For data collection, I get the error indicating that
the
> "session
> to node is currently down" even though I have no problems
doing an
> snmpwalk from the console to get the MIB variable values.
>
> Adibah Mohamed
> NCS
|