Three issues:
(1) There were several problems with demand poll and netmon in 5.1 which
were fixed in 5.1.1. But they were so severe and annoying that an "efix"
package was assembled for 5.1 customers, so they would not have to wait so
long for relief. If you want/need that package, please call Support
(1-800-Tivoli-8 or whatever number you have used in the past) and ask for
it.
(2) Tivoli customers who have a current maintenance contract will be
autoshipped 5.1.1. But if you cannot wait, then call the Support number
and ask them for help; or you can send a note to swdist@tivoli.com saying
you want NetView 5.1.1 for UNIX or NT, and include the usual information:
company name, customer number (preferably, a Tivoli cust# which starts with
a T, but IBM cust# can work), mailing address, contact name (that's you
presumably), and contact (your) telephone number.
(3) trapd does not write an event to the log until the next event arrives,
so your experience with the trapd.log is entirely normal
James Shanks
Tivoli (NetView for UNIX) L3 Support
Jan Green <greenjan@YAHOO.COM> on 04/07/99 09:26:48 AM
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: James Shanks)
Subject: Netmon Hanging and Demand Poll Hanging
Please Help!
I am running Netview 5.1(I do not have the patch 5.1.1
yet). We just upgraded the system. Since, have been
having problems with netmon hanging and demand poll
hanging.
I forced a trap through my rulesets and logged it
using the nvcdebug -d all command. It is finishing in
about 1 second.
When a node down comes through it is processed right
away, no problem. Demand poll is working as well.
However, when a node down/node up pair comes into
trapd.log it takes 20-30 minutes to arrive in the
ovevent.log. When many traps come in the problem is
multiplied. At peak times I have seen the delay 10-12
hours. During this time, demand poll is hanging.
This has only started happening since the upgrade. It
appears to be a netmon problem. Does anyone know what
may be causing this? And is there a patch?
______________________________________________________
This may or may not be related:
I have noticed that trapd.log is always one trap
behind. Almost like it holds one trap in a buffer
until another comes in. Then the first trap in the
buffer is displayed and the new one is held. Both show
up in the ovevent.log though.
For example; I send an event command at 11:15:00. The
event shows up in the event log but not in trapd.log.
Then I force another node up at 11:20:00. The second
one shows up in the event log and the first shows up
in trapd.log with the timestamp of 11:15:00. It is
always one behind.
I know this is confusing: I am out of ideas.
Thanks for any ideas.
Jan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|