Just a heads up - Java 7 Update 45 has problems and breaks UCSM launching successfully.
You may see one of two errors:
Login Error: java.io.IOException: Invalid Http response
Login Error: java.io.IOException: Server returned HTTP response code: 400 for URL: http://x.x.x.x:443/nuova
Temporary Workaround: Rollback Java 7 to Update 25 or lower. A UCSM patch will be released eventually to address this.
Cisco Bug ID: CSCuj84421
To add further, here is the change introduced in Java that breaks launch of UCSM
Any Java7 update 40 or earlier should work. No need to go back to Java6.
I suggest you remove all Java instanses and re-install Java7u40 or less.
Cisco is about time to move away from Java. most of the times there is a java update some cisco application won't work.
is any Cisco developer reading these forums?
This might be a interested post for all of us:
This issue is now fixed in 2.0(5f) just released yesterday.
Does this imply that a patch for 2.1. is forthcoming? This is affecting our 2.1(3a) environment as well.
There will be a fix for 2.1 firmware and 2.2 should be Java 7 Update 45 compatible.
Go to https://tools.cisco.com/bugsearch/bug/CSCuj84421and save the bug to your profile in order to get updates and patch notifications.
Just wanted to let you know that there is an new patch for the 2.0 release that includes the fix to the java issue.
CSCuj84421: Java 7 Update 45 breaks UCS Manager GUI
The Patch version is 2.0(5f)
Cisco Download page
Release notes for UCS 2.0
Has anyone tried "thinapp'ing" the UCS manager + matching Java version? I manage multiple clients with different UCS versions ( 1.4, 2.0 , 2.1)and switching between Java 6 & 7 is a hassle.
there appears to be a workarround
enable http and disable https redirection
we found the workarround in this post
This workaround is not secure as everything will be sent in clear text. This will extend threat surface of your UCS environment to anyone or anything on your network.
also there is a ucs update that addresses the issue.
it was just released
if your packet will be sniffed inside your network then you have bigger issues to worry.
till the upgrade, the workarround works fine.
till next java release and here we go again.
number of my customers reporting same problem, Java 7 update 45 seems to be "unlucky" build. You can solve the problem by uninstalling update 45 and installing java 7 update 25.
Just started updating from 2.1(3a) to 2.2(1b). Java Update 47 is now supported. But run into big issues after updating the first Fabric Interconnect! created a support case 5 minutes ago.
EDIT: Problem solved (work-around). I know it is off-topic, but worth to share. If you have configure another line-rate setting in your QoS policies you might run into numerous failures when you update you first FI to 2.2(1b). Once I set my the QoS policies settings back to 'line-rate' everthing started working again. This is just a quick reminder for those who want to get rid of the Java incompatibility and start updating.
We are running 2.1.1f in 4 seperate domains, and can successfully log into them with 7 U45, but have noticed that if the http is redirected to https, the login will fail. You can change this under Admin (filter All) communication management > comminication services from witin the GUI, or at the CLI under scope system > scope services disable http-redirect
uninstalling java 1.7 entirely fixed this issue for me, but i agree, Cisco needs to stop using Java for their interfaces. you can get the same level of dynamics in a console that uses no java at all, just look at F5.
So the UCS system I am trying to connect to is on 2.1(3a) and I am running Java 8.20 and receive this message:
java.io.IOException: Server returned HHTP response code:
400 for URL: http://xxx.xxx.xxx.xxx:443/nuova
Do you have to reboot UCS to recover?
What is the newest Java version that UCSM will work with?
.....and please hurry up and get the HTML5 version out!
Try 7 u21 for the moment, that works for me.
Thnx Kenny.....I went to the 7U25 version mentioned below and was able to access the system.....it is painful to have change versions depending on which Cisco application you are trying to access.....Can't wait for them to get rid of Java for UCSM.