Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Azure will be chosen as SyWay cloud service provider for all regions.
  • Syensqo network will connect to Azure tenants via ExpressRoute for all regions
  • Standard SAP RISE integration patterns will be leveraged when integrating S/4HANA, SAP connectors and SAP SaaS applications. 
  • As of writing this document, there are pending architectural decisions regarding North America & China , and RISE infrastructure. These designs will be added to this document as they are finalized.

...

In addition to the different hosting models, SyWay systems can be deployed to 1 or more regions (North America, Europe EU or to both EU and China )regions. The  The figure below describes how SyWay systems are deployed across Syensqo’s network.

...

draw.io Diagram
bordertrue
diagramNameUntitled Diagram-1744691252359
simpleViewerfalse
width1250
linksauto
tbstyletop
lboxtrue
diagramWidth13321591
height901509
revision34

Infrastructure Architecture

...

S/4HANA is hosted in SAP RISE along with supporting connectors and web dispatchers. SyWay project would leverage a common Sandbox, Development landscape that are deployed in Europe region and individual Integration Testing, Training, UAT, Parallel Testing and Production systems that are deployed to all three EU and China regions.

The table below lists the landscape, systems and the corresponding system ID (SID) for the three different regions.

WR2North AmericaEXT HXTWXTEX2 HX2WX2UATEXQ HXQWXQEX1 HX1WX1EXP HXP)

China

Region

Landscape

Systems

S/4HANA (HANA DB)

Web Dispatcher

SAP Cloud connector

SAP Data Provisioning Agent

SAC Agent

OpenText Connector

Europe

Sandbox

ERS (HRS)

WRS

N/A

N/A

N/A

N/A

Development

ERD (HRD)

WRD

CRD1

DRD1

SRD1

ORD1

Integration Testing

ERT (HRT)

WRT

N/A

N/A

N/A

N/A

Training

ER2 (HR2)

N/A

N/A

N/A

N/A

N/A

UAT

ERQ (HRQ)

WRQ

N/A

N/A

N/A

N/A

Parallel TestingRun

ER1 (HR1)

WR13

N/A

N/A

N/A

N/A

Production

ERP (HRP)

WRP & WRH

CRP

DRP

SRP

ORP



China

Integration TestingDevelopment

ECD (

HCD)2

WCD2

CXDCCD1

DXDDCD1

SXDSCD1

TBCOCD1

TrainingIntegration Testing

ECT (

HCT)

WCT

N/A

N/A

N/A

N/A

Training

EC2 (

HC2)

N/A

N/A

N/A

N/A

N/A

Parallel TestingUAT

ECQ (

HCQ)

WCQ

N/A

N/A

N/A

N/A

Training

EC2 (HC2)

WC2

Production Parallel Run

EC1 (

WXP

CXP

DXP

SXP

TBC

Integration Testing

ECT (HCT)

WCT

CCD1

DCD1

SCD1

OCD1

HC1)

WC13

N/A

N/A

N/A

N/A

UATProduction

ECQ ECP (HCQHCP)

WCP

WCQCCP

N/A

N/A

N/A

N/A

Parallel Testing

EC1 (HC1)

WC1

N/A

N/A

N/A

N/A

Production

ECP (HCP)

WCP

CCP

DCP

SCP

OCP

DCP

SCP

OCP

 1System shared across all non-PRD systems

Landscape Provisioning

The following diagrams illustrates the different RISE landscapes that are provision for the different phases. Post Go-Live, INT and PAR landscapes will be decommissioned and a 5 tier landscape will be maintained.

Europe

Image Removed

High Availability and Disaster Recovery

The table below summaries the SLA for HA and DR for production and non-production systems

...

S/4HANA

In SAP RISE, High Availability (HA) and Disaster Recovery (DR) is applicable to Production instances. For SyWay project, S/4HANA Production is provisioned with the following RISE add-ons.

  • Short distance disaster recovery
  • 99.9% SLA

With these add-ons, S/4HANA production is deployed across 2 availability zones with synchronous database replication and automated fail-over via pacemaker clusters as shown below.

draw.io Diagram
bordertrue
diagramNameSAP HA-DR
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth453
height488
revision3

The table below describes how HA is achieved for the different components.

...

.

2SAP RISE requires each region to host a development system which will be used for RISE administrations (e.g., upgrades). Hence ECD and WCD will be in the landscape and will be added to the transport route but not have a system role.

3Web dispatcher will be shared between Parallel Run and Training landscape. 

