Page History

{anchor:Top}
*Contents:*
{toc}

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

h4. 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.

h4. 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 |

h4. SLAC Network switch (Cisco) {{rtr-reg-l1}}
* [mailto:net-admin]
* [mailto:Antonio Ceseracciu <antony@slac.stanford.edu>]
* [Switch status and configuration|http://www-lanmon/current.cgi?rm=ports&device=rtr-reg-l1]

h4. RCE Network switch (Foundry) {{reg-l1-rce}}
* Management of the Foundry FastIron Workgroup X448 (FWSX448) is provided by our group
* [Foundry switch commands]
* Foundry manuals of varying ages can be found [here|http://www.foundrynet.com/ss/prod-manuals/] or other places on the net:
** [Foundry FastIron Stackable Hardware Installation Guide|http://www.andovercg.com/datasheets/foundry-fastiron-stackable-hardware-installation.pdf]
** [Foundry FastIron X-Series Configuration Guide|http://www.roedie.nl/downloads/foundry/Foundry_FastIron_User_Guide.pdf]
** [Foundry Switch and Router Installation and Basic Configuration Guide|http://www.systechsolutions.info/dd/Foundry%20-%20Foundry%20switch%20and%20router%20installation%20and%20basic%20configuration%20guide.pdf]
** [Foundry Enterprise Configuration and Management Guide|http://www.foundrynet.com/services/documentation/wlan_config/pdfs/wlan_config.pdf]
** [Foundry Security Guide|ftp://ftp.seawatch.org/pub/ftp.foundrynet.com/release/Bigiron/8000b/manual/Security.pdf]
** [Foundry Switch and Router Command Line Interface Reference|ftp://ftp.seawatch.org/pub/ftp.foundrynet.com/release/Bigiron/8000b/manual/SRCLI.pdf]
** [Foundry Diagnostic Guide|ftp://ftp.seawatch.org/pub/ftp.foundrynet.com/release/Bigiron/8000b/manual/SRDiag.pdf]
** [Foundry Management Information Base Reference|http://www.foundrynet.com/services/documentation/MIB/MIB_Aug2008_Reference.pdf]
** [Release Notes for the FastIron Workgroup Switch X-Series|http://www.roedie.nl/downloads/foundry/FESX03001cRelNotes.pdf]

h4. [Switch port assignments]

h4. [IP address assignments]

h4. [Digi Powerserver RS-232 server|Powerserv RS-232 server]
* Model is Digi Portserver TS 16 MEI
* Manual can be found [here|http://ftp1.digi.com/support/documentation/9028700c.pdf]

h4. [New lab machine setup|New RDUSR1* machine setup files]

h4. Taylor workgroup: {{dat}}

h4. Procedure for adding a user to the list of authorized Lab 1 users
* Issue training to the user on Lab 1 use.  Points to make:
** No access through middle hallway door
** No access to stuff not part of the user's project
** Stay out of the racks unless the user really needs access
*** High currents present
** No reconfiguration of computers
** No reconfiguration of the network
** Keep the place clean
** Point out [Dataflow Lab 1] Confluence page and have the user go over it
* Create a computer account for the user
{panel}
* *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}}
{panel}
** Add the account to the {{u-reg-lab1}} netgroup (NIS) with a request to {{[unix-admin|mailto:unix-admin@SLAC.Stanford.edu]}}
* 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-npa}} AFS group, if necessary
*** Needed for NPA cvs/svn access, as in, e.g., ATLAS
** Add the user to the {{g-cci}} AFS group, if necessary
*** Needed for RCE development svn access
* Add the account to the {{reg-lab}} listserv e-mail list (see [below|#EMailList])
** Send an e-mail to {{[majordomo|mailto:listserv@SLAC.Stanford.edu]}} with {{subscribe reg-lab <user>@SLAC.Stanford.edu}} in the message body

h4. [List of authorized users]

{anchor#EMailList}
h4. [Lab 1 Announcements|mailto:reg-lab@listserv.slac.stanford.edu]
* Listserv list name: [*REG-LAB*|https://listserv.slac.stanford.edu/cgi-bin/wa] (slaconly)
* Administration: [REG-LAB-ADMIN|https://listserv.slac.stanford.edu/cgi-bin/wa] (slaconly)
* List FAQ: [http://www2.slac.stanford.edu/comp/messaging/Reference/listserv-faq.htm]
* General help: [listserv|https://portal.slac.stanford.edu/info/maillist/Pages/owner.aspx] (slaconly)