Computers

NAT

10.0.0.1 # cisco firewall, default gateway

defines the 10.0.x.x private network for GT. The WAN name for this NAT is gt1.phy.anl.gov. Note: this NATBOX is not the standard GT ASA box; but the NAT box we use many places at ANL.

Decomposition computers

10.0.1.100              n0000 n0000.gam
10.0.1.1                n0001 n0001.gam
.
.
10.0.1.62               n0062 n0062.gam

n0000 is the Global Event Builder (GEB). The other ~60 nodes are decomposition computers. A few of them are dead.

mysterious IP addresses

10.2.0.1   ipmi-master_eth
10.2.0.200 ipmi-master
10.2.0.98  ipmi-a1.gam
10.2.0.52       fs1-bmc
10.2.0.154 ipmi-r610

# IPMI
#
10.2.1.100              ipmi-n0000
10.2.1.1                ipmi-n0001
10.2.1.2                ipmi-n0002
10.2.1.3                ipmi-n0003
.
.
10.2.1.58               ipmi-n0058
10.2.1.59               ipmi-n0059
10.2.1.60               ipmi-n0060
10.2.1.61               ipmi-n0061
10.2.1.62               ipmi-n0062

service/analysis computers

10.0.0.5	dell-6248-master # Dell swith, master, middle rack
10.0.0.7	dell-6248-shack # Dell swith, up on the shack

10.0.0.79	a0.gam a0 a0.gam.nscl.msu.edu
10.0.0.98	a1.gam.nscl.msu.edu a1.gam
10.0.0.99	a2.gam a2 a2.gam.nscl.msu.edu

The role of a1.gam is that of the NIS server, but like a2.gam it is also used for general software developments. At the moment we run all the DAQ control screens (and soft IOCs) from a1.gam

10.0.0.10	dogs.gam dogs dogs.gam.nscl.msu.edu

the decomposition machines get their systems from dogs (true?)

10.0.0.50	fs.gam fs fs.gam.nscl.msu.edu
10.0.0.51	fs2.gam fs2 fs2.gam.nscl.msu.edu
10.0.0.52	fs1.gam fs1 fs1.gam.nscl.msu.edu

the root host machine for fs1.gam is a1 (we think)

10.0.0.70	spdaq44 spdaq44.gam
10.0.0.71	spdaq38 spdaq38.gam
10.0.0.85	op0.gam op0 op0.gam.nscl.msu.edu
10.0.0.86	op1.gam op1 op1.gam.nscl.msu.edu
10.0.0.29	op2.gam op2 op2.gam.nscl.msu.edu
10.0.0.30	op3.gam op3 op3.gam.nscl.msu.edu
10.0.0.31	op4.gam op4 op3.gam.nscl.msu.edu
10.0.0.32	op5.gam op5 op5.gam.nscl.msu.edu
10.0.0.33	op6.gam op6 op6.gam.nscl.msu.edu
10.0.0.34	op7.gam op7 op7.gam.nscl.msu.edu
10.0.0.35	op8.gam op8 op8.gam.nscl.msu.edu
10.0.0.36	op9.gam op9 op9.gam.nscl.msu.edu
10.0.0.37	e1.gam e1 e1.gam.nscl.msu.edu
10.0.0.38	e2.gam e2 e2.gam.nscl.msu.edu
10.0.0.39	m1.gam m1 m1.gam.nscl.msu.edu
10.0.0.40	m2.gam m2 m2.gam.nscl.msu.edu
10.0.0.60	metal.gam metal metal.gam.nscl.msu.edu

10.0.0.11	gret-ts.gam gret-ts gret-ts.gam.nscl.msu.edu

10.0.0.110	sol.gam sol.gam.nscl.msu.edu sol

sol is the boothost for all the Digiticer IOCs

The computers above get their password file via NIS from a1.gam. Not all computers exists

Digiticer IOCs

10.0.3.1		vme01
10.0.3.2		vme02
.
.
10.0.3.47		vme47
10.0.3.48		vme48
10.0.3.49		vme49

User and access computers

10.0.10.11     reserved for tl laptop
10.0.10.12     ws1.gam ws1
10.0.10.13     ws2.gam ws2
10.0.10.14     ws3 gam ws3

these computers have their own password files independent of the NIS server a1.gam. In particular, access to ws1 is restricted to personel that need outside access to the GRETINA network at anl. (ws1), ws2 and ws3 are general purpose linux workstations for users to use and sort data on during experiments.

LN fill computers

10.0.4.11		gln1
10.0.4.12		gln2

misc other computers we know of

10.0.4.1       caenps01
10.0.4.2       caenps02
10.0.8.11	jays-happy-place
10.0.8.12	daqtape
10.0.9.11	middlemac

computer shutdown procedure

(for computers in g126 computer room)

- log in to ws1
  umount anything from fs1.gam (or you will have
  problems shutting down ws1) 
  [maybe not have anything mounted from fs1 anymore!?]
- a2.gam  (shutdown -h now)
- sol.gam (shutdown -g0 now) turn power off by hand
- ssh [email protected]
    pdsh -w n00[00-61] shutdown -h now
    shutdown dogs.gam (shutdown -h now)
