Академический Документы
Профессиональный Документы
Культура Документы
Oracle
Blogs Home
Products & Services
Downloads
Support
Partners
Communities
About
Login
Oracle Blog
Oracle Solaris Cluster Oasis
Availability Engineering
« Oracle Solaris Clust... | Main | Oracle EBusiness... »
Importing a zone into a zone cluster configuration using the new 'importzone'
subcommand
By Srikant BharadwajOracle on Jan 27, 2016
The zone cluster feature of Oracle Solaris Cluster supports importing nonglobal zones into a zone cluster starting
in version 4.3. This article is going to focus on the methods to import a zone and get the Oracle Solaris Cluster
software installed in it.
With this feature you can import existing installed zones into a new zone cluster or an existing zone cluster
configuration using the clzonecluster subcommand importzone. The syntax for this subcommand when
using clzonecluster in interactive mode is:
clzc:zcname:node> importzone zonename = zonename
When using a command file with the clzonecluster configure command, the syntax is:
importzone y zonename = zonename
There are two scenarios of importing a zone into a zone cluster. In the first scenario, you can import a set of
existing zones to create a new zone cluster. For example, in Fig(1) a 3node cluster has three zones, one zone in
each globalcluster node, which can be imported into a new zone cluster called webzc using the importzone
feature. A possible usecase for this scenario is when you have a zone on one of the physical nodes of the cluster
hosting an application and if in the future the admin plans to leverage the HA options provided by OSC, the admin
can import this zone into a new zone cluster using this procedure and this zone essentially becomes the first node
of the zone cluster and further nodes can be added or imported to the zone cluster based on the need.
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 1/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Fig 1: Importing zones zone1, zone2, and zone3 to a new zone cluster webzc
In the second scenario, an installed zone is imported into an existing zone cluster. For example, in Fig (2), zone
zone1 of a node can be imported into an existing 2node zone cluster webzc to form a 3node zone cluster.
Fig 2: Importing zone zone1 to an existing zone cluster webzc
The zone cluster properties zonepath, iptype, and brand must be defined in the zone cluster
configuration.
The importzone subcommand can be executed only in the node scope.
The property physicalhost must be specified in the node scope.
The rad:local SMF service, svc:/system/rad:local must be online on the physical host
hosting the zone.
Values of properties such as zonepath, iptype, and brand of the zone must match the property
values of the zone cluster.
The zone to be imported must be in an installed state.
The property zonename of the zone being imported cannot be a part of the zonepath property of the
zone cluster.
The zone to be imported cannot be:
on shared storage.
configured as a failover highly available zone.
part of any zone cluster configuration before importing.
The imported zone will be renamed.
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 2/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Interactive mode: User will be prompted to accept.
clzc:zc:node>importzone zonename=zone1
This operation renames the zone: webzone to the zonecluster's name: webzc. Do
you want to proceed ([y]/n)?
Command file: An additional flag 'y' needs to be set.
importzone y zonename=zone1
Step 1: Assume the root role on a node of the global cluster.
Step 2: Verify that the zones are in installed state.
Ensure that you meet the other requirements listed above
physhost1# zoneadm z zone1 list –v
ID NAME STATUS PATH BRAND
IP
zone1 installed /zones/webz solaris
excl
physhost2# zoneadm z zone2 list –v
ID NAME STATUS PATH BRAND
IP
zone2 installed /zones/webz solaris
excl
physhost3# zoneadm z zone3 list –v
ID NAME STATUS PATH BRAND
IP
zone3 installed /zones/webz solaris
excl
Step 3: Run the clzonecluster configure command.
physhost1# clzonecluster configure webzc
Step 4: Create the zone cluster.
clzc:webzc:> create
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 3/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Step 5: Set the necessary properties of the zone cluster.
clzc:webzc:> set zonepath=/zones/webz
clzc:webzc:> set iptype=exclusive
clzc:webzc:> set brand=solaris
Step 6: Enter node scope using add node command.
clzc:webzc:> add node
Step 7: Set physicalhost in the node scope.
clzc:webzc:node> set physicalhost=physhost1
Step 8: Run the importzone command.
clzc:webzc:node> importzone zonename=zone1
Step 9: Accept the prompt and verify the imported the resources.
This operation renames the zone: zone1 to the zonecluster’s name: webzc.
Do you want to proceed ([y]/n)? y
Validating the resources and properties...
Extracting the Zone configuration data ...
Importing zone configuration into the zone cluster...
clzc:webzc:node> info
node:
physical‐host: phys‐host‐1
hostname not specified.
net:
address not specified
physical: vnic0
defrouter: 192.168.1.1
allowed‐address: 192.168.1.11/24
configure‐allowed‐address: true
clzc:webzc:node>
This option imports all the preexisting zone resources into the node scope. In this case we can see that the zone's
net resource with all its preset properties (like defrouter, allowedaddress, physical) has been imported. After the
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 4/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
import operation is over, proceed to the next step.
Step 10: Set hostname in the node scope.
clzc:webzc:node> set hostname=host1
Step 11: (Optional) Set other node scope properties and resources, if necessary.
# clzc:webzc:node> add privnet
# clzc:webzc:node:privnet> set physical=vnic1
# clzc:webzc:node:privnet> end
Vnics created on top of the private interconnect network cards can be used to set the privnet resources.
Step 12: End the node scope.
clzc:webzc:node> end
Repeat steps 612 for other zones.
clzc:webzc> add node
clzc:webzc:node> set physicalhost= physhost2
clzc:webzc:node> importzone zonename= zone2
This operation renames the zone: zone1 to the zonecluster’s name: webzc.
Do you want to proceed ([y]/n)? y
Validating the resources and properties...
Extracting the Zone configuration data ...
Importing zone configuration into the zone cluster...
clzc:webzc:node> set hostname=host2
clzc:webzc:node> end
clzc:webzc> add node
clzc:webzc:node> set physicalhost= physhost3
clzc:webzc:node> importzone zonename= zone3
This operation renames the zone: zone1 to the zonecluster’s name: webzc.
Do you want to proceed ([y]/n)? y
Validating the resources and properties...
Extracting the Zone configuration data ...
Importing zone configuration into the zone cluster...
clzc:webzc:node> set hostname=host3
clzc:webzc:node> end
Step 13: Commit the configuration and exit.
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 5/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
clzc:webzc:> commit
clzc:webzc:> exit
Step 14: (Optional) Verify that the zone has been imported.
physhost1# clzonecluster show v webzc
=== Zone Clusters ===
Zone Cluster Name: webzc
zonename: webzc
zonepath: /zones/webz
autoboot: TRUE
brand: solaris
hostid: <NULL>
bootargs: <NULL>
pool: <NULL>
limitpriv: <NULL>
schedulingclass: <NULL>
iptype: exclusive
enable_priv_net: FALSE
resource_security: SECURE
Solaris Resources for webzc
Zone Cluster Nodes for webzc
Node Name: physhost1
physicalhost: physhost1
hostname: host1
Transport Adapter List: vnic1,vnic2
Solaris Resources for physhost1
Resource Name: net
address: <NULL>
physical: vnic0
defrouter: 192.168.1.1
allowedaddress: 192.168.1.11/24
Node Name: physhost2
physicalhost: physhost2
hostname: host2
Transport Adapter List: vnic1,vnic2
Solaris Resources for physhost2
Resource Name: net
address: <NULL>
physical: vnic0
defrouter: 192.168.1.1
allowedaddress: 192.168.1.12/24
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 6/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Node Name: physhost3
physicalhost: physhost3
hostname: host3
Transport Adapter List: vnic1,vnic2
Solaris Resources for physhost3
Resource Name: net
address: <NULL>
physical: vnic0
defrouter: 192.168.1.1
allowedaddress: 192.168.1.13/24
As you can see, the zones have been imported into a new zone cluster webzc.
Step 1: Assume the root role on a node of the global cluster.
Step 2: Verify that the zone is in installed state.
Ensure that you meet the other requirements listed above
physhost3# zoneadm z zone1 list –v
ID NAME STATUS PATH BRAND
IP
zone1 installed /zones/webz solaris
excl
Step 3: Run the clzonecluster configure command.
physhost3# clzonecluster configure webzc
Step 6: Enter node scope using add node command.
clzc:webzc:> add node
Step 7: Set physicalhost in the node scope.
clzc:webzc:node> set physicalhost=physhost3
Step 8: Run the importzone command
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 7/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
clzc:webzc:node> importzone zonename=zone1
Step 9: Accept the prompt and verify the imported resources.
This operation renames the zone: zone1 to the zonecluster’s name: webzc.
Do you want to proceed ([y]/n)? y
Validating the resources and properties...
Extracting the Zone configuration data ...
Importing zone configuration into the zone cluster...
clzc:webzc:node> info
node:
physical‐host: phys‐host‐3
hostname not specified.
net:
address not specified
physical: vnic0
defrouter: 192.168.1.1
allowed‐address: 192.168.1.13/24
configure‐allowed‐address: true
clzc:webzc:node>
This option imports all the preexisting zone resources into the node scope. In this case we can see that the zone's
net resource with all its preset properties (like defrouter, allowedaddress, physical) has been imported. After the
import operation is over, proceed to the next step.
Step 10: Set hostname in the node scope.
clzc:webzc:node> set hostname=host3
Step 11: (Optional) Set other node scope properties and resources, if necessary.
# clzc:webzc:node> add privnet
# clzc:webzc:node:privnet> set physical=vnic1
# clzc:webzc:node:privnet> end
Vnics created on top of the private interconnect network cards can be used to set the privnet resources.
Step 12: End the node scope.
clzc:webzc:node> end
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 8/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Step 13: Commit the configuration and exit.
clzc:webzc:> commit
clzc:webzc:> exit
Step 14: (Optional) Verify that the zone has been imported.
physhost1# clzonecluster show v webzc
=== Zone Clusters ===
Zone Cluster Name: webzc
zonename: webzc
zonepath: /zones/webz
autoboot: TRUE
brand: solaris
hostid: <NULL>
bootargs: <NULL>
pool: <NULL>
limitpriv: <NULL>
schedulingclass: <NULL>
iptype: exclusive
enable_priv_net: FALSE
resource_security: SECURE
Solaris Resources for webzc
Zone Cluster Nodes for webzc
Node Name: physhost1
physicalhost: physhost1
hostname: host1
Transport Adapter List: vnic1,vnic2
Solaris Resources for physhost1
Resource Name: net
address: <NULL>
physical: vnic0
defrouter: 192.168.1.1
allowed‐address: 192.168.1.11/24
Node Name: physhost2
physicalhost: physhost2
hostname: host2
Transport Adapter List: vnic1,vnic2
Solaris Resources for physhost2
Resource Name: net
address: <NULL>
physical: vnic0
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 9/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
defrouter: 192.168.1.1
allowedaddress: 192.168.1.12/24
Node Name: physhost3
physicalhost: physhost3
hostname: host3
Transport Adapter List: vnic1,vnic2
‐‐‐ Solaris Resources for phys‐host‐3 ‐‐‐
Resource Name: net
address: <NULL>
physical: vnic0
defrouter: 192.168.1.1
allowed‐address: 192.168.1.13/24
As you can see, the zone has been imported into an existing zone cluster webzc.
Step 1: Boot the zones that have been imported.
physhost1# clzonecluster boot –n phys‐host‐1,phys‐host‐2,phys‐host‐3 webzc
Step 2: Install cluster packages in the imported zones.
physhost1# clzonecluster installcluster –n phys‐host‐1,phys‐host‐2,phys‐host‐3 webzc
Installing the cluster packages in zone cluster “webzc”
Once the zone is installed with cluster packages, it will become a member of the zone cluster. Thus, in this way
you can import an existing zone into a zone cluster using the importzone feature in Oracle Solaris Cluster
4.3.
For more information:
a) Installation Guide: Importing a zone to a zone cluster
b) Man Page: clzonecluster(1CL)
Category: Oracle Solaris Cluster
Tags: cluster zone
Permanent link to this entry
« Oracle Solaris Clust... | Main | Oracle EBusiness... »
Comments:
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 10/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Post a Comment:
Name: guest
EMail:
URL:
Notify me by email of new comments
Remember Information?
Your Comment:
HTML Syntax: NOT allowed
Please answer this simple math question
7 + 2 =
Preview Post
About
Oracle Solaris Cluster Engineering Blog
Search
Enter search term:
Recent Posts
HA for Oracle VM Server for SPARC: How to Avoid Cold Switchover When a Live Migration Fails
SSL Live Migration for HA for Oracle VM Server for SPARC
Oracle EBusiness 12.2 support on Oracle Solaris Cluster
Importing a zone into a zone cluster configuration using the new 'importzone' subcommand
Oracle Solaris Cluster Manager: Configuring HA for Oracle Solaris Zones
Oracle Solaris Cluster Manager: Setting Up Geo Disaster Recovery Orchestration
New choices for Oracle Solaris Cluster Public Networking: Link Aggregation (Trunk & DLMP) and VNIC
Configuring a Data Service for Oracle VM Server for SPARC by Using a Graphical Wizard
Introducing the New Cluster Configuration Wizard
Oracle Solaris Cluster Manager: Getting Started
Top Tags
3.2
application
automation
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 11/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
availability
availabily
blog
blueprint
cli
cluster
clustering
cmt
colorado
command
console
containers
data
deploy
disaster
documentation
edition
engine
express
failover
geographic
grid
guard
guest
ha
hanfs
high
ldoms
node
ohac
open
openhacluster
opensolaris
oracle
osc
rac
recovery
server
services
solaris
sparc
sun
system
virtual
virtualization
zfs
zone
Categories
Agents
Doc
OSP
Open High Availability Cluster
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 12/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Oracle Solaris Cluster
Other
SDN
Sun
Archives
« March 2017
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31
Today
Bookmarks
Availability Suite Demo
Open Storage Program
SC Install Certification Program
SC Learning Center
SC Programs & Promotions
Majority Report
First Thoughts of Sun Cluster 3.2
Sun Cluster 3.2
Sun Cluster and MySQL
Menu
Blogs Home
Weblog
Login
Feeds
RSS
All
/Agents
/Doc
/OSP
/Open High Availability Cluster
/Oracle Solaris Cluster
/Other
/SDN
/Sun
Comments
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 13/14
4/3/2017 Importing a zone into a zone cluster configuration using the new 'importzone' subcommand (Oracle Solaris Cluster Oasis)
Atom
All
/Agents
/Doc
/OSP
/Open High Availability Cluster
/Oracle Solaris Cluster
/Other
/SDN
/Sun
Comments
The views expressed on this blog are those of the author and do not necessarily reflect the views of Oracle. Terms
of Use | Your Privacy Rights | Cookie Preferences
https://blogs.oracle.com/SC/en_US/entry/importing_a_zone_into_a 14/14