James,
determination the event window was not processing was done by
checking activity in trapd.log
Which had data that should have been forwarded to TEC but were not
displayed in event window.
Here we display all data that is sent to TEC in the event window.
The event window displayed no activity for approximately 30 mins.
Checked the tec cache member, which had 1538 object waiting to be
transferred to TEC.
Errpt has no indication that nvserverd cored
So, the bottom line here is, that this is a known problem scheduled to
be resolved in FP03?
Thanks Patrick.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On Behalf Of James Shanks
Sent: Monday, March 14, 2005 8:09 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] NVTECIA -STOP
Basically, my advice is to stay away from the nvtecia command until you
have FP03, where all the code involved in the rewrite of it is finally
shipped as one. FP03 is due out April .
If you must have it now, then you will need to obtain the fix for
IY65255, else you will not be able to restart the adapter with nvtecia
-reload.
But I haven't heard of nvserverd failing because of nvtecia -stop
before.
When you say the event window stops processing, how did you determine
that? Did you get a pop-up saying that nvserverd was down? How about a
core of nvserverd (check errpt -- "errpt -a | more")?
I also don't understand why you should have to stop all the daemons. A
simple ovstart nvserverd should do the trick.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
-----------------------------------------
This e-mail may contain confidential or privileged information. If you
think you have received this e-mail in error, please advise the sender by
reply e-mail and then delete this e-mail immediately. Thank you. Aetna
|