- ssh [email protected]
    lsof | grep global <--- kill processes
    pkill -u gretina
    pkill CArepeater
    umount anything from fs1.gam
    then shutdown fileserver fs1.gam as
       ssh fs1.gam, then issue command 'halt -t 1'
       rsh fs1.gam halt -t 1 <-- not correct
- Turn off the file server shelves
- Turn off the file server head
- a1.gam (shutdown -h now)
- 2 switches in racks sw02  & sw03
- power off gt1.phy.anl.gov (ws1) (shutdown -h now)
- power off NAT box
- throw 5 three phase switches in control panel

computer powerup procedure

- switches - sw02 and sw03
- fileserver - fs1.gam
   - Turn on fs1.gam head
   - Turn on the shelves
- NIS master - a1.gam
- a2.gam
- sol.gam
- dogs cluster
   - Power on dogs.gam
   - 'sh /root/ipmi/ipmi.poweron' to use IPMI to power on all compute nodes
- the super nodes
- 30 VMEs
- op3.gam
- op4.gam
- op5.gam

move dFMA DAQ to the GT network

To move the digital FMA DAQ (dFMA) from onenet network to the GT network, a number of steps must be followed. They are outlined below

On the GRETINA network, we will used these IP addresses for dFMA

10.0.50.189   dfma_darek  'set manually'
10.0.50.190   dfma_ts     'set manually'
10.0.50.191   dfma_ioc0   telnet dfma_ts 2004 TRIGGER VME32.cmd
10.0.50.192   dfma_ioc1   telnet dfma_ts 2001
10.0.50.193   dfma_ioc2   telnet dfma_ts 2002
10.0.50.194   dfma_ioc3   telnet dfma_ts 2003
10.0.50.195   dfma_ioc4   telnet dfma_ts 2005
10.0.50.196   dfma_ioc5   telnet dfma_ts 2012
10.0.50.197   dfma_ioc6   telnet dfma_ts 2007
10.0.50.198   dfma_ioc7   telnet dfma_ts 2008
10.0.50.199   dfma_ioc8   telnet dfma_ts 2009
10.0.50.200   dfma_ioc9   not there
10.0.50.201   dfma_ioc10  telnet dfma_ts 2010
10.0.50.202   dfma_ioc11  telnet dfma_ts 2011
10.0.50.203   dfma_ioc12  not there
10.0.50.204   dfma_ioc13  not there
10.0.50.205   dfma_ioc14  not there
10.0.50.205   dfma_ioc15  not there

Also shown in the list are the terminal access commands (subject to change in the future)

- First access all the OICs and reboot them, but leave them at the boot prompt. Type 'ctrl x' and then hit any key when they try to boot.

- now log into the terminal server through it's web interface 'firefox://192.168.203.190'. The username is 'root' and the password should be known to whoever tries this procedure. Now do this

IP setting
  change IP to 10.0.50.190
  with netmask 255.255.0.0
  Gateway 10.0.0.1
DNS setting
  10.0.0.1
reboot and turn off

-After this step, the terminal server does not function on onenet anymore, but it should come alive on the GT network. On onenet we use DHCP to get the terminal server on the net; but on the GT net we have no DHCP server, so we have to set the IP and netmask manually. Be careful about this step!! If you do it wrong, you may have trouble getting to the terminal server again.

-change the IP and netmask on the dfma_darek computer from DHCP to 10.0.50.189 and 255.255.0.0. Specify 10.0.0.1 for the router as well as DNS.

-now switch the WAN connection on the switch from onenet to GT

-reboot dfma_darek, or restart the network if you just stopped it. The machine should come up on the GT network.

-turn on the dfma_ts terminal server. If the above steps were done properly, it should come up on the GT network

-on dfma_darek, change the entries in the /etc/hosts to have these entries rather than the onenet IPs

 10.0.50.189 dfma_darek
 10.0.50.190 dfma_ts
 10.0.50.191 dfma_ioc0
 10.0.50.192 dfma_ioc1
 10.0.50.193 dfma_ioc2
 10.0.50.194 dfma_ioc3
 10.0.50.195 dfma_ioc4
 10.0.50.196 dfma_ioc5
 10.0.50.197 dfma_ioc6
 10.0.50.198 dfma_ioc7
 10.0.50.199 dfma_ioc8
 10.0.50.200 dfma_ioc9
 10.0.50.201 dfma_ioc10
 10.0.50.202 dfma_ioc11
 10.0.50.203 dfma_ioc12
 10.0.50.204 dfma_ioc13
 10.0.50.205 dfma_ioc14
 10.0.50.205 dfma_ioc15

-now, through the terminal server, access the IOCs, one by one, and change the IP

 from
   192.168.1.n:ffffff00
 to
   10.0.50.m:ffff0000
  

where n is the one from oenent and where 'm' is in the table above. Also change the gateway

 from
   192.168.203.189
 to 
   10.0.50.189

You should now be able to boot the IOC (type @)

- once all IOC are rebooted, you should be able to start the dFMA DAQ by typing this command

 (cd; dfmaCSS)

remember to start the soft IOC.

NOTE: the dFMA DAQ can function on the onenet with the dGS and with GRETINA on the GT network because the dFMA DAQ is using these non standard EPICS ports

 export EPICS_CA_SERVER_PORT=5068
 export EPICS_CA_REPEATER_PORT=5069