headers
Praneeth Ravikanti | 1 Jun 2011 10:44
Picon

JUmpStart Installation and ZFS flar installation

Can anybody please explain what is mean by JumpStart Installation. As far as I know Solaris installation
with ZFS flar can be done only with JUmpStart installation. Is that correct? If that is correct, what is
Jumpstart installation, how can we do?, Is JUmpstart installation can be done from any server or any
bootable CD?

Please do the needfull
--

-- 
This message posted from opensolaris.org
Permalink | Reply | 3 comments |
headers
Sebastien Roy | 1 Jun 2011 13:58
Picon
Favicon

Re: bridges and vlans...

On 05/30/11 13:29, Alexander wrote:
>> On 5/30/2011 8:06 AM, Alexander wrote:
>>> Hello. On FreeBSD host system I have the following
>> configuration:
>>> on physical interface I created vlan, connected it
>> to bridge, created epair and added it end to bridge. In such way I
>> can connect several jailed systems (VNET) to one vlan, providing
>> one virtual interface to each jail.
>>> I'm trying to achieve this functionality on
>> OpenIndiana system (oi_151) so that severals zones could be
>> connected to one vlan with own vnic, but I didn't managed yet. I
>> can't create  vnic based on vlan and can't bridge vlan...
>>
>> Bridges exist logically below the level of VLANs, so you can't
>> really just bridge two distinct VLANs together.  It doesn't make
>> sense, at least to me.
>
> Let me try to explain in more details. I'd like to create the
> following configuration:
>
> physicalInterface =>  vlanInterface<=>  bridge<=>  etherstub<=>
> VirutalInterfaces for zones
>
> In such way I'd like to achieve the following: each zone has
> exclusive ip stack and multiple zones can be in one vlan, which is
> seen from outside. It seems, that most of our tasks can be solved
> with usual configuration (shared ip stack), but on our FreeBSD hosts
> such configuration (exclusive ip stack + bridge per vlan) is quite
> convinient.  I was suprised that I can't achive similar configuration
> on Solaris host.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bob Palowoda | 4 Jun 2011 22:59

Re: bridges and vlans...

> On 05/30/11 13:29, Alexander wrote:
> >> On 5/30/2011 8:06 AM, Alexander wrote:
> >>> Hello. On FreeBSD host system I have the
> following
> >> configuration:
> >>> on physical interface I created vlan, connected
> it
> >> to bridge, created epair and added it end to
> bridge. In such way I
> >> can connect several jailed systems (VNET) to one
> vlan, providing
> >> one virtual interface to each jail.
> >>> I'm trying to achieve this functionality on
> >> OpenIndiana system (oi_151) so that severals zones
> could be
> >> connected to one vlan with own vnic, but I didn't
> managed yet. I
> >> can't create  vnic based on vlan and can't bridge
> vlan...
> >>
> >> Bridges exist logically below the level of VLANs,
> so you can't
> >> really just bridge two distinct VLANs together.
>  It doesn't make
> > sense, at least to me.
> >
> > Let me try to explain in more details. I'd like to
> create the
> > following configuration:
> >
(Continue reading)

Permalink | Reply | 0 comments |
headers
Darren Reed | 7 Jun 2011 01:15
Picon
Favicon

Re: JUmpStart Installation and ZFS flar installation

On  1/06/11 01:44 AM, Praneeth Ravikanti wrote:
> Can anybody please explain what is mean by JumpStart Installation. As far as I know Solaris installation
with ZFS flar can be done only with JUmpStart installation. Is that correct? If that is correct, what is
Jumpstart installation, how can we do?, Is JUmpstart installation can be done from any server or any
bootable CD?
>    

There is a lot of documentation on JumpStart installation.

I would suggest that you start reading it here:
http://download.oracle.com/docs/cd/E19253-01/821-0437/index.html

Darren
Permalink | Reply | 2 comments |
headers
Daniel Payno | 7 Jun 2011 01:43
Picon

Re: JUmpStart Installation and ZFS flar installation

[NON-PC]

In my early comp.os* and bbs's days, this would've gotten a blazing fast RTFM...

Kind of miss the old days 0;)

[NON-PC]
[useful]

If you're familiar with redhat's linux Kickstart autoconfiguration, you'll grasp the essence very fast
and will only need to learn the new syntax and req. services needed..  both share basic funcionality: tftp,
bootp/dhcp, etc..

Google it will produce tons of useful links

73s!

El 07/06/2011, a las 01:15, Darren Reed <darren.reed <at> oracle.com> escribió:

