Re: [OmniOS-discuss] LX zones and a small Howto

[Günther Alka]

Most important is the success of the Illumos or Open-ZFS platform.
LX containers are from Joyent (btw have you read this article 
https://www.infoq.com/news/2016/03/containers-summit-nyc ), SMB2+ and 
sequential resilvering are or may come from Nexenta and native 
encryption from ZoL with many features or additions that strengthen the 
platform from others versus Oracle or Linux.


ESXi, SmartOS or Proxmox are very good as a cloud or virtualisation 
platform where you can run or use ZFS  but OmniOS is a perfect NAS/SAN 
filer or server OS with the option to run a Linux container. This is 
indeed new.


Thanks to all

Gea

Am 12.10.2016 um 20:52 schrieb Dan McDonald:

On Oct 12, 2016, at 2:40 PM, Günther Alka  wrote:

What I must say is, that this seems to be a real killer innovation for OmniOS 
as you can run OmniOS as a very solid ZFS filer with additional Linux services 
running directly especially with preconfigured services as a container where 
you only need a copy and import/run after some small editings of a config file 
like shares or nics.

Joyent did most of the hard work here with LX -- credit where due, please. :)

By integrating it into OmniOS, though, you get the improvment of a 
fully-working global zone (where many sharing services can only function... 
e.g. no NFS in an NGZ currently) with the capability for closer-to-native Linux 
services (not as much running KVM in a zone now, for example).

Thanks for the napp-it update!
Dan



--

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zones and a small Howto

[Dan McDonald]

> On Oct 12, 2016, at 2:40 PM, Günther Alka  wrote:
> 
> What I must say is, that this seems to be a real killer innovation for OmniOS 
> as you can run OmniOS as a very solid ZFS filer with additional Linux 
> services running directly especially with preconfigured services as a 
> container where you only need a copy and import/run after some small editings 
> of a config file like shares or nics.

Joyent did most of the hard work here with LX -- credit where due, please. :)

By integrating it into OmniOS, though, you get the improvment of a 
fully-working global zone (where many sharing services can only function... 
e.g. no NFS in an NGZ currently) with the capability for closer-to-native Linux 
services (not as much running KVM in a zone now, for example).

Thanks for the napp-it update!
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX zones and a small Howto

[Günther Alka]

Gratulation!

I have also tried the CentOS example and it works for me.
I have created a small howto setup LX and the VM, see 
http://www.napp-it.org/doc/downloads/zones.pdf


I have not used SmartOS in the past so the concept was at first not 
clear to me.
What I must say is, that this seems to be a real killer innovation for 
OmniOS as you can run OmniOS as a very solid ZFS filer with additional 
Linux services running directly especially with preconfigured services 
as a container where you only need a copy and import/run after some 
small editings of a config file like shares or nics.


What I will add to the current concept in napp-it is deploying 
containers together with the config file (zone.cfg) like it is done on 
ESXi where you can simply provide a folder with the VM that you can 
simply import and run. An option is that one deploy LX images as a 
folder imagefile with the zone config file within and the container with 
the OS as a subfolder.


Gea

Am 12.10.2016 um 04:39 schrieb Dan McDonald:

The bloody repo server has an updated LX brand package with this fix.

Dan

Sent from my iPhone (typos, autocorrect, and all)

On Oct 11, 2016, at 2:20 PM, Richard Skelton > wrote:



Hi All,
Dan provided an updated lx_brand file which I installed in 
/usr/kernel/brand/amd64/lx_brand

After a reboot of the global zone all is now working :-)

CentOS release 6.8 (Final)
Kernel 2.6.32 on an x86_64

lx0 login:



Dan McDonald wrote:

On Oct 11, 2016, at 12:52 PM, Dan McDonald  wrote:

I'm going to check with SmartOS, and see if this is something I fubared, or if 
it's an upstream (i.e. their) problem too.  I suspect I mismerged something.  
It's fairly new, because I swear I used to see CentOS 6 consoles during the 
io-lx days.
 


Not mismerge, but missing bugfix:

 OS-5685 LTP vhangup02 fails and passes

Could you do me a favor and test a replacement lx_brand binary?  Please respond 
unicast, and we'll report back to the list once your post-fix findings match 
mine.  :)

Thanks,
Dan


   



___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


--

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Thomas Wagner]

The SSH Daemon is in most cases the limiting party. 
The ssh client is allowed to support much more older 
and weaker algorithms and protocols.
Therefore I would compare the Ciphers and macs the
Server supports.

If you run the ssh client with "ssh -vvv" then you see
what the SSH server offers and what the client can do.

Preferences can be tweaked from the server side if the
order inside the Chipers / KexAlgorithms / macs
are changed. The same is the case on the client side
if e.g. the allowed algorithms are locked down to a secure
and fast enough Cipher / mac.


