Vmware Workstation + Suse Linux one SP3 + DB2 Purescale V10.5 (Thu)

This article detailed record DB2 Purescale 10.5 on the VMware Workstation installation process, if you read my blog post, the practice of what the problem, welcome to add I 84077708, I will do my best for everyone.

Once VMware Tools is installed, you can freely exchange data between the physical machine and the virtual machine, starting with the configuration of the SUSE Linux 11SP3 operating system:

1, Configuration/etc/hosts

2. Configuring the DNS primary and standby server

3. Modify Kernel Parameters

4. Modify Resource Limits

5. Configuring the NTP server

First, configuration/etc/hosts (NODE01, NODE02 modified to the same)

127.0.0.1 localhost

# Special IPV6 Addresses

:: 1 localhost ipv6-localhost ipv6-loopback

fe00::0 ipv6-localnet

ff00::0 Ipv6-mcastprefix

Ff02::1 Ipv6-allnodes

Ff02::2 ipv6-allrouters

Ff02::3 ipv6-allhosts

192.168.142.101 node01.purescale.ibm.local node01

192.168.142.102 node02.purescale.ibm.local NODE02

Second, configure the primary DNS server (NODE01)

To configure the DNS server, you need to install bind-9.6esvr7p4-0.10.1.x86_64.rpm. After installing the BIND package, first use the root user to execute the following command to enable the named service to boot automatically.

node01:~ # chkconfig-a named

Named 0:off 1:off 2:off 3:on 4:off 5:on 6:off

When the named service is turned on, the named.conf file is generated in the/etc/directory, and the contents of the file are as follows:

Options {

Directory "/var/lib/named";

Dump-file "/var/log/named_dump.db";

Statistics-file "/var/log/named.stats";

Listen-on Port: (any;};

listen-on-v6 {any;};

allow-query {any;};

Notify No;

}

Zone "." In {

Type hint;

File "Root.hint";

};

Zone "localhost" in {

Type master;

File "Localhost.zone";

};

Zone "0.0.127.in-addr.arpa" in {

Type master;

File "127.0.0.zone";

};

Zone "Purescale.ibm.local" in {

Type master;

File "Purescale.ibm.local";

allow-transfer{192.168.142.102;};

};

Zone "142.168.192.in-addr.arpa" in {

Type master;

File "142.168.192.in-addr.arpa";

allow-transfer{192.168.142.102;};

};

# Include the meta include file generated by Createnamedconfinclude. This

# includes all files as configured in Named_conf_include_files from

#/etc/sysconfig/named

Include "/etc/named.conf.include";

In addition to the/etc/named.conf configuration file, there is a forward parsing configuration file and a reverse parsing configuration file. These two files are stored in the/var/lib/named directory. Filenames are purescale.ibm.local and 142.168.192.in-addr.arpa, respectively

The contents of the /var/lib/named/purescale.ibm.local forward parsing file are as follows:

$TTL 86400

@ in SOA Mydns root.mydns (

42; Serial (d. Adams)

3H; Refresh

15M; Retry

1W; Expiry

1D); Minimum

In NS NS

In NS ns2

NS in A 192.168.142.101

NS2 in A 192.168.142.102

Node01 in A 192.168.142.101

Node02 in A 192.168.142.102

The contents of the /var/lib/named/142.168.192.in-addr.arpa reverse parsing file are as follows:

$ORIGIN 142.168.192.in-addr.arpa.

$TTL 1H

@ in SOA ns.purescale.ibm.local. Root.purescale.ibm.local. (2

3H

1H

1W

1H)

@ in NS ns.purescale.ibm.local.

@ in NS ns2.purescale.ibm.local.

101 in PTR node01.purescale.ibm.local.

102 in PTR node02.purescale.ibm.local.

101 in PTR ns.purescale.ibm.local.

102 in PTR ns2.purescale.ibm.local.

After configuring these three files, you need to check the syntax for any problems:

Node01:/var/lib/named # named-checkconf

Node01:/var/lib/named # Named-checkzone Purescale.ibm.local purescale.ibm.local

Zone purescale.ibm.local/in:loaded Serial 42

Ok

node01:/var/lib/named #service named restart

Shutting down name server BIND do

Starting name server BIND Done

If the output is the above, the configuration is correct, otherwise the configuration is problematic.

Edit/etc/resolv.conf File

Add the following content:

Search Purescale.ibm.local

NameServer 192.168.142.101

NameServer 192.168.142.102

Verify that the primary DNS has no problem:

Node01:/var/lib/named # nslookup Node01

Server:192.168.142.101

address:192.168.142.101#53

Name:node01.purescale.ibm.local

Address:192.168.142.101

Node01:/var/lib/named # nslookup Node02

Server:192.168.142.101

address:192.168.142.101#53

Name:node02.purescale.ibm.local

address:192.168.142.102

Node01:/var/lib/named # nslookup 192.168.142.101

Server:192.168.142.101

address:192.168.142.101#53

101.142.168.192.in-addr.arpa name = node01.purescale.ibm.local.

101.142.168.192.in-addr.arpa name = ns.purescale.ibm.local.

Node01:/var/lib/named # nslookup 192.168.142.102

Server:192.168.142.101

address:192.168.142.101#53

102.142.168.192.in-addr.arpa name = ns2.purescale.ibm.local.

102.142.168.192.in-addr.arpa name = node02.purescale.ibm.local.

Here, the primary DNS is configured to complete.

Iii. Configuring Alternate DNS (NODE02)

