jkmills

That's easy to say, but this is turning into a serious problem. We purchased this product to monitor the performance of our arrays and were sold it on the premise that it would work with the code upgrade to 10.2.4.e Beyond that, the CIM errors have now cost us with equipment failures, data corruption and downtime on…

I agree that supporting TSM 6.x is needed soon. We are evaluating your product and are a little dismayed that it has been so long without an update on this. Version 6 has been out for a while.

My guess is that you are not running the same model (IBM Blade Chassis FC Switch - Brocade 4020) with FOS 6.2.2d I have noticed with a lot of things in the Storage Manager program that you must make a change and give it a while to take affect and start reporting. It may have just taken your particular switches a while to…

Yes, the 10.2.4f microcode release was created specifically for the this issue. I spoke with our TA regarding this and as you stated this is not going to be recommended for anyone who isn't dealing with this pain point, and it is not widely in use yet. I am looking forward to getting our XIV talking again but we our…

I have to say that I am glad to hear that I am not the only one. Now hopefully there can be progress in getting this resolved. From what I have heard (which is only a couple of cases) it seems to be Gen 2 specific. Ocgov2012, Did you experience module crashes as a result of either the initial issue or IBM support…

We upgraded to 10.2.4.e last night and everything went well with the upgrade. I have started monitoring again today with SW-STM and we have already failed the CIM agent on two out of three interface modules. I am not going to attempt to point it at the last module at this point, but there is still something seriously wrong…

We have done extensive troubleshooting with SolarWinds on this issue and have found that the port information is being collected, but it is not being recognized by the software. They have sent the information we collected to the engineering team and I will check with my contact today and see where we stand.

Update, in case this issue ever comes up for someone else. We are running TSM on Linux and we needed to select the two digit year format in order to get this to work correctly. We had followed the documentation and our queries were reporting with the four digit format, but support worked with us and we found this to be the…

The setting is referenced in this Knowledge Base article http://knowledgebase.solarwinds.com/kb/questions/2674/How+to+change+the+default+website+timeout+setting. In short, the setting is currently 30 (30 minutes) and can be found in webapps\ROOT\WEB-INF\web.xml <session-config>…

My IBM rep has given similar information that the fix is set for release in 10.2.4.f which is targeted for release in October.

Warning We experienced the exact same issues, the monitoring from SolarWinds Storage Manager was causing the cimserver process to fail. This was the case on microcode 10.2.4b and 10.2.4c1. Last Friday IBM Level 2 support logged into our XIV (Gen 2) and managed to restart the cimserver process. The repeated failures and…

Wow, I was actually logging in to look for the exact same thing. For some reason this appears to have been ommited. All other capacity/utilization statistics allow us to view historical data and see trends, except the Thin Pool Utilization.

Agreed, this is a noticeable absence from the product

Agreed we would also like to include our Data Domains in the Storage Manager. We would like to be able to verify: Capacitys/Free Space Errors/Alerts VTL Stats Performance of Interfaces, Disks, Compression, etc. We currently use the 670 model, primarily as a VTL for TSM.