Setting up a new login/submit node


  1. Pick a machine that will host the new login node if one has not already been picked. (Discuss with Philippe)
  2. Pick a rack and slot for the machine to go into. (Discuss with Philippe)
  3. Make sure you have the appropriate rails for the machine, both on the machine and in the slot it will go into.
  4. Put machine in rack.
  5. Get cables for each power supply, blue and green ethernet cables for the private and public networks, and a yellow (if possible) ethernet cable for the iDRAC.
  6. Attach all the cables to the machine (referance nearby machines to see which ethernet port the green and blue ethernet cables should go in).
  7. Find free ethernet ports in the nearest networking switch (look to the other cables on the networking switch to see if there are any patterns; such as green on top, blue on bottom) and plug in the ethernet cables (write down which ports you've chosen for each cable).
  8. Make sure the correct HDDs or SSDs are placed in the machine.
  9. Hook up the KVM (the vga and usb attachment for the monitor in the room) to the machine.
  10. Plug in the power cable and turn on the machine.
  11. While the machine attempts to boot, it should spit out the MAC addresses for the ethernet ports. An example being:
    eth0 842B2B5A9411
    eth1 842B2B5A9413
    Write these down for later.
  12. Restart the machine and create a RAID1 array from the disks (steps 6-9 here).
  13. Restart the machine and click the keys that will take you to the BOOT menu.
  14. Find the menu that lists the BOOT order (i.e., a list of what the machine will try to BOOT from first, second, etc...).
  15. Make sure the network adapter (NiC) is up towards the top of the BOOT order (at the very least before the BOOT drive).
  16. Turn off the machine for now.


  1. Open an x2go session and login to senna.
  2. In a browser open up the cobbler interface (https://msu-prov02.msulocal/cobbler_web).
  3. Click Systems in the side bar.
  4. Create a new system with the new name and hostname.
  5. In systems, pick a login node that has already been setup and want to copy as a reference.
  6. Aside from the Networking (which we will fill out later), make all of the remaining entries in the new system identical to the referance login node.
  7. Ask Philippe to get public and private IP addresses for the new node.
  8. Insert the MAC addresses recorded during the hardware setup and their new IP addresses into the Networking information. Make sure you assign the correct IP address to the correct MAC address, i.e. public vs. private.
  9. Each IP/MAC address has a subnet mask and gateway. Unless they've changed since time of writing they should be:
    Private: Subnet mask
    Public: Subnet mask
  10. The new login node should now be complete on cobbler.
  11. Finally, netboot enable the new login node on cobbler (steps 13-15 here).


  1. In the cfengine masterfiles, add the name of the new login node to the relevant places. For simplicty, just grep for the names of current login nodes (maron, heracles, and alpheaus at time of writiing) and add new node to same locations.
  2. Create a test policy as described here.
  3. Test the new policy on a representative set of machines, i.e., a login node and each type of worker node (PE1950, R610, etc.).
  4. Once you've confirmed the test policy works, update the T2 policies as described in the previous link.


  1. In a senna x2go session, open the browser and go to the website of the networks switch you plugged the ethernet cables into. Examples: msu-sw-112.msulocal
  2. Find the port numbers that you plugged the ethernet cables into (you should have written them down if you followed the instructions above).
  3. Go to VLAN membership and put the ports on either the public or private network (these should match what was put into cobbler).


  1. Turn on the new machine and see if it builds.
  2. Once it's finished building, let cfengine do its thing (which could take a few hours).
  3. In the meantime, change the root password to that in passpack. Use passwd, not kpasswd.
  4. Once cfengine is done, start testing out the node (except condor).
    1. Make sure it can see all the work disks.
    2. Make sure setupATLAS works.
    3. Make sure things run as you would expect.
  5. Once you've tested everything you can think of, start and test condor ( example).
  6. Once you are confident everything works, talk to Philippe about emailing the users.
-- ForrestPhillips - 12 Sep 2019
Topic revision: r1 - 12 Sep 2019, ForrestPhillips
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