Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3523

DHCP Option Set

$
0
0

i haven't seen this requirement in my previous CAL requests and i'm not entirely sure how to make it work. has anyone gone through this setup on AWS and eventually connected to SAP cloud servers?

 

the relevant pages are in section 4 of the cannot-be-attached guide.

 

thank you,

 

greg

 

P.S. The section from the guide as SCN does not allow uploading the whole PDF document:

 

4 Connecting to Your Solution

4.1 Connecting to SAP ERP / SAP HANA

4.1.1 Release and Support Package level

[Main Component]: SAP HANA Platform Edition 1.0

[Stack-no. of Main Component]: SPS09

[Localized Country]: USA

[Language]: EN

[Main Component]: SAP enhancement package 7 for SAP ERP 6.0

[Stack-no. of Main Component]: SPS08

[Localized Country]: US, Germany, China

[Language]: all standard languages

4.1.2 Mapping hostnames to IP address

Your Amazon VPC setup needs to have a DHCP Option Set, which defines a domain-name

<Domain Name>. If this is not the case, create the DHCP Option set, terminate your CAL instance and

create a new one. This is necessary as <Domain Name> is used in the CAL instance creation process.

When creating a CAL instance, the solution is deployed to a server with the predefined virtual host names

vhcalhdbdb, vhcalerpci, and vhcalerpcs and to a second server with the virtual host name bihost. You are also

provided with <IP Addresses> that allow you to access the servers. You can find the <IP Address> of the

respective servers by selecting the name of your instance in the SAP Cloud Appliance Library.ABAP application

server ERP and BI platform server BIHOST reach the HANA server HDB with the help of an entry for vhcalhdbdb

in its local /etc/hosts file.

You still need to publish a mapping between the server names and the IP address in your network. You could do

this within your Domain Name Service (DNS) setup or adjust the hosts file on the client.

The following steps describe how to adjust the hosts file on the client:

3. Open the hosts file of your operating system as administrator:

18

Getting Started with SAP S/4HANA, on-premise Edition - Fully Activated Landscape on SAP

Cloud Appliance Library

o For Windows operating system: Open the Start menu, type

notepad c:\windows\system32\drivers\etc\hosts

and hit Ctrl Shift Enter.

o For Linux operating system: /etc/hosts

4. Enter the following lines in the hosts file and save it:

# ERP and HDB

<IP Address ERP/HDB server> vhcalerpci vhcalerpci.<Domain Name>

<IP Address ERP/HDB server> vhcalerpcs vhcalerpcs.<Domain Name>

<IP Address ERP/HDB server> vhcalhdbdb vhcalhdbdb.<Domain Name>

# BI Platform

<IP Address BI Host server> bihost bihost.<Domain Name>

The predefined local domain name is dummy.nodomain. If you do not want to change the default settings, you

can map the hosts name to IP addresses as the following:

# ERP and HDB

<IP Address ERP/HDB server> vhcalerpcs vhcalerpcs.dummy.nodomain vhcalerpci

vhcalerpci.dummy.nodomain vhcalhdbdb vhcalhdbdb.dummy.nodomain

# BI Platform

<IP Address BI Host server> bihost bihost.dummy.nodomain

Working with the dummy.nodomain might require changes in your web browser in case there is a web proxy in

place. You need to set the Proxy Server as follows:

Address <your proxy server> for

example proxy

Port <your proxy port> for example

8080

Furthermore, you need to add the following to the Exceptions field: *.dummy.nodomain

In Microsoft Internet Explorer e.g., open Tools → Internet Options. Go to the Connections tab and

choose LAN settings .

In the Proxy server section, carry out the following steps:

- Check Use a proxy server for your …

- Maintain Address and Port

- Choose the Advanced button.

In section Exceptions, carry out the following steps:

- Add ;*.dummy.nodomain at the end of the entry field.

- Choose theOK button.


Viewing all articles
Browse latest Browse all 3523

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>