When will Active IQ Unified manager 9.14 or newer version become GA? Currently Active IQ UM 9.14 still RC1. When will Active IQ UM support RHEL 9? Or higher RHEL versions then 8.8? In the manual it states that you need RHEL 8.0 - RHEL 8.8.
... View more
Hi everyone, We're currently investigating some significant differences in the reported physical used capacity between NetApp versions 9.13 and 9.14 and would appreciate your insights. In version 9.13, when querying the physical used capacity using the CLI command volume show -volume Apr* -fields size,available,total,used,physical-used, we received the following results: vserver volume size available total used physical-used -------- ----------- ------- --------- ------- ----- ------------- NetApp_2 Apr_ss_15gb 17.89GB 17.89GB 17.89GB 340KB 340KB NetApp_2 Apr_ss_70gb 78.86GB 78.86GB 78.86GB 308KB 308KB However, when querying the same information in version 9.14 with the same CLI command, volume show -volume Apr* -fields size,available,total,used,physical-used,we observed a notable increase in the reported physical used capacity: vserver volume size available total used physical-used -------- ----------- ------- --------- ------- ----- ------------- NetApp_2 Apr_ss_15gb 17.89GB 17.89GB 17.89GB 468KB 17.99GB NetApp_2 Apr_ss_70gb 78.86GB 78.86GB 78.86GB 456KB 79.30GB We're trying to understand the reasons behind this discrepancy: What constitutes physical used capacity in NetApp? What changes were made between versions 9.13 and 9.14 that could account for the differences in physical used capacity? What additional data is included in the calculation of physical used capacity in version 9.14 compared to version 9.13? Where can we find documentation or resources detailing these changes to better understand how to interpret the physical used metric in our storage environment? Any insights or guidance you can provide would be greatly appreciated. Thank You.!
... View more
Hello All, because we have more Active IQUM installed in more customers, I ask you if have find the possibility to personalize Object on email alert. I don't have finded. Many thanks.
... View more
Hi We are experiencing an issue with one of our newer clusters. We have a few clusters added into Harvest and only this one is causing an issue. The problem is it will stop running after various amounts of time - usually 5-15 minutes. We see this on the NAbox web interface, home section under Harvest Systems. The cluster in question is showing Not Running in red. Once manually started it will run for another moment to fail again. NetApp Release 9.12.1P7 NAbox 2.6.3 (2020-05-05). NMSDK 9.7P1. Harvest 1.6. The below log shows me restarting the service twice today, however, there is no errors indicating what is causing it to stop. [2024-05-08 14:57:40] [NORMAL ] WORKER STARTED [Version: 1.6] [Conf: netapp-harvest.conf] [Poller: **********] [2024-05-08 14:57:40] [NORMAL ] [main] Poller will monitor a [FILER] at [**********:443] [2024-05-08 14:57:40] [NORMAL ] [main] Poller will use [password] authentication with username [netapp-harvest] and password [**********] [2024-05-08 14:57:40] [WARNING] [connect] Setting HTTP/1.0 because reverse hostname resolution (IP -> hostname) fails. To enable HTTP/1.1 ensure reverse hostname resolution succeeds. [2024-05-08 14:57:40] [WARNING] [connect] Setting HTTP/1.0 because reverse hostname resolution (IP -> hostname) fails. To enable HTTP/1.1 ensure reverse hostname resolution succeeds. [2024-05-08 14:57:40] [NORMAL ] [main] Collection of system info from [**********] running [NetApp Release 9.12.1P7] successful. [2024-05-08 14:57:40] [NORMAL ] [main] Found best-fit monitoring template (older generation or major release): [cdot-9.6.0.conf] [2024-05-08 14:57:40] [NORMAL ] [main] Added and/or merged monitoring template [/opt/netapp-harvest/template/default/cdot-9.6.0.conf] [2024-05-08 14:57:40] [NORMAL ] [main] Metrics will be submitted with graphite_root [**********] [2024-05-08 14:57:40] [NORMAL ] [main] Using graphite_meta_metrics_root [**********] [2024-05-08 14:57:40] [NORMAL ] Creating output plugins [2024-05-08 14:57:40] [NORMAL ] Created output plugins [2024-05-08 14:57:40] [NORMAL ] [main] Startup complete. Polling for new data every [60] seconds. [2024-05-08 17:03:02] [NORMAL ] WORKER STARTED [Version: 1.6] [Conf: netapp-harvest.conf] [Poller: **********] [2024-05-08 17:03:02] [NORMAL ] [main] Poller will monitor a [FILER] at [**********:443] [2024-05-08 17:03:02] [NORMAL ] [main] Poller will use [password] authentication with username [netapp-harvest] and password [**********] [2024-05-08 17:03:02] [WARNING] [connect] Setting HTTP/1.0 because reverse hostname resolution (IP -> hostname) fails. To enable HTTP/1.1 ensure reverse hostname resolution succeeds. [2024-05-08 17:03:02] [WARNING] [connect] Setting HTTP/1.0 because reverse hostname resolution (IP -> hostname) fails. To enable HTTP/1.1 ensure reverse hostname resolution succeeds. [2024-05-08 17:03:03] [NORMAL ] [main] Collection of system info from [**********] running [NetApp Release 9.12.1P7] successful. [2024-05-08 17:03:03] [NORMAL ] [main] Found best-fit monitoring template (older generation or major release): [cdot-9.6.0.conf] [2024-05-08 17:03:03] [NORMAL ] [main] Added and/or merged monitoring template [/opt/netapp-harvest/template/default/cdot-9.6.0.conf] [2024-05-08 17:03:03] [NORMAL ] [main] Metrics will be submitted with graphite_root [**********] [2024-05-08 17:03:03] [NORMAL ] [main] Using graphite_meta_metrics_root [**********] [2024-05-08 17:03:03] [NORMAL ] Creating output plugins [2024-05-08 17:03:03] [NORMAL ] Created output plugins [2024-05-08 17:03:03] [NORMAL ] [main] Startup complete. Polling for new data every [60] seconds. -------------- The [WARNING] [connect] messages are visible on the other clusters which work fine so I skipped investigating those. Are there other places in the logs that could be checked? Regards
... View more
Question about Active IQ Unified Manager Version: 9.14 Does anyone have an idea on how we might go about creating a notification on these two events: wafl.vol.autoSize.done wafl.vol.autoSize.fail We use auto grow throughout our environment and are reliant on getting notified each time a volume grows so that we can manage our volume autosize settings to make sure that volumes can continue to grow.
... View more