<!-- Title: 14:09:39  Thu Mar 10 2005 -->
<!-- Crewchief: Rick Tesarek -->
<!-- Op1: Thijs Wijnands -->
<!-- Op2: Christian Piagnard -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Begin logbook.</pre>


<!-- Date: Wed Mar 16 08:58:42 2005 -->
<pre>Date: Wed, 16 Mar 2005 15:56:29 +0100 
From: Thijs Wijnands &lt;Thijs.Wijnands@cern.ch&gt; 
To: Rick Tesarek &lt;tesarek@fnal.gov&gt; 
Subject: logbook 
Parts/Attachments: 
   1   OK    ~18 lines  Text (charset: ISO-8859-1) 
   2 Shown   ~30 lines  Text (charset: ISO-8859-1) 
---------------------------------------- 
 
Hi Rick 
  
Me again. Here is something for the e-log book if you like : 
  
================================================================ 
RADMON   -   CDF Radiation Monitoring 
================================================================ 
Intel(R) Pentium(R) 4 CPU 2.80GHz 2800MHz (512KB cache) 511 MB memory 
Linux i686 2.4.20-30.7.cern (AFS: i386_linux24) 
================================================================ 
 
Cheers - Thijs 
 
</pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Mon Apr 4 10:12:11 2005 -->
<pre>Date: Tue, 22 Mar 2005 13:55:29 -0600 
From: Tim Gierhart &lt;gierhart@fnal.gov&gt; 
To: tesarek@fnal.gov, 'Bourov Serguei I' &lt;bourov@fnal.gov&gt; 
Cc: bd-network@fnal.gov 
Subject: FW: Network Service Request Status 
 
 
 
-----Original Message----- 
From: netmanager@fnal.gov [mailto:netmanager@fnal.gov]  
Sent: Tuesday, March 22, 2005 1:39 PM 
To: gierhart@fnal.gov 
Subject: Network Service Request Status 
 
 
Your network service request # 97471 detail # 112174 has been completed. 
Any changes will be effective with the next name server reload(might need 24 
or more hours). 
You also might need to do the following to complete your networking setups: 
Request Kerberos principal, ftp, or related items: 
http://www.fnal.gov/docs/strongauth/html/unixinstall.html#27180 
Fermilab Web Server Security: 
http://computing.fnal.gov/security/WebServers/ 
Hardware/Software Maintenance:  http://www-esd.fnal.gov/contracts/ 
 
The computer has logged the following comments against your request: 
 
* Request # 97471 detail 112174 completed. 
* System RADMON created with system number N49748. 
* Asset created with class of CPU BOX, 
  serial number of 000CF1C69935. 
* Added asset to system. 
* Created owner claim on asset for FL/BD. 
* Hardware address 00-0C-F1-C6-99-35 attached to asset  
  CPU BOX Property Tag:  
* Created IP NODE RADMON @ 131.225.127.40. 
* The Network Mask will be: 255.255.255.0. 
* The Default Gateway Address will be: 131.225.127.200. 
* The Broadcast Address will be: 255.255.255.255. 
* The Primary Name Server will be: 131.225.8.120 
* The Secondary Name Server will be: 131.225.17.150 
*  ** 
*  If you are running Windows NT: 
*       Primary WINS Server - 131.225.9.1 
*       Secondary WINS Server - 131.225.110.15 
</pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Wed Apr 13 10:43:44 2005 -->
<pre>From Thijs.Wijnands@cern.ch Wed Apr 13 07:29:14 2005 
Date: Wed, 13 Apr 2005 14:29:24 +0200 
From: Thijs Wijnands &lt;Thijs.Wijnands@cern.ch&gt; 
To: Rick Tesarek &lt;tesarek@fnal.gov&gt; 
Subject: Boot & NTP servers FNAL 
 
Hi Rick 
  
Here is some information for the PC and for your controls experts. 
  
We have used the info in the e-log to set up the PC as far as we 
could, the 
IPs from the NTP servers are missing though (maybe not post all this 
on the 
web as it may invite hackers ?) 
  
1/ In /etc/ntp.conf you will find 
  
#restrict default noquery notrust nomodify 
#restrict 127.0.0.1 
#restrict 137.138.0.0 mask 255.255.0.0 
#restrict 137.138.16.69 
#restrict 137.138.17.69 
driftfile /etc/ntp.drift 
logfile /var/log/ntp.log 
server  137.138.16.69 
server  137.138.17.69 
  
and this we have to set to standard FNAL settings 
  
2/ Same for the file etc/ntp/step_tickers 
  
3/ Furthermore in /etc/grub.conf 
  
     default=2  -&gt; default=4 
  
4/ If IP address is wrong, we have to change 
  
/etc/boot-config/FNAL 
  
which is the boot config file I made for Fermilab. 
  
Best regards 
  
Thijs 
</pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Mon Apr 25 15:44:31 2005 -->
<pre>Rick and Serguei: 
Jim Patrick conveyed a request from you to connect RADMON in CDF to the 
AD controls network and to scan for any holes, etc.  We have configure 
port 9 on the switch, s-ad-c-2950-cdf, to accept traffic from mac 
address 00-0C-F1-C6-99-35 (the address we have registered for this 
device), but have the port shutdown at the moment.  We would like to 
have the node up and running with it physically connected to the switch 
port 9 first, and then we will enable the port and scan the device.  Is 
this reasonable or do you need further assistance?  Please respond to 
Tim Zingelman (zingelman@fnal.gov) and myself (dstenman@fnal.gov). 
Dan Stenman 
 
</pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Mon Apr 25 15:52:07 2005 -->
<pre>The radmon.fnal.gov node is up and connected "to port 9 on the switch, s-ad-c-2950-cdf,"                                                                                                       
</pre>
<!-- Author: Sergei -->


<!-- Date: Mon Apr 25 16:00:36 2005 -->
To be specific about the hookup.
<!-- Author: JJ -->


<!-- Date: Mon Apr 25 16:05:49 2005 -->
TRY AGAIN! 
To be Specific about the hookup... 
<ul> 
<li>A patch cable goes from RADMON PC in 1RR12H<br> 
    to port #1 on network patch panel in 1RR12D. 
<li>In third floor DataComm rack, 1RR12D/1 is  
    patched to 2RR02E/4. 
<li>In control room, port #4 on network patch panel in 2RR02E<br> 
    is patched to port #9 on AD switch s-ad-c-2950-cdf . 
</ul>
<!-- Author: JJ -->