SCS Console operation errors
Hi there,
I have been paying attention to console operation logs after reapplying configuration and I'm interested in undestanding this one:
Date and time: 9/18/2007 10:43:35 AM
Severity: Error
Error Code: 2202
Server name: TFSRTM
User name: AMTadmin
Platform UUID: 92CF7A0B-094A-DC11-9622-00E018889BFA
Platform FQDN:
Operation ID: 471
Description: Error Configuring Intel AMT device: Failed to connect to configured Intel AMT device at FQDN LINTVPRO-PC.AMT.LOCAL: AMT Connection Error: SOAP Error [24]: "getFullCoreVersion: Fault: 'No Data' : Details: 'get host by name failed in tcp_connect()'".
The AMT device is configured OK, but I can see error logs like one above and I can not access it by its Web UI (and of course it's Web UI profile enabled), so I think these issues are related each other.
Many thanks,
Javier Andrés
|
Re: SCS Console operation errors
Javiar,
This looks like it's not able to resolve the FQDN (LINTVPRO-PC.MT.LOCAL) correctly. If you ping that FQDN, can you find it? You could also try connecting to the web interface with IP address instead of FQDN, if that works then SCS isn't resolving the FQDN correctly.
This could be related to configuring the DHCP server to handle DNS registration of the AMT device, there's documentation about this starting at the bottom of page 104 in the SCS Installation guide (Edit: I forgot to add the title of the section, it's "Registering Intel AMT Devices in the DNS")
|
Re: SCS Console operation errors
Hello Andres,
I installed DHCP (It was missing) and re-configured server again and I don't get those erroes now but when I tried to re-apply configuration in log appeared these entries:
2007.09.25,16:19:46,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.WorkersWorkerThread.cpp,LINE=116,
Configuring Intel AMT device started.
2007.09.25,16:19:46,INFORMATIONAL,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.WorkersProvisionerWorker.cpp,LINE=23,
Enter provisioner worker, user AMTadmin
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #1 failed: WS-Management [13]: "Error calling WSMan getFullCoreVersion(CIM_SoftwareIdentity.Get): TCP error".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #2 failed: WS-Management [1]: "Error calling WSMan getFullCoreVersion(CIM_SoftwareIdentity.Get): General WSMan error".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #3 failed: AMT Connection Error: SOAP Error [-1]: "getFullCoreVersion: SOAP Unknown error".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #4 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #5 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #6 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:20:16,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #7 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:20:16,ERROR,SERVER=1,USER=AMTadmin,THREAD=652,SOURCE=.WorkersWorkerThread.cpp,LINE=145,
Error Configuring Intel AMT device: Failed to connect to configured Intel AMT device at FQDN LINTVPRO-PC.AMT.LOCAL: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:21:09,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=2016,SOURCE=.WorkersWorkerThread.cpp,LINE=116,
Maintenance started.
2007.09.25,16:21:09,INFORMATIONAL,SERVER=1,USER=AMTadmin,THREAD=2016,SOURCE=.WorkersMaintenanceWorker.cpp,LINE=20,
Enter Maintenance worker, user AMTadmin
2007.09.25,16:21:09,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=2016,SOURCE=.WorkersWorkerThread.cpp,LINE=126,
Maintenance completed successfully.
I can't enter the Web UI.
Many thanks,
|
Re: SCS Console operation errors
I forgot to mention that in platform collection panel (SCS Console 5.0) platform is marked as configured with verion 3.2.1 but when I click on it to check deatils I can see in History tab the "Reaply Configuration" operation marked as Delayed".
Thanks,
Javier Andrés
|
Re: SCS Console operation errors
Hello there,
I also forget to mention that before I installed DHCP server when I ping to AMT machine there was no reply, but now I can ping the FQDN or machine name or machine IP and there is always a reply.
Here another block of last log entries:
2007.09.25,16:36:09,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=3844,SOURCE=.WorkersWorkerThread.cpp,LINE=116,
Maintenance started.
2007.09.25,16:36:09,INFORMATIONAL,SERVER=1,USER=AMTadmin,THREAD=3844,SOURCE=.WorkersMaintenanceWorker.cpp,LINE=20,
Enter Maintenance worker, user AMTadmin
2007.09.25,16:36:09,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=3844,SOURCE=.WorkersWorkerThread.cpp,LINE=126,
Maintenance completed successfully.
2007.09.25,16:36:18,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.WorkersWorkerThread.cpp,LINE=116,
Configuring Intel AMT device started.
2007.09.25,16:36:18,INFORMATIONAL,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.WorkersProvisionerWorker.cpp,LINE=23,
Enter provisioner worker, user AMTadmin
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #1 failed: WS-Management [13]: "Error calling WSMan getFullCoreVersion(CIM_SoftwareIdentity.Get): TCP error".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #2 failed: WS-Management [1]: "Error calling WSMan getFullCoreVersion(CIM_SoftwareIdentity.Get): General WSMan error".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #3 failed: AMT Connection Error: SOAP Error [-1]: "getFullCoreVersion: SOAP Unknown error".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #4 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #5 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #6 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:36:48,SUCCESS,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.AMTConnectionAMTConnection.cpp,LINE=315,
The SOAP connection with connection parameter set #7 failed: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
2007.09.25,16:36:48,ERROR,SERVER=1,USER=AMTadmin,THREAD=1876,SOURCE=.WorkersWorkerThread.cpp,LINE=145,
Error Configuring Intel AMT device: Failed to connect to configured Intel AMT device at FQDN LINTVPRO-PC.AMT.LOCAL: AMT Connection Error: SOAP Error [26]: "getFullCoreVersion: Fault: 'EOF was observed that violates the protocol. The client probably provided invalid authentication information.' : Details: 'SSL connect failed in tcp_connect()'".
Many thanks,
Javier Andrés
|
Re: SCS Console operation errors
Hi there, Any idea? Thanks, Javier Andrés
|
Re: SCS Console operation errors
Hi there, I'm still getting the same error. Has anybody got the same one? Thanks, Javier Andrés Cáceres Alvis
|
Re: SCS Console operation errors
Hi there, I'm still getting the same error. Has anybody got the same one? Thanks, Javier Andrés Cáceres Alvis Sorry I didn't reply sooner Javier, we just changed forums and I initially lost my e-mail updates that there were new posts. It sounds like SCS wasn't able to fully provision the system, if "Delayed" is showing up in the status. If SCS got the hello packet, but wasn't able to get back to the system to finish the configuration (if there were DHCP problems this could happen), it wouldn't be fully configured. That would explain why the WebUI for the system isn't coming up, since until the AMT system hears back from SCS (or some other configuration server), it's not provisioned yet. One option is that you clear the system out of SCS and reprovision. You could either put Activator on the system to kick off hello packets again, or reset and reconfigure the AMT system. The other possibility is that something isn't set right in the AMT system that is preventing SCS from connecting. How did you initially setup the AMT system for provisioning? Did you use a USB key, or did you manually enter data into the ME? For either option, could you tell me what options you set when you were configuring the AMT system?
|
Re: SCS Console operation errors
Hello Andrew,
Many thanks for your post. I have also found some issues regarding forums change.
Here my answers:
-I manually entered PID/PPS into the ME.
-I set these options: Provision Mode (Enterprise), OTC (PID/PPS), DHCP enabled & domain name.
-I have reset and reconfigure the AMT system many times with same result.
-I'm sure DHCP is working fine.
-The Delayed status is in Re-Apply configuration operation; I decided re applied configuration cause I'm not able to connect via Web UI.
Many Thanks,
Javier Andrés Cáceres
|
Re: SCS Console operation errors
Hello Andrew, Do you need I provide more information? Many thanks, Javier Andrés
|
Re: SCS Console operation errors
Hmm, possibly. Is SCS attempting to use the default profile? The reason I ask is that WebUI is enabled in the default profile. I find it very suspicious that SCS is finding the system initially, but then not only does the WebUI not work, but you also can't reapply changes.
Do you always have this behavior with the AMT system you're configuring? Or have you configured and had the WebUI work?
| |
