My /etc/zones/server1.xml file for the zones that I want to communicate with.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/shar
e/lib/xml/dtd/zonecfg.dtd.1">
<!--
DO NOT EDIT THIS FILE. Use zonecfg(1M) instead.
-->
<zone name="server1" zonepath="/zpool2/server1" autoboot="false" brand="solaris8
">
<network address="10.10.1.21/24" physical="bge0"/>
<filesystem special="/install" directory="/install" type="lofs"/>
</zone>
---------------------------- second zone xml file --------------------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/shar
e/lib/xml/dtd/zonecfg.dtd.1">
<!--
DO NOT EDIT THIS FILE. Use zonecfg(1M) instead.
-->
<zone name="server2" zonepath="/zpool2/server2" autoboot="false" brand="solaris8
">
<network address="10.10.1.22/24" physical="bge0"/>
<filesystem special="/install" directory="/install" type="lofs"/>
</zone>
All of the zones will be configured based on the above template xml file. I am looking for something simple; The "/install" is a shared location on the global zone for s/w installs.
global zone is configured on the 192.168.xx.xx network.
The bge1 interface is currently not used / plumbed.
Ahh - found my error for zones not talking between each other; I had a bad IP address in one of the xml files. This overides the non-global host /etc/inet/hosts file entry.
I now have the internal non-global zones talking to each other; the next step is to have two sets of servers configured with a similar zone.xml file (unique IP addresses). From what I remember the 10.10.xx.xx is a private network address so the router/switch will either drop the packets; or not be able to figure out the route to the other machine(s).
So now I have the zones talking to each other; so the next step is to get a few machines running this configuration.
Code:
Sever 1 Server 2
192.168.x.1 < switch/router> 192.168.x.2
10.10.1.1 10.10.1.2
10.10.1.3 10.10.1.4
10.10.1.20 10.10.1.40
Hi Guys,
My requirement is I have file called /opt/orahome/.profile in non global zone.
PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:.
export PATH
PS1="\${ORACLE_SID}:`hostname`:\$PWD$ "
export PS1
EDITOR=vi
export EDITOR
ENV=/opt/orahome/.kshrc
export ENV... (1 Reply)
I'm in an LDOM. I'm building non-global IP exclusive zones. I am using manifests and profiles to configure the system after install so I don't have to tab through the sysconfig startup dialog everytime I boot a system the first time for settings that never change (DNS, regional data, NTP etc). I... (0 Replies)
Have 2 nics on physical system
net0 phys 1500 up --
net1 phys 1500 up --
1. I want to create a link aggregation with LACP enabled with above 2 nics
2. Create port-group(Like we create on ESXi) with VLAN-ID 2141
3. And assign this... (0 Replies)
Hi all - not really a problem as such, but just hoping someone can shed some light.
We point rexplorer to multiple Global zones and it works as expected. However, each Non-Global zone get around a hundred of root su'ing to root messages, i.e.:
SU 07/14 03:02 + ??? root-root
SU 07/14 03:02 +... (5 Replies)
Issue is : We have Solaris Global with 12 Zones and some have 15 Zones. All the OS version are10.
Is it possible to apply patch at Zone level instead of patching at Global level? Please let me know. (10 Replies)
Discussion started by: baladelaware73
10 Replies
LEARN ABOUT OPENSOLARIS
brands
brands(5) Standards, Environments, and Macros brands(5)NAME
brands - alternate operating environments for non-global zones
DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which
provide non-global zones that contain non-native operating environments.
The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones
structure.
Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed
and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default
is the native brand.
A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ-
ment. Once a zone has been assigned a brand, that brand cannot be changed or removed.
BrandZ extends the zones tools in the following ways:
o A brand is an attribute of a zone, set at zone create time.
o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone.
o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone.
Device Support
The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects
any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported
device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C),
ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F)SunOS 5.11 13 Feb 2009 brands(5)
10-15-2013
Ahh - found my error for zones not talking between each other; I had a bad IP address in one of the xml files. This overides the non-global host /etc/inet/hosts file entry.