Download Nees@UCSB Computer Systems:

Nees@UCSB Computer Systems:
Inventory, Configuration and Administration
Prepared by the Institute for Crustal Studies, UCSB
Copyright 2004
Version 1.02 December 17, 2004
1.0 Background
The NEES equipment site at UCSB relies on several computer systems running Linux
and Solaris. The following describes the configuration of these systems and provides
serial numbers and other important support tracking information.
In order to recover from catastrophic failure and keep track of changes that may affect the
operation or performance of all systems, procedures are followed that track important
files and record changes made to them. This tracking is not an automated system. You
must take small steps to record changed files into a version control system (VCS). Please
see Appendix A for more information on CVS, the Concurrent Versions System, and
instructions on saving changes to files.
1.1.1 Captains.log
The file
/root/captains.log
is a written log of changes and actions taken by the system administrator (root, etc.) to
subsystems and program configurations. (Changes to the Antelope DAQ software are
recorded in a different log file.) Entries in the log are in reverse chronological order so
the most recent change is listed first. Any system administrator that changes
configuration files, starts or stops daemon programs permanently, updates packages and
so forth, should make a brief note of those changes here. In particular if the system
behaves differently, this log will provide some information on recent changes that may be
the cause.
1.1.2 CVS Repository
In the directory
/root/cvs
is a directory tree that matches that of the system, with directories like etc, home, usr, etc.
Important system files are copied here so they can be placed into version control. See
Appendix A for more information on CVS.
2.0 HP Servers Running Linux
There are several servers manufactured by Hewlett Packard, running Red Hat Linux
Advanced Server 3.0 on Intel Xeon processors. This OS is available through special
educational licensing for $50 a year from Red Hat. The DL360 systems have dual Xeon
processors and RAID mirroring. The cost-effective DL140 is a single processor systems
with an IDE drive.
2.1 HP Proliant DL360 Servers
The NEESPop and Telepresence systems run the NEESgrid portal “CHEF” and
telepresence software:
Serial #
Model #
Drives:
Memory:
Warranty:
OS:
NIC:
nees.ucsb.edu
tpm.nees.ucsb.edu
6J38KYD1VON5
6J38KYD1V0NB
HP DL360 G3
HP DL360 G3
2x 147GB
2x 36GB
1GB (2x512 PC2100 ®)
1GB (2x512 PC2100 ®)
24/7 4hr Onsite. 3yr, @ 9-15-2004
RHN AS 3.0
RHN AS 3.0
2 x Broadcom BCM5703
2 x Broadcom BCM5703
2.1.1 Proliant DL360 Web Links
Home Page:
http://h18004.www1.hp.com/products/servers/proliantdl360/description-g3.html
Support Page:
http://welcome.hp.com/country/us/en/support.html
Drivers Page:
http://h18000.www1.hp.com/support/files/server/us/locate/101_4764.html
2.1.2 OS, Driver and Network Configuration
Red Hat Linux Advanced Server 3.0 is running on these systems. The Advanced Server
is the OS version officially supported by NEESgrid software. RH AS 3.0 was installed
with custom settings for each system for disk partition and packages.
Driver Configuration: See the section Proliant Support Pack below.
Network Configuration:
These dual channel systems are configured to connect to both the public Internet and the
VPN linking Garner Valley, Wildlife and UCSB. They do not bridge these networks and
the firewall specifically does not allow connections to bridge.
A route is configured on the second interface to route all VPN traffic (Garner Valley and
Salton Sea) to the local VPN router (gateway:192.168.0.1, netmask:255.255.0.0,
address=192.168.0.0). The network was configured with the xwindows utility
redhat-config-network which creates the expected files in
/etc/sysconfig/network-scripts.
Interface:
eth0
eth1
IP Address:
128.111.236.176
192.168.0.4
Interface:
eth0
eth1
IP Address:
128.111.236.177
192.168.0.5
NEESpop Server
Hostname :
nees.ucsb.edu, nees
icspop
Speed:
1GB/sec
100MB/sec
Telepresence Server
Hostname :
Speed:
tpm.nees.ucsb.edu, tpm 1GB/sec
icstpm
100MB/sec
2.2.1 Red Hat Network Updates
Note:
Red Hat Network Login Information:
URL:
http://www.redhat.com/software/rhn/
Login:
ucsb-nees
Password: 4Nees2RHN
Emails are sent to [email protected] from the Red Hat Network for all security and
other updates that are available. Note: it is not recommended that the kernel be updated
without consulting NITSC to assure that the NEESgrid software has been tested on the
new kernel version. Likewise, the Proliant Support Pack may also be incompatible with
the new kernel.
2.2.2 Proliant Support Pack
The Proliant Support Pack is a collection of drivers and system management tools
specifically for the DL360. The support pack comes with a graphical installation
program that should be run after any system/package updates because they may erase
Support Pack settings. The latest version of the software can be found on the drivers page
listed above.
The support pack installs custom drivers for the raid array, NIC cards and Lights-out
manager. It also comes with a web accessible system monitoring interface. The interface
can be access at:
http://[server-name-or-ip]:2301/
The Administrator login is the same as the root login. The monitoring system uses SNMP
to communicate system information to the web utility and any SNMP receiver configured
to receive the messages. The support pack is configured to shutdown the system if the
temperature of the CPU’s or other monitored areas, and turn the system back on after 10
minutes.
The Support Pack is can be installed from
/usr/local/src/compaq/csp/linux
Note that the PSP has replaced the Insight Manager that was originally installed on the
system. The latest version of Insight Manager requires the installation of the Postgress
database. It likely contains some features over the PSP, such as the ability to query the
system status (without using the web interface), but the overhead is significant and the
features appear to be weighed toward very large scale installations.
2.2 HP DL140 Server
The DL140 (rolled) operates as a backup to the Sun (shaken), communicating to the
dataloggers and transmitting waveform data to UCSB. With it’s very large storage
capacity (200GB) it also serves as a local storage system that is especially useful in the
event of loss of communications with the remote Garner Valley site. It is a single CPU
server with an Intel CPU:
“rolled”
Serial #
Model #
Drives:
Memory:
Warranty:
OS:
NIC:
HP DL140
1x 80GB IDE, 1x 200GB external firewire
512MB
1yr, Limited – Parts @ ??
RHN AS 3.0
2 x Broadcom BCM5703
Proliant DL140 Web Links:
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?locale=en_US&
submit.y=5&lang=en&cc=us&submit.x=4&prodTypeId=15351&prodSeriesId=37461
7
2.2.1 OS, Driver and Network Configuration
The system runs Red Hat Advanced Server 3.0. Please see the link above, in section
2.1.1, to obtain updates and OS support at Red Hat. The system has an external firewire
drive. In order to provide drivers for the device, a special module was installed from Red
Hat, the “kernel- unsupported” module (the actual module name matches the OS release
version) has been installed. Fur ther, the script /etc/rescan-scsi-bus.sh was
installed from http://linux1394.org. Finally, the drive must be mounted
manually. This is done in the startup script /etc/rc.local, where the module is
loaded and then the SCSI bus rescanned with the script.
There is a driver pack available from HP for this system. However, initial attempts to
install it conflicted with the firewire drivers. A second attempt, using updated packages is
scheduled as of this writing. Besides the firewire drive support, there are no other custom
modules or configurations.
Firewire Drive:
The drive as Maxtor “OneTouch” 250GB Firewire/USB (model A01A250) :
http://www.maxtor.com/_files/maxtor/en_us/documentation/data_sheets/onetouch_data_s
heet.pdf
It is attached with an Adaptec FireConnect 8300:
http://graphics.adaptec.com/pdfs/FC8300high_res.pdf
The network is configured as follows:
Interface:
eth0
eth1
IP Address:
172.16.235.33
192.168.2.6
DL140 Antelope Server
Hostname :
rolled
gvaroll
Speed:
100MB/sec
100MB/sec
3.0 Sun Servers Running Solaris
The seismic data collection is accomplished through several different systems, local to
the array sites and at the UCSB campus. These systems run Antelope from Boulder Real
Time Technologies, as well as the PASSCAL software and other utilities.
3.1 Sun Netra 120
There are two identical Sun Netra 120 servers, one at Garner Valley and a second at
UCSB. These are NEBS certified equipments designed to withstand telco operational
conditions. The system in Garner Valley has been tested on a shake table. Since it can
operate without any moving parts, it is expected to remain operational even in a large
earthquake.
Serial #
Model #
Drives:
Memory:
shaken.nees.ucsb.edu
CF31301202
SUN Netra 120
1 x 1GB Flash, 1 x 32GB SCSI
1GB
stirred.nees.ucsb.edu
CF31301191
Sun Netra 120
1 x 1GB Flash, 1 x 32GB SCSI
1GMB
Warranty:
OS:
NIC:
Solaris 9
Solaris 9
3.1.1 Netra 120 Weblinks:
Netra Home Page:
http://www.sun.com/products- n-solutions/hw/networking/120/
3.1.2 OS, Driver and Network Configuration
Solaris 9 on local drive
Solaris 9 on Flash Drive
The network on Solaris is configured through the files /etc/hosts,
/etc/hostname.eri0 and /etc/hostname.eri1. Normally, network routing is
accomplished through the file /etc/netmasks, however, we found it necessary to add
our routes, setting up a startup scrip, /etc/rc2.d/S69inet, which sets routes in the
file /etc/staticroutes. The hosts file must contain IP numbers and hostnames that
match the hostnames in the corresponding interface file. The netmasks file contains the
network and mask that define what class a connection is (ICS is a class C network).
Shaken, Garner Valley Server
Hostname :
shaken
gvashake
Interface:
eri0
eri1
IP Address:
192.168.2.5
172.16.235.34
Interface:
eri0
eri1
IP Address:
128.111.236.181
192.168.0.3
Stirred, ICS Server
Hostname :
stirred.nees.ucsb.edu, stirred
icsstir
Speed:
auto
auto
Speed:
auto
auto
3.3 Sun Blade 150
Blade 150 Documentation Home Page:
http://www.sun.com/products-nsolutions/hardware/docs/Workstation_Products/Workstations/Sun_Blade_Wor
kstations/Sun_Blade_150/index.html
A desktop system is available that supports both Solaris 9 and Windows (via the Sun PCI
card). The system has reasonable memory and processing power for program
development and seismic signal processing.
4.0 Intrynsic CerfCube Running Linux
At the Salton Sea Wildlife refuge, due to the solar power requirements, a low power
internet device was selected which had been tested previously with the Antelope data
collection software.
Intrynsic Cerfcube home page :
http://www.intrinsyc.com/products/cerfcube/
cube.nees.ucsb.edu
Serial #
Model #
Drives:
Memory:
64MB
Warranty:
OS:
NIC:
5.0 Dell Rackmount Servers Running Windows
Data acquisition for the SFSI structure is provided through Dell servers running MS
Windows and Digitexx software.
Appendix A – CVS Repository
Concurrent Versions System is an open source version control system for tracking
changes to files and marking groups of files with label so they can be recovered as a
group. A CVS repository exists on rattle.crustal.ucsb.edu contain all
software projects under development. The project “systems” is a project of the system
files for all the NEES managed computer systems.
The client CVS program communicates with the server program on rattle. It allows users
to login and inspect its repository, get files from the repository and then “check-in”
changes made to the files. To check out a project, you must indicate what repository you
want to use and then login to it:
# cvs –d:pserver:[email protected]:/opt/cvsroot –login
Note the –d option specifies the protocol (only pserver is currently operational), account
and system, and finally the directory to access. Note that the password for hankr on the
system rattle will be stored in ~/.cvslogin and accessed every time the repository is.
It is possible to get any project or subproject by checking it out of the repository:
# cvs checkout systems/nees
will checkout the nees subproject (which are the important system files for the server
nees.ucsb.edu).
When you want to make your changes permanent in the repository, commit them:
# cvs commit –m “Specify a message or you will get an editor to do so…”
will traverse all the directories from the current level and below committing the changed
files to the repository.
Other useful commands:
# cvs diff myfilename
Shows the differences between the local file “myfilename” and the repository file with
the same name.
CVS requires that all files be in the same project hierarchy. Therefore, the system
hierarchy containing all the directories that have files in them to be saved, has been
recreated in the
/root/cvs
directory. For example, the file /etc/modules.conf would be copied to
/root/cvs/etc/modules.conf so that it can be compared with repository and/or saved. The
project hierarchy contains subdirectories at each level named “CVS.” These directories
and the files they contain specify where the repository is and how to access it. Further,
these directories, and the files they contain cannot be scattered through the system, hence
the project hierarchy.
Appendix X – TODO
1.
2.
3.
4.
rsync or similar scripts to copy system files to /root/cvs
Determine if SNMP Traps can be/are sent to the configured email addresses.
Install Updated BIOS and drivers on DL140.
Install PBEAgent (fingers crossed) on DL140.