Is the non-global zone ip interface set to "shared"?
Both global and non-global zone look to be set to use "net0" so if the non-global zone requests "exclusive", it's not going to get it because the global zone is using it.
Thanks for your reply. How can I check to see if it is shared?
Also, the instructions I used to create a zone mention this:
Quote:
By default, all Oracle Solaris Zones are configured to have an automatic VNIC called anet, which gives us a network device automatically. We cannot see this network device yet, because it is automatically created when the zone is booted and also automatically destroyed on shutdown.
So I thought the interface should be automatically set up on the zone.
There might be some confusion because on the global zone the physical interface is also named net0, perhaps because the global zone is an LDom. So my global zone shows this:
While the aforementioned instructions show this:
Confusing for a network novice such as myself
I am seeking help from the gurus in this forum and hope that I can find answers soon. Anyone who provide the answers will be greatly appreciated.
I have a sparc box with Solaris 10 on it. We install Solaris with zone structure. One global zone and two other zone. I installed Oracle DB on global... (6 Replies)
Hi Everyone,
I have installed open solaris 10 on one of the x86 machines available but inspite of configuring the IP i am unable to access the machine through the network.
Can anyone please help me wih the settings required to access the machine across the network.Its really Urg..Any help is... (13 Replies)
Hi
i have created a solaris zone but have not yet connected any network cables for this new zone,
can i set the zone up without running the command 'add net' and not adding an ip or physical interface?
i tried to add dummy internet settings and get this
zonecfg:coddr> add net... (4 Replies)
I am trying to use a serial communications device that is connected to /dev/ttyb on a netra 240 server. This is a solaris zone configuration using solaris 10 0910. I am able to access /dev/ttyb from the global zone but not throught he non-global zone. I have enabled all of the tty devices in my... (0 Replies)
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 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)
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Hi,
I have a Solaris 10 zone which I need to configure on a new network. I have configured the new IP on the zone itself and I can ping the interface from a node on the same network, but not from another network. Basically I need to know how to route the traffic from the zone to it's... (3 Replies)
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT OPENSOLARIS
lx
lx(5) Standards, Environments, and Macros lx(5)NAME
lx - Linux branded zone
DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine
with a Solaris Operating System kernel.
The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone.
The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit
mode.
Supported Linux Distributions
The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions.
This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat.
In addition, the lx brand partially emulates the Linux /dev and /proc interfaces.
Configuration and Administration
The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems
of the zone.
The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be
changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used
to log in to the zone.
Application Support
The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems
from inside an lx zone.
You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to
verify.
You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be
applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated
are produced in the Solaris format, and such files can only be debugged with Solaris tools.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlxr, SUNWlxu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D)SunOS 5.11 19 Sep 2006 lx(5)