About EF & E-Series, SANtricity, and Related Plug-ins
Join conversations about NetApp EF/E-Series storage systems, SANtricity, and related plug-ins. Ask questions and get feedback from other users about these efficient storage systems optimized for demanding application-driven environments.
About EF & E-Series, SANtricity, and Related Plug-ins
Join conversations about NetApp EF/E-Series storage systems, SANtricity, and related plug-ins. Ask questions and get feedback from other users about these efficient storage systems optimized for demanding application-driven environments.
Hi, We decommissioned an old e5660 and at the time we recall that we were told that we had to also delete the supporting version of santricity due to the log4j issue and the fact that NetApp would not be patching the old EOS version of Santricity that supported the EOS e5660. We are now (much later) being challenged to provide doc showing that the software supporting the E5660 had the log4j bug and was not going to be patched due to being EOS. Of course being EOS and decommed, the serial # is useless for opening a ticket. 🙂 Any docs backing us up would be greatly appreciated. Thanks
... View more
Hello, we have a problem by mistake we installed the nvsram firmware first for the single controller and then for the dual, now we have the controllers with different versions one with single and one with dual, how can we synchronize them both with the firmware for dual controller?
... View more
Dear PowerShell community, We are glad to announce the release of the NetApp® ONTAP® 9.15.1.2407 PowerShell Toolkit. What’s new? Hydrate parameter support in NetApp PowerShell Toolkit The "Hydrate" parameter has been introduced to improve command execution performance by offering three options: Yes, No, and Partial. Yes: This is the default behavior, as it exists today. After a successful POST or PATCH request, a GET request is made with the query parameter ?fields=**, retrieving all fields. No: For POST or PATCH requests, it will pass ?return_records=true, and then display only the fields that ONTAP sets, which are usually just the keys and occasionally a few additional fields. This option is beneficial when performance is a priority and you do not need all the field details, avoiding the retrieval of unused fields. Partial: After a successful POST or PATCH request, a GET request is made with the query parameter ?fields=*, retrieving a subset of fields. This option is useful for balancing performance and the amount of data retrieved, reducing overhead by fetching only a subset of the fields. New Rest Endpoint Support 1. /security/key-manager-configs 2. /support/ems/role-configs/{access_control_role.name 3. /security/login/totps 4. /security/key-managers/{security_key_manager.uuid}/restore 5. /protocols/s3/services/{svm.uuid}/buckets/{s3_bucket.uuid}/rules/{name} NetApp ToolChest Download the package from the ToolChest. Extract the package. Execute Install.ps1 and enter the location where you want to update the existing package or do a fresh installation. Once the command has completed, import the module using both names “DataONTAP” and “NetApp.ONTAP”. For more details refer to PowerShell Toolkit Installation Guide Toolkit can be downloaded from PowerShell Gallery as well. In case of queries related to PSTK kindly drop a mail on ng-ontap-pstk-queries DL. Regards, NetApp PowerShell Toolkit Team
... View more
Hi Team, We are using 'NetApp E2800 Series E2824' with the current version being 11.70.4R1. We need to integrate it with the 'SolarWinds Platform, Hybrid Cloud Observability Advanced, SRM: 2023.3.0' through Storage Resource Monitor (SRM). Please suggest a compatibility version for the mentioned NetApp to SolarWinds through SRM. If possible could you share any article for the same. Thanks & Regards Brahmam
... View more