Post Go-Live Landscape

Post release 4 Group 2 go-live a 4-tier landscape (DEV, QAS, PAR and PRD) will be maintained. SBX, INT and TRG landscapes will be decommissioned. 

Region

Landscape

Systems

S/4HANA (HANA DB)

Web Dispatcher

SAP Cloud connector

SAP Data Provisioning Agent

SAC Agent

OpenText Connector

Europe

Development

ERD (HRD)

WRD

CRD1

DRD1

SRD1

ORD1

UAT

ERQ (HRQ)

WRQ

N/A

N/A

N/A

N/A

Parallel Testing

ER1 (HR1)

WR1

N/A

N/A

N/A

N/A

Production

ERP (HRP)

WRP & WRH

CRP

DRP

SRP

ORP

China

Development

ECD (HCD)2

WCD2

CCD1

DCD1

SCD1

OCD1

UAT

ECQ (HCQ)

WCQ

N/A

N/A

N/A

N/A

Parallel Testing

EC1 (HC1)

WC1

N/A

N/A

N/A

N/A

Production

ECP (HCP)

WCP & WCH

CCP

DCP

SCP

OCP

 1System shared across all non-PRD systems.

2SAP RISE requires each region to host a development system which will be used for RISE administrations (e.g., upgrades). Hence ECD and WCD will be in the landscape and will be added to the transport route but not have a system role.

High Availability and Disaster Recovery

The table below summaries the SLA for HA and DR for production and non-production systems

LandscapeAvailability SLARPORTO
Production99.9%0Contractually-guaranteed: 12 hours
Achievable: ~10 minutes
Non-Production98%N/AN/A

S/4HANA

In SAP RISE, High Availability (HA) and Disaster Recovery (DR) is applicable to Production instances. For SyWay project, S/4HANA Production is provisioned with the following RISE add-ons.

  • Short distance disaster recovery
  • 99.9% SLA

With these add-ons, S/4HANA production is deployed across 2 availability zones with synchronous database replication and automated fail-over via pacemaker clusters as shown below.

draw.io Diagram
bordertrue
diagramNameSAP HA-DR
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth453
height488
revision3

The table below describes how HA is achieved for the different components.

ComponentHA Design
Web DispatcherDeployed to both AZs in active-active configuration and Azure load balancer is used to distribute incoming HTTP traffic to both instances.
S/4HANA Application serversTwo application servers are deployed to each AZs in an active-active configuration.
S/4HANA Message server (SCS & ERS)Pacemaker cluster is configured between SCS and ERS servers to ensure SCS & ERS services fails over accordingly in the event of a failure.
SAPMNT Shared folderNetApp files is used to host the SAPMNT shared folder and is mounted across all S/4HANA application, SCS and ERS servers.
HANA DBTwo HANA nodes are deployed across 2 AZs in an active-standby configuration. HANA synchronous replication is configured to replicate data from the active to standby node. Pacemaker cluster is configured to ensure that the standby node is promoted to active node in the event of a failure.

SAP Connectors

Two instances of SAP Cloud connectors are deployed across 2 AZs and configured as active-standby nodes. In the event of a failure, the standby node will take over as active node

The following connectors do not have out of the box high-availability and will require SAP RISE team to manually failover the system in the event of a failure.

SAP RISE VM Details

Azure RegionEnvironmentSIDPurposePhysical HostnameVirtual HostnameCPUMemory/GBOS
North Europe (Dublin)

SandboxERSApp Server

hec42v331805.irl

SAP Connectors

Two instances of SAP Cloud connectors are deployed across 2 AZs and configured as active-standby nodes. In the event of a failure, the standby node will take over as active node

The following connectors do not have out of the box high-availability and will require SAP RISE team to manually failover the system in the event of a failure.

SAP RISE VM Details

Azure RegionEnvironmentSIDPurposePhysical HostnameVirtual HostnameCPUMemory/GBOSNorth Europe (Dublin)
SandboxERSApp Server

hec42v331805.irl.sap.eu.cloud.syensqo.com (172.16.33.10)

vhysqersci.sap.eu.cloud.syensqo.com (172.16.33.12)
vhysqerscs.sap.eu.cloud.syensqo.com (172.16.33.11)

1664SUSE SLES15HRSHANA DBhec42v331250.irl.sap.eu.cloud.syensqo.com (172.16.33.5)

