Start a Conversation

Unsolved

DC

4 Posts

3441

September 28th, 2021 17:00

Cannot add adaptor

When trying to connect an adapter for Openmanage Enterprise, i recieve the following error:
 
Connection error. Check that hostname or IP address 10.102.239.65 over port 443 is configured correctly and can be reached through the gateway.
Error Code: SAE-170031
 
From the application.log
ce Proxy is  successfullio.vertx.servicediscovery.Record @9017d8ba
29  Sep  2021   10:12:26,174  [ vert.x-eventloop-thread-4 ]  INFO    com.dell.sae.orchestrator.executors.DomainServiceExecutor-   82  - Orchestration layer before invoking domain service interface  com.dell.sae.common.services.appscommon.AdapterAppsCommonService  and method addAdapter  1632874346174
29  Sep  2021   10:12:26,426  [ vert.x-eventloop-thread-4 ]  INFO    com.dell.sae.orchestrator.executors.DomainServiceExecutor-   97  - Orchestration Invoke domain service is completed  1632874346426
29  Sep  2021   10:12:26,427  [ vert.x-eventloop-thread-4 ]  ERROR   com.dell.sae.orchestrator.executors.DomainServiceExecutor-   104  - Invoke is Failed :(RECIPIENT_FAILURE, 0 ) Connection error. Check that hostname or IP address  10 . 102 . 239 . 65  over port  443  is configured correctly and can be reached through the gateway.
29  Sep  2021   10:12:26,427  [ vert.x-eventloop-thread-4 ]  ERROR   com.dell.sae.orchestrator.executors.SimpleJobExecutor-   54  - simple workflow execution  failed: {}
com.dell.sae.commons.exceptions.AdapterException : Connection error. Check that hostname or IP address  10 . 102 . 239 . 65  over port  443  is configured correctly and can be reached through the gateway.
    at com.dell.sae.commons.exceptions.AdapterExceptionMessageCodec.decodeFromWire(AdapterExceptionMessageCodec.java:49) ~[utilities-5.0.0.0-APPLIANCE.RELEASE.jar:?]
    at com.dell.sae.commons.exceptions.AdapterExceptionMessageCodec.decodeFromWire(AdapterExceptionMessageCodec.java:9) ~[utilities-5.0.0.0-APPLIANCE.RELEASE.jar:?]
    at io.vertx.core.eventbus.impl.clustered.ClusteredMessage.decodeBody(ClusteredMessage.java:191) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.clustered.ClusteredMessage.body(ClusteredMessage.java:93) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.EventBusImpl.lambda$convertHandler$2(EventBusImpl.java:332) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:278) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:264) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.EventBusImpl$InboundDeliveryContext.next(EventBusImpl.java:567) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$4(EventBusImpl.java:527) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:366) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.vertx.core.impl.EventLoopContext.lambda$executeAsync$0(EventLoopContext.java:38) ~[vertx-core-3.9.5.jar:3.9.5]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) [netty-common-4.1.49.Final.jar:4.1.49.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) [netty-common-4.1.49.Final.jar:4.1.49.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [netty-transport-4.1.49.Final.jar:4.1.49.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-common-4.1.49.Final.jar:4.1.49.Final]
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.49.Final.jar:4.1.49.Final]
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.49.Final.jar:4.1.49.Final]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]

3 Posts

September 28th, 2021 19:00

I also have this issue. It works on Support Assist Enterprise without any issues.

I also cannot get it to connect to my smtprelay server where all other servers are working fine.

3 Posts

September 28th, 2021 20:00

I also have this issue (Adapter). It works on Support Assist Enterprise without any issues.

 

I also cannot get it to connect to my smtprelay server where all other servers are working fine.

It seems that the VE appliance is trying to authenticate to the SMTP Relay server, even with authentication disabled..

 

crashinit6_0-1632884886157.png

 

Moderator

 • 

3.5K Posts

September 28th, 2021 23:00

Hello @Dewey Cox, Hi @crashinit6,

 

The error seems to be point to the connection issue from the OME adapter, via port 443. Could you check out the documentation page 10 on network requirements: https://dell.to/2ZHlJFB both inbound and outbound requirement on port 443. 

 

 

3 Posts

September 29th, 2021 01:00

Hi Joey,

 

SCG and OME are on the same subnet and I have not enabled FW rules on the appliances themselves and they were deployed via OVMs within vCenter.

Our older Support Assist Enterprise VE appliance is able to connect to OME which are also on the same subnet so not sure this is a Firewall issue or networking issue.

 

Also, Any Idea around the SMTP error? Again, this is not an issue with the SMTP relay server and there are other devices using it currently without any issues. I believe that the Appliance is still enabling authentication even when disabled.

 

Thanks

 

Criag

Moderator

 • 

3.5K Posts

September 29th, 2021 02:00

Hello Craig (hopefully I get you name correctly),

 