I've seen on older CPUs that they limit transfer speed
early if newer algorithms are used. The hardware
accelleration does not help in all cases, as they can't
support all algorithms with accelerated subtasks.
Are junks very small? Then HW-accelleration is usually
killed by the overhead.

So I would experiment with the algorithms / macs and try 
finding one which is accellerated on both sides.

Thomas


> >
> > Can you provide the output of 'ssh -Q cipher' from both your FreeBSD and 
> > OmniOS boxes?
> >
> > /dale
> >
> 
>  Hi
> 
>  Seems to be the same
> 
>  Omnios box - ssh -Q cipher
>  3des-cbc
>  blowfish-cbc
>  cast128-cbc
>  arcfour
>  arcfour128
>  arcfour256
>  aes128-cbc
>  aes192-cbc
>  aes256-cbc
>  rijndael-...@lysator.liu.se
>  aes128-ctr
>  aes192-ctr
>  aes256-ctr
>  aes128-...@openssh.com
>  aes256-...@openssh.com
>  chacha20-poly1...@openssh.com
> 
> 
>  FreeBSD box - ssh -Q cipher:
>  3des-cbc
>  blowfish-cbc
>  cast128-cbc
>  arcfour
>  arcfour128
>  arcfour256
>  aes128-cbc
>  aes192-cbc
>  aes256-cbc
>  rijndael-...@lysator.liu.se
>  aes128-ctr
>  aes192-ctr
>  aes256-ctr
>  aes128-...@openssh.com
>  aes256-...@openssh.com
>  chacha20-poly1...@openssh.com
> 
>  ___
>  OmniOS-discuss mailing list
>  OmniOS-discuss@lists.omniti.com
>  http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

-- 
-- 
Thomas Wagner


Service rund um UNIX(TM), Wagner Network Services, Thomas Wagner
Solaris(TM), Linux(TM)Eschenweg 21, 89174 Altheim, Germany
Windows(TM)   TEL: +49-731-9807799, FAX: +49-731-9807711
Telekommunikation, LAN,   MOBILE/CELL: +49-171-6135989
Internet-Service, Elektronik  EMAIL: wag...@wagner-net.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool

[Natxo Asenjo]

hi,

>
> On Wed, Oct 12, 2016 at 6:07 PM, Gordon Ross 
> wrote:
>
>> Interesting finding re. VHD support needing resiliency support in SMB 2.1.
>> Thanks for the KB article: https://support.microsoft.com/en-us/kb/2920193
>>
>> We have resiliency support in NexentaStor 5.0 (shameless plug:)
>> https://nexenta.com/products/nexentastor
>> We should work on upstreaming that code soon.
>>
>
That would be terrific! Thanks for your efforts for making an awesome cifs
service.

--
Groeten,
natxo
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool

[Natxo Asenjo]

On Wed, Oct 12, 2016 at 6:07 PM, Gordon Ross 
wrote:

> Interesting finding re. VHD support needing resiliency support in SMB 2.1.
> Thanks for the KB article: https://support.microsoft.com/en-us/kb/2920193
>
> We have resiliency support in NexentaStor 5.0 (shameless plug:)
> https://nexenta.com/products/nexentastor
> We should work on upstreaming that code soon.
>
>
> On Wed, Oct 12, 2016 at 8:54 AM, Natxo Asenjo 
> wrote:
> > hi,
> >
> > There is  a w10 system at the home and it's a bit critical for the wife
> ;-),
> > so I want to have this up and running asap if some kind of trouble
> happens
> > with it.
> >
> > Anyway, this windows 10 OS has a backup tool that allows you to dump an
> > image to a network share using cifs, obviously.
> >
> > So I have a zfs file system, shared it for cifs, set the permissions for
> the
> > share. Start the backup, and it will fail consistently when it has
> reached
> > 57%.
> >
> > After much searching, I found this:
> > https://social.technet.microsoft.com/Forums/windows/
> en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup-
> win7-file-recovery-system-image-creation-to-nas-device-
> fails-with-error?forum=w8itprogeneral
> >
> > And yes, after:
> >
> > # sharectl set -p max_protocol=1 smb
> >
> > and restarting the cifs service, now the backup is running correctly (97%
> > and counting).
> >
> > Apparently it has to do with 'resilency support', whatever that may be:
> >
> > https://support.microsoft.com/en-us/kb/2920193
> >
> > Which is a shame, because now the cifs host is limited to smb 1.5
> instead of
> > 2.1 (but at least it works).
> >
> > Hopefully I spare somebody some unnecessary pain with this info. And it
> > would be awesome if this 'resiliciency support' made it to the cifs
> server
> > in a next version ;-)
> >
> > Thanks!
> >
> > --
> > Groeten,
> > natxo
> >
> > ___
> > OmniOS-discuss mailing list
> > OmniOS-discuss@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
> >
>



