Sounds like you may have a problem and you definitely have a
misunderstanding.
First the misunderstanding. The Events window does not show any old events
from ovevent.log. That was how it worked in NetView V3 and earlier. Now
you see events from nvcorrd's cache. If he has just been restarted when
you bring the GUI up then you will not see any events. You can check
whether everything is functioning by issuing the event command. Just type
in event. You should see a dummy Node Up event in the event window in a
few seconds.
If you do, then all is well. If you don't then you need to call Support as
you have a genuine problem.
You can configure the event window to hold more events (see
/usr/OV/app-defaults/Nvevents) but they will all be current ones (those
arriving after the last restart of nvcorrd). You cannot configure the
event window to load old events. If you want to see old ones, then use
Events History. That is what it is for.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Alain Menezes <a.menezes@cger.be> on 09/16/98 06:25:47 AM
Please respond to a.menezes@cger.be
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: nvevents
Hi,
When I launch the netview interface my events window is empty (most of
the times). How can I configure NetView to keep more events (thus older
ones) visible in the nvevents window ?
The way I understand trap processing, the nvevents app shows the events
that are logged in ovevents.log (that are also written in trapd.log);
once a max number of events reached the ovevents file is purged. Can
anyone confirm this ?
Thanks
Al
--
Alain Menezes Email: a.menezes@cger.be
ASLK-CGER Services GIE Tel.: +32 2 228.55.74
Rue Foss
é-aux-Loups, 48 Fax.: +32 2
228.83.69
1000 Brussels
|