nv-l
[Top] [All Lists]

Re: Antwort: Re: MLM multiple status update traps

To: nv-l@lists.tivoli.com
Subject: Re: Antwort: Re: MLM multiple status update traps
From: Leslie Clark <lclark@US.IBM.COM>
Date: Mon, 2 Aug 1999 22:10:42 -0400
Sorry, I've been on vacation. Yes, I was seeing the same sort of behavior, but
on AIX. I put on 5.1.1 MLM code and then the fix they sent me for the apar I
mentioned (new midmandV4 exeutable everywhere) and the problem cleared
up, at least for the few days I was there to watch it.  Big flurry of traps
every time
you stop/.start netmon, but as I explained to the customer, the mlms must assume
that that the Netview server is out of sync and update it, just as netmon would
do
a full status poll on startup. So you want to be more cautious about
stop/starting
netmon when you are using MLMs since now you are dealing with a bunch of
traps rather than a bunch of pings. But yes, that's what I was seeing.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager


---------------------- Forwarded by Leslie Clark/Southfield/IBM on 08/02/99
10:02 PM ---------------------------


Peter Farr <farr_p@INS.COM> on 07/14/99 03:49:19 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: Leslie Clark/Southfield/IBM)
Subject:  Re: Antwort: Re: MLM multiple status update traps





We are seeing a problem which may or may not be related. I have attached a
piece of the trap log showing the problem. Margit/Leslie... is this what you
are seeing as well? I am working with Raleigh and they are not able to
recreate this in their lab. We are at NetView 5.1.1 on AIX 4.3.2, and MLM
5.1.1 on NT 4.0 SP4.

As you can see from the log, when we restart midmand it sends in a bunch of
status traps, one for each device it manages - this is expected. One minute
later it sends in the same set of traps again, even though nothing changes.
Occasionally it will repeat this cycle over and over, sending in a complete
set of status traps every polling interval. Before the status traps we also
see some strange traps indicating that the alias and status monitoring
tables have changed to an invalid state.

Here is the log extract:
931806439  7  Mon Jul 12 15:07:19 1999 mlmtd291.ops.tdbank.ca    n Table
state change for: smMlmStatusMonitorState, entry name: NV142.205.66.71.1,
oldState = enabled, newState = invalid
931806439  7  Mon Jul 12 15:07:19 1999 mlmtd291.ops.tdbank.ca    n Table
state change for: smMlmAliasState, entry name: NV142.205.66.71.1, oldState =
enabled, newState = invalid
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.6 up for node tdtboot.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.7 up for node tdt-xterm-innesj.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.9 up for node tdt-xterm-wongn.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.11 up for node tdt-xterm-anselb.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.12 up for node tdt-xterm-chowd5.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.13 up for node tdt-xterm-lutze.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.16 up for node tdt-xterm-catraw.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.18 up for node
xterm-danchn.telecom.ops.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.19 up for node
xterm-needhm.telecom.ops.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.20 up for node 142.205.66.20.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.21 up for node 142.205.66.21.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.22 up for node tdt-xterm-tsaij.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.23 up for node levinvxterm.tdbank.ca.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.30 up for node 142.205.66.30.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.31 up for node 142.205.66.31.
931806443  7  Mon Jul 12 15:07:23 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.71 up for node tdtnv-f40.tdbank.ca.
931806499  7  Mon Jul 12 15:08:19 1999 mlmtd291.ops.tdbank.ca    n Table
state change for: smMlmStatusMonitorState, entry name: NV142.205.66.71.1,
oldState = enabled, newState = invalid
931806500  7  Mon Jul 12 15:08:20 1999 mlmtd291.ops.tdbank.ca    n Table
state change for: smMlmAliasState, entry name: NV142.205.66.71.1, oldState =
enabled, newState = invalid
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.6 up for node tdtboot.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.7 up for node tdt-xterm-innesj.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.9 up for node tdt-xterm-wongn.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.11 up for node tdt-xterm-anselb.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.12 up for node tdt-xterm-chowd5.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.13 up for node tdt-xterm-lutze.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.16 up for node tdt-xterm-catraw.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.17 up for node TDSI-RMONDB1.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.18 up for node
xterm-danchn.telecom.ops.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.19 up for node
xterm-needhm.telecom.ops.tdbank.ca.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.20 up for node 142.205.66.20.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.21 up for node 142.205.66.21.
931806504  7  Mon Jul 12 15:08:24 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.22 up for node tdt-xterm-tsaij.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.23 up for node levinvxterm.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.26 up for node
xterm-kitet.telecom.ops.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.30 up for node 142.205.66.30.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.31 up for node 142.205.66.31.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.71 up for node tdtnv-f40.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.100 up for node ibm-it-spec.ops.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.103 up for node tchrisc.ops.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.104 up for node mlmey06.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.105 up for node tgammam.ops.tdbank.ca.
931806505  7  Mon Jul 12 15:08:25 1999 mlmtd291.ops.tdbank.ca    n MLM
detected interface 142.205.66.108 up for node tralhad.tdbank.ca.

Regards...

Peter Farr
Network Systems Engineer
International Network Services (INS) Canada
Pager: (800) INS-1-INS or (888) 548-6174


-----Original Message-----
From:   Discussion of IBM NetView and POLYCENTER Manager on NetView
[mailto:NV-L@UCSBVM.UCSB.EDU] On Behalf Of Leslie Clark
Sent:   July 8, 1999 7:20 PM
To:     NV-L@UCSBVM.UCSB.EDU
Subject:        Antwort: Re: MLM multiple status update traps

They told me to get the efix for APAR IY00707. It is about
repetitive traps.

Cordially,

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


Can you tell us the number of this e-fix?

Regards
Margit



Bitte antworten an Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.UCSB.EDU>

An:     NV-L@UCSBVM.UCSB.EDU
Kopie:   (Blindkopie: Margit Holzwarth/RWSO/DE)
Thema:  Re: MLM multiple status update traps




I have been told that there is an efix out for a problem
with excess status traps, and it goes on after the MLM
update in 5.1.1, so you might want to call Support. I will
be trying it out at next week's customer.  Also make
sure you don't have multiple entries in the trap destination
table for each MLM, and have not also set the trap destination
in the /etc/snmpd.conf file on the MLMs.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking


My client is seeing a problem where their MLMs are sending in multiple
status traps for each interface they manage each polling cycle. This does
not happen all the time, nor does it come from the same MLM all the time.
When hit happens It is causing some severe performance problems since it
can
send in several thousand traps every update cycle. The problem has been
reported to IBM, but I thought I would also ask on this forum if anyone has
seen this and, if so, how it was fixed.
The MLMs are version 5.1.1 running on Windows NT 4.0. NetView is version
5.1.1 also, but running on AIX 4.x.
Regards...
Peter Farr
Network Systems Engineer
International Network Services (INS) Canada
Pager: (800) INS-1-INS or (888) 548-6174


<Prev in Thread] Current Thread [Next in Thread>
  • Re: Antwort: Re: MLM multiple status update traps, Leslie Clark <=

Archive operated by Skills 1st Ltd

See also: The NetView Web