Accessing SLAC Computers
Basic information for BABAR Collaborators regarding
obtaining a
SLAC Unix (and/or XP) account, accessing SLAC computers remotely, and
bringing computers to SLAC.
Last Updated: 03 Oct 2006
General Requirements for a SLAC Account
To get access to BABAR computing and directories at
SLAC, you
must go through the following steps which are
described in
more detail below (note that if you already have a SLAC Unix account
for some other reason, you must still check this list and perform any
needed actions to ensure access to BABAR-specific resources):
Other issues:
Windows account issues:
Objectivity access
Our contract with Objectivity requires that we limit access to the
database to bona fide collaborators who have read, agreed to, signed
and returned the license agreement. Access to Objy is controlled by an
access control list, thus this step must be completed prior to using
the database. The form is located here:
/BFROOT/doc/Computing/www/Tools/objectivity.html. This form should
be printed, signed and sent by mail or FAX to (650) 926-2657
Charlotte Hee:
Mail: Mail Stop 95, SLAC, 2575 Sand Hill Road, Menlo
Park, CA USA 94025
FAX: +1-650-926-2657 (If you have a question about a
FAX transmission, phone the Group C secretariat, Anna Pacheco,
at +1-650-926-2706).
You may send in the Objectivity Agreement at any time but access to
Objectivity will be granted after your computer account has been enabled.
SLAC Unix Account Forms
To get a user account on the SLAC Central Unix or
Windows
facilities you must first file an application. Application forms may
be obtained in one of two ways:
Request one at the Computer Center's Help Desk, 1st
floor,
building 50
Collect the documents via WWW: http://www2.slac.stanford.edu/comp/slacwide/account/account.html.
You
will need a PDF viewer. Follow the directions below for submitting
these forms.
In general, please follow the instructions on the SLAC
Account web page. BABAR-specific advice follows:
-
SLAC Computer Account Form (version of
1/23/2001)
- Your name (please print legibly in LARGE letters,
especially if you plan to FAX your application)
- Your SLAC office coordinates (if you have them)
- Your SID ID, if you know it. Do not worry if you do
not know your SID ID. This id will be filled in by the Helpdesk when
the account is created.
- Your off-site coordinates *** Please add your
off-site email address
- For your new account, check "Central UNIX" and
"Windows XP"
- Check "New Account" and fill in your requests for a
UserID (login
name).
- For email routing most users will wish to check
"Unix server".
NOTE: If you check "Exchange server", then you must also request
an "Exchange" account earlier on the form. Email received on the
Exchange server can be read by Netscape (via IMAP/SSL) or other
browser's email functions (or even a browser without special email
capabilities) and, thus, can be readily accessed via both Unix and
Windows operating systems. Configuring such an arrangement is beyond
the scope of this document but see this web page for more
information,http://www.slac.stanford.edu/comp/net/email/index.html
- Check "Additional instructions or special group
requirements" and
write "Please add to unix group bfactory"
- Do NOT sign the "Authorized Signature" area (and do
NOT have your
P.I. sign this form as it will be rejected)
-
If you are offsite (not at SLAC) and cannot pick up your account and password
information, write the word offsite on the "Additional instructions"
line. The information will be emailed to the address specified on
the request form (this should match the address in the database).
Otherwise the Helpdesk will hold your account information for pickup.
- Both the Account form and
the
Responsibilities form should be returned to Charlotte Hee or
Gregory Dubois-Felsmann for authorization. This can be done in person or via
fax, +1-650-926-2657. (If you have questions about the
transmission you may call the BABAR
Administration Office at +1-650-926-2363.) It can take several
business days from the time this occurs until an account is created.
- Once established, account information (userid and initial password)
may be picked up in person at the HELP Desk in building 50. You will need a
photo ID to get this information. Otherwise, SCS will either contact you by
telephone (if you are onsite) or send your account information in email. If
account information is sent by email the user will have 48 hours to change the
password otherwise it will be disabled and the user will have to contact the
HELP desk to have it reset.
You may wish to contact the HELP Desk if you don't hear from them in a
reasonable amount of time. For security reasons, you must change your
new, temporary password within 48 hours! Once the account has been created,
further questions should be directed to the
SCS HELP Desk, +1-650-926-HELP (926-4357), not the BABAR Administration
Office or the Group C secretariat.
Note: Slac usually closes during Christmas and New Year for about 2
weeks. All new account requests during this period must be
completed by the Wednesday before the shutdown. Any new accounts that
have exceeded the 48-hour time limit to change the password or have not
changed the password by 5pm of the Wednesday before the shutdown
(whichever comes first) will be disabled until after the shutdown.
New accounts that miss the deadline will be created after the shutdown.
Check that your SLAC Unix userid
is in the BABAR
database
Our AFS disk directories are made accessible to BABAR
users through
information stored in the BABAR database. To make this mechanism work
your SLAC Unix userid must appear in this database. Check to see
whether this information has been entered (and, if necessary, request
a correction) by bringing up your entry using the People
Search page, search for your own database entry, and then
clicking on the "submit a data correction to BABAR or PEP-II" link at
the bottom of the page.
Note that once you submit this correction email, someone
must
manually update the database, and then (around 0400 PT everyday) the
AFS access controls are updated. Thus, there will be a delay between
the time this correction is requested and the time you may
successfully access the BABAR code repositories. If you have a true
emergency and must access group directories, please contact Charlotte Hee, 926-3353.
Babar Publications Web Access
If you need more information regarding the Babar
Publications Database contact the BABAR
Administration Office.
Access to the BABAR Publications database requires an
Oracle account. BABAR participants may request an Oracle account (or
request password changes) by sending email to db-admin@slac.stanford.edu.
SLAC HyperNews Account
HyperNews
is a collection of discussion groups and is a primary communications
tool within BABAR. One may browse articles within individual groups
and respond to those articles within the context of a web browser.
All HyperNews groups also have mailing lists associated with them so
that for groups of interest, you may "subscribe" and thereby receive a
copy via email of each article submitted. Responses may also be made
via email.
Membership: Access to the HyperNews forums is
restricted
to BABAR members and associates. You will have to create a HyperNews
membership in order to have access. Once you have your SLAC UNIX
account, use ssh to login into
babar-hn.slac.stanford.edu. Instead of getting
your command
shell, you will be asked for information necessary to create your
HyperNews membership. This membership will have the same name as your
SLAC UNIX account, but you SHOULD NOT use your SLAC UNIX password for
important security reasons.
Bringing your computer to SLAC
Some advance preparation may be needed for your computer
to work
effectively at SLAC. Computers brought on site and connected to the
SLAC network must comply with current SLAC rules concerning OS type,
OS security patch level, OS configuration, disallowed servers
(e.g. web servers), etc. You are strongly advised to contact the User
Help Desk (926-HELP) for more information, and certainly BEFORE
making any connection to the SLAC network.
In addition, to operate meaningfully on the SLAC
network, you must
obtain a SLAC-specific IP address . There are two basic ways to handle
this.
Desktop machines and docking stations.
Once you
arrive on site, apply
for and install a new, fixed, SLAC-specific IP address. Each SLAC group
has
one or more people authorized to sign this form, a partial list
is the group of computing czars.
Stephen Gowdy and Charlotte Hee can sign for BABAR, Tom Glanzman for
Group EC, etc. Please select a person in your group or sponsoring
group.
Laptops. Laptops tend to fall into two
general
categories:
long-term laptops that "roam" around the SLAC
site
shot-term visitor laptops that are used primarily in
the
Auditorium or conference rooms
Long-term laptops
that need a wired network connection at multiple locations around the
laboratory, must register in advance for roaming DHCP
(Dynamic Host Configuration Protocol), a mechanism for dynamically
obtaining a "floating" IP address anywhere on site. Users may
register by sending the following information to the appropriate DHCP
czar for their workgroup (BABAR in this case). Other queries
should be sent to net-admin.
NOTE: To change an existing DHCP
registration,
e.g. if you replace your ethernet card, please send the information
below, along with your OLD hardware MAC addresses to net-admin only.
- MAC address for your computer, in a format
AA-BB-CC-DD-EE-FF or AA:BB:CC:DD:EE:FF (See this info on obtaining
your machine's MAC
address.)
- First Name, Last Name
- SLAC email address
- Your home institution
- [Computer Hostname] (if known)
- Property control number (for SLAC-owned
equipment)
- Name and phone of SLAC-employed contact person
who knows
how to reach you while onsite, e.g. your supervisor, manager, or
sponsor. BABAR visitors in the ROB may use Kathy Webb x2363;
SLAC employees use the name and phone number of your SLAC supervisor.
- Expiration date for this registration
(month/year)
- Operating system, version/service pack and
(where appropriate)
kernal version you plan to use with DHCP (e.g. WinXP SP1, Linux
RH7.2 kernel 2.4.9-13, etc.). On Unix/Linux systems, use the OS
identifier listed in the "uname -a" command. For Windows systems, get
this information from looking at "Properties" of "My Computer". On
Macs, use the "About this Computer" in the Apple menu.
- Read and Agree to SLAC Policy
and Security Guidelines contained on this page
Please provide ALL the requested information or your
email will be returned/ignored.
Alternatively, wireless (802.11b) connections
are also possible in a
growing number of locations around the laboratory, including the
Auditorium, various conference rooms, and the BABAR control room at
IR-2. Note that the wireless subnet is part of the visitor's
subnet, outside the SLAC firewall.
Wireless connections do not require advance
registration.
Short-term laptops have two options, wired
and wireless,
neither of which require advance registration -- but have some
restrictions.
Laptops may establish a wired network
connection in the SLAC
Auditorium (and a few conference rooms) via DHCP without first
being registered. The subnet serving the auditorium is the
visitor's subnet and is outside the SLAC
firewall.
Use an 802.11 wireless connection as described above.
This is
available only in selected public areas. This type of connection is
also outside the SLAC firewall.
Accessing SLAC computers
remotely
For security reasons, some of the older and insecure methods for
connecting (e.g. telnet) no longer work at SLAC. Various alternatives
for connecting are listed below (but this is not an inclusive list).
Use ssh for a terminal session to
interactive SLAC Unix machines (see http://www.slac.stanford.edu/comp/unix/public-machines.html
for a list of available machines)
FTP services are available at ftp.slac.stanford.edu
(see http://www.slac.stanford.edu/comp/unix/ftp.html
for more details)
To access Windows XP resources, you must use VPN
(Note: this page is visible only from SLAC machines.)
Check On Your Account
You may use the script chkuser to see if you have signed the
necessary software agreement and have the necessary account and
membership in order to run the BABAR software. You may type in a single
Slac Unixid or several Slac Unixids. From Unix,
issue the command chkuser userid
Some command examples:
chkuser chee
chkuser chee bartelt renata
Results:
UNIXID BFACT AFS BBR_COMM OBJECTIVITY
------------------------------------------------------------------
chee yes yes yes yes
bartelt yes yes yes yes
renata no yes no no
This page maintained by:
Charlotte Hee |