-- 
--
Groeten,
natxo
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool

[Natxo Asenjo]

On Wed, Oct 12, 2016 at 5:00 PM, Jeff Stockett 
wrote:

> FWIW, you could create a backup volume and share it via iscsi to your
> wife’s PC – quite a few commands to accomplish on the omnios side but easy
> if you have nappit already.  Once you attach it, run windows backup, and it
> will immediately see it as an available backup location and initialize it
> for just that purpose if you let it.  Then you could leave your CIFS shares
> 2.1.
>

sure, you can offer an iscsi disk but recovering bare metal from iscsi
targets is not as easy as from a share ;-) and well, as I read in the
thread, Nexenta already has this and will upstream their work (thanks!
awesome work), so for the time being I guess I can either turn smb 1 on/off
every now and then for a backup, or just live with a slower cifs protocol.

--
Groeten,
natxo
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Martin Waldenvik]

On 10/12/2016 06:34 PM, Dale Ghent wrote:



On Oct 12, 2016, at 12:05 PM, Martin Waldenvik  wrote:

omnios - ./openssl speed -elapsed -evp aes-256-gcm

The 'numbers' are in 1000s of bytes per second processed.
type16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
aes-256-gcm 36546.42k39239.49k39289.51k39519.91k  39613.78k

freebsd - ./openssl speed -elapsed -evp aes-256-gcm

The 'numbers' are in 1000s of bytes per second processed.
type16 bytes64 bytes256 bytes   1024 bytes   8192 bytes
aes-256-gcm 222688.71k  638351.04k  889610.92k  993149.57k   1017445.72k



That's still quite slow on the OmniOS box. On a 3.5GHz Haswell-E (E3-1241 v3) I 
get:

type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
aes-256-gcm 394656.68k  1001238.31k  2094818.99k  2407235.93k  2689916.93k

Perhaps you may want to check the BIOS settings of your OmniOS box and ensure that 
"AES-NI Instructions" are turned on. Your hardware vendor might have that 
termed differently - AES Acceleration and such.

/dale

Must be someting wrong with what i did. Used libressl to test chacha. 
This is with built in openssl:


type16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
aes-256-gcm 309921.38k   784682.82k  1614856.62k 1867160.92k  2117028.52k

Looks a lot better.

Martin
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Garland McAlexander]

They're autoneg, but I've been trying everything (including forcing to
10GbE).

For testing, I currently have one port set to autoneg, and one port to
10GbE to try and find a solution.

On Wed, Oct 12, 2016 at 12:34 PM, Dale Ghent  wrote:

>
> Interesting. So your switch configuration is set to nail the ports at
> 10Gbe rather than allow autoneg?
>
> /dale
>
> > On Oct 12, 2016, at 12:29 PM, Garland McAlexander 
> wrote:
> >
> > No no, I understood.
> >
> > When I set it to 0 and back to 1, the link will lose connection.
> >
> > On Wed, Oct 12, 2016 at 12:25 PM, Dale Ghent  wrote:
> >
> > Oof, I realized I may not have been clear in how I worded that. What I
> meant to ask is:
> >
> > What happens when you set en_10gfdx_cap to 0, then back to 1 ?
> >
> > > On Oct 12, 2016, at 12:23 PM, Garland McAlexander 
> wrote:
> > >
> > > Hah, yes, I tried with both interface 0 and 1.
> > >
> > > Changing that back and forth has no change.
> > >
> > > Both ixgbe0 and ixgbe1 will show as either 1000 when my switch ports
> are set to auto, and will show as STATE - Down and SPEED - 0 when I set my
> switch ports to 10GbE.
> > >
> > > On Wed, Oct 12, 2016 at 12:19 PM, Dale Ghent  wrote:
> > >
> > > I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)
> > >
> > > how about setting that to 0, then back to 1?
> > >
> > > /dale
> > >
> > > > On Oct 12, 2016, at 11:59 AM, Garland McAlexander <
> garl...@bustle.com> wrote:
> > > >
> > > > Yes, I'm getting a 1GbE link.
> > > >
> > > > Randomly it'll work as 10GbE after a reboot, but another reboot will
> cause it to go back to 1GbE.
> > > >
> > > > Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> > > >
> > > > On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> > > > On Oct 7, 2016, at 11:44 AM, Garland McAlexander 
> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It
> works perfectly fine at 10GbE if using Windows or CentOS on the same
> machine. Just to be safe, I've tried multiple switches and Cat6a cabling.
> > > > >
> > > > > Any tips on how to get this going?
> > > >
> > > > Are you getting a 1Gb link instead of a 10Gb link?
> > > >
> > > > Can you run this:
> > > >
> > > > dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> > > >
> > > > And check the link speed afterwards (dladm show-phys)
> > > >
> > > > /dale
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Garland McAlexander
> > > >
> > > > Technology Manager
> > > >
> > > > E: garl...@bustle.com
> > > >
> > > > 
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > Garland McAlexander
> > >
> > > Technology Manager
> > >
> > > E: garl...@bustle.com
> > >
> > > 
> > >
> >
> >
> >
> >
> > --
> > Garland McAlexander
> >
> > Technology Manager
> >
> > E: garl...@bustle.com
> >
> > 
> >
>
>


