On Saturday 17 March 2007 08:47 am, [EMAIL PROTECTED] wrote:
> >The IP Instances part of project crossbow deliver the feature to have a
> > zone have its own view of the stack. It is available as a BFU on top of
> > NV, but not yet integrated into NV.
>
> IP instances have integrated. (build 56 or
> My statement "At the beginning..." meant "When the first part(s) of
> Crossbow are in Solaris 10." At this point, IP Instances will probably
> be that "first part" and that is what I was talking about.
OK. From an engineering perspective, I consider the projects
complementary but independe
Peter Memishian wrote:
> > It might be nice to have a full list of the (otherwise Sun supported)
> > NICs which don't work, if there isn't one already. I wasn't aware
> > of this particular limitation. Do you know of such a list?
>
> At the beginning, Crossbow will only support GLDv3 NICs
Steffen Weiberle wrote:
I'll have to see if you steps are easier in a zone with an exclusive IP
instance.
FWIW There wasn't anything extra I had to do when I tested the DHCP
server in an exclusive-IP zone a few months back.
Erik
___
zones-discu
> > It might be nice to have a full list of the (otherwise Sun supported)
> > NICs which don't work, if there isn't one already. I wasn't aware
> > of this particular limitation. Do you know of such a list?
>
> At the beginning, Crossbow will only support GLDv3 NICs. Is there a
> list of
Dan Price wrote:
On Sat 17 Mar 2007 at 08:02PM, James Carlson wrote:
Dan Price writes:
- Currently must be tied to a physical NIC -- in other words
you must dedicate a real NIC (not a logical interface)
to each IP instance you want to run. This limitation is
On Sat 17 Mar 2007 at 08:02PM, James Carlson wrote:
> Dan Price writes:
> > - Currently must be tied to a physical NIC -- in other words
> > you must dedicate a real NIC (not a logical interface)
> > to each IP instance you want to run. This limitation is
> >
Dan Price writes:
> - Currently must be tied to a physical NIC -- in other words
> you must dedicate a real NIC (not a logical interface)
> to each IP instance you want to run. This limitation is
> expected to be lifted when the Virtual NIC part of Crossbow is
> - Currently must be tied to a physical NIC -- in other words
> you must dedicate a real NIC (not a logical interface)
> to each IP instance you want to run.
Or you can dedicate a VLAN on that NIC.
--
meem
___
zones-dis
On Sat 17 Mar 2007 at 04:47PM, [EMAIL PROTECTED] wrote:
>
> >The IP Instances part of project crossbow deliver the feature to have a zone
> >have its own view of the stack. It is available as a BFU on top of NV, but
> >not yet integrated into NV.
This is slightly inaccurate: I allows each zone to
> >The IP Instances part of project crossbow deliver the feature to have a zone
> >have its own view of the stack. It is available as a BFU on top of NV, but
> >not yet integrated into NV.
>
> IP instances have integrated. (build 56 or something?
Build 57 (and it's mostly separate from Cro
>The IP Instances part of project crossbow deliver the feature to have a zone
>have its own view of the stack. It is available as a BFU on top of NV, but
>not yet integrated into NV.
IP instances have integrated. (build 56 or something?
Casper
___
zon
Mike Gerdts wrote On 03/17/07 10:33,:
On 3/15/07, Darren Dunham <[EMAIL PROTECTED]> wrote:
(But you'd need to wait for some other changes to the networking
before you can run a DHCP server in a zone. I don't think that's
possible today).
In my lab, I have DHCP servers working in sparse non
13 matches
Mail list logo
