CHAPTER 5 Work after Operating System installation
5.1 Types of work
86
CA92344-0536-04
Work after Operating System
CHAPTER 5
installation
This chapter describes every setting that is required after the installation of the operating system of the PRIMEQUEST
2000 Series
5.1
Types of work
Content and type of operations that are to be implemented after installation of the operating system are given below.
TABLE 5.1
Type of operations
Task
Installed operating
system
See
Setting of SVAgent
Linux, Windows
5.2 Setting of SVS
(SVagent/SVAgentless
Service/SVmco)
Setting of sadump
Linux
Setting of Dump environment
Windows
5.4 Setup of dump environment
(Windows)
Setting of Dump environment
Linux
5.5 Setup of dump environment (Linux)
Setting of NTP client
Linux
Management information of MMB / Save
configuration information of BIOS
Linux, Windows
Setting of Write Policy of SAS array
controller card.
Linux, Windows
“Write Policy” recommended setting of
SAS array controller card”
5.2
Setting of SVS (SVagent/SVAgentless Service/SVmco)
If SVS installation was selected settings for following products must be done after installation of OS. See the following
manuals for the details of the settings of SVagent/SVmco.
SVmco is necessary, only when you use PRIMECLUSTER linkage
-
SVagent:
ServerView Operations Manager Installation ServerView Agents for Linux
ServerView Operations Manager Installation ServerView Agents for Windows
-
SVmco:
ServerView Mission Critical Option User Manual.
-
SVAgentless Service on SUSE Linux Enterprise Server
In case of SUSE Linux Enterprise Server, it is necessary to extend the syslog-ng configuration file
1. Insert the following lines into the file /etc/syslog-ng/syslog-ng.conf:
destination hwlog { pipe("/dev/HWLog/syslog_fifo"); };
log { source(src); destination(hwlog); };
2. Start YaST and select Novell AppArmor – Edit Profile.
3. Choose the name of the active syslog daemon (/sbin/syslog-ng or /sbin/syslogd) and click Next.
4. Enter /dev/HWLog/syslog_fifo in the Enter or modify File-name field.
5. Under Permissions activate the Read and Write option.
6. Save this entry.
7. Restart AppArmor by:
/etc/init.d/boot.apparmor restart
Due to a bug in SLES it is possible, that the AppArmor profile /etc/apparmor.d/sbin.syslog-ng contains an invalid
statement. The following line
@{CHROOT_BASE} =