-- 

Garland McAlexander

Technology Manager

E: garl...@bustle.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Dale Ghent]

> On Oct 12, 2016, at 12:05 PM, Martin Waldenvik  wrote:
> 
> omnios - ./openssl speed -elapsed -evp aes-256-gcm
> 
> The 'numbers' are in 1000s of bytes per second processed.
> type16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
> aes-256-gcm 36546.42k39239.49k39289.51k39519.91k  39613.78k
> 
> freebsd - ./openssl speed -elapsed -evp aes-256-gcm
> 
> The 'numbers' are in 1000s of bytes per second processed.
> type16 bytes64 bytes256 bytes   1024 bytes   8192 bytes
> aes-256-gcm 222688.71k  638351.04k  889610.92k  993149.57k   1017445.72k
> 

That's still quite slow on the OmniOS box. On a 3.5GHz Haswell-E (E3-1241 v3) I 
get:

type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
aes-256-gcm 394656.68k  1001238.31k  2094818.99k  2407235.93k  2689916.93k

Perhaps you may want to check the BIOS settings of your OmniOS box and ensure 
that "AES-NI Instructions" are turned on. Your hardware vendor might have that 
termed differently - AES Acceleration and such.

/dale
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Dale Ghent]

Interesting. So your switch configuration is set to nail the ports at 10Gbe 
rather than allow autoneg?

/dale

> On Oct 12, 2016, at 12:29 PM, Garland McAlexander  wrote:
> 
> No no, I understood.
> 
> When I set it to 0 and back to 1, the link will lose connection.
> 
> On Wed, Oct 12, 2016 at 12:25 PM, Dale Ghent  wrote:
> 
> Oof, I realized I may not have been clear in how I worded that. What I meant 
> to ask is:
> 
> What happens when you set en_10gfdx_cap to 0, then back to 1 ?
> 
> > On Oct 12, 2016, at 12:23 PM, Garland McAlexander  
> > wrote:
> >
> > Hah, yes, I tried with both interface 0 and 1.
> >
> > Changing that back and forth has no change.
> >
> > Both ixgbe0 and ixgbe1 will show as either 1000 when my switch ports are 
> > set to auto, and will show as STATE - Down and SPEED - 0 when I set my 
> > switch ports to 10GbE.
> >
> > On Wed, Oct 12, 2016 at 12:19 PM, Dale Ghent  wrote:
> >
> > I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)
> >
> > how about setting that to 0, then back to 1?
> >
> > /dale
> >
> > > On Oct 12, 2016, at 11:59 AM, Garland McAlexander  
> > > wrote:
> > >
> > > Yes, I'm getting a 1GbE link.
> > >
> > > Randomly it'll work as 10GbE after a reboot, but another reboot will 
> > > cause it to go back to 1GbE.
> > >
> > > Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> > >
> > > On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> > > On Oct 7, 2016, at 11:44 AM, Garland McAlexander  
> > > wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It works 
> > > > perfectly fine at 10GbE if using Windows or CentOS on the same machine. 
> > > > Just to be safe, I've tried multiple switches and Cat6a cabling.
> > > >
> > > > Any tips on how to get this going?
> > >
> > > Are you getting a 1Gb link instead of a 10Gb link?
> > >
> > > Can you run this:
> > >
> > > dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> > >
> > > And check the link speed afterwards (dladm show-phys)
> > >
> > > /dale
> > >
> > >
> > >
> > >
> > > --
> > > Garland McAlexander
> > >
> > > Technology Manager
> > >
> > > E: garl...@bustle.com
> > >
> > > 
> > >
> >
> >
> >
> >
> > --
> > Garland McAlexander
> >
> > Technology Manager
> >
> > E: garl...@bustle.com
> >
> > 
> >
> 
> 
> 
> 
> -- 
> Garland McAlexander
> 
> Technology Manager
> 
> E: garl...@bustle.com
> 
> 
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Garland McAlexander]

No no, I understood.

When I set it to 0 and back to 1, the link will lose connection.