vhysqersdb.sap.eu.cloud.syensqo.com (172.16.33.13)
vhysqhrsdb01.sap.eu.cloud.syensqo.com (172.16.33.8)
vhysqhrsdb.sap.eu.cloud.syensqo.com (172.16.33.7)

32256SUSE SLES15WRSWeb Dispatcherhec42v331253.irl.sap.eu.cloud.syensqo.com (172.16.33.6)

vhysqwrswd01.sap.eu.cloud.syensqo.com (172.16.33.9)

28SUSE SLES15DevelopmentERDApp Serverhec42v303048.irl.sap.eu.cloud.syensqo.com (172.16.33.48)

vhysqerdci.sap.eu.cloud.syensqo.com (172.16.33.49)
vhysqerdcs.sap.eu.cloud.syensqo.com (172.16.33.50)

864SUSE SLES15HRDHANA DB

hec42v302672.irl.sap.eu.cloud.syensqo.com (172.16.33.37)

vhysqerddb.sap.eu.cloud.syensqo.com (172.16.33.51)
vhysqhrddb01

.sap.eu.cloud.syensqo.com (172.16.33.

42

10)

vhysqhrddb

vhysqersci.sap.eu.cloud.syensqo.com (172.16.33.

43WRDWeb Dispatcherhec42v302675.irl.

12)

32256SUSE SLES15

vhysqerscs.sap.eu.cloud.syensqo.

com

com (172.16.33.

40

11)

vhysqwrdwd01.sap.eu.cloud.syensqo.com (172.
16
.33.44)2
64
8
SUSE SLES15
CRD
HRS
Cloud Connector
HANA DB
hec42v302678
hec42v331250.irl.sap.eu.cloud.syensqo.com (172.16.33.
45
5)
vhysqcrdcc01

vhysqersdb.sap.eu.cloud.syensqo.com (172.16.33.

46hec42v302676.irl

13)

28SUSE SLES15DRDData Provisioning Agent

vhysqhrsdb01.sap.eu.cloud.syensqo.com

 

(172.16.33.

41

8)

vhysqdrddpa01

vhysqhrsdb.sap.eu.cloud.syensqo.com

 

(172.16.33.

47

7)

4
32
16
256SUSE SLES15
SRD
WRS
SAC Agent
Web Dispatcher
hec42v302674
hec42v331253.irl.sap.eu.cloud.syensqo.com
 
(172.16.33.
39
6)
vhysqsrdweb01

vhysqwrswd01.sap.eu.cloud.syensqo.com (172.16.33.

38

9)

4
2
16
8SUSE SLES15
ORDOpenText Connector
DevelopmentERDApp Serverhec42v303048
hec42v318041
.irl.sap.eu.cloud.syensqo.com
 
(172.16.33.48)

vhysqerdci.sap.eu.cloud.syensqo.com (172.16.33.

54

49)

vhysqordotc01

vhysqerdcs.sap.eu.cloud.syensqo.com (172.16.33.

55

50)

4
8
16
64SUSE SLES15

Non-RISE

Overview

Systems that follow an IaaS or on-premises deployment model and are not hosted in SAP RISE, are hosted in Syensqo’s Azure subscription. The following systems are classified as Non-RISE. Depending on complexity, separate documents may be used to describe the architecture for these applications. 

...

Application

...

Region

...

Dev

...

INT

...

UAT

...

TRG

...

PAR

...

PRD

...

SAP WWI Server

...

EU

...

Non-PRD

...

PRD

...

US

...

-

...

Non-PRD

...

PRD

...

China

...

-

...

Non-PRD

...

PRD

...

Syniti Replicate

...

EU

...

PRD

...

China

...

PRD

...

Syniti Connector

...

EU

...

PRD

...

US

...

PRD

...

China

...

PRD

...

NextLabs

...

EU

...

DEV

...

QAS

...

-

...

PAR

...

PRD

...

US

...

-

...

QAS

...

PAR

...

PRD

...

OpenText xECM

...

EU

...

DEV

...

QAS

...

PRD

...

US

...

-

...

QAS

...

PRD

...

China

...

-

...

QAS

...

PRD

Hosting Region

Following considerations were taken into account in deciding the Azure hosting regions

  • NextLabs provides attribute-based access control (ABAC) and evaluates access to sensitive data during runtime execution. To prevent performance issues, NextLabs will require low latency network connection to S/4HANA.
  • NextLabs have its own Azure subscription and will be hosted in the same region & physical zone as S/4HANA. vNET peering will be established between SAP RISE and NextLabs vNET to achieve low latency connectivity.
  • Other applications can be hosted in region that is in line with Syensqo's Azure deployment strategy. 
  • US OpenText xECM instance may contain sensitive data. To consolidate SyWay applications, all non-RISE US instances will be hosted together, 
  • Different subscriptions will be created for different environment: non-PRD, Pre-PRD and PRD

