Isilon Devices No Longer Polling Following Upgrade to 8.0.0.4

This is a known bug. Multiple buddy drops have failed to resolve the issue. Devs are still working on it.

Is there anyway to be looped into updates on this?

Found something interesting that I posted in the NPM section.EMC Isilon Showing Up As Non-EMC device after Upgrade

What I found is that following the upgrade the Isilon devices were now showing themselves as Fraunhofer FOKUS devices. It looks like the OID for SystemID was changed for some reason.  If that's the case, would that affect polling of volumes and performance as I am experiencing?

So we recently upgraded from SRM Orion 6.3 to SRM 6.4, and I can now add the Isilon arrays running 8.0.0.2. Unsure if it also works with 8.0.0.4.

Good to know, but I'm having the issue in SRM Profiler (which used to be STM).  Any idea if there will be a patch/update for it?

Not sure on any updates on SRM Profiler.

In fact I have to withdraw my previous success story, while SRM Orion 6.4 does successfully inventory the Isilon disks, it doesn't actually collect any data (after applying SRM 6.4 HF1).

We have Isilons on 8.0.0.3 and SRM 6.4 HF1. Filers test connection successfully, but show as unreachable after being added. SRM pulls details from the Isilon like SN and code level but that's all.

Anyone found a resolution to this yet? I had a support call for an unrelated issue but asked about the Isilon bug and they said its the array's web console certificate that keeps changing and causing issues. Before I go through the headache of engaging EMC support, I would like to see if anyone else has fixed this successfully.

I haven't had any luck.  It seems to me like EMC changed the way the Isilon communicates and Solarwinds hasn't been updated with the changes.

Support was telling me I had to update the array's website certificate to sha256 compliant. Not sure if it's worth the hassle or not