On Wed, Oct 12, 2016 at 12:25 PM, Dale Ghent  wrote:

>
> Oof, I realized I may not have been clear in how I worded that. What I
> meant to ask is:
>
> What happens when you set en_10gfdx_cap to 0, then back to 1 ?
>
> > On Oct 12, 2016, at 12:23 PM, Garland McAlexander 
> wrote:
> >
> > Hah, yes, I tried with both interface 0 and 1.
> >
> > Changing that back and forth has no change.
> >
> > Both ixgbe0 and ixgbe1 will show as either 1000 when my switch ports are
> set to auto, and will show as STATE - Down and SPEED - 0 when I set my
> switch ports to 10GbE.
> >
> > On Wed, Oct 12, 2016 at 12:19 PM, Dale Ghent  wrote:
> >
> > I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)
> >
> > how about setting that to 0, then back to 1?
> >
> > /dale
> >
> > > On Oct 12, 2016, at 11:59 AM, Garland McAlexander 
> wrote:
> > >
> > > Yes, I'm getting a 1GbE link.
> > >
> > > Randomly it'll work as 10GbE after a reboot, but another reboot will
> cause it to go back to 1GbE.
> > >
> > > Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> > >
> > > On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> > > On Oct 7, 2016, at 11:44 AM, Garland McAlexander 
> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It
> works perfectly fine at 10GbE if using Windows or CentOS on the same
> machine. Just to be safe, I've tried multiple switches and Cat6a cabling.
> > > >
> > > > Any tips on how to get this going?
> > >
> > > Are you getting a 1Gb link instead of a 10Gb link?
> > >
> > > Can you run this:
> > >
> > > dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> > >
> > > And check the link speed afterwards (dladm show-phys)
> > >
> > > /dale
> > >
> > >
> > >
> > >
> > > --
> > > Garland McAlexander
> > >
> > > Technology Manager
> > >
> > > E: garl...@bustle.com
> > >
> > > 
> > >
> >
> >
> >
> >
> > --
> > Garland McAlexander
> >
> > Technology Manager
> >
> > E: garl...@bustle.com
> >
> > 
> >
>
>


-- 

Garland McAlexander

Technology Manager

E: garl...@bustle.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Dale Ghent]

Oof, I realized I may not have been clear in how I worded that. What I meant to 
ask is:

What happens when you set en_10gfdx_cap to 0, then back to 1 ?

> On Oct 12, 2016, at 12:23 PM, Garland McAlexander  wrote:
> 
> Hah, yes, I tried with both interface 0 and 1.
> 
> Changing that back and forth has no change.
> 
> Both ixgbe0 and ixgbe1 will show as either 1000 when my switch ports are set 
> to auto, and will show as STATE - Down and SPEED - 0 when I set my switch 
> ports to 10GbE.
> 
> On Wed, Oct 12, 2016 at 12:19 PM, Dale Ghent  wrote:
> 
> I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)
> 
> how about setting that to 0, then back to 1?
> 
> /dale
> 
> > On Oct 12, 2016, at 11:59 AM, Garland McAlexander  
> > wrote:
> >
> > Yes, I'm getting a 1GbE link.
> >
> > Randomly it'll work as 10GbE after a reboot, but another reboot will cause 
> > it to go back to 1GbE.
> >
> > Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> >
> > On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> > On Oct 7, 2016, at 11:44 AM, Garland McAlexander  wrote:
> > >
> > > Hi All,
> > >
> > > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It works 
> > > perfectly fine at 10GbE if using Windows or CentOS on the same machine. 
> > > Just to be safe, I've tried multiple switches and Cat6a cabling.
> > >
> > > Any tips on how to get this going?
> >
> > Are you getting a 1Gb link instead of a 10Gb link?
> >
> > Can you run this:
> >
> > dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> >
> > And check the link speed afterwards (dladm show-phys)
> >
> > /dale
> >
> >
> >
> >
> > --
> > Garland McAlexander
> >
> > Technology Manager
> >
> > E: garl...@bustle.com
> >
> > 
> >
> 
> 
> 
> 
> -- 
> Garland McAlexander
> 
> Technology Manager
> 
> E: garl...@bustle.com
> 
> 
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Garland McAlexander]

Hah, yes, I tried with both interface 0 and 1.

Changing that back and forth has no change.

Both ixgbe0 and ixgbe1 will show as either 1000 when my switch ports are
set to auto, and will show as STATE - Down and SPEED - 0 when I set my
switch ports to 10GbE.

On Wed, Oct 12, 2016 at 12:19 PM, Dale Ghent  wrote:

