Solaris OS

Getting Started by creating Virtual Lab ( Part 2)

2012-02-20T11:25:00.001-08:00

In this tutorial you will learn how to install Solaris 10 and Solaris 11.
Note :- This tutorial is part of a 3-part tutorial series
Getting Started by creating Virtual Lab ( Part 1)
Getting Started by creating Virtual Lab ( Part 2)
Getting Started by creating Virtual Lab ( Part 3)
In the previous tutorial we started creating virtual machine, in this tutorial we are going to complete what we started.
- after you selected where to store VDI ( Virtual Disk Image) you will see the icon of “Solaris Virtual Machine” on the main “Virtual Box “ interface as the following image

Click on “Settings”

- Select System

- select Hard and change the boot sequence .

- Click “OK”, on the main “Virtual Box “ interface as the following image,Select Solaris and click START

- Click select, the software will ask you about the Solaris OS .iso file which you already downloaded it from Oracle website, select the solaris .iso file and click next, then click start.

- Now the Virtual OS will restart and boot from Solaris 10 or Solaris 11 .ISO file and you will see the boot screen, At this point you have created Virtual Machine and you are going to install Solaris OS, if you want to install Solaris 10 Scroll Down to the “How to install Solaris 10" section, else go to the “ How to Install Solaris 11” section in the next tutorial.
How to Install Solaris 10
1- the first screen you will see after booting from Solaris 10 .ISO file is

Select the first option “ Solaris" and press “Enter”.
2- The next screen will ask you about the Installation type you want

Select choice number 4 “Solaris Interactive Text Console session” and press “Enter”.
3- Now configure the Keyboard Layout

Select “US ENGLISH” and press “F2”
4- Select Language

Type the language Number you want and press “Enter”
5- the next screen tells you about how installation Program works

Press “F2”.
6- The next screens ask you about “network information”, “Time Zone” and “Time/Date”

Press “F2”
7- Determine if the system will be Networked or not

Select “Yes” and Press “F2”.
8- Specify whether or not this Network Interface should use DHCP
Select “No” and Press “F2”
9- Enter the Host Name you want.

Type the host name you want and press “F2”.
10-Enter the IP address, if you don’t know what is the correct IP address just type it as the one in the next screen and we will change it later.
Press “F2”
11- Specify if the system is part of a subnet mask

select Yes and press “F2”
12- Specify the subnet mask

type 255.255.255.0 and Press “F2”
13- Specify whether or not you want to enable IPv6

Select “NO” and Press “F2”.
14- Specify the default Route

Select "None”, we will change it later and press “F2”.
15- Confirm Information

Press “F2”.
16- Configure Kerberos Security
Select “No” and press “F2”.
17- Confirm Kerberos Security Information

Press “F2”
18- Provide Name service Information

Select “None” and Press “F2”.
19- Confirm Name service information

Press “F2”
20- Specify NFSv4 Domain Configuration

Select “Use the NFSV4 domain derived by the system” and press “F2”.
21- Confirm Information for NFSV4 Domain.

Press “F2”.
22- Specify Time Zone

select your Time zone and press “F2”.
23- Select your country

select your country and press “F2”.
24- The root password for the System.

type the password twice and press “F2”.
25- Enabling Remote Services

Select “yes” then press “F2”.
26- Provide Solaris Auto Registration Info

Deselect “ I would like to register … etc.” then press “F2” for this and next screen.
27- On the following screens you will be asked for Software Installation, File system type and Disk layout.

Press “F2”.
28- Eject CD/DVD automatically.

Select “Automatically eject CD/DVD” then press “F2”.
29- Reboot After Installation

Select “Auto Reboot” and press “F2” for this and for the next screen.
30- Accept License by pressing “F2”.
31- Select Geographic regions

Select your Geographic regions and press “F2” for this screen and the next.
32- Additional Products :-

Select “None” then press “F2”.
33- Chose File system Type

I recommend you to select “ZFS”, then press “F2”.
34- Select Software

Select “Entire Distribution” then press “F2”
35- Select Disks

Press “F2”.
36- Configure ZFS Settings

Press “F2” for this and next screen.
37- the Solaris Initial Install Start

Getting Started by creating Virtual Lab

2012-02-19T11:11:00.001-08:00

This tutorial contains information in order to help you create a virtual Lab on your pc so you can use and practice “inside-Solaris”  tutorials.

Getting Started by creating Virtual Lab ( Part 1)
Getting Started by creating Virtual Lab ( Part 2)
Getting Started by creating Virtual Lab ( Part 3)

- Download Oracle Virtual Box software

Download

“ VirtualBox is a free virtualization product for enterprise as well as home use”

- Download Putty

Download

“ Putty is a free Telnet and SSH client”

- Download Solaris 10 \ Download Solaris 11 Text Install
Download \ Download

“ Solaris Operating System”

Note :- Solaris 11 Text Install doesn't have GUI desktop, use “pkg install slim_install “ command to install GUI Desktop.

1- Install VirtualBox (virtualization product ) on your pc, it's easy and straight

2- from your Desktop run Oracle VM VirtualBox you will see the following screen

3- Click on New Button, you will see the following

4- Click Next, and type the name of the Virtual machine you want , and select the operating System which is Solaris .
5- Click Next
6- Select the amount of memory

7- Click Next
8- Select Create New hard disk as the follow picture

9- Click Next, and select VDI ( Virtual Disk Image )

10- Click Next, Select Dynamically allocated

11- Click Next, Select the location you want to store the VDI also select the amount of disk space for new Virtual machine.

12- Click Next, then Click Create.

Next Getting Started by creating Virtual Lab ( Part 2)

AutoFS theoretical concepts

2011-12-05T22:59:00.001-08:00

AutoFs

Introduction

The AutoFS facility provide a method to mount remote directory automatically whithout needing to use mount or umount command, when a user or application access an NFS (shared) file system, the mount is established, when the file system is no longer needed or has not been accessed for certain time period, the file system is automatically unmounted.

Note :- This tutorial explains the theoretical concepts of some AutoFS features, if you want to skip it and go to practical tutorial go to AutoFS Practical.

---------------------------------------------------------------------------------------------------------------

Tutorial Prerequisites

NFS file system
Lab Preparation
----------------------------------------------------------------------------------------------------------------

Tutorial contents

AutoFS theoretical concepts
AutoFS Practical
---------------------------------------------------------------------------------------------------------------

Let's assume that we have two nodes (Server1 and client1), on server1 there is a directory we want to share it (/tmp_share), and we want to access the directory from client1, in this case we have two option :-

Option 1 : use traditional NFS by sharing the directory (/tmp_share) on server1 then create mount point on client1 and use mount command.

Option 2 : use AutoFS by sharing the directory (/tmp_share) on server1 then configure AutoFs on client 1 to access the (/tmp_share) without using mount command.

Advantages of AutoFS :

➊ Because shares are only mounted when they are accessed, system boot time is faster.
➋ The system doesn't have to wait for each NFS server to respond and the mount to succeed.

➌ it is more secure. Users on the client systems must know what directory is configured to mount the share before changing into that directory to force the mount.

➍ users can browse the contents of the shared directory if they have permission.

AutoFs features :

➊ AutoFs is client side service, when we want to use AtuoFs we configure some files on client side.
➋ AutoFs Mount and unmount file systems on demand and automatically.

AutoFs Configuration :

AutoFs is initialized by automount (automountd daemon) which is run at boot time. there are three configuration files for AutoFs called AutoFS maps

➊ Master map
➋ Direct Map
➌ Indirect Map

these files contain information about the local mount point and remote shared directory, Now if a request is made to access remote shared directory the system goes through the following steps :

➊ AutoFS intercepts the request.
➋ AutoFS sends a message to the automountd daemon for the requested file system to be mounted.
➌ automountd locates the file system information in a map and performs the mount.
➍ AutoFS allows the intercepted request to proceed.
➎ AutoFS unmounts the file system after a period of inactivity.

AutoFS Maps

Master Maps

at start up the automount command reads the master map (/etc/auto_master), this map tells about other maps and mount points.

ِِِAt the command prompt type :-

 bash-3.00# more /etc/auto_master

#  
 # Copyright 2003 Sun Microsystems, Inc. All rights reserved.  
 # Use is subject to license terms.  
 #  
 # ident "@(#)auto_master    1.8   03/04/28 SMI"  
 #  
 # Master map for automounter  
 #  
 +auto_master  
 /net      -hosts     -nosuid,nobrowse  
 /home      auto_home    -nobrowse  
 /-       auto_direct   -ro

