rreed@mntgfx.mentor.com (Robert Reed) (09/21/88)
This question has been raised several times in recent weeks. I, a random user, had just such a need Sunday night about 9 pm when operations staff was nonexistent. The following fairly describes the situation I ran into and the fix to which I resorted: A bug in SR9.7 causes spurious communcations error messages during DSEE operations that access objects on remote SR9.7 nodes. For example, during a DSEE history management operation, you may receive a "remote node failed to respond to request" error even when you are able to communcate with the remote node. Once this error occurs, you will be unable to access the remote object until you have rebooted one or both of the nodes involved.... If I had not been able to shut down the node, I would have been SOL and lost several hours of work towards my ever pressing deadlines.