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.
Yes, Robert just mentioned that :)
"Yes, developers read these forums. UCSM 3.x will be HTML5 based. Java is on the way out.