Follow up on partially puzzling results from mini-data challenge:
  Reminder:
    Reading from AGLT2 to MWT2 showed expected saturation for UM->MWT2
    But lower and uneven throughput for MSU->MWT2 (unstable? packet loss?) 
    Possible explanation: MSU storage currently only ~1/3 of AGLT2 total
      On read, files have to come from the pool with the requested file
      Independently from queue length for that pool 

  Repeat test with more controlled site targeting:
    Hiro generated a list of (large) candidate files from AGLT2 datadisk
    We sorted that list into 3 lists: MSU/UM/both (both = cached copies)
    Test started reading only from MSU -> saturation near 100G, as expected
    Then only from UM -> saturation near 80G, as expected
    Then from both (with mixed list of files matching MSU/UM storage ratio) -> both sides saturated 

03-Mar dCache update 11.2.0 -> 11.2.1
  This version added SciTag/fireflies for https transfers
  No problem with update
  ESNet dashboard for SciTags

problems with one data switch at the UM site, it went down twice in the past 2 days, had to power cycle it to bring it back. This causes 6 Tier2 work nodes to lost connections

Out of Warranty UPS in the UM Tier3 room had leaking battery , and it affect some Tie2 services as well. We were able to find some old batteries to replace them, and the alert is gone, still observing before placing order for new batteries.