...

Department of Defense (DoD) in Azure Government Virginia

...

Department of Defense (DoD) in Azure Government Virginia

...

Shanghai

HRDHANA DB

hec42v302672.irl.sap.eu.cloud.syensqo.com (172.16.33.37)

vhysqerddb.sap.eu.cloud.syensqo.com (172.16.33.51)
vhysqhrddb01.sap.eu.cloud.syensqo.com (172.16.33.42)
vhysqhrddb.sap.eu.cloud.syensqo.com (172.16.33.43)

32256SUSE SLES15
WRDWeb Dispatcher

hec42v302675.irl.sap.eu.cloud.syensqo.com (172.16.33.40)

vhysqwrdwd01.sap.eu.cloud.syensqo.com (172.16.33.44)

28SUSE SLES15
CRDCloud Connector

hec42v302678.irl.sap.eu.cloud.syensqo.com (172.16.33.45)

vhysqcrdcc01.sap.eu.cloud.syensqo.com (172.16.33.46)

28SUSE SLES15
DRDData Provisioning Agent

hec42v302676.irl.sap.eu.cloud.syensqo.com (172.16.33.41)

vhysqdrddpa01.sap.eu.cloud.syensqo.com (172.16.33.47)

416SUSE SLES15
SRDSAC Agenthec42v302674.irl.sap.eu.cloud.syensqo.com (172.16.33.39)

vhysqsrdweb01.sap.eu.cloud.syensqo.com (172.16.33.38)

416SUSE SLES15
TRDTM Optimizerhec42v350658.irl.sap.eu.cloud.syensqo.com (172.16.33.52)

vhysqtrdgtw01.sap.eu.cloud.syensqo.com (172.16.33.53)

1664SUSE SLES15
ORDOpenText Connectorhec42v318041.irl.sap.eu.cloud.syensqo.com (172.16.33.54)

vhysqordotc01.sap.eu.cloud.syensqo.com (172.16.33.55)

416SUSE SLES15
Integration TestERTApp Serverhec42v350888.irl.sap.eu.cloud.syensqo.com (172.16.33.74)

vhysqertci.sap.eu.cloud.syensqo.com (172.16.33.76)
vhysqertcs.sap.eu.cloud.syensqo.com (172.16.33.75)

1664SUSE SLES15
HRTHANA DBhec42v350674.irl.sap.eu.cloud.syensqo.com (172.16.33.71)

vhysqertdb.sap.eu.cloud.syensqo.com (172.16.33.77)
vhysqhrtdb01.sap.eu.cloud.syensqo.com (172.16.33.73)
vhysqhrtdb.sap.eu.cloud.syensqo.com (172.16.33.72)

64512SUSE SLES15
WRDWeb Dispatcher

hec42v349378.irl.sap.eu.cloud.syensqo.com (172.16.33.69)

vhysqwrtwd01.sap.eu.cloud.syensqo.com (172.16.33.70)

28SUSE SLES15

China North 3 (Hebei)



DevelopmentECDApp Serverhec60v072245.chn1.sap.cn.cloud.syensqo.com

vhycdecdci.sap.cn.cloud.syensqo.com
vhycdecdcs.sap.cn.cloud.syensqo.com

832SUSE SLES15
HCDHANA DBhec60v072019.chn1.sap.cn.cloud.syensqo.com

vhycdecddb.sap.cn.cloud.syensqo.com 
vhycdhcddb01.sap.cn.cloud.syensqo.com

32256SUSE SLES15
WCDWeb Dispatcherhec60v072016.chn1.sap.cn.cloud.syensqo.com

vhycdwcdwd01.sap.cn.cloud.syensqo.com

28SUSE SLES15
CCDSAP Cloud connectorhec60v072124.chn1.sap.cn.cloud.syensqo.com

vhycdccdcc01.sap.cn.cloud.syensqo.com

28SUSE SLES15
DCDData Provisioning Agenthec60v072234.chn1.sap.cn.cloud.syensqo.com 

vhycddcddpa01.sap.cn.cloud.syensqo.com

416SUSE SLES15
SCDSAC Agenthec60v072237.chn1.sap.cn.cloud.syensqo.com