>
> I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)
>
> how about setting that to 0, then back to 1?
>
> /dale
>
> > On Oct 12, 2016, at 11:59 AM, Garland McAlexander 
> wrote:
> >
> > Yes, I'm getting a 1GbE link.
> >
> > Randomly it'll work as 10GbE after a reboot, but another reboot will
> cause it to go back to 1GbE.
> >
> > Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> >
> > On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> > On Oct 7, 2016, at 11:44 AM, Garland McAlexander 
> wrote:
> > >
> > > Hi All,
> > >
> > > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It works
> perfectly fine at 10GbE if using Windows or CentOS on the same machine.
> Just to be safe, I've tried multiple switches and Cat6a cabling.
> > >
> > > Any tips on how to get this going?
> >
> > Are you getting a 1Gb link instead of a 10Gb link?
> >
> > Can you run this:
> >
> > dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> >
> > And check the link speed afterwards (dladm show-phys)
> >
> > /dale
> >
> >
> >
> >
> > --
> > Garland McAlexander
> >
> > Technology Manager
> >
> > E: garl...@bustle.com
> >
> > 
> >
>
>


-- 

Garland McAlexander

Technology Manager

E: garl...@bustle.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Dale Ghent]

I trust you set N to the interface instance of ixgbe :) (eg; ixgbe0)

how about setting that to 0, then back to 1?

/dale

> On Oct 12, 2016, at 11:59 AM, Garland McAlexander  wrote:
> 
> Yes, I'm getting a 1GbE link. 
> 
> Randomly it'll work as 10GbE after a reboot, but another reboot will cause it 
> to go back to 1GbE.
> 
> Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.
> 
> On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:
> On Oct 7, 2016, at 11:44 AM, Garland McAlexander  wrote:
> >
> > Hi All,
> >
> > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It works 
> > perfectly fine at 10GbE if using Windows or CentOS on the same machine. 
> > Just to be safe, I've tried multiple switches and Cat6a cabling.
> >
> > Any tips on how to get this going?
> 
> Are you getting a 1Gb link instead of a 10Gb link?
> 
> Can you run this:
> 
> dladm set-linkprop en_10gfdx_cap=1 ixgbeN
> 
> And check the link speed afterwards (dladm show-phys)
> 
> /dale
> 
> 
> 
> 
> -- 
> Garland McAlexander
> 
> Technology Manager
> 
> E: garl...@bustle.com
> 
> 
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool

[Gordon Ross]

Interesting finding re. VHD support needing resiliency support in SMB 2.1.
Thanks for the KB article: https://support.microsoft.com/en-us/kb/2920193

We have resiliency support in NexentaStor 5.0 (shameless plug:)
https://nexenta.com/products/nexentastor
We should work on upstreaming that code soon.


On Wed, Oct 12, 2016 at 8:54 AM, Natxo Asenjo  wrote:
> hi,
>
> There is  a w10 system at the home and it's a bit critical for the wife ;-),
> so I want to have this up and running asap if some kind of trouble happens
> with it.
>
> Anyway, this windows 10 OS has a backup tool that allows you to dump an
> image to a network share using cifs, obviously.
>
> So I have a zfs file system, shared it for cifs, set the permissions for the
> share. Start the backup, and it will fail consistently when it has reached
> 57%.
>
> After much searching, I found this:
> https://social.technet.microsoft.com/Forums/windows/en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup-win7-file-recovery-system-image-creation-to-nas-device-fails-with-error?forum=w8itprogeneral
>
> And yes, after:
>
> # sharectl set -p max_protocol=1 smb
>
> and restarting the cifs service, now the backup is running correctly (97%
> and counting).
>
> Apparently it has to do with 'resilency support', whatever that may be:
>
> https://support.microsoft.com/en-us/kb/2920193
>
> Which is a shame, because now the cifs host is limited to smb 1.5 instead of
> 2.1 (but at least it works).
>
> Hopefully I spare somebody some unnecessary pain with this info. And it
> would be awesome if this 'resiliciency support' made it to the cifs server
> in a next version ;-)
>
> Thanks!
>
> --
> Groeten,
> natxo
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] KVM +NVMe + dedup

[Machine Man]

I am looking to build an all NVMe system using:

SYS-1028U-TN10RT+


OS will be on a mirror pair of 400GB and there will be a data pool of 4x 800GB 
in striped mirror pair. (there will be one 2x small VMs on rpool)

The system will run 7 virtual machines (most will be Windows 2012R2 and one a 
300GB SQL 2014 server) configured in KVM on OmniOS.

The main reason for not using 10K or 15K drives is performance and dedup. I 
would like to get down to the a 1U chassis for this build.

I have not been that successful with SAS 10/15K  configuration and using KVM. I 
have tried different block sizes and some tuning and it could just be the load 
of these systems.

We have a number of system running for years now, but never considered dedup 
largely due to fear of all the negative post, but most could also be due 
incorrect hardware configurations.


