eSilicon

GlobalDesign

Quickstart Guide

February 2006

Contents
Introduction and Overview ........................................................................................ 1 Using the GlobalDesign Portal .................................................................................... 2 Basic LSF Concepts .................................................................................................. 4 Using escad_lsf........................................................................................................ 6 Using xlsbatch ......................................................................................................... 7 Using bjobs ............................................................................................................. 8

Introduction and Overview

Welcome to the quick start guide for eSilicon GlobalDesign. GlobalDesign has been constructed to give a secure, seamless, integrated work environment to employees, consultants, vendors, suppliers and customers involved in ASIC design and manufacturing. It provides access to all relevant resources, artifacts and tools worldwide. GlobalDesign consists of 3 major components: a secure access portal, a centralized computing environment and job allocation based on established project and program priorities. (see Figure 1). GlobalDesign provides security with encrypted and authenticated access from a web browser or Virtual Private Network, VPN. Once you are connected to the portal, jobs are submitted and then executed on the computing array when resources are available.

GlobalDesign jobs are submitted to LSF which clones your environment and queues your job. Job execution is based upon the specified resource requirements when the job is submitted and queue management within the company. When all of the resources become available, LSF will configure the execution environment and run the job on the appropriate server(s). LSF applies your environment variables to your job and sets the OS and Tool paths accordingly.

Figure 1

The primary commands to submit and manage jobs are: escad_lsf A command-line UI to submit jobs using standard configurations for eSilicon design tools. xlsbatch A graphical UI to manage jobs. bjobs A command-line UI to manage jobs. Portal accessing ModelSim GUI from LSF Job

eSilicon GlobalDesign - Quickstart guide

Figure 2

Using the GlobalDesign Portal

Basic Portal Use
The GlobalDesign portal is available using Internet Explorer 6 (or greater) at http://globaldesign.esilicon.com. Communications with the portal are encrypted using 128bit SSL and allows authorized access to the eSilicon GlobalDesign facilities. You must log in to the portal using your assigned user name and password (see Figure 3). After entering those values, click the "Log In" button to proceed. If you enter your password incorrectly 3 times, your account will become disabled and you will need to contact eSilicon IT for assistance.

Figure 3

After logging in, the next screen will show a list of applications (see Figure 4) providing a full CDE desktop or a simple XTERM. Click on an icon to start an application. These application icons will provide you access to the front-end servers using a familiar Citrix display. You can reconnect to disconnected Citrix application sessions.

Figure 4

eSilicon GlobalDesign - Quickstart guide

Customizing the Portal

You can customize the User Interface by using the 2nd icon to the right of Applications.

Figure 5

Items that you may want to customize are the Window Size and Window Color Depth. Customizations are saved in your local computer and do not migrate to other computers. Note: If you use a XTERM, to avoid application session reconnection issues do not use seamless for the Window Size.

eSilicon GlobalDesign - Quickstart guide

Basic LSF Concepts

LSF is a load sharing facility which manages computing resources and makes sure they are available to the queued jobs using configured policies.

Basic Terms
Job A command submitted for execution. LSF queues, schedules, controls, and tracks the job according to configured policies. Job states The state of a job. Jobs have the following states: o PEND--Waiting in a queue for scheduling and dispatch. o RUN--Dispatched to a host and running. o DONE--Finished normally with an exit value (return code) of zero. o EXITED--Finished with an exit value (return code) other than zero. This generally indicates an error condition. o PSUSP--Suspended while pending. This usually means that the job was submitted on hold. o USUSP--Suspended by user. o SSUSP--Suspended by the LSF system. This usually means that the job was suspended to allow higher priority jobs to preempt this jobs execution. Queue A container for jobs. All jobs wait in queues until they are scheduled and dispatched to hosts. Queues do not correspond to individual hosts; each queue can use all server hosts in the cluster, or a configured subset of the server hosts. LSF dispatches the job to the best available execution host in the cluster. Execution Host The host where a job runs.

Basic Job Life Cycle

1. You submit a job from a Front-End server. Jobs are held in a queue waiting to be scheduled and have the PEND state. Job ID - LSF assigns each job a unique job ID when you submit the job. 2. The job is scheduled. a. LSF evaluates the jobs in the queue and makes scheduling decisions using: i. Job priority ii. Scheduling policies iii. Available resources b. LSF selects the optimal server(s) to run the job. 3. The job is dispatched for execution. 4. The job is run on the Execution Server(s). a. The job runs under the same account that submitted the job and has the status RUN. b. The execution environment is copied from the submission host to the execution host and includes the following: i. Environment variables needed by the job. ii. The Working directory is set based upon your current directory when you submit the job.