vhycdscdweb01.sap.cn.cloud.syensqo.com

416SUSE SLES15
TCDTM Optimizerhec60v072226.chn1.sap.cn.cloud.syensqo.com

vhycdtcdgtw01.sap.cn.cloud.syensqo.com

1664SUSE SLES15
Integration TestECTApp Serverhec60v072421.chn1.sap.cn.cloud.syensqo.com

vhycdectci.sap.cn.cloud.syensqo.com
vhycdectcs.sap.cn.cloud.syensqo.com

1664SUSE SLES15
HCTHANA DBhec60v072123.chn1.sap.cn.cloud.syensqo.com

vhycdectdb.sap.cn.cloud.syensqo.com
vhycdhctdb01.sap.cn.cloud.syensqo.com

64512SUSE SLES15

Non-RISE

Overview

Systems that follow an IaaS or on-premises deployment model and are not hosted in SAP RISE, are hosted in Syensqo’s Azure subscription. The following systems are classified as Non-RISE. Depending on complexity, separate documents may be used to describe the architecture for these applications. 

Application

Region

Dev

INT

UAT

TRG

PAR

PRD

SAP WWI Server

EU

Non-PRD

PRD

China

-

Non-PRD

PRD

Syniti Replicate

EU

PRD

China

PRD

Syniti Connector

EU

PRD

China

PRD

NextLabs

EU

DEV

QAS

-

PAR

PRD

OpenText xECM

EU

DEV

QAS

PRD

China

-

QAS

PRD

Hosting Region

Following considerations were taken into account in deciding the Azure hosting regions

  • NextLabs provides attribute-based access control (ABAC) and evaluates access to sensitive data during runtime execution. To prevent performance issues, NextLabs will require low latency network connection to S/4HANA.
  • NextLabs have its own Azure subscription and will be hosted in the same region & physical zone as S/4HANA. vNET peering will be established between SAP RISE and NextLabs vNET to achieve low latency connectivity.
  • Other applications can be hosted in region that is in line with Syensqo's Azure deployment strategy. 
  • Different subscriptions will be created for different environment: non-PRD, Pre-PRD and PRD
RegionCategorySubscriptionsAzure Region
EUNextLabs3 (non-PRD, Pre-PRD, PRD)North Europe (Dublin)
Non-RISE (excluding NextLabs)2 (non-PRD, PRD)France Central (Paris)
ChinaNon-RISE2 (non-PRD, PRD)

TBC

Azure Low Level Design

Azure landscape for SyWay is managed my Syensqo IT as part of their overall Azure management. See Azure management roles and responsibility for more details. 

RegionCategoryLLD 
EUNextLabsLink
Non-RISE (excluding NextLabs)
ChinaNon-RISE

Following tables lists down SyWay Azure details.

CategoryEnvironmentAzure Subscription NamevNETStorage AccountKey vault
NextLabsDEV & QASOTH - Next Lab - 00azrneuvntdnlasha0000azrneustodnlasha0000azrneukvtdnlasha0000




  

VM Details

CategoryEnvironmentApplicationVM NameIPVM TypeOS DiskData DiskOS
NextLabsDEVNextLabs Control Centerazrneuvmldnlaapp0000172.16.48.5Standard D4s v5128GB128GBRHEL 9.4
NextLabs Policy Controllerazrneuvmldnlaapp0100172.16.48.6Standard D4s v5128GB64GBRHEL 9.4

SQL Server

CategoryEnvironmentApplicationSQL ServerSQL DBIPSchema
NextLabsDEVNextLabs azrneuvmldnlaapp0000azrneusdbdnlasha0000172.16.48.20dbo

Shared File Systems

EnvironmentStorage accountPurpose TypeShare name
DEVazrneustodnlasha0000
NextLabs installation filesAzure filesdae-install-dev
NextLabs working directoryAzure filesdae-working-dev
ERS interface shared folderAzure filesinterface-ers
ERD interface shared folderAzure filesinterface-erd

Azure Low Level Design

Azure landscape for SyWay is managed my Syensqo IT as part of their overall Azure management. See Azure management roles and responsibility for more details. 

...

Following tables lists down SyWay Azure details.

TBC

VM Details

TBC

Shared File Systems

...

Network Architecture 

Europe 

...

draw.io Diagram
bordertrue
diagramNameUntitled Diagram-1761724000735
simpleViewerfalse
width1250
linksauto
tbstyletop
diagramDisplayName
lboxtrue
diagramWidth1557
height865
revision12

North America 

