Solaris operating systems tips

How to delete mirror

2011-09-08T19:45:00.000-07:00

You can delete your mirror device. It is very simple like the steps below.

See your file system which is mounted from mirror device. For example you have filesystem /sample that is mounted from mirror device d1
bash-3.00# df -h /sample

Filesystem size used avail capacity Mounted on

/dev/md/dsk/d1 940M 1.0M 883M 1% /sample

See your mirror configuration. In this example you can see there are a mirror called d1, with 2 submirrors called d11 and d12.
bash-3.00# metasatt tat|more

d1: Mirror

Submirror 0: d11

State: Okay

Submirror 1: d12

State: Resyncing

Resync in progress: 2 % done

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 2048000 blocks (1000 MB)

d11: Submirror of d1

State: Okay

Size: 2048000 blocks (1000 MB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c3t2d0s0 0 No Okay Yes

d12: Submirror of d1

State: Resyncing

Size: 2048000 blocks (1000 MB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c3t3d0s0 0 No Okay Yes

Device Relocation Information:

Device Reloc Device ID

c3t3d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB5c17d304-00de27e4

c3t2d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB08da0d81-38b71174

Unmount your filesystem
bash-3.00# umount /sample
Detach one of the submirror. For example you detach d12
bash-3.00# metadetach d1 d12
d1: submirror d12 is detached

Delete your mirror and submirror device
bash-3.00# metaclear -r d1

d1: Mirror is cleared

d11: Concat/Stripe is cleared

bash-3.00# metaclear d11 2

d12: Concat/Stripe is cleared

How to configure IPv6 IPMP

2011-07-25T06:52:00.000-07:00

IPMP enable to recover from network path failures. If a failure occurs in one network link and an alternate link is configured, IP address can fails over. So network access changes automatically from the failed link to the alternate link, providing uninterrupted access to the network. Here is tips to configure IPMP with Ipv6. You need Solaris 8 10/00 as minimum.

Verify the solaris OS release
# more /etc/release
Solaris 10 5/08 s10x_u5wos_10 X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008
In SPARC system, you must configure the host to have unique MAC address for each interface.
# eeprom "local-mac-address?"
local-mac-address?=false
# eeprom "local-mac-address?=true"
# eeprom "local-mac-address?"
local-mac-address?=true

Your two interfaces are already set up using Ipv4. View your configuration. This below example shows 2 interfaces: e1000g0 and e1000g1.
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255
ether 8:0:27:7e:12:82
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255
ether 8:0:27:7e:12:83
Set your interface to include IPMP. You need to edit /etc/hostname6.<interface> file. The two interfaces will be member of IPMP group. In this example, you have group jupiter-group.
# more /etc/hostname6.e1000g0
-failover group jupiter-group up
# more /etc/hostname6.e1000g1
-failover group jupiter-group up
Configure each interface to start using IPMP.
# ifconfig e1000g0 group jupiter-group
# ifconfig e1000g1 group jupiter-group
Confiure each interface to start use IPMP for IPv6

# ifconfig e1000g0 inet6 plumb up

# ifconfig e1000g1 inet6 plumb up

Configure IPv6 test address for each interface.
# ifconfig e1000g0 inet6 -failover
# ifconfig e1000g1 inet6 -failover
View your IPMP configuration
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255
groupname jupiter-group
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255
groupname jupiter-group

ether 8:0:27:7e:12:83

e1000g0: flags=a000841<UP,RUNNING,MULTICAST,IPv6,NOFAILOVER> mtu 1500 index 2

ether 8:0:27:7e:12:82

inet6 fe80::a00:27ff:fe7e:1282/10

groupname jupiter-group

e1000g1: flags=a000841<UP,RUNNING,MULTICAST,IPv6,NOFAILOVER> mtu 1500 index 2

ether 8:0:27:7e:12:83

inet6 fe80::a00:27ff:fe7e:1283/10

groupname jupiter-group

Check that mpathd daemon is running. If not running, start this daemon.
# /sbin/in.mpathd

How to delete a zone

2011-07-25T06:49:00.000-07:00

You can delete a non global zone if you no longer need it. Below is tips to delete non global zone. Fot this example your non global zone name is zone1.

Shutdown non global zone
# init 0
See the status of non global zone. If your non global zone is already down, status become 'installed'.
root@solaris-sunray # zoneadm list -cp
0:global:running:/::native:shared
2:zone1:installed:/export/home/zone1:3bec2239-802b-e1b4-99dd-bd732571e925:native:shared
Uninstall non global zone. Your non global status become 'configured'.
root@solaris-sunray # zoneadm -z zone1 uninstall
root@solaris-sunray # zoneadm list -cp
0:global:running:/::native:shared
2:zone1:configured:/export/home/zone1:3bec2239-802b-e1b4-99dd-bd732571e925:native:shared
Delete non global zone.
root@solaris-sunray # zoneadm -z zone1 delete

Are you sure you want to delete zone zone1(y/[n])? y
root@solaris-sunray # zoneadm list -cp
0:global:running:/::native:shared

How to create soft partition

2011-03-31T23:45:00.000-07:00

Soft partition are used to divide physical disk partition/slice into smaller area. For eample you have a disk slice 1 GB, and you want to divide that slice become 10 areas (each with 100 MB size). You can create a soft partition with following steps:

Create soft partition. In this example you will create 100 MB soft partition on disk slice c3t2d0s0 with 1 GB size.
bash-3.00# metainit d10 -p c3t2d0s0 100mb

d10: Soft Partition is setup

Check soft partition status
bash-3.00# metastat -p

d10: Soft Partition

Device: c3t2d0s0

State: Okay

Size: 204800 blocks (100 MB)

Device Start Block Dbase Reloc

c3t2d0s0 0 No Yes

Extent Start Block Block count

0 1 204800

Device Relocation Information:

Device Reloc Device ID

c3t2d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB08da0d81-38b71174

Create file system on the soft partition
bash-3.00# newfs /dev/md/rdsk/d10

/dev/md/rdsk/d10: Unable to find Media type. Proceeding with system determined parameters.

newfs: construct a new file system /dev/md/rdsk/d10: (y/n)? y

/dev/md/rdsk/d10: 204800 sectors in 100 cylinders of 64 tracks, 32 sectors

100.0MB in 7 cyl groups (16 c/g, 16.00MB/g, 7680 i/g)

super-block backups (for fsck -F ufs -o b=#) at:

32, 32832, 65632, 98432, 131232, 164032, 196832,

Mount soft partition. For example mount on /document

bash-3.00# mount /dev/md/dsk/d10 /document

How to create and backup a snapshot

2011-03-16T00:17:00.000-07:00

You can use below procedure to create snapshot. In this example you create a snapshot of /data

Determine where you are going to store the backing store (the snapshot) file.
For example you use /var/tmp as a location to store the backing-store file, and you will snapshot /data filesystem.
Create the snapshot.
root@solaris-sunray # fssnap -F ufs -o backing-store=/var/tmp /data
Verify that snapshot is successful.
root@solaris-sunray # fssnap -i
0 /data
Mount the virtual device as you wish (optional)
root@solaris-sunray # mount -F ufs -o ro /dev/fssnap/0 /mnt
root@solaris-sunray # ls /mnt
Backup filesystem to tape
root@solaris-sunray # ufsdump 0ucf /dev/rmt/0 /dev/fssnap/0

How to create zone

2011-02-23T04:02:00.000-08:00

Zone allow virtual environment to run in the same host server. You can limit amount of physical resource that a zone can use. There are 2 types of zone, global zone and non-global zone. Global zone is the host server it self. Non global zone is the zone that we want to create. You can have maximum 8192 non global zone in a single host server. Below is tips to create a zone.

Set the zonepath for your zone. In this example zonepath is /export/home/zone1 from the global zone.
root@solaris-sunray # mkdir -p /export/home/zone1

root@solaris-sunray # chmod 700 /export/home/zone1

Configure the zone. Below example shows that your zone use IP address 172.16.31.150, use 20% of CPU resource, and label “zone number 1”.
root@solaris-sunray # zonecfg -z zone1

zone1: No such zone configured

Use 'create' to begin configuring a new zone.

zonecfg:zone1> create

zonecfg:zone1> set zonepath=/export/home/zone1

zonecfg:zone1> set autoboot=true

zonecfg:zone1> add net

zonecfg:zone1:net> set physical=e1000g0

zonecfg:zone1:net> set address=172.16.31.150

zonecfg:zone1:net> end

zonecfg:zone1> add rctl

zonecfg:zone1:rctl> set name=zone.cpu-shares

zonecfg:zone1:rctl> add value (priv=privileged,limit=20,action=none)

zonecfg:zone1:rctl> end

zonecfg:zone1> add attr

zonecfg:zone1:attr> set name=comment

zonecfg:zone1:attr> set type=string

zonecfg:zone1:attr> set value="zone number 1"

zonecfg:zone1:attr> end

After you configure the zone, do verify and commit.
zonecfg:zone1> verify

zonecfg:zone1> exit

Check the zone status (zone is configured properly or not)

root@solaris-sunray # zoneadm -z zone1 list -v

ID NAME STATUS PATH BRAND IP

- zone1 configured /export/home/zone1 native shared

root@solaris-sunray # zoneadm -z zone1 verify

Install the zone
root@solaris-sunray # zoneadm -z zone1 install

Preparing to install zone <zone1>.

Creating list of files to copy from the global zone.

Copying <7079> files to the zone.

Initializing zone product registry.

Determining zone package initialization order.

Preparing to initialize <1077> packages on the zone.

...

Initialized <1077> packages on zone.

Zone <zone1> is initialized.

Installation of <1> packages was skipped.

Installation of these packages generated warnings: <STATsrv>

The file </export/home/zone1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.

Change the zone state to ready and verify
root@solaris-sunray # zoneadm -z zone1 ready

zoneadm: zone 'zone1': WARNING: The zone.cpu-shares rctl is set but

zoneadm: zone 'zone1': FSS is not the default scheduling class for

zoneadm: zone 'zone1': this zone. FSS will be used for processes

zoneadm: zone 'zone1': in the zone but to get the full benefit of FSS,

zoneadm: zone 'zone1': it should be the default scheduling class.

zoneadm: zone 'zone1': See dispadmin(1M) for more details.

root@solaris-sunray # zoneadm -z zone1 verify

root@solaris-sunray # zoneadm -z zone1 list -v

ID NAME STATUS PATH BRAND IP

1 zone1 ready /export/home/zone1 native shared

Boot the zone and verify
root@solaris-sunray # zoneadm -z zone1 boot

root@solaris-sunray # zoneadm -z zone1 bootlist -v

ID NAME STATUS PATH BRAND IP

1 zone1 running /export/home/zone1 native shared

Log in to the zone console and set initial configuration like: host name, root password, timezone, name service, security policy, terminal type
root@solaris-sunray # zlogin -C zone1

[Connected to zone 'zone1' console]

...

[Connected to zone 'zone1' pts/4]

Last login: Fri Oct 15 11:22:13 on pts/4

Sun Microsystems Inc.SunOS 5.10GenericJanuary 2005

# exit

[Connection to zone 'zone1' pts/4 closed]

How to configure probe-based IPMP

2011-02-08T23:27:00.000-08:00

IPMP enable to recover from network path failures. If a failure occurs in one network link and an alternate link is configured, IP address can fails over. So network access changes automatically from the failed link to the alternate link, providing uninterrupted access to the network. Probe based IPMP utilize test address to monitor the health of interfaces. You need Solaris 8 10/00 as minimum.

Verify the solaris OS release
# more /etc/release
Solaris 10 5/08 s10x_u5wos_10 X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008
In SPARC system, you must configure the host to have unique MAC address for each interface.
# eeprom "local-mac-address?"

local-mac-address?=false

# eeprom "local-mac-address?=true"

# eeprom "local-mac-address?"

local-mac-address?=true

Edit your hosts file. In this example, you have 2 interface e1000g0 and e1000g1. Each interface has 2 IP address (data address and test address).
# more /etc/inet/hosts
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
172.16.31.11 jupiter loghost # data address for e1000g0
172.16.31.21 jupiter-e1000g1 # data address for e1000g1
172.16.31.111 jupiter-test # test address for e1000g0
172.16.31.211 jupiter-e1000g1-test # test address for e1000g1
Set your interface to include IPMP. You need to edit /etc/hostname.<interface> file. The two interfaces will be member of IPMP group. In this example, you have group jupiter-group.
# more /etc/hostname.e1000g0
jupiter netmask + broadcast + group jupiter-group up

addif jupiter-test deprecated netmask + broadcast + -failover up

# more /etc/hostname.e1000g1

jupiter-e1000g1 netmask + broadcast + group jupiter-group up

addif jupiter-e1000g1-test deprecated netmask + broadcast + -failover up

Configure each interface to start using IPMP.
# ifconfig e1000g0 jupiter netmask + broadcast + group jupiter-group up
# ifconfig e1000g0 addif jupiter-test deprecated netmask + broadcast + -failover up
# ifconfig e1000g1 jupiter-e1000g1 netmask + broadcast + group jupiter-group up
# ifconfig e1000g1 addif jupiter-e1000g1-test deprecated netmask + broadcast + -failover up
See your IPMP configuration

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.111 netmask fffffc00 broadcast 172.16.31.255

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

e1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.211 netmask fffffc00 broadcast 172.16.31.255

Verify that IPMP daemon is running.
# pgrep -lf in.mpathd
6513 /usr/lib/inet/in.mpathd
Test your IPMP configuration
# if_mpadm -d e1000g0
Nov 3 13:24:31 jupiter in.mpathd[119]: Successfully failed over from NIC e1000g0 to NIC e1000g1

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g0:1: flags=9040843<BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.111 netmask fffffc00 broadcast 172.16.31.255

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

e1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.211 netmask fffffc00 broadcast 172.16.31.255

e1000g1:2 flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

Return to your original IPMP configuration
# if_mpadm -r e1000g0
Nov 3 13:24:31 jupiter in.mpathd[535]: Successfully failed back to NIC e1000g0

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g0:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.111 netmask fffffc00 broadcast 172.16.31.255

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

e1000g1:1: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu

1500 index 2

inet 172.16.31.211 netmask fffffc00 broadcast 172.16.31.255

How to configure link-based IPMP

2011-01-28T00:51:00.000-08:00

IPMP enable to recover from network path failures. If a failure occurs in one network link and an alternate link is configured, IP address can fails over. So network access changes automatically from the failed link to the alternate link, providing uninterrupted access to the network. Link based IPMP utilize interface kernel driver to monitor the health of interfaces. Link-based IPMP do not use test address. You need Solaris 9 12/02 as minimum.

Verify the solaris OS release
# more /etc/release
Solaris 10 5/08 s10x_u5wos_10 X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008
In SPARC system, you must configure the host to have unique MAC address for each interface.
# eeprom "local-mac-address?"

local-mac-address?=false

# eeprom "local-mac-address?=true"

# eeprom "local-mac-address?"

local-mac-address?=true

Edit your hosts file. In this example, you have 2 interface e1000g0 and e1000g1.
# more /etc/inet/hosts
#
# Internet host table
#
::1 localhost
127.0.0.1 localhost
172.16.31.11 jupiter loghost # data address for e1000g0
172.16.31.21 jupiter-e1000g1 # data address for e1000g1
Set your interface to include IPMP. You need to edit /etc/hostname.<interface> file. The two interfaces will be member of IPMP group. In this example, you have group jupiter-group.

# more /etc/hostname.e1000g0
jupiter netmask + broadcast + group jupiter-group up

# more /etc/hostname.e1000g1

jupiter-e1000g1 netmask + broadcast + group jupiter-group up

Configure each interface to start using IPMP.
# ifconfig e1000g0 jupiter netmask + broadcast + group jupiter-group up
# ifconfig e1000g1 jupiter-e1000g1 netmask + broadcast + group jupiter-group up
See your IPMP configuration

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

verify that IPMP daemon is running.
# pgrep -lf in.mpathd
6513 /usr/lib/inet/in.mpathd
Test your IPMP configuration
# if_mpadm -d e1000g0
Nov 3 13:24:31 jupiter in.mpathd[119]: Successfully failed over from NIC e1000g0 to NIC e1000g1

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

e1000g1:1 flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

Return to your original IPMP configuration
# if_mpadm -r e1000g0
Nov 3 13:24:31 jupiter in.mpathd[535]: Successfully failed back to NIC e1000g0

# ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.11 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:82

e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.21 netmask fffffc00 broadcast 172.16.31.255

groupname jupiter-group

ether 8:0:27:7e:12:83

How to mirror root file system on x86 system

2011-01-24T23:44:00.000-08:00

You can mirror root disk with Solaris Volume manager. This is useful to protect your root file system. Root file system (/) is a critical file system that need to be cared well. For eample you have a root disk with partition 0 is belong to root (/) file system. You can mirror this root disk to other disk with following steps:

Check your root file system is mounted from your root disk. In this example you use c0d0s0 as your root filesystem.
bash-3.00# df -k /

Filesystem size used avail capacity Mounted on

/dev/dsk/c0d0s0 14G 8.9G 5.4G 63% /

Make the disk that will be used as second submirror tobe bootable.
bash-3.00# fdisk -b /usr/lib/fs/ufs/mboot -n /dev/rdsk/c1d0s0
bash-3.00# /sbin/installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1d0s0
Create 2 metadevices that you will use as submirror. In this example you create d11 and d12.
bash-3.00# metainit -f d11 1 1 c0d0s0

d11: Concat/Stripe is setup

bash-3.00# metainit d12 1 1 c1d0s0

d12: Concat/Stripe is setup

Create the mirror. In this example you create mirror d1 use metadevice d11 as submirror
bash-3.00# metainit d1 -m d11

d1: Mirror is setup

Backup the affected file. Then set your mirror device d1 as your root filesystem. Check also that your root file system is now mounted from the mirror.
bash-3.00# cp /etc/system /etc/system.bck

bash-3.00# cp /etc/vfstab /etc/vfstab.bck

bash-3.00# metaroot d1

bash-3.00# more /etc/vfstab

#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options

/dev/md/dsk/d1 /dev/md/rdsk/d1 / ufs 1 no -

Reboot your system. Synchronize file systems before you reboot.
bash-3.00# lockfs -a
bash-3.00# init 6
Verify that your system now using mirror d1 as root filesystem.
bash-3.00# df -h /

Filesystem size used avail capacity Mounted on

/dev/md/dsk/d1 14G 8.9G 5.4G 63% /

Attach the second submirror d12 to the mirror.
bash-3.00# metattach d1 d12

d1: submirror d12 is attached

Check your mirror. Now it is resyncing

bash-3.00# metastat

d1: Mirror

Submirror 0: d11

State: Okay

Submirror 1: d12

State: Resyncing

Resync in progress: 4 % done

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 30732345 blocks (14 GB)

d11: Submirror of d1

State: Okay

Size: 30732345 blocks (14 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c0d0s0 0 No Okay Yes

d12: Submirror of d1

State: Resyncing

Size: 31391010 blocks (14 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c1d0s0 0 No Okay Yes

Device Relocation Information:

Device Reloc Device ID

c1d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB238eb2cf-1b6348b6

c0d0 Yes id1,cmdk@AVBOX_HARDDISK=VBceae357c-d2e0a4a0

Edit GRUB entries to include the second submirror as boot device
bash-3.00# vi /boot/grub/menu.lst

....

title alternate boot

root (hd1,0,a)

kernel /boot/multiboot

module /boot/x86.miniroot-safe

How to mirror root file system on SPARC system

2011-01-19T02:10:00.000-08:00

Check your root file system is mounted from your root disk. In this example you use c0t0d0s0 as your root filesystem.
bash-3.00# df -k /

Filesystem size used avail capacity Mounted on

/dev/dsk/c0t0d0s0 14G 8.9G 5.4G 63% /

Create 2 metadevices that you will use as submirror. In this example you create d11 and d12.
bash-3.00# metainit -f d11 1 1 c0t0d0s0

d11: Concat/Stripe is setup

bash-3.00# metainit d12 1 1 c3t4d0s0

d12: Concat/Stripe is setup

Create the mirror. In this example you create mirror d1 use metadevice d11 as submirror
bash-3.00# metainit d1 -m d11

d1: Mirror is setup

Backup the affected file. Then set your mirror device d1 as your root filesystem. Check also that your root file system is now mounted from the mirror.
bash-3.00# cp /etc/system /etc/system.bck

bash-3.00# cp /etc/vfstab /etc/vfstab.bck

bash-3.00# metaroot d1

bash-3.00# more /etc/vfstab

#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options

/dev/md/dsk/d1 /dev/md/rdsk/d1 / ufs 1 no -

Reboot your system. Synchronize file systems before you reboot.
bash-3.00# lockfs -a
bash-3.00# init 6
Verify that your system now using mirror d1 as root filesystem.
bash-3.00# df -h /

Filesystem size used avail capacity Mounted on

/dev/md/dsk/d1 14G 8.9G 5.4G 63% /

Attach the second submirror d12 to the mirror.
bash-3.00# metattach d1 d12

d1: submirror d12 is attached

Check your mirror. Now it is resyncing

bash-3.00# metastat

d1: Mirror

Submirror 0: d11

State: Okay

Submirror 1: d12

State: Resyncing

Resync in progress: 4 % done

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 30732345 blocks (14 GB)

d11: Submirror of d1

State: Okay

Size: 30732345 blocks (14 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c0t0d0s0 0 No Okay Yes

d12: Submirror of d1

State: Resyncing

Size: 31391010 blocks (14 GB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c3t4d0s0 0 No Okay Yes

Device Relocation Information:

Device Reloc Device ID

c3t4d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB238eb2cf-1b6348b6

c0t0d0 Yes id1,cmdk@AVBOX_HARDDISK=VBceae357c-d2e0a4a0

Determine the path of second submirror, then enter OK prompt
bash-3.00# ls -l /dev/dsk/c3t4d0s0

lrwxrwxrwx 1 root root 57 Oct 25 11:22 /dev/dsk/c3t4d0s0 -

> ../../devices/pci@1f,0/pci@1/pci@1/SUNW,isptwo@4/sd@4,0:a

bash-3.00# init 0

Make the second submirror bootable.
ok nvalias mirror_disk /pci@1f,0/pci@1/pci@1/SUNW,isptwo@4/sd@4,0:a
Make alias for the second submirror. So you can boot from the second sub mirror.
ok printenv boot-device

boot-device= disk net

ok setenv boot-device disk mirror_disk net

boot-device= disk mirror_disk net

(Optional) after resyncing process on step 8 is done, you can try to boot from the second submirror.
ok boot mirror_disk

How to create mirror

2011-01-16T23:56:00.000-08:00

You can mirror two disk partition with Solaris Volume manager. Steps for do mirror is very simple like below.

Create metadevice that you will use for build mirror. In this example you create d11 and d12
bash-3.00# metainit d11 1 1 c3t2d0s0

d11: Concat/Stripe is setup

bash-3.00# metainit d12 1 1 c3t3d0s0

d12: Concat/Stripe is setup

Create the mirror. In this example you create mirror d1 use metadevice d11 as sub mirror
bash-3.00# metainit d1 -m d11

d1: Mirror is setup

Attach the other submirror. In this example you use d12 as the other submirrror
bash-3.00# metattach d1 d12

d1: submirror d12 is attached

Check the mirror configuration

bash-3.00# metastat

d1: Mirror

Submirror 0: d11

State: Okay

Submirror 1: d12

State: Resyncing

Resync in progress: 2 % done

Pass: 1

Read option: roundrobin (default)

Write option: parallel (default)

Size: 2048000 blocks (1000 MB)

d11: Submirror of d1

State: Okay

Size: 2048000 blocks (1000 MB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c3t2d0s0 0 No Okay Yes

d12: Submirror of d1

State: Resyncing

Size: 2048000 blocks (1000 MB)

Stripe 0:

Device Start Block Dbase State Reloc Hot Spare

c3t3d0s0 0 No Okay Yes

Device Relocation Information:

Device Reloc Device ID

c3t3d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB5c17d304-00de27e4

c3t2d0 Yes id1,sd@SATA_____VBOX_HARDDISK____VB08da0d81-38b71174

Create file system on the mirror
bash-3.00# newfs /dev/md/rdsk/d1

/dev/md/rdsk/d1: Unable to find Media type. Proceeding with system determined parameters.

newfs: construct a new file system /dev/md/rdsk/d1: (y/n)? y

/dev/md/rdsk/d1: 2048000 sectors in 1000 cylinders of 64 tracks, 32 sectors

1000.0MB in 63 cyl groups (16 c/g, 16.00MB/g, 7680 i/g)

super-block backups (for fsck -F ufs -o b=#) at:

32, 32832, 65632, 98432, 131232, 164032, 196832, 229632, 262432, 295232,

1738432, 1771232, 1804032, 1836832, 1869632, 1902432, 1935232, 1968032,

2000832, 2033632

Check new file system that you just have created
bash-3.00# fsck /dev/md/rdsk/d1

** /dev/md/rdsk/d1

** Last Mounted on

** Phase 1 - Check Blocks and Sizes

** Phase 2 - Check Pathnames

** Phase 3a - Check Connectivity

** Phase 3b - Verify Shadows/ACLs

** Phase 4 - Check Reference Counts

** Phase 5 - Check Cylinder Groups

2 files, 9 used, 962486 free (14 frags, 120309 blocks, 0.0% fragmentation)

Mount the file system
bash-3.00# mount /dev/md/dsk/d10 /sample

bash-3.00# df -k

Filesystem kbytes used avail capacity Mounted on

/dev/dsk/c0d0s0 15133279 9349803 5632144 63% /

/devices 0 0 0 0% /devices

ctfs 0 0 0 0% /system/contract

proc 0 0 0 0% /proc

mnttab 0 0 0 0% /etc/mnttab

swap 2712956 936 2712020 1% /etc/svc/volatile

objfs 0 0 0 0% /system/object

sharefs 0 0 0 0% /etc/dfs/sharetab

/usr/lib/libc/libc_hwcap1.so.1

15133279 9349803 5632144 63% /lib/libc.so.1

fd 0 0 0 0% /dev/fd

swap 2712056 36 2712020 1% /tmp

swap 2712048 28 2712020 1% /var/run

/dev/dsk/c0d1s0 10275725 7438965 2734003 74% /u01

/dev/dsk/c3t0d0s0 5153886 223930 4878418 5% /disk01

/dev/dsk/c3t1d0s0 5153886 678049 4424299 14% /disk02

/dev/dsk/c0d0s7 3448584 3441 3410658 1% /export/home

/dev/md/dsk/d1 962495 1041 903705 1% /sample

How to configure link aggregation

2011-01-13T19:21:00.000-08:00

Link aggregation is used because increased demand for network bandwith. It specifies how two or more ethernet connection can be linked to share load and increase reliability. With link aggregation we can increase bandwith, increase reliability, and load balancing. Below is tips to configure link aggregation.

Display the link type.In this example non-vlan type indicates that they are supported GLDv3-based drivers and able to be aggregated. If type is legacy, the link can not be aggregated.
root@solaris-sunray # dladm show-link
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g0
e1000g2 type: non-vlan mtu: 1500 device: e1000g0
Determine link that available for an aggregation. It is better that you use link that has not been used. In this case e1000g1 and e1000g2 is available.

root@solaris-sunray # ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255

ether 8:0:27:7e:12:82

Display link status, speed and duplex property.
root@solaris-sunray # dladm show-dev
e1000g0 link: up speed: 1000 Mbps duplex: full
e1000g1 link: down speed: 1000 Mbps duplex: unknown
e1000g2 link: down speed: 1000 Mbps duplex: unknown
Create an aggregation link that consist of e1000g1 and e1000g2 with identification key 1.
root@solaris-sunray # dladm create-aggr -d e1000g1 -d e1000g2 1
root@solaris-sunray # dladm show-link
e1000g0 type: non-vlan mtu: 1500 device: e1000g0
e1000g1 type: non-vlan mtu: 1500 device: e1000g0
e1000g2 type: non-vlan mtu: 1500 device: e1000g0
aggr1 type: non-vlan mtu: 1500 aggregation: key 1
Configure and set IP address of new link aggregation.
root@solaris-sunray # ifconfig aggr1 plumb 192.168.1.10 netmask 255.255.255.0 broadcast 192.169.1.255 up

root@solaris-sunray # ifconfig -a

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255

ether 8:0:27:7e:12:82

aggr1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5 inet 192.168.1.10 netmask ffffff00 broadcast 192.168.1.255

Make your link aggregation is presistent across reboot.

root@solaris-sunray # vi /etc/hostname.aggr1

192.168.1.10

How to configure IPv6 address in Solaris

2011-01-12T21:26:00.000-08:00

Ipv4 use 32 bits, whereas IPv6 uses 128 bits. Ipv6 have autoconfiguration capability,so it is no more difficult to administer IPv6 addressing than it is with IPv4. You can use below procedure to configure IPv6 address. In this example you configure one network interface (e1000g) to use Ipv6.

Create /etc/hostname6.<interface> file and reboot. This will make interface to configure with Ipv6.

root@solaris-sunray # touch /etc/hostname6.e1000g0

Configure Ipv6 address.
root@solaris-sunray # ifconfig e1000g0 inet6 plumb up
View your Ipv6 address.
root@solaris-sunray # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255
ether 8:0:27:7e:12:82
e1000g0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::a00:27ff:fe7e:1282/10
ether 8:0:27:7e:12:82
Edit your /etc/inet/ipnodes to contain your Ipv6 address. And test your new ipaddress.
root@solaris-sunray # vi /etc/inet/ipnodes
...
fe80::a00:27ff:fe7e:1282 solaris-sunray6
root@solaris-sunray # ping solaris-sunray6
solaris-sunray6 is alive

How to work with NIS no server available error

2011-01-12T00:15:00.001-08:00

Sometimes NIS client can not communicate with NIS master server or NIS slave servers. NIS client show message “No server available”. Below is tips to work with this problem.

Check network connection between NIS client and NIS servers.
Check /var/yp/binding/domainname/ypservers. This file should contain lists of NIS servers. If no NIS servers listed, type ypinit -c command to list your NIS server again.
# ypinit -c
Check that NIS servers listed on /var/yp/binding/domainname/ypservers are operational or not. You may add new NIS server.
Check that NIS servers listed on ypservers file is also listed on /etc/hosts.

How to work with NIS daemon not running

2011-01-10T20:34:00.000-08:00

From NIS client, you can list the NIS servers with ypwhich command. Sometimes ypwhich command is not working. Below is tips to work with this issue.

From NIS client, kill ypwhich process.
# pkill ypwhich
Login as root user on NIS server and check if ypbind and ypserv daemon is running.
root@solaris-sunray # pgrep -fl yp
438 /usr/lib/netsvc/yp/rpc.yppasswdd -D /var/yp -m
132 /usr/lib/crypto/kcfd
443 /usr/lib/netsvc/yp/ypserv -d
433 /usr/lib/netsvc/yp/rpc.ypupdated
435 /usr/lib/netsvc/yp/ypxfrd
474 /usr/lib/netsvc/yp/ypbind
If ypbind or ypserv process is not running on step 2, you must stop and start NIS service.
root@solaris-sunray # svcadm disable network/nis/server:default

root@solaris-sunray # svcadm enable network/nis/server:default

If ypbind or ypserv process is running on step 2, ypserv process has probably hung. You must kill ypserv process and restart NIS service.
root@solaris-sunray # pkill ypserv
root@solaris-sunray # svcadm disable network/nis/server:default

root@solaris-sunray # svcadm enable network/nis/server:default

How to delegate dataset to non global zone

2011-01-10T00:29:00.000-08:00

You can delegate ZFS filesystem as dataset from global zone to non global zone. With this method, non global zone administrator can administer property of filesystem delegated. Tips to delegate dataset as below.

See ZFS file system on your host. In this example you will share mirrpool/fs1 filesystem.
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 168K 976M 18K /mirrpool
mirrpool/fs1 18K 976M 18K legacy
mirrpool/fs2 18K 976M 18K /mirrpool/fs2
Reconfigure the non global zone to include ZFS filesystem. In this example non global zone name is zone1.
bash-3.00# zonecfg -z zone1
zonecfg:zone1> add dataset
zonecfg:zone1:dataset> set name=mirrpool/fs2
zonecfg:zone1:dataset> end
zonecfg:zone1> exit
See the zoned property of your ZFS filesystem.
bash-3.00# zfs get -r zoned mirrpool
NAME PROPERTY VALUE SOURCE
mirrpool zoned off default
mirrpool/fs1 zoned off default
mirrpool/fs2 zoned off default
Reboot the non global zone.
bash-3.00# zoneadm -z zone1 reboot
zoneadm: zone 'zone1': WARNING: The zone.cpu-shares rctl is set but
zoneadm: zone 'zone1': FSS is not the default scheduling class for
zoneadm: zone 'zone1': this zone. FSS will be used for processes
zoneadm: zone 'zone1': in the zone but to get the full benefit of FSS,
zoneadm: zone 'zone1': it should be the default scheduling class.
zoneadm: zone 'zone1': See dispadmin(1M) for more details.
zoneadm: zone 'zone1': WARNING: e1000g0:1: no matching subnet found in netmasks(4) for 172.16.31.150; using default of 255.255.0.0.
Login to the non global zone and see the ZFS filesystem that shared from global zone.
bash-3.00# zlogin zone1
[Connected to zone 'zone1' pts/5]
Last login: Tue Nov 2 15:22:28 on pts/5
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
# df -h mirrpool/fs2
Filesystem size used avail capacity Mounted on
mirrpool/fs2 976M 18K 976M 1% /mirrpool/fs2
Remember that non global zone administrator can administer the file system. List the ZFS filesystem.
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 168K 976M 18K /mirrpool
mirrpool/fs2 18K 976M 18K /mirrpool/fs2
Return to the global zone and see the zoned property of filesystem that you have delegated to non global zone.
bash-3.00# zfs get -r zoned mirrpool
NAME PROPERTY VALUE SOURCE
mirrpool zoned off default
mirrpool/fs1 zoned off default
mirrpool/fs2 zoned on local

How to create ZFS file system

2011-01-07T06:54:00.000-08:00

You must have zpool (ZFS pool) before you work with ZFS file system. When you create zpool, you also automatically create ZFS file system. Below is tips to about ZFS filesystem.

See ZFS file system on your host.
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 106K 976M 18K /mirrpool
Create a new filesystem under /mirrpool. In this example you create a new file system named fs1.
bash-3.00# zfs create mirrpool/fs1
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 130K 976M 18K /mirrpool
mirrpool/fs1 18K 976M 18K /mirrpool/fs1
See that your new file system is mounted.
bash-3.00# mount
...
/mirrpool on mirrpool read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=2d50004 on Tue Nov 2 11:41:14 2010
/mirrpool/fs1 on mirrpool/fs1 read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=2d50005 on Tue Nov 2 11:54:00 2010
Try to create a new file on there. See you do not need to use newfs command as previous UFS.
bash-3.00# touch /mirrpool/fs1/data1
bash-3.00# ls -al /mirrpool/fs1/
total 7
drwxr-xr-x 2 root root 3 Nov 2 11:54 .
drwxr-xr-x 3 root root 3 Nov 2 11:54 ..
-rw-r--r-- 1 root root 0 Nov 2 11:54 data1
See all properties of new file system.
bash-3.00# zfs get all mirrpool/fs1
NAME PROPERTY VALUE SOURCE
mirrpool/fs1 type filesystem -
mirrpool/fs1 creation Tue Nov 2 11:54 2010 -
mirrpool/fs1 used 18K -
mirrpool/fs1 available 976M -
mirrpool/fs1 referenced 18K -
mirrpool/fs1 compressratio 1.00x -
mirrpool/fs1 mounted yes -
mirrpool/fs1 quota none default
mirrpool/fs1 reservation none default
mirrpool/fs1 recordsize 128K default
mirrpool/fs1 mountpoint /mirrpool/fs1 default
mirrpool/fs1 sharenfs off default
mirrpool/fs1 checksum on default
mirrpool/fs1 compression off default
mirrpool/fs1 atime on default
mirrpool/fs1 devices on default
mirrpool/fs1 exec on default
mirrpool/fs1 setuid on default
mirrpool/fs1 readonly off default
mirrpool/fs1 zoned off default
mirrpool/fs1 snapdir hidden default
mirrpool/fs1 aclmode groupmask default
mirrpool/fs1 aclinherit restricted default
mirrpool/fs1 canmount on default
mirrpool/fs1 shareiscsi off default
mirrpool/fs1 xattr on default
mirrpool/fs1 copies 1 default
mirrpool/fs1 version 3 -
mirrpool/fs1 utf8only off -
mirrpool/fs1 normalization none -
mirrpool/fs1 casesensitivity sensitive -
mirrpool/fs1 vscan off default
mirrpool/fs1 nbmand off default
mirrpool/fs1 sharesmb off default
mirrpool/fs1 refquota none default
mirrpool/fs1 refreservation none default

How to create ZFS storage pool

2011-01-06T02:31:00.000-08:00

ZFS is file system that implemented on solaris 10 6/06 or later release. To use this file system you should create ZFS pool first. ZFS pool can be a single disk (non redundant), mirrored disk, raid 5 or raid 6 disk. Below is tips to create mirrored Zpool (ZFS pool).

See that the are no existing ZFS pool
bash-3.00# zpool list
no pools available
List the disk that you want to use as a pool. In this example you will use 2 available disks c3t2d0 and c3t3d0 as a mirrored pool.
bash-3.00# df -F ufs -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0d0s0 14G 8.9G 5.4G 63% /
/dev/dsk/c0d0s7 3.3G 3.4M 3.3G 1% /export/home
/dev/dsk/c0d1s0 9.8G 7.1G 2.6G 74% /u01
/dev/dsk/c3t0d0s0 4.9G 219M 4.7G 5% /disk01
/dev/dsk/c3t1d0s0 4.9G 662M 4.2G 14% /disk02
bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0
1. c0d1 <DEFAULT cyl 1302 alt 2 hd 255 sec 63>
/pci@0,0/pci-ide@1,1/ide@0/cmdk@1,0
2. c3t0d0 <DEFAULT cyl 2556 alt 2 hd 128 sec 32>
/pci@0,0/pci8086,2829@d/disk@0,0
3. c3t1d0 <DEFAULT cyl 2556 alt 2 hd 128 sec 32>
/pci@0,0/pci8086,2829@d/disk@1,0
4. c3t2d0 <DEFAULT cyl 1020 alt 2 hd 64 sec 32>
/pci@0,0/pci8086,2829@d/disk@2,0
5. c3t3d0 <DEFAULT cyl 1020 alt 2 hd 64 sec 32>
/pci@0,0/pci8086,2829@d/disk@3,0
Specify disk (enter its number): ^C
Create the mirrored pool with 2 disks. This pool name is mirrpool.
bash-3.00# zpool create mirrpool mirror c3t2d0 c3t3d0
bash-3.00# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
mirrpool 1008M 94K 1008M 0% ONLINE -
Check condition of the pool
bash-3.00# zpool status
pool: mirrpool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
mirrpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c3t2d0 ONLINE 0 0 0
c3t3d0 ONLINE 0 0 0
errors: No known data errors

How to work with ZFS snapshot and clone

2011-01-05T03:04:00.000-08:00

ZFS clone is a clone from zfs filesystem whose intial contents are the same with the filesystem from which it was created. Clones can only be created from snapshot. Below is tips to create sanpshot from ZFS filesystem and then create clone.

See ZFS file system on your host.
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 132K 976M 19K /mirrpool
mirrpool/fs1 18K 976M 18K /mirrpool/fs1
See the content of your file system.
bash-3.00# ls -al /mirrpool/fs1
total 7
drwxr-xr-x 2 root root 3 Nov 2 11:54 .
drwxr-xr-x 3 root root 3 Nov 2 11:54 ..
-rw-r--r-- 1 root root 0 Nov 2 11:54 data1
Create a snapshot from your filesystem. In this example you create snapshot from mirrpool/fs1.
bash-3.00# zfs snapshot mirrpool/fs1@today
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
mirrpool 133K 976M 19K /mirrpool
mirrpool/fs1 18K 976M 18K /mirrpool/fs1
mirrpool/fs1@today 0 - 18K -
See that your snapshot also contain same data with your original filesystem (step 2).
bash-3.00# ls -al /mirrpool/fs1/.zfs/snapshot/today
total 4
drwxr-xr-x 2 root root 3 Nov 2 11:54 .
dr-xr-xr-x 3 root root 3 Nov 2 11:54 ..
-rw-r--r-- 1 root root 0 Nov 2 11:54 data1
Create clone from the snapshot. In this example you create a clone named mirrpool/fs2. Initial content of clone is same with the original file system.
bash-3.00# ls -al /mirrpool/fs2
total 7
drwxr-xr-x 2 root root 3 Nov 2 11:54 .
drwxr-xr-x 4 root root 4 Nov 2 13:44 ..
-rw-r--r-- 1 root root 0 Nov 2 11:54 data1
See that origin from the clone is the snapshot.
bash-3.00# zfs get -r origin mirrpool
NAME PROPERTY VALUE SOURCE
mirrpool origin - -
mirrpool/fs1 origin - -
mirrpool/fs1@today origin - -
mirrpool/fs2 origin mirrpool/fs1@today -

How to display user without password

2011-01-04T00:40:00.000-08:00

You can monitor user who login to your system without password with following tips. This will be usefull to increase your system security.

Become super user on your host
root@solaris-sunray #
Show user login without password with logins command.
root@solaris-sunray # logins -p
Andy 501 other 1 Andy Bob
See that user Andy login without password. You can tell this user to create a new password.

How to configure NIS slave server

2011-01-03T00:02:00.000-08:00

You can use tips below to configure host as NIS slave server. You should have at least one NIS slave server as backup in case NIS master server become unavailable.

Modify your /etc/inet/hosts file to include IP address – hostname of NIS master, all NIS slave servers and NIS clients.
Set NIS domain on your host.
# vi /etc/defaultdomain
sun.com
# domainname sun.com
Initialize your system as NIS client. When system prompts for list of NIS servers, enter the name of NIS master server and all NIS slave servers.
# ypinit -c
Modify your /etc/nsswitch.conf to contain NIS. For instance, copy from /etc/nsswitch.nis file
# cp /etc/nsswitch.nis /etc/nsswitch.conf
Make sure ypserv process is running on NIS master server. If it is not running, run the NIS service on your NIS master server.
# pgrep -fl ypserv
# svcadm enable svc:/network/nis/server:default (optional if ypserv is not running)
Note : Remember to work this step 5 in NIS master server, not on NIS slave server
Return to your NIS slave server and start your NIS client service
# svcadm enable svc:/network/nis/client:default
Initialize your system as NIS slave servers that will refer to NIS master server. In this example your NIS master server hostname is jupiter. This command also pull and get all NIS map from NIS master server. So your NIS slave server maps is updated with the current NIS master server maps.
# ypinit -s jupiter
Stop your NIS client service
# svcadm disable svc:/network/nis/client:default
Start your NIS slave server service
# svcadm enable svc:/network/nis/server:default
Test your NIS client functionality. List NIS maps and NIS server for each map.
# ypwhich -m

How to configure NIS master server

2010-12-30T02:08:00.000-08:00

You can use below tips to configure host as NIS master server. Remember that you can only have one master server in your domain. This master server contain original ASCII file that used to create NIS map. It also will propagate NIS map to all slave server.

Create /var/yp/securenets file on your NIS master server. This file will restrict which host can access NIS service that provided by this master server. In this example NIS service can be accessed by NIS master server itself, all hosts in 192.168.1.2/24, and host with IP address 10.10.10.1
# vi /var/yp/securenets
host 127.0.0.1

255.255.255.0 192.168.1.2

host 10.10.10.1

Set NIS domain on your host.
# vi /etc/defaultdomain

sun.com

# domainname sun.com

Build NIS maps.
Your NIS maps need at least 3 kind of files, ex: /etc/passwd, /etc/group and /etc/hosts. Collect that 3 kind of files from all hosts that have same domain with NIS server.
Make a new passwd file that contain all records from all passwd file you have collected. Delete all root record from your new passwd file. Store this new passwd file on /var/yp, this new passwd file will be used as passwd map.
Make a new group file and hosts file too that contain all records from all group and hosts file you have collected. Store this new group and hosts file on /var/yp, this new group and hosts file will be used as group map and hosts map.
For security collect also /etc/shadow from all hosts in the same domain. Create file passwd.adjunct that combine all record from /etc/shadow. Delete all root record from your passwd.adjunct file.
Put passwd.adjunct file in /var/yp/security, then edit your /var/yp/Makefile in section all to include passwd.adjunct (see step 4)
You also can optionally collect and combine the other /etc files, ex : /etc/timezone, /etc/netgroup, /etc/ethers, /etc/bootparams, /etc/netmasks and many more. You can see all /etc files that can be configured by see section all in /var/yp/Makefile
# vi /etc/defaultdomain
...
all: passwd group hosts ipnodes ethers networks rpc services protocols
netgroup bootparams aliases publickey netid netmasks c2secure
timezone auto.master auto.home ageing
auth.attr exec.attr prof.attr user.attr audit.user passwd.adjunct
...
Edit file /var/yp/Makefile.
Assign DIR, PWDIR, INETDIR parameter to /var/yp
Modify your /etc/inet/hosts file to include IP address – hostname of all NIS slave servers and NIS clients
Initialize your system as NIS master server. When system prompts for list of NIS slave servers, enter the name of all NIS slave servers.
# ypinit -m
Modify your /etc/nsswitch.conf to contain NIS. For instance, copy from /etc/nsswitch.nis file
# cp /etc/nsswitch.nis /etc/nsswitch.conf
Start your NIS master server service and test your NIS
# svcadm enable svc:/network/nis/server:default
# ypcat passwd

How to configure NIS client

2010-12-28T20:20:00.000-08:00

You can use tips below to configure host as NIS client. In this example you already have NIS master server and NIS slave server. You only can have 1 NIS master server, but can have several NIS slave server.

Modify your /etc/inet/hosts file to include IP address – hostname of NIS master server and NIS slave servers.
Set NIS domain on your host.
# vi /etc/defaultdomain

sun.com

# domainname sun.com

Initialize your system as NIS client. When system prompts for list of NIS servers, enter the name of NIS master server and all NIS slave servers.
# ypinit -c
Modify your /etc/nsswitch.conf to contain NIS. For instance, copy from /etc/nsswitch.nis file
# cp /etc/nsswitch.nis /etc/nsswitch.conf
Start your NIS client service
# svcadm enable svc:/network/nis/client:default
Test your NIS client functionality. List NIS maps and NIS server for each map.
# ypwhich -m

How to configure IP address

2010-12-28T02:59:00.000-08:00

You can use basic simple tips below to configure your host IP address. In this example you set an intel network interface (e1000g) IP address to 172.16.31.242 with subnet 255.255.252.0

Modify /etc/inet/hosts and /etc/inet/ipnodes and insert following record.
172.16.31.242 solaris-sunray
Modify /etc/hostname.e1000g0 and input hostname
solaris-sunray
Modify /etc/inet/netmasks and input netwrok address and netmask address.
172.16.28.0 255.255.252.0
Set the IP address
root@solaris-sunray # ifconfig e1000g0 solaris-sunray netmask + broadcast + up

root@solaris-sunray # ifconfig -a

lo0:
flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232

index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

inet 172.16.31.242 netmask fffffc00 broadcast 172.16.31.255

ether 8:0:27:7e:12:82

How to configure DNS client

2010-12-27T05:33:00.002-08:00

You can use below procedure to configure host as DNS client. In this example you already have DNS server

Modify your /etc/nsswitch.conf file to include DNS. For instance, you can copy from /etc/nsswitch.dns
root@solaris-sunray # cp /etc/nsswitch.dns /etc/nsswitch.conf
Modify your /etc/resolv.conf to include IP address of your DNS server. In this example, your DNS server IP address is 172.16.20.249
root@solaris-sunray # vi /etc/resolv.conf

nameserver 172.16.20.249

domain sun.com

search sun.com

Make sure that your DNS client service is running.
root@solaris-sunray # svcadm enable svc:/network/dns/client:default
Set your client domain name.
root@solaris-sunray # vi /etc/defaultdomain

sun.com

# domainname sun.com

Test your DNS client configuration. Look IP address of server pool.ntp.org
root@solaris-sunray # nslookup pool.ntp.org
Server: 172.16.20.249
Address: 172.16.20.249#53
Non-authoritative answer:
Name: pool.ntp.org
Address: 202.134.6.170
Name: pool.ntp.org
Address: 152.118.24.8
root@solaris-sunray # dig pool.ntp.org
; <<>> DiG 9.3.4-P1 <<>> pool.ntp.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1371
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 9, ADDITIONAL: 12
;; QUESTION SECTION:
;pool.ntp.org. IN A
;; ANSWER SECTION:
pool.ntp.org. 270 IN A 152.118.24.8
pool.ntp.org. 270 IN A 202.134.6.170
;; AUTHORITY SECTION:
pool.ntp.org. 3122 IN NS d.ntpns.org.
pool.ntp.org. 3122 IN NS e.ntpns.org.
pool.ntp.org. 3122 IN NS f.ntpns.org.
pool.ntp.org. 3122 IN NS g.ntpns.org.
pool.ntp.org. 3122 IN NS h.ntpns.org.
pool.ntp.org. 3122 IN NS i.ntpns.org.
pool.ntp.org. 3122 IN NS a.ntpns.org.
pool.ntp.org. 3122 IN NS b.ntpns.org.
pool.ntp.org. 3122 IN NS c.ntpns.org.
;; ADDITIONAL SECTION:
a.ntpns.org. 16553 IN A 207.171.17.42
b.ntpns.org. 6723 IN A 207.171.7.84
c.ntpns.org. 16553 IN A 212.200.82.148
d.ntpns.org. 16553 IN A 94.23.191.112
e.ntpns.org. 16553 IN A 70.85.157.108
f.ntpns.org. 16553 IN A 202.191.108.134
g.ntpns.org. 16553 IN A 78.153.203.28
h.ntpns.org. 16553 IN A 64.142.113.8
h.ntpns.org. 16553 IN A 85.214.25.217
h.ntpns.org. 16553 IN A 212.12.50.229
i.ntpns.org. 16553 IN A 141.89.226.53
i.ntpns.org. 16553 IN AAAA 2001:638:807:201:215:5dff:fee2:700c
;; Query time: 261 msec
;; SERVER: 172.16.20.249#53(172.16.20.249)
;; WHEN: Thu Nov 11 16:09:54 2010
;; MSG SIZE rcvd: 416