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) 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:/10.123.32.51:9972 - 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:

Environment

SAP Cloud Connector(SCC) older than 2.12.

Product

SAP BTP, Neo environment 1.0 ; SAP Connectivity service 2.0

Keywords

Production, ABAP R/3, ERP, SRM, CRM, ERP, PPM, SEM, APO, XI, PI, PORTAL, Test, development, QA, KBA, On Premise, HANA Database, SAP Cloud Platform, Cloud Connector, xsodata, On-Premise, Access, large, datasets, AlwaysCompressed, DNS, IP, IP Addresses, IP address, hostname, host, change, deviate, new ip, proxy, SCC, BTP , 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.