Vistec EBPG5200 Guide de démarrage rapide

Vistec Lithography Tel: +31 (0)499 336880

De Dintel 27a Fax: +31 (0)499 336899

5684PS Best eb-sales@vistec-semi.com

The Netherlands http://www.vistec-semi.com

EBPG5200 Linux

Workstation Notes

Document: Notes

EBPG5200 Linux Workstation Notes

Abstract

How to use and maintain the Linux Master Control Computer (MCC) for the EBPG5200

All reasonable steps have been taken to ensure that this publication is correct and

complete, but should there be doubt about any details, clarification may be sought

from Vistec Lithography Limited, or their accredited representative. Vistec

pursues a policy of ongoing product design improvements; the information in this

document is therefore subject to change without notice. No responsibility can be

accepted for any errors that may be present in this document.

or communicated to a third party without prior written permission of Vistec Lithography

Ltd.

Document: Notes

Date: 31-Jan-2014

Issue: 1

Author: René Pijnenburg

Printed in The Netherlands. This document is originally written in English.

Corrections and changes to this manual should be forwarded by email to:-

Lithography-manuals@Vistec-semi.com, Giving full details of the changes required.

Vistec Lithography manual Page i

EBPG5200 Linux Workstation Notes Notes

Table of Contents

1. Introduction......................................................................................1

1.1. Scope of this document ....................................................................................... 1

2. System specific information...........................................................2

3. How to use projects.........................................................................3

4. How to maintain BEAMS.................................................................4

4.1. Beams-script........................................................................................................ 4

4.2. Upgrading beams................................................................................................. 4

5. Documentation................................................................................. 5

6. Network ............................................................................................ 6

7. Raid 1 storage.................................................................................. 7

7.1. sas2ircu................................................................................................................ 7

7.2. Failing disk........................................................................................................... 7

8. Mail Setup.........................................................................................8

9. Linux Tools.......................................................................................9

10. Backup............................................................................................ 10

11. Linux (Re)Installation .................................................................... 11

11.1. Standard from a kickstart file ............................................................................. 11

11.2. Manual Linux installation ...................................................................................12

12. Vacuum Controller (RE)install...................................................... 14

12.1. Principle ............................................................................................................. 14

12.2. Create bootable USB stick.................................................................................14

12.3. Make the Automation PC USB stick bootable. .................................................. 15

12.4. Installation.......................................................................................................... 16

12.5. Trouble shooting................................................................................................ 17

13. Vistec access to the machine....................................................... 18

14. RGS................................................................................................. 19

14.1. RGS through a ssh tunnel ................................................................................. 19

15. Appendix A..................................................................................... 20

1. INTRODUCTION

The EBPG5200 Linux Workstation is configured in the way the Vistec engineers use it as

well. The advantage of this is that if any discussion is made with Vistec engineers, they

know where to find the files and eventually support is easier.

1.1. Scope of this document

This document explains how to work with the EBPG5200 Linux Workstation. This includes

the description of the users, how to use the applications, how to maintain these

applications and how to maintain the system itself.

Although explained the use of the applications, the functionality itself is not discussed.

However, the documentation of these applications is included on the system.

2. SYSTEM SPECIFIC INFORMATION

Table 1: System specific Information

Hardware

Base system

Z820

Storage

2*450GB RAID 1

Memory

8 GB memory

Swap

16 GB partition

Software

Operating System

Red Hat Enterprise Linux (RHEL) 6.4, 64bit

Beams

y09_06e

Network Information

Hostname

a217

Account Number

Subscription number

3c5d-1b38-3d51-631a

Redhat login name

Redhat password

User Information

root

beamwriter

beams

beamwriter

3. HOW TO USE PROJECTS

Beams commands make use of the environment variables which point to directories in

wherein to write files or wherefrom to read files. Directly after login, these environment

variables have default the next values:

PG_BIN="/home/pg/bin"

PG_JOBS="/home/pg/jobs"

PG_LOG="/home/pg/log"

PG_PATTERNS="/home/pg/patterns"

PG_SCRIPTS="/home/pg/scripts"

The default directory is the home directory: /home/pg, after the user ‘pg’ has logged in.

The ‘pg’ environment is created in the way that the ‘pg’-user can organize its data-files

into projects. This is organized with the tool ‘ce’ (change environment).

[pg@a217 pg]~> ce service

When the project “service” doesn’t exist, then “ce” asks for confirmation to create the

project. If the project already exist or when created by “ce” then the current directory

(pwd) is changed to:

/home/pg/users/service

Also the environment variables showed above, are changed into:

PG_BIN="/home/pg/users/service/bin"

PG_JOBS="/home/pg/users/service/jobs"

PG_LOG="/home/pg/users/service/log"

PG_PATTERNS="/home/pg/users/service/patterns"

PG_SCRIPTS="/home/pg/users/service/scripts"

There is also a file “.service” in the “service”-project directory which will be executed every

time the user executes “ce service”. You can include any command in this file to make a

default setup when this project is entered.

4. HOW TO MAINTAIN BEAMS

The user ‘beams’ owns all the beams-applications. The reason for this is that the ‘root’-

user is not required for updating beams. Thus when the beams applications has to be

upgraded, the ‘beams’-user has to be used.

4.1. Beams-script

A beams-script “beams” exists in the home-directory of user “beams”. With this script the

releases of beams can be maintained. This includes: downloading new beams releases,

installing/extracting releases and even downgrading.

Go to the “beams”-directory:

[beams@a217 ~]$ cd ~

