CLONWiki - User contributions [en]

SSH

2026-08-06T21:41:34Z

Boiarino: /* RHEL9 */

== RHEL9 ==

On RHEL9 machines, to be able to ssh to old machines (like vme controllers under CentOS5), run following as root:

update-crypto-policies --set LEGACY

and then probably reboot, not sure.

'''NOTE:''' that worked on RHEL9.7. On RHEL9.8, in addition, have to add 2 lines to the end of ''/etc/ssh/ssh_config'':

HostKeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa

== other issues ==

To ssh ignoring 'Offending key in /site/etc/ssh_known_hosts' do following:

ssh -o UserKnownHostsFile=/dev/null <hostname>

If does not work, comment out following line in your ''/etc/ssh/ssh_config'':

###GlobalKnownHostsFile /site/etc/ssh_known_hosts

== old ==

First, enable X11 forwarding: uncommented and properly set 2 following lines in ''/etc/ssh/ssh_config'' file:

Host *
ForwardX11 yes

Normally ''ssh'' creates ''.Xauthority'' file in ''$HOME'' directory. If ''$HOME'' directory is on file server and shared between different machines, it can be a conflict. It is recommended in that case to tell ''ssh'' to place ''.Xauthority'' file somewhere else, for example in ''/tmp'' directory which is usually local. Do following:

1. Uncomment or add following line in ''/etc/ssh/sshd_config'' (it will force execution of /etc/ssh/sshrc script which we'll create below; also every user's $HOME/.ssh/environment file will be processed):

PermitUserEnvironment yes

2. Create ''/etc/ssh/sshrc'' with following contents:

HOME=/tmp
XAUTHORITY=$HOME/.Xauthority.$USER
export XAUTHORITY
if read proto cookie && [ -n "$DISPLAY" ]
then
if [ `echo $DISPLAY | cut -c1-10` = 'localhost:' ]
then
# X11UseLocalhost=yes
echo add unix:`echo $DISPLAY |
cut -c11-` $proto $cookie
else
# X11UseLocalhost=no
echo add $DISPLAY $proto $cookie
fi | /usr/openwin/bin/xauth -q -
fi

(on RHEL4 ''xauth'' is located at ''/usr/X11R6/bin/xauth'', on RHEL5 at ''/usr/bin'', adjust script accordingly)

3. Add two lines in ''/etc/profile'':

XAUTHORITY=/tmp/.Xauthority.$LOGNAME
export XAUTHORITY

4. NOTIFY ALL USERS TO HAVE THAT FILE WITH CORRESPONDING CONTENTS IN THEIR ''$HOME/.ssh'' directories. You can do it for example by placing following into ''/etc/.login'' (on linux you can use ''/etc/csh.login''):

if (! -e ~/.ssh/environment ) then
echo ""
echo "===== ERROR: create file '~/.ssh/environment' containing following line:"
echo "===== XAUTHORITY=/tmp/.Xauthority.$LOGNAME"
echo "===== OTHERWISE SSH/X11 MAY NOT WORK PROPERLY"
echo ""
endif

5. Create ''/root/.ssh/environment'' file with following contents:

XAUTHORITY=/tmp/.Xauthority.root

6. Restart ssh service by

svcadm restart network/ssh

(on Linux ''/etc/init.d/sshd restart'')

7. If need to make ssh without password between different clon machines for some user, login as that user and do following (chmod commands are important !):

mkdir .ssh
chmod 700 .ssh
cd .ssh
ssh-keygen -t rsa
<hit return 3 times>
#cp id_rsa.pub authorized_keys
ssh-copy-id <machine_name_you_are_in>
chmod 600 *

After that for this user all machines with the same home directory have to be accessible without typing password. If machine has different home directory, copy contents of the 'id_rsa.pub' into remote machine 'authorized_keys' file.

8. Tunneling: for example to tunnel from home to clontrig0 for vnc (port 5902) do following:
ssh -L 5902:localhost:4321 login1.jlab.org
and then from the same window:
ssh -L 4321:localhost:5902 clontrig0
Now if VNCVIEWER on home machine connect to localhost:5902, it will actually connect to clontrig0:5902.

JLAB VME TID

2026-07-31T18:10:19Z

Boiarino:

'''This page describes 12GeV-era TI board.'''

