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.
As many of you are aware there's a nice NetApp repo with an E-Series performance monitor, InfluxDB and Grafana put together as one monolithic docker-compose setup which runs all these things on one VM: https://github.com/netApp/eseries-perf-analyzer I created a friendly fork of it with Collector as a stand-alone container: https://github.com/scaleoutsean/eseries-perf-analyzer What this does is lets you - an E-Series admin or Ops guy - run and manage one Collector per one array, and not touch shared Grafana or InfluxDB containers. You still need InfluxDB (the older v1) to send data to, but it can be set up and managed by one team/person for the entire organization. So for example three teams can each have their own Collector and manage SANtricity password rotation without touching a shared instance or being able to access other people's E-Series. Upstream EPA v3..0.0 (current version) doesn't make it very easy to run multiple collectors. It is possible and done by default, in fact, but it makes use of SANtricity Web Service Proxy (WSP), which means one container that can manage all E-Series arrays, which many admins don't like: the moment you let one admin access WSP, they can accidentally access all arrays, break InfluxDB, etc. My fork removes Collector's dependency on WSP - all an admin has to do is run a Python script (inside or outside of a single container) - and specify a monitor (not admin) account of their E-Series array. If you already use EPA v3.0.0, it is possible to run additional Collectors outside and send data to existing EPA v3.0.0 without adding Grafana and InfluxDB instances. The fork retains upstream's Docker Compose with Grafana/InfluxDB and adds another Compose for a stand-alone Collector (or Collectors). The Collector container(s) can also be deployed to run on Kubernetes or run containerless. It needs less than 32 MB of RAM so it takes less than 1GB of memory to collect data from 32 arrays. In that way running one per each E-Series array is very affordable, given the security and operational benefits. Says I. EPA users who wish to contribute or have an opinion or question are welcome to leave their comment here.
... View more
Hi In e5760 (120 hdd - 2 dpp pool -11 volumes we do not understand the reason -at this moment all - ddp pool and volumes failed in HW -only 1 hdd failed Is it possible to recover data in this case? DISK POOLS------------------------------ SUMMARY Total Disk Pools: 2 Total Capacity: 1,293.070 TB Usable, 1,276.445 TB Used Total Free Capacity: 16.625 TB Status: 0 Optimal, 2 Non Optimal Name Status Usable Capacity Used Capacity Free Capacity Preservation Capacity Drive/Media Type Volumes DA Capable vidanl_ddp1 Failed 646.535 TB 630.000 TB (97%) 16.535 TB 42.748 TB(3 Drives) SAS, Hard Disk Drive 6 Yes vidanl_ddp2 Failed 646.535 TB 646.445 TB (100%) 92.000 GB 42.748 TB(3 Drives) SAS, Hard Disk Drive 5 Yes SUMMARY Number of volumes: 11 Name Thin Provisioned SSD Cache Status Capacity Accessible by Source ddp1-vid3301_0 No No Failed 10.000 TB Host srv-vid3301 Disk Pool vidanl_ddp1 ddp1-vid3302 No No Failed 200.000 TB Host srv-vid3302 Disk Pool vidanl_ddp1 ddp1-vid3302_1 No No Failed 140.000 TB Host srv-vid3302 Disk Pool vidanl_ddp1 ddp1-vid3302_2 No No Failed 40.000 TB Host srv-vid3302 Disk Pool vidanl_ddp1 ddp1-vid3303 No No Failed 200.000 TB Host srv-vid3303 Disk Pool vidanl_ddp1 ddp1-vid3303_2 No No Failed 40.000 TB Host srv-vid3303 Disk Pool vidanl_ddp1 ddp1-vid3304 No No Failed 6,600.000 GB Host srv-vid3304 Disk Pool vidanl_ddp2 ddp2-anl3303 No No Failed 100.000 TB Host srv-anl3303 Disk Pool vidanl_ddp2 ddp2-vid3302 No No Failed 200.000 TB Host srv-vid3302 Disk Pool vidanl_ddp2 ddp2-vid3303 No No Failed 200.000 TB Host srv-vid3303 Disk Pool vidanl_ddp2 ddp2-vid3303_1 No No Failed 140.000 TB Host srv-vid3303 Disk Pool vidanl_ddp2
... View more
Hi All, I got a broken disk today when I being volumes group extend implementation, I have order RMA and follow the manual to being fail disk replacement. After I login to SANtricity for checking status, the replacement disk was in unassigned. Volumes group now still in degree status, I has been put the disk assigned as spare. But it still not take action for volumes group rebuild, what should I do? P.S. The processing job still running volumes extend, may I know the rebuild job was cannot process with volumes extend at the same time? Many thanks. Terry
... View more
I just wanted to share that Rocky Linux 8 and 9 have been added to IMT for E-Series. Rocky Linux is designed to be bug-for-bug compatible with its upstream Linux distribution. * Rocky Linux - https://rockylinux.org/ (free download) * NetApp Interoperability Matrix: https://imt.netapp.com/ (login required)
... View more
Hello . My E2824 firmware verion is 11.73. I need to revert it to 11.60.3. When i tried to firmwware downgrade on smcli using bellow command downlod storageArray firmware file="c:\RCB_11.60.R2_280x_5fab8f6.dlp" downgrade=TRUE activate=TRUE healthCheckMelOverride=TURE; always downgrade failed. How can I revert it ?
... View more
