topic Re: ML110 G9 Remote Console does not work in HPE ProLiant Servers (ML,DL,SL)

ML110 G9 Remote Console does not work

Robertomcat — Fri, 20 Jul 2018 18:11:01 GMT

Hello good afternoon.

I have a problem with the remote console when I try to run the .NET since the last update in which iLO passed from version 2.55 to 2.60 when I upgraded the server with the last SPP.

From the browsers of Microsoft the .net does not work, but the problem disappears when I run the remote console through Java, since I can execute it from any browser and it works perfectly.

A few days ago I got an email about the problems in general that arise in the servers, and one of them was the problem that I am commenting. This link https://bit.ly/2msZEUm explains how problems can be solved in order to run the remote console through .NET, but I have not been able to run the application and other colleagues who have the same version on other servers run it without problems.

When I click on the .net link, I get the message that I left in an image below.

Details:

INFORMACIÓN DE VERSIÓN DE LA PLATAFORMA
Windows : 10.0.17134.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.7.3056.0 built by: NET472REL1
clr.dll : 4.7.3131.0 built by: NET472REL1LAST
dfdll.dll : 4.7.3056.0 built by: NET472REL1
dfshim.dll : 10.0.17134.1 (WinBuild.160101.0800)

ORÍGENES
Dirección URL de la implementación : https://xxxxxxxxx/html/IRC.application?addr=xxxxxxxxxxxxx&sessionKey=2f6f2&lang=en&port=2&alt_mode=0&cofc_goback=false

RESUMEN DEL ERROR
Abajo se muestra un resumen de los errores; los detalles de estos errores se incluyen en el registro.
* La activación de https://XXXXXXXXXXXXXX/html/IRC.application?addr=XXXXXXXXXXXXX&sessionKey=2f6cd7465&lang=en&port=9&alt_mode=0&cofc_goback=false dio como resultado una excepción. Se detectaron los siguientes mensajes de error:
+ No se realizó la descarga de https://XXXXXXXXXXXX/html/IRC.application?addr=XXXXXXXXXXXXX&sessionKey=2f6f285&lang=en&port=9&alt_mode=0&cofc_goback=false correctamente.
+ Se ha terminado la conexión: No se puede establecer una relación de confianza para el canal seguro SSL/TLS.
+ El certificado remoto no es válido según el procedimiento de validación.

RESUMEN DE ERRORES DE TRANSACCIÓN DEL ALMACÉN DE COMPONENTES
No se detectó ningún error de transacción.

ADVERTENCIAS
No se generó ninguna advertencia durante esta operación.

ESTADO DE PROGRESO DE LA OPERACIÓN
* [20/07/2018 19:18:19] : Se ha iniciado la activación de https://XXXXXXXXXXXXX/html/IRC.application?addr=37&sessionKey=2f6f28&lang=en&port=2&alt_mode=0&cofc_goback=false.

DETALLES DEL ERROR
Se detectaron los siguientes errores durante esta operación.
* [20/07/2018 19:18:20] System.Deployment.Application.DeploymentDownloadException (subtipo desconocido)
- No se realizó la descarga de https://XXXXXXXXXXXX/html/IRC.application?addr=38&sessionKey=2f6f28856cdg=en&port=&alt_mode=0&cofc_goback=false correctamente.
- Origen: System.Deployment
- Seguimiento de la pila:
en System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
en System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
en System.Deployment.Application.FileDownloader.Download(SubscriptionState subState, X509Certificate2 clientCertificate)
en System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
en System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
en System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
en System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
en System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
en System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Excepción interna ---
System.Net.WebException
- Se ha terminado la conexión: No se puede establecer una relación de confianza para el canal seguro SSL/TLS.
- Origen: System
- Seguimiento de la pila:
en System.Net.HttpWebRequest.GetResponse()
en System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
--- Excepción interna ---
System.Security.Authentication.AuthenticationException
- El certificado remoto no es válido según el procedimiento de validación.
- Origen: System
- Seguimiento de la pila:
en System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
en System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
en System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
en System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
en System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
en System.Net.ConnectStream.WriteHeaders(Boolean async)

DETALLES DE TRANSACCIÓN DEL ALMACÉN DE COMPONENTES
No hay información disponible sobre la transacción.

