7/304.
>
> Any details on what this is? The case doesn't seem to be available on
> opensolaris.org and the mercurial change log is not terribly
> revealing.
It's an open case, so everything ought to be there. I'll drop a line
to the ARC discuss list.
--
James
les for the non-global zones..
Sure. Ipf rules specified for the global zone apply to all 'regular'
(non-exclusive) non-global zones as well.
The rules themselves don't have a way to filter based on Zone ID or
name, but you can still filter based on address.
--
Jam
ng:
http://www.opensolaris.org/os/community/arc/caselog/2007/304/
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fa
and own resources, I
think the right answer is to go with some VM-like solution, such as
Xen, LDOMS, Domains, or VMware.
> All this allows is filtering between zones the global zones ipf rules..
Yes; that's what the loopback intercept is for.
--
James Carlson, Solaris Networking
;s designed to
do.
What does the console on the zone say? It's not busy doing sysid, is
it?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2
erit-pkg-dir
> set dir=/lib
> end
Note the set of IPDs -- these make the result into a sparse-root zone.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781
end
>
> and then specify dhcp in sysidcfg, the way we can with exclusive-ip?
I don't see why that's a special case ...
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS
>
> I think it is not, and does not require VNICs, just IP Instances.
> But VNICs allows that with one NIC.
I see. I think that just pushes the issue elsewhere, as you have to
deal with (potentially) very large numbers of MAC addresses.
--
James Carlson, Solaris Networking
ministrative intervention.
So, yes, I think you could potentially solve that same problem of
having multiple zones on one physical interface using VNICs, and there
are probably some advantages to doing so, but one detraction would be
having to manage the MAC addresses. Doing the same thing
larry lancaster writes:
> when i use zones, can I migrate then without havign to reboot my machine?
>
> Is ohter words is the zone migration static or live?
The zone itself must be shut down in order to migrate, but the machine
itself doesn't need to be rebooted.
--
James Ca
t at logical interfaces. Instead, they point at
physical interfaces -- the actual output path. Secondly, the
non-zones usage would likely result in a large number of duplicates.
This can probably be revisited (to allow for DHCP-acquired addresses
that happen to be on different subnets), but it
randZ I basically don't care...
Got it; that's an important consideration.
Getting the DHCP data into a form where Linux can use it inside the
zone might be a challenge, but it's worth some thought.
--
James Carlson, Solaris Networking <[E
Erik Nordmark writes:
> James Carlson wrote:
>
> > Getting the DHCP data into a form where Linux can use it inside the
> > zone might be a challenge, but it's worth some thought.
>
> I think it would also require emulation/translation of some additional
> Linux
he csw packages and then
using whole-root zones. That might not be the best answer, though.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBU
ist for any OpenSolaris-based
distribution, so you must be referring to Solaris 10. Solaris 10 and
patching aren't normally supported on opensolaris.org. It would be
good to get in touch with Sun's support group instead.
--
James Carlson, Solaris Networking <[EMAIL PROT
ones may have. Just a guess, though, and it depends on
the individual products, not on the Zones feature itself.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR
be consistent with the
system libraries and kernel.
Binaries that you find elsewhere may not necessarily work.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781
Dan Price writes:
> On Thu 26 Jul 2007 at 05:04PM, James Carlson wrote:
> > > Here's a code snippet :
> > >
> > > ZONECMD=${PKG_INSTALL_ROOT}/usr/bin/zonename
> >
> > That's the broken part. That should be just:
> >
> > ZONECM
xclusive stack instance. See the "ip-type"
property in zonecfg(1M).
(Are you running an OpenSolaris-based distribution? If so, then if
you have a recent enough build, you should already have this feature.)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]
re install and
management?
If that's not good, then I'd suggest that a single virtualization
group would be a good way to start.
In fact, other than a possibly excessive list of community group
leaders and core contributors, I find it a little hard to understand
why separate CGs would
arbitrary sharing
between selected sets of non-global zones. Just create a directory
and export it into the desired non-global zones via lofs.
The alternative is to choose some other means for sharing files --
such as (for example) a web, ftp, ssh, or rsync server running in the
non-glob
u3) the upgrade mechanism consisted of
some tricky patch-based work, from a project code-named "Ashanti."
The problem with that mechanism is that it required the distribution
medium (DVD-only) to carry the same bits twice -- once as packages
(for regular upgrades of global-zone-o
Mike Gerdts writes:
> On 8/16/07, James Carlson <[EMAIL PROTECTED]> wrote:
> > Previously (in S10u1 through S10u3) the upgrade mechanism consisted of
> > some tricky patch-based work, from a project code-named "Ashanti."
> > The problem with that mechanism
re/AppServer/deploytool/itp/configuration
zonecfg:blue:fs> set special=/export/blue-itp-configuration
zonecfg:blue:fs> set type=lofs
zonecfg:blue:fs> end
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W
s, and that a common community
would serve no useful purpose.
I don't quite agree, but in our last OGB meeting, we did approve the
LDoms community proposal.
Going ahead with a virtualization community that _doesn't_ involve
LDoms seems much more feasible to me.
--
James Carlson, So
ers -- were rejected by the LDoms
proponents.
The only ones in favor of the broader community were the other groups,
such as Xen:
http://mail.opensolaris.org/pipermail/ogb-discuss/2007-August/002234.html
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Net
y where
> these areas of overlap are. If anything, the zones project was the odd man
> out, since they virtualize at a different level of the stack than Xen and
> LDoms.
Even with Zones, I'd expect software packaging, install, and
maintenance issues to be shared (at least in part) wit
is not possible to use the Solaris 10 8/07 Live
Upgrade packages on a previous version of Solaris without following
the Solaris 10 8/07 patch requirements that will be detailed in this
document.
"8/07" is U4.
--
James Carlson, Solaris Networking <[EMAIL PROTECTE
e longest release cycle we've ever had.
Fortunately, none of us here are really involved in the process, so we
can't give you clear or accurate answers. ;-}
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox
scription is slightly inaccurate. It should say "by means of an
internal path within IP itself, as is the case for traffic sent to any
other local IP address."
Nothing actually "goes over" the fictional loopback interface.
--
James Carlson, Solaris Networking <[EMA
27;date'<- Not working
> xc12p11-b1-ce0-zone2: Connection refused
What's the status of svc:/network/shell:default in that zone?
Did you perhaps configure zone2 and forget to go through sysid?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Mi
Russ Petruzzelli writes:
>
> run "inetadm", see if rlogin is enabled...
Note that rlogin and rsh (shell) are two completely separate and
unrelated protocols.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive
re. It's 2007. In general, you ought not be using them
anymore. Try ssh instead.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.4
[EMAIL PROTECTED] writes:
> It is enabled but uninitialized.
Aha.
That almost certainly means that you need to log into the console of
that zone and answer the questions that sysidtool is asking.
You can look at "svcs -x" to find out more about the state of the zone
services.
--
uch as the root
password and default time zone) are what's blocking it from booting up.
Once you've done that, it'll boot up correctly.
Alternatively, you can make sure that you use a sysidcfg file when you
install the zone. There are references to this in the documentation
do that. Crossbow VNICs will eventually
make that possible, but for now, an exclusive IP instance is exactly
that: it's exclusive and cannot talk to other zones except through
normal (external) networking interfaces.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
env.sh; cd /jds/spec-files; pkgtool
> uninstal
> 20147 /usr/bin/perl -I /jds/cbe/lib/pkgbuild-1.2.0
> /jds/cbe/lib/pkgbuil
It looks like Perl is stuck. What does truss say it's doing?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsyst
Damien Carbery writes:
> If someone inside Sun would like to poke around the machine (it's in Dublin),
> I can provide the login details.
This is a zlogin bug (actually, several bugs). I'm writing up the CR
now.
--
James Carlson, Solaris Networking <[EM
one-ose005': WARNING: unable to hold network interface
> 'qfe2'.: Invalid argument
> zoneadm: zone 's8-zone-ose005': WARNING: unable to hold network interface
> 'hme0'.: Invalid argument
That's expected.
--
James Carlson, Solaris Networking
al zone!). Any sub-mounts
that appear there will not be mirrored into the zone, because lofs
doesn't cross mount points.
There currently isn't a mechanism that will do exactly what the
original poster asked. The individual mounts would need to be
replicated in each zone.
--
James Carlson
mgr/files/zonemgr-1.8.1.txt
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
___
zones-
Mike DeMarco writes:
> Is there a way to loopback mount a filesystem from the global zone
> to a local zone without having to reboot the local zone?
Yes. Use the "mount" command, something like this:
mount -F lofs /export/foo /zones/blue/root/export/foo
--
James
[EMAIL PROTECTED] writes:
> Are you sure? "lofs" generally missors the entire tree below the
> mountpoint and not just the toplevel mount.
Doh; I tried with nfs mounts. You're right.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Micr
zone or other
> local zones. Thus I'd prefer to avoid exposing zoneid_t's
> to the consumers completely, if I can.
I'm really not fond of the idea of making NULL equivalent to a
wildcard. It's far too likely to be an error case. If we need a
wildcard for a zone name, then l
That's sort of the point.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_
ble problems with such
> configurations.
We discussed the sharing issues at length during Zulu development, and
the information ended up in the design documents. I don't know,
though, how that was translated into user documentation.
--
James Carlson, Solaris Networking &l
s 24-bit?)
It doesn't always work very well, which is why I generally recommend
against /etc/netmasks. It may have been an ok interface 20 years ago,
but with CIDR, it's mostly a defect looking for a place to happen.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]
t;vni" -- it's just a place to hang a local IP
address. That's why they say "NOXMIT" when you configure them.
> The global zone has 192.168.200.14 configured on bge0
You need to give your zones access to bge0 if you want them to
transmit there. You "give ac
the FAQ:
http://www.opensolaris.org/os/community/zones/faq/#cfg_io
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Mike Gerdts writes:
> On Dec 3, 2007 5:43 AM, James Carlson <[EMAIL PROTECTED]> wrote:
> > It doesn't always work very well, which is why I generally recommend
> > against /etc/netmasks. It may have been an ok interface 20 years ago,
> > but with CIDR, it's m
e.
You have to delete the inherit-pkg-dir entries to create a whole root
zone.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N
nces, you'll need to have software that
supports it. There's a 'ce' driver change (CR 6606507) that seems to
be available now, and also a Solaris Zones change (CR 6616075) that is
integrated in OpenSolaris Nevada build 80, but that isn't available on
Solaris 10 yet.
--
ow that version matters here, so
describe the system you're using. Quite a few changes have gone into
OpenSolaris-based distributions that haven't gotten back (and may
never get back) to S10.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsy
#x27;s
probably a documentation bug.
The issue is with the design of the driver. If it uses GLDv3, then
zoneadmd can issue a special new ioctl to move the link into the
zone. If it doesn't use GLDv3, then that doesn't work.
--
James Carlson, Solaris Networking <[EMAIL PR
rently, the only framework that supports the feature is
GLDv3, which is why the "exclusive IP stack" is tied to GLDv3 support.
But non-GLDv3 drivers can also be modified (with some difficulty) to
support the feature, and that's what's being done for 'ce.'
--
James Car
Ihsan Zaghmouth writes:
> James Carlson wrote:
> There is an interesting support issue for Trunking and/or Aggregation
> that needs to be addressed
> to support of ce and ge by GLDV3.
Indeed.
> Solaris Trunking 1.3 does support ce and ge, unlike Solaris 10
> Aggregation (dla
cause we cannot form L2 forwarding loops) and IP has nothing to do
with the way in which bridging works, so how do zones cause problems?
Or what problems do you specifically see?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive7
distinction is a bit confusing because the default VLAN for an
interface is effectively ID zero -- no VLAN header at all, as long as
no CoS bits are set -- and that can be placed into a non-global zone.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 N
it'll bridge between them.
I would expect that other configurable switches have similar features.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01
; T1000.
I'm not sure what's going on with this system (it sounds like you need
some local support), but you can do this on just about any Solaris
system to discover what NICs are installed:
ifconfig -a plumb
ifconfig -a
If you're really using OpenSolaris, the
ent builds. Narrowing
down the field seems like the first obvious step.
Is it perhaps Indiana? If so, then you should be contacting that
project team directly.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1
uch reason to pester a broken
network with useless packets.
For the second question, you can listen to a routing socket if you
want. You'll get notified of routing changes, and these (particularly
RTM_ADD) may well signal a good time to schedule another connection
attempt.
Any time t
ave patches. What are you running?
If you're using Solaris 10, you should be contacting Sun's support
group instead. (I believe IP Instances went into Solaris 10 Update 4,
but, unlike OpenSolaris, some Ethernet drivers are not supported, and
you may need patches for others.)
-
07, which I think are 137042-01 and 118777-12 for SPARC. But
since you're not using OpenSolaris, you should be working with your
local support folks on that rather than an OpenSolaris-related mailing
list.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsy
et
being sent from the system (ARP can still fail and Spanning Tree can
disable ports silently) or whether delivery is possible.
Only sending data can do that, and only then in retrospect. If you
get an answer, then it must have worked.
I strongly disagree that we should be offer
The proper procedure is to close the socket, and
build a new one.
I think you're barking up the wrong tree by attempting to establish
some sort of dependency on routing.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Micros
oss reboot for qfe0 through qfe3:
touch /etc/hostname.qfe0 /etc/hostname.qfe1
touch /etc/hostname.qfe2 /etc/hostname.qfe3
Not sure if that's what you were after, though. (More context needed ...)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Micros
Ellard Roush writes:
> James Carlson wrote:
> > That point in time is as soon as your application can start. It need
> > not have any dependencies at all.
> >
> Here is the other point that needs to be clarified.
> This is not an application.
> Applications do no
acket, but since you
chose last time, it'd be good to choose again if you're able."
The root issue I described remains: if you don't bind a UDP socket (or
use one of the advanced mechanisms for specifying a source address,
like IP_PKTINFO), then just like all other systems that
is attempted. As far as the user is
concerned, the answers are (1) you must discard a TCP socket if it
fails to connect and you're going to try again and (2) when you try
again, you get another roll of the dice as far as forwarding and
source selection is concerned. If something new is a
Sanjay Akula writes:
> Does any one have automated useradd and user del scripts for solaris 10. I
> need to add mutiple users on multiple servers at a time. Need some help.
Not sure what that has to do with zones ... but have you tried
useradd(1M) and userdel(1M)?
--
James Carlson, S
ination.
If you're seeing such a difference, then document it, and file a bug.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803
James Carlson writes:
> Steffen Weiberle writes:
> > BTW, this only works for default routes. Static ones don't work. at
> > least that is my/others' experience.
>
> That's not true. Default routes are not supposed to be special.
> They're just regul
Ben Rockwood writes:
> I'm gonna bump this with hopes a developer will pick it up. I do not yet see
> a bug associated with this issue.
You're talking about CR 6684810, which was fixed back in snv_88.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
e physical ethernet interface, is that possible ?
Yes, if you can configure a VLAN on this interface using dladm. (I'm
guessing that 'vfe' isn't a GLDv3 driver, and thus you can't do that.)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsyst
Alain Durand writes:
> I built the driver with GLDv3 :
>
> # dladm show-link
> vfe0type: non-vlan mtu: 1500 device: vfe0
>
> What was your idea with a VLAN ?
You can create VLANs on that device and place them into exclusive
stack zones using zonecfg.
Alain Durand writes:
> Could you please elaborate a bit further ? I must admit I do not
> really understand what should be done.
Something like this:
# dladm create-vlan -l vfe0 -v 1
# zonecfg -z blue 'add net; set physical=vfe1000; end'
--
James Carlson, So
oup
for S10 issues (yes, I saw your email address) and (b) this stuff
works in current OpenSolaris.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS
Jim Nissen writes:
> Will Solaris 10 Zones, with exclusive IP, allow one to set NGZ TCP
> tunables, like tcp_conn_req_max_q?
Yes, every zone configured as exclusive has its own TCP/IP stack
instance.
Are you asking because you've encountered some problem with this?
--
James Carls
then gets the ioctl and can decide to do
anything it wants with it. Sometimes, it sets a variable somewhere,
or perhaps modifies multiple variables. Other ndd ioctls cause other
functions to be called, locks to be taken, and other work done.
Unlike /etc/system, the possibilities are endless.
--
J
pporting the old syntax is a minimum requirement, which
(in addition to other problems) means you likely end up having have to
define what "zoneadm -z foo boot bar" actually means.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network D
inary IP nodes, and need not know
that DSR is going on.
(Note that doing load balancing across multiple zones on the same
machine, while possible, might not make operational sense.)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive
n what problem we're solving. Is it just
that zlogin has a command line that behaves like rlogin (needing no
option to select "host"), and that zoneadm/zonecfg use an option to
specify the same thing?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun M
(I guess).
I'd expect it to work fine, but be pointless. Why load-balance across
multiple instances in a single box?
In any event, using the 'vni' interface rather than 'lo' is likely to
get you better results for most applications. This is exactly the
sort of thin
that no backport
is in progress, at least right now.
The way a backport often ends up happening is that a contract customer
for one of those older supported releases makes a formal request
through Sun's support group. That doesn't happen on opensolaris.org.
--
James Carlson, Solaris Netw
and later on
> re-deploy 2 zones to physical boxes...
Ah, ok. For staging, that makes sense. It was the deployment part I
was looking at ... I couldn't see a reason why you'd want a permanent
configuration built that way.
--
James Carlson, Solaris Networking <[EMAIL
# zoneadm -z jcp-mail-zn-mn-colo1 halt
> ^C (after 10 minutes)
>
> Any clues to what is going on?
Is there any chance that it's stuck trying to shut down? I'd first
look for threads that appear to be stuck in mdb's "::threadlist -v"
output.
--
James Carlson, Solari
g stacks.
(There are more systematic ways to search for the offender, including
locating the zone_t and finding out what it's blocked on, but looking
at the stacks is often effective and quick.)
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems /
ocumented system library interfaces -- and not at the system call
level.)
What you're suggesting isn't supported and can't be supported.
Instead of that, I'd suggest using nawk for now, and adding a call
record to CR 6387333. useradd/groupadd should know how to deal with
script will fail miserably when 'pkgadd' is pointed at
an alternate boot environment, or when invoked during a custom
install.
That's why I'm discouraging its use, and instead pointing folks to CR
6387333. There's a missing feature here, and trying to paint around
it ju
don't think we know how many of these sorts of special dependencies
exist in ON. Except for the controlled environment of patches, we've
always assumed synchronous delivery of everything built in ON as part
of our design.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]&g
.
The part that's unclear is why this is a problem. What are you doing
that depends on a logical interface name, and that needs to keep that
name static?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +
Ben Rockwood writes:
> James Carlson wrote:
> >> Let me know if you my explanation is not clear .
> >>
> >
> > The part that's unclear is why this is a problem. What are you doing
> > that depends on a logical interface name, and that needs to ke
s to watch out for?
It should work on any update that supports Etude. There've been
continuous updates to our networking support since S10 FCS, but using
VLANs (at least on some interfaces) was a feature in FCS.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
S
#x27;re obviously quite right ... I don't know where I got the idea
that 'exclusive' didn't work here. Sorry about that. :-<
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 208
easily see which global zone matches your
> local.
Yet another way it leaks through, at least on systems with shared IP
stacks, is in hardware addresses. Look at "netstat -np".
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Netwo
at it's
always been a bit problematic. It wasn't the design center for the
original Kevlar/Zones project: all zones were expected to go on a
common set of subnets.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71
re any
log messages? What was the exact configuration used? (And have you
contacted Sun's support group?)
There are some known problems, such as CR 6632938, which makes a
pattern like "/dev/dsk/c2t1d0s*" not work, but getting to the root of
the problem will require details.
--
Ja
pkg to do your upgrades, then it's the OpenSolaris
distribution.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01
ing automated tools without imposing a great burden
> on the tool developer.
That sounds like a bug that should be fixed.
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 0
101 - 200 of 272 matches
Mail list logo