In this directory the script “beams” can be executed:

[beams@a217 ~]$ beams

Usage:

beams <version> [-ghixs]

Type "beams --help" for detailed help.

As the bottom line says, type “beams --help”.

Read this detailed help carefully.

4.2. Upgrading beams

The usual action to start with an upgrade of “beams” is first looking for available releases

and what is installed on the system. The option “--show” does this all:

[beams@a217 ~]$ beams --show

Usually the last beams-release is the best beams-release. When a new “beams”-release

is available, e.g. “y09_07a”, install/upgrade it next to the other releases as follows:

[beams@a217 ~]$ beams y09_07a --get --install

Although a new beams-release can be got and installed in one action as shown above, it

is recommended to do it in two steps.

First get the release y09_07a from the Vistec ftp server:

[beams@a217 ~]$ beams y09_07a --get

Then extract and install beams-release y09_07a:

[beams@a217 ~]$ beams y09_07a --install

That is all to upgrade beams.

5. DOCUMENTATION

The distributions of “beams” include documentation files in html format and manual-

pages. To get a full list of available “pg” commands, enter next command:

[pg@a217 pg]~> man pg

For detailed help for a particular “pg” command see the header “SEE ALSO” in the above

manual page, e.g.:

[pg@a217 pg]~> man pg adjust

Also for the “hill-shelly” programming interface and “gpf” functions, manual pages are

available. Unfortunately a complete list of all “hill_shelly” functions is not available, but a

“hill-shelly” function can be found by appending a corresponding “pg” command after

“hill_”, e.g.

[pg@a217 pg]~> man hill_adjust

The list of “gpf” functions can be displayed by:

[pg@a217 pg]~> man gpf

For both of these types of functions see the header “SEE ALSO” to get detailed help for a

particular function.

Exactly the same text, but in html format is also available. A HTML-server is installed on

the workstation and the home page looks like:

In the left column reside the links to documentation on the local system. This home page

can be accessed from any computer system in the local network, by typing the correct

system name, known in the network, in the address bar of the browser, or typing the IP-

address of this system in the address bar. When on the local system, just type “localhost”

in the address bar of “mozilla” or “firefox” to get this home page.

See further the “beams”-documentation

6. NETWORK

When the system has to get other network settings for the Internet, execute:

[root@a217 ~]# nm-connection-editor

Then the next window appears on the screen:

To make changes to the Internet, only change the device “eth0”. Ask the local network

manager for the details to get system connected to the Internet.

NOTE: Never change the device “eth1”, otherwise the computer can’t communicate with

the machine anymore.

After changing the Internet settings, restart the network:

[root@a217 ~]# service network restart

NOTE: When a firewall is required then be sure the ports 69:udp and 20440:udp are

trusted or make eth1 entirely trusted. See:

[root@a217 ~]# system-config-firewall

Or:

[root@a217 ~]# system-config-firewall-tui

7. RAID 1 STORAGE

The system is delivered with a hardware RAID 1 implementation, which consists of one

controller on the motherboard and 2 450GB SAS-disks. These two disks make, together

one 450GB storage device. With RAID 1, a storage device contains 2 disks, which are

identical mirrored. Thus when one disk fails, then the other disk takes over the control of

the data.

The hardware RAID controller offers a storage device to the machine. This means that

the operating system (Linux) doesn’t see what physically is “behind” the controller. Thus it

only offers about 450GB of storage. Thus this means that the operating system: Linux,

can’t see what the real status is of the physical disks.

Although the utility: “kinfocenter”, supplied with RHEL distribution, is able to show the

disks behind the disk/raid-controller, it cannot see the status and the configuration of the

volume.

[pg@a217 pg]~> kinfocenter

7.1. sas2ircu

[root@a217 ~]# sas2ircu 0 status

LSI Corporation SAS2 IR Configuration Utility.

Version 15.00.00.00 (2012.11.08)

Background command progress status for controller 0...

IR Volume 1

Volume ID : 323

Current operation : None

Volume status : Enabled

Volume state : Optimal

Volume wwid : 0401f828ab027aaa

Physical disk I/Os : Not quiesced

SAS2IRCU: Command STATUS Completed Successfully.

SAS2IRCU: Utility Completed Successfully.

Manuels Ordinateur de bureau populaires d'autres marques

HP m9060n - Pavilion - Elite Fiche technique

Asus

Asus E210 Series Manuel utilisateur

Dell

Dell Inspiron 600m Manuel utilisateur

Dell

Dell Inspiron 3662 Manuel utilisateur

TotalFlow

TotalFlow uFLO Manuel utilisateur

HP Presario SV7000 - Desktop PC Manuel utilisateur

HP ProDesk 400 G5 Manuel

Logitech

Logitech MK320 Manuel utilisateur

Dell

Dell XPS 730 H2C Manuel utilisateur

Sony

Sony Vaio Series Manuel utilisateur

Sony

Sony VGC-LT32E - Vaio All-in-one Desktop Computer Manuel utilisateur

Alto

Alto MD 250 Manuel utilisateur

Lenovo

Lenovo ThinkCentre Edge 72 Manuel

Lenovo

Lenovo ThinkStation D20 Manuel

Arbor Technology

Arbor Technology FPC-7800 Series Manuel utilisateur

Sony

Sony VAIO VGX-TP1 Series Manuel utilisateur

Asus

Asus Eee Box B204 Manuel utilisateur

Dell

Dell Optiplex 9010 All In One Manuel utilisateur