[OpenIndiana-discuss] network errors

Jonathan Adams t12nslookup at gmail.com
Fri Jun 19 18:28:38 UTC 2015


I generally use ip-type=exclusive all the time now, mainly because I'm fed
up with all the "default" route issues.

You can set up all the interfaces the same way you did in Solaris 10, just
create a vnic in the parent and use physical:default in the zone instead of
nwam.

dladm create-vnic -l nge0 <zone name>0

Then add the net physical=<zone name>0 to the zone set ip-type to exclusive
and boot the zone! ☺

Might be worth a go.

Jon
On 19 Jun 2015 18:07, "the outsider" <openindiana at out-side.nl> wrote:

> zonecfg -z gls3  info
> zonename: gl3
> zonepath: /zones/gls3
> brand: ipkg
> autoboot: true
> bootargs:
> pool:
> limitpriv:
> scheduling-class:
> ip-type: shared
> hostid:
> fs-allowed:
> net:
>         address: 192.168.132.173/24
>         allowed-address not specified
>         physical: nge0
>         defrouter: 192.168.132.1
>
> I have multiple zones that share nics over net0, net1 and net2.
> I come from the dark lands of solaris 10 and never used crossbow or vnics
> because it was never needed.
>
> Today I tried to use a vnic setup for a zone to test with it, but Oi
> documentation is very limited and new solaris11 documentation uses
> instructions that are not incorporated in OI.
> "Ipadm create-ip" is for example a solaris 11 instruction which is not
> available in OI. There is a ipadm create-if in OI, but I don't know if it
> is
> the same.
>
> When I finally had a zone running with a vnic it couldn't reach the
> network,
> so I moved the complete webserver to solaris 11 and there it runs without
> problems with the same ip-address.
>
> Roel
>
> -----Oorspronkelijk bericht-----
> Van: Jonathan Adams [mailto:t12nslookup at gmail.com]
> Verzonden: vrijdag 19 juni 2015 18:04
> Aan: Discussion list for OpenIndiana
> Onderwerp: Re: [OpenIndiana-discuss] network errors
>
> just to start, are these ip-type=shared, or ip-type=exclusive?
>
> If they are shared, can you show us a limited "net" only section of your
> svccfg -z <zone> info ?
>
> Is there any reason that you are using separate cards for each zone, and
> not
> just virtualizing the cards?
>
> Jon
>
>
> On 19 June 2015 at 16:56, the outsider <openindiana at out-side.nl> wrote:
>
> > I have a server with 3 networkports connected to the local network
> > (1GB)
> >
> > On my server I run multiple zones all within the same range.
> > (192.168.132.x)
> >
> >
> >
> >
> > I have several OI and solaris 11 servers and have never seen these
> > problems before, they seem to be related:
> >
> > Problem 1:
> >
> > When I try pkg update from the global zone I get only error messages
> > like
> >
> > URL: 'http://pkg.openindiana.org/sfe'. (happened 4 times)
> >
> > 3: Framework error: code: 7 reason: Failed to connect to 91.194.74.133:
> > Cannot assign requested address
> >
> > URL: 'http://pkg.openindiana.org/legacy'. (happened 4 times)
> >
> >
> >
> > This "Cannot assign requested address" can be caused by a limit on
> > free sockets, but I tried "netstat -s |fgrep -i listendrop" and it
> reports:
> >
> > netstat -s |fgrep -i listendrop
> >
> >         tcpListenDrop       =     0     tcpListenDropQ0     =     0
> >
> >         sctpListenDrop      =     0     sctpInClosed        =     0
> >
> >
> >
> > so no packets seem to get dropped
> >
> >
> >
> > Problem 2:
> >
> > From the within the zones I get ping and other connection errors like
> > DNS to all IP-adresses outside the server. This happens randomly it
> > seems.
> >
> > root at GF03:~# traceroute openindiana.org
> >
> > traceroute to openindiana.org (95.131.249.92), 30 hops max, 40 byte
> > packets
> >
> > 1  * * *
> >
> > 2  * * *
> >
> > 3 ^C
> >
> >
> >
> > But 2 minutes later:
> >
> > root at GF03:~# traceroute openindiana.org
> >
> > traceroute: unknown host openindiana.org
> >
> > root at GF03:~# traceroute openindiana.org
> >
> > traceroute: unknown host openindiana.org
> >
> >
> >
> > a couple of weeks ago the problems were even bigger and I stumbled
> > upon a helpfile on the internet suggesting to turn on
> > svc:/network/location:default
> >
> > svcadm enable svc:/network/location:default
> >
> > It cured a lot of connection problems, but it was the first time that
> > I had to enable it within zones and there a still strange connection
> errors.
> >
> >
> >
> > OS is : SunOS PSK-OI 5.11 oi_151a9 i86pc i386 i86pc Solaris
> >
> >
> >
> > The server is connected to a 24 port Gigabit switch, together with
> > another Solaris 11 box and a windows server. These 2 servers don't
> > have any problem.
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > openindiana-discuss mailing list
> > openindiana-discuss at openindiana.org
> > http://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>


More information about the openindiana-discuss mailing list