eSilicon GlobalDesign - Quickstart guide

iii. The Execution Host paths and other system-dependent environment settings are applied to the jobs execution environment. 5. The job completes. When a job is completes without any problems, the job is assigned the DONE status. If the job has errors which prevent the job from completing, the job is assigned the EXIT status. 6. The job output is sent to you. LSF returns the job output, job error, and job information to you in an e-mail or file. The details of this will be covered later.

eSilicon GlobalDesign - Quickstart guide

Using escad_lsf
The command-line utility escad_lsf is an eSilicon developed utility which will give you the ability to submit jobs to LSF. The most commonly used arguments should be familiar to you. For example: escad_lsf -t o_msim "vsim -gui". This will submit an LSF job which: Uses the default options for queue, required memory and required walltime. -t o_msim sets up the environment for modelsim on the execution host. vsim gui is the UNIX command that will be run after the modelsim environment is setup on the execution host. When you submit a job via escad_lsf: Your local environment, including DISPLAY is cloned. This environment is adjusted by the execution host where the job runs. You will receive an e-mail notification when the job starts and when the job completes. Job output will be in the completion e-mail unless you use the escad_lsf o option. If you do not have an eSilicon e-mail account, then you must use the u option to specify your email address. For example: escad_lsf u somebody@somecompany.com ... <other options> Other escad_lsf job examples: Setup the Magma 4.2.39 environment and run command mantle passing gui option to mantle escad_lsf -t magma_4.2.39 "mantle -gui" Setup the Magma 5.3.91 environment and run command blastfusion passing gui option to blastfusion escad_lsf -t magma_5.3.91 "blastfusion -gui"
Note: with Magma versions > 5, mantle gui does not function. You must use product invocations like blastfusion gui, blastplan gui, or blastcreate gui

Setup the primetime 0512 64-bit environment and run command pt_shell with primetime script commands in file run.pt. escad_lsf -t 0512_pts -64 pt_shell f run.pt
Note: when using multiple t setup options you need to place around the options.

Run a o o o o o

Calibre distributed processing MTFlex job requiring 8 cpus. The job needs 4 cpus and 26 GB RAM on the Master system. The job needs 4 additional slave cpus from 2 dual cpu system. Each slave system will require 10 GB RAM. The job will be limited to 28.5 hours of wall time. The job will use the drc deck /projects/lsfverify/athens/athens_drc.deck and save the drc output in drc-run.log.

escad_lsf -mastercpus 4 -m 26000 -slavesys 4:2:10000 \ -W 28:30 -multitool calibre -t "l_cal -64" \ "calibre -drc -hier -64 /projects/lsfverify/athens/athens_drc.deck > drc-run.log"
Note: using the multitool calibre instructs escad_lsf to generate the distributed processing configuration files and set the turbo options according to the systems selected by LSF. Support for multi-scenario primetime is also enabled in escad_lsf.

Help for using escad_lsf, including all command line options, is available by typing escad_lsf.

eSilicon GlobalDesign - Quickstart guide

Using xlsbatch
This application (see Figure 7) allows you to view all jobs and to manipulate your jobs in the system. You can view all jobs, checkpoint, suspend and terminate your jobs. The checkpoint operation is only supported by some tools. Queue administration is done by the Design Managers. They are authorized to use xlsbatch to manipulate all jobs. Jobs waiting to run can have their position in the queue altered or the job can be switched from one queue to another queue.

Figure 6

For more details on xlsbatch, see the online Help or man xlsbatch.

eSilicon GlobalDesign - Quickstart guide

Using bjobs
The bjobs command-line utility reports the status of LSF jobs. The bjobs command has various options to display the status of jobs in the LSF system. The functions of the bjobs command are also available via the xlsbatch application. Executing bjobs with no options specified displays information about your jobs in the PEND, RUN, USUSP, PSUSP, and SSUSP states. Running bjobs -l with a job ID displays all the information about a job, including: Submission parameters Execution environment Resource usage

Executing bjobs -p displays information for pending jobs (PEND state) and the reasons. There can be more than one reason why a job is pending. For more details on these or other bjobs options, see man bjobs.

eSilicon GlobalDesign - Quickstart guide