Summer 2022 CDS system upgrade

The plan is to upgrade the 40m CDS system to latest RTS release. As of this writing, that would be advLigoRTS 4.2.8.

The basic plan:

  1. Set up a new rack midway down the Y arm (1Y3b).
  2. Move all 6 current front end machines, and FB, to the new rack.
  3. Install a new front end machine with support for AVX512 instructions in the new rack.
  4. Run OneStop fiber between all the front ends and their IO chassis (which all stay in their current locations).

  5. Install Dolphin IX interconnect for all front ends in the new rack (drop all old RFM).
    • IX card in all front ends
    • IX switch in new rack
  6. Upgrade all machines (front ends (via diskless boot) and FB) to Debian 11 (or 10, whichever is currently in production at the sites).
  7. Install all needed software components via CDSSoft Debian 11 (or 10) archive.

Before the upgrade we will test the new software configuration on the 40m test stand.

We will assume that we will support up to 8 front end machines in the new system (7 will be present after the upgrade)


What do we need that we don't currently have:

What we need that we think we currently have (need to actually find and store these to avoid double counting):

  1. A Rack
  2. Some other FE machines for all of our running models? How many? Can we re-use some existing computers? NEED to TEST that new RTS works on these or we are in danger of hanging up the whole 40m during this upgrade.
  3. A framebuilder. I know is **SHOULD** work, but that's what we say about everything right before it doesn't work. Need to test this also and possibly buy a new FB if our old one has issues.

Items

Quantity

Description

Status

Action

KVM 8-port Switch

1

keyboard and display control switch

unknown

See table below for details

OneStop Card

17

PCIe extension from FE to IO chassis

received

OneStop Fibre (100 m)

7

PCIe extension fibre

received

Dolphin IX Card

8

FE RFM adapter card

received

Dolphin IX Cables

8

FE to dolphin switch

received

Dolphin 8-port switch

1

dolphin switch to connect all FE

received

Rack

1

Rack to mount all FE machines, dolphin switch, KVM switch

received


Items

Quantity

Description

Link

Price

KVM PS2 8-port Switch

1

Keyboard and display control switch

KVMPS2

$429.95

PS/2 KVM Cable 6 Ft

2

Converts the VGA to VGA + PS2 for the older computers

PS/2 KVM Cable

$19.95

OneStop Fiber Optic Cable

6

Connects IOChssis to Computers. (THESE ARE DIRECTIONAL)

4G3 PCEIO Cable

Available at Request

OneStop Copper Cable

1

Connects IOChssis to Computers. (THESE ARE DIRECTIONAL)

Copper OneStop 7m Cable

$372.00


C1teststand

The FE machines initially spec'd for the teststand are c1sus2 and c1bhd. Currently, c1sus2 has been moved to the main system and c1bhd may be moved over in the near future, so I believe we need at least 2+ FE machines to have an operational teststand longterm. In the meantime, we need a new front-end to test dolphin communication with c1bhd.

Items

Quantity

Description

Status

Action

Front-end (FE) machines

2+

Needed to test dolphin communication

received

OSS-PCIE-HIB25-X4 Gen 2 Host Cable Adaptor.

2+

OneStop companion card on FE

unknown


recipe

fb1

` Unable to find the following file in CDS_MEDM_PATH: SUS_SINGLE.adl ERROR: Could not find file: generate_KisselButton.py Searched path: /opt/rtcds/caltech/c1/post_build Exiting make: *** [Makefile:166: install-c1sus] Error 1 `

---

chroot installation issues

We ran into some problems installing dolphin via chroot, which was fixed by

uname -r dolphin driver install issue

We also noticed that the different linux kernel versions on the bootserver and front-ends was causing issues due to chroot 'uname -r' call giving the bootserver's kernel instead of the FE kernel, so we fixed that by installing the same FE rtcds kernel on the boost server as well.

boot server

These are the cmds we ran to setup dolphin on the bootserver.

---

We decided the symlink idea was not a good one, so we edited /diskless/root/etc/fstab to mount a writeable /etc/dis instead.

Model edits for dolphin test

RCG guide

Additional configuration for Gen2 dolphin

(posible bug in packaging) System services needed

To get dolphin communication working, we had to do the following:

FIX

DAQ setup

On FB1

On FE

CDS/Upgrade2022 (last edited 2022-10-11 22:35:28 by JancarlosanchezATligoDOTorg)