Target Release Date 16 May 2022 

Final edits due 12 May 2022 

Introduction

This edition is extra special as we have for the first time a section for LCLS IT recording some of the improvements and maintenance activities of Omar's team!

...

ECS would like to take a moment to emphasize the importance of EEIP at LCLS and SLAC in general and remind everyone reading this newsletter to look into what EEIP is, and how to make sure your equipment is compliant. You can learn more about EEIP here: https://slacspace.slac.stanford.edu/sites/pcd2/eeip/default.aspx 

EEIP ES&H Ch8 (Electrical Safety) is everyone's responsibility. 

...

More controls requirements were developed in March and April. These requirements were specifically focused on EPICS network size, DAQ bandwidth, EPICS archiver size and reliability, as well as the logging systems. High-level requirements are being developed as ConOps are updated/ generated. If there is any particularly important requirement of the control system, or high-level functionality please let Alex Wallace or Jing Yin know.

...

The purpose is to provide 100GbE stacking and/or uplinks for maximum reliability and multigigabit access.  The first 24x (1 - 24) ports provide 1000 Mbps connection and the next 24x (25 - 48) ports provide 10,000 Mbps connectivity.  All ports provide POE+ with /802.3bt (90W per port)  with up to 1500W power budget with 2 power supplies.

Ruckus ICX 7850-48ZP

WEKA Home/FFB Cluster Upgrade

LCLS has 2 WEKA storage clusters: i) provides the home directories and software for all users and staff, and ii) the FFB  for the user's experiments.  There was a bug with the previous release of WEKA affecting quota. The latest version was installed to fix the quota bug and improve performance.  The team is still working with the WEKA team to provide the users with the output of their appropriate space usage (quota)deliver a feature for users to check their current quota usage.

DSS and MON Nodes

There have been many incidents where the Experiment Controls and DAQ team is not aware of the available DSS and MON nodes fell into disrepair during a given experimentan experiment and communication about their state as well as a checklist for the required setup was missing.  To provide transparency across the multiple teams, the IT team has created a confluence page that explains the validation methodology and provides a log of the current functional DSS and MON servers.  This will prevent the teams from guessing which nodes are available and allow the IT team to fix those that are not available.  Coming soon, the IT team will deploy a new image with monitoring that will provide alerts so that actions can be taken in a timely manner.

...

We saw the highest number of resolved issues in March and in general a leveling out of delivery related issues.

Over 200 issues resolved in the past two months. Not bad!

...