My main reason for posting is to perhaps get feedback if this route can be 
considered or to stick to 2U 24x drive chassis and use more spindles without 
dedup. The system will have 192GB of memory and the VMs will not even consume 
close to 100GB.

CPUs will be 2x 2.6Ghz 6core E5-2600 v3.

The systems are fairly critical and the reason for not using VMware or 
commercial products is for snapshots and to cut down on how many products we 
need to update (hypervisor, backup software, replication components).


Also, when using dedup, is there a higher disk of data corruption in the event 
of power outage?


Thanks,
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Issues with 10GbE - X540

[Garland McAlexander]

Yes, I'm getting a 1GbE link.

Randomly it'll work as 10GbE after a reboot, but another reboot will cause
it to go back to 1GbE.

Running 'dladm set-linkprop en_10gfdx_cap=1 ixgbeN' has no change.

On Fri, Oct 7, 2016 at 1:07 PM, Dale Ghent  wrote:

> On Oct 7, 2016, at 11:44 AM, Garland McAlexander 
> wrote:
> >
> > Hi All,
> >
> > I'm unable to link at 10GbE with my onboard X540 (X10DRW-iT). It works
> perfectly fine at 10GbE if using Windows or CentOS on the same machine.
> Just to be safe, I've tried multiple switches and Cat6a cabling.
> >
> > Any tips on how to get this going?
>
> Are you getting a 1Gb link instead of a 10Gb link?
>
> Can you run this:
>
> dladm set-linkprop en_10gfdx_cap=1 ixgbeN
>
> And check the link speed afterwards (dladm show-phys)
>
> /dale
>
>


-- 

Garland McAlexander

Technology Manager

E: garl...@bustle.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[John D Groenveld]

In message , Martin Waldenvik wri
tes:
>I have used those ciphers in that order on all my servers and it works 
>in full speed i both freebsd and linux but not in Omnios.

If your FreeBSD and OmniOS installs are on similar hardware,
openssl(1) speed benchmark might be interesting.

John
groenv...@acm.org

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Martin Waldenvik]

On 10/12/2016 04:53 PM, Dale Ghent wrote:



On Oct 12, 2016, at 10:45 AM, Martin Waldenvik  wrote:

On 10/12/2016 04:37 PM, Dan McDonald wrote:



On Oct 12, 2016, at 10:21 AM, Martin Waldenvik  wrote:



Thank you so much Guo-Rong for your help. When i changed from:
Ciphers 
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr

to Ciphers 
aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr

I get full speed. I am so happy for this.


I'm curious about one thing.  Are your ciphers on FreeBSD pre-set to the 
reduced list (i.e. no chacha) by default?  Or does chacha20 run faster on 
FreeBSD?

Thanks,
Dan



Hi Dan

I have used those ciphers in that order on all my servers and it works in full 
speed i both freebsd and linux but not in Omnios.

I have configured my ssh-servers as recommended here:

https://stribika.github.io/2015/01/04/secure-secure-shell.html


Can you provide the output of 'ssh -Q cipher' from both your FreeBSD and OmniOS 
boxes?

/dale



Hi

Seems to be the same

Omnios box - ssh -Q cipher
3des-cbc
blowfish-cbc
cast128-cbc
arcfour
arcfour128
arcfour256
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-...@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-...@openssh.com
aes256-...@openssh.com
chacha20-poly1...@openssh.com


FreeBSD box - ssh -Q cipher:
3des-cbc
blowfish-cbc
cast128-cbc
arcfour
arcfour128
arcfour256
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-...@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-...@openssh.com
aes256-...@openssh.com
chacha20-poly1...@openssh.com

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Dale Ghent]

> On Oct 12, 2016, at 10:45 AM, Martin Waldenvik  wrote:
> 
> On 10/12/2016 04:37 PM, Dan McDonald wrote:
>> 
>>> On Oct 12, 2016, at 10:21 AM, Martin Waldenvik  wrote:
 
>>> Thank you so much Guo-Rong for your help. When i changed from:
>>> Ciphers 
>>> chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
>>> 
>>> to Ciphers 
>>> aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
>>> 
>>> I get full speed. I am so happy for this.
>> 
>> I'm curious about one thing.  Are your ciphers on FreeBSD pre-set to the 
>> reduced list (i.e. no chacha) by default?  Or does chacha20 run faster on 
>> FreeBSD?
>> 
>> Thanks,
>> Dan
>> 
> 
> Hi Dan
> 
> I have used those ciphers in that order on all my servers and it works in 
> full speed i both freebsd and linux but not in Omnios.
> 
> I have configured my ssh-servers as recommended here:
> 
> https://stribika.github.io/2015/01/04/secure-secure-shell.html