> On  1/06/11 01:44 AM, Praneeth Ravikanti wrote:
>> Can anybody please explain what is mean by JumpStart Installation. As far as I know Solaris installation
with ZFS flar can be done only with JUmpStart installation. Is that correct? If that is correct, what is
Jumpstart installation, how can we do?, Is JUmpstart installation can be done from any server or any
bootable CD?
>>   
> 
> There is a lot of documentation on JumpStart installation.
> 
> I would suggest that you start reading it here:
> http://download.oracle.com/docs/cd/E19253-01/821-0437/index.html
(Continue reading)

Permalink | Reply | 1 comment |
headers
Darren Reed | 9 Jun 2011 02:55
Picon
Favicon

Re: JUmpStart Installation and ZFS flar installation

This is not a list for the discussion of platforms other than OpenSolaris.

The suggestions you provided are not in any way helpful in answering the 
original question.

In the future, please stick to providing information related to the 
topic at hand.

I will also go further and note that JumpStart is no longer used for 
automated network installs of OpenSolaris - Automated Install (AI) is. 
Questions about AI are best raised in other forums on opensolaris.org. 
Suffice to say that AI is very different to JumpStart.

Darren

On  6/06/11 04:43 PM, Daniel Payno wrote:
> [NON-PC]
>
> In my early comp.os* and bbs's days, this would've gotten a blazing fast RTFM...
>
> Kind of miss the old days 0;)
>
> [NON-PC]
> [useful]
>
> If you're familiar with redhat's linux Kickstart autoconfiguration, you'll grasp the essence very fast
and will only need to learn the new syntax and req. services needed..  both share basic funcionality: tftp,
bootp/dhcp, etc..
>
> Google it will produce tons of useful links
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vladimir Kotal | 23 Jun 2011 19:56
Picon
Favicon

dtrace script for CLOSE_WAIT leaks ?


Hi all,

Does anyone have a dtrace script for observing connection/socket leaks ? 
I.e. when application does not do shutdown()/close() on a socket which 
it previously accept()'ed ? Ideally with IP address/port pairs printed 
in the output.

v.
Permalink | Reply | 7 comments |
headers
Brian Utterback | 23 Jun 2011 20:37
Picon
Favicon

Re: dtrace script for CLOSE_WAIT leaks ?

On 06/23/11 13:56, Vladimir Kotal wrote:
> 
> Hi all,
> 
> Does anyone have a dtrace script for observing connection/socket leaks ?
> I.e. when application does not do shutdown()/close() on a socket which
> it previously accept()'ed ? Ideally with IP address/port pairs printed
> in the output.

Not sure what you would be looking for. You could trace connections as
they transition to CLOSE_WAIT, but that isn't what you want, is it? The
problem is not when they transition into CLOSE_WAIT, but when they fail
to transition out of CLOSE_WAIT. How could you trace that?

--

-- 
blu

Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. - Martin Golding
-----------------------------------------------------------------------|
Brian Utterback - Solaris RPE, Oracle Corporation.
Ph:603-262-3916, Em:brian.utterback@...
Permalink | Reply | 0 comments |
headers
Brian Ruthven | 23 Jun 2011 22:48
Picon
Favicon

Re: dtrace script for CLOSE_WAIT leaks ?

On 23/06/2011 18:56, Vladimir Kotal wrote:
>
> Hi all,
>
> Does anyone have a dtrace script for observing connection/socket leaks 
> ? I.e. when application does not do shutdown()/close() on a socket 
> which it previously accept()'ed ? Ideally with IP address/port pairs 
> printed in the output.
>

I've looked to do this kind of thing with dtrace in the past, and 
concluded that it couldn't be done (which could well be incorrect!). The 
problem with leaked stuff is that whilst capturing data, you can pair up 
and eliminate the symmetric events, but the stuff you're interested in 
is the bit left over.

It's fairly trivial to pair up the opens and closes, something like this 
(pseudo-d-code):

transition-to-close-wait:entry
{
     array[port] = 1;
}

delete-tcp-or-close-socket:entry
/array[port]/
{
     array[port] = 0;
}
(Continue reading)

Permalink | Reply | 5 comments |
headers
raghu | 24 Jun 2011 05:03

mac_link state

Hello,

1) Is it true that even after specifying mac_link_update(adapter->mach, LINK_STATE_UNKNOWN),
ethernet driver xmit routine can still get packets from stack. Application I am using is netperf. 
2) Will it not create any problem for OS like creating backpressure in its Queues because I keep getting
mbufs even after indicating LINK_STATE_UNKOWN and I return those mbufs from xmit. All these packets may
end up in OS  Queues.
3) Is there any thing more to stop getting packets apart from doing LINK_STATE_UNKNOWN/DOWN.

Thanks
Raghu.
--

-- 
This message posted from opensolaris.org
Permalink | Reply | 0 comments |

Gmane