NRS6311: PCINIT on Telnet devices

Commentary

Tuesday, March 13, 2007 at 02:30:43 am    Client reports sessions with some devices suddenly go PCINIT. Running a trace shows device sending in BIND and Director doesn't respond.

Wednesday, March 14, 2007 at 03:59:43 am    Spoke with Client and it now appears the problem occurred directly after one of the systems in the complex "disappeared". Additionally, issuing a Director RELEASE NET= command against the LU appear to clear the symptoms (meaning, the LU appears to work properly after the command). We'll leave this in WAIT state (Open, but waiting for client) until we get a higher comfort level for whether we've cleared the symptoms or not.

Thursday, March 22, 2007 at 08:36:56 am    Client called and they've not experienced the problem again. He suspects the original issue was aggravated by an unrelated system problem (device reserves, etc.) that lasted 5 minutes or so (after which, the Director exhibited the reported symptoms). After R N= against the LUs, the problem corrected itself. And, after IPL over the weekend, there's been no re-occurrance....so Client suggested we close this APAR.