cancel
Showing results for 
Search instead for 
Did you mean: 

HANA System Replication using internal hostnames

kashyap_shah3
Contributor

Hello,

I had HANA System Replication enabled between Primary (sapshdb001) and Secondary (sapshdb002) system using public network interface i.e. using same IP range that SAP application uses to connect to HANA. That worked completely fine.

I am now trying to secure HSR using separate internal network defined within HANA system topology by system_replication_hostname_resolution from global.ini and not /etc/hosts config.

As per Host Name Resolution for System Replication documentation, I've defined listeninterface parameter from system_replication_communication to .global and defined system_replication_hostname_resolution section as

10.5.2.1 sapshdb002 - at System level on Primary system
10.5.1.1 sapshdb001 - at System level on Secondary system

As per documentation, above minimum configuration should have worked but I see erros in nameserver trace on Secondary as attached. I've also raised incident with SAP with no resolution as yet. It would be really helpful to know if anyone have done similar setup and how.

Please Note: HANA release is 2.0 SP 04
Firewall at OS level is disabled on both Primary and Secondary, also there's no firewall between Priamry and Secondary. Again as I mentioned earlier, not using separate internal network but public, HSR had worked fine.

Thanks.

Best Regards,
Kashyap Shah

View Entire Topic
ravindrakumartbc
Explorer
0 Kudos

Hi Kashyap, thanks for your response . we have followed what you had advice in your thread .

below is our setup .

Redhat scale up HA cluster . Two hana standalone nodes on two Redhat boxes. Isolation is enabled.

HANA client Lan is 10.250.150.x . when i enabled replication by using this lan all work fine.

in order to make replication traffic on separate lan i assign replication host name in global.ini as 10.250.145.x than our replication wont work , throw error regarding 40002 ports error.

trying to follow below blog from SAP. but issue remain the same .

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/c0cba1cb2ba34ec89f45b48b21...