Stopping Ops Center 12c
# /opt/SUNWxvmoc/bin/proxyadm stop -wv
# /opt/SUNWxvmoc/bin/satadm stop -wv
Starting Ops Center 12c
# /opt/SUNWxvmoc/bin/satadm start -wv
# /opt/SUNWxvmoc/bin/proxyadm start -wv
Thursday, June 21, 2012
Installing IDR on solaris 11
Installing IDR on solaris 11 is different from Solaris 10 (patches). They called it idr (interim diagnostic relief) indentifier on Solaris 11
Following example, I am installing idr111 on Solaris 11 server
# pkgrepo create /var/tmp/idrrepo
# cd /var/tmp
# pkgrecv -s ./idr111p5p -d /var/tmp/idrrepo '*'
# pkg set-publisher -g file:///var/tmp/idrrepo solaris
# pkg publisher ( To verify that publisher is available)
solaris (non-sticky) origin online file:///var/tmp/idrrepo/
Install the idr using following command:
# pkg install idr111
Verify the package is installed by
# pkg verify -v idr111
PACKAGE STATUS
pkg://solaris/idr111 OK
Following example, I am installing idr111 on Solaris 11 server
# pkgrepo create /var/tmp/idrrepo
# cd /var/tmp
# pkgrecv -s ./idr111p5p -d /var/tmp/idrrepo '*'
# pkg set-publisher -g file:///var/tmp/idrrepo solaris
# pkg publisher ( To verify that publisher is available)
solaris (non-sticky) origin online file:///var/tmp/idrrepo/
Install the idr using following command:
# pkg install idr111
Verify the package is installed by
# pkg verify -v idr111
PACKAGE STATUS
pkg://solaris/idr111 OK
Wednesday, June 20, 2012
Error while luactivate
/usr/sbin/luactivate: /etc/lu/DelayUpdate/: cannot create
Workaround:
execute folloing:
# export BOOT_MENU_FILE="menu.lst"
Workaround:
execute folloing:
# export BOOT_MENU_FILE="menu.lst"
Debugging issues on Solaris using truss
In original ksh terminal, find out the PID of the ksh shell:
# ps
On 2nd terminal:
# truss -faeldo locale.truss -vall -r0 -w 1,2 -p (PID of ksh shell)
In original ksh terminal:
Execute the command which is having issues
On 2nd terminal:
Tail the locale.truss or read the contents for more details
# ps
On 2nd terminal:
# truss -faeldo locale.truss -vall -r0 -w 1,2 -p (PID of ksh shell)
In original ksh terminal:
Execute the command which is having issues
On 2nd terminal:
Tail the locale.truss or read the contents for more details
Tuesday, April 10, 2012
Modules of Cloud
There are basically three service modules in the cloud computing:
1) SaaS -> Software as a Service, Providers will provide the client with a complete software application environment, including management and the user interface. Clients usually have access to the environment through a thin user interface such as browser, which enables data entry and manages user interactions. Provider must manage everything else, from the infrastructure to the architecture.
2) PaaS -> Platform as a Service, provides clients with the complete development environment incuding virtual machines . operating systems, applications, services. Clients can deploy their own applications programmed using PaaS-compatible languages and tools. With this model, the service provider is responsible for managing cloud infrastructure and the operating systems, and client develop, install and manage the applications they want to deploy.
3) IaaS-> Infrastructure as a Service provides hardware assets to clients, who can then provision themm. Example of these hardware assets are virtual computing systems, storage resources.Clients are responsible for deploying and managing all the other aspects of the infrastructure including Opeations sytstem, application and user interactions with the systems.
1) SaaS -> Software as a Service, Providers will provide the client with a complete software application environment, including management and the user interface. Clients usually have access to the environment through a thin user interface such as browser, which enables data entry and manages user interactions. Provider must manage everything else, from the infrastructure to the architecture.
2) PaaS -> Platform as a Service, provides clients with the complete development environment incuding virtual machines . operating systems, applications, services. Clients can deploy their own applications programmed using PaaS-compatible languages and tools. With this model, the service provider is responsible for managing cloud infrastructure and the operating systems, and client develop, install and manage the applications they want to deploy.
3) IaaS-> Infrastructure as a Service provides hardware assets to clients, who can then provision themm. Example of these hardware assets are virtual computing systems, storage resources.Clients are responsible for deploying and managing all the other aspects of the infrastructure including Opeations sytstem, application and user interactions with the systems.
Tuesday, February 28, 2012
Working on extents on Redhat LVM
If you want to create Logical volume using extents:
By default PE size for volume group is 4 MB.
PE Size 4.00 MiB
If you want to change it, you can use -s option when you are creating volume group
For example
# vgcreate -s 8 helloguruvg /dev/sdh
For now, i am using default value which is 4 MB.
I am creating Logical volume with 30 extents (which will be 30 x 4 MB size)
[root@kumar ~]# lvcreate -l 30 -n hellogurulg helloguruvg
Making ext4 filesystem:
[root@kumar ~]# mkfs.ext4 /dev/mapper/helloguruvg-hellogurulg
[root@kumar ~]# mkdir /hellogurufs
[root@kumar ~]# mount /dev/mapper/helloguruvg-hellogurulg /hellogurufs
[root@kumar ~]# df -h
/dev/mapper/helloguruvg-hellogurulg 117M 5.6M 105M 6% /hellogurufs
Edit the fstab to make it persistent
By default PE size for volume group is 4 MB.
PE Size 4.00 MiB
If you want to change it, you can use -s option when you are creating volume group
For example
# vgcreate -s 8 helloguruvg /dev/sdh
For now, i am using default value which is 4 MB.
I am creating Logical volume with 30 extents (which will be 30 x 4 MB size)
[root@kumar ~]# lvcreate -l 30 -n hellogurulg helloguruvg
Making ext4 filesystem:
[root@kumar ~]# mkfs.ext4 /dev/mapper/helloguruvg-hellogurulg
[root@kumar ~]# mkdir /hellogurufs
[root@kumar ~]# mount /dev/mapper/helloguruvg-hellogurulg /hellogurufs
[root@kumar ~]# df -h
/dev/mapper/helloguruvg-hellogurulg 117M 5.6M 105M 6% /hellogurufs
Edit the fstab to make it persistent
Adding SWAP on Redhat using LVM
Following steps to add swap using LVM with out creating new partition
1) Check if you have enough space in the volume group
[root@kumar ~]# vgs
VG #PV #LV #SN Attr VSize VFree
test1VG 1 4 0 wz--n- 1020.00m 36.00m
testingextentvg 1 1 0 wz--n- 104.00m 24.00m
vgexttest 1 1 0 wz--n- 96.00m 32.00m
Following command will create Logical volume swaphello with the size 10 MB
[root@kumar ~]# lvcreate -L 10M -n swaphello test1VG
[root@kumar ~]# mkswap /dev/mapper/test1VG-swaphello
[root@kumar ~]# swapon /dev/mapper/test1VG-swaphello
Add swap entry in the fstab so that it will be persistent
[root@kumar ~]# vi /etc/fstab
/dev/mapper/test1VG-swaphello swap swap defaults 0 0
Check your work
[root@kumar ~]# free -m
[root@kumar ~]# swapon -s
1) Check if you have enough space in the volume group
[root@kumar ~]# vgs
VG #PV #LV #SN Attr VSize VFree
test1VG 1 4 0 wz--n- 1020.00m 36.00m
testingextentvg 1 1 0 wz--n- 104.00m 24.00m
vgexttest 1 1 0 wz--n- 96.00m 32.00m
Following command will create Logical volume swaphello with the size 10 MB
[root@kumar ~]# lvcreate -L 10M -n swaphello test1VG
[root@kumar ~]# mkswap /dev/mapper/test1VG-swaphello
[root@kumar ~]# swapon /dev/mapper/test1VG-swaphello
Add swap entry in the fstab so that it will be persistent
[root@kumar ~]# vi /etc/fstab
/dev/mapper/test1VG-swaphello swap swap defaults 0 0
Check your work
[root@kumar ~]# free -m
[root@kumar ~]# swapon -s
Subscribe to:
Posts (Atom)
Welcome to the UNIX world