I'm fairly new to SCG board, I'll try my best to help out. From where the error on SCG and OME adapter configuration error, it seems to be a firewall issue. I had a simple review on SAE and SCG network requirement, both seems to be similar. But on Page 24: https://dell.to/2Yd0J97, it seems we may have to troubleshoot based on what is required to narrow down the root cause. 

 

Can you let me know if you're trying to configure SMTP settings, at page 56 https://dell.to/3F3C5s8 and having the error?

 

September 30th, 2021 18:00

As already mentioned, it's not firewall related, it's an issue with the appliance.

 

 

01 Oct 2021 11:10:26,621 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.vertx.AdapterService- 132 - Inside add adapter method
01 Oct 2021 11:10:26,635 [vert.x-eventloop-thread-1] INFO com.dell.sae.commons.utility.ServiceProxyDiscovery- 63 - Get Service Proxy is Called starts
01 Oct 2021 11:10:26,636 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.util.ExternalModuleService- 114 - Successfully fetched the InventoryAppsCommonService handler
01 Oct 2021 11:10:26,645 [vert.x-eventloop-thread-1] INFO com.dell.sae.commons.utility.ServiceProxyDiscovery- 66 - Get Service Proxy is Called
01 Oct 2021 11:10:26,646 [vert.x-eventloop-thread-1] INFO com.dell.sae.commons.utility.ServiceProxyDiscovery- 68 - Get Service Proxy is successfullio.vertx.servicediscovery.Record@245aefac
01 Oct 2021 11:10:26,655 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.util.ExternalModuleService- 107 - Successfully fetched inventoryAppsCommonService service instance
01 Oct 2021 11:10:26,655 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.util.ExternalModuleService- 129 - Successfully fetched inventory application proxy service service instance
01 Oct 2021 11:10:26,682 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.util.ExternalModuleService- 215 - Successfully fetched the Credential profile for the given id
01 Oct 2021 11:10:26,690 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.dao.impl.AdapterDAO- 82 - Successfully executed query in getAdapterByHostAddressOrHostName operation
01 Oct 2021 11:10:26,690 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.vertx.AdapterDatabaseServiceImpl- 237 - Duplicate adapter doesn't exist with the given hostname
01 Oct 2021 11:10:26,692 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.vertx.AdapterDatabaseServiceImpl- 138 - Started checkIfFriendlyNameIsDuplicate method
01 Oct 2021 11:10:26,693 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.dao.impl.AdapterDAO- 234 - Inside getAdaptersByFriendlyName method
01 Oct 2021 11:10:26,695 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.dao.impl.AdapterDAO- 60 - Successfully executed the query in getAdaptersByFriendlyName operation
01 Oct 2021 11:10:26,695 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.vertx.AdapterDatabaseServiceImpl- 182 - Successfully fetched adapters with given friendly name
01 Oct 2021 11:10:26,695 [vert.x-eventloop-thread-2] INFO com.dell.sae.adapter.appscommon.persistence.vertx.AdapterDatabaseServiceImpl- 153 - Duplicate adapter is not found with this friendly name: ome
01 Oct 2021 11:10:26,696 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.appscommon.service.util.AdapterHelper- 38 - Started transformToAdapterObj method
01 Oct 2021 11:10:26,712 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 53 - Method getConsoleAPI execution started, returning client instance
01 Oct 2021 11:10:26,731 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 290 - Execution of getHttpOptions method started
01 Oct 2021 11:10:26,732 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 301 - Execution of getHttpOptions method done, returning HTTP Client Options
01 Oct 2021 11:10:26,733 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 278 - Execution of getRequestInterceptor method started
01 Oct 2021 11:10:26,733 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 280 - Execution of getRequestInterceptor method done, returning Request Interceptor
01 Oct 2021 11:10:26,842 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.api.helper.ClientTrustOptions- 26 - Creating custom Reloadable Trsut Manager Factory.
01 Oct 2021 11:10:26,935 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.AdapterUtility- 44 - Inside method getAuthorizationHeader to create authorization header
01 Oct 2021 11:10:26,954 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.AdapterUtility- 54 - Returning authorization header to Caller....
01 Oct 2021 11:10:26,956 [OMENTERPRISE_THREAD_POOL-0] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 178 - Inside execute Task
01 Oct 2021 11:10:26,960 [OMENTERPRISE_THREAD_POOL-0] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 36 - Execution of method apply started
01 Oct 2021 11:10:26,961 [OMENTERPRISE_THREAD_POOL-0] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 43 - Execution of method getHeaderValue started
01 Oct 2021 11:10:26,961 [OMENTERPRISE_THREAD_POOL-0] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 50 - Execution of method getHeaderValue started, returning header value
01 Oct 2021 11:10:26,961 [OMENTERPRISE_THREAD_POOL-0] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 39 - Execution of method apply is done
01 Oct 2021 11:10:27,073 [vert.x-eventloop-thread-1] ERROR com.dell.sae.adapter.common.api.helper.ClientTrustOptions- 46 - Exception:Issued certificate not matched with the DN.
01 Oct 2021 11:10:27,242 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 36 - Execution of method apply started
01 Oct 2021 11:10:27,243 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 43 - Execution of method getHeaderValue started
01 Oct 2021 11:10:27,243 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 50 - Execution of method getHeaderValue started, returning header value
01 Oct 2021 11:10:27,243 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.HttpRequestInterceptor- 39 - Execution of method apply is done
01 Oct 2021 11:10:27,259 [vert.x-eventloop-thread-1] ERROR com.dell.sae.adapter.common.api.helper.ClientTrustOptions- 46 - Exception:Issued certificate not matched with the DN.
01 Oct 2021 11:10:27,263 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.omenterprise.rest.helper.ConsoleAPIHelper- 167 - OMENTERPRISE_SYSTEM_TIME completed
01 Oct 2021 11:10:27,263 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.AdapterUtility- 106 - Execution of method
01 Oct 2021 11:10:27,263 [vert.x-eventloop-thread-1] ERROR com.dell.sae.adapter.common.util.AdapterUtility- 123 - Cause in Response Object from OMEnterprise is nullfor operatio type : OMENTERPRISE_SYSTEM_TIME with params : null
01 Oct 2021 11:10:27,263 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.AdapterUtility- 167 - Method getErrorJsonObject execution started
01 Oct 2021 11:10:27,264 [vert.x-eventloop-thread-1] INFO com.dell.sae.adapter.common.util.AdapterUtility- 173 - Error model is created with httpstatus as 500 ,errorcode as , errorReason as Cause in Response Object from OMEnterprise is null and errorMEssage as Cause in Response Object from OMEnterprise is null
01 Oct 2021 11:10:27,267 [vert.x-eventloop-thread-1] ERROR com.dell.sae.adapter.appscommon.service.util.OMEnterpriseAPIService- 99 - Failed to get OMEnterprise system time with cause : {}
io.vertx.core.impl.NoStackTraceThrowable: {"errorCode":"Adapter-201","errorMessage":"AdapterNotReachable","httpStatus":500,"errorReason":"Cause in Response Object from OMEnterprise is null"}
01 Oct 2021 11:10:27,288 [vert.x-eventloop-thread-1] ERROR com.dell.sae.adapter.appscommon.service.domainservice.AdapterAppsCommonServiceImpl- 57 - Error Occurred while adding lex adapter
01 Oct 2021 11:10:27,292 [vert.x-eventloop-thread-1] INFO com.dell.sae.services.logactivity.factory.ServiceProxyFactory- 34 - getAuditService method called.

 

