| Dave,
>>With PCM 1.5 ECO 1 installed on OSF/1 v2.0, if you select the exit option from
>>the monitor interface, i.e. using the mouse and select option File, then Exit,
>>the process remains on the system and must be manually killed. This problem
>>can be serious as these processes are not killed off by a CM shutdown/startup
>>either.
We knew this was a problem on ULTRIX, but were unaware of this on OSF/1, basically,
we dont get told via a signal or any mechanism that the controlling terinal is going
away when you use the "Exit" option! So the process just sits around and does nothing.
Not a lot we can do about this I am afraid except tell your customer "DON'T DO IT!!"
>>Finally, a customer (same scenario as above) has reported the following message
>>appeared for one of the connected nodes -
>> Console Link loss detection disabled for system XXX.
>>This message is not included as a CM event and there were some comms problems
>>with this node at the time. Can anyone shed any light on this message or
>>when it occurs/under what circumstances etc.
You should have an event in your PCM database called "CMgr Console Lost Disabled" which
is the event the customer is seeing. My guess is that your customer is using a terminal
server which doesnt support the TELNET GETSTATUS option, when we open the connection to
the listener on the terminal server we perform some TELNET option negotiation, we need
the GETSTATUS option in order to periodically check that the server is still on the
network (unlike LAT we dont get told when the connection/server goes away). So, without
this option we have to disable our code which periodically checks the status of the
connection hence the event telling you about this.
In summary BUY a DIGITAL terminal server, they ALL support the GETSTATUS option.
Cheers,
Phil
|