TECH.kulish.com

# format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c1t1d0
/pci@1,0/pci103c,60b0@5/sd@1,0
1. c1t4d0
/pci@1,0/pci103c,60b0@5/sd@4,0

bash-3.00# prtvtoc /dev/rdsk/c1t1d0s2 | fmthard -s – /dev/rdsk/c1t4d0s2
fmthard: New volume table of contents now in place.

bash-3.00# metadb -a -f -c2 /dev/dsk/c1t1d0s7 /dev/dsk/c1t4d0s7

/dev/dsk/c1t1d0s1 – - swap – no -
/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 / ufs 1
no -
/dev/dsk/c1t1d0s3 /dev/rdsk/c1t1d0s3 /var ufs 1
no -
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /export ufs 2
yes

bash-3.00# metainit -f d10 1 1 c1t1d0s0
d10: Concat/Stripe is setup
bash-3.00# metainit d20 1 1 c1t4d0s0
d20: Concat/Stripe is setup
bash-3.00# metainit d30 -m d10
d30: Mirror is setup

bash-3.00# zoneadm list -iv
ID NAME STATUS PATH
0 global running /
11 foo running /export/zones/foo
13 bar running /export/zones/bar
bash-3.00# zonecfg -z fubar
fubar: No such zone configured
Use ‘create’ to begin configuring a new zone.

zonecfg:fubar> create
zonecfg:fubar> set zonepath=/export/zones/fubar
zonecfg:fubar> set autoboot=true
zonecfg:fubar> add net
zonecfg:fubar:net> set physical=eth0
zonecfg:fubar:net> set address=192.168.1.1
zonecfg:fubar:net> end
zonecfg:fubar> add attr
zonecfg:fubar:attr> set name=comment
zonecfg:fubar:attr> set type=string
zonecfg:fubar:attr> set value=”FOOBED”
zonecfg:fubar:attr> end
zonecfg:fubar> verify
zonecfg:fubar> commit
zonecfg:fubar> exit

bash-3.00# zoneadm -z fubar install

This is the first part in a series of notes taken regarding new(ish) Solaris 10 technologies. Other items I have notes on are ZFS and new service administration.

Zones, Containers, Domains and Partition (According to Sun):

Zone: chroot’d virtual machine. Some resources are shared, for example, the kernel or /usr/lib.
More info below.

Container: Zone with resource controls in place. At this time, limited to number of CPUs.
See “Resource Pools”

Domain: Grouping of hardware in enterprise class Sun servers

Partition: Segregation of domain grouped hardware.

Some items concerning Solaris 10.

Zone: chrooted “virtual” machine. Kernel is a shared resource.
Domain: Grouping of hardware in larger sun servers.
Partition: Separation of domains.
Container: Zone with resource controls in place.

/etc/zones contains data on all zones.

ipmp auto nic failover. Both must be in same subnet.

core: application failure
panic: kernel failure

pool stuff (page 2-34):
pools contain sets (dynamic processor sets)
dynamic resource pool: limit resources in a zone
poolcfg -dc info get info on pools
pooladm -e save active pool config /etc/pooladm.conf
pooladm -x removes all user configured pools

Quick step-by-step for when I am forgetting things:

hostname:root> cfgmgr
Discover disks

hostname:root> lspv
Note whether SAN is HDLM (Hitachi) or VPATH (Shark)
Note hdisk# or vpath#
Should also report disks, in VGs and otherwise

hostname:root> lsvg -l VGname
Note which VG a filesystem is in

hostname:root> smitty lvm
>> Volume Groups
>> Add a Data Path Volume to a Volume Group (Shark)
>> Force the creation of a volume group? no (Leave Default)
>> * VOLUME GROUP name (F4 to list volume groups)
>> * PHYSICAL VOLUME names (F4 to list available volumes)