TBC

China

TBC

SAP RISE ExpressRoute Design

...

TBC
RegionMegaport LocationAzure Edge locationSAP RISE RegionNon-RISE Region
EuropeParis Equinix PA2/3 & Paris Interxion PAR5DublinAzure North Europe (Dublin)Azure France Central (Paris)
ChinaNorth AmericaAshburn Equinix DC4 & Reston Core Site VA1TBCTBCTBCChinaTBC

Azure China North 3 (Hebei)

TBCTBC

Europe

The following diagram describes the ExpressRoute design between Megaport and SAP RISE in EU region.  

North America

TBC

China

TBC

IP Allocation

The 172.16.32.0/19 IP range has been allocated for SyWay. The following table lists down the IP allocation for the different regions and subnets.

1494047Unassigned
52555663
RegionLandscapeRegion IP Allocation RISE SubnetCIDRNetwork NameSubnet IP AllocationRangeUsable Hosts
EuropeSAP RISE172.16.32.0/22Production

172.16.34.0/25

172.16.34.0 - 172.16.34.127

126

Production (HA components)

172.16.34.128/25

172.16.34.128 - 172.16.34.255

126

ECS Services

172.16.32.0/24

172.16.32.1 - 172.16.32.254 254
Sandbox

172.16.33.0/27

172.16.33.1 - 172.16.33.30

30

Development

172.16.33.32/27

172.16.33.33 - 172.16.33.62

30

Integration Test

172.16.33.64/27

172.16.33.65 - 172.16.33.94

30

QA / UAT

172.16.33.96/27

172.16.33.97 - 172.16.33.126

30

Pre-Production (PAR)

172.16.33.128/27

172.16.33.129 - 172.16.33.158

30

Training

172.16.33.160/27

172.16.33.161 - 172.16.33.190

30

Non-Prod Reserve 

172.16.33.192/27

172.16.33.193 - 172.16.33.222

30

Tools / Other Needs

172.16.33.224/27

172.16.33.225 - 172.16.33.254

30

Unassigned

172.16.35.0/24

172.16.35.1 - 172.16.35.254

254

NextLabs

172.16.48.0/23

Production172.16.49.0/25172.16.49.0 - 172.16.49.127 126
HUB172.16.49.128/25172.16.49.128 - 172.16.49.255 126
Pre-Production (PAR)172.16.48.128/25172.16.48.128 - 172.16.48.255 126
OTH (DEV & QAS)172.16.48.0/25172.16.48.0 - 172.16.48.127126

Non-RISE

TBC

TBCTBCTBCTBC
China

SAP RISE

172.16.36.0/22

TBCTBC172.16.36.0 - 172.16.39.2551022

Non-RISE

TBC

TBCTBCTBCTBC
Unassigned
UnassignedNorth AmericaSAP NS2 RISE172.16.4052.0/21222TBC-TBC

-

172.16.52.0 - 172.16.55.2552046 1022
NextLabsUnassigned172.16.5056.0/2321TBC-TBC

-

172.16.5056.0 - 172.16.5163.255 510

Non-RISE

TBC

TBCTBCTBCTBC
 2046
Unassigned

172.16.

52

40.0/

222

21

-

-

172.16.40.0 - 172.16.47.255 10222046
Unassigned

172.16.

56

50.0/

21

23

-

-

172.16.50.0 - 172.16.51.255 2046 510

DNS Architecture

Domain Name

...

...

North America
RegionSyensqo DNSSAP RISE DNS
Europe

172.23.128.104
10.53.73.3
10.129.131.52
10.129.131.53
172.18.180.142
172.18.181.116
172.19.1.42
172.19.1.57
10.237.6.11
10.233.6.5
172.23.193.70
172.23.193.86
172.18.164.7
172.18.164.22
172.19.113.69
172.19.113.86

DNS –CSN-A-HA IP - 172.16.32.14 (vhysqirlcsna-ha.irl.sap.eu.cloud.syensqo.com)

DNS –CSN-B-HA IP - 172.16.32.30 (vhysqirlcsnb-ha.irl.sap.eu.cloud.syensqo.com)

DNS –CSN-C-HA IP - 172.16.32.46 (vhysqirlcsnc-ha.irl.sap.eu.cloud.syensqo.com)

TBCChinaTBC

Network Firewall

For SyWay project, the following firewalls will be leveraged to manage the corresponding traffic.

...

US
RegionHostnamePort
EUproxy3128
China

Inbound Internet traffic

...