2815876 - DNS Caching leads to SAP Cloud Connector connection issues

Symptom

Connection from SAP Cloud Connector(SCC) to SAP BTP Cloud Platform fails, upon checking SCC trace (ljs_Trace.log/scc_core.trc) it's perceived an IP address change according to below:

#TRACE#com.sap.core.connectivity.tunnel.core.Tunnel#metering-scheduler-111-1#0x00000000#Will send message of type 4 with size 4,680 over tunnel channel [id: 0x6149ab89, L:/<LocalIpAddress>:<LocalPort> - R:connectivitynotification.cf.ap10.hana.ondemand.com/54.79.5.6:443]. Tunnel id: "account:///..."|

#ERROR#com.sap.core.connectivity.tunnel.client.notification.NotificationClient#notification-client-100-5# #Unable to handshake with notification server connectivitynotification.cf.ap10.hana.ondemand.com/3.105.155.106:443 io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out:

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP Cloud Connector(SCC) older than 2.12.

Product

SAP BTP, Neo environment 1.0 ; SAP Connectivity service 2.0

Keywords

AlwaysCompressed, DNS, IP, IP Addresses, IP address, hostname, host, change, deviate, new ip, proxy, SCC, BTP, SCC, cloud connector, CC, connector, com.sap.core.connectivity.tunnel.core.Tunnel, tunnel, subaccount, sub-account, sub account, tenant, timeout time out, timed out, hana.ondemand.com, cf10, cf, Neo, cloud foundry, DNS, network, name resolution, name translation , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-CON , Neo to On-premise Connectivity service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.