Can you provide the output of 'ssh -Q cipher' from both your FreeBSD and OmniOS 
boxes?

/dale
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Martin Waldenvik]

On 10/12/2016 04:37 PM, Dan McDonald wrote:



On Oct 12, 2016, at 10:21 AM, Martin Waldenvik  wrote:



Thank you so much Guo-Rong for your help. When i changed from:
Ciphers 
chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr

to Ciphers 
aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr

I get full speed. I am so happy for this.


I'm curious about one thing.  Are your ciphers on FreeBSD pre-set to the 
reduced list (i.e. no chacha) by default?  Or does chacha20 run faster on 
FreeBSD?

Thanks,
Dan



Hi Dan

I have used those ciphers in that order on all my servers and it works 
in full speed i both freebsd and linux but not in Omnios.


I have configured my ssh-servers as recommended here:

https://stribika.github.io/2015/01/04/secure-secure-shell.html

Regards
Martin
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] problem with boot-archive after upgrade

[Dale Ghent]

> On Oct 11, 2016, at 6:03 PM, Jeff Stockett  wrote:
> 
> I upgraded a system from 012 to 018 just now and everything went totally 
> smoothly – system rebooted fine.  However, the boot environment names weren’t 
> what I wanted and since beadm can’t rename the active one, I create a new 
> one, activated it, and rebooted again.  On reboot this second (and subsequent 
> times), I’m getting this in /var/src/log/system-boot-archive:default.log:
>  
> [ Mar 20 14:25:01 Executing start method ("/lib/svc/method/boot-archive"). ]
> cannot find: /etc/cluster/nodeid: No such file or directory
> cannot find: /etc/devices/mdi_ib_cache: No such file or directory
> cannot find: /etc/devices/retire_store: No such file or directory
> [ Mar 20 14:25:50 Method "start" exited with status 0. ]
> [ May 18 05:20:09 Enabled. ]
> [ May 18 05:20:14 Executing start method ("/lib/svc/method/boot-archive"). ]
> [ May 18 05:21:15 Method or service exit timed out.  Killing contract 16. ]
> [ May 18 05:21:15 Method "start" failed due to signal KILL. ]
>  
> The system eventually comes up to a single user mode login, and if I login as 
> root, and enter “svcadm clear system/boot-archive” and/or maybe just wait a 
> while longer, then logout the system eventually comes up and works fine in 
> multi-user mode, but I was wondering if there is an easy way to fix whatever 
> I’ve done to shoot myself in the foot here?  I tried “bootadm update-archive” 
> but that doesn’t appear to fix it.

When you manually ran 'bootadm update-archive' did it give you any output such 
as "updating..." , or did it silently exit?

If the latter, do something like 'touch /etc/system' first, then run it, as 
bootadm will regenerate the boot archive only if it detects any changes in the 
files its concerned with. And yes, I've seen this same problem you speak of on 
rare occasion, with a rebuild of the boot archive being the cure.

/dale

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Slow ssh transfers

[Dan McDonald]

> On Oct 12, 2016, at 10:21 AM, Martin Waldenvik  wrote:
>> 
> Thank you so much Guo-Rong for your help. When i changed from:
> Ciphers 
> chacha20-poly1...@openssh.com,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
> 
> to Ciphers 
> aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
> 
> I get full speed. I am so happy for this.

I'm curious about one thing.  Are your ciphers on FreeBSD pre-set to the 
reduced list (i.e. no chacha) by default?  Or does chacha20 run faster on 
FreeBSD?

Thanks,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool

[Natxo Asenjo]

hi,

There is  a w10 system at the home and it's a bit critical for the wife
;-), so I want to have this up and running asap if some kind of trouble
happens with it.

Anyway, this windows 10 OS has a backup tool that allows you to dump an
image to a network share using cifs, obviously.

So I have a zfs file system, shared it for cifs, set the permissions for
the share. Start the backup, and it will fail consistently when it has
reached 57%.

After much searching, I found this:
https://social.technet.microsoft.com/Forums/windows/en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup-win7-file-recovery-system-image-creation-to-nas-device-fails-with-error?forum=w8itprogeneral

And yes, after:

# sharectl set -p max_protocol=1 smb

and restarting the cifs service, now the backup is running correctly (97%
and counting).

Apparently it has to do with 'resilency support', whatever that may be:

https://support.microsoft.com/en-us/kb/2920193

Which is a shame, because now the cifs host is limited to smb 1.5 instead
of 2.1 (but at least it works).

Hopefully I spare somebody some unnecessary pain with this info. And it
would be awesome if this 'resiliciency support' made it to the cifs server
in a next version ;-)

Thanks!

--
Groeten,
natxo
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss