CIMC Launch KVM Console

[elarkin01]

I am on the CIMC and when I select Launch KVM Console,  I get a pop up a Do you want to continue ? I select Continue

It goes to starting application, Verifying application. ( takes about a minute )   then pops up a  Do you want to run this application ?

I check accept the risk and run this application.

It automatically goes to Connecting to KVM Server , then Message popup Login Failed or Timed out. Please try again.

I have set up a admin account under admin.

any suggestions would be greatly appreciated

Edith

[Randall White]

Thanks Damon,

That fix worked for me.

[Toivo Voll]

That's crazy. But hey, worked for me as well. I wonder how it's supposed to work.

[CS47]

Worked for me too. (Windows Server 2003 R2 + Java 7 update 67, hitting the same issue)

[Jeremy Coudrain]

worked for me too on OSX.  It was working fine for three days and then changed somehow.  edited the file and good to go.  THANKS DAMON!!!!!

[State924sj1]

Example Please. Could you highlight your changes with a different color or bold them?

[faf1967]

What did you change the user name and password to?

[parx Casino]

This saved my butt, thank you!!!

[asinghi]

Thanks Damon, that was really helpful

[Zaira Vega]

What is your server firmware version?

Older versions require Java 6

[mike.kellys1]

Thanks Damon, that worked for me and made me look like a hero to other people on my team who couldn't get it to work.!!!

[hshahdil]

Debug Logs:

===============

Java Web Start 11.181.2.13 amd64 Using JRE version 1.8.0_181-b13 Java HotSpot(TM) 64-Bit Server VM User home directory = C:\Users\hshahdil ---------------------------------------------------- c: clear console window f: finalize objects on finalization queue g: garbage collect h: display this help message m: print memory usage o: trigger logging p: reload proxy configuration q: hide console r: reload policy configuration s: dump system and deployment properties t: dump thread list v: dump thread stack 0-5: set trace level to ---------------------------------------------------- Missing Application-Name manifest attribute for: https://10.59.227.43:443/software/avctNuova.jar.pack.gz KVM/VM Client Version: 5.04.04 (Build 392) scalingmenuchecked from pref storage = true CMDUtil setscalingon = true Scaling state:true scalingMenuChecked::true defScaleMenuValue::true replace numpad replace numpad ** Max Size: W = 3360 H = 2020 ** Window Pref Size: W = 1050 H = 861 ** Max Size: W = 3360 H = 2020 ** Window Pref Size: W = 1050 H = 861 JNLPClassLoader: Finding library VMAPI_DLL.dll JNLPClassLoader: Finding library jawt.dll JNLPClassLoader: Finding library avctKVMIO.dll ProtocolAPCP.receieveSessionSetup : v1.2 APCP = true APCP Version = 260 Supported protocols: [SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2] Enabled protocols: [TLSv1, TLSv1.1, TLSv1.2] Supported ciphers: [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_EMPTY_RENEGOTIATION_INFO_SCSV, TLS_DH_anon_WITH_AES_256_GCM_SHA384, TLS_DH_anon_WITH_AES_128_GCM_SHA256, TLS_DH_anon_WITH_AES_256_CBC_SHA256, TLS_ECDH_anon_WITH_AES_256_CBC_SHA, TLS_DH_anon_WITH_AES_256_CBC_SHA, TLS_DH_anon_WITH_AES_128_CBC_SHA256, TLS_ECDH_anon_WITH_AES_128_CBC_SHA, TLS_DH_anon_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_DH_anon_WITH_DES_CBC_SHA, TLS_RSA_WITH_NULL_SHA256, TLS_ECDHE_ECDSA_WITH_NULL_SHA, TLS_ECDHE_RSA_WITH_NULL_SHA, SSL_RSA_WITH_NULL_SHA, TLS_ECDH_ECDSA_WITH_NULL_SHA, TLS_ECDH_RSA_WITH_NULL_SHA, TLS_ECDH_anon_WITH_NULL_SHA, SSL_RSA_WITH_NULL_MD5, TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5] Enabled ciphers: [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256] SSL session using protocol TLSv1.2, cipher suite TLS_RSA_WITH_AES_128_CBC_SHA KVMIOWindowListener::setup KVMIOWindowListener::setup m_preemptionSharing::0 CMDUtil setscalingon = true CMDUtil setscalingon = true

[GeorgePerkins0204]

In my particular situation I was getting this error: kvm unable to launch the application Server returned HTTP response code: 403 for URL /software/avctNuova.jar.pack.gz

My solution was to edit the viewer.jnlp file in Notepad++. For unknown reasons this file contained an incorrect IP address. I did a replace all operation to change the IP to match my CIMC's IP. Then re-launched and Java prompted me for the usual security warnings and successfully opened the KVM.

Windows 10

Java 8 Update 221

CIMC 4.0(2f) on a Cisco S3260M4

[SriramVS62525]

In case the suggested solution did not work for you. Please try the following steps which helped me resolve my issue. 

KVM Console is not Working

• Make a note of the service profile template the service profile is attached to.
• Unbind the service profile template from service profile. Now you will notice the Change Management IP address option will get highlighted.
• Click Change the Management IP address and choose static instead of esx-mgmt. Enter an unused ip address from the esx-mgmt pool. [Better to choose an ip address on the far range.] Eg:
  10.x.x.233
  255.x.x.x
  10.x.x.1.
  Click OK & close the Window.
• Now when you launch KVM console, you will notice 2 options namely
  open KVM console with the given static IP or
  with derived IP address from the pool.
  you will be able to open KVM console with either of them.
• Click Change the Management IP address once again & this time choose esx-mgmt instead of static and Click OK. Close the Window.
• Check if KVM console is working again.
• Bind the service profile back to the same service profile template & close.

Thanks ! ! 

Sriram V S