2012-10-20 20:16, Jim Klimov wrote:
As a midway point, vanity naming did not solve this.
IPMP also failed to help me. It does work out of the box,
but does not create the kind of interface that can be used
by dladm - I can't bind a vnic to "ipmp0" or make an aggr
using it as a component :(
Ove
I hate bringing up Solaris11 again, but by default NICs are named net0
net1 net2. Maybe, someday...
Mike
On Sat, 2012-10-20 at 20:16 +0400, Jim Klimov wrote:
> As a midway point, vanity naming did not solve this.
> It only applies the name to the first interface in the datalink.conf
> file with
As a midway point, vanity naming did not solve this.
It only applies the name to the first interface in the datalink.conf
file with this name, regardless of whether its device exists.
In particular, if the eth0 name is mapped onto rge0 first, then gani0,
the system boots up with an unavailable et
Bridging only supports physical NICs, not VNICs :-(
Adding multiple VNICs to a physical NIC addresses this, but you are back
to your original problem of changing physical NICs.
I see scripting in your future...
NWAM might be used to trigger your scripts.
Mike
On Sat, 2012-10-20 at 19:28 +040
2012-10-20 19:05, Michael Stapleton wrote:
Maybe you could have your zones and the global zone on an etherstub
through VNICs,
Then route from the global zones real NIC to the VNIC connected to the
etherstub. Can you use NAT? IP addresses might be the next challenge.
Solaris11 also support DHCP wi
Maybe you could have your zones and the global zone on an etherstub
through VNICs,
Then route from the global zones real NIC to the VNIC connected to the
etherstub. Can you use NAT? IP addresses might be the next challenge.
Solaris11 also support DHCP with zones, Any one know if that might get
por
2012-10-20 18:40, Michael Stapleton wrote:
I can't believe I'm saying this, but maybe this is a job for NWAM
profiles?
Intriguing, at least ;)
I wonder if NWAM can provide a single IP interface (over which
vnics and zones can be attached) using whatever device is
available, like aggr/ipmp do?
I can't believe I'm saying this, but maybe this is a job for NWAM
profiles?
DTrace along with MDB can help you debug your NIC driver problems.
I wish I could just say what you need to probe.. :-)
You might also try different ACPI modes if it seems to be an interrupt
problem.
Mike
On Sat, 2012
Solaris 11 zonecfg support a NIC configuration called anet.
"When such a zone boots, a lower-link (see below) will be
automatically determined and a temporary VNIC automati-
cally created over that link for the zone. The lower-
link and VNIC are deleted when the zone
I really wonder how DTrace can help here - what should I track? ;)
2012-10-20 18:07, Michael Stapleton wrote:
IPMP does not have to be configured with test addresses. IPMP will uses
"Link based" by default if your NIC drivers support link state
notification.
The documentation really needs work..
Hi Jim,
Sounds to me like DTrace is the tool for you.
http://docs.oracle.com/cd/E19253-01/817-6223/chp-intro/index.html
It's not something you learn in 5 minutes, but it really is worth the
effort.
IPMP does not have to be configured with test addresses. IPMP will uses
"Link based" by default
As I wrote earlier, I am trying to match-and-use varied
drivers for my computer's NIC, one at a time, transparently
to other users of the system (including vnics over this link).
FWIW, I tried to solve the problem differently than discussed
before: now I tried to make an aggregation from instance
Jim Klimov wrote:
> 2012-10-01 15:04, James Carlson wrote:
>> Given that etherstubs aren't real Ethernet interfaces and thus cannot be
>> bridged, that plan may be hard to achieve. It's also unclear to me what
>> doing that would buy, except perhaps lower performance.
>
> As for the idea with bri
2012-10-01 15:04, James Carlson wrote:
Jim Klimov wrote:
I expected that "vanity naming" can help me in this
case by naming "the present NIC" for example "eth0",
and my zone and VNIC attachments would go over eth0.
Should this work?
Yes; it's how they were designed to work.
Thanks for the
Jim Klimov wrote:
> I expected that "vanity naming" can help me in this
> case by naming "the present NIC" for example "eth0",
> and my zone and VNIC attachments would go over eth0.
> Should this work?
Yes; it's how they were designed to work.
> Alternately, can I create an etherstub with sev
15 matches
Mail list logo