The /etc/master_map has the following syntax :
<mount-point> <map-name> <mount-options>

<mount-point> The full pathname of a directory that is used as the mount point.
<map-name> The map that used to find directions to locations or mount information.

The first line in /etc/master_map :

 +auto_master

this file directs the automountd daemon to look at the NIS, NIS+, or LDAP databases before it reads the rest of the map. If this line is commented out, only the local files are searched unless the /etc/nsswitch.conf file specifies that NIS, NIS+, or LDAP should be searched.

The second line in /etc/master_map :

 /net      -hosts     -nosuid,nobrowse

let us explain this line by example, assume you have an NFS server called server1 that has /share_directory directory shared, from you machine if you type

 bash-3.00# cd /net/server1 or bash-3.00# cd /net/10.109.9.15

where 10.109.9.15 is the ip address of server1.
then type :

 bash-3.00# ls

the output will be :-

 share_directory

that means you can access any shared directory in remote machine through the following command :-

 bash-3.00# cd /net/remote_machine_(name or IP)

Note :- if you want to use the remote machine name instead of IP address add the remote host name and its IP address in the /etc/hosts file.

When you specified /net with a hostname (server1), automountd looked at the map file—in this case, /etc/hosts—and found server1 and its IP address. It then went to server1, found the /share_directory file system, and created a local mount point for /net/server1/share_directory .

the third line in /etc/auto_master

 /home      auto_home    -nobrowse

This map provides the mechanism to allow users to access their centrally located $HOME directories, i will explain it later in Lab Preparation .

4th line in /etc/auto_master

 /-       auto_direct   -ro

represent direct map.

Direct Map

Lists the mount points as absolute (Full) path names. This map explicitly indicates the mount point on the client, let us say that you have an NFS servers server1,server2,server3 and in each server there is a shared directory directory1, directory2,directory3 and we want to make these shared directories available from client1.

at client1 command prompt type :-

 bash-3.00# vi /etc/auto_direct

add the following line to the file :-

/home/directory1   -ro,soft server1:/directory1  
 /home/directory2  -ro,soft server2:/directory2  
 /home/directory3  -ro,soft server3:/directory3

where :

➟ /home/dierctory1,/home/directory2,/home/directory3 are directories created on client1 to act as mount points.

➟ -ro,soft :- ro refers to read only, soft This option returns an error if the server does not respond

➟ server1:/directory1,server2:/directory2,server3:/directory3 are remote hosts and remote shared directories

to access server1:/directory1 type cd /home/directory1
to access server2:/directory2 type cd /home/directory2
to access server3:/directory3 type cd /home/directory3

Indirect Maps
Lists the mount points as relative path names. This map uses a relative path to establish the mount point on the client, Indirect map specifies the main mount point and the name of the map in /etc/auto_master,

Example:- create an entry in the /etc/auto_master file by adding the following line (/share /etc/auto_share).

 bash-3.00# vi /etc/auto_master

"/etc/auto_master" 12 lines, 268 characters   
 #  
 # Copyright 2003 Sun Microsystems, Inc. All rights reserved.  
 # Use is subject to license terms.  
 #  
 # ident "@(#)auto_master    1.8   03/04/28 SMI"  
 #  
 # Master map for automounter  
 #  
 +auto_master  
 /net      -hosts     -nosuid,nobrowse  
 /home      auto_home    -nobrowse  
 /-       auto_direct   -ro  
 /share     /etc/auto_share

where :-
➟ /share is the name of the local mount point.
➟ /etc/auto_share is the name of the indirect map.

create the in direct map ( /etc/auto_share ) and add the following line

"directory server1:/share/directory"

 vi /etc/auto_share

 directory  server1:/share/directory

create the directory called "directory" in /share.

to access the remote directory

 bash-3.00# cd /share/directory

Note :- When making changes to the master map or creating a direct map, run the automount command to make the changes effective.

Resources :-
➊ ExamPrep Solaris 10 by Bill Calkins
➋ Advanced System Administration for the Solaris™ 10 by SUN Microsystems
➌ Oracle Documentation

Solaris Logs (Events)

2011-12-04T05:17:00.001-08:00

Solaris System Logs

system logs are files contain events that are recorded by the operating system, system logs contain information about errors, warnning, device changes, events, hardware errors and more.

solaris system logs are managed by syslog facility, at the command prompt type :-

 bash-3.00# ps -ef | grep -i syslog

 root 527 1 0 08:47:48 ? 0:26 /usr/sbin/syslogd

you can notice that syslog facility is running with PID of 527.

How syslog works ?

in solaris system a message is generated by kernal, daemon, application, user ... etc, syslog send this message to the syslogd daemon, syslogd daemon runs the m4 macro processor, the m4 macro processor reads the /etc/syslog.conf and process any m4 statments in the input, and passes the output to the syslogd daemon, the syslogd daemon uses the information output by the m4 processor to route messages (logs) to the appropriate places.

the main configuration file is /etc/syslog.conf.

Where syslog store log ?

➊ remote host

➋ local file

➌ console

➍ specific users :- display a message (Event) to the user.

Syslog configuration

A configuration entry in the /etc/syslog.conf file consists of two separated fields : selector and action.

selector field has two components : facility and level writen as facility.level, where facility represents the process that can generate the message, level represents the priority and the category of the message, for example "kern.err" where kern represent the facility ant it indicates that Messages generated by the kernel, "err" represents the priority of the message.

the follwoing are facilities options in solaris :-

Field	Description
kern	Messages generated by the kernel.
user	Messages generated by user processes.
mail	The mail system
daemon	System daemons, such as the in.ftpd and the telnetd daemons.
auth	The authorization system, including the login, su,and ttymon commands.
syslog	Messages generated internally by the syslogd daemon.
lpr	The line printer spooling system
cron	The cron and at facilities, including crontab, at, and cron.
*	All facilities, except the mark facility.

the follwoing are levels options in solaris :-

Level	Priority	Description
emerg	0	Panic conditions that are normally broadcast to all users
alert	1	Conditions that should be corrected immediately,such as a corrupted system database
crit	2	Warnings about critical conditions, such as hard device errors
err	3	Errors other than hard device errors
warning	4	Warning messages
notice	5	Non-error conditions that might require special handling
info	6	Informational messages
debug	7	Messages that are normally used only when debugging a program
none	8	Messages are not sent from the indicated facility to the selected file

again, the general form for syslog confiuration is :- selector action

where selector form is :- facility.level

action field defiens where forward the message,this field can have one of the following fields :-

/pathname ➡ Full path name to the targeted file.

@host ➡ The @ sign denotes that messages must be forwarded to a remote host. Messages are forwarded to the syslogd daemon on the remote host.

user_name ➡ The user user_name receives messages if they are logged in.

* ➡ All logged in users receive messages.

Example :-

we want to forward all messages of daemon facility and notice level to server3 remote host.

 bash-3.00# vi /etc/syslog.conf

 ident "@(#)syslog.conf    1.5   98/12/14 SMI"  /* SunOS 5.0 */  
 #  
 # Copyright (c) 1991-1998 by Sun Microsystems, Inc.  
 # All rights reserved.  
 #  
 # syslog configuration file.  
 #  
 # This file is processed by m4 so be careful to quote (`') names  
 # that match m4 reserved words. Also, within ifdef's, arguments  
 # containing commas must be quoted.  
 #  
 *.err;kern.notice;auth.notice          /dev/sysmsg  
 *.err;kern.debug;daemon.notice;mail.crit    /var/adm/messages  
 *.alert;kern.err;daemon.err           operator  
 *.alert                     root  
 *.emerg                     *  
 daemon.notice               @server3  
 # if a non-loghost machine chooses to have authentication messages  
 # sent to the loghost machine, un-comment out the following line:

add the line with red color.
↪ Add server3 ip address to the /etc/hosts file.

 bash-3.00# vi /etc/hosts

# Internet host table  
 #  
 ::1   localhost  
 127.0.0.1    localhost  
 10.109.9.251  solaris1    loghost  
 10.109.9.15 server3

now any messages of daemon facility and notice level will be founded at server3 in /var/adm/messages.

Solaris Zone part four ( Zone Configuration )

2011-11-21T05:23:00.001-08:00

Solaris Zone part four ( Zone Configuration )

In this tutorial we will learn how to configure some Solaris zone configuration

