TITLE: 01/27 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 24mph Gusts, 22mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY:

H1 Is Down:

Jeff gave me a summary of the issues he's had with locking as he fought valiently to bring it back over the last half of his shift.  I just took H1 to DOWN.  Will try a fresh start at locking as-is post-DOWN, but after that, if there are issues, I'll begin an alignment, check alogs for issues over the last week to see if this sheds light, and so on.

Another Network Issue:

As Jeff was getting ready to leave, he noticed he was no longer connected to the LHO GC Staff wifi network (and I was not the GC Staff wifi via my laptop or phone either.)  This sounds different to Niko's CDS network issue from yesterday. 

I cannot glean any ideas from the CDS Overview (which makes sense since this issue appears to be related tothe GC-network). 

Operator TeamSpeak:  We are not logged into this.  So I phoned the LLO opearator to notify them of our situation. 

Since this is just GC-related, I'm not going to wake Richard/Dave up about this & only going to send an email to cds admin about this and leave it for morning.  Currently I have access to the internet (i.e. email, alog, etc.) via CDS web browsers so will next move to working on H1. 

This sounds like a similar issue (see here, here)to what I had about 6-weeks ago where Richard brought us back when he got in (although for that GC-outage we also had some phones down (I confirmed my office phone was fine).

I'm tagging FRS on this alog due to the GC Network connectivity issue.