Alternate DNS is basically the same as the primary DNS configuration, except that there are some differences in the/etc/named.conf file, that you want to configure alternate DNS, and you need to install the BIND-9.6ESVR7P4-0.10.1.X86_64.RPM software package. Then use the root user to execute the following command:

node02:~ # chkconfig-a named

Named 0:off 1:off 2:off 3: on 4:off 5: on 6:off

After executing the above command, a new named.conf configuration file is generated under the NODE02/etc/directory

Modify the contents of the file as follows:

Options {

Directory "/var/lib/named";

Dump-file "/var/log/named_dump.db";

Statistics-file "/var/log/named.stats";

Listen-on Port: (any;};

listen-on-v6 {any;};

allow-query {any;};

Notify No;

}

Zone "." In {

Type hint;

File "Root.hint";

};

Zone "localhost" in {

Type master;

File "Localhost.zone";

};

Zone "0.0.127.in-addr.arpa" in {

Type master;

File "127.0.0.zone";

};

Zone "Purescale.ibm.local" in {

Type slave;

File "Slave/purescale.ibm.local";

masters{192.168.142.101;};

};

Zone "142.168.192.in-addr.arpa" in {

Type slave;

File "Slave/142.168.192.in-addr.arpa";

masters{192.168.142.101;};

};

# Include the meta include file generated by Createnamedconfinclude. This

# includes all files as configured in Named_conf_include_files from

#/etc/sysconfig/named

Include "/etc/named.conf.include";

/etc/named.conf file configuration, the remaining forward parsing files and reverse parsing files, the alternate DNS server forward parsing files and reverse parsing files are stored in the/var/lib/named/slave/directory on the NODE02, The file content is identical to the file contents of the primary DNS server, only the purescale.ibm.local file and 142.168.192 in the/var/lib/named directory of the primary DNS server. The In-addr.arpa file is copied to the/var/lib/named/slave/directory of the NODE02 virtual machine using the SCP command.

node01:/var/lib/named #scp purescale.ibm.local [email protected]:/var/lib/named/slave/

node01:/var/lib/named #scp 142.168.192.in-addr.arpa [email protected]:/var/lib/named/slave/

Edit/etc/resolv.conf File

Add the following content:

Search Purescale.ibm.local

NameServer 192.168.142.101

NameServer 192.168.142.102

The configuration of the alternate DNS server has also been completed.

The authentication method that is configured correctly is the same as the authentication method for the primary DNS server, and is not duplicated here.

Four, modify the kernel parameters (NODE01, node02 to modify)

Kernel parameter file is/etc/sysctl.conf

Add the following at the end of the file: (Configured in memory 3.5GB as an example)

kernel.shmmni=1024

kernel.shmmax=3758096384

kernel.shmall=1048576

KERNEL.SEM=250 256000 32 1024

kernel.msgmni=1024

kernel.msgmax=65536

kernel.msgmnb=65536

FS.AIO-MAX-NR = 1048576

Fs.file-max = 6815744

V. Modify the resource restriction file (NODE01, NODE02)

Resource Limit file is/etc/security/limits.conf

Add the following at the end of the file:

* Soft Nofile 65536

* Hard Nofile 65536

* Soft Nproc 65536

* Hard Nproc 65536

* Soft Stack 65536

* Hard Stack 65536

* Hard Memlock 134217728

* Soft Memlock 134217728

Vi. Configuring the NTP server (NODE01)

The configuration file for the NTP server is/etc/ntp.conf, which reads as follows:

Tinker Panic 0

Restrict default Kod nomodify notrap

Restrict 127.0.0.1

#--CLIENT NETWORK-------

Restrict 192.168.142.0 mask 255.255.0.0 nomodify notrap

#---Our timeservers-----

Server 192.168.142.1

Server 127.127.1.0

# undisciplined Local Clock.

# Fudge 127.127.1.0 Stratum 9

Driftfile/var/lib/ntp/drift/ntp.drift # path for drift file

Broadcastdelay 0.008

LOGFILE/VAR/LOG/NTP # Alternate log file

Keys/etc/ntp.keys # path for keys file

Trustedkey 1 # define trusted keys

Requestkey 1 # key (7) for accessing server variables

Where the red part of the server 192.168.142.1 is the physical machine (gateway) IP address, as to how to configure the NTP server on the WIN7 operating system, ask the degree Niang.

Configure the NTP service to boot automatically.

node01:~ # chkconfig-a NTP

NTP 0:off 1:off 2:off 3: on 4:off 5: on 6:off

Vii. Configuring the NTP Client (NODE02)

The NTP client is a NODE02 virtual machine, and the configuration file is/etc/ntp.conf, as follows:

Tinker Panic 0

Restrict default Kod nomodify notrap

Restrict 127.0.0.1

#--CLIENT NETWORK-------

#---Our timeservers-----

Server 192.168.142.101 Iburst

Server 127.127.1.0

# undisciplined Local Clock.

# Fudge 127.127.1.0 Stratum 9

Driftfile/var/lib/ntp/drift/ntp.drift # path for drift file

Broadcastdelay 0.008

LOGFILE/VAR/LOG/NTP # Alternate log file

Keys/etc/ntp.keys # path for keys file

Trustedkey 1 # define trusted keys

Requestkey 1 # key (7) for accessing server variables

The DNS primary and standby server and the NTP server and the client are all configured.

In addition to the above configuration, there are SSH user-free login, iSCSI server and iSCSI client is not configured, for this part, see "Vmware Workstation + Suse Linux SP3 + DB2 Purescale V10.5 (v) 》 。

This article from "The Memories of Tao elder brother" blog, declined reprint!

Vmware Workstation + Suse Linux one SP3 + DB2 Purescale V10.5 (Thu)