Solaris Zone Part 1 ( Concepts and theory )
Solaris Zone Part 2 ( Sparse Solaris zone )
Solaris Zone Part 3 ( whole Solaris zone )
Solaris Zone part 4 ( Zone Configuration )

➊ change solaris zone IP address

↬ From global zone at the command prompt type :-

 zonecfg:zone1> select net address=10.109.9.211

 zonecfg:zone1:net> set address=10.109.9.212

 zonecfg:zone1:net> end

 zonecfg:zone1:net> endzonecfg:zone1> verify

 zonecfg:zone1> commit

 zonecfg:zone1> exit

↬ reboot the zone

 zoneadm -z zone1 reboot

↬ where :-

- zone1 is the name of the zone

- 10.109.9.211 is the old IP address

- 10.109.9.212 is the new IP address

➋ change the Zone Host name

↬ from the zone at the command prompt type :-

 vi /etc/hosts

↬ change the old name with new.

 vi /etc/nodename

↬ change the old name with new .

↬ reboot the zone

 zoneadm -z zone1 reboot

➌ Delete zone

↬ from global zone at the command prompt :-

 zoneadm -z zone1 halt

 zoneadm -z zone1 uninstall

 zonecfg -z zone1 delete

➍ swap space in non-global zone

↬ A non-global zone inherits its swap space setting from the global zone. For example, in my global zone:

Solaris Zone Part 3 ( whole Solaris zone )

2011-11-20T02:41:00.001-08:00

Creating whole solaris zone

Big zone no files are shared between this type of zone and global zone, need more space because more files and packages will be installed.

Solaris Zone Part 1 ( Concepts and theory )
Solaris Zone Part 2 ( Sparse Solaris zone )
Solaris Zone Part 3 ( whole Solaris zone )
Solaris Zone part 4 ( Zone Configuration )

➊ Select the disk that will be used for Solaris zone, also select the mount point and add them to /etc/vfstab file.

 bash-3.00# vi /etc/vfstab

add the following to the file

 /dev/dsk/c1d0s0 /dev/rdsk/c1d0s0    /workzone/apache    ufs   1     yes   -

where the :
/dev/dsk/c1d0s0 is the name of the disk.
/workzone/apache is the mount point

➋ at the command prompt type

 bash-3.00# zonecfg -z zone2

↪ where zonecfg is the command used to set up zone configuration, zone2 is the name of the zone.

➌ type create command to create the zone

 zonecfg:zone1>create -b

➍ set zonepath parameter

 zonecfg:zone1>set zonepath=/workzone/zone2

↪ zonepath is the Path that the zone will be installed, the directory you select must have 700 permission. type chmod 700 /yourdirectory to change directory path.

➎ set autoboot parameter

 zonecfg:zone1> set autoboot=true

↪ to boot the zone automatically

➏ add network configuration

 zonecfg:zone1> add net

↪ add network configuration

➐ set the physical network card

 zonecfg:zone1:net> set physical=e1000g1

↪ the network card name is used for the physical interface.

➑ set IP address

 zonecfg:zone1:net> set address=10.109.9.234

↪ the ip address of zone

 zonecfg:zone1:net> end

➒ verify your configuration

 zonecfg:zone1> verify

↪ Determine whether the resources and properties specified are valid

➓ save your configuration

 zonecfg:zone1> commit

↪ save your configuration

 zonecfg:zone1> exit

➊➊ check zone status

 zoneadm list -cv

ID NAME       STATUS   PATH              BRAND  IP    
   0 global      running  /               native  shared  
   - zone2     installed /workzone/zone2        native  shared

↪ to see the zone status, you can see zone1 status is configured.
zone status can be :
1- Configured
2- Incomplete
3- Installed
4- Ready
5- Running

➊➋ to install the zone at the command prompt type

 bash-3.00# zoneadm -z zone2 install

↪ this will take some time, now check zone status

➊➌ check zone status

 bash-3.00# zoneadm list -cv

 ID NAME STATUS PATH BRAND IP

 0 global running / native shared

 - zone2 installed /workzone/zone1 native shared

↪ you can see that zone status is changed from confiugrd to installed

➊➍ now boot solaris zone, at the command prompt type:-

 bash-3.00# zoneadm -z zone2 boot

➊➎ check your zone status :-

bash-3.00# zoneadm list -cv

 ID NAME       STATUS   PATH              BRAND  IP    
   0 global      running  /               native  shared  
   3 zone2      running  /workzone/zone1        native  shared

↪ it is now running. the zone status has changed form configured => installd => running

↪ use the command zlogin -C zone1 to complete the zone configuration:-

bash-3.00# zlogin -C zone1

What type of terminal are you using?

1) ANSI Standard CRT

2) DEC VT52

3) DEC VT100

4) Heathkit 19

5) Lear Siegler ADM31

6) PC Console

7) Sun Command Tool

8) Sun Workstation

9) Televideo 910

10) Televideo 925

11) Wyse Model 50

12) X Terminal Emulator (xterms)

13) CDE Terminal Emulator (dtterm)

14) Other Type the number of your choice and press Return:

Select 13

1- the first screen will ask you about hostname:- type the host name. then press (esc+2)
2- select No for Kerberos Security then press (esc+2).
3- select your Name service type then press (esc+2)
4- select your country and password ... etc .

the zone is rebooting now, after rebooting login to your zone normally.

Solaris Zone Part 2 ( Sparse Solaris zone )

2011-11-20T01:04:00.001-08:00

This tutorial describe how to create sparse Solaris zone.

Solaris Zone Part 1 ( Concepts and theory )
Solaris Zone Part 2 ( Sparse Solaris zone )
Solaris Zone Part 3 ( whole Solaris zone )
Solaris Zone part 4 ( Zone Configuration )

➊ at the command prompt type

 bash-3.00# zonecfg -z zone1

↪ where zonecfg is the command used to set up zone configuration, zone1 is the name of the zone.

➋ type create command to create the zone

 zonecfg:zone1>create

➌ set zonepath parameter

 zonecfg:zone1>set zonepath=/workzone/zone1

↪ zonepath is the Path that the zone will be installed, the directory you select must have 700 permission. type chmod 700 /yourdirectory to change directory path.

➍ set autoboot parameter

 zonecfg:zone1> set autoboot=true

↪ to boot the zone automatically

➎ add file system using fs parameter

 zonecfg:zone1> add fs

↪ to determine how and where to mount file systems.

➏ set dir parameter

 zonecfg:zone1:fs> set dir=/zone1

↪ Specifies the mount point for the file system

➐ set block device

 zonecfg:zone1:fs> set special=/dev/dsk/c1d1s0

↪ Specifies the block special device name or directory from the global zone to mount

➑ set raw device

 zonecfg:zone1:fs> set raw=/dev/rdsk/c1d1s0

↪ Specifies the raw device on which to run fsck before mounting the file system

➒ set file system type

 zonecfg:zone1:fs> set type=ufs

↪ Specifies the file system type

 zonecfg:zone1:fs> end

➓ add network configuration

 zonecfg:zone1> add net

↪ add network configuration

➊➊ set the physical network card

 zonecfg:zone1:net> set physical=e1000g1

↪ the network card name is used for the physical interface.

➊➋ set IP address

 zonecfg:zone1:net> set address=10.109.9.233

↪ the ip address of zone

 zonecfg:zone1:net> end

➊➌ verify your configuration

 zonecfg:zone1> verify

↪ Determine whether the resources and properties specified are valid

➊➍ save your configuration

 zonecfg:zone1> commit

↪ save your configuration

 zonecfg:zone1> exit

➊➎ check zone status

 zoneadm list -cv

ID NAME       STATUS   PATH              BRAND  IP    
   0 global      running  /               native  shared  
   - zone1      installed /workzone/zone1        native  shared

↪ to see the zone status, you can see zone1 status is configured.
zone status can be :
1- Configured
2- Incomplete
3- Installed
4- Ready
5- Running

➊➏ to install the zone at the command prompt type

 bash-3.00# zoneadm -z zone1 install

↪ this will take some time, now check zone status

➊➐ check zone status

 bash-3.00# zoneadm list -cv

 ID NAME STATUS PATH BRAND IP

 0 global running / native shared

 - zone1 installed /workzone/zone1 native shared

↪ you can see that zone status is changed from confiugrd to installed

➊➑ now boot solaris zone, at the command prompt type:-

 bash-3.00# zoneadm -z zone1 boot

➊➒ check your zone status :-

bash-3.00# zoneadm list -cv

 ID NAME       STATUS   PATH              BRAND  IP    
   0 global      running  /               native  shared  
   3 zone1      running  /workzone/zone1        native  shared

