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 DEBIAN
install-solaris
install-solaris(1M)install-solaris(1M)NAME
install-solaris - install the Solaris operating system
SYNOPSIS
install-solaris
install-solaris invokes the Solaris Install program. Depending on graphical capability and available memory at the time of invocation,
install-solaris invokes either a text-based installer or a graphical installer.
The following minimum requirements for physical memory dictate which features are available during installation:
For SPARC machines:
128 MB
Minimum physical memory for all installation types
128 MB
Minimum physical memory required for windowing system
384 MB
Minimum physical memory required for graphical-based installation
For x86 machines:
256 MB
Minimum physical memory for all installation types
256 MB
Minimum physical memory required for windowing system
512 MB
Minimum physical memory required for graphical-based installation
In some cases, even if the minimum physical memory is present, available virtual memory after system startup can limit the number of fea-
tures available.
install-solaris exists only on the Solaris installation media (CD or DVD) and should be invoked only from there. Refer to the for more
details.
install-solaris allows installation of the operating system onto any standalone system. install-solaris loads the software available on the
installation media. Refer to the for disk space requirements.
Refer to the for more information on the various menus and selections.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcdrom (Solaris instal- |
| |lation media) |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
pkginfo(1), install(1M), pkgadd(1M), attributes(5)
It is advisable to exit install-solaris by means of the exit options in the install-solaris menus.
23 Sep 2005 install-solaris(1M)
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.