we have an issue with our PE boxes, where we get memory interlocks when this happens commands like vwcemp -l, vwtool stop working..
the out of the box monitors for PE do not seem to be able to alert me of this issue..
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2009-06-19T13:35:07Z by Steven_Bass
Pinned topic new help getting FSM to monitor PE
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-06-19T13:35:07Z at 2009-06-19T13:35:07Z by Steven_Bass
Martin.Willingham 060001XT2B13 PostsACCEPTED ANSWER
Re: new help getting FSM to monitor PE2009-06-19T03:07:52Z in response to SystemAdminLou,
How are you checking memory interlocks? With vwspy?
FSM has a monitor called "Process Status" that can detect how many processes are in different states.
It's also possible to have FSM run a custom script (shell, perl, etc) that checks whatever you normally do at the command line, such as using vwspy to check for the number of processes running longer than a specified time.
What version of FSM are you running?
Steven_Bass 270000MJD130 PostsACCEPTED ANSWER
Re: new help getting FSM to monitor PE2009-06-19T13:35:07Z in response to SystemAdminLou,
Have you considered employing vwtool and vwcemp as custom monitors. If a monitor utilizing these commands fail, it would be a good indicator that your interlock issue may be occurring, and give you the advance warning you need.