Re: ML110 G9 Remote Console does not work

Jimmy Vance — Fri, 20 Jul 2018 18:51:14 GMT

Have you tried using the stand-alone version of the .net remote console application? I rarely access the console via the iLO web interface anymore. I keep a series of windows shortcuts that take me directly to remote console.

HPE Lights-Out Standalone Remote Console for Windows
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_bc8e3ffa59904ec3b505d9964d

syntax is
hplocons.exe -addr x.x.x.x -name uname -password pword

Re: ML110 G9 Remote Console does not work

Robertomcat — Fri, 20 Jul 2018 20:34:21 GMT

Thanks for your answer.

Yes, I have also used it, but I have not remembered to name it in my comments.

This is the error that it gives me:

Re: ML110 G9 Remote Console does not work

AWarmke — Fri, 20 Jul 2018 20:41:26 GMT

The .NET remote console was re-signed in v2.60, and now requires version 4.5.1 or later of the .NET Framework. I wonder if that might be the issue you are running into?

Release Notes that say that are located here: https://support.hpe.com/hpsc/doc/public/display?docId=c03334036

Take a look and see if any of that helps you.

Regards,

Aggie Warmke
Documentation Program Manager
HPE EG Knowledge Management

Re: ML110 G9 Remote Console does not work

Robertomcat — Fri, 20 Jul 2018 20:54:17 GMT

Thanks for your answer.

I am using the latest version of Windows 10, the 1803, and I think it brings the updated Framework to the latest versions. I also tried to install the newer versions of that software, and before installing it told me that it already had the most modern version.

Suggest that you do some kind of check or something that comes to mind?

I've also tried another computer, and the same error comes out.

Re: ML110 G9 Remote Console does not work

Robertomcat — Sat, 21 Jul 2018 10:06:57 GMT

When I'm on LAN I also get the same error when I try to run the remote console from .NET in both Microsoft browsers.

Re: ML110 G9 Remote Console does not work

KSINGH_2018 — Sat, 21 Jul 2018 14:14:57 GMT

Few suggestions:
To isolate the network/firewall issues kindly establish peer-to-peer connection with ilo port on server and check if the same issue persists on a different browser as well. If yes the kindly perform ilo Factory reset for RBSU, reconfigure it and cross-check with same peer-to-peer connection.

Re: ML110 G9 Remote Console does not work

Robertomcat — Sat, 21 Jul 2018 14:21:26 GMT

Thanks for your reply.

Right now I can not verify what you tell me, since I am 80 km away from the server and I will not go where you are physically in two weeks.

The factory reset of iLO, apart from the restoration of all the ports that could have changed, and the user and password to access, makes some other change?

Re: ML110 G9 Remote Console does not work

KSINGH_2018 — Sat, 21 Jul 2018 23:08:53 GMT

Few more suggestions:

1. Kindly disable "Enforce AES/3DES Encryption" setting from the "iLO web GUI >> Administration >> Security >> Encryption" and retry

2. Kindly esure that TLSv1.2 is enabled on your browser
Internet Options >> Advanced tab >> Ensure that the "Use TLS 1.2" checkbox is checked

3. If the "IRC requires trust" setting (under Remote Console > Security) is enabled, ensure that a valid and trusted SSL certificate is installed in iLO which has not been expired

Re: ML110 G9 Remote Console does not work

Robertomcat — Mon, 23 Jul 2018 15:26:54 GMT

Thanks for your reply.

By disabling the iLO security certificate requirement, the remote console now runs without any problem. I do not understand how it was enabled, it must be the cause of the last update, although later I checked it and made sure it was disabled.

Is there any way to get a certificate for a secure connection?

Re: ML110 G9 Remote Console does not work

Robertomcat — Tue, 24 Jul 2018 09:10:57 GMT

Hello good day.

Yesterday I followed your steps when I was on LAN, and I managed to make it work, but today I'm out of the network and I still have the same problem. When you ran the remote console from the .NET, it does not make any movement or output anything, it does not do anything.

I do not understand what is happening, I have never had problems when using the remote console in any of the servers I have had, and since this version 2.60 this problem has arisen.