↪ it is now running. the zone status has changed form configured => installd => running

↪ use the command zlogin -C zone1 to complete the zone configuration:-

bash-3.00# zlogin -C zone1

What type of terminal are you using?

1) ANSI Standard CRT

2) DEC VT52

3) DEC VT100

4) Heathkit 19

5) Lear Siegler ADM31

6) PC Console

7) Sun Command Tool

8) Sun Workstation

9) Televideo 910

10) Televideo 925

11) Wyse Model 50

12) X Terminal Emulator (xterms)

13) CDE Terminal Emulator (dtterm)

14) Other Type the number of your choice and press Return:

Solaris Zone Part 1

2011-11-19T11:26:00.001-08:00

Solaris Zone ( Concepts and theory )

In this tutorial will learn some key concepts about Solaris zones.

Solaris Zone Part 1 ( Concepts and theory )
Solaris Zone Part 2 ( Sparse Solaris zone )
Solaris Zone Part 3 ( whole Solaris zone )
Solaris Zone part 4 ( Zone Configuration )

what is solaris zones :-

zones is a technology that enable system administrator to create multiple independent operating systems with independent process space, allocated resources, and users. that means inside one physical server you can create four zones as follow ( zone 1 = apache, zone 2 = dns, zone 3 = MySQL, zone 4 = whatever application ), each one of these zones has its own process, file system ... etc. Processes running within a zone, cannot affect activity in other zones. think of zones as opreating system inside Operating system.

Solaris Zones features :-

➊ Solaris zones can host only instance of solaris. Not other OSs.
➋ Program Isolation - zone1 (Apache), zone2(MySQL)
➌ Security : Processes running within a zone, even one with superuser credentials, cannot affect activity in other zones.
➍ Virtualization, Granularity, Transparency.
➎ each zone has its own ID. ID 0, ID1, ID2 ...etc.
➏ No additional hardware is required for a zone

Solaris Zone Types :-

➊ Global zone
➋ Non-global zone

Features of GLOBAL zone
➊ Every Solaris system contains a global zone.
➋ Solaris ALWAYS boots to the global zone
➌ Knows about ALL hardware devices attached to the system.
➍ Knows about ALL non-global zones
➎ The global zone is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled
➏ Only the global zone is bootable from the system hardware.
➐ The global zone is always mapped to zone ID 0.
➑ thers is only ine global zone in the system.
➒ Global zone is created automatically when you install solaris OS for the first time, that means the Global zone is the current solaris OS you are working on now.

Features of Non-GLOBAL zone
➊ The non-global zones contain an installed subset of the complete Solaris Operating System software packages.
➋ The non-global zone is not aware of the existence of any other zones.
➌ The non-global cannot install, manage, or uninstall itself or any other zones.

whene you create a new zone ( Non-global zone), it shares some file with the global zone.

zones can be installed as :-

➊ Sparse Root zone
➋ Whole Root zone

Sparse Root zone :-
Small zone, it consumes the least disk space, because Only a subset of the packages installed in the global zone are installed directly into the non-global zone, and it shares most of the files whith the global zone, but in this type of zones the /usr and /lib are not writable.
Features :-

- smaller disk
- better security since /usr and /lib are not writable
- faster to create and patch
- easier to migrate

Whole Root zone
Big zone no files are shared between this type of zone and global zone, need more space because more files and packages will be installed.

steps to create zones
➊ determine zone types :- Sparse Root zone OR Whole Root zone
➋ determine the name of the zone
➌ determine the zonepath, zonepath is the Path that the zone will be installed.
➍ dtermine the zone file system :- dir,special,raw,type ( i will explain them later in solaris zone lab )
➎ determine zone network card and IP address.
➏ other option .

Solaris Packet sniffer

2011-10-27T02:56:00.000-07:00

Solaris Packet sniffer

Accroding to Network Dictionary sniffing tool is a program that monitors data traveling over a network, and it can be used both for stealing network information or for monitoring and maintenance network.

snoop tool

snoop is a command line packet sniffer in oracle solaris operating system. You can use the snoop utility to capture and inspect network packets to determine what kind of data is transferred between systems.

snoop command :-

 snoop

Result :- captures and displays all packets sent and received .

 snoop host_name

Result :- captures and display packets sent and received to/from host_name

 snoop -v

Result :- display detailed information (Ether Header, IP Header, UDP Header, SUN RPC Header, SUN NFS)

 snoop hostA hostB

Result :- captures and display packets sent and recived between hostA and hostB

 snoop -o file_name

Result :- Redirects the snoop utility output to filename in summary mode

 snoop -i file_name

Result :- Read saved snoop output from file_name

 snoop -o file_name tcp port 80

Result :- Redirects the snoop output to file_name and listen to tcp packets on port 80

 snoop -o file_name host hostA hostB and tcp and port 21

Result :- Redirects the snoop output between hostA and hostB to file_name and listen to tcp traffic on port 21 (FTP)

Example :-
Let's assume that we have serverA and we want to know the password of FTP from hostA to that server.

➊ at the command prompt on serverA type :-

 snoop -o snoop_ftp host hostA serverA and tcp and port 21

➋ establish an FTP connection from hostA to serverA

➌ at the command prompt on serverA type

 snoop -V -i snoop_ftp | grep -i user

you will see the FTP name account

 snoop -V -i snoop_ftp | grep -i pass

you will see the FTP account password.

Solaris ZFS

2011-10-23T09:29:00.000-07:00

what is ZFS ?

ZFS is a UNIX file system like NTFS and FAT in windows, It's used widely in Solaris and its transactional file system which ensures that any sequence of operations is either entirely committed or entirely ignored. This mechanism ensures that the ZFS file system can never be corrupted through loss of power or a system crash.

ZFS Features

➊ Support up to 256 quadrillion zettabytes, (zettabytes = 1024 Exabytes = 1024 petabytes = 1024 Terabyte = 1024 Gigabyte = 1024 Megabyte ), quadrillion is 10^15.

➋ support snapshots, snapshots is a read only copy of file system.

➌ file system grow dynamically as disk is added

➍ File systems may span multiple physical disks

➎ ZFS is transactionl file system

➏ ZFS file systems are auto-mounted

➐ ZFS file systems support quota and reservation

➑ provides web-based managment tool.

System Recommendation

➊ One GB or more of memory is recommended.

➋ Run ZFS on a system that runs a 64-bit kernel

➌ Approximately 64 KB of memory is consumed per mounted ZFS file system.

➍ Set up one pool using whole disks per system

Tutorial Requremens

➊ 1GB RAM

➋ three hard disks ( You can use Virtual Box as a free tool to follow this tutorial step by step click here to learn Virtual BOX )

➌ Solaris 10 operating system

Tutorial information

in this tutorial we will

➊ create a zpool ( assume zpool is a container or repository that will hold ZFS file systems).

➋ create ZFS file system,set quota and reservation.

➌ Mirror ZFS file system ( RAID 0 , RAID 1 , RAIDZ)

➍ create snapshot of file system.

➏ create clones

↬ Create and configure ZFS

Zpool Creation, zpool is a container or repository that will hold ZFS file systems

➊ create zpool.

 zfs create test_pool c0d1

where c0d1 is the logical device name of the second hard disk (use format command to view hard disk name ), "test_pool" is the name of the pool.

➋ at the command prompt show test-pool information

 zpool list

output :-

NAME SIZE ALLOC FREE CAP HEALTH ALTROOT

 test_pool 3.97G 95.5K 3.97G 0% ONLINE -

Now you have a pool which will contain you zfs filesystem.

ZFS file system creation

➊ to create zfs file system at the ok prompt type

 zfs create test_pool/home1

➋ to create a second zfs file system at the ok prompt type

 zfs create test_pool/home2

➌ show zfs file system status and informatio

 zfs list

output :-

NAME USED AVAIL REFER MOUNTPOINT

test_pool 130K 3.91G 22K /test_pool

test_pool/home1 21K 3.91G 21K /test_pool/home1

 test_pool/home2 21K 3.91G 21K /test_pool/home2

now as you can see we have one pool called test_pool and its size equal to the of the second hard disk size and we have two zfs file system home1 and home 2 which they share the test-pool size.

if you don't want home1 file system to exceed 2GB set the quota property as following

Quota property

➊ You can use the quota property to set a limit on the amount of disk space a file system can use, to set quota to 2GB at the ok prompt type

 zfs set quota=2g test_pool/home1

