23-Dec-2009

Router problem
Usually, I check the logs on the system and mail over the web as soon as I get at my office. This morning I could access the operation desk (the protected access to do system manager work) but there it ended. ANY site on grootersnet.nl was inaccessible – couldn’t be accessed.
Tonight it turned out the router hung: ALL access failed. Not just incoming traffic. All traffic failed: DNS (it serves as a resolver), Outgoing traffic, it’s admin page – it all failed. So what remains was resetting it. That solved the issue – but also removed any clue of what may have caused it.
Well, I’m in for a new one anyway. But nevertheless, a VMS port of syslogd will be installed in Diana to serve as loghost for the router.
Access problems of another kind
Since the new PWS has a differential SCSI card installed – KZPSA-CA – I decided to hook it on the Shared SCSI and boot from the shared system disk.
Bit problem. Diana lost connection to the quorum disk and postponed all activity.It regained access and resumed after the HSZ50 was disconnected.
It may have been a termination issue – though there is a termination on the cable. But it might have been the -CA type. I have been able to boot the old AlphaServer 400 from this disk using a KZPSA-CY controller. So I switched the cards and retried. This time, though Diana keeps complaining loosing the quorum disk, it always regained access and continued. The new box started booting, but always ended starting MSCP serving. Nor did it enter the clsuter environment! So that may actually be the problem
But booting form it’s own (VMS 7.3-2) system disk succeeds, even when hooked up to the shared SCSI. The system joins the cluster, as shown in SHOW CLUSTER, and accessing the disks seems possible.
But here as well, Diana looses access to the quorum disk at times….
Perhaps Iĺl have to re-create the node-environment from scratch…