Chapter 5 Work After Operating System Installation; Types Of Work; Setting Of Svs (Svagent/Svagentless Service/Svmco); Table 5.1 Type Of Operations - Fujitsu PRIMEQUEST 2000 Series Installation Manual

Hide thumbs Also See for PRIMEQUEST 2000 Series:
Table of Contents

Advertisement

CHAPTER 5 Work after Operating System installation

5.1 Types of work

CHAPTER 5
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.
Setting of SVAgent
Setting of sadump
Setting of Dump environment
Setting of Dump environment
Setting of NTP client
Management information of MMB / Save
configuration information of BIOS
Setting of Write Policy 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} =
Work after Operating System
installation
TABLE 5.1
Task
Linux, Windows
Linux
Windows
Linux
Linux
Linux, Windows
Linux, Windows
Type of operations
Installed operating
system
5.2 Setting of SVS
(SVagent/SVAgentless
Service/SVmco)
5.3 Setting of sadump
5.4 Setup of dump environment
(Windows)
5.5 Setup of dump environment (Linux)
5.6 Setup of NTP client
"5.7 Saving management and
configuration information
"Write Policy" recommended setting of
SAS array controller card"
86
See
CA92344-0536-04

Advertisement

Table of Contents
loading

Table of Contents