Moderator

 • 

3.5K Posts

September 30th, 2021 21:00

Hi @Dewey Cox,

 

Understood. Perhaps I may need to check with engineering about the issue, I'll be getting back to you. Would you please PM me the following detail of SCG SWID (Software ID), it's located in the software About section and the server's service tag which SCG appliance is installed. 

October 5th, 2021 15:00

Sure, PM sent.

Moderator

 • 

3.5K Posts

October 5th, 2021 17:00

Hi @Dewey Cox,

 

Thanks for the PM information. I'll be corresponding to your via PM to work with you on the issue.

October 12th, 2021 13:00

Hi,

Just to add to this i'm also having the same issue with SMTP and unable to add an SMTP server, other dell/emc systems can send email without any issue, so be good to know the outcome from engineering.

thanks,

Steve

Gateway version 5.00.00.10

Moderator

 • 

3.9K Posts

October 12th, 2021 13:00

Hello stephen.ion,

 

Joey is off shift at the moment but I will get in contact with him to see what he found out.

 

Some information I can see:

 

SCG only support OME 3.6.1. The error may occur due to compatibility issue.

 

Ref: Page 47 https://dell.to/3ljsEwW

 

Also noted a new version of SCG is coming out but no release date listed at this time.

 

Moderator

 • 

3.5K Posts

October 15th, 2021 00:00

Hi,

 

Based on the error message, the SCG is unable to communicate with OME due to it's compatibility. If OME version is higher than 3.6.1, you may face such issue. Unfortunately, I wasn't told when the new version of SCG is coming.

1 Message

November 15th, 2021 17:00

What more info do you need to address this issue? I've updated to OME version 3.8.0 (Build 35), using Services plugin 1.2.0.515. When attempting to create an adapter In Secure Connect Gateway version 5.00.00.10, I'm prompted with Error Code: SAE-170031 "Check that hostname or IP address ome.rockstargames.com over port 443 is configured correctly and can be reached through the gateway."

Like the original post, I'm on the same vlan with no firewall in place.  Prior to SCG we were using Support Assist Enterprise with no issues when connecting to our OME instance.

Moderator

 • 

4.3K Posts

November 15th, 2021 22:00

Hi, at this point,

Would you try

downgrading OME version to lower than 3.6.1?

 

Secure Connect Gateway 5.00.00.xy — Application Edition Support Matrix (https://dell.to/3qHrYEA)

 

(Please refer to page 32)

 

No Events found!

Top