FEC overview

This article is about the frontends supported by the FE group.

Names and subnets

FECs are available in different domain names:
  • hostname.acc.gsi.de
  • hostnomen.fec.acc.gsi.de
  • FEC loads software from asl in the subdirectory with the name 'nomen'.
If hostname scuxl0815 is mapped to kgp2cu02:
  • scuxl0815.acc.gsi.de
  • kgp2cu02.fec.acc.gsi.de
  • FEC loads software from asl in the subdirectory 'kgp2cu02'.


The IN group supplies frontends with the following hostname conventions.


  • SCU = standard control unit
  • X = (64bit system, wanted by m.thieme)
  • L = linux
  • xxxx = 0001 - 9999

MicroIOCs and in general x86 based FECs

  • FELxxxx
  • FE = frontend
  • L = linux
  • MicroIOC if number starts with 9
(if the fecname has "i64" appended, it is a management interface [integrated lights out management = ilo] Ilos are not in their default vlan -> vlan number "64" [which is normal acc net] is appended.)


  • All linux tools are working for hostname and nomenclature.
  • e.g. ping nomen.fec.acc.gsi.de

Log-in, environment and diagnosis via hostname

There are several comfort functions which support you while working on and with a FEC. -- (will also be implemented to work with the host nomen)

Prerequisites: To benefit from this function the user needs to be in the group "fesa" (type groups in the console to find out, which groups you belong to). Or, if you aren't, just source the needed script with the following command "/common/usr/cscofe/scripts/fesa_uti/fec_access.sh".

How to interact with a FEC the proper way:
    • logs in as root on scuxlSCU_NUMBER (leading zeros are padded automatically) or FEC_NAME
    • configures the relevant comfort aliases and helper functions
    • runs a short diagnosis
  • diag [SCU_NUMBER | FEC_NAME]
    • runs a short diagnosis on scuxlSCU_NUMBER (leading zeros are padded automatically) or FEC_NAME
Paswordless login with ssh-key
  • generate key-pair for ssh and add the according line to the cscofe script in the export directory (/common/export/cscofe/fe_keys.sh)
  • make sure your fec has a symlink to "../global/cscofe" in /common/export/nfsinit/<!FEC>
  • reboot the FEC
  • start the ssh-agent on the asl cluster and add your key(s) to it:
    eval `ssh-agent -s`; ssh-add
  • login to the FEC via ssh/sss
  • ask MatthiasWiebel if there are problems

Hostname to hostnomen mapping (FEC DNS mapping)

FEC names are mapped to a nomenclature via a DNS service. Look-ups and new mappings can be done on the asl with the tool fec-nomen-mapper. Execute with -h if you are looking for help.
fec-nomen-mapper -m scuxl0815 kgp2cu02   # Make new mapping. Implicitly deleting old one
fec-nomen-mapper -l                      # List of all mappings 
fec-nomen-mapper -l someRegEx            # Filtered list of mappings

Virtual FECs

See the list of virtual frontends for more information about where to run your mocks.

Access Devices

Overview of communication paths in SCU

SCU interaction diagram.pdf
Topic attachments
I Attachment Action Size Date Who Comment
SCU interaction diagram.pdfpdf SCU interaction diagram.pdf manage 25 K 19 Feb 2020 - 15:31 MatthiasWiebel Overview of communication paths in SCU
Topic revision: r18 - 23 May 2020, AlexanderSchwinn
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback