Glen,

I'm not trying to be difficult but the "What DART version, what FLARE" typical EMC response is not the solution. Plus the fact that you state nothing beyond the recommendations will be addressed. Really ? You say nothing beyond IE 7 and 7.1 is recommended ? Microsoft released IE 11 ! That after IE 8, 9, and 10 for the last couple years. Firefox is on release 25 !

Look, the problem is that the EMC client is not up to date addressing the latest browsers & Java builds working together. Old no longer left over items left on the system from the antique EMC client code are causing the problem.

EMC needs to fix and address this otherwise when are refresh comes up, we "will" look at alternatives.

...and I "do not" have time to spend an hour working with a level 1 tech trying this and that to get the old clunker agent to work.

Fix your Windows Client !!

Joey,

you can start looking at alternatives right now, because i can guarantee you EMC won't do squat to fix it. That applies to many vendors, look at Cisco DCNA client that is used to manage Cisco MDS FC switches. You install anything greater than 1.6.32 and it complains about java being at not supported level ..but at least it runs.

I'm not trying to be difficult about the Java issue, in support we are aware that the different combinations of flare and host operating systems and browsers makes for an challenging environment.

What I was trying to point out, is that when each new version of EMC software is released, it is tested and qualified at certain versions. This testing process is quite extensive and time consuming and not all versions of operating systems or browsers or Java will be tested due to the large number of variations or that we have discovered issues with the 3rd party software (OS/browser/Java) that either will cause issues, must be fixed by 3rd party or that the combinations just will not work together but the older versions will. The release notes will contain the information about what the currently released versions are and that's what support must adhere to. If you are using those versions that are listed in the release notes and it's not working, then support can escalate that issue to engineering to see about getting a fix or if it has already been fixed but not yet released.

So the release notes are updated with what is actually tested for each new version as the currently supported version. From a support perspective we get a lot of calls about "will this work with that" and if it doesn't, why not. E-Lab contains all the variations on what has been tested and supported. If you look at that latest Compatibility Guide for VNX, there are now 12409 pages. I can remember when the CLARiiON FC4700 guide "only" had a couple hundred pages.

glen

So basically nothing has changed & you don't have a fix & EMC may or may not put out an updated client ? Fact - more than one user is having the problem. We want a fix.

You know this whole JAVA has really gotten out of hand not just with EMC and the CISCO DCNM but we use Kronos for our time keeping, payroll etc.  You want to talk about Cluster mess.  I understand what Glen is saying and I FELL Joey's and others frustration on this issue as I spent 5 hours last week trying to get Unisphere to work.

I have a virtual server specifically for SAN work so I don't have to worry what Java I'm using and can easily fall back.  Well the server had Ver 7U45 and all was well when using the Clariion version of Unisphere until I ran reports.  The reports would run and were saved to my drive but they would no longer popup or after click on the link the report presented they did nothing.  Once I went to the stored area I was able to click on the reports and it opened up.  This is when I tried using the Unisphere client V1.2 it just error out with Java message.  So after spending more than 5 hours troubling shooting this problem and searching the web and coming into with this forum I reverted back to Java 1.6U45 and now the reports popup and the link work again.

But I can't install Unisphere V1.2 it errors out with files are missing during the installation

So where can I get the latest Unisphere 1.3. All the post point to the old site and on this site I only find Unisphere for VMAX.  I'm running 2 Clariions CX4's-240 &  480

Thanks

John

   Boy

Your best bet is complain through other channels like sales, or submit a Request for Enhancement (RFE).  The folks on the forums are support people, not engineering.  Your local sales team has a better shot of sending the complaints up the food chain to engineering and development staff, than posts here on the forums.  As others have said, this problem has existed for years with many supposed Tech giants.  I had a really good conversation at EMC World last year with some engineers about ways to get the problem noticed. Pity that plan hasn't really panned out this year....

Just noticed that you're using a NS480 - that's an integrated Celerra system with a captive CX4-480 array on the backend. To access the SP Management ports you must have proxy-arp configured on the Control Station in order to access the SP ports. Run the following command on the Control Station to see what it's configured for, then make sure you put one of the IP addresses in Client.

[nasadmin@Twix ~]$ /nas/sbin/clariion_mgmt -info

Public IP address for SPA: 10.10.10.10

Public IP address for SPB: 10.10.10.11

Start on boot : yes

Current implementation  : Proxy-ARP

Status : Started

The last item is which version of software on the CX4-480 supports the Unisphere interface. Unisphere was introduced in Flare release 30 for the CX4 and is the minimum flare release that would support Unisphere. Make sure that you Celerra is at the most current release 6.0.70.4/5.30.000.525.

I tested the 1.3 Client on one of the lab NS480's running the above versions and using Java 1.6.30 and did not experience and issues. I was using IE 7.1 on a Windows 7 workstation. I also tried this on a Windows 7 with IE 8 and Java 1.6.30 and a Windows XP with IE 8 and Java 1.6.30 without issues.

As I said before, of your NS480 is at the currently supported Dart/Flare version and your PC is running the supported configuration that are listed in the Unisphere Client Release notes and you're experiencing issues, then if you open a service request we will get engineering to fix that issue.

glen

We too are facing more and more challenges with Java compatibility.

Oracle stopped releasing public security updates to Java 1.6 in April of 2013.

It is riddled with security vulnerabilities that are actively being exploited.

Its slightly amazing to me that EMC's official support line would still be "go back to 1.6"

I can appreciate the time and effort needed to test and certify a new release of Unisphere, but please EMC, at least give us an update on the current development status. When well we have a version of Unisphere that is certified with Java 1.7 including the manifest signing changes that will be introduced in January? Are you even working on one?

I have an open service request where I ask EMC:

Is EMC actively working to update Unisphere to insure compatibility with newer (newest) versions of JRE

I have also found some nice blog and news articles that summ up very well what the current situation is in Java land:

http://arstechnica.com/security/2013/09/security-of-java-takes-a-dangerous-turn-for-the-worse-experts-say/

http://blog.trendmicro.com/java-security-situation-quietly-got-much-worse/?sf17098354=1

Java 6 Zero Day Exploit Pushes Users to Shift to Latest Java Version | Security Intelligence Blog | Trend Micro

The Trend Micro blog summs up the situation best:

This is the first in what is sure to be an ongoing series of attacks against unpatched Java 6 vulnerabilities. As long as a sizeable pool of people stay on this unsupported version of Java attacks will be viable. And so attacks will be carried out.

To be honest I do face the same issues with Unisphere client and the plague called Java.

OS: win7 x64

Browser: IE11

Client: UnisphereClient-Win-32-x86-en_US-1.3.1.1.0033-1

Java: 1.7.0_45

It's about time to release a version qualified for 1.7 - it's almost 2014!!!

frustrated regards, Masl