NexentaStor Release Notes 4.0.4
Date: July, 2015 Subject: NexentaStor Release Notes Software: NexentaStor Software Version: 4.0.4 Part Number: 7000-nxs-4.0.4-000017-A
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED www.nexenta.com NexentaStor Release Notes
This page intentionally left blank
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 VAAI Block Changes ...... 2 Warning about upgrading without preparation ...... 3 Planning for upgrade ...... 4 Identifying VMFS datastore extents and checking ATS status ...... 4 Disabling ATS on Existing Datastores ...... 6 Enabling ATS on Existing Datastores ...... 6 Enabling ATS on NexentaStor ...... 7 Reverting to pre-FP3 checkpoints ...... 8 IPMI Support ...... 8 Determining the Version of the Appliance ...... 8 System Requirements ...... 8 List of SMB Supported Client Operating Systems ...... 9 Upgrading ...... 10 Upgrading Minor Versions of NexentaStor 4.0.x ...... 10 Change in NMV Port ...... 10 Upgrading from Version 3.1.x to 4.0.4 ...... 10 Upgrading from Latest Version of 3.1.6 to 4.0.4 with an Internet Connection ...... 11 Upgrading from Latest Version of 3.1.6 to 4.0.4 without an Internet Connection ...... 13 Upgrading to Version 4.0.4 After Rolling Back to Latest Version of 3.1.6 ...... 13 Enhancements ...... 15 Resolved Common Vulnerabilities and Exposures (CVE) ...... 16 Resolved Issues ...... 17 Known Issues ...... 20
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED iii www.nexenta.com NexentaStor Release Notes 4.0.4
This page intentionally left blank
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED iv 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
AI support disabled by AI ng when it comes to when it comes to ng run with VAAI enabled system, the user will have to user will have to the system, from a storage system disrupts system from a storage MP manager is available in NexentaStor. The in NexentaStor. MP is available manager d, it also ships with VA bre Channel ports and will automatically and will automatically Channel ports bre t for the following storage enclosures: enclosures: storage following the t for tor requires some planni requires tor ng ESXi environments to ckend storage systems that do provide that storage systems that do provide that ckend ores that have it enabled and causes loss of access to the access to loss of have it enabled and causes that ores fault on creation with VMFS5. with on creation fault Test and Set (ATS) functionality and Set (ATS) functionality Test ock on a fresh NexentaStor 4.0.4 fresh ock on a for more for details. Nexenta Support Nexenta 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 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 default. In order to use VAAI Bl VAAI use to In order default. on NexentaStor. first enable the functionality from of version a previous NexentaS Upgrading VAAI support. Removing Atomic VMFS locking mechanismfor datast by de ESXi enables ATS datastore. • Campus/Metropolitan Support clusters for at the ESXi level to benefit from other ba benefit from to ESXi level at the functionality. certifie Block VAAI fully is 4.0.4 NexentaStor While Fix Pack 3 and above for NexentaStor 4.0.3 have all VAAI support disabled by default. This was This default. by disabled support VAAI all have 4.0.3 NexentaStor for above and 3 Pack Fix customer data still allowi while done to protect • 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 VAAI Block Changes Block VAAI 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 enta, may Enabling ATS on ATS Enabling NexentaStor Release Notes 4.0.4 Notes Release NexentaStor e following KB articles pt, provided by Nex with VMware and then, as with VMware faults without without faults configuring first applying configuration changes before changes configuration applying locking fail to mount after an upgrade an upgrade mount after to fail locking upgrade. A vaaictl scri A vaaictl upgrade. 1 1 to obtain the vaaictl script. See section See section script. the vaaictl to obtain t the original documents. Th here summarizeinformation providedin VMware ld first open support cases n minimize reboots by ainst an upgrade that changes de upgrade that an ainst Nexenta Support Nexenta level guidance, based on starting NexentaStor version to get to a to get to NexentaStor version starting on based level guidance, be consistent with the new defaults. ct if the settings are on the system at consultation with VMware: consultation with 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 ATS-only to use ATS-only configured , datastores VAAI fully enabled. 2037144 for more details. for more details.
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 To change To change ATS settings on NexentaStor requires a reboot. You ca Upgrading from Upgrading 4.0.3or earlier FP2 version version 4.0.3or later FP3 2037144 be used to You can contact enable VAAI features. needed, with Nexenta as joint support. joint as with Nexenta needed, ATS locking for affected datastores to datastores affected locking for ATS VMwareAs per KB In case of any issues with these procedures, you shou these with issues any In case of VMware and Nexenta both recommend ag knowledge base articles. You are recommended to consul 2006858 2030416 2094604 The procedures and background information provided information background and procedures The 1 NexentaStor When planning an upgrade, consider that: consider an upgrade, planning When • default. byenabled VAAI with 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 high some provides The following table VMware environment with upgrading your system, as they effe will take were reviewed by Nexenta in by Nexenta were reviewed 1033665 Warning about upgrading without preparation about upgrading Warning Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Table 2-1: Steps to enable VAAI enableVAAI to Steps 2-1: Table
iple hosts, you should esxcli storage storage esxcli log into the ESXi log by by but VMware not that a datastore uses extents e ESXi host(s), using what is , the datastore must be inactive (guests be inactive (guests must datastore , the up in the vSphere client datastore view. In view. datastore client vSphere up in the vert to the previously running snapshot, snapshot, the previously running vert to which extents they use, which extents they tastores mounted by mult tastores a support case with VMware to confirm confirm VMware to with case support a orming the preparatory steps outlined below, outlined below, steps the preparatory orming including others from the listed KBs. the including others from 2030416 disable ATS documented ", as in our example: ", the ESXi console (ssh into th into (ssh the ESXi console by a NexentaStor block device, use " device, block by a NexentaStor extents. All procedures assume r LUNs. In case of datastores using extents backed by storage by storage extents backed using datastores r LUNs. In case of tify possibletifyfurther opening sources of risk, joint support orage vendors as appropriate. orage vendors as grades. As per KB grades. As per andsupport open casewith a VMware as necessary,given following the 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 ~ # esxcli storage core device list -d device list core storage ~ # esxcli naa.600144f0c140cf6e0000546fca5d0002 ~ # esxcli storage vmfs extent list vmfs storage ~ # esxcli Number Extent UUID VMFS Name Volume Partition Name Device ------ham01-zv01 546fcc0f-d40379dd-5ae5-002590daef96 0 1 naa.600144f0c140cf6e0000546fca5d0002 53b43e1d-d4ab8871-1a8d-002590daef96 lrtsesx01-ds-01 0 t10.ATA_____ST1000NM00332D9ZM173______Z1W 3 11CAL running the belowsteps. also termed “tech support mode”): support termed “tech also core device list -d
5 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor vmkfstools -Phv1 /vmfs/volumes/ vmkfstools e the Vendor field is set to NEXENTA. For each For NEXENTA. is set to field Vendor e the tor-exported extents, use " " to confirm that ATS is enabled, as in our example: as enabled, ATS is that confirm " to ~ # vmkfstools -Phv1 /vmfs/volumes/ham01-zv01 -Phv1 vmkfstools ~ # 1 partitions. spanning system file VMFS-5.60 ham01-zv01 any): label (if system File ATS-only public Mode: TB size 62.9 1 MB, max file block size file GB available, 2 TB, 725.6 Capacity 2014 21 23:34:39 Fri Nov Time: Creation Volume 130000/129619 (max/free): Files 64512/63162 (max/free): Blocks Ptr 32000/31911 (max/free): Blocks Sub 256/256 (max/free): Blocks Ptr Secondary 0/1353841/0 %): (overcommit/used/overcommit Blocks File 0/1350/0 %): (overcommit/used/overcommit Blocks Ptr 0/89/0 %): (overcommit/used/overcommit Blocks Sub 814383104 size: Metadata Volume 546fcc0f-d40379dd-5ae5-002590daef96 UUID: "lvm"): spanned (on Partitions naa.600144f0c140cf6e0000546fca5d0002:1 YES Capable: Native Snapshot Is 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: true Is RDM Capable: false Is Local: false Is Removable: false Is SSD: false Is Offline: false Reserved: Is Perennially Size: 0 Sample Queue Full 0 Threshold: Queue Full yes Status: Thin Provisioning Filters: Attached unknown VAAI Status: vml.0200010000600144f0c140cf6e0000546fca5d0002434f4d535441 Other UIDs: false SAS Device: Is Local false Is USB: false USB Device: Is Boot 32 worlds: competing IOs with No of outstanding
r ATS see status, the r ATS see status, the ompt to confirm the change of may proceed with upgrade, may proceed with the : provides a list of symptoms to check in symptoms to a list of provides 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 ds disabling ATS on a per-device basis, per-device basis, ATS on a ds disabling ded to open a support ded to open case with VMware, a support r storage and check thei r storage and check thei the datastore is not configured to use ATS. use to configured not is the datastore 2006858 ailability are suspected or apparent. suspected or are ailability line indicates that the datastore is configured to use ATS. If If use ATS. to is configured datastore the line indicates that sabled for the datastore, you sabled for the following output, including a pr vmkfstools --configATSOnly 0 /vmfs/devices/disks/ --configATSOnly vmkfstools ", as in our example: Disabling VAAI entirely on the ESXi host may may host the ESXi on entirely Disabling VAAI be can you all devices, for of disabling VAAI LUNs. other impacting ~ # vmkfstools --configATSOnly 0 /vmfs/devices/disks/ 0 --configATSOnly ~ # vmkfstools naa.600144f0c140cf6e0000546fca5d002:1 VMware ESX Question: be will naa.600144f0c140cf6e0000546fca5d0002:1 device VMFS on that the Please ensure from ATS capability. upgraded to or downgraded ESX 4.x or remote local by any active use not in is volume VMFS-5 servers. capability? of ATS configuration with Continue 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 OBJLIB-LIB: ObjLib cleanup done. cleanup ObjLib OBJLIB-LIB: section “Identifying VMFS datastore extents and checking ATS status”. and checking ATS extents datastore VMFS section “Identifying To disable" ATS,use To identify VMFS datastores using NexentaSto using To identify VMFS datastores
7 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor to obtain the vaaictl script. to obtain the vaaictl ng the vaaictl invocation ng the vaaictl invocation upgrade, checking the VMware, requesting joint VMware, requesting joint by setting the execution setting the execution by check in case resulting problems to confirm the change of settings: of the change confirm to ”. exenta Support Support exenta N . re that it is executable that re open a support case with a support open the previous steps, changi ore, you may proceed with run the following script: run reboot. You can minimize reboots by applying by reboots You can minimize reboot. orage and their check ATS status, see the section provides a list of symptoms to symptoms to list of provides a g your system, they as will take effect if the settings are the on 2006858 the following output, including a prompt including output, the following the device as admin and admin the device as vmkfstools --configATSOnly 1 /vmfs/devices/disks/ 1 --configATSOnly vmkfstools ", as in our example: as ", Identifying VMFS datastore extents and checking ATS status ATS checking and extents datastore VMFS Identifying # -bash-4.2$ chmod 555 ./vaaictl chmod 555 # -bash-4.2$ --enable sudo ./vaaictl # -bash-4.2$ VMware ESX Question: ESX VMware to or upgraded will be naa.600144f0c140cf6e0000546fca5d0002:1 on device VMFS not in is volume VMFS-5 that the ensure Please capability. from ATS downgraded 4.x servers. ESX or remote by any local use active of ATS capability? configuration with Continue 0) _Yes 1) _No 0-1: 0 from a number Select may This file system. valid device as a using this hosts are if remote Checking seconds... a few take from ATS 'naa.600144f0c140cf6e0000546fca5d0002:1' VMFS-5 on Downgrading capability...done ~ # vmkfstools --configATSOnly 1 /vmfs/devices/disks/ --configATSOnly vmkfstools ~ # naa.600144f0c140cf6e0000546fca5d002:1 To enable ATS, use " mode of the file: mode of Copy the script to admin’s home directory, and make su and make admin’s home directory, the script to Copy
above steps have preparatory been l SES-based JBOD monitoring. In such cases, k current settings using this invocation, which invocation, settings using this k current refer to the “System Requirements” section in refer to the “System Requirements” ntaStor. You can determine the version of the of the can determine the version ntaStor. You ly locking disabled will continue to be be disabled will continue to ly locking anged without a system reboot, which means that reboot, system without a anged tute for traditional SES-based monitoring. SES-based traditional tute for e system to follow product defaults again: follow product defaults to system e . revert defaults. revert defaults. As long as the g system are uncertain: Type: version nmc:/$ show appliance response: System 40-0-47 NMS version: 40-0-39 NMC version: 40-0-45 NMV version: 20 2015 Date: June Release # -bash-4.2$ sudo ./vaaictl --default ./vaaictl sudo # -bash-4.2$ --disable ./vaaictl sudo # -bash-4.2$ --status ./vaaictl # -bash-4.2$ NexentaStor Installation Guide Installation NexentaStor To determine the version of the appliance using NMC: using appliance version of the the determine To For system requirements for each environment, For system requirements for each environment, the you can use IPMI monitoring as a substi as monitoring IPMI use can you Nexe of NexentaStor 4.0.4 is the current release appliance usingNMC. 4.0.4) (version Nexenta/illumos System: Operating Some storage vendors no longer support traditiona Reverting checkpoints will or to disableexplicitly: You can chec require reboot. All settings changes will warn you if the config file has been ch has file config the if you will warn settings on the runnin ATS-on with datastores successfully completed, accessible. either to restore defaults, allowing th allowing defaults, restore to either Reverting to pre-FP3 checkpoints pre-FP3 to Reverting System Requirements System Determining the Version of the Appliance the Version Determining IPMI Support 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 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor Workgroup Mode ating Systems that have Systems that ating the permissions specified in the the in the permissions specified Windows Server 2003 Windows Windows Server R2 2003 Controllers and client Oper Controllers ing the Server Message Block (SMB) protocol if protocol (SMB) Message Block ing the Server Windows Windows Server 2008 and has an active machine account. account. machine active has an and te the domain users according to users according to te the domain ed with the indicated Domain Controller. with the indicated ed Windows Windows R2 Server 2008 Windows Windows Server 2012 X X X XXX X XXX X X X X XX XXX X X X N/S N/S N/S N/S X X XX XXX X X XX XXX X Windows Windows R2 Server 2012 X X X X X X X X X X X X X X X X X X X X X X X X X X X X domain to which NexentaStor is joined domain of Domain versions describes the The following table work with NexentaStor. successfully tested to been NexentaStor can properly authentica NexentaStor Network clients can access files on NexentaStor us access files on NexentaStor Network clients can entOS 6.5 entOS Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com Red Hat/ С 12.04 Ubuntu LTS Mac OS X 10.9.2 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 2012 R2 Windows Windows 2012 Windows 2008 R2 Windows Windows 2008 Windows 2003 R2 N/S represents those OSs that are not test are that those OSs N/S represents Table 2-2: SMB 2-2: CompatibilityMatrix Table List of SMB Supported Client Operating Systems Operating Client of SMB Supported List
. Upgrading Minor Versions of Minor Versions Upgrading lumes remain available to network clients. The clients. network to available remain lumes Upgrading from Latest Version of 3.1.6 to 4.0.4 of 3.1.6 to Version Latest from Upgrading of NexentaStor 4.0.x, see: of NexentaStor 4.0.x, Upgrading from Latest Version of 3.1.6to 4.0.4 of an with Version Latest from Upgrading , Upgrading from Latest Version of 3.1.6 to 4.0.4 without an Internet 4.0.4 of 3.1.6 without to an Internet Version Latest from Upgrading , Upgrading from Latest Version of 3.1.6 to 4.0.4 with an Internet Connection Internet an 4.0.4 with of 3.1.6 to Version Latest from Upgrading Type: nmc:/$ setup appliance upgrade nmc:/$ setup appliance Upgrade to the latest version of 3.1.6. version the latest to Upgrade 4.0.3. of version latest to Then, upgrade 4.0.4 to Then, upgrade See To upgrade the appliance to 4.0.4 from 4.0.x or 4.0.3 FPx releases: FPx 4.0.x or 4.0.3 from 4.0.4 to appliance the upgrade To 1. Upgrading NexentaStor from version 3.1.x to 4.0.4 is a three-step process. First you need to to need you First process. a three-step 4.0.4 is 3.1.x to version from NexentaStor Upgrading 4.0.4. to 4.0.3 and then latest to then upgrade 3.1.6 and of version latest the to upgrade 1. 2. 3. In NexentaStor 4.0.x, the default NMV port has been changed to 8457. to been changed NMV port has default the 4.0.x, NexentaStor In port the registered Nexenta vendors, other networking with conflicts potential avoid to In order port the default uses longer no access 4.x and above, web releases Nexenta with IANA. For 8457 4.x, 3.x NMV to is by release now from accessed when 2000Note upgrading andport 8457. uses port 8457. Connection single with a command. 4.0.3 FP releases or from 4.0.x release Version from upgrade can You To upgrade between minor versions between To upgrade 4.0.x NexentaStor To upgradeNexentaStor from to 4.0.x, 3.1.x see Connection Internet without an Connection Internet During the upgrade, NexentaStor services and vo services NexentaStor upgrade, the During the upgrade that recommended is it Therefore, restart. system requires operation upgrade servicesand NexentaStor All window. maintenance during a system be scheduled process restart. during the available not are volumes 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 Minor Versions Upgrading Upgrading 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 and NexentaStor Release Notes 4.0.4 Notes Release NexentaStor ’ command or proceed proceed or ’ command Partner Portal Partner or Customer Portal Portal Customer setup nexentastor upgrade -r upgrade nexentastor setup y disable the multi-NMS and restart NMS. restart and the multi-NMS y disable This upgrade creates Rollback Checkpoint. You may may You Checkpoint. Rollback creates This upgrade at are not included with the NexentaStor build. with the NexentaStor not included are at show appliance show appliance checkpoint 3.1.6 to 4.0.4 with an Internet an Internet with 4.0.4 3.1.6 to changes, visit the respective the visit changes, included in the hardware compatibility list for NexentaStor 4.0.x. NexentaStor compatibilityfor list in the hardware included t meets the following prerequisites: meets the following t tain the new license key. . Running this command willRunning this automaticall . setup appliance upgrade setup appliance setup appliance upgrade setup appliance
setting is not maintained, and and maintained, is not setting rebooting, all NexentaStor all NexentaStor rebooting, . View nfsmapid_domain nfsmapid_domain . or restart the NexentaStor appliance. the NexentaStor restart or lumes to version 28 by typing: 28 version to lumes pane, click , logbash: in to proceed with the reboot. When with the reboot. proceed Settings > Appliance Settings for all NexentaStor volumes all NexentaStor for Upgrade Checkpoints Upgrade nfsmapid_domain nfsmapid_domain nfsmapid_domain Step 10 Step After you upgrade the volume version, back up your system. Backups created for for created Backups system. backup the volume your version, upgrade you After the upgrade. after not be available may versions volume earlier pools with mirrored In NMV, click In NMV, In the nmc:/$ option expert_mode =1 option expert_mode nmc:/$ nmc:/$ !bash To set the set To nmc:/$ setup volume
13 for setup NexentaStor Release Notes 4.0.4 Notes Release NexentaStor . . If you try to run the the run to try you . If file and run the [email protected] version and4.0.4, the data version ll prerequisites described in described thissection. ll prerequisites Upgrading from Latest Version of 3.1.6 to Version Latest from Upgrading version during the upgrade to to upgrade the during version NexentaStor HACluster User Guide e volume version 28 is not supported in version 3.1.6. 3.1.6. in version isnot supported 28 version volume e /volumes/.config/.3_to_4_upgrade ternet upgrade to contactyour system, /volumes/.config/.3_to_4_upgrade to 4.0.4 with no Internet connection: connection: with no Internet 4.0.4 to Upgrading from Latest Version of 3.1.6 to 4.0.4 with an Internet Internet an with 4.0.4 to 3.1.6 of Version Latest from Upgrading in in out an Internet connection, review review connection, out Internet an . Then verify that your environment meets a meets environment your that . Then verify Step 11 Step to command again. . Step 2 Step To upgrade the HA Cluster plugin, see: plugin, see: the HA Cluster upgrade To # sharectl set -p nfsmapid_domain=
setup appliance upgrade appliance setup nmc:/$ setup nexentastor upgrade -r
15 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor k runner ival_anti_flapping setting to address to address k runner setting ival_anti_flapping ging snapshot ownership for Auto-services. ging for snapshot ownership event using two disks from the same tray. the same from disks two using event fixes #5376, #5498, and #5514. and #5498, #5376, fixes ity of the SNMP traps. the SNMPtraps. ity of Description intervention. by JBOD sensors. being reported values possible false interoperating with MIT KDCs. once. Directory. Copyright © 2015 Nexenta Systems, ALL RIGHTSALL RESERVED Systems, © 2015Copyright Nexenta www.nexenta.com NEX-2788 chan for 3.x functionality Restored NEX-1099 administrative require list always to runners clearing the faulted behavior Changed for NEX-1160 NFS. use with for NIS client of management appliance Provided NEX-1955ses-chec the of value the default Changed NEX-2510 population and keytab principal creation support client for Kerberos NMC Enhanced NEX-2694pr logic to pool creation Updated NEX-2849updates. driver Emulex Incorporated NEX-2865 at schedules Auto-snap multiple accommodate to Auto-sync to functionality Added NEX-2951 3.x functionality by ACL Microsoft Active auto-tierreplication for for Restored NEX-3082RSF. to monitoring status port FC Added NEX-3134 functional Enhanced NEX-3145 prior a Added to user response snapshotdeleting sources. confirmation Auto-sync NEX-3663kmem_reap Illumos Ported Key Enhancements 4.0.4. in NexentaStor enhancements This section lists
I script that does not read from its its from read not does that I script its from read not does that I script alysis of ciphertext in a large number in a large ciphertext of alysis C only if the MAC field has a nonzero C only if the field MAC has a nonzero , when request body decompression is body decompression , when request he HTTP Server before 2.4.10 does not have have not does 2.4.10 HTTP before he Server Apache HTTP Server 2.2.22 allows remote remote HTTP allows 2.2.22 Apache Server 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 HTTP before le in Apache Server the a timeout mechanism, which allows remote attackers to cause a denial of denial of a cause to attackers remote mechanism, a timeout which allows a CG to hang) via a request service (process plaintext. use the same that sessions of stdin file descriptor. stdin or service(crash) a denial of cause to man-in-the-middle attackers allows URL. crafted via a code arbitrary possibly execute the in a header placing by directives unset" "RequestHeader bypass to attackers vendor the NOTE: coding. transfer chunked with sent of data portion trailer a securi not is "this states file descriptor. stdin 2.4.10 HTTPthe Apache before Server of service (resource denial a cause to attackers remote allows enabled, size. a muchlarger to data that decompresses request consumption)viacrafted conduct to attackers remote for it easier which makes biases, single-byte an statistical via attacks plaintext-recovery length, which makes it easier for man-in-the-middle attackers to spoof packets packets spoof to man-in-the-middle attackers for easier it which makes length, theby omitting MAC. denial of a cause to attackers remote mechanism, a timeout which allows a CG to hang) via a request service (process Description in NTP in ntpd in ntp_proto.c function in the receive feature The symmetric-key MA a correct 4.2.8p2 requires before 4.x CVE (CVE-2014-0231) The mod_cgid module in the Apac (CVE-2014-6273) (CVE-2014-6273) earlier in APT 1.0.1 and in apt-get code in the HTTP transport overflow Buffer (CVE-2013-5704) in module the The mod_headers (CVE-2014-0118) in function deflate_in_filter The (CVE-2013-2566) Theand RC4 algorithm, SSL as inhas many protocol, theused TLS protocol (CVE-2003-1418) (CVE-2003-1418) The mod_cgid modu (CVE-2015-1798) (CVE-2015-1798) (CVE-2015-1799) (CVE-2015-2781) The following CVEs have been incorporated into NexentaStor 4.0.4. NexentaStor into been incorporated CVEs have The following Resolved Common Vulnerabilities and Expo- and Vulnerabilities Common Resolved (CVE) sures 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 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
18 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
19 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
20 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 NEX-3648 hang and loss Manual cause of failovers 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 COMSTAR, FibreCOMSTAR, Channel, HA 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
21 /$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
22 NexentaStor Release Notes 4.0.4 Notes Release NexentaStor 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 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 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 Table 2-3: Known Issues in 4.0.4 in Issues Known 2-3: Table
23 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
24 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
25 rop smbd/smb2_enable=false smbd/smb2_enable=false rop id_domain=
7000-nxs-4.0.4-000017-A
Copyright © 2015 Nexenta Systems, ALL RIGHTS RESERVED www.nexenta.com