Manual for the intermediate TID board:
[https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TImaster.pdf (pdf)] [https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TImaster.docx (docx)]

Manual for the TI at April 23, 2013:
[https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TI_23_apr_2013.pdf (pdf)]

Manual for the TI at December 3, 2013:
[https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TI_3_dec_2013.pdf (pdf)]

Clock distribution manual:
[https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TriggerClock.pdf (pdf)] [https://clonwiki0.jlab.org/wiki/clondocs/Docs/JLAB_VME_TriggerClock.docx (docx)]

'''NOTE:''' To switch to 125MHz, flip the SC1 switch (very bottom of the board) bit#3 and bit#5 to HIGH (up). (The numbers are marked on the switch, from right to left).

JLAB VME TID

2026-07-31T18:10:10Z

Boiarino:

MPD

2026-07-29T19:12:54Z

Boiarino:

'''Things to try in case of problems:'''

* recycle gem LV (and HV ?)

* roc_reboot gem1/gem2

* roc_reboot mpd1/2/3 and gem1/gem2

* roc_reboot everything (helped once)

'''Useful commands to debug MPD/VTP readout problems:'''

tcpClient gem1vtp vtpRocStatus - check 'Trigger Cnt' and 'Trigger Acks'
tcpClient gem1vtp mpdGStatus - check 'Event Builder' table
tcpClient gem1vtp vtpMpdPrintStatus - check ...

'''MPD->SSP/VTP data format:'''

[https://clonwiki0.jlab.org/wiki/clondocs/Docs/SSP_MPD_EventFormat_31_oct_2025.pdf (pdf)]

'''MPD VTP firmware:'''

fe_vtp_v7_mpd_jan1_26.bin - copied to fe_vtp_v7_mpd.bin and used
fe_vtp_v7_mpd_jul29_26.bin - new version to address possible issues, to be tested

Boiarino:

'''Initial setting:'''

Unplug ethernet cable.

For new controller, push and hold '''DEL'' to get BIOS.

In BIOS, go to '''Advanced->Network Stack Configuration''' and enable '''Network Stack''' and '''Ipv4 PXE Support'''.

In BIOS, go to '''Abaco->Network Boot Configuration''' and enable '''PXE ROM - ETH3''' and '''PXE ROM - ETH4'''.

In BIOS, go to '''Abaco->VMEbus Configuration''' and set '''Reserve VME Space''' to '''512 MBytes'''.

'''Save & Exit'''

Connect ethernet cable to the top port. Recycle power, it should boot (if not, in BIOS, go to '''Boot''' and set appropriate network port(s) in BOOT Option #1 (and #2)).

Tftpboot

2026-04-01T19:18:43Z

Boiarino:

'''Tftpboot setting to boot diskless VME controllers'''

If ''/tftpboot'' directory does not exist yet, copy it from ''/usr/downloads'' (it come from Bryan Moffit in April 2025).

'''EFI boot'''

File ''/tftpboot/efi/boot/grub2/grub.cfg'' should have following contents (to use ''/diskless'' from file server, below set ''...root=nfs:129.57.167.16:/vol/diskless/...''):

function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod all_video
}

load_video
set gfxpayload=keep
insmod gzio
set timeout=2
menuentry 'Diskless CentOS7 x86_64, any network device' --class redhat --class gnu-linux --class gnu --class os {
linuxefi linux-install/CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64 zram=1 ip=::::::dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root ro vga=0x305 module_blacklist=ipmi_si,ipmi_msghandler,ipmi_devintf,w83977f_wdt
initrdefi linux-install/CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img
}

that file will serve all EFI-bootable VME controllers, '''no need to set anything in ''/tftpboot'' area'''

'''PXE boot'''

In directory ''/tftpboot/pxelinux.cfg'', PXE-bootable controllers boot files are stored. For example:
C0A80A06 -> test6
test6

where ''C0A80A06'' is test6's IP address in hex format (192.168.10.6), and ''test6'' has following contents:
default CentOS7

label CentOS7
kernel CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64
append initrd=CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img ip=dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root,tcp ro

# label CentOS7
# kernel CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64
# append initrd=CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img ip=bootdev:dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root,tcp ro ifname=bootdev:00:20:38:0A:07:D7

It should be mentioned that in both cases VME controller's root directories will be mounted as 'read only'. All individual controller-specific directories will be placed in 'snapshot' area.