ITTC Resources

ITTC Resources

Introduction

Welcome to the Information and Telecommunication Technology Center (ITTC).

Email

You can access your ITTC e-mail via IMAP, POP, or Webmail.

Webmail

Webmail allows you to access your e-mail using a web browser from any location in the world. You can use either Webmail or Webmail2. Webmail requires general authentication to access the login page. Please e-mail mailto:help@ittc.ku.edu to request the login and pass, if you do not already know it.

IMAP & POP

You can access your ITTC email through your favorite e-mail program using the secure IMAP or secure POP protocol.

• Incoming Configuration:

Server: mail.ittc.ku.edu
Type: IMAPS (port 993) or POPS (port 995)
Encryption: Required; This server requires an encrypted or secure connection using SSL or TLS.

• Outgoing Configuration:

Server: mail.ittc.ku.edu
Type: SMTPS (port 465)
Encryption: Required; This server requires an encrypted or secure connection for sending email.
Authorization: SMTP-AUTH must be used for authentication, allowing you to relay mail from anywhere on the Internet. SMTP-AUTH requires a secure connection (SSL or TLS) using either the LOGIN or PLAIN authentication method.

Pine with IMAP

Historically Pine has accessed e-mail from the mail spool. In order to user IMAP, you need to reconfigure your ~/.pinerc as follows:

  user-domain=ittc.ku.edu
  smtp-server=mail.ittc.ku.edu/ssl/novalidate-cert/user=YOURUSERNAME
  inbox-path={mail.ittc.ku.edu/ssl/novalidate-cert/user=YOURUSERNAME}inbox
  folder-collections="imap mail" {mail.ittc.ku.edu/ssl/novalidate-cert}[]
  default-fcc={mail.ittc.ku.edu/ssl/novalidate-cert}sent-mail

If you want to store your sent mail in the same folder as Webmail, then reconfigure your ~/.pinerc as follows:

  default-fcc={mail.ittc.ku.edu/ssl/novalidate-cert}Sent

Change ITTC Password

Visit https://password.ittc.ku.edu:600/password.html and follow the instructions there.

Wireless Access

A unsecure wireless network called "ITTC-guest" is available for all guests. The guest network should NOT be used by students. For all ITTC personnel, a secure WPA2 network is available. The network uses your username and password for authentication.

For Windows users, you can access the secure wireless by using the following settings (if available):

Network Name (SSID): ITTC-wpa2
Network Authentication: WPA2
Data Encryption: AES
EAP type: Protected EAP
Authenticate as computer when computer information is available: unchecked
Validate server certificate: unchecked
Authentication Method: Secure password (EAP-MSCHAP v2)
Automatically use my Windows logon name and password (and domain if any): unchecked
Domain: ITTCKU
Connect Even If the Network Is Not Broadcasting (SP3): checked

Additionally, For Windows 7 users:

Select user authentication from dropdown list, or reboot after configuring wireless network.
Login using your ITTC account information -- with the domain name included as part of your ITTC username (ITTCKU\username).

For OSX users, use the following settings:

Network Name: ITTC-wpa2
Wireless Security: WPA2 Enterprise
User Name: <your username>
Password: <your password>
802.1X Configuration: TTLS - PAP

For Apple iPhone users, please do the following:

