Contents:

Racks

The racks are numbered from 1 to 4, left to right. They are labeled as such as of August, 2011.

ATCA Crates

The ATCA crates are numbered from 1 to 4, from bottom to top. Thus ShelfMgr4 refers to the shelf manager in the top-most (large) crate.

Patch Panel

The Rack 4 patch panel is cabled to panels mounted near the work benches. These cables can carry either network or serial (RS-232) traffic.

Bench

Port

ATLAS IBL

1 - 12

EXO

13 - 24

LSST

25 - 36

SLAC Network switch (Cisco) rtr-reg-l1

RCE Network switch (Foundry) reg-l1-rce

Switch port assignments

IP address assignments

Digi Powerserver RS-232 server

  • Model is Digi Portserver TS 16 MEI
  • Manual can be found here

New lab machine setup

Taylor workgroup: dat

Adding a new user

  • Issue training to the user on Lab 1 use. Points to make:
    • Avoid working in the room alone
    • Get, and keep current, appropriate electrical training
    • Get a ladder if you need to get up high
      • No climbing on chairs, tables, benches, etc.
      • A spotter must be present in order to use a ladder
    • No access to stuff not part of your project
    • Stay out of the racks unless access is really needed
      • High current sources present
    • No reconfiguration of computers
    • No reconfiguration of the network
    • Keep the work area clean
    • Avoid accessing Lab1 through the middle hallway door
    • Point out Dataflow Lab 1 Confluence page and have the user go over it
  • Introduce the user to Mike

  • Create a computer account for the user

    • For the old method, see /reg/common/tools/bin/addlabuser, etc.
      • This is obsolete as of 1/1/2012, now that we have moved to unix-admin style maintenance. However, it may still be needed for legacy set-ups.
      • On rdsrv100, issue:
        /reg/common/tools/bin/addlabuser <username>
        • Puts user in the appropriate groups, e.g., lab-users
        • Add --superuser to add the user to the sudo list, if necessary
      • If this fails with a 'User not found in ou=People...' message issue:
        /reg/common/tools/ldap-helpers/nis2ldap
        • Retry addlabuser
    • Add the account to the u-reg-lab1 netgroup (NIS) with a request to unix-admin
  • If the user is involved with RCE development (DAT, CTK, CCI, NPA, etc.):
    • Send a request to confluence-admin to add the user to the cci-confluence-editors group and get the user CCI JIRA privileges
    • Add the user to the g-npaAFS group, if necessary
      • Needed for NPA cvs/svn access, as in, e.g., ATLAS
    • Add the user to the g-cciAFS group, if necessary

      • Needed for RCE development svn access

        pts membership g-cci
pts adduser <username> g-cci
    • Add the user to the reg-lab1YP group, if necessary

      • Needed for certain Lab 1 NFS disk operations

        ypgroup exam -group reg-lab1
ypgroup adduser -group reg-lab1 -user <username>

    • Some dongles have udev rules that put the usb device into the group users

      • Add the user to the users group on the relevant host, if necessary

        sudo /usr/sbin/usermod -G users <username>

       

  • Add the account to the reg-lab listserv e-mail list (see below)
    • Send an e-mail to listserv with subscribe reg-lab <user>@SLAC.Stanford.edu in the message body
    • Can also add the user by going to listserv

List of authorized users

Lab 1 Announcements

  • No labels