https://clonwiki0.jlab.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=129.57.167.42CLONWiki - User contributions [en]2026-04-09T08:00:01ZUser contributionsMediaWiki 1.42.1https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5756GE XVB6012012-02-22T19:08:21Z<p>129.57.167.42: /* List of boards */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
== Module manufacturer information ==<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
Documentation: <br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf Datasheet]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf Hardware Reference]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Transition Module Installation Guide]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Product Configurations]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br />
<br />
== List of boards ==<br />
<br />
* [01] 00:20:38:04:23:5E / 129.57.68.88 / croctest1 (curently: 129.57.68.xx / hps1)<br />
<br />
* [02] 00:20:38:04:23:60 / 129.57.68.90 / croctest3 (curently: 129.57.68.xx / hps2)<br />
<br />
* [03] 00:20:38:04:29:2E / 129.57.68.68 / tage<br />
<br />
* [04] 00:20:38:04:23:64 / 129.57.68.86 / tage2<br />
<br />
== Initial settings ==<br />
<br />
Install new board into VME crate. Connect ethernet to the upper LAN port, rs232 9600N1 serial line (optional), VGA monitor and USB keyboard. Turn on power, setup page should appear (for future reboots hold '''DEL''' key to enter setup). Goto '''Advanced->Onboard Device''', set memory size to '''512MB''' and enable '''Onboard Gigabit LAN 1'''. Goto '''Advanced->Serial Port Console Redirection''', enable '''COM1 Console Redirection''' and in '''Console Redirection Settings''' set '''Bits per second=9600'''. Do '''Save & Exit'''.<br />
<br />
Sergey Boyarinov only: open web browser from '''clonweb''' and goto '''jnet.jlab.org'''. Login using CUE login and password. Click on '''Machine Registration''' button. Click '''Add Device'''. Fill in a form, for example:<br />
Connection Type: wired<br />
MAC address: 00:20:38:04:23:64<br />
VLAN: VLAN 568 : Hall B Data Acquisition <choose from the list><br />
Hostname: tage2.jlab.org<br />
IP address: 129.57.68.86 <unselect 'Automatically Assign Statis IP><br />
JLAB Username: boiarino<br />
Has PII: no<br />
Machine Type: other<br />
Property Tag: F<br />
Click '''Submit'''. Following message must shows up:<br />
The device (00:20:38:04:23:64) has been successfully added to the registration table.<br />
-----------------<br />
The device (00:20:38:04:23:64) has been successfully added to the assignment table.<br />
-----------------<br />
(DHCP) This entry will be added to DHCP the next time the server restarts (about 10 seconds).<br />
-----------------<br />
hallb-rtr.jlab.org ethernet8/9 is not an access port, blip failed...<br />
<br />
Add IP name to the [[clonfs1]] export list, if not done yet.<br />
<br />
Recycle power. Messages on monitor must show successful DHCP connection. Go to the following section to setup TFTP etc.<br />
<br />
== Software structure description ==<br />
<br />
* following is installed in ''/tftpboot'' area on clon10 server:<br />
<br />
linux-install/Centos5PAE_new/initrd.img<br />
/initrd.img.backup<br />
/vmlinuz<br />
/msgs/boot.msg<br />
/expert.msg<br />
/general.msg<br />
/param.msg<br />
/rescue.msg<br />
/snake.msg<br />
/pxelinux.0<br />
/pxelinux.cfg/81394458 -> croctest1<br />
/81394459 -> croctest2<br />
/croctest1<br />
/croctest2<br />
/default<br />
/pxeos.xml<br />
<br />
Every client must has a file in ''/pxelinux.cfg/'' area with the name containing IP address in HEX format, for example croctest1's IP is 129.57.68.88, so file name must be 81394458. It can be a symbolic link. The contents of the file for croctest1:<br />
<br />
default Centos5PAE_new<br />
label Centos5PAE_new<br />
kernel Centos5PAE_new/vmlinuz<br />
append initrd=Centos5PAE_new/initrd.img root=/dev/ram0 init=disklessrc NFSROOT=129.57.167.16:/vol/diskless/Centos5 ramdisk_size=31809 ETHERNET=eth0 SNAPSHOT=croctest1.jlab.org NISDOMAIN=CCCHP acpi=force vga=0x305 vmalloc=256MB console=ttyS0,9600<br />
<br />
All settings in that file are more or less generic. To customize it for another client only ''SNAPSHOT=croctest1.jlab.org'' must be changed. Statement ''NFSROOT=129.57.167.16:/vol/diskless/Centos5'' defines the fileserver IP and directory where diskless Linux is located, in our case it is ''clonfs1''. Statement ''console=ttyS0,9600'' force Centos5 to send boot messages to the com port so they can be monitored using ''tsconnect''.<br />
<br />
* diskless Linux is installed on ''clonfs1'' fileserver in ''/vol/diskless/Centos5'' volume. That volume is mounted on the clonpc3 RHEL machine as well, and all Centos5 installation was performed on clonpc3, as it described in EXPERT PART section below. Directory ''/diskless/Centos5/root'' will be mounted as ''/'' level on all diskless clients, so that part is generic for all clients. Custom areas in ''/diskless/Centos5/snapshot'' will be client-specific, for every new client new directory with appropriate name must be creates there using templete tar ball, for example:<br />
tar xvf templete.jlab.org.tar<br />
mv templete.jlab.org croctest1.jlab.org<br />
* File ''files'' contains the list of all files/directories to be used from snapshot area rather then from root area, that file was created during Centos5 installation. File ''files.custom'' can be used to specify additional files/directories, not in use right now.<br />
<br />
== Customizing kernel installed in ''/diskless/Centos5/root'' ==<br />
<br />
After expert installation is done, following changes must be applied. They are similar to the RHEL installation on clon cluster PCs and servers:<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
'''NOTE''': to add new used you may use command ''useradd'', for example<br />
useradd -u 6246 -g nagios -d /home/nagios -c "Nagios" -s /bin/tcsh nagios<br />
(add flag '-m' if want to force home directory creation).<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
To install updates, ssh to clonpc3 as ''root'' and start chroot environment: ''chroot /misc/diskless/Centos5/root''. After that you can use ''yum'', for example:<br />
yum install gcc-c++<br />
yum install mysql-devel<br />
yum install compat-gcc-34-g77<br />
yum install libXpm-devel<br />
yum install libXtst<br />
yum install java<br />
<br />
In case of yum, rpm etc problems usually you have to rebuild dictionary, google the error message.<br />
<br />
== EXPERT PART: setting everything from scratch using clonpc3 ==</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Linux_Installation_Procedure&diff=5606Linux Installation Procedure2011-11-13T02:17:12Z<p>129.57.167.42: </p>
<hr />
<div>== RHEL6 ==<br />
<br />
Installed using CD provided by Computer Center. Requires MAC address to be registered with Computer Center (using jnet.jlab.org as 'boiarino') because it is network-based installation.<br />
<br />
'''NOTE: all disks will be reformatted in a process, all information will be lost !'''<br />
<br />
Dialog:<br />
<br />
* boot: <enter><br />
<br />
* ...[D]esktop: <enter><br />
<br />
* root password: enter root password<br />
<br />
* admin user: boiarino<br />
<br />
Installation will proceed. When prompted, remove installation disk and reboot machine if not done automatically. After reboot patching process will be started and it will take a while, do not interrupt it, otherwise system will not be installed correctly.<br />
<br />
<br />
== RHEL5 ==<br />
<br />
Installed using CD provided by Computer Center. Requires MAC address to be registered with Computer Center (email to helpdesk@jlab.org) because it is network-based installation.<br />
<br />
Dialog:<br />
<br />
* boot: <enter><br />
<br />
* ...[D]esktop: Server (it is ignored, will do Desktop anyway ...)<br />
<br />
* root password: enter root password<br />
<br />
* system user: <enter><br />
<br />
* manually partition disk: 100MB /boot, 2048 etc MB swap, the rest /.<br />
<br />
'''CFENGINE''': there are procesess restoring some system config files (in particular ''/etc/ssh/sshd_config'') in according to the Computer Center - maintained templete. To shut them down comment out ''cfengine''-related stuff in root cronjobs and do ''/etc/init.d/cfengine stop''. To stop it permanently, do ''chkconfig cfengine off''. Ask CC (Sherman White, Paul Letta) to fix templete.<br />
<br />
Run ''/usr/bin/system-config-authentication'' and set NIS servers list as ''clon00,clon10,nis1''.<br />
<br />
Add following in the end of ''/etc/passwd'':<br />
clasrun:x:2508:9998:Online DAQ:/home/clasrun:/bin/tcsh<br />
clascron:x:6005:146:CLAS Cron Jobs:/home/clascron:/bin/tcsh<br />
nagios:x:6246:9997:Nagios:/home/nagios:/bin/tcsh<br />
+@clon_cluster::::::<br />
+@ccc::::::<br />
<br />
Add following in the end of ''/etc/group'':<br />
perl::9999:freyberg<br />
onliners::9998:heyes,hujl,rwm,timmer,wolin,taylorw,cuevas,abbottd,abulafia,anciant,anghi,aswin,auger,avakian,banta,barrow,battagli,bjlee,bogdan,brooksw,bruhwel,boiarino,buckle,burchesk,burin,bzh,cetina,chen,cole,cords,corvi,costy,davidl,costy,davidl,dcarter,dcurry,dennisl,deppman,dhlee,doughty,drago,dytman,dugger,dugger,elton,fedro,ficenec,fklein,france,freyberg,gholden,gilfoyle,golovach,gurjyan,haddock,heddle,jenkins,jhardie,jmorris,kellyk,klusman,kmkim,kossov,lcsmith,longhi,manak,marchand,marki,mastersj,mjohnson,mosbackr,mueller,muguira,murphyl,necaise,odonnell,opper,parkkj,pasyuk,phkim,piot,riccardi,richardt,ripani,rossi,saw,sergpozd,serov,sholt,staylor,taiuti,tang,tedeschi,vineyard,vlassov,vvsap,weygand,wooyoung,burchesk,clasrun,giovanet,clasboot,clascoda,clasroot,clasmail,clascron,trigger,epics,southern,carstens,ccutter,danagu,heyes,huertas,jacobsg,kliv,lachniet,mestayer,primex,nerses<br />
clon::383:clascoda,clascron,clasmail<br />
nagios::9997:nagios<br />
<br />
Create ''/etc/shadow'' files with entries for users clasrun, epics and nagios (copy from another machine).<br />
<br />
Install updates: normally all updates should be installed by now, it can be done manually by commands<br />
yum list updates<br />
yum update<br />
<br />
Configure [[SSH]].<br />
<br />
Install missing packages:<br />
yum install openmotif-devel xinetd mysql-devel<br />
<br />
Some additional packages on request (for EPICS):<br />
<br />
yum install mc lapack lapack-devel blas blas-devel giflib-devel<br />
<br />
Proceed to the [[Linux Customization on CLON Cluster]].<br />
<br />
'''PROBLEMS''':<br />
<br />
1. /usr/lib/libg2c.so link is missing<br />
<br />
FIXED ??? 2. /usr/lib/libXm.so link is missing<br />
<br />
3. Created /etc/shadow file for clasrun, epics and nagios<br />
<br />
== RHEL4 ==<br />
<br />
Get RHEL4 CDs from Paul Letta.<br />
<br />
Connect terminal, keyboard and mouse.<br />
<br />
Boot from CD1. Follow instructions. When asked, choose following options:<br />
<br />
* Choose 'Manually partition with Disk Druid', set /boot to 100MB, then / to 40GB, then swap to 8192MB or at least double memory size. The rest of disk can be set as /space.<br />
<br />
* Network: choose manually, type clonpc2.jlab.org; click 'EDIT', deactivate 'Configure using DHCP',<br />
type IP address and netmask (255.255.255.0), click Ok.<br />
Type Gateway (for example 129.57.167.99) and 3 DNS servers (129.57.167.5,129.57.167.14,129.57.32.100).<br />
<br />
* Choose 'No firewall'<br />
<br />
* Disable 'SELinux'<br />
<br />
* Choose 'Customize software packages to be installed', click 'Everything'.<br />
<br />
You will be asked to install CD2, CD3 and CD4, then CD1 again.<br />
Then you will be asked to click 'Reboot'. First remove CD, then click 'Reboot'.<br />
You will be asked few more questions. When asked to activate service, choose<br />
'Tell me why I need to register ..' and click 'Next'. Choose 'I can not complete registration ..'<br />
and click 'Next'. You will see 'System user' screen, click 'Use network login..'.<br />
Choose 'Enable NIS support' and click 'Configure NIS'. Type NIS Domain: 'CCCHP' and NIS Server: clon00.jlab.org.<br />
Finish installation process.<br />
<br />
* fix files ''/etc/passwd'', ''/etc/shadow'' and ''/etc/group'' adding clasrun etc (see examples on another machines).<br />
<br />
'''NOTE''': if machine has multiple network ports, Linux may not assign them properly to specified IP names and addresses. If problem occures, open network GUI and delete all existing records. After that, click ''New'' and pick hadrware port you want to configure from the list of available ports (tricky part is to know which RJ-45 connector corresponds to which port ..). Configure and activate it, make sure it works. Repeat for other ports. Results will be stored in directory ''/etc/sysconfig/network-scripts'', file names will be ''ifcfg-eth0'', ''ifcfg-eth1'' etc. If modifying those files manually, restart network by ''/etc/init.d/network restart''. Finally, set routing, for example for ''clonmon'' command ''route -n'' shows following:<br />
Kernel IP routing table<br />
Destination Gateway Genmask Flags Metric Ref Use Iface<br />
129.57.160.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1<br />
129.57.68.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3<br />
129.57.69.0 0.0.0.0 255.255.255.0 U 0 0 0 dev5937<br />
129.57.64.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0<br />
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3<br />
0.0.0.0 129.57.68.100 0.0.0.0 UG 0 0 0 eth3<br />
Run following commands:<br />
/sbin/route add -net 129.57.160.0 netmask 255.255.255.0 gw 129.57.160.5 dev eth1<br />
/sbin/route add -net 129.57.68.0 netmask 255.255.255.0 gw 129.57.68.26 dev eth3<br />
/sbin/route add -net 129.57.69.0 netmask 255.255.255.0 gw 129.57.69.206 dev dev5937<br />
/sbin/route add -net 129.57.64.0 netmask 255.255.255.0 gw 129.57.64.57 dev eth0<br />
Now ''route -n'' shows following:<br />
Kernel IP routing table<br />
Destination Gateway Genmask Flags Metric Ref Use Iface<br />
129.57.160.0 129.57.160.5 255.255.255.0 UG 0 0 0 eth1<br />
129.57.160.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1<br />
129.57.68.0 129.57.68.26 255.255.255.0 UG 0 0 0 eth3<br />
129.57.68.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3<br />
129.57.69.0 129.57.69.206 255.255.255.0 UG 0 0 0 dev5937<br />
129.57.69.0 0.0.0.0 255.255.255.0 U 0 0 0 dev5937<br />
129.57.64.0 129.57.64.57 255.255.255.0 UG 0 0 0 eth0<br />
129.57.64.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0<br />
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3<br />
0.0.0.0 129.57.68.100 0.0.0.0 UG 0 0 0 eth3<br />
In that example automount will do configured using ''clonmon-daq1'' interface, because default ''clonmon'' interface is on external subnet. To make that routing table permanent (retore it after reboot) I tried to add four files with following contents to the ''/etc/sysconfig/network-scripts'' directory:<br />
route-eth1:<br />
GATEWAY0=129.57.160.5<br />
NETMASK0=255.255.255.0<br />
ADDRESS0=129.57.160.0<br />
route-eth3:<br />
GATEWAY0=129.57.68.26<br />
NETMASK0=255.255.255.0<br />
ADDRESS0=129.57.68.0<br />
route-dev5937:<br />
GATEWAY0=129.57.69.206<br />
NETMASK0=255.255.255.0<br />
ADDRESS0=129.57.69.0<br />
route-eth0:<br />
GATEWAY0=129.57.64.57<br />
NETMASK0=255.255.255.0<br />
ADDRESS0=129.57.64.0<br />
It did not worked. Then I added four ''/sbin/route add ..'' lines to ''/etc/rc.local'' script, and it worked.<br />
<br />
From now on you can use remote 'ssh' connection.<br />
<br />
* To configure your system to use the patch server, issue the following commands as root:<br />
# mount jlabsite:/site /mnt<br />
# /mnt/CC/linux/satellite-connect --patchall<br />
The script will prompt you for an activation key, but if you don't know what this is, just hit ENTER and it will use a sensible default. Depending on how many patches need to be applied to your system to bring it up to the current level, this script may take a very long time to run. When it finishes, you should reboot your machine to make the new patches take effect.<br />
<br />
To install updates later run ''up2date -uf'' as ''root''.<br />
<br />
Configure [[SSH]].<br />
<br />
* Proceed with [[Linux Customization on CLON Cluster]] if applicable.<br />
<br />
To boot Linux in single user mode (no graphics), add ''single'' to the end of boot line during boot process.<br />
<br />
<br />
<br />
== '''background info''' ==<br />
<br />
'''Add startup script'''<br />
<br />
Create script in ''/etc/init.d/'' directory (use existing scripts as example). Must have a line like<br />
# chkconfig: - 91 09<br />
which specifies start and stop order. Run commands<br />
chkconfig --add <scriptname><br />
chkconfig --level 3 <scriptname> on<br />
for every level you want that script to be executed (usualy 3 and/or 4 and/or 5). Check if it os done using command<br />
chkconfig --list | grep <scriptname><br />
<br />
<br />
'''xxx'''<br />
<br />
You can choose to download the RHEL operating system directly from the Red Hat Web site and not receive a media kit from HP containing the software. This scenario occurs when the media option AJR is deselected from the order. (The media kit option is always selected by default. )<br />
<br />
It is necessary to register at the Red Hat Web site prior to download. Registration requires the activation code that each customer receives from HP when ordering either RHEL.<br />
<br />
You can download RHEL for each available platform as four CD ISO images or one DVD ISO image.<br />
<br />
Use the following procedure to download RHEL and create the installation media:<br />
<br />
1.<br />
<br />
Register and log in at the following Red Hat Web site:<br />
<br />
www.redhat.com/rhn<br />
2.<br />
<br />
Click on channels and then select Red Hat Enterprise Linux ES (v.4 for 64–bit Intel Itanium).<br />
3.<br />
<br />
Select Downloads and then download the ISO images of install, compatibility and source disks<br />
<br />
Files with ia64 in the name are for the Itanium platform.<br />
4.<br />
<br />
Create the CDs or a DVD from the ISO images.<br />
<br />
<br />
IMPORTANT: Create the CDs or DVD using the contents of the ISO images. Do not create the CDs or DVD by burning the .iso files themselves to CD or DVD. For example, if you are using K3b to burn a CD, click Tools>CD>Burn CD Image, select the .iso image, then click Burn.<br />
<br />
'''Bootup scripts''' for example for level 5 execution (multiuser with X):<br />
<br />
cp <script-file> /etc/init.d/<br />
chmod +x /etc/init.d/<script-file><br />
ln -s /etc/init.d/<scriptfile> /etc/rc.d/rc5.d/S50<scriptfile><br />
ln -s /etc/init.d/<scriptfile> /etc/rc.d/rc5.d/K50<scriptfile><br />
<br />
<br />
'''Changing hostname/IP address'''<br />
<br />
Changing hostname on RHEL<br />
1. Change the HOSTNAME line in /etc/sysconfig/network<br />
2. Change the hostname (FQDN and alias) in /etc/hosts<br />
3. Run '/bin/hostname new_hostname' for the hostname change to take effect immediately.<br />
4. Run '/sbin/service syslog restart' for syslog to log using the new hostname.<br />
A reboot is not required to change the system hostname.<br />
<br />
IP address: You have to change the IP address entry in<br />
/etc/sysconfig/network-scripts/ifcfg-eth0.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonusr1&diff=5605Clonusr12011-11-13T01:59:42Z<p>129.57.167.42: Created page with "Supermicro SuperServer 8042 under RHEL, tag F418161, eth0: /129.57.167.108"</p>
<hr />
<div>Supermicro SuperServer 8042 under RHEL, tag F418161, eth0: /129.57.167.108</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonusr2&diff=5604Clonusr22011-11-13T01:57:16Z<p>129.57.167.42: </p>
<hr />
<div>DELL Precision R5400 server under RHEL, tag F424383, eth0: 00:25:64:90:B9:E5/129.57.167.48, eth1: 00:25:64:90:B9:E6</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonusr3&diff=5603Clonusr32011-11-13T01:56:44Z<p>129.57.167.42: </p>
<hr />
<div>DELL Precision R5400 server under RHEL, tag F424385, eth0: 00:25:64:90:B7:B4/129.57.167.49, eth1: 00:25:64:90:B7:B5</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonusr3&diff=5602Clonusr32011-11-13T01:48:18Z<p>129.57.167.42: Created page with "DELL Presicion R5400 server under RHEL, tag F424385, eth0: 00:25:64:90:B7:B4/129.57.167.49, eth1: 00:25:64:90:B7:B5"</p>
<hr />
<div>DELL Presicion R5400 server under RHEL, tag F424385, eth0: 00:25:64:90:B7:B4/129.57.167.49, eth1: 00:25:64:90:B7:B5</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=5601CLON Index2011-11-13T01:38:11Z<p>129.57.167.42: </p>
<hr />
<div>[[akcp]] temperature/humidity etc sensors<br />
<br />
[[Apache]]<br />
<br />
[[automounts]]<br />
<br />
[[Bertan MWPC]] High Voltage Power Supplies<br />
<br />
[[Bootp]]<br />
<br />
[[Cacti]]<br />
<br />
[[CAEN A464]] caenet board (installed in sy527 mainframes)<br />
<br />
[[CAEN A1733 A1833]] 12/28 ch. 3kV/3mA, 4kV/2mA High Voltage Boards ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br />
<br />
[[CAEN A1932A]] 48 ch. 3kV 500uA High Voltage Board ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br />
<br />
[[CAEN SY1527 Mainframe]]<br />
<br />
[[CAEN SY527 Mainframe]] and modules<br />
<br />
[[CAEN V1190]] TDC board (128 ch 100 ps)<br />
<br />
[[CAEN V1290]] TDC board (32 ch 25 ps)<br />
<br />
[[CAEN V1495]] General Purpose VME Board<br />
<br />
[[CAEN V1720]] Flash ADC VME Board<br />
<br />
[[CAEN V288]]<br />
<br />
[[CAEN V560]] scaler board<br />
<br />
[[CAEN V775]] TDC Board<br />
<br />
[[CAEN V792]] ADC Board<br />
<br />
[[CAEN V895]] 16 ch. Leading Edge Discriminator with individual thresholds<br />
<br />
[[Capfast]]<br />
<br />
[[Cisco Switches]]<br />
<br />
[[Clasweb]]<br />
<br />
[[Clasxt]]<br />
<br />
[[Clon00]]<br />
<br />
[[Clon01]]<br />
<br />
[[Clon02]]<br />
<br />
[[Clon03]]<br />
<br />
[[Clon04]]<br />
<br />
[[Clon05]]<br />
<br />
[[Clon06]]<br />
<br />
[[Clon10]]<br />
<br />
[[Clon20]]<br />
<br />
[[Clondaq1]]<br />
<br />
[[Clondaq2]]<br />
<br />
[[Clondb1]]<br />
<br />
[[Clondb2]]<br />
<br />
[[Clondb3]]<br />
<br />
[[Clonfs]] Main RAID System<br />
<br />
[[Clonfs1]]<br />
<br />
[[Clonfs2]]<br />
<br />
[[clonhp]]<br />
<br />
[[clonhp2]]<br />
<br />
[[Clonmon]]<br />
<br />
[[Clonmon0]]<br />
<br />
[[Clonmon1]]<br />
<br />
[[Clonmon2]]<br />
<br />
[[Clonpc1]]<br />
<br />
[[Clonpc2]]<br />
<br />
[[Clonpc3]]<br />
<br />
[[Clonpc5]]<br />
<br />
[[Clonpc6]]<br />
<br />
[[Clonpc8]]<br />
<br />
[[Clontrig0]]<br />
<br />
[[Clonusr1]]<br />
<br />
[[Clonusr2]]<br />
<br />
[[Clonusr3]]<br />
<br />
[[Clonweb]]<br />
<br />
[[Clonwiki]]<br />
<br />
[[Coda]]<br />
<br />
[[Compcontrol CC121]]<br />
<br />
[[CycladesTS1000]]<br />
<br />
[[DATEL DVME-628]]<br />
<br />
[[DNS server]]<br />
<br />
[[Electronics Documentation]]<br />
<br />
[[EtherLite32]]<br />
<br />
[[EPICS Base Installation]]<br />
<br />
[[EPICS: Generation of IOC with different options and customization for HallB]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: vxWorks IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Timeline Histories]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[EPICS: EDM compilation and configuration]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[EVIO]]<br />
<br />
[[Fiber Channel Switches]]<br />
<br />
[[FieldPoint]]<br />
<br />
[[Flash ADC Studies]]<br />
<br />
[[Foundry BigIron 15000 Switch]]<br />
<br />
[[Foundry Switches]]<br />
<br />
[[GE XVB601]] VME controller<br />
<br />
[[Helicity Signals from MCC]]<br />
<br />
[[HYTEC VSD2992]]<br />
<br />
[[JAVA installation]]<br />
<br />
[[JLAB Discriminators]]<br />
<br />
[[JLAB FANIO]] VME TDC FanIO board for v1190/v1290 CAEN TDCs<br />
<br />
[[JLAB FADC250]]<br />
<br />
[[JLAB FLEXIO]]<br />
<br />
[[JLAB LF]] VME Latch FIFO Board<br />
<br />
[[JLAB LD]] VME Latch Driver Board<br />
<br />
[[JLAB Level2 Majority]] Logic Unit<br />
<br />
[[JLAB MLU]] VME Memory Lookup Unit (MLU)<br />
<br />
[[JLAB OR]] VME Programmable “OR” Module<br />
<br />
[[JLAB TS2]] VXI D-size Trigger Supervisor Module<br />
<br />
[[JLAB TI]] CODA Trigger Interface Cards<br />
<br />
[[JLAB PCI TI]] PCI Trigger Interface Card<br />
<br />
[[JLAB VME TI]] VME Trigger Interface Module<br />
<br />
[[JLAB VME TID]] New VME/VXS Trigger Interface Module<br />
<br />
[[Joerger VSC16]]<br />
<br />
[[KineticSystems 2917]]<br />
<br />
[[Labeling Machines]]<br />
<br />
[[Linux Installation Procedure]]<br />
<br />
[[Linux Customization on CLON Cluster]]<br />
<br />
[[Lnf cluster]]<br />
<br />
[[Mac OS X Installation Procedure]]<br />
<br />
[[Motorola MVME5500]]<br />
<br />
[[MRTG]]<br />
<br />
[[mSQL]]<br />
<br />
[[MySQL Installation]]<br />
<br />
[[MySQL Usage]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Net-SNMP]]<br />
<br />
[[NFS]]<br />
<br />
[[NIS server]]<br />
<br />
[[Nrpe]]<br />
<br />
[[Ntp]]<br />
<br />
[[OMS VME44]] by Oregon Micro Systems<br />
<br />
[[OMS VS4]] by Oregon Micro Systems<br />
<br />
[[OpenSSL]]<br />
<br />
[[PERL]]<br />
<br />
[[Procmail]]<br />
<br />
[[PrPMC]]<br />
<br />
[[raidold]]<br />
<br />
[[Routing]]<br />
<br />
[[Rrdtool]]<br />
<br />
[[SBS VIPC616]]<br />
<br />
[[Serial Connections from Computer Ports]]<br />
<br />
[[Sfs61]]<br />
<br />
[[Slow Controls Time History]]<br />
<br />
[[SmartSockets]]<br />
<br />
[[SNMP]]<br />
<br />
[[Software Documentation]]<br />
<br />
[[Solaris Installation Procedure]]<br />
<br />
[[Solaris Customization on CLON Cluster]]<br />
<br />
[[Solaris Patches]]<br />
<br />
[[SSH]]<br />
<br />
[[Struck SIS3801]]<br />
<br />
[[Sudo]]<br />
<br />
[[SUN Microsystems]]<br />
<br />
[[SYSTRAN VMESC5]]<br />
<br />
[[Tcl/Tk]]<br />
<br />
[[Tftp]]<br />
<br />
[[Troubleshooting printing]]<br />
<br />
[[Tsi148]] VME Tempe controller<br />
<br />
[[Universe II]] VME controller<br />
<br />
[[UNIX Automount on CLON Cluster]]<br />
<br />
[[UPS (Uninterruptible Power Supplies)]]<br />
<br />
[[UPS CHB1]]<br />
<br />
[[UPS CHB2]]<br />
<br />
[[UPS Troubleshooting]]<br />
<br />
[[VHDL programming]]<br />
<br />
[[VI editor]]<br />
<br />
[[VMIC VMIVME-3122]]<br />
<br />
[[VMIC VMIVME-2120]]<br />
<br />
[[VMIC VMIVME-1129]]<br />
<br />
[[VMIC VMIVME-2232]]<br />
<br />
[[VMIC VMIVME-6015]]<br />
<br />
[[VMIC VMIVME-6016]]<br />
<br />
[[VNC]]<br />
<br />
[[WIENER]]<br />
<br />
[[Wiki]]<br />
<br />
[[Wiring]]<br />
<br />
[[X server]]<br />
<br />
[[Xycom DIO XVME-240]]<br />
<br />
[[Xycom XVME-564]]<br />
<br />
[[Xycom XVME-560]]<br />
<br />
[[ZFS]]</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonusr2&diff=5600Clonusr22011-11-13T01:08:00Z<p>129.57.167.42: Created page with "DELL Presicion R5400 server under RHEL, tag F424383, eth0: 00:25:64:90:B9:E5/129.57.167.48, eth1: 00:25:64:90:B9:E6"</p>
<hr />
<div>DELL Presicion R5400 server under RHEL, tag F424383, eth0: 00:25:64:90:B9:E5/129.57.167.48, eth1: 00:25:64:90:B9:E6</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=5599CLON Index2011-11-13T01:05:06Z<p>129.57.167.42: </p>
<hr />
<div>[[akcp]] temperature/humidity etc sensors<br />
<br />
[[Apache]]<br />
<br />
[[automounts]]<br />
<br />
[[Bertan MWPC]] High Voltage Power Supplies<br />
<br />
[[Bootp]]<br />
<br />
[[Cacti]]<br />
<br />
[[CAEN A464]] caenet board (installed in sy527 mainframes)<br />
<br />
[[CAEN A1733 A1833]] 12/28 ch. 3kV/3mA, 4kV/2mA High Voltage Boards ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br />
<br />
[[CAEN A1932A]] 48 ch. 3kV 500uA High Voltage Board ( SY1527 / SY2527 / SY3527 Universal Multichannel System )<br />
<br />
[[CAEN SY1527 Mainframe]]<br />
<br />
[[CAEN SY527 Mainframe]] and modules<br />
<br />
[[CAEN V1190]] TDC board (128 ch 100 ps)<br />
<br />
[[CAEN V1290]] TDC board (32 ch 25 ps)<br />
<br />
[[CAEN V1495]] General Purpose VME Board<br />
<br />
[[CAEN V1720]] Flash ADC VME Board<br />
<br />
[[CAEN V288]]<br />
<br />
[[CAEN V560]] scaler board<br />
<br />
[[CAEN V775]] TDC Board<br />
<br />
[[CAEN V792]] ADC Board<br />
<br />
[[CAEN V895]] 16 ch. Leading Edge Discriminator with individual thresholds<br />
<br />
[[Capfast]]<br />
<br />
[[Cisco Switches]]<br />
<br />
[[Clasweb]]<br />
<br />
[[Clasxt]]<br />
<br />
[[Clon00]]<br />
<br />
[[Clon01]]<br />
<br />
[[Clon02]]<br />
<br />
[[Clon03]]<br />
<br />
[[Clon04]]<br />
<br />
[[Clon05]]<br />
<br />
[[Clon06]]<br />
<br />
[[Clon10]]<br />
<br />
[[Clon20]]<br />
<br />
[[Clondaq1]]<br />
<br />
[[Clondaq2]]<br />
<br />
[[Clondb1]]<br />
<br />
[[Clondb2]]<br />
<br />
[[Clondb3]]<br />
<br />
[[Clonfs]] Main RAID System<br />
<br />
[[Clonfs1]]<br />
<br />
[[Clonfs2]]<br />
<br />
[[clonhp]]<br />
<br />
[[clonhp2]]<br />
<br />
[[Clonmon]]<br />
<br />
[[Clonmon0]]<br />
<br />
[[Clonmon1]]<br />
<br />
[[Clonmon2]]<br />
<br />
[[Clonpc1]]<br />
<br />
[[Clonpc2]]<br />
<br />
[[Clonpc3]]<br />
<br />
[[Clonpc5]]<br />
<br />
[[Clonpc6]]<br />
<br />
[[Clonpc8]]<br />
<br />
[[Clontrig0]]<br />
<br />
[[Clonusr2]]<br />
<br />
[[Clonweb]]<br />
<br />
[[Clonwiki]]<br />
<br />
[[Coda]]<br />
<br />
[[Compcontrol CC121]]<br />
<br />
[[CycladesTS1000]]<br />
<br />
[[DATEL DVME-628]]<br />
<br />
[[DNS server]]<br />
<br />
[[Electronics Documentation]]<br />
<br />
[[EtherLite32]]<br />
<br />
[[EPICS Base Installation]]<br />
<br />
[[EPICS: Generation of IOC with different options and customization for HallB]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: vxWorks IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Timeline Histories]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[EPICS: EDM compilation and configuration]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[EVIO]]<br />
<br />
[[Fiber Channel Switches]]<br />
<br />
[[FieldPoint]]<br />
<br />
[[Flash ADC Studies]]<br />
<br />
[[Foundry BigIron 15000 Switch]]<br />
<br />
[[Foundry Switches]]<br />
<br />
[[GE XVB601]] VME controller<br />
<br />
[[Helicity Signals from MCC]]<br />
<br />
[[HYTEC VSD2992]]<br />
<br />
[[JAVA installation]]<br />
<br />
[[JLAB Discriminators]]<br />
<br />
[[JLAB FANIO]] VME TDC FanIO board for v1190/v1290 CAEN TDCs<br />
<br />
[[JLAB FADC250]]<br />
<br />
[[JLAB FLEXIO]]<br />
<br />
[[JLAB LF]] VME Latch FIFO Board<br />
<br />
[[JLAB LD]] VME Latch Driver Board<br />
<br />
[[JLAB Level2 Majority]] Logic Unit<br />
<br />
[[JLAB MLU]] VME Memory Lookup Unit (MLU)<br />
<br />
[[JLAB OR]] VME Programmable “OR” Module<br />
<br />
[[JLAB TS2]] VXI D-size Trigger Supervisor Module<br />
<br />
[[JLAB TI]] CODA Trigger Interface Cards<br />
<br />
[[JLAB PCI TI]] PCI Trigger Interface Card<br />
<br />
[[JLAB VME TI]] VME Trigger Interface Module<br />
<br />
[[JLAB VME TID]] New VME/VXS Trigger Interface Module<br />
<br />
[[Joerger VSC16]]<br />
<br />
[[KineticSystems 2917]]<br />
<br />
[[Labeling Machines]]<br />
<br />
[[Linux Installation Procedure]]<br />
<br />
[[Linux Customization on CLON Cluster]]<br />
<br />
[[Lnf cluster]]<br />
<br />
[[Mac OS X Installation Procedure]]<br />
<br />
[[Motorola MVME5500]]<br />
<br />
[[MRTG]]<br />
<br />
[[mSQL]]<br />
<br />
[[MySQL Installation]]<br />
<br />
[[MySQL Usage]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Net-SNMP]]<br />
<br />
[[NFS]]<br />
<br />
[[NIS server]]<br />
<br />
[[Nrpe]]<br />
<br />
[[Ntp]]<br />
<br />
[[OMS VME44]] by Oregon Micro Systems<br />
<br />
[[OMS VS4]] by Oregon Micro Systems<br />
<br />
[[OpenSSL]]<br />
<br />
[[PERL]]<br />
<br />
[[Procmail]]<br />
<br />
[[PrPMC]]<br />
<br />
[[raidold]]<br />
<br />
[[Routing]]<br />
<br />
[[Rrdtool]]<br />
<br />
[[SBS VIPC616]]<br />
<br />
[[Serial Connections from Computer Ports]]<br />
<br />
[[Sfs61]]<br />
<br />
[[Slow Controls Time History]]<br />
<br />
[[SmartSockets]]<br />
<br />
[[SNMP]]<br />
<br />
[[Software Documentation]]<br />
<br />
[[Solaris Installation Procedure]]<br />
<br />
[[Solaris Customization on CLON Cluster]]<br />
<br />
[[Solaris Patches]]<br />
<br />
[[SSH]]<br />
<br />
[[Struck SIS3801]]<br />
<br />
[[Sudo]]<br />
<br />
[[SUN Microsystems]]<br />
<br />
[[SYSTRAN VMESC5]]<br />
<br />
[[Tcl/Tk]]<br />
<br />
[[Tftp]]<br />
<br />
[[Troubleshooting printing]]<br />
<br />
[[Tsi148]] VME Tempe controller<br />
<br />
[[Universe II]] VME controller<br />
<br />
[[UNIX Automount on CLON Cluster]]<br />
<br />
[[UPS (Uninterruptible Power Supplies)]]<br />
<br />
[[UPS CHB1]]<br />
<br />
[[UPS CHB2]]<br />
<br />
[[UPS Troubleshooting]]<br />
<br />
[[VHDL programming]]<br />
<br />
[[VI editor]]<br />
<br />
[[VMIC VMIVME-3122]]<br />
<br />
[[VMIC VMIVME-2120]]<br />
<br />
[[VMIC VMIVME-1129]]<br />
<br />
[[VMIC VMIVME-2232]]<br />
<br />
[[VMIC VMIVME-6015]]<br />
<br />
[[VMIC VMIVME-6016]]<br />
<br />
[[VNC]]<br />
<br />
[[WIENER]]<br />
<br />
[[Wiki]]<br />
<br />
[[Wiring]]<br />
<br />
[[X server]]<br />
<br />
[[Xycom DIO XVME-240]]<br />
<br />
[[Xycom XVME-564]]<br />
<br />
[[Xycom XVME-560]]<br />
<br />
[[ZFS]]</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5199GE XVB6012011-04-04T15:26:18Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
Documentation: <br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_ds_gfa1299.pdf Datasheet]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_xvb601_hr_500-930007815-000_E.pdf Hardware Reference]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_522-9300800627-000_A.book.pdf Installation Guide]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Configuration_Guide_XVB601.pdf Product Configurations]<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/ge_Ruggedization_Levels_GFA-926a.pdf Ruggedization]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''List of boards'''<br />
<br />
* [01] 00:20:38:04:23:5E / 129.57.68.88 / croctest1<br />
<br />
* [02] 00:20:38:04:23:60 / 129.57.68.89 / croctest2<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* ''yum install system-config-netboot''<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* ''service xinetd restart''<br />
<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.167.0/255.255.255.0</code> only allows the 167 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
''service nfs reload''<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
* Enable remote syslog (optional)<br />
<br />
Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
Restart syslogd<br />
service syslog restart<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5174GE XVB6012011-03-24T22:44:20Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* ''yum install system-config-netboot''<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* ''service xinetd restart''<br />
<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.167.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.167.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.167.0/255.255.255.0</code> only allows the 167 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
''service nfs reload''<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
* Enable remote syslog (optional)<br />
<br />
Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5173GE XVB6012011-03-24T22:38:13Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* ''yum install system-config-netboot''<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* ''service xinetd restart''<br />
<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
''service nfs reload''<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5172GE XVB6012011-03-24T22:37:06Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* ''yum install system-config-netboot''<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* ''service xinetd restart''<br />
<br />
'''Configure NFS'''<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5171GE XVB6012011-03-24T22:36:36Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* 'service xinetd restart'<br />
<br />
'''Configure NFS'''<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5170GE XVB6012011-03-24T22:35:04Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
'''Configure NFS'''<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5169GE XVB6012011-03-24T22:33:40Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
'''Customizing kernel installed on the FLASH'''<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
'''Enable the tftp server to start at boot'''<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
'''Configure NFS'''<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5168GE XVB6012011-03-24T22:32:33Z<p>129.57.167.42: </p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
'''Enable the tftp server to start at boot'''<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
'''Configure NFS'''<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
''' Enable remote syslog (optional) '''<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
'''DHCP Server Setup'''<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
'''Configure Client OS'''<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
'''Setup of Diskless Kernel'''<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
'''Setup of chroot environment'''<br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
'''Setup of diskless system configurations'''<br />
<br />
''' Which NFS directories to mount '''<br />
<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
''' Configure a NEW diskless client '''<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
''' Configuration on the tftp/NFS server '''<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
''' Configuration on the Diskless Client '''<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
''' Other useful packages to install '''<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5167GE XVB6012011-03-24T22:29:30Z<p>129.57.167.42: </p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
'''Trying netboot following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
<br />
<br />
<br />
== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5166GE XVB6012011-03-24T22:24:51Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
'''following Bryan's instructions, using clonpc3'''<br />
<br />
* yum install system-config-netboot<br />
<br />
*<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=GE_XVB601&diff=5165GE XVB6012011-03-24T22:23:54Z<p>129.57.167.42: /* Customization for the CLON cluster */</p>
<hr />
<div>Company site: [http://www.ge-ip.com/products/family/embedded-systems GE Intelligent Platforms]<br />
<br />
Board page on company site: [http://www.ge-ip.com/products/3448 XVB601]<br />
<br />
== Customization for the CLON cluster ==<br />
<br />
* ''/usr/bin/system-config-network''<br />
<br />
* fix ''/etc/passwd'', ''/etc/shadow'', ''/etc/group''<br />
<br />
* fix ''/etc/nsswitch.conf''<br />
<br />
* fix ''/etc/yp.conf'' (add lines ''domain CCCHP server clon00.jlab.org'' and ''ypserver clon10.jlab.org'')<br />
<br />
* fix ''/etc/sysconfig/network'' (add line ''NISDOMAIN=CCCHP'')<br />
<br />
* ''/etc/init.d/ypbind start''<br />
<br />
* ''chkconfig ypbind on''<br />
<br />
<br />
* set RHEL-style [[automounts]]<br />
<br />
* ''/etc/init.d/autofs restart''<br />
<br />
* fix symbolic links to /apps, /home, /usr/local etc<br />
<br />
<br />
'''following Bryan's instructions'''<br />
<br />
== Network-based booting ==<br />
<br />
The page is geared towards the setup of Diskless nodes for Intel-based VME Controllers, but may be useful for similar other applications. Much of what is here was derived from the [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/ch-diskless.html Redhat Enterprise Linux 3 Documentation].<br />
<br />
This examples assumes:<br />
* The DHCP server (phecda: 129.57.29.104) has been installed and works. Here we're using the dhcp 3.0.1 package distributed by RHEL4.<br />
* The TFTP and NFS server (mizar: 129.57.29.100) is running RHEL5.5 x86_64.<br />
* The Diskless Client (dafarm44: 129.57.29.54) will run Centos 5.5 x86_64.<br />
<br />
There's nothing stopping you from having the DHCP server on the same machine as that servering TFTP and NFS. You can obviously have more than one diskless client.<br />
<br />
Once the first four steps have been completed, new clients can be configured individually with step 5.<br />
<br />
= Client Setup of OS in VirtualBox =<br />
Here, we've downloaded the latest and greatest Centos 5.5 x86_64 ISO and have set up a VirtualBox Client to use it to boot. We will not attempt to describe the VirtualBox installation or Setup of the ISO to boot as the VirtualBox Guest.<br />
<br />
The Centos 5.5 installation proceeds as normal installations go, but we opt to do a minimal installation (excluding KDE and/or GNOME components) since we're running on a VME controller. Other packages will be installed after first boot.<br />
<br />
=== First Boot ===<br />
At first boot (after installation), a UI will appear and provide you with some options.:<br />
* Disable firewall and SELinux. SELinux setup can be double checked in the file:<br />
/etc/selinux/config<br />
* Disable sendmail, and other services not required for a VME controller<br />
<br />
=== Update packages and transfer the OS to Server ===<br />
Login as root<br />
* Update all installed packages:<br />
yum update<br />
* Install the following packages, with:<br />
yum install <i>package</i><br />
:: busybox-anaconda<br />
:: gcc<br />
:: kernel-devel<br />
:: gdb<br />
:: valgrind<br />
:: cvs<br />
:: subversion<br />
:: compat-libstdc++-33<br />
:: redhat-rpm-config<br />
<br />
* Copy the Client OS to the tftp/NFS Server.<br />
** On The Server:<br />
mkdir -p /diskless/x86_64/Centos5.5/root<br />
: In The VirtualBox Guest:<br />
rsync -Pav -e ssh --exclude='/proc/*' --exclude='/sys/*' / mizar:/diskless/x86_64/Centos5.5/root/<br />
<br />
You are now done with the Centos5.5 Guest installed in the VirtualBox. It can be closed down now.<br />
<br />
= tftp and NFS Server Setup =<br />
Follow these steps on the machine serving out tftp and NFS:<br />
<br />
===Install <code>system-config-netboot</code> ===<br />
(This should automatically install the tftp server)<br />
yum install system-config-netboot<br />
<br />
=== Enable the tftp server to start at boot ===<br />
* Change line (<code>/etc/xinetd.d/tftp</code>):<br />
disable = yes<br />
: To<br />
disable = no<br />
<br />
* Restart <code>xinetd</code><br />
service xinetd restart<br />
<br />
=== Configure NFS ===<br />
* Add these entries to <code>/etc/exports</code><br />
/diskless/x86_64/Centos5.5/root/ 129.57.29.0/255.255.255.0(ro,sync,no_root_squash)<br />
/diskless/x86_64/Centos5.5/snapshot/ 129.57.29.0/255.255.255.0(rw,sync,no_root_squash)<br />
: Where the <code>129.57.29.0/255.255.255.0</code> only allows the 29 subnet to access these mounts.<br />
<br />
* Reload the NFS configuration or start NFS, if it's not started<br />
service nfs reload<br />
<br />
* Make sure NFS is started at boot<br />
/sbin/chkconfig --level 345 nfs on<br />
<br />
=== Enable remote syslog (optional) ===<br />
* Change syslog argument in <code>/etc/sysconfig/syslog</code> from:<br />
SYSLOGD_OPTIONS="-m 0"<br />
:: To<br />
SYSLOGD_OPTIONS="-m 0 -r"<br />
<br />
* Restart syslogd<br />
service syslog restart<br />
<br />
= DHCP Server Setup =<br />
On the machine hosting the DHCP server.<br />
<br />
* Add an entry in <code>/etc/dhcpd.conf</code>:<br />
<pre><br />
host dafarm44<br />
{<br />
filename "linux-install/pxelinux.0"; # File location relative to /tftpboot/<br />
next-server 129.57.29.38; # TFTP server<br />
hardware ethernet 00:20:38:03:D8:52; # Client MAC<br />
fixed-address 129.57.29.54; # Client IP<br />
}<br />
</pre><br />
<br />
* Restart dhcpd<br />
service dhcpd restart<br />
<br />
= Configure Client OS =<br />
<br />
Here, we configure the OS that each and every Diskless Client will enjoy.<br />
<br />
=== Setup of Diskless Kernel ===<br />
Run system-config-netboot (on TFTP server):<br />
system-config-netboot<br />
<br />
* In "First Time Druid" window. Click on "Diskless"<br />
# Click "Forward" on first page<br />
# Enter Name and Description.<br />
# Enter IP address of TFTP server and the "root" directory exported via NFS<br />
# Select a kernel<br />
# Click on Apply.<br />
: This will take a minute or two to compile a boot kernel for the diskless client.<br />
<br />
=== Setup of chroot environment === <br />
There are lots of specifics here for setup on the JLab CUE and Data Acquisition Network (daqfs).<br />
This enviroment will give you the capability to do system updates/upgrades for all diskless clients at the same time.<br />
chroot /diskless/x86_64/Centos5.5/root<br />
mount /proc /proc -t proc<br />
mkdir /u <br />
mkdir /group<br />
mkdir /daqfs<br />
mv /home /home.old<br />
ln -s /u/apps /apps<br />
ln -s /u/site /site<br />
ln -s /daqfs/home /home<br />
<br />
=== Setup of diskless system configurations ===<br />
''' Which NFS directories to mount '''<br />
* Add entry to <code>/etc/fstab</code><br />
phecda:/raid /daqfs nfs rw,soft,intr 0 0<br />
<br />
* Mount daqfs<br />
mount /daqfs<br />
<br />
''' Which users/groups to allow access '''<br />
* Add entries to /etc/passwd<br />
+@da::::::<br />
+@ccc::::::<br />
+::::::/bin/false<br />
<br />
''' A proxy for yum ''' (may be optional)<br />
* Add entry to /etc/yum.conf<br />
proxy=http://jprox:8080<br />
<br />
''' domain servers for ypbind '''<br />
* Add entries to /etc/yp.conf<br />
domain CCCHP server nis2.jlab.org<br />
domain CCCHP server nis3.jlab.org<br />
<br />
* Make sure ypbind started at boot<br />
/sbin/chkconfig --level 345 nfs on <br />
<br />
''' NTP setup ''' (optional... ntp must be installed)<br />
* Add entries to <code>/etc/ntp.conf</code><br />
server 127.0.0.1 # local clock<br />
fudge 127.0.0.1 stratum 10<br />
server ntp1.jlab.org<br />
server ntp2.jlab.org<br />
driftfile /etc/ntp/drift<br />
broadcastdelay 0.008<br />
authenticate no<br />
<br />
''' Some additional JLab CUE directories to mount '''<br />
* Add entries to <code>/etc/auto.master</code><br />
/group /etc/auto.group --timeout=0<br />
/u auto.u.bb --DOSNAME=Linux-RHEL5<br />
<br />
''' Additional files, not included in the standard diskless filesystem '''<br />
* Add a new file <code>/diskless/x86_64/Centos5.5/snapshot/files.custom</code>. Entry:<br />
/tmp/<br />
/etc/minirc.dfl<br />
<br />
= Configure a NEW diskless client =<br />
This operation must be peformed to add a new Diskless Client. <br />
<br />
=== Configuration on the tftp/NFS server ===<br />
* In <code>system-config-netboot</code> "Network Installation and Diskless Environment" window:<br />
# Click on "New"<br />
# Enter hostname<br />
# Select OS<br />
# Enter "CCCHP" in Enable NISDOMAIN box.<br />
# Enter options in "Edit Extra Kernel Boot Options" <br /> <code>vga=0x305 acpi=force</code><br />
# Enter hostname as snapshot name. Make sure "generate" is check-marked<br />
# Click "OK"<br />
<br />
=== Configuration on the Diskless Client ===<br />
* PXEboot must be enabled and should be the primary boot option. This is set in the BIOS.<br />
<br />
= Other useful packages to install =<br />
Later on... I installed some other useful packages using the chroot environment. Here they are:<br />
<br />
* <code>xorg-x11-xauth</code> - Required to run X-applications remotely<br />
* <code>ntp</code> - Synchronize system clock with a central server<br />
: To Execute <code>ntpdate</code> on server startup:<br />
:* Add <code><b>-x</b></code> to <code>OPTIONS</code> in<br />
/etc/sysconfig/ntpd<br />
:* Make sure it starts on boot<br />
/sbin/chkconfig --level 345 nfs on</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonpc1&diff=5163Clonpc12011-03-24T15:31:08Z<p>129.57.167.42: </p>
<hr />
<div>DELL PowerEdge 1655MC running RHEL5.<br />
<br />
Hardware manuals: [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_Installation.pdf Installation Guide (pdf)] [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_System_Configuration.pdf System Configuration Guide (pdf)].<br />
<br />
Usage: SoftIOC.<br />
<br />
IP address:<br />
clonpc1/129.57.167.59/00:0B:DB:AD:2E:A7<br />
<br />
To get access: <print-screen> and double click on server name.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonpc2&diff=5162Clonpc22011-03-24T15:30:43Z<p>129.57.167.42: </p>
<hr />
<div>DELL PowerEdge 1655MC running RHEL5.<br />
<br />
Hardware manuals: [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_Installation.pdf Installation Guide (pdf)] [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_System_Configuration.pdf System Configuration Guide (pdf)].<br />
<br />
Usage: SoftIOC.<br />
<br />
IP address:<br />
clonpc2/129.57.167.60/00:0B:DB:AD:30:8D<br />
<br />
To get access: <print-screen> and double click on server name.<br />
<br />
System disk partisioning (preserve DOS partition if reinstalling !):<br />
<br />
Disk /dev/sda: 18.2 GB, 18210036736 bytes<br />
255 heads, 63 sectors/track, 2213 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 1 5 40131 de Dell Utility<br />
/dev/sda2 * 6 18 104422+ 83 Linux<br />
/dev/sda3 19 1933 15382237+ 83 Linux<br />
/dev/sda4 1934 2213 2249100 5 Extended<br />
/dev/sda5 1934 2213 2249068+ 82 Linux swap<br />
<br />
Filesystem 1K-blocks Used Available Use% Mounted on<br />
/dev/sda3 15140492 6274236 8097148 44% /<br />
/dev/sda2 101105 11313 84571 12% /boot<br />
none 257272 0 257272 0% /dev/shm<br />
/dev/sda1 40034 8598 31436 22% /dos<br />
<br />
<br />
NOTES:<br />
<br />
1. Hard drive reported errors, replaced on 17-jan-2007</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonpc2&diff=5161Clonpc22011-03-24T15:30:17Z<p>129.57.167.42: </p>
<hr />
<div>DELL PowerEdge 1655MC running RHEL4.<br />
<br />
Hardware manuals: [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_Installation.pdf Installation Guide (pdf)] [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_System_Configuration.pdf System Configuration Guide (pdf)].<br />
<br />
Usage: SoftIOC.<br />
<br />
IP address:<br />
clonpc2/129.57.167.60/00:0B:DB:AD:30:8D<br />
<br />
To get access: <print-screen> and double click on server name.<br />
<br />
System disk partisioning (preserve DOS partition if reinstalling !):<br />
<br />
Disk /dev/sda: 18.2 GB, 18210036736 bytes<br />
255 heads, 63 sectors/track, 2213 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 1 5 40131 de Dell Utility<br />
/dev/sda2 * 6 18 104422+ 83 Linux<br />
/dev/sda3 19 1933 15382237+ 83 Linux<br />
/dev/sda4 1934 2213 2249100 5 Extended<br />
/dev/sda5 1934 2213 2249068+ 82 Linux swap<br />
<br />
Filesystem 1K-blocks Used Available Use% Mounted on<br />
/dev/sda3 15140492 6274236 8097148 44% /<br />
/dev/sda2 101105 11313 84571 12% /boot<br />
none 257272 0 257272 0% /dev/shm<br />
/dev/sda1 40034 8598 31436 22% /dos<br />
<br />
<br />
NOTES:<br />
<br />
1. Hard drive reported errors, replaced on 17-jan-2007</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Clonpc1&diff=5160Clonpc12011-03-24T14:44:55Z<p>129.57.167.42: </p>
<hr />
<div>DELL PowerEdge 1655MC running RHEL4.<br />
<br />
Hardware manuals: [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_Installation.pdf Installation Guide (pdf)] [https://clonwiki.jlab.org/wiki/clondocs/Docs/DELL_1655_System_Configuration.pdf System Configuration Guide (pdf)].<br />
<br />
Usage: SoftIOC.<br />
<br />
IP address:<br />
clonpc1/129.57.167.59/00:0B:DB:AD:2E:A7<br />
<br />
To get access: <print-screen> and double click on server name.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Apache&diff=4203Apache2009-02-24T17:19:19Z<p>129.57.167.42: /* PHP Installation */</p>
<hr />
<div>== Apache initial installation ==<br />
<br />
Login as 'root'. Do following:<br />
<br />
download 'httpd-2.2.3.tar.gz' from web to '/usr/local/download/'<br />
cp /usr/local/downloads/httpd-2.2.3.tar.gz /usr/local/src<br />
cd /usr/local/src<br />
gunzip httpd-2.2.3.tar.gz<br />
tar xvf httpd-2.2.3.tar<br />
rm httpd-2.2.3.tar<br />
<br />
If in 'clonweb' do fillowing (on 'clonwiki' replace 'clonweb' by 'clonwiki'). Make sure directory '/www/apache2.2.3' exist, create it if necessary.<br />
<br />
mv httpd-2.2.3 httpd-2.2.3_clonweb<br />
cd /usr/local/src/httpd-2.2.3_clonweb<br />
./configure --enable-module=so --prefix=/www/apache2.2.3<br />
make<br />
make install<br />
<br />
Make sure that user set to 'apache' (should exist already):<br />
<br />
grep "^User" /www/apache2.2.3/conf/httpd.conf<br />
emacs /www/apache2.2.3/conf/httpd.conf<br />
set User (and Group) to 'apache' if necessary<br />
<br />
== PHP Installation ==<br />
<br />
Login as 'root'. Do following:<br />
<br />
download 'php-5.2.0.tar.gz' from web to '/usr/local/download/'<br />
cp /usr/local/downloads/php-5.2.0.tar.gz /usr/local/src<br />
cd /usr/local/src<br />
gunzip php-5.2.0.tar.gz<br />
tar xvf php-5.2.0.tar<br />
rm php-5.2.0.tar<br />
<br />
Following is for 'clonweb', use your machine name if necessary:<br />
<br />
mv php-5.2.0 php-5.2.0_clonweb<br />
cd /usr/local/src/php-5.2.0_clonweb<br />
./configure --with-mysql --with-apxs2=/www/apache2.2.3/bin/apxs --enable-sockets --with-snmp<br />
make<br />
make install<br />
##cp /usr/local/src/php-5.2.0_clonweb/libs/libphp5.so /www/apache2.2.3/modules<br />
<br />
Fix apache config file /www/apache2.2.3/conf/httpd.conf:<br />
<br />
DirectoryIndex index.php index.html<br />
LoadModule php5_module modules/libphp5.so<br />
AddType application/x-httpd-php .php<br />
AddType application/x-httpd-php .php3<br />
AddType application/x-httpd-php .phtml<br />
<br />
== Final Apache Installation ==<br />
<br />
Edit /www/apache2.2.3/htdocs/index.html file (or do it later).<br />
<br />
To start/stop apache server do following:<br />
<br />
/www/apache2.2.3/bin/apachectl start<br />
/www/apache2.2.3/bin/apachectl stop<br />
<br />
If it started fine, fix startup script '/etc/rc.d/init.d/httpd' setting correct pathes:<br />
<br />
# config: /www/apache2.2.3/conf/httpd.conf<br />
# pidfile: /www/apache2.2.3/logs/httpd.pid<br />
apachectl=/www/apache2.2.3/bin/apachectl<br />
httpd=${HTTPD-/www/apache2.2.3/bin/httpd}<br />
pidfile=${PIDFILE-/www/apache2.2.3/logs/httpd.pid}<br />
<br />
Modified file is saved as ''/www/apache2.2.3/httpd.for_etc_init_d'', copy it as ''/etc/init.d/httpd''.<br />
<br />
Now apache can be controled by following commands:<br />
<br />
/etc/init.d/httpd stop<br />
/etc/init.d/httpd start<br />
/etc/init.d/httpd restart<br />
<br />
Add apache to the list of services to be started at boot time using:<br />
<br />
/usr/bin/system-config-services<br />
<br />
== Password protection ==<br />
<br />
1. Create password file:<br />
htpasswd -c /www/apache2.2.11/conf/passwords user1<br />
New password: <br />
Re-type new password: <br />
Adding password for user user1<br />
NOTE: more users can be added by<br />
htpasswd /www/apache2.2.11/conf/passwords user2<br />
or deleted by<br />
htpasswd -D /www/apache2.2.11/conf/passwords user2<br />
<br />
2. Create group file ''/www/apache2.2.11/conf/groups'' with appropriate contents, for example:<br />
GroupName: user1 user2<br />
<br />
3. Close by default access to the ''DocumentRoot'' directory (will be allowed for every subdirectory, see next paragraph):<br />
<Directory "/www/apache2.2.11/htdocs"><br />
...<br />
#sergey<br />
#Allow from all<br />
Deny from all<br />
</Directory><br />
<br />
4. Add following to the end of ''httpd.conf'' file:<br />
#protect personal directories by password <br />
<Directory "/www/apache2.2.11/htdocs/user1"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
Require user user1<br />
Allow from all<br />
</Directory><br />
<Directory "/www/apache2.2.11/htdocs/user2"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
Require user user2<br />
Allow from all<br />
</Directory><br />
<Directory "/www/apache2.2.11/htdocs"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
AuthGroupFile /www/apache2.2.11/conf/groups<br />
Require Group GroupName<br />
Allow from all<br />
</Directory><br />
it will give an password-protected access for user1 to directories ''user1'' and ''guest'', and for user2 to directories ''user2'' and ''guest''.<br />
<br />
5. Restart apache<br />
<br />
== SSL configuration ==<br />
<br />
1. Generate certificate:<br />
ssleay req -out certificate.pem -nodes -new -x509 -days days<br />
openssl req -new -x509 -days 3650 -keyout ./private/myserver.key -out myserver.crt<br />
openssl x509 -in myserver.crt -text -noout | more</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4202Cacti2009-02-24T17:09:56Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "clondb1";<br />
$database_username = "cactiuser";<br />
$database_password = "cloncacti";<br />
<br />
* create user 'cactiuser' with private group 'cactiuser'<br />
<br />
* Set the appropriate permissions on cacti's directories for graph/log generation. You should execute these commands from inside cacti's directory to change the permissions:<br />
chown -R cactiuser rra/ log/<br />
<br />
* Create ''/www/cacti-0.8.7d/cron'' subdirectory and ''cronjob'' file inside with following contents:<br />
*/5 * * * * cactiuser php /www/cacti-0.8.7d/poller.php > /dev/null 2>&1<br />
Login as ''cactiuser', go to that directory and start cron job:<br />
crontab cronjob<br />
Check that it is running:<br />
crontab -l<br />
<br />
* Point your web browser to http://clonweb/cacti/.<br />
<br />
* Log in the with a 'admin'/'admin'. You will be required to change this password immediately. Make sure to fill in all of the path variables carefully and correctly on the following screen.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4201Cacti2009-02-24T17:05:08Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "clondb1";<br />
$database_username = "cactiuser";<br />
$database_password = "cloncacti";<br />
<br />
* create user 'cactiuser' with private group 'cactiuser'<br />
<br />
* Set the appropriate permissions on cacti's directories for graph/log generation. You should execute these commands from inside cacti's directory to change the permissions:<br />
chown -R cactiuser rra/ log/<br />
<br />
* Create ''/www/cacti-0.8.7d/cron'' subdirectory and ''cronjob'' file inside with following contents:<br />
*/5 * * * * cactiuser php /www/cacti-0.8.7d/poller.php > /dev/null 2>&1<br />
Login as ''cactiuser', go to that directory and start cron job:<br />
crontab cronjob<br />
Check that it is running:<br />
crontab -l<br />
<br />
* Point your web browser to http://clonweb/cacti/.<br />
<br />
* Log in the with a username/password of admin. You will be required to change this password immediately. Make sure to fill in all of the path variables carefully and correctly on the following screen.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4200Cacti2009-02-24T16:56:08Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "clondb1";<br />
$database_username = "cactiuser";<br />
$database_password = "cloncacti";<br />
<br />
* create user 'cactiuser' with private group 'cactiuser'<br />
<br />
* Set the appropriate permissions on cacti's directories for graph/log generation. You should execute these commands from inside cacti's directory to change the permissions:<br />
chown -R cactiuser rra/ log/<br />
<br />
* Add a line to your /etc/crontab file similar to:<br />
*/5 * * * * cactiuser php /www/cacti/poller.php > /dev/null 2>&<br />
1<br />
<br />
* Point your web browser to http://clonweb/cacti/.<br />
<br />
* Log in the with a username/password of admin. You will be required to change this password immediately. Make sure to fill in all of the path variables carefully and correctly on the following screen.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Apache&diff=4199Apache2009-02-24T16:34:56Z<p>129.57.167.42: /* PHP Installation */</p>
<hr />
<div>== Apache initial installation ==<br />
<br />
Login as 'root'. Do following:<br />
<br />
download 'httpd-2.2.3.tar.gz' from web to '/usr/local/download/'<br />
cp /usr/local/downloads/httpd-2.2.3.tar.gz /usr/local/src<br />
cd /usr/local/src<br />
gunzip httpd-2.2.3.tar.gz<br />
tar xvf httpd-2.2.3.tar<br />
rm httpd-2.2.3.tar<br />
<br />
If in 'clonweb' do fillowing (on 'clonwiki' replace 'clonweb' by 'clonwiki'). Make sure directory '/www/apache2.2.3' exist, create it if necessary.<br />
<br />
mv httpd-2.2.3 httpd-2.2.3_clonweb<br />
cd /usr/local/src/httpd-2.2.3_clonweb<br />
./configure --enable-module=so --prefix=/www/apache2.2.3<br />
make<br />
make install<br />
<br />
Make sure that user set to 'apache' (should exist already):<br />
<br />
grep "^User" /www/apache2.2.3/conf/httpd.conf<br />
emacs /www/apache2.2.3/conf/httpd.conf<br />
set User (and Group) to 'apache' if necessary<br />
<br />
== PHP Installation ==<br />
<br />
Login as 'root'. Do following:<br />
<br />
download 'php-5.2.0.tar.gz' from web to '/usr/local/download/'<br />
cp /usr/local/downloads/php-5.2.0.tar.gz /usr/local/src<br />
cd /usr/local/src<br />
gunzip php-5.2.0.tar.gz<br />
tar xvf php-5.2.0.tar<br />
rm php-5.2.0.tar<br />
<br />
Following is for 'clonweb', use your machine name if necessary:<br />
<br />
mv php-5.2.0 php-5.2.0_clonweb<br />
cd /usr/local/src/php-5.2.0_clonweb<br />
./configure --with-mysql --with-apxs2=/www/apache2.2.3/bin/apxs --enable-sockets<br />
make<br />
##make install<br />
cp /usr/local/src/php-5.2.0_clonweb/libs/libphp5.so /www/apache2.2.3/modules<br />
<br />
Fix apache config file /www/apache2.2.3/conf/httpd.conf:<br />
<br />
DirectoryIndex index.php index.html<br />
LoadModule php5_module modules/libphp5.so<br />
AddType application/x-httpd-php .php<br />
AddType application/x-httpd-php .php3<br />
AddType application/x-httpd-php .phtml<br />
<br />
== Final Apache Installation ==<br />
<br />
Edit /www/apache2.2.3/htdocs/index.html file (or do it later).<br />
<br />
To start/stop apache server do following:<br />
<br />
/www/apache2.2.3/bin/apachectl start<br />
/www/apache2.2.3/bin/apachectl stop<br />
<br />
If it started fine, fix startup script '/etc/rc.d/init.d/httpd' setting correct pathes:<br />
<br />
# config: /www/apache2.2.3/conf/httpd.conf<br />
# pidfile: /www/apache2.2.3/logs/httpd.pid<br />
apachectl=/www/apache2.2.3/bin/apachectl<br />
httpd=${HTTPD-/www/apache2.2.3/bin/httpd}<br />
pidfile=${PIDFILE-/www/apache2.2.3/logs/httpd.pid}<br />
<br />
Modified file is saved as ''/www/apache2.2.3/httpd.for_etc_init_d'', copy it as ''/etc/init.d/httpd''.<br />
<br />
Now apache can be controled by following commands:<br />
<br />
/etc/init.d/httpd stop<br />
/etc/init.d/httpd start<br />
/etc/init.d/httpd restart<br />
<br />
Add apache to the list of services to be started at boot time using:<br />
<br />
/usr/bin/system-config-services<br />
<br />
== Password protection ==<br />
<br />
1. Create password file:<br />
htpasswd -c /www/apache2.2.11/conf/passwords user1<br />
New password: <br />
Re-type new password: <br />
Adding password for user user1<br />
NOTE: more users can be added by<br />
htpasswd /www/apache2.2.11/conf/passwords user2<br />
or deleted by<br />
htpasswd -D /www/apache2.2.11/conf/passwords user2<br />
<br />
2. Create group file ''/www/apache2.2.11/conf/groups'' with appropriate contents, for example:<br />
GroupName: user1 user2<br />
<br />
3. Close by default access to the ''DocumentRoot'' directory (will be allowed for every subdirectory, see next paragraph):<br />
<Directory "/www/apache2.2.11/htdocs"><br />
...<br />
#sergey<br />
#Allow from all<br />
Deny from all<br />
</Directory><br />
<br />
4. Add following to the end of ''httpd.conf'' file:<br />
#protect personal directories by password <br />
<Directory "/www/apache2.2.11/htdocs/user1"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
Require user user1<br />
Allow from all<br />
</Directory><br />
<Directory "/www/apache2.2.11/htdocs/user2"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
Require user user2<br />
Allow from all<br />
</Directory><br />
<Directory "/www/apache2.2.11/htdocs"><br />
# AuthType Digest<br />
AuthType Basic<br />
AuthName "Restricted Area"<br />
AuthUserFile /www/apache2.2.11/conf/passwords<br />
AuthGroupFile /www/apache2.2.11/conf/groups<br />
Require Group GroupName<br />
Allow from all<br />
</Directory><br />
it will give an password-protected access for user1 to directories ''user1'' and ''guest'', and for user2 to directories ''user2'' and ''guest''.<br />
<br />
5. Restart apache<br />
<br />
== SSL configuration ==<br />
<br />
1. Generate certificate:<br />
ssleay req -out certificate.pem -nodes -new -x509 -days days<br />
openssl req -new -x509 -days 3650 -keyout ./private/myserver.key -out myserver.crt<br />
openssl x509 -in myserver.crt -text -noout | more</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4198Cacti2009-02-24T16:29:36Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "clondb1";<br />
$database_username = "cactiuser";<br />
$database_password = "cloncacti";</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4197Cacti2009-02-24T16:27:35Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "localhost";<br />
$database_username = "cactiuser";<br />
$database_password = "cacti";</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4196Cacti2009-02-24T16:27:17Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin -h clondb1 -u root -p create cacti<br />
Import the default cacti database:<br />
mysql -h clondb1 -u root -p cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql -h clondb1 -u root -p mysql<br />
mysql> GRANT ALL ON cacti.* TO cactiuser@clonweb IDENTIFIED BY 'cloncacti';<br />
mysql> flush privileges;<br />
mysql> exit;<br />
<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "localhost";<br />
$database_username = "cactiuser";<br />
$database_password = "cacti";</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4195Cacti2009-02-24T16:20:10Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory><br />
<br />
* configure mysql:<br />
Create database:<br />
mysqladmin --user=root create cacti<br />
Import the default cacti database:<br />
mysql cacti < cacti.sql<br />
Create a MySQL username and password for Cacti:<br />
mysql --user=root mysql<br />
GRANT ALL ON cacti.* TO cactiuser@localhost IDENTIFIED BY 'somepassword';<br />
flush privileges;<br />
Edit include/config.php and specify the database type,<br />
name, host, user and password for your Cacti configuration:<br />
$database_type = "mysql";<br />
$database_default = "cacti";<br />
$database_hostname = "localhost";<br />
$database_username = "cactiuser";<br />
$database_password = "cacti";</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4194Cacti2009-02-24T16:13:15Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* untar cacti tarball in /www creating directory<br />
/www/cacti-0.8.7d<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory></div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=Cacti&diff=4193Cacti2009-02-24T16:12:06Z<p>129.57.167.42: </p>
<hr />
<div>Cacti requires MySQL, PHP, RRDTool, net-snmp, and a webserver that supports PHP such as Apache.<br />
<br />
* add following to the Apache ''httpd.conf'':<br />
<br />
###sergey: for CACTI<br />
Alias /cacti "/www/cacti-0.8.7d/"<br />
<Directory "/www/cacti-0.8.7d/"><br />
Options Indexes FollowSymLinks<br />
AllowOverride None<br />
Order allow,deny<br />
Allow from all<br />
</Directory></div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3250February 13, 2008 online meeting minutes2008-03-10T18:52:09Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.<br />
One important issue is related to the expected superlayer unefficiency: since we should be able to find the road using 5 out of 6 superlayers, region-based segment finding become not very useful so we'll not implement it on segment-finding level, although it can be taken into account somehow in road finder. Sergey's slides:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan1.gif slide1],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan2.gif slide2],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan3.gif slide3],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan4.gif slide4].<br />
<br />
We discussed several projects we want to complete during downtime. FASTBUS power supplies seems too low at +-5V current (115A), we may need to increase it to 230A, will discuss it with WIENER. Mark Jones asked to borrow 10 1877 TDCs, Sergey P. will test all boards arrieved recently and 10 boards will be provided. High Voltage 1535 boards are under testing by Sergey P. along with splitters, they will be installed in the Hall after testing. One of Lecroy mainframes in the counting house shows wierd behaviour, will be monitored closely using serial connection. Inventory database is in progress, will continue until everything is there. G9A data files with swap problem will be fixed and written to the SILO with extension *.B** (runs from 56097 to 56118). Sergey B. is planning to finish new firmware testing for v1190/v1290 TDCs - long time project.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3249February 13, 2008 online meeting minutes2008-03-10T18:51:15Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.<br />
One important issue is related to the expected superlayer unefficiency: since we should be able to find the road using 5 out of 6 superlayers, region-based segment finding become not very useful so we'll not implement it on segment-finding level, although it can be taken into account somehow in road finder. Slides:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan1.gif slide1],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan2.gif slide2],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan3.gif slide3],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan4.gif slide4].<br />
<br />
We discussed several projects we want to complete during downtime. FASTBUS power supplies seems too low at +-5V current (115A), we may need to increase it to 230A, will discuss it with WIENER. Mark Jones asked to borrow 10 1877 TDCs, Sergey P. will test all boards arrieved recently and 10 boards will be provided. High Voltage 1535 boards are under testing by Sergey P. along with splitters, they will be installed in the Hall after testing. One of Lecroy mainframes in the counting house shows wierd behaviour, will be monitored closely using serial connection. Inventory database is in progress, will continue until everything is there. G9A data files with swap problem will be fixed and written to the SILO with extension *.B** (runs from 56097 to 56118). Sergey B. is planning to finish new firmware testing for v1190/v1290 TDCs - long time project.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLAS12_Trigger_System_Design&diff=3248CLAS12 Trigger System Design2008-03-10T18:50:46Z<p>129.57.167.42: </p>
<hr />
<div>Leader: Sergey Boyarinov<br />
<br />
Support: Ben Raydo, David Doughty, Chris Cuevas, Ed Jastrzembski, Konstantin Mikhailov, Alex Vlassov<br />
<br />
Goal: CLAS12 Trigger System Design<br />
<br />
Status: in progress<br />
<br />
Project was planned in June 2006 to be completed during FY07. Actual job started in November 2006.<br />
We had several meetings discussing existing CLAS trigger, what can be improved<br />
in CLAS12 desing, and new technologies available today. Our work plan was summarized on Wednesday CLON<br />
meeting December 13, 2006 (see [[December 13, 2006 online meeting minutes]]).<br />
<br />
First very preliminary CLAS12 Trigger System design was presented and discussed on Friday upgrade meeting<br />
December 15, 2006 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
Trigger efficiency simulation is very important but was not started yet.<br />
<br />
'''Level 1: Forward Calorimeter Cluster Finding'''<br />
<br />
Currently we are trying to develop Forward Calorimeter Cluster Finding algorithm which can be used in Level 1.<br />
We started from algorithm used in data analysis, and we hope to develop similar procedure to be loaded into<br />
FPGA.<br />
<br />
Ed's mail on FPGA-based look up tables:<br />
<br />
Thu, 25 Jan 2007 13:47:39 -0500 (EST)<br />
To: Serguei Boiarinov <boiarino@jlab.org><br />
CC: Hai Dong <hdong@jlab.org>, "C. Cuevas" <cuevas@jlab.org>,<br />
David Abbott <abbottd@jlab.org><br />
Subject: FPGA look up tables<br />
Hi Sergey,<br />
I did some investigating on the use of FPGA memory as a look up <br />
table for trigger system applications. For Altera FPGAs, the total <br />
on-chip memory can be up to 9 Mbits. However, the largest single RAM <br />
block is 512 Kbits. This can be organized as 64K x 8, 32K x 16, 16K <br />
x 32, ... , or 4K x 128. Larger chips have multiple 512 Kbit blocks <br />
(along with smaller and faster blocks). Thus, a look up table with as <br />
many as 16 inputs and 8 outputs can be created. Multiple tables can be <br />
created in the larger capacity FPGAs. The downside of using the large <br />
capacity FPGAs is that the pin count and cost also increases with memory <br />
capacity. For example, 9 Mbit Altera chips have pin counts of > 1000 <br />
pins (BGA) and cost ~$3000 each.<br />
To test the performance in an Altera FPGA, I created the following <br />
cascaded (2-level) look up table using 512 Kbit segments: (64K x 8, <br />
64K x 8) => (64K x 8). (i.e. 32 inputs => 8 outputs). The timing <br />
analysis performed by the Altera software indicates that the design will <br />
run at > 250MHz clock frequency. This fits in a 484 pin BGA (with much <br />
spare logic).<br />
I'll check with Hai Dong (Fast Electronics Group) about memory <br />
resources in Xilinx FPGAs. He may also be able to comment on the <br />
performance of such a look up table in a Xilinx target. It is probably <br />
comparable to the Altera's speed.<br />
- Ed J.<br />
<br />
Next preliminary CLAS12 Trigger System design was presented and discussed on TWG meeting<br />
February 28, 2007 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
CLAS trigger efficiency study was completed using e1-6 data, result is here<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.ps PostScript],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.pdf PDF].<br />
<br />
<br />
'''CLAS12 DAQ and Trigger'''<br />
<br />
We had several meetings in March, April and May and finally CLAS12 trigger design was completed. Following document was included into CLAS12 TDR2007. It also contains CLAS12 Data Aquisition System description, probably for the first time we have completed DAQ layout in one document.<br />
<br />
DAQ/Trigger section from TDR2007 can be found here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ps PostScript].<br />
<br />
The snapshot of the ''tex'' directory is here [http://clonwiki/wiki/clondocs/TDR2007/tex tex directory], permanent place is ''$CVSROOT/12gev/TDR/TDR2007/main/detector/daq_trigger''.<br />
<br />
Supporting slides (all pictures with short text) are here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clas12_sergey_timeline.pdf Timeline chart October 31, 2007 (pdf)]<br />
<br />
Nov 13, 2007: we are resuming project after DVCS Trigger design reached intermediate finish. Following links contains EC-related Level1 materials: <br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
Feb 1, 2008: first version of ECFinder in vhdl is ready and passed to Hai. Job was done by Sergey B. under Ben Raydo's supervision. Schematics:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.pdf PeakFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.eps PeakFinder(eps)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.pdf ClusterFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.eps ClusterFinder(eps)].<br />
<br />
<br />
Feb 13, 2008: first level 2 discussion, see [[February 13, 2008 online meeting minutes]].</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3247February 13, 2008 online meeting minutes2008-03-10T18:49:46Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.<br />
One important issue is related to the expected superlayer unefficiency: since we should be able to find the road using 5 out of 6 superlayers, region-based segment finding become not very useful so we'll not implement it on segment-finding level, although it can be taken into account somehow in road finder. Slides:<br />
<br />
<br />
We discussed several projects we want to complete during downtime. FASTBUS power supplies seems too low at +-5V current (115A), we may need to increase it to 230A, will discuss it with WIENER. Mark Jones asked to borrow 10 1877 TDCs, Sergey P. will test all boards arrieved recently and 10 boards will be provided. High Voltage 1535 boards are under testing by Sergey P. along with splitters, they will be installed in the Hall after testing. One of Lecroy mainframes in the counting house shows wierd behaviour, will be monitored closely using serial connection. Inventory database is in progress, will continue until everything is there. G9A data files with swap problem will be fixed and written to the SILO with extension *.B** (runs from 56097 to 56118). Sergey B. is planning to finish new firmware testing for v1190/v1290 TDCs - long time project.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3246February 13, 2008 online meeting minutes2008-03-10T18:49:23Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.<br />
One important issue is related to the expected superlayer unefficiency: since we should be able to find the road using 5 out of 6 superlayers, region-based segment finding become not very useful so we'll not implement it on segment-finding level, although it can be taken into account somehow in road finder.<br />
<br />
We discussed several projects we want to complete during downtime. FASTBUS power supplies seems too low at +-5V current (115A), we may need to increase it to 230A, will discuss it with WIENER. Mark Jones asked to borrow 10 1877 TDCs, Sergey P. will test all boards arrieved recently and 10 boards will be provided. High Voltage 1535 boards are under testing by Sergey P. along with splitters, they will be installed in the Hall after testing. One of Lecroy mainframes in the counting house shows wierd behaviour, will be monitored closely using serial connection. Inventory database is in progress, will continue until everything is there. G9A data files with swap problem will be fixed and written to the SILO with extension *.B** (runs from 56097 to 56118). Sergey B. is planning to finish new firmware testing for v1190/v1290 TDCs - long time project.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLAS12_Trigger_System_Design&diff=3245CLAS12 Trigger System Design2008-03-10T18:44:18Z<p>129.57.167.42: </p>
<hr />
<div>Leader: Sergey Boyarinov<br />
<br />
Support: Ben Raydo, David Doughty, Chris Cuevas, Ed Jastrzembski, Konstantin Mikhailov, Alex Vlassov<br />
<br />
Goal: CLAS12 Trigger System Design<br />
<br />
Status: in progress<br />
<br />
Project was planned in June 2006 to be completed during FY07. Actual job started in November 2006.<br />
We had several meetings discussing existing CLAS trigger, what can be improved<br />
in CLAS12 desing, and new technologies available today. Our work plan was summarized on Wednesday CLON<br />
meeting December 13, 2006 (see [[December 13, 2006 online meeting minutes]]).<br />
<br />
First very preliminary CLAS12 Trigger System design was presented and discussed on Friday upgrade meeting<br />
December 15, 2006 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
Trigger efficiency simulation is very important but was not started yet.<br />
<br />
'''Level 1: Forward Calorimeter Cluster Finding'''<br />
<br />
Currently we are trying to develop Forward Calorimeter Cluster Finding algorithm which can be used in Level 1.<br />
We started from algorithm used in data analysis, and we hope to develop similar procedure to be loaded into<br />
FPGA.<br />
<br />
Ed's mail on FPGA-based look up tables:<br />
<br />
Thu, 25 Jan 2007 13:47:39 -0500 (EST)<br />
To: Serguei Boiarinov <boiarino@jlab.org><br />
CC: Hai Dong <hdong@jlab.org>, "C. Cuevas" <cuevas@jlab.org>,<br />
David Abbott <abbottd@jlab.org><br />
Subject: FPGA look up tables<br />
Hi Sergey,<br />
I did some investigating on the use of FPGA memory as a look up <br />
table for trigger system applications. For Altera FPGAs, the total <br />
on-chip memory can be up to 9 Mbits. However, the largest single RAM <br />
block is 512 Kbits. This can be organized as 64K x 8, 32K x 16, 16K <br />
x 32, ... , or 4K x 128. Larger chips have multiple 512 Kbit blocks <br />
(along with smaller and faster blocks). Thus, a look up table with as <br />
many as 16 inputs and 8 outputs can be created. Multiple tables can be <br />
created in the larger capacity FPGAs. The downside of using the large <br />
capacity FPGAs is that the pin count and cost also increases with memory <br />
capacity. For example, 9 Mbit Altera chips have pin counts of > 1000 <br />
pins (BGA) and cost ~$3000 each.<br />
To test the performance in an Altera FPGA, I created the following <br />
cascaded (2-level) look up table using 512 Kbit segments: (64K x 8, <br />
64K x 8) => (64K x 8). (i.e. 32 inputs => 8 outputs). The timing <br />
analysis performed by the Altera software indicates that the design will <br />
run at > 250MHz clock frequency. This fits in a 484 pin BGA (with much <br />
spare logic).<br />
I'll check with Hai Dong (Fast Electronics Group) about memory <br />
resources in Xilinx FPGAs. He may also be able to comment on the <br />
performance of such a look up table in a Xilinx target. It is probably <br />
comparable to the Altera's speed.<br />
- Ed J.<br />
<br />
Next preliminary CLAS12 Trigger System design was presented and discussed on TWG meeting<br />
February 28, 2007 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
CLAS trigger efficiency study was completed using e1-6 data, result is here<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.ps PostScript],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.pdf PDF].<br />
<br />
<br />
'''CLAS12 DAQ and Trigger'''<br />
<br />
We had several meetings in March, April and May and finally CLAS12 trigger design was completed. Following document was included into CLAS12 TDR2007. It also contains CLAS12 Data Aquisition System description, probably for the first time we have completed DAQ layout in one document.<br />
<br />
DAQ/Trigger section from TDR2007 can be found here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ps PostScript].<br />
<br />
The snapshot of the ''tex'' directory is here [http://clonwiki/wiki/clondocs/TDR2007/tex tex directory], permanent place is ''$CVSROOT/12gev/TDR/TDR2007/main/detector/daq_trigger''.<br />
<br />
Supporting slides (all pictures with short text) are here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clas12_sergey_timeline.pdf Timeline chart October 31, 2007 (pdf)]<br />
<br />
Nov 13, 2007: we are resuming project after DVCS Trigger design reached intermediate finish. Following links contains EC-related Level1 materials: <br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
Feb 1, 2008: first version of ECFinder in vhdl is ready and passed to Hai. Job was done by Sergey B. under Ben Raydo's supervision. Schematics:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.pdf PeakFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.eps PeakFinder(eps)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.pdf ClusterFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.eps ClusterFinder(eps)].<br />
<br />
<br />
Feb 13, 2008: first level 2 discussion, see [[February 13, 2008 online meeting minutes]]. Sergey's slides are here:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan1.gif slide1],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan2.gif slide2],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan3.gif slide3],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan4.gif slide4].</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLAS12_Trigger_System_Design&diff=3244CLAS12 Trigger System Design2008-03-10T18:42:57Z<p>129.57.167.42: </p>
<hr />
<div>Leader: Sergey Boyarinov<br />
<br />
Support: Ben Raydo, David Doughty, Chris Cuevas, Ed Jastrzembski, Konstantin Mikhailov, Alex Vlassov<br />
<br />
Goal: CLAS12 Trigger System Design<br />
<br />
Status: in progress<br />
<br />
Project was planned in June 2006 to be completed during FY07. Actual job started in November 2006.<br />
We had several meetings discussing existing CLAS trigger, what can be improved<br />
in CLAS12 desing, and new technologies available today. Our work plan was summarized on Wednesday CLON<br />
meeting December 13, 2006 (see [[December 13, 2006 online meeting minutes]]).<br />
<br />
First very preliminary CLAS12 Trigger System design was presented and discussed on Friday upgrade meeting<br />
December 15, 2006 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
Trigger efficiency simulation is very important but was not started yet.<br />
<br />
'''Level 1: Forward Calorimeter Cluster Finding'''<br />
<br />
Currently we are trying to develop Forward Calorimeter Cluster Finding algorithm which can be used in Level 1.<br />
We started from algorithm used in data analysis, and we hope to develop similar procedure to be loaded into<br />
FPGA.<br />
<br />
Ed's mail on FPGA-based look up tables:<br />
<br />
Thu, 25 Jan 2007 13:47:39 -0500 (EST)<br />
To: Serguei Boiarinov <boiarino@jlab.org><br />
CC: Hai Dong <hdong@jlab.org>, "C. Cuevas" <cuevas@jlab.org>,<br />
David Abbott <abbottd@jlab.org><br />
Subject: FPGA look up tables<br />
Hi Sergey,<br />
I did some investigating on the use of FPGA memory as a look up <br />
table for trigger system applications. For Altera FPGAs, the total <br />
on-chip memory can be up to 9 Mbits. However, the largest single RAM <br />
block is 512 Kbits. This can be organized as 64K x 8, 32K x 16, 16K <br />
x 32, ... , or 4K x 128. Larger chips have multiple 512 Kbit blocks <br />
(along with smaller and faster blocks). Thus, a look up table with as <br />
many as 16 inputs and 8 outputs can be created. Multiple tables can be <br />
created in the larger capacity FPGAs. The downside of using the large <br />
capacity FPGAs is that the pin count and cost also increases with memory <br />
capacity. For example, 9 Mbit Altera chips have pin counts of > 1000 <br />
pins (BGA) and cost ~$3000 each.<br />
To test the performance in an Altera FPGA, I created the following <br />
cascaded (2-level) look up table using 512 Kbit segments: (64K x 8, <br />
64K x 8) => (64K x 8). (i.e. 32 inputs => 8 outputs). The timing <br />
analysis performed by the Altera software indicates that the design will <br />
run at > 250MHz clock frequency. This fits in a 484 pin BGA (with much <br />
spare logic).<br />
I'll check with Hai Dong (Fast Electronics Group) about memory <br />
resources in Xilinx FPGAs. He may also be able to comment on the <br />
performance of such a look up table in a Xilinx target. It is probably <br />
comparable to the Altera's speed.<br />
- Ed J.<br />
<br />
Next preliminary CLAS12 Trigger System design was presented and discussed on TWG meeting<br />
February 28, 2007 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
CLAS trigger efficiency study was completed using e1-6 data, result is here<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.ps PostScript],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.pdf PDF].<br />
<br />
<br />
'''CLAS12 DAQ and Trigger'''<br />
<br />
We had several meetings in March, April and May and finally CLAS12 trigger design was completed. Following document was included into CLAS12 TDR2007. It also contains CLAS12 Data Aquisition System description, probably for the first time we have completed DAQ layout in one document.<br />
<br />
DAQ/Trigger section from TDR2007 can be found here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ps PostScript].<br />
<br />
The snapshot of the ''tex'' directory is here [http://clonwiki/wiki/clondocs/TDR2007/tex tex directory], permanent place is ''$CVSROOT/12gev/TDR/TDR2007/main/detector/daq_trigger''.<br />
<br />
Supporting slides (all pictures with short text) are here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clas12_sergey_timeline.pdf Timeline chart October 31, 2007 (pdf)]<br />
<br />
Nov 13, 2007: we are resuming project after DVCS Trigger design reached intermediate finish. Following links contains EC-related Level1 materials: <br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
Feb 1, 2008: first version of ECFinder in vhdl is ready and passed to Hai. Job was done by Sergey B. under Ben Raydo's supervision. Schematics:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.pdf PeakFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.eps PeakFinder(eps)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.pdf ClusterFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.eps ClusterFinder(eps)].<br />
<br />
<br />
Feb 13, 2008: first level 2 discussion, see [[February 13, 2008 online meeting minutes]]. Sergey's slides are here:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clon_13feb2008_scan1.gif slide1],</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLAS12_Trigger_System_Design&diff=3243CLAS12 Trigger System Design2008-03-10T18:39:54Z<p>129.57.167.42: </p>
<hr />
<div>Leader: Sergey Boyarinov<br />
<br />
Support: Ben Raydo, David Doughty, Chris Cuevas, Ed Jastrzembski, Konstantin Mikhailov, Alex Vlassov<br />
<br />
Goal: CLAS12 Trigger System Design<br />
<br />
Status: in progress<br />
<br />
Project was planned in June 2006 to be completed during FY07. Actual job started in November 2006.<br />
We had several meetings discussing existing CLAS trigger, what can be improved<br />
in CLAS12 desing, and new technologies available today. Our work plan was summarized on Wednesday CLON<br />
meeting December 13, 2006 (see [[December 13, 2006 online meeting minutes]]).<br />
<br />
First very preliminary CLAS12 Trigger System design was presented and discussed on Friday upgrade meeting<br />
December 15, 2006 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger.ppt.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
Trigger efficiency simulation is very important but was not started yet.<br />
<br />
'''Level 1: Forward Calorimeter Cluster Finding'''<br />
<br />
Currently we are trying to develop Forward Calorimeter Cluster Finding algorithm which can be used in Level 1.<br />
We started from algorithm used in data analysis, and we hope to develop similar procedure to be loaded into<br />
FPGA.<br />
<br />
Ed's mail on FPGA-based look up tables:<br />
<br />
Thu, 25 Jan 2007 13:47:39 -0500 (EST)<br />
To: Serguei Boiarinov <boiarino@jlab.org><br />
CC: Hai Dong <hdong@jlab.org>, "C. Cuevas" <cuevas@jlab.org>,<br />
David Abbott <abbottd@jlab.org><br />
Subject: FPGA look up tables<br />
Hi Sergey,<br />
I did some investigating on the use of FPGA memory as a look up <br />
table for trigger system applications. For Altera FPGAs, the total <br />
on-chip memory can be up to 9 Mbits. However, the largest single RAM <br />
block is 512 Kbits. This can be organized as 64K x 8, 32K x 16, 16K <br />
x 32, ... , or 4K x 128. Larger chips have multiple 512 Kbit blocks <br />
(along with smaller and faster blocks). Thus, a look up table with as <br />
many as 16 inputs and 8 outputs can be created. Multiple tables can be <br />
created in the larger capacity FPGAs. The downside of using the large <br />
capacity FPGAs is that the pin count and cost also increases with memory <br />
capacity. For example, 9 Mbit Altera chips have pin counts of > 1000 <br />
pins (BGA) and cost ~$3000 each.<br />
To test the performance in an Altera FPGA, I created the following <br />
cascaded (2-level) look up table using 512 Kbit segments: (64K x 8, <br />
64K x 8) => (64K x 8). (i.e. 32 inputs => 8 outputs). The timing <br />
analysis performed by the Altera software indicates that the design will <br />
run at > 250MHz clock frequency. This fits in a 484 pin BGA (with much <br />
spare logic).<br />
I'll check with Hai Dong (Fast Electronics Group) about memory <br />
resources in Xilinx FPGAs. He may also be able to comment on the <br />
performance of such a look up table in a Xilinx target. It is probably <br />
comparable to the Altera's speed.<br />
- Ed J.<br />
<br />
Next preliminary CLAS12 Trigger System design was presented and discussed on TWG meeting<br />
February 28, 2007 ([http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.ppt PowerPoint],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_Trigger_TWG_Feb_2007.htm HTML]).<br />
<br />
'''Trigger Efficiency Studies'''<br />
<br />
CLAS trigger efficiency study was completed using e1-6 data, result is here<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.ps PostScript],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/2007-009.pdf PDF].<br />
<br />
<br />
'''CLAS12 DAQ and Trigger'''<br />
<br />
We had several meetings in March, April and May and finally CLAS12 trigger design was completed. Following document was included into CLAS12 TDR2007. It also contains CLAS12 Data Aquisition System description, probably for the first time we have completed DAQ layout in one document.<br />
<br />
DAQ/Trigger section from TDR2007 can be found here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ps PostScript].<br />
<br />
The snapshot of the ''tex'' directory is here [http://clonwiki/wiki/clondocs/TDR2007/tex tex directory], permanent place is ''$CVSROOT/12gev/TDR/TDR2007/main/detector/daq_trigger''.<br />
<br />
Supporting slides (all pictures with short text) are here<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/TDR2007/TDR2007_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/clas12_sergey_timeline.pdf Timeline chart October 31, 2007 (pdf)]<br />
<br />
Nov 13, 2007: we are resuming project after DVCS Trigger design reached intermediate finish. Following links contains EC-related Level1 materials: <br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.ppt Power Point],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.pdf PDF],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/TDR2008_DAQ_TRIGGER.htm HTML].<br />
<br />
<br />
Feb 1, 2008: first version of ECFinder in vhdl is ready and passed to Hai. Job was done by Sergey B. under Ben Raydo's supervision. Schematics:<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.pdf PeakFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF1.eps PeakFinder(eps)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.pdf ClusterFinder(pdf)],<br />
[http://clonwiki/wiki/clondocs/CLAS12_Trigger/CLAS12_TRIGGER_CF2.eps ClusterFinder(eps)].<br />
<br />
<br />
Feb 13, 2008: first level 2 discussion on CLON meeting. Sergey's slides are here.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3242February 13, 2008 online meeting minutes2008-03-10T18:16:36Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.<br />
<br />
We discussed several projects we want to complete during downtime. FASTBUS power supplies seems too low at +-5V current (115A), we may need to increase it to 230A, will discuss it with WIENER. Mark Jones asked to borrow 10 1877 TDCs, Sergey P. will test all boards arrieved recently and 10 boards will be provided. High Voltage 1535 boards are under testing by Sergey P. along with splitters, they will be installed in the Hall after testing. One of Lecroy mainframes in the counting house shows wierd behaviour, will be monitored closely using serial connection. Inventory database is in progress, will continue until everything is there. G9A data files with swap problem will be fixed and written to the SILO with extension *.B** (runs from 56097 to 56118). Sergey B. is planning to finish new firmware testing for v1190/v1290 TDCs - long time project.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3241February 13, 2008 online meeting minutes2008-03-10T18:06:12Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong<br />
<br />
We had first discussion on CLAS12 level2 trigger design which is optional for CLAS12 uograde. Sergey B. described general design for Segment Finder and Road Finder components. In according to the plan level2 will be not a pipeline system, it will start on level1 accept signal. Segment finder will process data from entire superlayer, and execution time will be constant for any number of hits. Road finder will process input segments one by one, and the maximum number of possible combinations will be set; if that number is exceeded then level2 will issue 'l2pass' signal. Dave made several useful comments, and Sergey will continue with design.</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=February_13,_2008_online_meeting_minutes&diff=3240February 13, 2008 online meeting minutes2008-03-10T16:35:37Z<p>129.57.167.42: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Dave Doughty, Hai Dong</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_January_30,_2008&diff=3239CLON meeting January 30, 20082008-03-10T16:32:56Z<p>129.57.167.42: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, January 30 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Projects status<br />
<br />
* CLAS12 trigger<br />
<br />
* CLON inventory<br />
<br />
<br />
2. G9A run status</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=3238CLON Group Meetings2008-03-10T16:32:25Z<p>129.57.167.42: </p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
==== 2007<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
==== 2008<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_February_13,_2008&diff=3237CLON meeting February 13, 20082008-03-10T16:30:15Z<p>129.57.167.42: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, February 13 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Projects status<br />
<br />
* CLAS12 trigger, level 2 - first discussion<br />
<br />
* work in the Hall during downtime</div>129.57.167.42https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_February_13,_2008&diff=3236CLON meeting February 13, 20082008-03-10T16:29:54Z<p>129.57.167.42: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, February 13 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Projects status<br />
<br />
- CLAS12 trigger, level 2 - first discussion<br />
<br />
- work in the Hall during downtime</div>129.57.167.42