# virtinfo -a
Output similar to the following appears:
Domain role: LDoms control I/O service root Domain name: primary Domain UUID: 96ef6675-114f-e6b1-d29b-90dd48693efb Control domain: etc25dbadm01 Chassis serial#: AK00083251
The domain shown in this line is your control domain. If you are logged in to this particular domain when you enter the virtinfo -a command, you also see the value LDoms control I/O service root in the Domain role: line for this domain.
# ssh control-dom Password: control-dom#
For example:
# ssh etc4m7dbadm0101 Password: root@etc4m7dbadm0101#
control-dom# ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME primary active -n-cv- UART 256 244224M 0.3% 0.3% 32d 11m ssccn1-dom1 active -n---- 5001 256 244224M 0.4% 0.4% 32d 11m ssccn1-dom2 active -n---- 5002 256 244224M 0.0% 0.0% 32d 11m ssccn1-dom3 active -n--v- 5003 16 32G 0.1% 0.1% 32d 11m ssccn1-io-db-medium active -n---- 5008 32 64G 0.7% 0.7% 5h 46m ssccn1-io-db-small active -n---- 5007 16 32G 0.2% 0.2% 6h 8m ssccn1-io-etc4m7-ioappadm0101 active -n---- 5006 16 32G 0.1% 0.1% 10h 21m ssccn1-io-etc4m7zioadm0101 active -n---- 5004 32 64000M 1.3% 1.3% 5h 32m
For example, using the output above, you could create zones on the I/O Application Domain:
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME primary active -n-cv- UART 256 244224M 0.3% 0.3% 32d 11m ssccn1-dom1 active -n---- 5001 256 244224M 0.4% 0.4% 32d 11m ssccn1-dom2 active -n---- 5002 256 244224M 0.0% 0.0% 32d 11m ssccn1-dom3 active -n--v- 5003 16 32G 0.1% 0.1% 32d 11m ssccn1-io-db-medium active -n---- 5008 32 64G 0.7% 0.7% 5h 46m ssccn1-io-db-small active -n---- 5007 16 32G 0.2% 0.2% 6h 8m ssccn1-io-etc4m7-ioappadm0101 active -n---- 5006 16 32G 0.1% 0.1% 10h 21m ssccn1-io-etc4m7zioadm0101 active -n---- 5004 32 64000M 1.3% 1.3% 5h 32m
control-dom# exit
# ssh app-dom Password: app-dom#
For example:
# ssh etc4m7-ioappadm0101 Password: root@etc4m7-ioappadm0101#
app-dom# svcprop -a id|grep configuration/ldom_type
If the Application Domain is a dedicated domain, output similar to the following appears:
configuration/ldom_type astring dedicated
If the Application Domain is an I/O Domain, output similar to the following appears:
configuration/ldom_type astring io
app-dom# svcprop -a id|grep configuration/domain_type
Output similar to the following appears:
configuration/domain_type astring app
The action you take next varies, depending on whether you currently have zones or a template zone on this Application Domain:
If you currently have zones on this Application Domain, you will make a note of those zone names so that you can give the new zones different names from the existing zones on this Application Domain.
If you do not currently have a template zone on this Application Domain, you can create one later in this process, if you want. Creating the template zone on the Application Domain expedites the process of creating multiple zones. When you create the template zone on each Application Domain, the core Oracle Solaris packages are installed on each Application Domain. When zones are created later on, the core Oracle Solaris packages can be cloned from the template zone onto each of the zones that are created on the Application Domains. This process can significantly reduce the amount of time it takes to install core Oracle Solaris packages on each zone.
Enter this command to determine if you currently have zones and/or a template zone on this Application Domain:
app-dom# zoneadm list -cv
If you see output similar to the following:
ID NAME STATUS PATH BRAND IP 0 global running / solaris shared
then this Application Domain does not currently contain any zones or a template zone. You can create a template zone in this case, if you want (covered later in these procedures), and you are free to name the new zones you create with any name that you wish.
If you see output similar to the following:
ID NAME STATUS PATH BRAND IP 0 global running / solaris shared - s10-zone configured /export/home/s10-zone solaris10 shared
then this Application Domain currently contains a zone called s10-zone, but it does not have a template zone. In this case, you can create a template zone using procedures provided later in these steps, if you want, and when you create additional zones, make sure to name the new zones something other than the s10-zone name currently used by the existing zone.
If you see output similar to the following:
ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 61 etc4m7zdbadm010206 running /zoneHome/etc4m7zdbadm010206 solaris excl 65 etc4m7-appadm0103_T installed /zoneHomeT/etc4m7-appadm0103_T solaris excl
then this Application Domain currently contains a zone called etc4m7zdbadm010206, and it also contains a template zone, shown with a "_T" at the end of the file name (etc4m7-appadm0103_T in this example). In this case, you do not have to create a template zone later on in these procedures, and when you create additional zones, make sure to name the new zones something other than the etc4m7zdbadm010206 name currently used by the existing zone.
# ssh app-dom Password: app-dom#
For example:
# ssh etc4m7-appadm0103 Password: root@etc4m7-appadm0103#
root@etc4m7-appadm0103# /usr/bin/ssh-keygen -t rsa -f ~/.ssh/id_rsa -N "" -q ; sync;sync;sync;
root@etc4m7-appadm0103# cat .ssh/id_rsa.pub
Below is example output, with the relevant information that you would need to copy highlighted in bold font:
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6eqf6BJTIVHKgoEGNnon6sS9m6pFp0f4qvpyHCNudStJRv8tR+z4fFNpLb9U3ImS6asENT4+1GxoLTsNrs0CzhITyaRVTuRuHBD0CHT17DrSZxm/oAwxaJhxjAC0Viq4KAP28daFjBODvIMLcB/paiLlNo4zLQsNbU3aDfrcL7R9yRtni63lgAM2U0BWN/V6HUGvSK6rlhv7WQIucv4PlyjOrjPU31IMkO0MSrgxyBwfkvijiEN+55BJFN8/7xOTMqqZOdDryw0fVS0Wyc2lvV1vzF8MidVSAhGkz2Kwyz7VuPujeB7U+wGylpdgW877fmxSYGplQMBkqPkANqX9lQ== root@etc4m7-appadm0103
root@etc4m7-appadm0103# ssh -o StrictHostKeyChecking=no zfs-controller1-hostname.domain-name zfs-controller1-hostname:> exit
where:
zfs-controller1-hostname is the host name for the first storage head on the ZFS storage appliance
domain-name is the domain name for your company
For example:
root@etc4m7-appadm0103# ssh -o StrictHostKeyChecking=no etc4m7-h1-storadm.us.example.com etc4m7-h1-storadm:> exit
root@etc4m7-appadm0103# ssh -o StrictHostKeyChecking=no zfs-controller1-hostname zfs-controller1-hostname:> exit
where zfs-controller1-hostname is the host name for the first storage head on the ZFS storage appliance. Note that you do not append your company's domain name for these two entries. For example:
root@etc4m7-appadm0103# ssh -o StrictHostKeyChecking=no etc4m7-h1-storadm etc4m7-h1-storadm:> exit
# ssh zfs-controller1-hostname Password: zfs-controller1-hostname:>
For example:
# ssh etc4m7-h1-storadm Password: etc4m7-h1-storadm:>
etc4m7-h1-storadm:> configuration users etc4m7-h1-storadm:configuration users> select root etc4m7-h1-storadm:configuration users root> preferences keys etc4m7-h1-storadm:configuration users root preferences keys> create etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> set type=RSA
etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> set key="copied-output"
where copied-output is the output that you copied from Step 11.d, within quotation marks. For example:
etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> set key="AAAAB3NzaC1yc2EAAAABIwAAAQEA6eqf6BJTIVHKgoEGNnon6sS9m6pFp0f4qvpyHCNudStJRv8tR+z4fFNpLb9U3ImS6asENT4+1GxoLTsNrs0CzhITyaRVTuRuHBD0CHT17DrSZxm/oAwxaJhxjAC0Viq4KAP28daFjBODvIMLcB/paiLlNo4zLQsNbU3aDfrcL7R9yRtni63lgAM2U0BWN/V6HUGvSK6rlhv7WQIucv4PlyjOrjPU31IMkO0MSrgxyBwfkvijiEN+55BJFN8/7xOTMqqZOdDryw0fVS0Wyc2lvV1vzF8MidVSAhGkz2Kwyz7VuPujeB7U+wGylpdgW877fmxSYGplQMBkqPkANqX9lQ=="
etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> set comment="comment"
where comment is a unique comment for the changes you just applied, such as the name of the Application Domain and the date. For example:
etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> set comment="etc4m7-appadm0103-20170420"
etc4m7-h1-storadm:configuration users root preferences key (uncommitted)> commit
etc4m7-h1-storadm:configuration users root preferences key> done etc4m7-h1-storadm:> exit root@etc4m7-appadm0103#
From the ssc_exavm directory, create the template zone:
root@etc4m7-appadm0103# cd /opt/oracle.supercluster/zonetools/ssc_exavm root@etc4m7-appadm0103:/opt/oracle.supercluster/zonetools/ssc_exavm# ./ssc_exavm -template
The output shown below is abbreviated from the actual output.
INFO: Logging all actions in /opt/oracle.supercluster/zonetools/ssc_exavm/tmp/etc4m7-appadm0103-20121129093659.log and traces in /opt/oracle.supercluster/zonetools/ssc_exavm/tmp/etc4m7-appadm0103-20121129093659.trc and o/p in /opt/oracle.supercluster/zonetools/ssc_exavm/tmp/etc4m7-appadm0103-20121129093659.out INFO: Begin Template Creation INFO: Checking for etc4m7-appadm0103_T INFO: Checking for etc4m7-appadm0103_T INFO: Creating a template Virtual Guest for future use INFO: 2012-11-29 09:37:14 : Executing zfs create rpool/etc4m7-appadm0103_T INFO: Executing /opt/oracle.supercluster/zonetools/ssc_exavm/tmp/vmtrash/8461.SysCall.0.cmd INFO: Running System command ... R R SUCCESS: Done INFO: 2 : Completed Command Execution INFO: 2012-11-29 09:37:16 : Completed Command Execution INFO: 2012-11-29 09:37:16 : Executing zfs set quota=6G rpool/etc4m7-appadm0103_T INFO: Executing /opt/oracle.supercluster/zonetools/ssc_exavm/tmp/vmtrash/8461.SysCall.1.cmd ... (OUTPUT ABBREVIATED) ... INFO: Running System command ... R SUCCESS: Done INFO: 1 : Completed Command Execution INFO: 2012-11-29 09:51:25 : Completed Command Execution SUCCESS: Completed creation of Virtual guests INFO: Virtual Guest creation Summary : INFO: Completed : etc4m7-appadm0103_T Data file :: none
The name for the template zone for this particular domain is app-dom_T (for example, etc4m7-appadm0103_T).
Enter the following command to verify that the template zone was created successfully:
root@etc4m7-appadm0103# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 65 etc4m7-appadm0103_T running /zoneHomeT/etc4m7-appadm0103_T solaris excl
root@etc4m7-appadm0103# cd /opt/oracle.supercluster/zonetools/ssc_exavm
root@etc4m7-appadm0103# cp testzone_app.xml testzone_app.xml.orig
In the next step, you will edit the testzone_app.xml file to replace the default entries in that file with zone-specific entries. Use the following table to determine what the default values are and what values you want to use for the zone that you want to create in the Application Domain.
Note the following:
If there is a default entry that should remain as-is when you make your zones-specific changes to the testzone_app.xml file, that entry will be repeated in the Your Zone-Specific Entry column to show you that this default entry should remain as-is in your edited file.
The SLAVES fields are empty in the generic testzone_app.xml file, and should remain empty in your zone-specific edited version of the file.
|
Use the information that you entered in the table in the previous step to replace the default values in the file with the zone-specific values.
root@etc4m7-appadm0103# ./ssc_exavm -create -xml testzone_app.xml
At the end of the process, you should see a confirmation message similar to the following:
INFO: Completed: etc4m7zdbadm010206 Data file : : testzone_app.xml
root@etc4m7-appadm0103# zoneadm list -cv
Output similar to the following appears - note the addition of the new zone:
ID NAME STATUS PATH BRAND IP 0 global running / solaris shared 67 etc4m7zdbadm010206 running /zoneHome/etc4m7zdbadm010206 solaris excl - etc4m7-appadm0103_T installed /zoneHomeT/etc4m7-appadm0103_T solaris excl
root@etc4m7-appadm0103# zlogin etc4m7zdbadm010206 root@etc4m7zdbadm010206#
root@etc4m7zdbadm010206# ipadm show-addr
Output similar to the following should appear:
ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 scm_ipmp0/v4 static ok 10.111.22.19/22 sc_ipmp0/v4 static ok 10.111.222.20/22 bondib0/v4 static ok 192.111.10.15/22 lo0/v6 static ok ::1/128
You should not see duplicate in the STATE column for the zone that you just created. If you do see duplicate IP addresses in the output:
root@etc4m7zdbadm010206# ipadm delete-addr ADDROBJ-entry
root@etc4m7zdbadm010206# ipadm create-addr -T static -a local=new-ADDR ADDROBJ-entry
For example:
root@etc4m7zdbadm010206# ipadm delete-addr net0/v4 root@etc4m7zdbadm010206# ipadm create-addr -T static -a local=10.7.8.9/24 net0 net0/v4
root@etc4m7zdbadm010206# exit root@etc4m7-appadm0103#