docker run -dit --name cldvds-always-restart --restart=always busyboxBut if you want container to always restart unless it is explicitly stopped or restarted, use:-
docker run -dit --name cldvds-except-stop --restart unless-stopped busyboxIn case you want the container to stop after 3 restart attempt use below command.
docker run -dit --name cldvds-restart-3 --restart=on-failure:3 busyboxYou can see the logs of a container using
docker logs cldvds-restart-3If you want to change the restart policy of running container you can do it with “docker update” e.g. here we are changing restart attempt from 3 to 4 of container cldvds-restart-3.
docker update --restart=on-failure:4 cldvds-restart-3
VBoxManage.exe convertfromraw filename.usb filename.vmdk --format VMDKIn the below example we will be converting a Solaris 11 USB file sol-11_2-openstack-x86_Copy.usb to vmdk.
E:\>"C:\VBoxManage.exe" convertfromraw sol-11_2-openstack-x86.usb sol-11_2_cldvds-openstack-x86_Copy.vmdk --format VMDK Converting from raw image file="sol-11_2-openstack-x86.usb" to file="sol-11_2_cldvds-openstack-x86_Copy.vmdk"... Creating dynamic image with size 8655764992 bytes (8255MB)...Convert .usb to .vdi
E:\>"C:\VBoxManage.exe" convertfromraw sol-11_2-openstack-x86.usb sol-11_2_cldvds_openstack-x86_Copy.vdi --format VDI Converting from raw image file="sol-11_2-openstack-x86.usb" to file="sol-11_2_cldvds_openstack-x86_Copy.vdi"... Creating dynamic image with size 8655764992 bytes (8255MB)...Convert .vdi to .vmdk
E:\>"C:\VBoxManage.exe" convertfromraw sol-11_2-openstack-x86_Copy.vdi sol-11_2_cldvds-openstack-x86_Copy.vmdk --format VMDK Converting from raw image file="sol-11_2-openstack-x86_Copy.vdi" to file="sol-11_2_cldvds-openstack-x86_Copy.vmdk"... Creating dynamic image with size 6624903168 bytes (6318MB)...If you want to convert from vmdk to vdi the syntax will be:
VBoxManage.exe convertfromraw filename.vmdk filename.vdi --format VDIConvert .vdi to .vhd
E:\>"C:\VBoxManage.exe" convertfromraw sol-11_2-openstack-x86_Copy.vdi sol-11_2_cldvds-openstack-x86_Copy.vhd --format VHD Converting from raw image file="sol-11_2-openstack-x86_Copy.vdi" to file="sol-11_2_cldvds-openstack-x86_Copy.vhd"... Creating dynamic image with size 6624903168 bytes (6318MB)...You can use similar steps to convert the other way round like convert .vmdk to .vdi or .vhd to .vdi.
num_proc=9Thus as per above example 9 zones can be patched in parallel. This will reduce lot of downtime if you have 9 zones running in a server. Once the entry in pdo.conf is done you can continue with normal patching process.
In this post we will discuss how to add an IP to a running Solaris zone.
If you want to add a new IP address to a running local zone(zcldvds01) you can do it by plumbing the IP manually from the global zone.
root@cldvds-global()# ifconfig aggr1:2 plumb root@cldvds-global()# ifconfig aggr1:2 inet 10.248.3.167 netmask 255.255.255.0 broadcast 10.248.3.255 zone zcldvds01 up
This change is not persistent across reboot. To make it permanent you will have to make an entry through zonecfg:-
root@cldvds-global()# zonecfg -z zcldvds01 zonecfg:zcldvds01> add net zonecfg:zcldvds01:net> set physical=aggr1 zonecfg:zcldvds01:net> set address=10.248.3.167 zonecfg:zcldvds01:net> end zonecfg:zcldvds01> verify zonecfg:zcldvds01> commit zonecfg:zcldvds01> exit
Now if you run "ifconfig -a" in the zone. You should see the new IP plumbed.
Change IP in zone
If you want to change the IP address of a zone you can simply do it by using "remove". If we take above example and we want to change IP from 10.248.3.167 to 10.248.3.175 we will do as below:-
root@cldvds-global()# zonecfg -z zcldvds01 zonecfg:zcldvds01> remove net address=10.248.3.167 zonecfg:zcldvds01> add net zonecfg:zcldvds01:net> set physical=aggr1 zonecfg:zcldvds01:net> set address=10.248.3.175 zonecfg:zcldvds01:net> end zonecfg:zcldvds01> verify zonecfg:zcldvds01> commit zonecfg:zcldvds01> exit
df -h | grep -i sagufs df -Z | grep -i sagufsAbove command will give you the complete path of the filesystem and zpool name even if it's in zone.
root# zpool status sagu-zpool pool: sagu-zpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM sagu-zpool ONLINE 0 0 0 c0t911602657A702A0004D339BDCF15E111d0 ONLINE 0 0 0 c0t911602657A702A00BE158E94CF15E111d0 ONLINE 0 0 0 c0t911602657A702A004CD071A9CF15E111d0 ONLINE 0 0 0 errors: No known data errors
root# zpool list sagu-zpool NAME SIZE ALLOC FREE CAP HEALTH ALTROOT sagu-zpool 249G 178G 71.1G 71% ONLINE -
root# format c0t9007538111C02A004E73B39A155BE211d0
root# zpool add sagu-zpool c0t9007538111C02A004E73B39A155BE211d0
root# zfs set quota=155G sagu-zpool/sagufs
root# zfs set reservation=155G sagu-zpool/sagufs
# mount -F nfs -o vers=3 host:/export/XXX /YYY
e.g.
# mount -F nfs -o vers=3 hostA:/home/cv/share_fs /tmp/testIf this works fine than make the entry permanent by modifying the /etc/default/nfs file and uncomment the variable NFS_CLIENT_VERSMAX and put entry 3
vi /etc/default/nfsNFS_CLIENT_VERSMAX=3If you are still getting permissions as nobody:nobody then you have to share the filesystem on NFS server as anon.
share -o anon=0 /home/cv/share_fsNow try re-mount on NFS Client
mount -F nfs -o vers=3 hostA:/home/cv/share_fs /tmp/test
Time during execution of CloudVedas script S90datetest.sh is Monday, 23 September 2016 16:19:43 IST Time during execution of CloudVedas script S91datetest.sh is Monday, 23 September 2016 16:19:48 ISTSimilarly during shutdown K90datetest.sh script was executed first and then K91datetest.sh .
Time during execution of CloudVedas script K90datetest.sh is Monday, 23 September 2016 16:11:43 IST Time during execution of CloudVedas script K91datetest.sh is Monday, 23 September 2016 16:11:48 ISTThis sequencing is also a trick interview question and it confuses many people.
- This AWS Crash Course series is created to give you a quick snapshot of AWS technologies. You can check about other AWS services in this series over here .
[root@cloudvedas ~]# ln -s /usr/interface/HB0 CLVSo now when you list using “ls -l” the softlink thus created will look like.
[root@cloudvedas ~]# ls -llrwxrwxrwx. 1 root root 18 Aug 8 23:16 CLV -> /usr/interface/HB0[root@cloudvedas ~]#Try going inside the link and list the contents.
[root@cloudvedas ~]# cd CLV[root@cloudvedas CLV]# lscloud1 cloud2 cloud3[root@cloudvedas CLV]#You can see the contents of /usr/interface/HB0 directory.
#init 0ok>boot -s
flarcreate -n my_bkp_image1 -c -S -R / -x /flash /flash/recovery_image.flar
cp -p /flash/recovery_image.flar /net/FLAR_recovery/recovery_image.flarFlar Restoration
For booting the boot media (installation CD/DVD). ok> boot cdromIf you want to boot from network do.
ok> boot net
If you want to cap the usage of memory for a zone, follow below steps:-
Here we will ensure that zone(zcldvdas) doesn't use more than 3072mb memory.
# zonecfg -z zcldvdas zonecfg:zcldvdas> add capped-memory zonecfg:zcldvdas:capped-memory> set physical=3072m zonecfg:zcldvdas:capped-memory> end zonecfg:zcldvdas> verify zonecfg:zcldvdas> commit zonecfg:zcldvdas> exit
Now if you want to dedicate 3072mb memory to a zone so that it's always available only to this zone. Follow below steps:-
# zonecfg -z zcldvdas zonecfg:zcldvdas> add capped-memory zonecfg:zcldvdas:capped-memory> set locked=3072m zonecfg:zcldvdas:capped-memory> end zonecfg:zcldvdas> verify zonecfg:zcldvdas> commit zonecfg:zcldvdas> exit
You can also use a combination of physical and locked to assign max and min memory to a zone.
In the next example we are assigning maximum memory the zone can use as 3072mb while minimum 1024mb which should always be available to zone.
# zonecfg -z zcldvdas zonecfg:zcldvdas> add capped-memory zonecfg:zcldvdas:capped-memory> set physical=3072m zonecfg:zcldvdas:capped-memory> set locked=1024m zonecfg:zcldvdas:capped-memory> end zonecfg:zcldvdas> verify zonecfg:zcldvdas> commit zonecfg:zcldvdas> exit
This change will be effective after reboot of the local zone.
zoneadm -z zcldvdas reboot
From Solaris10u4 onwards you can cap the memory online also using rcapadm.
rcapadm -z zcldvdas -m 3G
But remember the changes made my rcapadm are not persistent across reboot so you will still have to make the entry in zonecfg as discussed above.
You can view the set memory using rcapstat from Global Zone.
rcapstat -z 2 5
From local zone you can check this with prtconf.
prtconf -vp | grep Mem
Auditing is a good way to keep logs of all the activities happening in your Solaris server. In this post we will see how to enable auditing of both global and local zones and store the logs of all in a single file in global zone.
1) In the global zone create a new FS of 20GB and mount it.
mkdir /var/audit/gaudit mount /dev/md/dsk/d100 /var/audit/gaudit chmod -R 750 /var/audit/gaudit
2) Modify /etc/security/audit_control and add "lo,ex" before flags and naflags as below.
vi audit_control # # Copyright (c) 1988 by Sun Microsystems, Inc. # # ident "@(#)audit_control.txt 1.4 00/07/17 SMI" # dir:/var/audit/gaudit flags:lo,ex minfree:20 naflags:lo,ex
3) Modify /etc/security/audit_startup and add +argv and +zonename entries as described below. This entry will create audit logs for all zones in /var/audit/gaudit .
vi audit_startup #! /bin/sh # # Copyright 2004 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # ident "@(#)audit_startup.txt 1.1 04/06/04 SMI" /usr/bin/echo "Starting BSM services." /usr/sbin/auditconfig -setpolicy +cnt /usr/sbin/auditconfig -conf /usr/sbin/auditconfig -aconf /usr/sbin/auditconfig -setpolicy +argv /usr/sbin/auditconfig -setpolicy +zonename #
4) Copy audit_control file to /etc/security of each zone or loopback mount them in each zone.
5) Once all the zones are configured enable the audit service by running /etc/security/bsmconv. This will require reboot of system.
6) Check audit logs in /var/audit/gaudit using
auditreduce 20170709091522.not_terminated.solaris1 | praudit
7) For checking logs of a specific zone follow below
root@solaris1 # auditreduce -z zone1 20170709091522.not_terminated.solaris1 | praudit file,2017-07-09 16:26:00.000 +02:00, zone,zone1 header,160,2,execve(2),,solaris1,2017-07-09 16:26:00.697 +02:00 path,/usr/sbin/ping attribute,104555,root,bin,85,200509,0 exec_args,2,ping,127.0.0.1 subject,root,root,root,root,root,2164,2187,0 0 0.0.0.0 return,success,0 zone,zone1 file,2017-07-09 16:26:00.000 +02:00, root@solaris1 #
In this post we will see how to take XSCF snapshot of an M-Series server
Save snapshot on different server
snapshot -LF -t username@serverip:/full_path_to_data_location -k download
Here is an example. We created test user in 192.168.99.10 destination server, and snapshot will be saved in it's /var/tmp directory.
XSCF> snapshot -LF -t test@192.168.99.10:/var/tmp -k download
Save snapshot on same server.
If you want to save snapshot on same server of which you are collecting snapshot use below steps.
XSCF> showdscp DSCP Configuration: Network: 10.1.1.0 Netmask: 255.255.255.0 Location Address ---------- --------- XSCF 10.1.1.1 Domain #00 10.1.1.2 Domain #01 10.1.1.3 Domain #02 10.1.1.4 Domain #03 10.1.1.5
XSCF> showdomainstatus -a DID Domain Status 00 Running 01 - 02 - 03 -
XSCF> ping 10.1.1.2 PING 10.1.1.2 (10.1.1.2): 56 data bytes 64 bytes from 10.1.1.2: icmp_seq=0 ttl=255 time=2.1 ms 64 bytes from 10.1.1.2: icmp_seq=1 ttl=255 time=2.0 ms
XSCF> snapshot -LF -t test@10.1.1.2:/var/tmp -k download
cd /sys/class/scsi_host/
[root@scsi_host]# ls
host0 host1 host2
[root@scsi_host]#
echo "- - -" > /sys/class/scsi_host/hostX/scan
[root@cloudvedas]# echo "- - -" > /sys/class/scsi_host/host0/scan
[root@cloudvedas]# echo "- - -" > /sys/class/scsi_host/host1/scan
[root@cloudvedas]# echo "- - -" > /sys/class/scsi_host/host2/scan
[root@cloudvedas]# echo "- - -" > /sys/class/scsi_host/host3/scanTIP:- Here the “- – -” denotes CxTxDx i.e. Channel(controller) , Target ID and Disk or LUN number. This is asked in Linux Admin Interviews also.
#ls /sys/class/fc_hosthost0 host1 host2
echo "1" > /sys/class/fc_host/host0/issue_lip
echo "1" > /sys/class/fc_host/host1/issue_lip
echo "1" > /sys/class/fc_host/host2/issue_lipTip :- Here echo “1” operation performs a Loop Initialization Protocol (LIP) and then scans the interconnect and causes the SCSI layer to be updated to reflect the devices currently on the bus. A LIP is, essentially, a bus reset, and will cause device addition and removal. This procedure is necessary to configure a new SCSI target on a Fibre Channel interconnect. Bear in mind that issue_lip is an asynchronous operation.
fdisk -l |egrep '^Disk' |egrep -v 'dm-'Method 2 :-
yum install sg3_utils
/usr/bin/rescan-scsi-bus.sh
dd if=/dev/zero of=/swap1 bs=1024 count=102400Secure swap file
# sudo chown root:root /swap1# sudo chmod 0600 /swap1Set up a Linux swap area
# sudo mkswap /swap1Activate /swap1 swap space :
# sudo swapon /swap1Update /etc/fstab file to make it persistent across reboot.
vi /etc/fstabAdd the following line in file:
/swap1 swap swap defaults 0 0To check if the swap file is added or not
#sudo swapon -sFilename Type Size Used Priority/dev/dm-0 partition 839676 0 -1/swap1 file 102396 0 -2It should show you the new file.
# lvcreate VG1 -n LV1 -L 1GFormat the new swap space using mkswap:
# mkswap /dev/VG1/LV1Update /etc/fstab file with below entry:
# /dev/VG1/LV1 swap swap defaults 0 0Enable the extended logical volume:
# swapon -v /dev/VG1/LV1
loadkeys usThis simple command will map the session with US keyboard layout. So now when you type “A” in your US layout keyboard it will be printed as “A” only. And this won’t change any langs in OS as it is mapped only to your session.
sudo hostnamectl set-hostname --static cloudvedas(Here “cloudvedas” is the new hostname.)
sudo vi /etc/cloud/cloud.cfgAt the end of file add the following line and save the file
preserve_hostname: trueFinally reboot the server
sudo rebootOnce the server is up, check the hostname.
ec2-user# hostname
cloudvedas
ec2-user#It should now show you the new hostname.
sudo su -If you want to change the hostname temporarily do as below:-
hostname <new-hostname>
e.g.
hostname cloudvedasBut above change is not permanent and will change back to old name after reboot.
NETWORKING=yes
HOSTNAME=cloudvedasNext you have to modify /etc/hosts file. Entry in hosts file should look like.
172.25.31.65 cloudvedasRHEL 7
hostnamectl set-hostname --static cloudvedasThe above steps will make the hostname change persistent across reboot.
root# hostname
cloudvedas
root#It should now show you the new hostname.
cd C:\users
mkdir ProjectVagrantcd ProjectVagrant
vagrant init ubuntu/trusty64
vagrant up
vagrant sshAbove command will give you IP, Port and Private key for the machine.