➋ show quota information

 zfs get -r quota test_pool/home1

output :-

NAME PROPERTY VALUE SOURCE test_pool/home1 quota 2G local

➌ to clear quota property

 zfs set quota=none test_pool/home1

ٌReservation property

➊ you can use the reservation property to guarantee that a specified amount of disk space is reserved to a file system, at the ok prompt type

zfs set reservation=3g test_pool/home2

➋ to clear reservation property

 zfs set reservation=none test_pool/home1

Remove ZFS file system

➊ to remove ZFS file system, at the command prompt type:-

 zfs destroy test_pool/home1

➋ to remove ZFS pool, at the command prompt type:-

 zpool destroy test_pool

↬ Mirror ZFS file system

Extend the ZFS file system space ( RAID 0 )

assume you have a zfs file system and the file system is approximately fully and you want to add a disk space to.

Note:- create a pool if you have destoryed it.

 zfs add test_pool c1d0

(where c0d1 is the logical device name of the third hard disk, use format command to get your hard disk name.

Mirror pool ( RAID 1 )

A RAID 1 creates an exact copy (or mirror) of a set of data on two or more disks.

➊ case 1 :- at the time of ZFS file system creation

Note:- Destroy all previous pool.

 zpool create test_poll mirror c0d1 c1d0

( where c0d1 and c1d0 are hard disk logical device names)

➋ list pool information

 zpool status

output:-

pool: test_pool  
  state: ONLINE  
  scrub: none requested  
 config:  
     NAME    STATE   READ WRITE CKSUM  
     test_pool  ONLINE    0   0   0  
      mirror-0 ONLINE    0   0   0  
       c0d1  ONLINE    0   0   0  
       c1d0  ONLINE    0   0   0  
 errors: No known data errors

➌ remove disk from mirror

 zpool detach test_pool c1d0

( this will remove c1d0 from pool)

Case 2 :- if you have a pool and you want to create RAID 1 ( Mirror ) at the ok prompt type :-

Note ;- destroy previous pool.

➊ create a pool

 zpool create test_pool c0d1

➋ create RAID 1 ( Mirror)

 zpool attach test_pool c0d1 c1d0

( where c1d0 is the new disk)

➌ remove disk from mirror

 zpool detach test_pool c1d0

RAIDZ

➊ Destroy previous pool

 zpool destory test_pool

➋ create a pool with RAIDZ

 zpool create test_pool raidz c0d1 c1d0 c2d0

↬ ZFS snapshot

snapshot is a read only copy of file system that is used for redundancy and backup assues.

Note :- to be not confused destroy prevous pool and create a new pool and zfs file system home1, home2, home3.

Steps to create a snapshot:-

➊ list all pervious snapshot

 zfs list -t snapshot

output :-

 no datasets available

➋ create snapshot

 zfs snapshot test_pool/home3@snapshot_name

➌ list snapshot configuration

 zfs list -t snapshot

output:-

NAME              USED AVAIL REFER MOUNTPOINT  
 test_pool/home3@snapshot_name   0   -  21K -

Steps to delete a snapshot

 zfs destroy test_pool/home3@snapshot_name

Steps to Rename a snapshot

 zfs rename test_pool/home3@snapshot_name test_pool/home3@new_snapshot_name

Restore snapshot

if you accidentally delete files or folders and you want to restore it from snapshot :-

 zfs reollback test_pool/home3@snapshot_name

where the "test_pool/home3@snapshot_name" is the name of the snapshot.

↬ ZFS Clones

ZFS clones is a writable copy of file system, ZFS clone linked to snapshot you must create a snapshot then create a clone.

steps to create snapshot :-

➊ Create pool

➋ create snapshot

➌ create clone

 fs clone test_pool/home3@snapshot_name test_pool/home5

this command will create new zfs file system home5,

Oracle VirtualBOX

2011-10-23T09:27:00.000-07:00

Oracle VirtualBOX

Oracle VM VirtualBox is an virtualization software package, you can install and will enable you to install another operating system on your computer. It will share the ram and CPU power of your other OS, form example if you are running windows and install virtualbox you can then install oracle solaris and other operating system, Download VirtualBOX from here VirtualBOX

To install Oracle Solaris on VirtualBOX

Download Oracle Solaris 10/11 form here Solaris 10
Run VirtualBox from your computer
Click on new, and choose a name for your virtual machine, and also choose the OS type you will install on it.

4. Choose the memory amount, and click on next and next again

5. Choose the size of disk you want to be availble for the virtual machine

6.Click create

7. insert Oracle Solaris Media .

8. select the OS you want and click start bottom from the Menu, follow the information to install Solaris OS.

9. if you want to add more hard disks to your virtual OS, select the Virtual OS and click settingd

10. select Storage

11. click add hard disk

12. Click Next, then choose "Fixed size", Click Next

13. choose your new Hard disk size, click Next, click create.

14. your hard disk is ready now.

Configure caching-only Server

2011-10-05T02:46:00.000-07:00

Caching server gets its information from another server ( Master DNS server ) in response to a host query and then cache this information locally, it saves cached data until the time period "time-to-live" in named.conf file expire. When a caching only DNS server starts for the first time, it has't cached informaton , the caching only DNS server collects information as it send and recive quires.

Caching only Characteristic
1- A caching-only server is not authoritative for any domain.
2- Caching-only DNS servers do not host zones.
3- caching-only DNS servers are excluded from the zone transfer process, and therefore do not generate network traffic from zone transfers.

Configure Caching only DNS server

before configure Caching-only DNS server yu have to configure Master DNS server Follow this link to learn how to :-

Configure DNS server on oracle solaris 10

the files that are needed to start Caching-only DNS server are :- 

1- named.conf

2- root server file

➊ make sure your DNS daemon is disabled.

 svcadm disable dns/server

➋ create the DNS confiuration file "named.conf"

 touch /etc/named.conf

➌ edit the "named.conf" file

 vi /etc/named.conf

The file will be opened for editing , if you don't know how to use VI editor follow this link to be more familiar with VI Editor:- UNIX VI editor

➍ add the following lines to the "named.conf" file.

options {  
         "/var/named";  
 };

zone "." {  
       type hint;  
       file "db.cache";  
 };

➎ create db.cache

 mkdir /var/named

 cd /var/named

↪ Download root servers file

 /usr/sfw/bin/wget ftp://ftp.rs.internic.net/domain/named.root

↪ rename named.root to db.cache

 mv named.root db.cache

UNIX VI editor

2011-10-04T05:59:00.000-07:00

The vi editor is a command-line editor that has three basic modes of operation:

➊ Command mode
➋ Edit mode
➌ Last line mode

➊ Command mode :- The command mode is the default mode for the vi editor. In this mode, you can perform commands to delete, change, copy, and move text. You can also position the cursor, search for text strings, and exit the vi editor.

➋ Edit mode :- You can enter text into a file in the edit mode. The vi editor interprets everything you type in the edit mode as text. To enter the edit mode,
perform the commands:

➟ i – Inserts text before the cursor
➟ o – Opens a new blank line below the cursor
➟ a – Appends text after the cursor

➌ Last Line Mode :- You can use advanced editing commands in the last line mode. To access the last line mode, enter a colon (:) while in the command mode. The colon places your cursor at the bottom line of the screen.

Switching Between the Command and Edit Modes

The default mode for the vi editor is the command mode. When you perform an i, o, or (a) command, the vi editor switches to the edit mode. After editing a file, press Escape to return the vi editor to the command mode. When in the command mode, you can save the file and quit the vi editor.

The following example shows how to switch modes in the vi editor:

1. Perform the vi filename command to create a file. You are
automatically in the command mode.

2. Type the i command to insert text. The i command switches the vi editor to the edit mode.

3. Press Escape to return to the command mode.

4. Perform the :wq command to save the file and exit the vi editor.

Inserting and Appending Text

➟ a - Appends text after the cursor
➟ A - Appends text at the end of the line
➟ i - Inserts text before the cursor
➟ I - Inserts text at the beginning of the line
➟ o - Opens a new line below the cursor
➟ O - Opens a new line above the cursor
➟:r -filename Inserts text from another file into the current file

Moving the Cursor Within the vi Editor

➟ h,left arrow,or Backspace - Left one character
➟ j or down arrow         - Down one line
➟ k or up arrow             - Up one linel,
➟ right arrow,or space bar - Right (forward) one character
➟ w                         - Forward one word
➟ b     - Back one word
➟ e                         - To the end of the current word
➟ $                         - To the end of the line
➟ 0 (zero)                  - To the beginning of the line
➟ Return Down               - to the beginning of the next line
➟ G                         - Goes to the last line of the file
➟ 1G                        - Goes to the first line of the file
➟ :n                        - Goes to Line n
➟ nG                      - Goes to Line n
➟ Control-F - forward one screen
➟Control-D                 - Scrolls down one-half screen
➟Control-B                  - Pages back one screen
➟Control-U                  - Scrolls up one-half screen
➟Control-L                  - Refreshes the screen
➟Control-G                  - Displays current buffer information

Editing Files by Using the vi Editing Commands

➟ x                          - Deletes a character at the cursor.
➟ dw                         - Deletes a word
➟ dd                         - Deletes the line
➟:n,nd                     - Deletes Lines n –n

Using the Text-Replacing Commands

➟ /string                    - Searches forward for the string.
➟ ?string                    - Searches backward for the string.
➟ n                          - Searches for the next occurrence.
➟ N    - Searches for the previous occurrence of the string.

Using the Text-Copying and Text-Pasting Commands

➟yy :- Yanks a copy of a line
➟p :- Puts yanked or deleted text under the line containing
the cursor.
➟P :- Puts yanked or deleted text before the line containing
the cursor

Using the File Save and Quit Commands

➟:w :- Saves the file with changes by writing to the disk
➟:w new_filename :- Writes the contents of the buffer to new_filename
➟:wq :- Saves the file with changes and quits the vi editor
➟:x :- Saves the file with changes and quits the vi editor
➟ZZ :- Saves the file with changes and quits the vi editor
➟:q! :- Quits without saving changes

Summery

Search Functions                                               Move and Insert Text
/exp Go forward to exp                                      :3,8d Delete line 3-8
?exp Go backward to exp                                  :4,9m 12 Move lines 4-9 to 12
                                                                           :2,5t 13 Copy lines 2-5 to 13
Save Files and Exit                                           :5,9w file Write lines 5-9 to file
:w Write to disk
:w newfile Write to newfile                                Screen/Line Movement
:w! file Write absolutely                                      j    Move cursor down
:wq Write and quit                                              k    Move cursor up
:q Quit editor                                                      h    Move cursor left
:q! Quit and discard                                            l    Move cursor right
                                                                            0   Go to line start (zero)
Word Movement     $    Go to line end
w   Go forward 1 word                                    G    Go to last file line
b    Go backward 1 word

Delete Text                                                         Add/Append Text
x    Delete 1 character                                         a    Append after cursor
dw    Delete 1 word                                             A    Append at line end
dd    Delete 1 line                                                 i    Insert before cursor
D    Delete to end of line                                      5i    Insert text 5 times
d0    Delete to start of line                                   I    Insert at beginning of line
dG    Delete to end of file

Copy and Insert Text                                            Add New Lines
Y    Yank a copy                                                   o    Open a line below cursor
5Y   Yank a copy of 5 lines                                   O    Open a line above cursor
p    Put below cursor
P    Put above cursor

Configure Slave DNS server on solaris 10

2011-10-03T02:57:00.000-07:00

Configure Slave DNS server Solaris

Slave DNS server provide DNS services even if the master goes down , Slave DNS server gets its zone data using a zone transfer operation from a zone master (master DNS server) , Zone transfer is the process of receiving data from master server to slave server.

Slave DNS server Configuration : -

➟ Configure Master DNS server

➟ Configure SLave DNS server

Master Server IP address :- 192.168.2.2

Slave Server IP address :- 192.168.2.3

Master Server Name :- ns1.test.domain

Slave Server Name :- ns2.test.domain

➟ Configure Master DNS server

➊ make sure your DNS daemon is disabled.

 svcadm disable dns/server

➋ create the DNS confiuration file "named.conf"

 touch /etc/named.conf

➌ edit the "named.conf" file

 vi /etc/named.conf

The file will be opened for editing , if you don't know how to use VI editor follow this link to be more familiar with VI Editor:- UNIX VI editor

➍ add the following lines to the "named.conf" file , Note : Don't add "Block #" word it's just for illustration purpose.

Block 1

options {  
         "/var/named";  
 };

Block 2

zone "." {  
       type hint;  
       file "db.cache";  
 };

Block3

zone "0.0.127.in-addr.arpa" {  
            type master;  
            file "db.127.0.0";  
 }

Block4

zone "2.168.192.in-addr.arpa" {  
               type master;  
               file "db.192.168.2";  
 };

Block5

zone "domain.test" {  
             type master;  
             file "db.domain.test";  
 };

Note That :-

Block1:-tells the DNS that zone files are located in "/var/named".

Block2:- tells the DNS the address of root servers and the zone configuration file is called db.cache , if you don't know what root servers follow this link HOW DNS WORK.

Block3:-tells the DNS server there are a localhost zone and its called db.127.0.0 This zone allows resolution of the name 'localhost' to the loopback address 127.0.0.1 when using the DNS server.

Block4:- tells the DNS server that there are reverse lookup zone and the zone configuration file is called db.192.168.2 .

Block5:- tells the DNS server that there are forward zone and the zone configuration file is called db.domain.test.

Now create zone files on master server

as shown in "named.conf" file there are four zone configuration files.

db.cache , db.127.0.0 , db.192.168.2 , domain.test .

➊ create db.cache

 mkdir /var/named

 cd /var/named

➋ Download root servers file

 /usr/sfw/bin/wget ftp://ftp.rs.internic.net/domain/named.root

➌ rename named.root to db.cache

 mv named.root db.cache

➍ create db.127.0.0

 vi db.127.0.0

➎ type the following information inside "db.127.0.0" file

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS ns1.

      NS ns2. 
 1     IN     PTR     localhost.

Note :-
ns1. is:-(your DNS server name), to find your server name :-

 uname -n

✔ The serial number is a record of how often this DNS entry has been updated. Every time a change is made to the entry, the serial number must be incremented.

✔ The "refresh" number stands for how often secondary name servers should check the primary for a change in the serial number.

✔ Expire" is how long the secondary server should use its current entry if it is unable to perform a refresh

✔ "minimum" is how long other nameservers should cache, or save, this entry

➏ create db.192.168.2

 vi db.192.168.2

➐ type the following information inside "db.192.168.2" file .

@ IN SOA ns1.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS ns1.

     NS ns2.
2     IN     PTR     localhost.

Note :

2 IN PTR localhost. => 2 is the last part of the server ip (192.168.2.2)

➑ create db.domain.test

 vi db.domain.test

➒ type the following information inside "db.domain.test" file .

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS ns1.

      NS ns2.  
ns1    IN     A     192.168.2.2

ns2    IN     A     192.168.2.3

➓ check your configuration syntax

named-checkconf -z /etc/named

if there are any errors you will see a warning messages.

- enable dns server daemon

 svcadm enable dns/server

- check the status of dns/server daemon

 svcs -a | grep dns/server

online         19:42:04 svc:/network/dns/server:default

➟ Configure SLave DNS server

➊ make sure your DNS daemon is disabled.

 svcadm disable dns/server

➋ create the DNS confiuration file "named.conf"

 touch /etc/named.conf

➌ edit the "named.conf" file

 vi /etc/named.conf

The file will be opened for editing , if you don't know how to use VI editor follow this link to be more familiar with VI Editor.

➍ add the following lines to the "named.conf" file.

options     {  
      directory "/var/named";  
 };  
 zone "." {  
      type hint ;  
      file "db.cache";  
 };  
 zone     "0.0.127.in-addr.arpa" {  
      type slave ;  
      file "db.127.0.0";  
      masters {192.168.2.2;};  
 };  
 zone     "9.109.10.in-addr.arpa" {  
      type slave ;  
      file "db.10.109.9" ;  
      masters {192.168.2.2;};  
 };  
 zone     "2.168.192.in-addr.arpa" {  
      type slave ;  
      file "db.192.168.2" ;  
      masters {192.168.2.2;};  
 };  
 zone     "test.internal" {  
      type slave ;  
      file "db.test.internal" ;  
      masters {192.168.2.2;};  
 } ;

Now create zone files :- db.127.0.0 , db.cache

➊ create db.cache

 mkdir /var/named

 cd /var/named

➋ Download root servers file

 /usr/sfw/bin/wget ftp://ftp.rs.internic.net/domain/named.root

➌ rename named.root to db.cache

 mv named.root db.cache

➍ create db.127.0.0

 vi db.127.0.0

➎ type the following information inside "db.127.0.0" file

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS ns1.

      NS ns2. 
 1     IN     PTR     localhost.

➏ check your configuration syntax

named-checkconf -z /etc/named

if there are any errors you will see a warning messages.

➐ enable dns server daemon

 svcadm enable dns/server

➑ check the status of dns/server daemon

 svcs -a | grep dns/server

online         19:42:04 svc:/network/dns/server:default

Configure DNS server on oracle solaris 10

2011-09-24T10:39:00.001-07:00

Master DNS Server Configuration

Estimated Time :- 30 Minutes ツ

To configure DNS server , you need to set up a number of configuration files, mainly you need to configure "named.conf" file and zone files.

named.conf file is located in /etc/, and it includes information about zones and other options.

➊ First Step is to configure "named.conf" file:-

↪ make sure your DNS daemon is disabled.

 svcadm disable dns/server

↪ create the DNS confiuration file "named.conf"

 touch /etc/named.conf

↪ edit the "named.conf" file

 vi /etc/named.conf

The file will be opened for editing , if you don't know how to use VI editor follow this link to be more familiar with VI Editor:- UNIX VI editor

↪ add the following lines to the "named.conf" file , Note : Don't add "Block #" word it's just for illustration purpose.

Block 1

 options {  
         "/var/named";  
 };

Block2

 zone "." {  
       type hint;  
       file "db.cache";  
 };

Block3

 zone "0.0.127.in-addr.arpa" {  
            type master;  
            file "db.127.0.0";  
 };

Block4

zone "2.168.192.in-addr.arpa" {  
               type master;  
               file "db.192.168.2";  
 };

Block5

zone "domain.test" {  
             type master;  
             file "db.domain.test";  
 };

Note That :-

Block1:-tells the DNS that zone files are located in "/var/named".

Block2:- tells the DNS the address of root servers and the zone configuration file is called db.cache , if you don't know what root servers follow this link HOW DNS WORK.

Block3:-tells the DNS server there are a localhost zone and its called db.127.0.0 This zone allows resolution of the name 'localhost' to the loopback address 127.0.0.1 when using the DNS server.

Block4:- tells the DNS server that there are reverse lookup zone and the zone configuration file is called db.192.168.2 .

Block5:- tells the DNS server that there are forward zone and the zone configuration file is called db.domain.test.

➋ second step is to create and configure zone file .

as shown in "named.conf" file there are four zone configuration files.

db.cache , db.127.0.0 , db.192.168.2 , domain.test .

↪ create db.cache

 mkdir /var/named

 cd /var/named

↪ Download root servers file

 /usr/sfw/bin/wget ftp://ftp.rs.internic.net/domain/named.root

↪ rename named.root to db.cache

 mv named.root db.cache

↪ create db.127.0.0

 vi db.127.0.0

↪ type the following information inside "db.127.0.0" file .

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS server_name.  
 1     IN     PTR     localhost.

Note :-

server_name.domain.test is:-(your DNS server name).(your domain).

to find your server name :-

 uname -n

✔ The serial number is a record of how often this DNS entry has been updated. Every time a change is made to the entry, the serial number must be incremented.

✔ The "refresh" number stands for how often secondary name servers should check the primary for a change in the serial number.

✔ Expire" is how long the secondary server should use its current entry if it is unable to perform a refresh

✔ "minimum" is how long other nameservers should cache, or save, this entry

↪ create db.192.168.2

 vi db.192.168.2

↪ type the following information inside "db.192.168.2" file .

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS server_name.  
2     IN     PTR     localhost.

Note :

2 IN PTR localhost. => 2 is the last part of the server ip (192.168.2.2)

↪ create db.domain.test

 vi db.domain.test

↪ type the following information inside "db.domain.test" file .

@ IN SOA server_name.domain.test. admin_mail.domain.test. (  
      20110622 ; serial number   
      7200 ; Refresh Interval  
      3600 ; Retry Interval  
      86400 ; Expire  
      600 ) ; TTL  
      NS server_name.  
server_name    IN     A     192.168.2.2

➌ check your configuration syntax

named-checkconf -z /etc/named

if there are any errors you will see a warning messages.

➍ enable dns server daemon

 svcadm enable dns/server

➎ check the status of dns/server daemon

 svcs -a | grep dns/server

online 19:42:04 svc:/network/dns/server:default

Apache shared hosting

2011-09-06T15:27:00.000-07:00

Introduction : -

Shared Hosting or Virtual Hosting refers to a hosting service where more than one web site reside on the same server , each web site has its own space.

Apache Shared Hosting can be implementing in two ways :-

1- Apache IP-based virtual Hosting : - each web site should has its own IP address or web sites can share one IP address but with different PORT number (www.site1.com:8888 , www.site2.com:8889 ... ) .

2- Apache Name-based Virtual Hosting :- more than one web site can share the same IP address , that means all web sites in the DNS point to the same IP address and the apache takes care of redirect the requester to the correct site.

Example :-

x hosting company host six web sites ( www.site1.com , www.site2.com .... www.site6.com ) on the same server and each of them belong to different person.

Implementation :-

assume we have one server running solaris 10 and we want to host two web sites on this server .

Information :-

- First web Server IP :- 192.168.1.50

- Second web Server IP :- 192.168.1.51 (you need the second IP just if you want to implement IP-based Virtual host based on port number)

- first web site name :- site1.com

- second web site name :- site2.com

Steps :-

Note :- Clear cache storage in the web browser before test any changes .

- IP-based virtual host (case 1 :- each site has its own IP address )

➊ make sure the apache service is running on solaris 10 , at the prompt type :-

  svcs -a | grep -i apache2

if the apache is running you will see the following : -

 online   0:28:03 svc:/network/http:apache2

if the status is disabled ,

 disable   0:28:03 svc:/network/http:apache2

enable it , at the command prompt type :-

  svcadm enable apache2

➋ create directories that will hold site1 and site 2 files , 

cd /var/apache2/htdocs       
mkdir site1 site2         
cd site1             
echo "Site1 Page">>index.html   
cd ..                 
cd site2             
echo "Site2 Page">>index.html

note that the "/var/apache2/htdocs is the DocumentRoot folder which holds all web sites files.

➌ Copy the file /etc/apache2/httpd.conf-example to /etc/apache2/httpd.conf by running the following command .

 cp /etc/apache2/httpd.conf-example /etc/apache2/httpd.conf

➍ edit the httpd.conf file as the following :-  

  vi /etc/apache2/httpd.conf

Follow the link to Configure basic apache setting :- Configure Apache on Solaris

scroll down until you reach Virtual Hosts section .

add the following information :-

<VirtualHost 192.168.1.50:80>   
  ServerName site1.com   
  ServerAdmin admin@site1.com   
  DocumentRoot /var/apache2/htdocs/site1   
  ErrorLog /var/apache2/logs/site1.error.log   
  Customlog /var/apache2/logs/site1.access.log combind   
  </VirtualHost>   
  <VirtualHost 192.168.1.55:80>   
  ServerName site2.com   
  ServerAdmin admin@site2.com   
  DocumentRoot /var/apache2/htdocs/site2   
  ErrorLog /var/apache2/logs/site2.error.log   
  CustomLog /var/aapche2/logs/site2.access.log   
  </VirtualHost>

➎ save and close the document.

➏ restart the apache service

  svcadm restart apache2

now , you have completed the configuration , try to access the site1.com by its IP address by type 192.168.1.50 in the web browser , if you see Site1 Page then your configuration is OK , now try to access site2.com by type 192.168.1.55 in the web browser , you have to see Site2 Page.

if you want to access site1 and site2 by names add a recored in the DNS for site1 and site2 , if you don't have a DNS server you can do that from hosts file in the operating system as follow :-

↪ UNIX + Linux = edit /etc/hosts file and add a record for site1 and site2 as following :-

192.168.1.50 site1.com

192.168.1.55 site2.com

↪ Windows = edit C:\WINDOWS\system32\drivers\etc\hosts file and add a record for site1 and site as following :-

192.168.1.50 site1.com

192.168.1.55 site2.com

-IP-based virtual host ( case 2 :- web sites share one IP address with different PORT )

➊ clear all configuration in previous step .

➋ make sure the apache service is running on solaris 10 , at the prompt type :- 

  svcs -a | grep -i apache2

if the apache is running you will see the following : -

online   0:28:03 svc:/network/http:apache2

if the status is disabled ,

disable   0:28:03 svc:/network/http:apache2

enable it , at the command prompt type :-

svcadm enable apache2

➌ create directories that will hold site1 and site 2 files .

cd /var/apache2/htdocs       
mkdir site1 site2         
cd site1             
echo "Site1 Page">>index.html   
cd ..                 
cd site2             
echo "Site2 Page">>index.html

note that the "/var/apache2/htdocs is the DocumentRoot folder witch holds all web sites files .

➍ Copy the file /etc/apache2/httpd.conf-example to /etc/apache2/httpd.conf by running the following command .

cp /etc/apache2/httpd.conf-example /etc/apache2/httpd.conf

➎ edit the httpd.conf file as the following :- 

  vi /etc/apache2/httpd.conf

scroll down until you reach Listen Directive , add the following information :-

 Listen 192.168.1.50:8081   
 Listen 192.168.1.50:8082

➏ scroll down until you reach Virtual Host section and ad the following :-  

<VirtualHost 192.168.1.50:8081>   
  ServerName site1.com   
  ServerAdmin admin@site1.com   
  DocumentRoot /var/apache2/htdocs/site1   
  ErrorLog /var/apache2/logs/site1.error.log   
  Customlog /var/apache2/logs/site1.access.log combind   
 </VirtualHost>   
 <VirtualHost 192.168.1.50:8080>   
  ServerName site2.com   
  ServerAdmin admin@site2.com   
  DocumentRoot /var/apache2/htdocs/site2   
  ErrorLog /var/apache2/logs/site2.error.log   
  CustomLog /var/aapche2/logs/site2.access.log   
 </VirtualHost>

➐ save and close the document.

➑ restart the apache service

 svcadm restart apache2

now , you have completed the configuration , try to access the site1.com by its IP address by type 192.168.1.50:8081 in the web browser , if you see Site1 Page then your configuration is OK .

now try to access site2.com by type 192.168.1.50:8080 in the web browser you have to see Site2 Page.

if you want to access site1 and site2 by names add a recored in the DNS for site1 and site2 , if you don't have a DNS server you can do that from hosts file in the operating system as follow :-

↪ UNIX + Linux = edit /etc/hosts file and add a record for site1 and site2 as following :-

192.168.1.50 site1.com

192.168.1.50 site2.com

↪ Windows = edit C:\WINDOWS\system32\drivers\etc\hosts file and add a record for site1 and site as following :-

192.168.1.50 site1.com

192.168.1.50 site2.com

in the browser type site1.com:8081 and site2.com:8080

- Name-Based Virtual Host

➊ clear all configuration in previous step .

➋ make sure the apache service is running on solaris 10 , at the prompt type :-

 svcs -a | grep -i apache2

if the apache is running you will see the following : -

  online   0:28:03 svc:/network/http:apache2

Copy the file /etc/apache2/httpd.conf-example to /etc/apache2/httpd.conf by running the following command .

 cp /etc/apache2/httpd.conf-example /etc/apache2/httpd.conf

➌ create directories that will hold site1 and site 2 files .

cd /var/apache2/htdocs   
 mkdir site1 site2    
 cd site1    
 echo "Site1 Page">>index.html   
 cd ..   
 cd site2   
 echo "Site2 Page">>index.html

➍ edit the httpd.conf file as the following :- 

  vi /etc/apache2/httpd.conf

➎ scroll down until you reach Virtual Host section and ad the following :- NameVirtualHost 192.168.1.50:80

<VirtualHost 192.168.1.50>   
  ServerName site1.com   
  ServerAdmin admin@site1.com   
  DocumentRoot /var/apache2/htdocs/site1   
  ErrorLog /var/apache2/logs/site1.error.log   
  Customlog /var/apache2/logs/site1.access.log combind   
</VirtualHost>   
<VirtualHost 192.168.1.50>   
  ServerName site2.com   
  ServerAdmin admin@site2.com   
  DocumentRoot /var/apache2/htdocs/site2   
  ErrorLog /var/apache2/logs/site2.error.log   
  CustomLog /var/aapche2/logs/site2.access.log   
</VirtualHost>

➏ save and close the document.

➐ restart the apache service 

  svcadm restart apache2

if you want to access site1 and site2 by names add a recored in the DNS for site1 and site2 , if you don't have a DNS server you can do that from hosts file in the operating system as follow :-

↪ UNIX + Linux = edit /etc/hosts file and add a record for site1 and site2 as following :-

192.168.1.50 site1.com

192.168.1.50 site2.com

↪ Windows = edit C:\WINDOWS\system32\drivers\etc\hosts file and add a record for site1 and site as following :-

192.168.1.50 site1.com

192.168.1.50 site2.com

in the browser type site1.com and site2.com

Configure Apache on Solaris

2011-09-06T09:29:00.000-07:00

Step by Step tutorial to Configure httpd.conf apache file .

Before reading this article be sure that your apache is running

 svcs -a | grep -i apache2

if the status is on-line you apache is running

 online     11:37:06 svc:/network/http:apache2

if the status is disable or something else read the following article

Starting Apache on Solaris 10

### Notes ###

- httpd.conf file is a configuration file that contains all information (Directives) necessary for apache server to run .

- Commonly , I use VI editor to edit and configure httpd.conf file , click here to learn more about VI editor ./////

- Apache is configured by placing directives in plain text configuration files.

- Before editing httpd.conf, make a copy the original file.

Apache requires the following information for the DEFAULT HOST :

➟ ServerName

➟ ServerAdmin

➟ DocumentRoot

➟ Listen directive

➟ ServerName

is a valid Domain Name Service (DNS) name that can be resolved by the system.

Example : www.yoursite.com

the steps To set the ServerName Directive in httpd.conf :-

➊ at the command prompt type

 vi /etc/apache2/httpd.conf

➋ Vi editor will open the httpd.conf , search for the ServerName directive and change it to your site name .

 ServerName www.yoursite.com

save and close the file .

➟ ServerAdmin

the E-mail address of the web server administrator , this address shows up in error messages .

the steps to set the ServerAdmin Directive in hhtpd.conf

➊ at the command prompt type 

 vi /etc/apache2/httpd.conf

➋ Vi editor will open the httpd.conf , search for the serverAdmin directive and change it to the web server administrator.

 ServerAdmin you@yourhost.com

save and close the file .

➟ DocumentRoot

DocumentRoot is a directory where all your website files (HTML files) reside , the default location in Solaris 10 is /var/apache2/htdocs ,for example the server might receive a request for the following document :- www.yourwebsite.com/file.html , The server looks for the file in the default directory: /var/apache2/htdocs , you can change its value by editing httpd.conf .

➟ Listen directive

The Listen directive tells the server to accept incoming requests only on the specified port or address-and-port combinations.

Examples : -

To make the server accept connections on ports 80 and 8888 change the Listen Directive in httpd.conf as follow :-

Listen 80  
Listen 8888

To make the server accpet connectios on only port 8888 change the value of Listen Directive to be : -

 Listen 8888

that means if the client request your web site just by its name ( www.site.com ) the request will be failed because the default Port is ( 80 ) and you have changed it to ( 8888 ) so , the client should request the site name plus the port number (www.site.com:8888) to get the correct response.

the default value for Listen Directive is :-  

Listen 80

Starting Apache on Solaris 10

2011-09-06T03:42:00.001-07:00

Step By Step tutorial to start Apache on Solaris 10

### Notes ###

- Apache is a free web server that is distributed under an "Open Source" license.

- Apache web server is already installed on Solaris10.

- The main Configuration file for Apache is httpd.conf .

- The httpd.conf file does not exist by default .

### Steps To Start Apache on Solaris ###

➊ Connect To your Server .
➋ check if the apache is already running by running the following command :-

 svcs -a | grep -i apache2

Output :-

 disabled    Jun_18  svc:/network/http:apache2

you can see that the apache is disabled .

➌ Copy the file /etc/apache2/httpd.conf-example to /etc/apache2/httpd.conf by running the following command .

 cp /etc/apache2/httpd.conf-example /etc/apache2/httpd.conf

Note :- The file 'httpd.conf-example' contains an example of how to configure your apache web server .

➍ Start the apache web server by running the following command.

 svcadm enable apache2

➎ check the apache server status by running the following command :-

 svcs -a | grep -i apache2

Output :-

 online     11:37:06 svc:/network/http:apache2

you can see that the apache status is online , and that means everything is ok at the moment.

➏ to check your work enter the following URL in the web server browser http://localhosts/manual , if you see the following page then your first step is correct .