|
Softpanorama
(slightly skeptical)
Open Source Software Educational Society |
May the
source be with you,
but remember the KISS principle ;-)
|
SUSE 10 SP1 on Dell 1950/2950 Installation Checklist
Dr. Nikolai Bezroukov
(version 1.03, Created May 18, 2007; Last modified Dec 07, 2007)
Server:
______________________________
- Create Dell partition
- Boot the Suse 10 DVD
- Partition the Harddrives
- Select set of
packages to be installed from Suse DVD
- Additional
YAST Installation steps
-
Configuration
steps after the system reboot
- Install additional packages
- Verify and enable standard daemons
- Configure passwd, groups and user directories
- Register server with Novell and install patches
-
Create application specific users and home directories
-
Perform initial hardening to satisfy audit req (should be
automatic or semiautomatic)
- Installation of additional utilities and packages
- Create baseline
- Additional items that were
missed
Before You Begin
Before you install a SUSE Linux
Enterprise Server 10 verify the following:
-
You have Dell Installation and Server management disk
-
You have a registration number from Novell
-
DRAC card is configured and you can access it from your
PC.
-
You are using Suse 10 installation the DVD with SP1 not
the original GA release.
-
Server IP addresses corresponds to those in DNS.
-
Network masks and gateway information that you have are
correct.
- Install Dell Installation CD in DVD drive and reboot the server with Ctrl-Alt-Del.
- Note -- boot is slow and sometimes it looks like the server died. Be
patient...
- Configure the drives into RAID as prompts suggest (if you have just 4
drives and want two separate logical drives you can use Raid 1 or 10
depending on the capabilities of the controller and the level of your
love for RAID 10 ;-)
Note: If you changed RAID configuration using controller BIOS
you need go to the creation of a service partition as it looks like Dell startup disk write signatures on
the disks and reboot the system. You can delete it later if you do not
want it (it is actually very small).
- Usually enterprise class PE1950/2950 servers have a 4 drives
configuration if there is no NAS and 2 drive with NAS:
- Disks 1,2 The first pair of 36G or 73G drive (or rarely larger)
typically are used as OS partitions. 36G drives are OK but home
directories are a little bit tight. For 73G drives
size of partitions listed below can be doubled). Generally they should be
high speed (15K RPM).
- It make sense to make /usr/local
a symbolic link to /opt.
That permits to use smaller /usr.
- Disks 3,4 are application partition mounted at application
specific mount point. If NAS storage used for application those are
essentially redundant but can be used for swap.
- Create Dell utility partition. Run Dell utility for
creation of service partition until it will do 10% and then stop it by power
recycling (you need to keep power key on PowerEdge server until power will
switch off). If it runs to 20% it will ask for Suse DVD but will not accept
it so you can reboot the server at this time but it is unclear it it makes sense to wait.
- Replace Dell
installation CD with the Suse 10 SP 1 DVD and wait until the server boots
(do not leave the console).
- Immediately after the server boots select Installation from the console menu
(otherwise it will boot from the hard drive
on expiration of "pass-through" timer -- that means that you can leave
DVD in the drive even if you boot order has DVD-ROM before harddrive).
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
Notes:
- We assume 4 73G drives configured into two logical drives using
mirroring.
- Always use Ext 3 filesystem
for all partitions, do not use Reisner (Ext3 is not a default of Suse 10 SP1)
- Mark all partitions except swap with format options (unless this is a
re-install)
- With Suse 10 SP1 you can use LVM: it looks like there is no difference in
stability and it gives some additional flexibility..
- Recommended size of the swap is the size of the RAM.
See Linux swap
- For most servers with over 4G memory this can be 1/2 of memory size.
For example this is Oracle recommendation for application servers.
- On special purpose severs with 512 of RAM (if such exists those
days) it probably should be equal to double of memory size as Suse is a
pretty memory hungry OS. Beagle and other memory hogs should be
de-installed in this case. Smaller footprint X manager is recommended
instead of this fat pig called Gnome.
- It is desirable to install LVM as this makes installation more
flexible.
- it make some sense to use separate partitions for /var and /opt
(aka /use/local ) is you are not too squeezed for space...
Some examples of partitioning
Example 1:
mirrored pair of 36 drives (no LVM)
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 4128320 338524 3580032 9% /
/dev/sda2 298471 16210 266850 6% /boot
/dev/sda10 5207780 737020 4206212 15% /home
/dev/sda8 4128320 735412 3183144 19% /opt
/dev/sda9 4128320 240456 3678100 7% /tmp
/dev/sda6 4128320 1851872 2066684 48% /usr
/dev/sda7 8256696 342928 7494288 5% /var
Example 2:
mirrowed pair of 73G drives (with LVM)Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg01-root
4128448 304384 3614352 8% /
/dev/sda2 297485 16507 265618 6% /boot
/dev/mapper/vg01-home
1032088 77000 902660 8% /home
/dev/mapper/vg01-opt 2064208 633432 1325920 33% /opt
/dev/mapper/vg01-tmp 4128448 136468 3782268 4% /tmp
/dev/mapper/vg01-usr 4128448 1404892 2513844 36% /usr
/dev/mapper/vg01-var 10321208 917848 8879072 10% /var
/dev/mapper/vg02-backup
17546044 6162448 10492308 38% /backup
Partitioning of hard drives using LVM
We will assume two 135 disk mirrowed
via controller (sda 135GB).
First you need to switch to the advanced mode in YAST2 Partitioner. You will see that
one partition is already created.
- sda1 Dell Util
31MB 0-3
# created in prev step
If there are extra partitions on the boot drive you need to delete them.
- Create primary partition for /boot by entering +200M. Set the type of
partition to Ext3 and check "format"
sda2
/boot
200MB
4-29
(format ext3)
-
Create swap partition by using swap partition code from the menu For example for 32G of RAM enter +32G:
sda3
swap
32GB
30-4207
- Create extended partition for the rest of the drive
sda4
Extended 103GB (rest of disk)
-
Enroll this partition into LVM by clicking on LVM button
sda5 LVM
103GB (do not format, Linux LVM, rest of disk)
- Switch LVM view and create logical volume lv00
- Within LVM create additional partitions. Use name of partitions for
labels ( root for / partition). For example:
vg00
103GB
vg00 lv01
/ 4GB
vg00 lv02 /usr
4GB
vg00 lv03 /var
4GB
vg00 lv04
/opt 4GB
vg00 lv05 /tmp
4GB
vg00 lv06
/home 4GB
- Recheck that all partitions you created are Ext3 based.
- If you have the second pair of drives you can create logical volume lv01 for the second pair of drives
-
Note: In Suse 10 default filesystem for some reason is still Reisner so
please recheck that all slices are Ext3 based.
Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
Important:
- Click on details to see full content of each group of packages
- Deselect power saving features by deselecting the following packages:
for server they can lead to troubles:
- Do not touch mono -- it is used in many places and despite being a
Microsoft .NET clone it cannot be deleted.
- In “Base Technology”
- Select "Server Base Package" and inside of it deselect:
- dhcpcd -- A DHCP Client Daemon
- powersave
- powersave-libs
- ppp -- point-to-point Tunneling Protocol
- pppt -- point-to-point Tunneling Protocol (PPTP) Client
- wvdial
- ypbind
- wol -- wake_on_lan client
- Select "Common Code Package" and deselect:
- Leave "Novell AppArmor" selected
- Leave 32-bit environment selected
- In “Graphical Environment”
- select only Gnome and X Windows.
- Do not select KDE unless application
requires it.
- In Primary Functions
- Select "file server".
- open tab and explicitly deselect
SAMBA,
- Select pure-ftpd
- Note: if you have a lot of Red Hat servers you can
install vsftpd
instead
- Deselect Printserver
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ____ Select root password
- ____ Specify hostname and domain
- ___ In Network configuration (Important: Do not forget to disable IPv6)
- ___ Disable Firewall
- ___ Disable IPv6
- ___ Configure network interfaces (IP, netmask, domain search,
default gateway)
- ___ Enable VNC Remote access
- ___ Configure a Proxy server in order to
access the internet, you must first configure YaST with the correct Proxy
information.
- Enter the correct proxy URLs in both the
HTTP field only.
- Select "same for all services tab"
- No not fill user and password fields
- ___Configure the first non-root user (just yourself, at this time do not worry about replication of
other accounts).
- ____ Create yourself as a user
- ____ Important: Enroll
yourself into wheel group and modify /etc/sudoers to allow members of
whell group to su to root.
Open Yast2 and make the following configuration changes:
- ___ Modify default local
security policies
- min passwd length=8,
- 5 Sec delay
- 5 retries in case of wrong password
- Alt-Ctrl-Del ignore
- Allow
Remote Graphical,
- Set userID limits 100-999999, guid limits 100-999999,
- Change default users so that they were not members of video and
sound groups.
- ___ Configure NTP
- ____ Configure ntp using expert option by adding two
servers:
- “server ntp1.YourCompany-corp.com”
- "server ntp2.YourCompany-corp.com"
Notes:
- two
NTP servers always should be specified.
- Deleted undisciplined local clock entry
- ___ Verify if telnet is installed.
- change /etc/xnetd.d/telnet to disable=no
- ____ Verify if pure-ftpd is installled.
Note: if you have a lot
of Red Hat servers you can install vsftpd
FTP daemon instead for consistency...
- ____ Configure
/etc/pure-ftpd/pure-ftpd.conf file
- ____ Disallow anonymous access by copying the file from already
configured server.
- ____ Edit file /etc/xinetd.d/pure-ftpd.conf
and enable ftpd (disable=no)
- ___ Important: turn on ftpd daemon in xinetd
services (chkcfg.sh ) or via Yast2.
- ___ Modify /etc/hosts
- verify and remove 127.0.0.2 <hostname…> entry (it should be
absent in SP1 )
- ___ remove if necessary all references
in /etc/hosts for IPv6 addresses.
- add loghost entry for SYSLOG collection, for example:
- 10.201.13.253 nti253
loghost
- ___ Modify /etc/services
-
___ Verify that you can access internet using FireFox.
Set proxy.
- ___ Verify NIC speed
- ___ Set the second NIC to fixed speed to backup segment,
if used:
- Test with sftp the actual speed of transfer to another host in the same
datacenter
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Install additional utilities
- ___ Install ksh93 RPM package (to be
used as standard Korn shell for users that prefer ksh)
- uninstall package
pdksh - Public Domain Korn Shell
- install AT&K versiion of
Korn Shell.
- Prebuild packages are available from the
|
OpenSuSE. For example
ksh-93s-48.x86_64.rpm
- Hard link /usr/bin/ksh to /usr/bin/ksh93
- ___ Install mc RPM package
(from DVD)
- ___ Modify crontab as necessary
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Verify is xinetd is running and if necessary enable it.
service --status-all
Checking for service
xinetd: unused
chkconfig xinetd.on
- Enable telent and ftp if nessesary
- chkconfig telnetd on
- chkconfig pure-ftpd on
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
Note: The best way is to use Red Hat style of primary group
assignments: each user has GID identical to UID and all enrollment into groups
is done in /etc/group
- ___ Install standard accounts via script
- Note: Use bash as the default shell
for all human users
- ___ Group staff should contain software application owners who
use the servers
- ___ Group operators should contain operators
- ___ Enroll yourself into the group wheel.
- ___ Edit /etc/sudoers to make
group wheel root equivalent.
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Check if ZMD package is missing and install it, if necessary
- ___ Verify that proxy server is correctly configured by accessing
Novell.com via FireFox
- ___ Register the server using registration code for the server provided by Novell.
- You do not need to put your credentials as a part of proxy
configuration
- If registration fails open ticket with Novel and let them do the job.
- ___ Install all the patches:
- might require several iterations
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Create application specific users and directories
- ___ Enable NSF Create NFS mounts, if nessessary
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Delete redundant accounts:
- uucp
- ftp (unless you need anonymous ftp access)
- games
- news
- wwwrun
- ___ Delete redundant groups
- ___ Modify /etc/issue &
motd
- Configure syslog and change in /etc/syslog.conf to point to log server
- All linux servers should forward syslog to SYSLOG server
- Verify log rotation (/etc/logrotate.conf)
- Install writable file check script into cron
- Configure SSH for applications, if necessary (SSH is enabled out of the
box in Suse)
- Disable SSH1
- Verify correctness of home directories permissions
- Populate all home directories and /root
directory with .profile and
.kshrc files (for bash users this is
.bash_profile and
.bashrc) and verify they are properly own
and have permissions 700 or 701
- ___ Important Check and if necessary disable
test,
guest and any other unused accounts if any were created
during the installation.
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ____ Install Tivoli endpoint (check ssh connectivity from TMR server
before the installation)
- ___ Install SecurID client
- ___ Install Sarcheck
- ___ Install Data Protector client
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- ___ Creation of the baseline of key config files for the server and
possibly burning it to CD.
- Adopt one of the scripts used in troubleshooting and run it after the
installation just before giving the server to application people.
- Copy all the critical config file to /root/baseline/date directory the way JASS does this on
Solaris.
- ___ Verify the /boot/grub/menu.lst is configured correctly.
- ___ Check is all online updates are installed:
- use SPident -v and see
"Unknown" percentage
Summary (using 893 packages) Product/ServicePack conflict match update (shipped) SLES-10-x86_64-current 0 0% 751 84.1% 141 (2099 35.8%) Unknown 142 15.9%
CONCLUSION: System is up-to-date! found SLES-10-x86_64-current + "online updates"
- If unknown percentage is large try
SPident -vv SPident -vvvv (up to
SPident -wwww ) to see actual packages
claimed unknown (might be a bug in Suse 10 before SP 1).
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- Notes
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
- __________________________________________________________________________________
Copyright © 1996-2008 by Dr. Nikolai Bezroukov.
www.softpanorama.org was
created as a service to the UN Sustainable Development Networking Programme (SDNP)
in the author free time.
Submit
comments This document is an industrial compilation designed and created
exclusively for educational use and is placed under the copyright of the
Open Content License(OPL).
Original materials copyright belong to respective owners. Quotes are made
for educational purposes only in compliance with the fair use doctrine.
Standard disclaimer: The statements, views and opinions presented on
this web page are those of the author and are not endorsed by, nor do they necessarily
reflect, the opinions of the author present and former employers, SDNP or any other
organization the author may be associated with. We do not warrant the correctness
of the information provided or its fitness for any purpose.
Last modified:
August 19, 2008
|