TruCluster Server High Availability Case Study
Software Configuration: V1.6 Archive

The following information describes the software for the hardware configuration shown in the Hardware Configuration page:

• Installed software
• Network configuration
• Sample /etc/sysconfigtab file
• Cluster software configuration
• ASE services:
• kitche service configuration
• kase2 service configuration
• unix service configuration
• xirtlu service configuration

For detailed system configuration information, see the sample sys_check utility output.

Installed Software

The following table lists the software installed on the cluster:

Software	Description	Purpose
Operating System	DIGITAL UNIX Version 4.0F, patch kit: BL13	Basic operations
Cluster	TruCluster Production Server Version 1.6	High availability
Disk Storage	Logical Storage Manager	Disk management and data mirroring
	Advanced File System Utilities	File system management
	Networker for DIGITAL UNIX Version 5.5	Online network backups
	SCSI CAM Medium Changer Driver V3.1E	SCSI device driver for the tape loaders
	StorageWorks Command Console V2.0	Disk management and RAID 5
Networking	NFS	Network file system
	Advanced Server for UNIX (ASU) Version 4.1	Windows NT and Tru64 UNIX interoperability
	DECnet/OSI V4.0B	Networking
	Asynchronous Transfer Mode (ATM)	High-performance network
Internet	Netscape Navigator Gold V3.04	Web browser
	Netscape Enterprise Server	Web server
Internet AlphaServer Solutions (IASS)	Apache	Web server
	Squid Proxy/Caching server	Proxy/caching server
	Cyrus IMAP mail server	Mail administration
	Popper V2.4 Qualcomm POP3 mail server	Berkeley Post Office
	ProcMail 3.11pre7 Mail filtering software	Mail processing utility
	Sendmail V8.8.8 Mail Transport Agent	Sendmail program
Monitoring	Revision and Configuration Management Tool (RCM)	Configuration reporting
	Digital Product Performance (DPP)	Data collection and reporting process
	Monitoring Performance History (MPH)	Data collector for DPP
	DECevent Translation and Analysis	Event monitoring and analysis
	BMC Patrol	Event management and notification
	cre8_node_info.pl	Checks system availability, mail server access, ping responses, system load (uptime), mounts (ASE and local), disk availability, disk errors, disk space, file system space, mail, swap disks, swap space usage, processes running, network interfaces, LSM (voldisk), AdvFS, UFS, and printer links every 10 minutes. Another cron job running on an independent server monitors the output of this script and sends mail and pages administration if the script detects problems.
	ck_dirs	Checks file system accessibility every 5 minutes and pages and sends mail if it is unable to change to the directory.
	ckmt	Checks and restarts mountd, if necessary, and sends mail if it restarts.
	do_hot_spare.pl	Makes hot spares of / and /usr twice a day.
	ckasdu.kitche	Checks the status of ASU with netstat. Calls /var/adm/ues/bin/asdump -s if the kitche service is running on the system.
	asdump	Checks the status of ASU on kitche.
	restart_auto.build	Checks and restarts auto.build, if necessary.
	daily.kitche	Daily system information: NSR index info, asemgr database, disk info nightly scripts (NIGHTLY.sh, NIGHTLY_kitche.sh, NIGHTLY_kase2.sh, NIGHTLY_unix.sh), UES daily stuff, disk usage (list of disk hogs), and displaced mail (checkmail)
	idlenot	Program that logs out users after 4 hours of idle time.
	weekly.kitche	On a weekly basis, gathers system information, including backup schedules, disk space usage, and printer logs; checks for root programs in staff areas; and cleans up NSR syslogs. Mails the information to the admininistrator.
	monthly.kitche	On a monthly basis, rotates log files and gathers the NSR stats for the previous month.
	ck_lmf.pl	On a monthly basis, checks license expiration dates, and sends mail if a license is expiring this month.
	sys_check	On a monthly basis, gathers system configuration.
Miscellaneous	DEC C++	Programming
	Advanced Printing Software	Printing
	PrintServer Software for OSF/1 AXP	Network printing
	Printxchange client	Network printing
	C2-Security	Security
	Ladebug Debugger	Kernel and application debugging

Network Configuration

The following table lists the basic network configuration:

Network Configuration	Description
BIND caching server	Naming service
NIS slave server	Naming service
NFS server	Remote file system exports
ogated daemon	Gateway routing daemon
ASEROUTING=yes	Allows host-based routes from a service with multiple interfaces
16 nfsd daemons	Remote NFS-compatible server
1 pcnfsd daemon	(PC)NFS authentication and print request server
7 nfsiod daemons	Local NFS-compatible asynchronous I/O daemon

Sample /etc/sysconfigtab File

The /etc/sysconfigtab file contains any permanent changes to kernel subsystem attributes. See sys_attrs.5 for information about attributes.

The following is a portion of one of the kitche member's /etc/sysconfigtab file:

Cluster Software Configuration

The following table lists the TruCluster Production Server Version 1.6 software configuration. For detailed information about the cluster configuration, see the sample ASE configuration database.

Cluster Component	Description
Member systems	kitche1 and kitche2
Logging level	Informational
Shared storage configuration	Six three-disk striped (RAID 0) storage sets, mirrored with LSM
	Five JBOD disks mirrored with LSM
File system	AdvFS
Services	kitche, kase2, unix, and xirtlu

kitche Service Configuration

The following table lists the attributes for the kitche service. (For more information about the start and stop action scripts for the kitche service, see the sample scripts.)

Service Component	Description
Service type	NFS
Service purpose	ASU, NFS, mail, and printing
Relocate on boot of favored member	No
Placement policy	Balanced
Favored members	mc0kitche1 and mc0kitche2
Scripts	Print services, lpd, and the LPS clients for the service
	Primary mail service
	NFS (internal)
	ASU
Special considerations	Because of dependencies, mail, printing, NFS, and ASU must be running on the same system. The system that is running the kitche service is always the primary mail and print server. Unless a failover has occurred, the kitche and xirtlu (backup mail and print) services must run on different systems.

kase2 Service Configuration

The following table lists the attributes for the kase2 service.

Service Component	Description
Service type	Tape
Service purpose	Networker backups
Relocate on boot of favored member	Yes
Placement policy	Favored
Favored members	mc0kitche2 and mc0kitche1
Script	NSR
Special considerations	None

unix Service Configuration

The following table lists the attributes for the unix service.

Service Component	Description
Service type	Disk
Service purpose	Web services
Relocate on boot of favored member	Yes
Placement policy	Favored
Favored members	mc0kitche2 and mc0kitche1
Scripts	Squid/caching server
	Apache server
	Netscape
	LDAP
Special considerations	None

xirtlu Service Configuration

The following table lists the attributes for the xirtlu service.

Service Component	Description
Service type	Disk
Service purpose	Backup mail service and print service
Relocate on boot of favored member	No
Placement policy	Balanced
Favored members	mc0kitche2 and mc0kitche1
Scripts	The lpd for the backup print server The sendmail process for the backup mail server
Special considerations	The system that is running the xirtlu service is the backup mail and print server. The system that is running the kitche service is the primary mail or print server. Unless a failover has occurred, the xirtlu service runs on the system that is not running the kitche service.