1. Open MobileSafari (web browser) on your iPhone
2. Navigate to [1]
3. After you are redirected to the "Install Profile" screen, tap the button labeled "Install"
4. Don't worry if the Configuration Profile isn't "verified"
5. Enter your ITTC username, then tap "Next"
6. Enter your ITTC password, then tap "Next"
7. At the "Profile Installed" screen, tap "Done"
8. Return Home, then tap on the Settings app, then "Wi-Fi"
9. The public wireless networks should show up immediately, and after a few seconds the ITTC-wpa2 network should show up as well. Tap "ITTC-wpa2" to connect
10. Return Home, then tap on the Safari app and surf away! (Note, you may have to register your iPhone's MAC address with ITTC and then reboot the phone. Just follow the directions of any page you get redirected to)

For Linux users, please e-mail (help@ittc.ku.edu) for access.

Windows Terminal Server

If you are on the ITTC network, you can use a remote desktop client to connect to "win.ittc.ku.edu". If you need remote access, use one of the options below.

Remote Access

Two methods are available for accessing the ITTC network from external machines. Neither is enabled by default; both are available only upon request .

SSH

ITTC maintains a SSH gateway, ssh.ittc.ku.edu, which allows indirect access to machines in Raymond Nichols Hall. To access Linux machines, one first logs into the ssh server, then connects to the intended Linux machine from there. For more information, see http://www.ittc.ku.edu/remote/ .

Forwarding Ports

The above link automatically generates configuration files for Windows clients; for Linux clients, ports can be forwarded easily from the ssh command line using the following syntax:

ssh -p62 -Y <username>@ssh.ittc.ku.edu -L <localport>:<ittchost>:<remoteport>

to forward arbitrary ports ("remoteport") on machines in Nichols Hall ("ittchost") so they appear temporarily to be ports ("localport") on your personal machine.

VPN

A VPN connection works as though the remote machine was fully a part of the ITTC network. Since this carries additional risks, VPN access is now available *ONLY* with administrative approval. More information is available at http://www.ittc.ku.edu/remote/ .

Testbeds

Reserving Machines

You can check out systems at https://testbeds.ittc.ku.edu/checkout/index.php

Using the KVM

Presently, this procedure is intended for Microsoft Internet Explorer on win.ittc.ku.edu (email mailto:help@ittc.ku.edu if you need a login account for win), and only for testbeds 100-116:

1. Visit http://raritan in a web browser.
2. You will get a warning about the site's security certificate. Click Yes to accept the certificate and proceed.
3. A popup window will ask you for a username and password. Enter "testbeds" as your username, and "ittc2006" as your password, and click "Login".
4. Upon successful login, the resulting window will show a list of available testbeds in the left pane. Double-click the name of one of these testbeds to connect.
5. You should see the video output for the selected testbed, and keyboard and mouse activity will be forwarded through the web interface to the remote machine.
6. If you lose the display at any time, "Auto-sense Video Settings" under the "Video" menu can often successfully re-detect the display parameters.
7. When finished with the display, simply close the window(s) for the remote display, and select "Logout" from the "Session" menu at the list of testbeds. The system will log you out if your session is idle for a while.

Please forward any questions to help@ittc.ku.edu

Using the Remote APC PDU

In a web browser, go to: "http://testbed-power.ittc.ku.edu". The login is "testbeds" and the password is "Ittc2007!". Once logged in, you will be able to power cycle any node on the 8 outlet PDU.

RCS

RCS stands for Revision Control System. ITTC currently uses two, cvs and subversion.

GIT

Git is a free distributed revision control, or software source code management project with an emphasis on being fast. Git was initially created by Linus Torvalds for Linux kernel development.

All GIT repositories are located at "/projects/git".In order to access or view the repositories you need to have an ITTC account. To get a git repository send an email to help@ittc.ku.edu.

The following link is a tutorial on how to use git. [2]

CVS

CVS stands for Concurrent Versioning System. The purpose of CVS is both to store the history of the changes that are made to source files and to keep all the source files relating to the same project in one easy-to-reach location. This is extremely useful in situations where multiple people are working on the same project and a number of modifications are made to the same file by different people.

All CVS repositories are located in "/projects/cvs". A symlink exists for all pre-existing repositories from their original location to "/projects/cvs/[repo-name]". All group and user persmissions on the cvs repositories is set to "cvsd:cvsd". Local access to the files in the cvs repositories will not be available. If users need to access files in the repository, they will have to access them through the pserver connection.

• A CVS Quickstart Guide has been created to help introduce users to cvs.

Subversion

Subversion is a free/open-source version control system. That is, Subversion manages files and directories over time. A tree of files is placed into a central repository. The repository is much like an ordinary file server, except that it remembers every change ever made to your files and directories. This allows you to recover older versions of your data, or examine the history of how your data changed.

A subversion server resides on the primary public ITTC webserver. In order to access the subversion repositories, you need to have a ITTC user account. In addition, you need to be added to the svn-writer group. Email helpdesk@ittc.ku.edu to request addition to this group.

• You can browse through the subversion repository of your choice by going to https://subversion.ittc.ku.edu/<repo name>.

• A SVN Quickstart Guide has been created to help introduce users to subversion.

ViewVC

ViewVC is a browser interface for CVS and Subversion repositories. It generates templatized HTML to present navigable directory, revision, and change log listings. It can display specific versions of files as well as diffs between those versions.

• You can find viewvc at https://viewvc.ittc.ku.edu/viewvc.

Filesystem ACLs

ACLs are Access Control Lists for files and directories and are an addition to the standard Unix file permissions (r,w,x,-) for User, Group, and Other. ACLs give users and administrators flexibility and fine-grained control over who can read, write, and execute files. This can all be done without adding additional Unix groups. A ACL Guide has been created to help introduce users to the ACL tools and provides examples of usage.

Compiling Matlab

Matlab under Linux has the capability to be compiled. Once it is compiled the program runs like any other program under linux.

Compiling Matlab Cluster

• Cluster Usage: NOTE: You will need a cluster account to accomplish this.

Before doing this make sure that your code has the capability to checkpoint. Check pointing is used to save data periodically to the local disk. This gives your program the ability to restart from the last iteration instead of having to start over.

  #>mcc -m test_function.m
  The above command will compile the Matlab function into an executable with the same name.

  Create submission script Script Howto
  submit script to cluster
  #>qsub pbs_submit

Matlab is able to use multiple threads for many of its functions, and will automatically detect the number of cores on the system to use. Request a number of cores for your job in your pbs script and use the following command in your Matlab code to set the number of cores. See the maxNumCompThreads documentation from MathWorks

  LASTN = maxNumCompThreads(N)

When running multiple compiled Matlab programs simultaneously on the cluster, you will need to set the MCR_CACHE_ROOT to avoid interference between programs. Compiled Matlab programs unpack the MCR cache by default into the directory where they are executed. If this is a location on NFS, the cluster jobs will all use the same location and a single program may lock out other programs from using the MCR cache. Instead, set the MCR_CACHE_ROOT to a location in /tmp and remove the temporary directory when finished. In the following example, $RANDOM is a bash function that returns a random number.

  MCR_CACHE_ROOT=/tmp/mcr$RANDOM
  ./matlab_executable
  rm -rf $MCR_CACHE_ROOT

Compiling Matlab Compute Intensive Systems

• Bit Bucket Usage: NOTE: This works on all Linux systems except freestyle and benchmark

Adding checkpoint capabilities to your code is a very good idea before proceeding to the next steps. Since the "bit buckets" are used other users and could possibly crash, having the ability to start from the last iteration will make your life easier.

  #>mcc -m test_function.m

• Running compiled program

  #>./test_function&

• 64-bit usage (including freestyle and benchmark)

  #>/tools/matlab2006b/bin/mcc -m test_function.m

• Running compiled program

  #>./test_function&

Using Third Party Toolboxes

If you are using third party toolboxes (ex: FullBNT), you need to add the CPD directory to the CTF archive:

   #>mcc -a real1.m -a /some_directory/FullBNT-1.0.3/BNT/CPDs/

For more mcc options, refer to: http://www.mathworks.com/access/helpdesk/help/toolbox/compiler/mcc.html

Printing

ITTC Printers available for general usage:

Printer Name	Type	Room	Windows Neighborhood Name	Duplex Capable
Boiler	HP LaserJet 2200	240	\\spool\boiler	-
Crinkle	HP LaserJet 4050N	345	\\spool\crinkle	-
Crumple	HP LaserJet 4100N	148B	\\spool\crumple	-
Fade	Dell Color Laser 3110cn	144	\\spool\fade	-
Mailroom	HP LaserJet 4000N	146	\\spool\mailroom	-
Paperjam	HP LaserJet 4250DTN	227	\\spool\paperjam	Yes
Savin	Savin 9922DP	146	\\spool\savin	Yes
Shredder	HP LaserJet 4050N	247S	\\spool\shredder	-
Streak	HP LaserJet 2100	148	\\spool\streak	-
Tofu	Xerox Phaser 6250	240	\\spool\tofu	Yes

To access a printer for use, simply type "\\spool\printer_name" into your browser. Example: \\spool\crumple

Public Computer Lab

The public computer lab, in Room 148B, houses the following machines:

Computer Name:	Operating System:	IP Address:
Ash	Windows 7	129.237.122.104
Burner	Windows 7	129.237.122.100
Cedar	Windows 7	129.237.122.105
Fir	Windows Vista Enterprise	129.237.122.103
Oak	Windows 7	129.237.122.102
Accessible Remotely:
Xenon	RedHat Linux	129.237.121.95
Spruce	RedHat Linux	129.237.121.12
Redwood	RedHat Linux	129.237.120.240
Piggy	Cent OSx	129.237.121.164

Compute Intensive Systems

The following systems can be used for compute intensive tasks, e.g., matlab or cluster computing. Note that only one of these systems does not have a primary use. As we have always done, the other systems are available if not utilized by their primary use (i.e., there are available cycles) and in coordination with the listed contact.

Machine Name:	benchmark.ittc.ku.edu
Type:	Dual 3.2 Xeon EM64T with 4Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	freestyle.ittc.ku.edu
Type:	Quad 3.2 Xeon EM64T with 16Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	fusion.bioinfo.ittc.ku.edu
Type:	64 Dual 3.2 Intel Xeon x86_64 with 4Gb Ram per node
	64 Dual Dual 2.8 Intel Xeon x86_64 with 6Gb Ram per node
	48 Dual Quad 2.83 Intel Xeon x86_64 with 16Gb Ram per node
	32 Dual Quad 2.6 AMD Opteron x86_64 with 6Gb Ram per node
PI:	Victor Frost
Major Use:	bioinformatics, cluster computing
Contact:	Charles Henry
Access Method:	ssh
Machine Name:	berkelium.ittc.ku.edu
Type:	Dual 2.66 Xeon with 4Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	californium.ittc.ku.edu
Type:	Dual 2.66 Xeon with 4Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	einsteinium.ittc.ku.edu
Type:	Dual 2.66 Xeon with 4Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	fermium.ittc.ku.edu
Type:	Dual 2.66 Xeon with 4Gb Ram
PI:	Victor Frost
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	sentinel.ittc.ku.edu
Type:	Quad 2.0 Xeon with 16Gb Ram
PI:	Gary Minden
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	sentry.ittc.ku.edu
Type:	Quad 2.0 Xeon with 8Gb Ram
PI:	Gary Minden
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	minuteman.ittc.ku.edu
Type:	Quad 2.0 Xeon with 8Gb Ram
PI:	Gary Minden
Major Use:	ittc general computing system
Contact:	Mike Hulet
Access Method:	ssh
Machine Name:	frenzy.ittc.ku.edu
Type:	Dual 3.16 Xeon with 4Gb Ram
PI:	Charles Henry
Major Use:	Fermi CUDA capable computing
Contact:	Charles Henry
Access Method:	ssh

User File Storage

There are three shared filesystems at ITTC for user file storage.

• /users (1000 GB)
  • Contains all user home directories, which is your login directory on Unix systems and the H: drive on Windows systems. Your home directory is the place to keep all personal files and data.

• /projects (1000 GB)
  • Contains directories for ITTC projects. All project-related files and data should be placed in /projects. If you need a /projects directory created, contact help@ittc.ku.edu.

• /tools (500 GB)
  • Contains all ITTC installed Unix tools, applications and configuration information.

If you have a problem accessing any of these directories, or have questions about their appropriate usage, please contact help@ittc.ku.edu.

LaTeX Template

KU-compatible LaTeX template for thesis: http://intranet.ittc.ku.edu/assistance/thesisTemplateKU.tar.gz