Re: [OpenIndiana-discuss] Same networking with varied NICs
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 :( Overall, I guess an RFE is in order for an aggr that can exist while some devices are missing. That would be good on several accounts - both a situation like mine, and a server whose NIC breaks or is removed and the rest of networking should not go to hell (seems it would now). //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 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 eth0 interface and creates a > new vanity naming gani0=gani0. If I reverse those two lines, things > work. So, vanity names don't really help my case - not without an > intermittent reboot, or some (SMF?) script to vanity-name the correct > interface and continue with dladm setup of the system. > > That's something but not enough to satisfy me ;) > > 2012-10-20 20:08, Michael Stapleton wrote: > > 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... > > Yes, my prophet! That might be possible ;) > > > NWAM might be used to trigger your scripts. > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 eth0 interface and creates a new vanity naming gani0=gani0. If I reverse those two lines, things work. So, vanity names don't really help my case - not without an intermittent reboot, or some (SMF?) script to vanity-name the correct interface and continue with dladm setup of the system. That's something but not enough to satisfy me ;) 2012-10-20 20:08, Michael Stapleton wrote: 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... Yes, my prophet! That might be possible ;) NWAM might be used to trigger your scripts. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 +0400, Jim Klimov wrote:
> 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 with zones, Any one know if that might get
> > ported to OI?
>
> Yeah, DHCP with zones works, as well as exclusive networking
> with routers and firewalls in zones.
>
> The challenge in this setup would be to bring the routing to
> life. There are setups where the GZ has no public IP address
> and a local zone has a dedicated public interface and works
> as a router/firewall/NAT for the whole system (GZ and other
> LZs) kind of like what you outlined. I wonder if that can
> work with the multiple interfaces, one of which is present
> at a time ("raw", ipmp or aggr to start with). If my other
> options don't pan out, I research this more - thanks for
> the idea ;)
>
> I did however want to bind at least my bridged VMs to VNICs
> on the physical public interface, so they can be addressed
> from the external net with that net's addresses. I am not
> sure this would work well over NAT (i.e. serving CIFS from
> several VMs on one public IP address is tricky), and I did
> start my questions (unanswered) discussing the possibility
> of just attaching an etherstub to external net like a switch,
> bridging over the available one of the physical interfaces.
>
> //Jim
>
>
> ___
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 with zones, Any one know if that might get
ported to OI?
Yeah, DHCP with zones works, as well as exclusive networking
with routers and firewalls in zones.
The challenge in this setup would be to bring the routing to
life. There are setups where the GZ has no public IP address
and a local zone has a dedicated public interface and works
as a router/firewall/NAT for the whole system (GZ and other
LZs) kind of like what you outlined. I wonder if that can
work with the multiple interfaces, one of which is present
at a time ("raw", ipmp or aggr to start with). If my other
options don't pan out, I research this more - thanks for
the idea ;)
I did however want to bind at least my bridged VMs to VNICs
on the physical public interface, so they can be addressed
from the external net with that net's addresses. I am not
sure this would work well over NAT (i.e. serving CIFS from
several VMs on one public IP address is tricky), and I did
start my questions (unanswered) discussing the possibility
of just attaching an etherstub to external net like a switch,
bridging over the available one of the physical interfaces.
//Jim
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 ported to OI? Mike On Sat, 2012-10-20 at 18:52 +0400, Jim Klimov wrote: > 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? > > //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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? //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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-10-20 at 18:22 +0400, Jim Klimov wrote: > 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... I think the documentation shows > > examples of "Probe based" because it is much more difficult to configure > > than "Link based". > > Simply add the interfaces to the same IPMP group. Done.. > > Yes, thanks. Today I stumbled upon this nice post about "simple > IPMP setup" without active probing, might help me. I wonder why > these are not wrapped in dladm management ;) > > http://cooperlees.com/blog/?p=328 > > And these are examples of "complicated setup" with active probing > which I was reluctant to do, from Joerg Moellenkamp's excellent > posts: > > http://www.c0t0d0s0.org/archives/6298-Less-known-Solaris-features-IP-Multipathing-Part-6-New-IPMP.html > http://www.c0t0d0s0.org/archives/6300-Less-known-Solaris-features-IP-Multipathing-Part-8-Classic-IPMP.html > > > > But, IPMP is really about uptime, not band width. If you want to use > > multiple interfaces, they all need IP addresses. They just do not have > > to have "Test" addresses. > > > > To use Aggregations, your switch and device drivers must support it. > > I think your NIC drivers have to be GLDv3 compliant. > > In fact, as per my original post, I don't exactly need IPMP nor > LACP for my case. My laptop has a single wired NIC which can be > represented by different drivers, one at a time. I want to make > switching between these simple and transparent to other network > configs on the system (vnics, zones and such). > > I plan to try "simple IPMP" and/or vanity naming (i.e. try to > name all of the possible NIC names "net0") and see if that works > later this weekend. > > At the moment I still wonder if any of these work while a device > is absent altogether (i.e. when the dual-booted OI is on physical > hardware, it has rge or gani but no e1000g; when it's booted as > a VM, it has e1000g but no rge/gani). I am now concerned that aggr > does not seem to work at all if a component device is missing - > this does seem like a bad bug in architecture or implementation. > > Thanks, > //Jim Klimov > > > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 halts." Does anyone know if there are plans to add this feature to OI? Mike On Sat, 2012-10-20 at 15:38 +0400, Jim Klimov wrote: > 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 instances of > the different drivers. VNICs over the aggregation do seem to > work, as well as "normal" communications from the GZ to internet, > though the intermittent hangs do still appear with both stock > rge and gani drivers for the builtin Realtek 8168/8111 GbE NIC. > > The problem is that the aggregation can only be defined over > existing interfaces (also if directly hacking into the config > file /etc/dladm/datalink.conf), so basically I can't predefine > an "aggr0" over "rge0 + gani0 + e1000g0" and have it work with > whatever driver I currently have loaded. If I mention a driver > which is not present at the moment (i.e. "rge0" while "gani" is > loaded, or "e1000g0" while in physical hardware boot) the aggr0 > link is not spawned at all. > > I looked at IPMP, but it seems too unwieldy for the laptop case > (each component of an ipmp group needs its own IP and a known > external node to test against). > > Can the aggregations be forced to accept missing devices and > work with those currently available? If that's not currently > possible, does it seem like a good RFE (i.e. hardware can break > so upon a reboot a server's NIC really can go missing - would > be bad to lose a whole aggr because of that)? > > Also, config changes made with dladm program take their place > immediately, however hacks into its config file require a reboot. > How can I make the system re-read the /etc/dladm/datalink.conf > file and apply manually changed settings? I tried to run > "svcadm restart datalink-management" - did not help... > > 2012-10-01 14:02, Jim Klimov wrote: > > Hello all, > > > >I wondered what is a Crossbow+VanityNaming way of > > doing some things I've done some time ago with static > > config files: > > > >I have an installed OS image which can be booted on > > different hardware (say, a pass-through partition with > > OI that can be booted from hardware BIOS as a dual-boot > > option, as well as in a VM from another host OS on the > > box). In these different hardware environments this box > > sees varied networking gear - an rge0 in one case and > > an e1000g0 in another. I want the logical networking > > to be the same in these cases. > > > >So, previously for a singular global zone I made two > > files (/etc/hostname.e1000g0 and /etc/hostname.rge0) > > with identical contents, and the system plumbed the > > one "present" NIC with the needed addressing setup. > > > >Now I want to make some VNICs and configure some > > local zones with attachment to the external NIC (can > > play with both exclusive and shared IP stacks). > > > >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? > > > >Alternately, can I create an etherstub with several > > attached VNICs, including one with IP configuration > > for the global zone, and bridge it to external LAN > > via "the one present NIC" (i.e. by attaching both > > e1000g0 and rge0 instances to the etherstub)? > > > >Disclaimer: I did not yet try either variant, and > > am in the process of setting up the boot of physical > > OI from a VM in another OS, but wanted to know in > > advance what to expect ;) > > > > Thanks, > > //Jim > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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... I think the documentation shows examples of "Probe based" because it is much more difficult to configure than "Link based". Simply add the interfaces to the same IPMP group. Done.. Yes, thanks. Today I stumbled upon this nice post about "simple IPMP setup" without active probing, might help me. I wonder why these are not wrapped in dladm management ;) http://cooperlees.com/blog/?p=328 And these are examples of "complicated setup" with active probing which I was reluctant to do, from Joerg Moellenkamp's excellent posts: http://www.c0t0d0s0.org/archives/6298-Less-known-Solaris-features-IP-Multipathing-Part-6-New-IPMP.html http://www.c0t0d0s0.org/archives/6300-Less-known-Solaris-features-IP-Multipathing-Part-8-Classic-IPMP.html But, IPMP is really about uptime, not band width. If you want to use multiple interfaces, they all need IP addresses. They just do not have to have "Test" addresses. To use Aggregations, your switch and device drivers must support it. I think your NIC drivers have to be GLDv3 compliant. In fact, as per my original post, I don't exactly need IPMP nor LACP for my case. My laptop has a single wired NIC which can be represented by different drivers, one at a time. I want to make switching between these simple and transparent to other network configs on the system (vnics, zones and such). I plan to try "simple IPMP" and/or vanity naming (i.e. try to name all of the possible NIC names "net0") and see if that works later this weekend. At the moment I still wonder if any of these work while a device is absent altogether (i.e. when the dual-booted OI is on physical hardware, it has rge or gani but no e1000g; when it's booted as a VM, it has e1000g but no rge/gani). I am now concerned that aggr does not seem to work at all if a component device is missing - this does seem like a bad bug in architecture or implementation. Thanks, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 if your NIC drivers support link state notification. The documentation really needs work... I think the documentation shows examples of "Probe based" because it is much more difficult to configure than "Link based". Simply add the interfaces to the same IPMP group. Done.. But, IPMP is really about uptime, not band width. If you want to use multiple interfaces, they all need IP addresses. They just do not have to have "Test" addresses. To use Aggregations, your switch and device drivers must support it. I think your NIC drivers have to be GLDv3 compliant. Mike On Sat, 2012-10-20 at 15:38 +0400, Jim Klimov wrote: > 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 instances of > the different drivers. VNICs over the aggregation do seem to > work, as well as "normal" communications from the GZ to internet, > though the intermittent hangs do still appear with both stock > rge and gani drivers for the builtin Realtek 8168/8111 GbE NIC. > > The problem is that the aggregation can only be defined over > existing interfaces (also if directly hacking into the config > file /etc/dladm/datalink.conf), so basically I can't predefine > an "aggr0" over "rge0 + gani0 + e1000g0" and have it work with > whatever driver I currently have loaded. If I mention a driver > which is not present at the moment (i.e. "rge0" while "gani" is > loaded, or "e1000g0" while in physical hardware boot) the aggr0 > link is not spawned at all. > > I looked at IPMP, but it seems too unwieldy for the laptop case > (each component of an ipmp group needs its own IP and a known > external node to test against). > > Can the aggregations be forced to accept missing devices and > work with those currently available? If that's not currently > possible, does it seem like a good RFE (i.e. hardware can break > so upon a reboot a server's NIC really can go missing - would > be bad to lose a whole aggr because of that)? > > Also, config changes made with dladm program take their place > immediately, however hacks into its config file require a reboot. > How can I make the system re-read the /etc/dladm/datalink.conf > file and apply manually changed settings? I tried to run > "svcadm restart datalink-management" - did not help... > > 2012-10-01 14:02, Jim Klimov wrote: > > Hello all, > > > >I wondered what is a Crossbow+VanityNaming way of > > doing some things I've done some time ago with static > > config files: > > > >I have an installed OS image which can be booted on > > different hardware (say, a pass-through partition with > > OI that can be booted from hardware BIOS as a dual-boot > > option, as well as in a VM from another host OS on the > > box). In these different hardware environments this box > > sees varied networking gear - an rge0 in one case and > > an e1000g0 in another. I want the logical networking > > to be the same in these cases. > > > >So, previously for a singular global zone I made two > > files (/etc/hostname.e1000g0 and /etc/hostname.rge0) > > with identical contents, and the system plumbed the > > one "present" NIC with the needed addressing setup. > > > >Now I want to make some VNICs and configure some > > local zones with attachment to the external NIC (can > > play with both exclusive and shared IP stacks). > > > >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? > > > >Alternately, can I create an etherstub with several > > attached VNICs, including one with IP configuration > > for the global zone, and bridge it to external LAN > > via "the one present NIC" (i.e. by attaching both > > e1000g0 and rge0 instances to the etherstub)? > > > >Disclaimer: I did not yet try either variant, and > > am in the process of setting up the boot of physical > > OI from a VM in another OS, but wanted to know in > > advance what to expect ;) > > > > Thanks, > > //Jim > > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 instances of the different drivers. VNICs over the aggregation do seem to work, as well as "normal" communications from the GZ to internet, though the intermittent hangs do still appear with both stock rge and gani drivers for the builtin Realtek 8168/8111 GbE NIC. The problem is that the aggregation can only be defined over existing interfaces (also if directly hacking into the config file /etc/dladm/datalink.conf), so basically I can't predefine an "aggr0" over "rge0 + gani0 + e1000g0" and have it work with whatever driver I currently have loaded. If I mention a driver which is not present at the moment (i.e. "rge0" while "gani" is loaded, or "e1000g0" while in physical hardware boot) the aggr0 link is not spawned at all. I looked at IPMP, but it seems too unwieldy for the laptop case (each component of an ipmp group needs its own IP and a known external node to test against). Can the aggregations be forced to accept missing devices and work with those currently available? If that's not currently possible, does it seem like a good RFE (i.e. hardware can break so upon a reboot a server's NIC really can go missing - would be bad to lose a whole aggr because of that)? Also, config changes made with dladm program take their place immediately, however hacks into its config file require a reboot. How can I make the system re-read the /etc/dladm/datalink.conf file and apply manually changed settings? I tried to run "svcadm restart datalink-management" - did not help... 2012-10-01 14:02, Jim Klimov wrote: Hello all, I wondered what is a Crossbow+VanityNaming way of doing some things I've done some time ago with static config files: I have an installed OS image which can be booted on different hardware (say, a pass-through partition with OI that can be booted from hardware BIOS as a dual-boot option, as well as in a VM from another host OS on the box). In these different hardware environments this box sees varied networking gear - an rge0 in one case and an e1000g0 in another. I want the logical networking to be the same in these cases. So, previously for a singular global zone I made two files (/etc/hostname.e1000g0 and /etc/hostname.rge0) with identical contents, and the system plumbed the one "present" NIC with the needed addressing setup. Now I want to make some VNICs and configure some local zones with attachment to the external NIC (can play with both exclusive and shared IP stacks). 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? Alternately, can I create an etherstub with several attached VNICs, including one with IP configuration for the global zone, and bridge it to external LAN via "the one present NIC" (i.e. by attaching both e1000g0 and rge0 instances to the etherstub)? Disclaimer: I did not yet try either variant, and am in the process of setting up the boot of physical OI from a VM in another OS, but wanted to know in advance what to expect ;) Thanks, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 bridging - I understand that an > etherstub is not an interface, but rather a switch or > hub. I wondered if this virtual hub can get connected > to the physical LAN (bridged at the ethernet layer) > using a physical NIC attached to both. Not that I know of. Etherstubs don't quite play in the same area as real NICs. >> It should be much easier to create VNICs on top of a chosen Ethernet >> interface. > > Basically, my main concern was that in one boot-up case > the OS has to create all those virtual and aliased NICs > over "rge0" and in another case over "e1000g0". I want > to minimize or eliminate manual changes in configs when > I boot the OI OS image on hardware or in the VM, thus > I wanted both "rge0" and "e1000g0" (whichever is present) > to map to an "eth0" and set up all the rest above this. > If this works, it would reach my goal. I see. I guess I'd be tempted to script the VNIC creation part. -- James Carlson 42.703N 71.076W ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 encouragement, I hope it will also work as advertised ;) Alternately, can I create an etherstub with several attached VNICs, including one with IP configuration for the global zone, and bridge it to external LAN via "the one present NIC" (i.e. by attaching both e1000g0 and rge0 instances to the etherstub)? 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 bridging - I understand that an etherstub is not an interface, but rather a switch or hub. I wondered if this virtual hub can get connected to the physical LAN (bridged at the ethernet layer) using a physical NIC attached to both. It should be much easier to create VNICs on top of a chosen Ethernet interface. Basically, my main concern was that in one boot-up case the OS has to create all those virtual and aliased NICs over "rge0" and in another case over "e1000g0". I want to minimize or eliminate manual changes in configs when I boot the OI OS image on hardware or in the VM, thus I wanted both "rge0" and "e1000g0" (whichever is present) to map to an "eth0" and set up all the rest above this. If this works, it would reach my goal. Thanks, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Same networking with varied NICs
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 several > attached VNICs, including one with IP configuration > for the global zone, and bridge it to external LAN > via "the one present NIC" (i.e. by attaching both > e1000g0 and rge0 instances to the etherstub)? 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. It should be much easier to create VNICs on top of a chosen Ethernet interface. -- James Carlson 42.703N 71.076W ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Same networking with varied NICs
Hello all, I wondered what is a Crossbow+VanityNaming way of doing some things I've done some time ago with static config files: I have an installed OS image which can be booted on different hardware (say, a pass-through partition with OI that can be booted from hardware BIOS as a dual-boot option, as well as in a VM from another host OS on the box). In these different hardware environments this box sees varied networking gear - an rge0 in one case and an e1000g0 in another. I want the logical networking to be the same in these cases. So, previously for a singular global zone I made two files (/etc/hostname.e1000g0 and /etc/hostname.rge0) with identical contents, and the system plumbed the one "present" NIC with the needed addressing setup. Now I want to make some VNICs and configure some local zones with attachment to the external NIC (can play with both exclusive and shared IP stacks). 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? Alternately, can I create an etherstub with several attached VNICs, including one with IP configuration for the global zone, and bridge it to external LAN via "the one present NIC" (i.e. by attaching both e1000g0 and rge0 instances to the etherstub)? Disclaimer: I did not yet try either variant, and am in the process of setting up the boot of physical OI from a VM in another OS, but wanted to know in advance what to expect ;) Thanks, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
