NexentaStor Release Notes 4.0.4
Date: September 2015 Subject: NexentaStor Release Notes Software: NexentaStor Software Version: 4.0.4 Part Number: 7000-nxs-4.0.4-000017-B
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED www.nexenta.com NexentaStor Release Notes 4.0.4
Copyright © 2015 Nexenta SystemsTM, ALL RIGHTS RESERVED
Notice: No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose, without the express written permission of Nexenta Systems (hereinafter referred to as “Nexenta”).
Nexenta reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Nexenta products and services only can be ordered under the terms and conditions of Nexenta Systems’ applicable agreements. All of the features described in this document may not be available currently. Refer to the latest product announcement or contact your local Nexenta Systems sales office for information on feature and product availability. This document includes the latest information available at the time of publication.
Nexenta, NexentaStor, NexentaEdge, and NexentaConnect are registered trademarks of Nexenta Systems in the United States and other countries. All other trademarks, service marks, and company names in this document are properties of their respective owners.
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ii www.nexenta.com NexentaStor Release Notes 4.0.4
Contents
What is New in this Release? ...... 1 Recommendations ...... 2 VAAI Block Changes ...... 3 Warning about upgrading without preparation ...... 4 Planning for upgrade ...... 5 Identifying VMFS datastore extents and checking ATS status ...... 5 Disabling ATS on Existing Datastores ...... 6 Enabling ATS on Existing Datastores ...... 7 Enabling ATS on NexentaStor ...... 8 Reverting to pre-FP3 checkpoints ...... 8 IPMI Support ...... 9 Determining the Version of the Appliance ...... 9 System Requirements ...... 9 List of SMB Supported Client Operating Systems ...... 9 Upgrading ...... 11 Upgrading Minor Versions of NexentaStor 4.0.x ...... 11 Change in NMV Port ...... 11 Upgrading from Version 3.1.x to 4.0.4 ...... 11 Upgrading from Latest Version of 3.1.6 to 4.0.4 with an Internet Connection ...... 12 Upgrading from Latest Version of 3.1.6 to 4.0.4 without an Internet Connection ...... 14 Upgrading to Version 4.0.4 After Rolling Back to Latest Version of 3.1.6 ...... 14 Enhancements ...... 16 Resolved Common Vulnerabilities and Exposures (CVE) ...... 17 Resolved Issues ...... 18 Known Issues ...... 21
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED iii www.nexenta.com
1 Known NexentaStor Release Notes 4.0.4 Notes Release NexentaStor now fully certified for now fullycertified for -Sync user guide for more more user guide for -Sync for more details. Known Issues Known tar and block services issues to refactor the block tor 4.0.4, NexentaStor is NexentaStor 4.0.4, tor e Channel using Emulex LPe16002 HBAs. Please see Please HBAs. LPe16002 using Emulex e Channel y to change snapshot ownership, formally allowing allowing formally snapshot ownership, change y to events in typical large scale VMware environments. environments. VMware scale large typical in events ns a number of functionality enhancements exposed exposed ns a number of functionality enhancements that ZFS record sizes of 32KB and above help in help above 32KB and of sizes record ZFS that
ary site. See NMV ary site. and Auto the ee the VMware Storage Compatibility Guide for more more Compatibility Guide for Storage VMware the ee gnificant improvements in the areas of general stability, stability, general of in the areas improvements gnificant doing parallel deletes of large files. of large deletes parallel doing found internally by Nexenta Engineering since 4.0.3. The 4.0.3. since Engineering Nexenta by internally found bre Channel and Channel iSCSI block services. bre lt addresses a large number of known issues and delivers dramatic dramatic and delivers known numberissues of large a lt addresses c snapshots. It also enhances failback capabilities, removing the need need the removing capabilities, failback enhances It also snapshots. c section Nexenta engineering took a holistic view of known Coms of known view a holistic took engineering Nexenta 4.0.4. The resu NexentaStor in stack improvements in reliability of both Fi reliability in improvements VMware certification for VAAI Block services VAAI for certification VMware With NexentaS in the Fibre changes iSCSI and Channel VMware VAAI Block for ESXi 5.5 and ESXi 6.0.S ESXi and 5.5 ESXi Block for VAAI VMware details.more details For in support ESXi the6.0, intermsNEX-3648 ofNexentaStor for review Issues In addition to changes in 4.0.4, testing has shown has 4.0.4, in testing changes to In addition when APD of events instances mitigating engineeringNexenta is actively workingon this ofadditionalZFS and area expect we have to scalability under See NEX-3890 Fix in upcoming Packs. improvements Previous releases of NexentaStor have exhibited performance challenges when having to delete large large delete to having when challenges performance exhibited have NexentaStor of releases Previous by VM from deletions be triggered issue can that environments, once. In VMware at of data amounts virtualmachines. affecting Down) events APDand (All as exhibits itself Path datastores mounted the ability handle to deletes improving enhancements ZFS a number of core 4.0.4 contains NexentaStor APD of occurrence the and minimizing files large of the creation of clones from auto-syn from of clones the creation failing the back prim to before do a fullto resync details. HBAs FC 16Gbps LPe16002 Emulex for Support 4.0.4 has been certified with 16Gbps FibrNexentaStor supportingthis HBA. configurations Compatibility for List Hardware the latest in NMV. Specifically, NexentaStor 4.0.4 adds the abilit4.0.4 adds NexentaStor Specifically, NMV. in Auto-Sync reliability and functionality extensions reliability functionality and Auto-Sync a number of addressing to addition In usability Auto-Sync and reliability. 4.0.4 improves NexentaStor in 4.0.4 contai Auto-Sync issues, reported customer • Fibre and iSCSI Block services Channel hardening • • file ZFS scalability delete improvements • • Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com What is New in this Release? is New What si delivers that update maintenance is a 4.0.4 NexentaStor scalability and performance. NexentaStor 4.0.4 builds on all the fixes previously released as of version 4.0.3-FP4 of version and as released previously 4.0.4 buildsall onfixes the scalability NexentaStor and performance. issues as well as issues, reported customer addresses highlighting: worth are and enhancements changes following
nfsd and lockd threads threads lockd and nfsd alability ensure that you increase the nfsd the nfsd alabilityincrease you that ensure MP manager is available in NexentaStor. The in NexentaStor. MP is available manager bre Channel ports and will automatically and will automatically Channel ports bre t for the following storage enclosures: enclosures: storage following the t for the maximum number of number the maximum for more for details. Nexenta Support Nexenta Log in to NMC. Log in to Type: nmc:/$ setup network service nfs-server configure nfs-server service setup network nmc:/$ nmc:/$ Option ? configure To change the NFS settings, using NMC: using settings, NFS the change To 1. 2. With the newly released MetroHA support for NexentaStor 4.0.4, the capability to create create to 4.0.4, the capability NexentaStor support for MetroHA With released newly the to added been has distance metropolitan a over stretch that clusters available highly 4.0. NexentaStor With the release of 4.0.4, the defaults for for 4.0.4, the defaults of With release the to handle larger willallowThis256. NexentaStor increase 16 to from increased been have requests. NFS concurrent number of when 16, was 4.0x NexentaStor of versions earlier in threads lockd and nfsd default As the will threads of NFS older settings 4.0.4 earlier versions,the from to NexentaStor upgrade you and sc performance NFS improve To be retained. and lockd thread counts. No changes are required in the case of fresh installation of 4.0.4. installation fresh of in the case required are changes No counts. thread and lockd With the release of NexentaStor 4.0.4 a new SN new 4.0.4 a of NexentaStor With the release Fi front-end monitors now 4.0.4 NexentaStor • Dell/Compellent SC280, enclosure 84 bay SP2584, enclosure 84 OneStor bay • Seagate enclosure 44 bay SMC-847E2C, • Supermicro enclosure bay 24 SC216BE2C, • Supermicro available. is now VSS Microsoft with 4.0.4 NexentaStor integrating for provider A plug-in Contact SNMP manager can now listen and act on SNMP traps received from external systems. This systems. external from received SNMP traps on and act listen now can SNMP manager can be used to automate a NexentaStor appliance and have it react to traps generated by center in a data other systems a on ports all front-end of failure concurrent a of event in the fail-over controller trigger controller. managemen chassis adds 4.0.4 NexentaStor • Campus/Metropolitan Support clusters for • NFS settings • NFS • Copy Shadow Services (VSS) Volume Microsoft for provider New • information trap SNMP display to available Manager SNMP New • Fibre of ports Channel monitoring RSF • Chassis Management updates Management • Chassis Recommendations Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ALL RIGHTS Systems, Nexenta 2015 © Copyright www.nexenta.com NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 2
3 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor to VAAI support. comes t disabled by default. In default. by t disabled NFS connectivity issues on issues connectivity NFS ts VMFS locking mechanism ts VMFS locking VAAI enabled at the ESXi level to Configure > ires some planning when it when planning ires some also ships with VAAI supporVAAI also with ships aStor deployed in VMware ESXi environments, you you environments, ESXi in VMware deployed aStor access to the datastore. ESXi enables ATS by default om a storage system disrup storage system om a 4 system, the user will have to first enable the enable the first 4 system, the user will have to ’ and make appropriate changes on the ESXi server. ESXi the on changes appropriate ’ and make that do provide that functionality. provide do that NFS Server NFS > eld, change the value of the maximum number of concurrent NFS NFS of number of the maximum eld, change the concurrent value in the VMware KnowledgeBase article ' KnowledgeBase in the VMware level guidance, based on starting NexentaStor version to get to a to get to NexentaStor version starting on based level guidance, wing ESXi environments to run with to ESXi environments wing Shares > VAAI fully enabled. Data Management Data nmc:/$ Server Version : 4 Version Server nmc:/$ : 4 Version Client nmc:/$ : 32 Servers NFSD Concurrent nmc:/$ servers. NFSD the of number concurrent Increase Go to Go to In the Concurrent NFSD Servers fi Servers NFSD In the Concurrent requests. To change the NFS settings, using NMV: using settings, NFS the change To 1. 2. NetApp NFS filers on ESXi 5.x/6.0 (2016122) 5.x/6.0 on ESXi filers NFS NetApp Regardless of what version of 4.0.x you are upgrading from, or what it's defaults were, the customers customers the were, defaults it's what or from, upgrading are 4.0.x you of version what of Regardless by or changed default were if settings Meaning, during regardless will the upgrade. settings be retained it will remain upgrade prior to disabled VAAI had if you manipulation customer; byactive of settings enabled. was if setting versa vice upgrade; after disabled should review the settings proposed proposed settings the should review To prevent NFS connection issues with any Nexent any with issues connection NFS prevent To Removing Atomic Test and Set (ATS) functionality fr functionality Set (ATS) Test and Atomic Removing benefit from backend systems benefit other storage While NexentaStor 4.0.4 is fully VAAI Block certified, it order to use VAAI Block on 4.0. a fresh NexentaStor NexentaStor. on functionality Upgradinga previous version from of NexentaStor requ for datastores that have it enabled and causes loss of enabled and it have that datastores for VMware environment with on creation with VMFS5. on creation with that: consider planning an upgrade, When • default. byenabled with VAAI included FP2 shipped up to 4.0.3 versions NexentaStor • by default. disabled with ship FP3 4.0.3 and with later VAAI version NexentaStor some high The following table provides Fix Pack 3 and above for NexentaStor 4.0.3 have all VAAI support disabled by default. This was done to to done was This default. by disabled support VAAI have all 4.0.3 NexentaStor for above and 3 Pack Fix allo while still data protect customer • ESXi settings • ESXi VAAI Block Changes VAAI Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com
Enabling Enabling https:// faults without faults first iple hosts, you should ies section. See section ots applyingby configuration by by but VMware not in the vSphere client datastore datastore the vSphere client in are on the system at upgrade. A vaaictl A vaaictl systemare at upgrade. on the S-only locking fail to mount after mount after fail to S-only locking open support cases with VMware VMware cases with open support 1 1 can minimize rebo minimize can upgrade that changes de ided here summarize information provided in you revert to the previously running snapshot, snapshot, the previously running you revert to in the NexentaStor Utilit in the NexentaStor tastores mounted by mult tastores orming the preparatory steps outlined below, outlined below, steps the preparatory orming es to be consistent with the newdefaults. es to commended to consult the original documents. original consult the to commended by Nexenta in consultation with VMware: disable ATS documented they will take effect if the settings the settings if effect take they will to disable and do not show not show up do and to disable tor requires a reboot. You used to enable VAAI features. Download the vaaictl script from script from vaaictl features. Download the VAAI enable used to Procedure on NexentaStor 1. Enable ATS NexentaStor 2. Upgrade on NexentaStor 1. Enable ATS NexentaStor 2. Upgrade servers ESXi on existing ATS 3. Re-enable , datastores configured to use AT use to configured datastores , ese procedures, you should first ese procedures, Nexenta as joint support. as joint Nexenta andsupport open casewith a VMware as necessary,given following the for more details. details. more for 2037144 2094604
The combination of one host using ATS-only and another host using SCSI Reserve/Release Reserve/Release SCSI using host another and ATS-only using host one of The combination corruption. in filesystem result might To change ATS settings on NexentaS Upgrading from Upgrading 4.0.3 FP2 or earlier or earlier FP2 4.0.3 version version or later FP3 4.0.3 script, provided by Nexenta, may be and then, as needed, with as and then, changes before upgrading before upgrading changes your system, as view. In this situation Nexenta recommends that Nexenta situation view. In this the change in thereby reverting defaults, perf then returning to the upgrade checkpoint. then returning If you are running ESXi 6.0 with multi-extent da consult KB consult In case of any issues with th of any case In an both recommend against Nexenta VMware and 1033665 2006858 2030416 2094604 KB As per VMware ATS on NexentaStor ATS proceduresThe and background information prov 1 nexenta.com/products/downloads/nexentastor are re You VMware knowledge base articles. were reviewedarticles KB The following configuring ATS datastor affected locking for This can result from other procedures to other procedures result from This can notice in that KB: that in notice 2037144 an upgrade that changes defaults an upgrade that changes defaults Warning about upgrading without preparation about upgrading Warning Table 2-1: Steps to enable VAAI enable to VAAI 2-1: Steps Table Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ALL RIGHTS Systems, Nexenta 2015 © Copyright www.nexenta.com NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 4
5
NexentaStor Release Notes 4.0.4 Notes Release NexentaStor
orage from more than one orage from more than
g into the ESXi console and type the ESXi console g into esxcli storage core device device core storage esxcli Name Name what is also termed “tech support what is support termed “tech also Device Device
irm appropriate procedures and identify and procedures irmappropriate Number using extents backed by st using extents backed ures assume that a datastore uses extents backed backed uses extents datastore a that ures assume t cases with Nexenta and other storage storage vendors as other and Nexenta t cases with epare for upgrades on ESXi hosts and complete complete and hosts for upgrades on ESXi epare Extent
including others from the listed KBs. the listed from others including
, the datastore must be inactive (guests must either be migrated be migrated either must be inactive (guests must datastore , the
entify which extents they use, lo they which extents entify
(ssh into the ESXi host(s), using ESXi host(s), (ssh into the by a NexentaStor block device, use "
2030416
UUID UUID en a support case with VMware to conf with VMware case en a support ", as in our example: ", VMFS VMFS
Name Name 3 ~ # esxcli storage core device list -d naa.600144f0c140cf6e0000546fca5d0002 list device storage core esxcli ~ # naa.600144f0c140cf6e0000546fca5d0002 Disk Channel Fibre Name: NEXENTA Display (naa.600144f0c140cf6e0000546fca5d0002) true Name: Display Has Settable Size: 2097152 Direct-Access Device Type: NMP Plugin: Multipath /vmfs/devices/disks/naa.600144f0c140cf6e0000546fca5d0002 Devfs Path: NEXENTA Vendor: Model: COMSTAR 1.0 Revision: 5 SCSI Level: false Is Pseudo: on Status: ~ # esxcli storage vmfs extent list extent storage vmfs esxcli ~ # Volume Partition ------0 546fcc0f-d40379dd-5ae5-002590daef96 ham01-zv01 1 naa.600144f0c140cf6e0000546fca5d0002 0 53b43e1d-d4ab8871-1a8d-002590daef96 lrtsesx01-ds-01 t10.ATA_____ST1000NM00332D9ZM173______Z1W11CAL below steps. To confirm that an extent is backed extent an that confirm To exclusively by NexentaStor LUNs. In case of datastores exclusively by NexentaStor supporrisk, opening joint sources of possible further console the ESXi from the following -d
d is set to NEXENTA. NEXENTA. to is set d vmkfstools -Phv1 / -Phv1 vmkfstools : introduce issues in the environment. Instead Instead in the environment. issues introduce 2006858 disable it only for the affected LUN without LUN affected the only for it disable because the Vendor fiel the Vendor because ds disabling ATS on a per-device basis, basis, per-device ATS on a ds disabling the datastore is not configured to use ATS. use to configured not is the datastore line indicates that the datastore is configured to use ATS. If use ATS. If is configured to datastore the line indicates that NextaStor-exported extents, use " extents, NextaStor-exported " to confirm that ATS is enabled, as in our example: as ATS is enabled, that confirm " to Disabling VAAI entirely on the ESXi host may may host on the ESXi entirely Disabling VAAI be can you all devices, for of disabling VAAI LUNs. other impacting ~ # vmkfstools -Phv1 /vmfs/volumes/ham01-zv01 -Phv1 ~ # vmkfstools partitions. 1 spanning system file VMFS-5.60 ham01-zv01 (if any): label File system ATS-only Mode: public size max file file block size 1 MB, GB available, Capacity 2 TB, 725.6 62.9 TB 2014 23:34:39 Nov 21 Time: Fri Creation Volume 130000/129619 Files (max/free): 64512/63162 (max/free): Ptr Blocks 32000/31911 (max/free): Sub Blocks 256/256 (max/free): Blocks Ptr Secondary %): 0/1353841/0 (overcommit/used/overcommit File Blocks %): 0/1350/0 (overcommit/used/overcommit Ptr Blocks %): 0/89/0 (overcommit/used/overcommit Sub Blocks Volume Metadata size: 814383104 UUID: 546fcc0f-d40379dd-5ae5-002590daef96 (on "lvm"): spanned Partitions naa.600144f0c140cf6e0000546fca5d0002:1 YES Capable: Snapshot Is Native done. cleanup ObjLib OBJLIB-LIB: Is RDM Capable: true Capable: Is RDM false Is Local: false Is Removable: false Is SSD: false Is Offline: false Reserved: Is Perennially 0 Size: Full Sample Queue 0 Full Threshold: Queue yes Status: Provisioning Thin Filters: Attached unknown Status: VAAI UIDs: Other vml.0200010000600144f0c140cf6e0000546fca5d0002434f4d535441 false Device: SAS Is Local false Is USB: false Device: USB Is Boot 32 worlds: with competing IOs outstanding No of vmfs/volumes/
7 ", as in our as ", sulting problems NexentaStor Release Notes 4.0.4 Notes Release NexentaStor the upgrade, checking VMware, requesting joint VMware, requesting joint check in case re case in check to confirm the change of settings: of the change confirm to to confirm the change of settings: of the change confirm to ”. open a support case with a support open store, you may proceed with you may store, orage and their check ATS status, see the section orage and orage and their check status, ATS see the section provides a list of symptoms to to of symptoms list provides a 2006858 tents and checking ATS status”. and checking ATS tents the following output, including a prompt output, the following the following output, including a prompt including output, the following vmkfstools --configATSOnly 0 /vmfs/devices/disks/
https:/ s, changing the vaaictl s, r ATS see status, the . they will take effect if the effect if will take they utable by setting the execution the utable by setting above steps have preparatory been provides a list of symptoms to check in k current settings using this invocation, which invocation, settings using this k current in the NexentaStor Utilities section. Copy the section. Copy NexentaStor Utilities the in follow the previous the follow step ded to open a support ded to open case VMware, with a support datastore, you may proceed with the upgrade, datastore, r storage and check thei es a reboot. You can by minimize reboots features. Download the vaaictl script from script from Download the vaaictl features. 2006858 ng the system to follow product defaults again: defaults follow product ng the system to anged without a system reboot, which means that which means that reboot, system without a anged ailability are suspected or apparent. suspected or are ailability as admin and run the following script: fore upgrading your system, as system, your upgrading fore and make sure that it and make sure is exec that it revert defaults. revert defaults. As long as the g system are uncertain: Identifying VMFS datastore extents and checking ATS status ATS checking and extents datastore VMFS Identifying # -bash-4.2$ sudo ./vaaictl --disable ./vaaictl sudo # -bash-4.2$ --status ./vaaictl # -bash-4.2$ # -bash-4.2$ chmod 555 ./vaaictl chmod # -bash-4.2$ --enable ./vaaictl sudo # -bash-4.2$ --default ./vaaictl sudo # -bash-4.2$ 0) _Yes 1) _No 0 from 0-1: a number Select system. file as a valid device this are using hosts if remote Checking few seconds... take a This may from on 'naa.600144f0c140cf6e0000546fca5d0002:1' VMFS-5 Downgrading ATS capability...done script to admin’s home directory, home to admin’s script case resulting problems with storage av with resulting problems case will warn you if the config file has been ch has file config the if you will warn settings on the runnin Reverting checkpoints will All settings changes require reboot. You can chec All settings changes require reboot. checking guest I/O afterwards. VMware KB VMware guest I/O afterwards. checking section restore defaults, allowi either to invocation or to disableexplicitly: To apply changes, ssh into the device the into To apply changes, ssh can disable VAAI thereafter, you to If you need requesting joint support from Nexenta as appropriate. as Nexenta from requesting joint support for the enabled ATS-only mode has been Once /nexenta.com/products/downloads/nexentastor To identify VMFS datastores using NexentaSto using To identify VMFS datastores In case of any other output, you are recommen you other output, of any case In To change ATS settings on NexentaStor requir NexentaStor ATS settings on To change upgrade. system at the settings are on VAAI enable may be used to The vaaictl script applying configuration changes be applying configuration mode of file: the Reverting to pre-FP3 checkpoints pre-FP3 to Reverting Enabling ATS on NexentaStor Enabling ATS Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ALL RIGHTS Systems, Nexenta 2015 © Copyright www.nexenta.com NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 8
9 ses, you can use can ses, you NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workgroup Mode ating Systems that have Systems that ating ring. In such ca ring. the permissions specified in the the in the permissions specified Windows Server 2003 Windows Windows Server R2 2003 Controllers and client Oper Controllers tor. You can determine the version of the appliance the version of determine You can tor. fer to the “System Requirements” section in the section Requirements” the “System fer to ing the Server Message Block (SMB) protocol if protocol (SMB) Message Block ing the Server Windows Windows Server 2008 t traditional SES-based JBOD monito and has an active machine account. machine account. active has an and te the domain users according to users according to te the domain with ATS-only locking disabledwill continue be accessible.to r traditionalSES-based monitoring. Windows Windows R2 Server 2008 . Windows Windows Server 2012 Windows Windows R2 Server 2012 X X X X X X X Type: version appliance show nmc:/$ response: System 40-0-47 version: NMS 40-0-39 version: NMC 40-0-45 version: NMV 2015 June 20 Date: Release To determine the version of the appliance using using NMC: of the appliance version the determine To IPMI as fo monitoring a substitute Network clients can access files on NexentaStor us Network clients can access files on NexentaStor can properly authentica NexentaStor For system requirements for each environment, re environment, each requirements for For system NexentaStor Installation Guide Installation NexentaStor to which NexentaStor is joined domain of Domain versions The following table describes the work with NexentaStor. successfully tested to been 4.0.4) (version Nexenta/illumos System: Operating NexentaStor 4.0.4 is the current release of NexentaS NexentaStor using NMC. Some storage vendors no longer suppor longer vendors no Some storage successfully completed, datastores completed, successfully Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Windows Windows 2012 R2 Table 2-2: SMB 2-2: CompatibilityMatrix Table List of SMB Supported Client Operating Systems Operating Client of SMB Supported List System Requirements System Determining the Version of the Appliance of the Version Determining IPMI Support
Workgroup Mode Windows Windows Server 2003 Windows Windows R2 Server 2003 Windows Windows Server 2008 ed with the indicated Domain Controller. with the indicated ed Windows Windows R2 Server 2008 Windows Windows Server 2012 X X X X X X X XX XXX X X XX XXX X XX X XXX X XX XXX X X X N/S N/S N/S N/S X X X X X X X X X X X X X X X X X X X X X X X Windows Windows R2 Server 2012 entOS 6.5 entOS Red Hat/ С Windows XPWindows Windows X2003 X X X X X X Windows 8 X X X X X X X 8 X X X X X X X 7 Windows Windows 2012 Windows 2008 R2 Windows Windows 2008 Windows 2003 R2 Ubuntu 12.04 Ubuntu LTS X OS Mac 10.9.2 N/S represents those OSs that are not test not are OSs that those represents N/S Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ALL RIGHTS Systems, Nexenta 2015 © Copyright www.nexenta.com NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 10
11 out an Upgrading Upgrading , NexentaStor Release Notes 4.0.4 Notes Release NexentaStor . ith an Internet Connectionith an Internet w 4 Upgrading Minor Versions of NexentaStor of NexentaStor Minor Versions Upgrading o 4.0. t ith an Internet Connection ith an Internet w services and volumes are not available during the not available are and volumes services 3.1.6 3.1.6 king vendors, Nexenta registered the port 8457 with 8457 the port registered Nexenta king vendors, 4 s remain available to network clients. The upgrade upgrade The clients. network to available s remain of recommended that the upgrade process be scheduled be scheduled process upgrade the that recommended Upgrading from Latest Version of 3.1.6 to 4.0.4 with 4.0.4 to 3.1.6 of Version Latest from Upgrading nternet Connection nternet o 4.0. t 4.x, NMV is now accessed by port 8457. NMV 4.x, is now accessed Version 3.1.6 out an I out of of Latest Latest V port has been changed to 8457. to changed been V port has of NexentaStor 4.0.x, see: Version Latest Latest Upgrading from from Upgrading , Upgrading from from Upgrading nmc:/$ setup appliance upgrade appliance setup nmc:/$ Type: Upgrade to the latest version of 3.1.6. of version the latest to Upgrade of 4.0.3. version latest to Then, upgrade 4.0.4 to Then, upgrade See x To upgrade the appliance 4.0.4 from to 4.0.xor4.0.3 FPx releases: To nternet Connection nternet 1. Upgrading NexentaStor from version 3.1.x to 4.0.4 is a three-step process. First you need to upgrade to the to upgrade to need you First process. 4.0.43.1.x is a three-step to version from NexentaStor Upgrading 4.0.4. 4.0.3 then and to latest to 3.1.6and of then upgrade version latest 1. 2. 3. In NexentaStor 4.0.x, the default NM the default 4.0.x, In NexentaStor with other networ conflicts potential avoid to In order port and port 2000 uses default the uses no longer 4.xweb access and above, releases Nexenta IANA. For 3.x to release from upgrading when Note 8457. from Latest Version of 3.1.6 to 4.0.4 with to 3.1.6 of Version Latest from command. a single with FP releases 4.0.3 or from release 4.0.x Version from upgrade can You To upgrade between minor versions To 4.0. see to 4.0.x, upgrade from 3.1.x NexentaStor To I operation requires system restart. Therefore, it is Therefore, restart. system requires operation During the upgrade, NexentaStor services and volume and services NexentaStor During the upgrade, NexentaStor All window. maintenance duringsystem a restart. Upgrading from Version 3.1.x to 4.0.4 3.1.x to Version from Upgrading Change in NMV Port Change Upgrading Minor Versions of NexentaStor 4.0.x of NexentaStor Versions Minor Upgrading Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Upgrading
Partner Partner show show or Customer Portal Portal Customer setup nexentastor nexentastor setup lt in the loss of components that are not not are that lt in loss of components the e hardware compatibility list for NexentaStor of all available checkpoints by using ‘ by using checkpoints available of all changes, visit the respective t meets the following prerequisites: following the t meets ’ command or proceed with 4.0.4 upgrade. 4.0.4 with proceed or ’ command . Running this command will automatically disable the multi-NMS disable the will Running this command automatically . setup appliance upgrade appliance setup setup appliance upgrade appliance setup and provide the following to obtain the new license key. new license the obtain the following to and provide upgrade -r
13 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor setting is not maintained, and must be reset be reset and must is not maintained, setting you have incomplete archiving tasks. Otherwise, Otherwise, tasks. archiving incomplete have you ing NexentaStor 3.1.6 after the first stage of the stage the first 3.1.6 after ing NexentaStor may not be available after the upgrade. after be available not may . View nfsmapid_domain nfsmapid_domain . or restart the NexentaStor appliance. the NexentaStor or restart ooting, all NexentaStor services and datasets are unavailable for for unavailable are and services datasets ooting, all NexentaStor pane, click , log in to bash: to , log in Settings > Appliance > Settings for all NexentaStor volumes all NexentaStor for Upgrade Checkpoints nfsmapid_domain nfsmapid_domain nfsmapid_domain Step 10Step After you upgrade the volume version, back up your system. Backups created for for created Backups system. your back up version, volume the upgrade you After versions volume with earlier pools mirrored In NMV, click In NMV, In the nmc:/$ option expert_mode =1 expert_mode option nmc:/$ To set the the set To nmc:/$ setup volume
Version . . If you try . If you ith an file and run file run and w Latest Latest 4 o 4.0. t 3.1.6 3.1.6 of Upgrading from from Upgrading Version Latest Latest NexentaStor HA Cluster User Guide User HA Cluster NexentaStor /volumes/.config/.3_to_4_upgrade /volumes/.config/.3_to_4_upgrade you upgrade the volume version during the upgrade to to during the upgrade version the volume upgrade you . Then verify that your environment meets all prerequisites all prerequisites meets environment your that Then verify . Upgrading from from Upgrading in out an Internet connection, review command again. again. command for the ISO image. for . Step 11Step to Step 2 Step To upgrade the HA Cluster plugin, see: plugin, HA Cluster the upgrade To ith an Internet Connection ith an Internet nmc:/$ !bash nfs nfsmapid_domain=
15 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor setup appliance upgrade setup appliance nmc:/$ setup nexentastor upgrade -r 4.0.3 -r upgrade nexentastor setup nmc:/$ # exit
ync snapshot sources. k runner ival_anti_flapping setting to address address to setting k runner ival_anti_flapping ior to deleting Auto-s ior to plication by auto-tier for Microsoft Active Active Microsoft for by auto-tier plication ging snapshot ownership for Auto-services. for ownership ging snapshot fixes #5376, #5498, and #5514. #5376, fixes Description intervention. Directory. possible false values being reported JBODby sensors. beingpossible reported values false with MIT KDCs. interoperating once. NEX-1099 administrative require always to list runners the faulted clearing for behavior Changed NEX-1160 NFS. with use for NIS client of management appliance Provided NEX-1955of the ses-chec value the default Changed NEX-3082 port Added monitoringFC status to RSF. NEX-3134 functionality Enhanced of the SNMP traps. NEX-3145pr response user confirmation a Added NEX-2510 population keytab and creation principal for support client Kerberos NMC Enhanced NEX-2694same tray. the from disks using two prevent to logic pool creation Updated NEX-2788 chan for 3.x functionality Restored NEX-2951 re ACL for 3.x functionality Restored NEX-2849 updates. driver Emulex Incorporated NEX-2865at multiple schedules Auto-snap to accommodate Auto-sync functionality Added to Key NEX-3663 Illumos kmem_reap Ported This section lists enhancements in NexentaStor 4.0.4. in NexentaStor enhancements lists This section Enhancements Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED ALL RIGHTS Systems, Nexenta 2015 © Copyright www.nexenta.com NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 16
17 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor nction in ntp_proto.c in ntpd in NTP in ntpd nction in ntp_proto.c alysis of ciphertext in a large number large in a of ciphertext alysis C only if the MAC field has a nonzero nonzero a has field only if the MAC C er for remote attackers to conduct conduct to attackers remote er for mod_deflate.c in the mod_deflate module in in the mod_deflate mod_deflate.c ty issue in httpd as such." as ty issue in httpd le in the Apache HTTP Server before 2.4.10 does not have not have 2.4.10 does HTTPle in the Apache Server before Description fu receive the in feature The symmetric-key MA a correct requires 4.2.8p2 4.x before packets spoof to man-in-the-middle attackers for it easier makes which length, the MAC. omitting by of denial a cause to attackers remote allows mechanism, which timeout a its from not read script does that CGI a to hang) via a request service (process file descriptor. stdin or service (crash) of denial a cause to man-in-the-middle attackers allows URL. via a crafted code arbitrary possibly execute in the by placing a header unset" directives "RequestHeader bypass to attackers the vendor NOTE: coding. transfer with chunked sent portion trailer of data "this is not a securi states of denial a cause to attackers remote allows mechanism, which timeout a its from not read script does that CGI a to hang) via a request service (process file descriptor. stdin is decompression body when request 2.4.10, HTTP before Apache Server the service denial of (resource a cause to attackers remote allows enabled, size. larger a much to decompresses that data request crafted via consumption) it easi whichmakes biases, single-byte an via statistical attacks plaintext-recovery of sessions that use the same plaintext. that of sessions CVE (CVE-2003-1418) The mod_cgid modu (CVE-2015-1798) (CVE-2015-1799) mod_cgid (CVE-2015-2781) The (CVE-2003-1418) (CVE-2014-6273) overflow Buffer in theHTTP transport inAPT code 1.0.1 apt-get in andearlier (CVE-2013-5704) remote HTTP2.2.22 allows Server Apache the module in The mod_headers (CVE-2014-0231) not have 2.4.10 does mod_cgid The HTTPmodule in the Apache Server before (CVE-2014-0118) in function The deflate_in_filter (CVE-2013-2566) many has andprotocol, SSL in the TLS protocol used algorithm, as The RC4 Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Resolved Common Vulnerabilities and Exposures Exposures and Vulnerabilities Common Resolved (CVE) 4.0.4. NexentaStor into incorporated been CVEs have The following
18 tolearn NexentaStor Release Notes 4.0.4 Notes Release NexentaStor displaying open files via Microsoft Microsoft via files open displaying What is New this in is New Release? What sulting in unresponsiveness to ESXi clients. ESXi to sulting in unresponsiveness Auto-sync service could timeout under under timeout service could Auto-sync ity of Auto-sync flip-direction mode. flip-direction of Auto-sync ity ble for flip-directions. ble for about the options availa about the options replicated. not snapshots were Exec. Backup Symantec Description Management Console Computer Management snap-in. Management Console Computer Management 3.1.x. from upgrade a seamless extensions. unresponsiveness. system could cause status. degraded to lead potentially hang and a possible fault. NMS. See Auto-sync User Guide or Guide User See Auto-sync certain conditions. reverse-service. logged each timenmwatchdog starts. NMV. settings. policy with the retention comply upgrade. Key NEX-2617 resolution DNS a to lead could configuring LDAP where issue Resolved NEX-3596 3.x functionality vianfsmapid_domain the allow setting to Restored This sectionThis describesfixed the issues in NexentaStor 4.0.4. Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area AutosysncCIFS NEX-3009CIFS that report incorrectly could nmwatchdog issue where Resolved NEX-3430 NEX-3576 when using fail could via SMB mount backups where issue Resolved when 1726 RPC error Resolved Appliance Management CommandsCOMSTAR NEX-3203COMSTARCOMSTAR NEX-2723 and install between a in inconsistency NTPfresh configuration Resolved Daemons NEX-2787 NEX-2862 handling with VAAI Enhanced used when commands of SCSI write NEX-2893 SCSI issuetarget Resolved re UNMAP issuing operations issue many where SCSI Target Resolved could cache configuration volume stale a issue where Addressed Appliance Management Autosync NEX-2385 the where issue Resolved AutoSyncAutoSync NEX-3167AutoSync NEX-3420AutoSyncwith issue changing running direction back after auto-sync Resolved NEX-3512AutoSync is $fmri" error value of uninitialized "Use where condition Resolved NEX-3531AutoSync in Auto-serviceslogs not refresh would rotated where case Addressed NEX-3573 didSnapshots" not properly Any "Destroy condition where Resolved NEX-3656 seamless after expire not does snapshot autosync 3.x, for Fixes the functional Corrected Resolved Issues Resolved
19 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor for further details. for during a volume import if the import a volume during failing to replace an unavailable drive drive an unavailable replace failing to uring an IP alias on top of a uring an VLAN IP on top alias Known Issues Known errors with certain anonymous access access anonymous with certain errors cloning vmdkthan450Gb files via larger r Illumos #4950 to address situation where where situation address r Illumos #4950 to sVMotion could occasionallyfail. between nodes. synchronizing hostnames. non-existent for DNS performing lookups RSF outage. brief a to pools, leading on existing services under See NEX-3890 deletes. Description initiators using standby ALUA path. using standby ALUA initiators with a hot spare. updated. directories and/or files could not be deleted from the FS once refquota once files the refquota FS could and/or not befrom deleted directories exceeded. was FS the on set or hostname changing the mode after settings. interface. hostname had been had hostname previously changed. boundaries. filesystem folder Key NEX-2591 not being appropriately was drives FRU field for issue where Resolved Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com HAHAHAHAHA NEX-2508 NEX-3049HA NEX-3085HA cache. by invalid caused memory RSF fault Addressed NEX-3161 IP addressing. virtual cluster between inconsistency Resolved NEX-3391Kernel control. cluster service under exporting when handling error Improved NEX-3405 servicein node cluster names. handling Corrected letters of uppercase not backup-globals was stmfha where condition Resolved SUP-949 NEX-1823 by could be caused delays condition during where a failover Resolved would restart control adding condition cluster a pool where to Resolved Illumosduring the#5911 minimize impact of I/Os large to Incorporated Functional Area FibreChannel NEX-3295 where condition Resolved KernelKernelKernel NEX-1825 chassis Kernel, management NEX-941 Windows discovery for LUN preventing condition SCSI target Resolved SUP-930 was ZFS issue where Resolved buffers. reused and freed by caused panic a Resolved Kernel, ProtocolsKernel, NEX-2936 fix fo Incorporated NFS NEX-2529 maintenance enter service may the NFS where condition Resolved NFSNMS NEX-3758 NEX-3018locks. stale of NFSv3 logging and detection Enhanced config functionality Added for NFSNFSNFS NEX-3019 NEX-3095 exported across writes forbidding issue specification by NFSv3 Address NEX-3505 leaks and server code. other in the NFS minor issues Fixed Authentication NFS Resolved
20 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor tting share-level security usingshare-level tting h caused an error while joining Microsoft while Microsoft error joining an h caused e permissions for user home directory user home directory e for permissions ability to communicate with NTP server ability communicate to .x on clients without anonymous read/write read/write anonymous without clients on .x Description were set improperly by default. by improperly set were node on the a cluster. of inactive Directory Active 4 3.x to from upgrade enabled. mode. maintenance to go to trigger nms-check could when se error snap-in Management Windows Server2008 R2. settings. certain with normalization letters case failover. on cluster access Key Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area NMS NEX-607 issue wher security Resolved NMVNMVProtocolsUpgrade Seamless NEX-1670 NEX-2609 NEX-2464 NEX-2713 UpgradeSeamless pair. NMVkey of generation Enhanced NEX-915Securityan after connectivity situation could be caused where issues Resolved in NMS whic change. defect NMV password for Resolved message error Corrected SMB disable SMART. to defaults Changed NEX-3084ZFSZFS NEX-2525in when condition Resolved NEX-3209 and Storage Share Console Management Microsoft Resolved NEX-3485upper- recognizing properly not were folders situation where Corrected loss of NFS to lead could deletes deferred condition where Addressed
21 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workaround No known workaround No known Execute the following command via bash: bash: via command the following Execute network/smb/server restart svcadm No known workaround No known This issue is not unique to NexentaStor and has been Thisissue is not unique NexentaStor to VMware. While to posted we work thisissue with 5.5 use ESXi to recommended is the Customer VMware LUNs. using FC environments clustered for Server If an automatic failover times out, manually initiate the the initiate out, manually times failover If an automatic NMV or NMC. from failover Configurations using STEC SAS SSD’s as data drives with with drives data as SSD’s SAS STEC using Configurations E50x or should earlier not be revision firmware a issues manufacturer the device until upgraded thisConfigurations issue. resolve to update firmware not are or log devices cache as SSD’s SAS using STEC by this restriction. affected Retry the operation if this condition is encountered. is if this condition the operation Retry Description from SMB session management. SMB session from upcoming in will fixed be panic This release intermittentlyfails aftera cluster fail- over. intermittent FC FC link resets. intermittent communication with FC LUNs LUNs with FC communication in an6.0 ESXi cluster. configured large number of nfs mounts and auto- mounts number of nfs large sync jobs. upgrading a system using PGR3 a system upgrading using release a later to Reservations SCSI-2 Reservations. unable to import full volumes due to due to volumes import full unable to prior created being sub-shares certain their mount. to Key NEX-2941MMC through ACL level share Editing This section lists the known issues in NexentaStor 4.0.4 as of July4.0.4 2015.as inthe known NexentaStor sectionThis issues lists Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area CIFS NEX-1999 panic but highly infrequent Potential, Commands + Commands Daemons COMSTAR NEX-2971 cause can I/Os up clean to Failure NFS NEX-3648 hang and loss Manual cause of failovers HA NEX-3191with in clusters on failover failure Export HA NEX-3394 after failover cluster with Issues HA NEX-3504 are systems issue where Intermittent Known Issues 4.0.4 in Issues Known 2-3: Table
22 /$1/" 's#/#\\\\/#g'` | sed NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workaround There are two possibleworkarounds. two are There /opt/HAC/RSF-1/bin/purge-stmf.sh 1. Edit line: this replace 's#/#\\\\/#g'` | sed "/rdsk/$1" volume_pattern=`echo with this: "/rdsk volume_pattern=`echo for allow don't servicenames that sure 2. Make named services Having matching. pattern undesired but will problems, mypool2 cause and mypool isfine.combination mypool2 and mypool1 Contact system installer or support provider to to provider or support installer system Contact numbers. controller manually reconcile Use 512 native or 512 emulated drives for NexentaStor NexentaStor for drives emulated or 512 native 512 Use installations. Use redundantlyUse configured(mirrored) ZILs. Execute the following command via bash: bash: via command the following Execute svcadm restart nlockmgr No known workaround No known workaround No known Avoid hotplugging when replacing Toshiba THNSNJ96 hotpluggingAvoid when replacing Toshiba SSDs. SATA issue where VM slack in VM issue where Description similar names can be susceptible similarto can names deletions uponfailover. LU unintended NexentaStor clusters can have have can clusters NexentaStor numbers controller mismatched the nodes. between drive with 4k native sector size. size. sector with 4k native drive single ZIL can cause a system panic system a single cause can ZIL the remove to attempt when users failed ZIL. always release deleted files causing deleted release always leak. a space like looks what non-ARC ZFS kmem caches can degrade degrade can kmem caches ZFS non-ARC performance. ARC record sizes can cause longzio_cache reaps. recognized upon hotplug. recognized Key Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area HA NEX-3769 pools with more with 2 or Systems Installation NEX-1881 circumstances, certain Under Installation NEX-3488a from NexentaStor boot to Unable Kernel NEX-2940 a as drive sTEC failed with a pools Disk Kernel NEX-2966not NLM does servers NFS busy On Kernel NEX-3043 different of datasets to I/Os Alternating KernelKernel NEX-3585 Intermittent NEX-3717 SSD is not THNSNJ96 SATA Toshiba Table 2-3: Known Issues in 4.0.4 in Issues Known 2-3: Table
23 ed files for eachbrowser NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Wikipedia:Bypass_your_cache Workaround Check pool for duplicate mountpoints before failover, failover, before mountpoints duplicate Check pool for manual remediation. perform 1) Serialize delete1) operations Serialize 2)a Use largerrecordsize (for example, 128k) Ensure that required components are installed and installed are components required that Ensure when using configured ZEUSproperly in IOPS drives a JBOD. No known workaround No known Before starting an install or upgrade, ensure that the the that ensure or upgrade, an install starting Before issue is If this correctly. set are time/date system correct the to the system reboot encountered, checkpoint. Restart NMS if large amounts of memory are being of memory are amounts NMS if large Restart used. On systems exhibiting this behavior, manually create create manually behavior, this exhibiting systems On without metis. using volumes Clear any cached files for the NexentaStor RSF GUI. RSF NexentaStor the files for cached any Clear Details clearing for the cach in Wikipedia article.can be found base knowledge NMV the reload file force the cache clear you Once page. https://en.wikipedia.org/wiki/ Description mountpoint path on two different ZFS ZFS different on two path mountpoint volume broken to leading filesystems, services. deletions of very large files builtfiles with large very of deletions can see performance small recordsize during the delete. degradation a mptsas deadlock may occur due to a occur due to may deadlock a mptsas backplane. the with poor connection certain situations date set incorrectly can boot to the boot to can set incorrectly date checkpoint. incorrect while allocations. reclaim failing to "Create New Volume" may not show all show not may Volume" New "Create drives. andprofiles available there are instances when NMV pages do when NMV pages instances are there HAC, to related information not display iSCSI mapping. Key Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area Kernel NEX-3734 a duplicate set to the user allows ZFS Kernel NEX-3890 parallel several performing Users Kernel NEX-928 a JBOD, in When usingZEUS IOPS drives Kernel, ZFSKernel, NEX-1760 in times kmem reap long exhibits ZFS NMC NEX-3969a time/ with systems upgrade, Upon NMS SUP-737 memory heap time grow over NMV may NMV NEX-2782NMV configurations, large very On NMV NEX-4198 4.0.4 NexentaStor to upgrading After Table 2-3: Known Issues in 4.0.4 in Issues Known 2-3: Table
24 ACL in place on the root of of root the place on in ACL C as Administrator on the on Administrator as C NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workaround You can use MMC Windows command console from to You shares. on CIFS settings ACL add/modify/delete MM start to sure 1) Make windows client. an have you that 2) Ensure ACL perform to rights sufficient has that share, the modifications. 3)windows Launch MMC from /s) (%windir%\system32\compmgmt.msc of top at Management" "Computer click on 4) Right IP Enter "Another computer". select and window click can on you Alternatively, in or FQDN box. address to which system AD server, select from and browse manage. and Tools" 5) Launch and application click on "System "Shares". and then Folders" then click on "Shared modify click and select and to right 6) Select the share tab "Security".and select top properties users/groups add/remove/modify to on "edit" 7) click correct have you then check that errors, any get If you view/modifysecurity settings. permissions to Description ACLCollector.pm error when editing when editing error ACLCollector.pm on folders. settings CIFS Key Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area NMV NEX-3511 an encounter may Users Table 2-3: Known Issues in 4.0.4 in Issues Known 2-3: Table
25 rop smbd/smb2_enable=false smbd/smb2_enable=false rop NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workaround Set NStor SMB server to SMB1: SMB1: to SMB server NStor Set smb -p smb2_enable=false set sharemgr svcadm restart smb/server or setp -s smb/server svccfg smb/server refresh svcadm svcadm restart smb/server disable SMBv2 client or on MS client: on the MS and SMBv3 SMBv2 the Disables -EnableSMB2Protocol Set-SmbServerConfiguration $false reboot client on the client: SMBv2 and SMBv3 re-enable to -EnableSMB2Protocol Set-SmbServerConfiguration $true reboot client Description PowerShell script, running though MS script, PowerShell a script encounter can Scheduler, Task with failure error. STATUS_BUFFER_OVERFLOW Key Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Functional Area Protocols NEX-3941a query with a performing Users Table 2-3: Known Issues in 4.0.4 in Issues Known 2-3: Table
26 rop smbd/smb2_enable=false smbd/smb2_enable=false rop id_domain=
7000-nxs-4.0.4-000017-B
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED www.nexenta.com