purpose of this guidewpc.c320.edgecastcdn.net/00c320/sap netweaver quick... · web viewsubmit order...

SAP NetWeaver on IBM BluemixInfrastructure

Quick Reference Guide

February 2017

V1.0

SAP NetWeaver on IBM Bluemix infrastructurequick reference guide

ContentsPurpose of this guide...............................................................................................................3

Installing a 32GB server single-node.......................................................................................4

Order your 32GB server.....................................................................................................................4

Preparing your server for the SAP installation (32GB).......................................................................9

Partitioning and file systems..............................................................................................................9

Installing a 256GB and a 32GB server in a three-tier setup..................................................12

Order your servers for a three-tier installation................................................................................12

Preparing your server for the SAP installation (256GB)...................................................................17

Partitioning and file systems............................................................................................................17

Network and NFS considerations for three-tier setup.....................................................................20

Provisioning external storage to your server...................................................................................22

Installing your SAP landscape...............................................................................................29

RPM package prerequisites.............................................................................................................29

Download your SAP software..........................................................................................................29

Preparation for SAP’s Software Provisioning Manager (SWPM) graphical user interface (GUI)......29

Installing SAP software....................................................................................................................31

Appendix A.............................................................................................................................33

2 © Copyright IBM Corp. 2017. All rights reserved.Materials may not be reproduced in whole or in part

without prior written permission of IBM.

SAP NetWeaver on IBM Bluemix infrastructure quick reference guide

Purpose of this guideThe purpose of this guide is to provide an introduction for customers who are new to the SoftLayer environment and would prefer a “quick start” format versus more detailed documentation. Two sample configurations help you through the ordering process to the start of the SAP installation.

The first configuration sample is the smallest one possible—a single node 32GB RAM server. The second is an advanced configuration of two nodes, a 32GB RAM server and a 256GB RAM server with an external storage configuration. The disk layout might vary if you do not choose the same options in the examples. The sample layouts may not be your preferred layout; the purpose is to show you two possibilities if you are not experienced with the Linux operating system.

Note that you can find an example of how to attach external storage to your provisioned server under Provisioning external storage to your server.

The SoftLayer® infrastructure is now the core of IBM® Bluemix®. Over the coming months all references to SoftLayer will be replaced with Bluemix branding and naming. You will find SoftLayer referenced in this guide as well as on IBM web pages, e.g., the SoftLayer customer control portal and KnowledgeLayer. See https://www.ibm.com/blogs/bluemix/2016/10/bluemix-softlayer-unified-cloud-platform for more information.

Note – important information: Currently, all SAP certified servers are shipped with a pre-configured amount of RAM and hard disks that cannot be changed during the ordering process nor via a support ticket after provisioning.

© Copyright IBM Corp. 2017. All rights reserved. 3Materials may not be reproduced in whole or in part

without the prior written permission of IBM.

https://www.ibm.com/blogs/bluemix/2016/10/bluemix-softlayer-unified-cloud-platform


Installing a 32GB server single-nodeOrder your 32GB server

1. Open a browser window, enter https://control.softlayer.com and click the Log in with IBMid link.

Figure 1. SoftLayer log in dialog box

2. Enter your IBMid or email and click the Continue button.3. Enter your Password and click the Sign in button.4. Click the Devices icon on the Account Summary page.

Figure 1. Device icon

5. Click the Monthly link under Bare Metal Servers on the Devices page.

Figure 1. Bare metal servers monthly link

The Server List dialog box will appear.

6. Click the hyperlink under STARTING PRICE PER MONTH to select server BI.S1.NW32.



https://control.softlayer.com/


Figure 1. Hyperlink to Configure/Order page

Figure 1. Configure/Order page

Data Center, Server, RAM and Hard Drives will default to predefined values, which cannot be changed.

7. Select Red Hat Enterprise Linux for SAP Business Application 6.X as your Operating System.

8. Select 500 GB for Public Bandwidth.9. Select 1 Gbps Redundant Public & Private Network Uplinks for Uplink Port

Speed.

For this sample installation, leave the default values for all other fields. You can consult the SAP NetWeaver Implementation and Operations Guide for detailed descriptions of the options.

10. Click the Add to Order button at the end of the scroll.You will be redirected to the Checkout page once your order has been verified.




Figure 2. Checkout page

11. Scroll down and enter the values in Table 1 under Advanced System Configuration.

Field Value

Backend VLAN Select from the drop-down list, e.g., tor01.bcr01a.1241

Subnet Select from the drop-down list, e.g., 10.114.63.64/26

Frontend VLAN Select from the drop-down list, e.g., tor01.fcr01a.1199


Provision Scripts Defaults to None

SSH Keys Add

Hostname E.g., e2e1270

Domain E.g., saptest.com

Table 1. 32GB advanced configuration values




Figure 1. Advanced System Configuration on the Checkout page

12. Confirm your selections on the Checkout page and click the Cloud Service terms checkbox on the right-hand side of the page.

Figure 1. Cloud Service terms checkbox

13. Click the Submit Order button on the right-hand side of the form. You will be redirected to a page with your order number. You can print the page because it is also your order receipt. In addition, you will receive a confirmation email with the subject Your IBM Bluemix Order ## has been approved with ## being your order number.




Once the order is submitted, the server will, depending on your order, be available for use within one to four hours. You can check the Device Details screen on the main SoftLayer portal page (Devices > Device List) for a status of the provisioning steps. Click your device’s hostname to see its status (Figure 1).

Figure 1. Device provisioning status

See Preparing your server for the SAP installation (32GB) once your server has been provisioned.




Preparing your server for the SAP installation (32GB)A public IP is being used for remote access, which means you can connect to your server through an ssh client (e.g., putty on Microsoft Windows). Use the public IP address displayed in the Device List for your device. The root password for your server is also displayed; be sure to click the Show Password checkbox to see it.

Figure 1 Device List - find password

Partitioning and file systemsFor the single-node example, a server with two logical disks (both in RAID1) was ordered. There are two mirrored disks appearing in the operating system (OS)—one for the OS and the other unallocated, but partitioned and a file system mounted. The second disk will be adapted to the planned layout. The following is just one possible approach for a layout. For production use, you may want to follow the sizing information for your system as other layouts may better cater to your needs or SAP requirements.

1. Look at the disks layout.

[root@e2e1270 ~]# /sbin/fdisk -l

Disk /dev/sda: 959.7 GB, 959656755200 bytes255 heads, 63 sectors/track, 116671 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x00037dae

Device Boot Start End Blocks Id System/dev/sda1 * 1 33 262144 83 LinuxPartition 1 does not end on cylinder boundary./dev/sda2 33 164 1048576 82 Linux swap / SolarisPartition 2 does not end on cylinder boundary./dev/sda3 164 116672 935853056 83 Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdb: 959.7 GB, 959656755200 bytes255 heads, 63 sectors/track, 116671 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x00000000

Device Boot Start End Blocks Id System/dev/sdb1 1 116672 937164799+ ee GPT




Partition 1 does not start on physical sector boundary.In the disk layout listed in step 1, sdb is the unallocated disk that needs be re-partitioned since there is one large partition by default. Swap will be added to the configuration and allocated to the remainder of the disk for data (i.e., for the database installation and data). You will have to unmount the file system /disk1 before you execute the partition parted:

2. [root@e2e1270 ~]# umount /disk1

3. [root@e2e1270 ~]# parted /dev/sdb

4. Delete the existing partition.

(parted) rm 1

5. Create more swap.

(parted) mkpart primary linux-swap 1 32GiB

6. Add a data partition for DB2.

(parted) mkpart primary ext2 32GiB 100%

7. Leave parted.

(parted) quit

8. Format the swap partition.

[root@e2e1270 ~]# mkswap /dev/sdb1

Setting up swapspace version 1, size = 33553404 KiBno label, UUID=9033b77d-95ea-4802-b6e5-7c43849f5ada

9. Enter the swap device line into /etc/fstab after the existing swap line using your favorite editor and take the universally unique identifier (UUID) that the previous command is showing at the console.

UUID=9033b77d-95ea-4802-b6e5-7c43849f5ada swap swap defaults 0 0

and on the command-line to activate all swap devices.

[root@e2e1270 ~]# swapon -a

10. Create the file system for the database, the /etc/fstab entry and mount it.

[root@e2e1270 ~]# mkfs.ext3 /dev/sdb2mke2fs 1.41.12 (17-May-2010)Filesystem label=OS type: LinuxBlock size=4096 (log=2)Fragment size=4096 (log=2)...

Note that when you see the following line, it will take about 20 seconds to format the file system.

writing superblocks and filesystem accounting information:

Get hold of the file system’s UUID:




[root@e2e1270 ~]# ls -als /dev/disk/by-uuid/* | grep sdb20 lrwxrwxrwx. 1 root root 10 Nov 24 07:50 /dev/disk/by-uuid/cede78e0-6cee-400e-b9b4-292cf1f8c734 -> ../../sdb2

11. Enter this new file system in /etc/fstab and insert the following line using your favorite editor and take the UUID that the previous command is showing on the console.

UUID=cede78e0-6cee-400e-b9b4-292cf1f8c734 /db2 ext3 defaults 1 2

12. Delete the line that defines the obsolete /disk1. Save and quit the editor.

13. Mount the new file system after creating the directory /db2.

[root@e2e1270 ~]# mkdir /db2[root@e2e1270 ~]# mount /db2

14. Check the file system; it should look similar to the following:

[root@e2e1270 ~]# df -h(should display something similar)

Filesystem Size Used Avail Use% Mounted on/dev/sda3 879G 1,5G 833G 1% /tmpfs 16G 0 16G 0% /dev/shm/dev/sda1 248M 64M 173M 27% /boot/dev/sdb2 849G 201M 805G 1% /db2

In regards to storage, the server is now prepared for further installation steps. Refer to RPM package prerequisites to continue with your SAP installation. The information within it will help make graphical access to your server easier.




Installing a 256GB and a 32GB server in a three-tier setup

Following is a more complex scenario using a 32GB server as the SAP NetWeaver application server and a 256GB server as the database server. External storage will also be provisioned as backup space for the database for both archived log files and online full backups.

Order your servers for a three-tier installation1. Follow the steps in Order your 32GB server to order the SAP NetWeaver application

server. The following steps will guide you through ordering the database server.2. Open a browser window, enter https://control.softlayer.com and click the Log in with

IBMid link.

Figure 1. SoftLayer log in dialog box

3. Enter your IBMid or email and click the Continue button.4. Enter your Password and click the Sign in button.5. Click the Devices icon on the Account Summary page.

Figure 1. Device icon

6. Click the Monthly link under Bare Metal Servers on the Devices page.





Figure 1. Bare metal servers monthly link

The Server List dialog box will appear.

7. Click the hyperlink under STARTING PRICE PER MONTH to select server BI.S1.NW256.

Figure 3. Hyperlink to Configure/Order page

Figure 1. Configure/Order page

Data Center, Server, RAM and Hard Drives will default to predefined values, which cannot be changed.




10. Select Red Hat Enterprise Linux for SAP Business Application 6.X as your Operating System.

11. Select 500 GB for Public Bandwidth.12. Select 1 Gbps Redundant Public & Private Network Uplinks for Uplink Port

Speed.

For this sample installation, leave the default values for all other fields. You can consult the SAP NetWeaver Implementation and Operations Guide for detailed descriptions of the options.

13. Click the Add to Order button at the end of the scroll.You will be redirected to the Checkout page once your order has been verified.

Figure 1. Checkout page




15. Scroll down and enter the values in Table 1 under Advanced System Configuration:

Field Value

Backend VLAN Select from the drop-down list, e.g., tor01.bcr01a.1241


Frontend VLAN Select from the drop-down list, e.g., tor01.fcr01a.1199


Provision Scripts Defaults to None

SSH Keys Defaults to None

Hostname Server1 E.g., e2e2690

Domain Server1 E.g., saptest.com

Table 1. Advanced System Configuration values

Figure 1. Advanced System Configuration on the Checkout page




16. Confirm your selections on the Checkout page and click the Cloud Service terms checkbox on the right-hand side of the page.

Figure 1. Cloud Service terms checkbox

17. Click the Submit Order button. You will be redirected to a screen with your order number. You can print the screen because it’s also your order receipt.

Once the order is submitted, the server will, depending on your order, be available for use within one to four hours. You can check the Device Details screen on the main SoftLayer portal page (Devices > Device List) for a status of the provisioning steps. See Preparing your server for the SAP installation (256GB) once your server(s) has been provisioned.




Preparing your server for the SAP installation (256GB)A public IP is being used for remote access, which means you can connect to your servers through an ssh client (e.g., putty on Windows). Use the public IP addresses that are displayed in the Device List for your device. The root passwords for your servers are also displayed; be sure to click the Show Password checkbox to see them.

Figure 1. Device List - find password

Partitioning and file systemsFor the three-tier example, a 256GB server (database server) with four logical disks (on RAID10) was ordered, as well as a 32GB server (application server) with two logical disks (on RAID 1). The 256GB server has four mirrored disks appearing in the OS—one for the OS with available free space and three unallocated disks. We will not use the default file system on the three disks, but put them under the volume manager. Doing this allows for more space to be available for the database in one large file system and to have separate file systems for /sapmnt and /usr/sap.

For the 32GB server, follow the steps 1 to 10 in Preparing your server for the SAP installation (32GB); then continue with steps 11 to 14, but replacing /db2 with /usr/sap

/sapmnt and /usr/sap/trans will be created and the network file system (NFS) exported from the database server, which will also keep the Advanced Business Application Programming (ABAP) SAP Central Service (ASCS) instance.

The following is just one possible approach for a layout. For production use, you may want to follow the sizing information for your system as other layouts may better cater to your needs or SAP requirements. You will need to unmount the three default file systems on /disk[1-3] otherwise they cannot be used by the volume manager; fdisk will show the disk layout.

1. [root@e2e2690 ~]# umount /disk1[root@e2e2690 ~]# umount /disk2[root@e2e2690 ~]# umount /disk3

2. Look at the disks layout.

[root@e2e2690 ~]# /sbin/fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdb: 599.6 GB, 599584145408 bytes255 heads, 63 sectors/track, 72895 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x00000000




Device Boot Start End Blocks Id System/dev/sdb1 1 72896 585531391+ ee GPTPartition 1 does not start on physical sector boundary.

Disk /dev/sda: 599.6 GB, 599584145408 bytes255 heads, 63 sectors/track, 72895 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x0007d012

Device Boot Start End Blocks Id System/dev/sda1 * 1 33 262144 83 LinuxPartition 1 does not end on cylinder boundary./dev/sda2 33 164 1048576 82 Linux swap / SolarisPartition 2 does not end on cylinder boundary./dev/sda3 164 72896 584219648 83 Linux

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdc: 599.6 GB, 599584145408 bytes255 heads, 63 sectors/track, 72895 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x00000000

Device Boot Start End Blocks Id System/dev/sdc1 1 72896 585531391+ ee GPTPartition 1 does not start on physical sector boundary.

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdd: 599.6 GB, 599584145408 bytes255 heads, 63 sectors/track, 72895 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 262144 bytes / 262144 bytesDisk identifier: 0x00000000

Device Boot Start End Blocks Id System/dev/sdd1 1 72896 585531391+ ee GPTPartition 1 does not start on physical sector boundary.

Because the disks are RAID10, they can be striped for simplicity without imposing further risk. The goal is to create a large database file system, plus two smaller ones for the SAP installation.




3. Create a volume group.

[root@e2e2690 ~]# vgcreate datavg /dev/sdb1 /dev/sdc1 /dev/sdd1

4. Create logical volumes and file systems.

[root@e2e2690 ~]# lvcreate -i 3 -I 256 -l 70%VG -n datalv datavg Rounding size 1.15 TiB (300197 extents) up to stripe boundary size 1.15 TiB (300198 extents).

Logical volume "datalv" created.[root@e2e2690 ~]# lvcreate -i 3 -I 256 -l 10%VG -n swaplv datavg Logical volume "swaplv" created.[root@e2e2690 ~]# lvcreate -i 3 -I 256 -l 10%VG -n saplv datavg Logical volume "saplv" created.[root@e2e2690 ~]# lvcreate -i 3 -I 256 -l 10%VG -n sapmntlv datavg Logical volume "sapmntlv" created.

[root@e2e2690 ~]# mkfs.ext4 /dev/datavg/saplv...

[root@e2e2690 ~]# mkfs.ext4 /dev/datavg/sapmntlv...

[root@e2e2690 ~]# mkfs.ext4 /dev/datavg/datalv...

[root@e2e2690 ~]# mkswap /dev/datavg/swaplv mkswap: /dev/datavg/swaplv: warning: don't erase bootbits sectors

on whole disk. Use -f to force.Setting up swapspace version 1, size = 175656956 KiBno label, UUID=0ca4b895-f9cf-43f1-9179-969bb7e3c7ef

[root@e2e2690 ~]# mkdir /sapmnt /usr/sap /db2

5. Edit the file /etc/fstab, remove the entries for /disk1, /disk2 and /disk3, and add the entries below.

/dev/datavg/datalv /db2 ext4 defaults 1 2/dev/datavg/saplv /usr/sap ext4 defaults 1 2/dev/datavg/sapmntlv /sapmnt ext4 defaults 1 2/dev/datavg/swaplv swap swap prio=0,defaults 0 0

6. Mount the file systems and activate the swap volume.

[root@e2e2690 ~]# mount -a

[root@e2e2690 ~]# swapon -a

The server is now prepared for further installation steps in regards to storage. See Network and NFS considerations for three-tier setup for a description of the network layout and specific steps for the SAP installation.




Network and NFS considerations for three-tier setupIf you are planning to install a three-tier setup, you need to prepare the network setup accordingly. For the sample setup, a 256GB database server (named e2e2690) and a 32GB application server (named e2e1270) were deployed. The database server will also host the ASCS instance. Adding the IPs on the private network to your /etc/hosts will help with upcoming steps and make sure that SAP internal network traffic will go through the right network.

Figure 1. Sample of three-tier set up

1. Log in to the machines and find their private network configuration.

[root@e2e2690 ~]# ifconfig bond0bond0 Link encap:Ethernet HWaddr 0C:C4:7A:66:2D:A8

inet addr:10.17.139.35 Bcast:10.17.139.63 Mask:255.255.255.192inet6 addr: fe80::ec4:7aff:fe66:2da8/64 Scope:LinkUP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1RX packets:128080 errors:0 dropped:0 overruns:0 frame:0TX packets:25491 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0 RX bytes:19137850 (18.2 MiB) TX bytes:3426015 (3.2 MiB)

[root@e2e2690 ~]# ifconfig bond1bond1 Link encap:Ethernet HWaddr 0C:C4:7A:66:2D:A9

inet addr:208.43.211.118 Bcast:208.43.211.127 Mask:255.255.255.224 inet6 addr: fe80::ec4:7aff:fe66:2da9/64 Scope:Link

UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1RX packets:289610 errors:0 dropped:0 overruns:0 frame:0TX packets:109371 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0 RX bytes:31216160 (29.7 MiB) TX bytes:18591947 (17.7 MiB)




In this example, 10.17.139.35 is the private IP of the database server; it is from one of the IP ranges from RFC 1597. You can determine the IP of the application server, too, and add both IPs to both servers’ /etc/hosts.

[root@e2e2690 ~]# cat /etc/hosts127.0.0.1 localhost.localdomain localhost208.43.211.118 e2e2690.saptest.com e2e2690

10.17.139.35 e2e2690-priv10.17.139.46 e2e1270-priv

On e2e1270 add the two last lines, too.

2. Install NFS software nfs-utils on both servers.

[root@e2e2690a ~]# yum install nfs-utils

Make sure you start and register the rpcbind and NFS service on the database server.

[root@e2e2690 ~]# service rpcbind start [root@e2e2690 ~]# chkconfig nfs on[root@e2e2690 ~]# service nfs start

3. Use NFS to export /sapmnt and /usr/sap/trans from the database server to the application server by adding the required entry to /etc/exports of the database server.

/sapmnt/C10 10.17.139.46(rw,no_root_squash,sync,no_subtree_check)/usr/sap/trans 10.17.139.46(rw,no_root_squash,sync,no_subtree_check)

The sample value C10 needs to be replaced with the SAP System ID for your SAP system. You must create the directory before you export it. Run the following from the command line of the database server:

[root@e2e2690 ~]# mkdir /sapmnt/C10[root@e2e2690 ~]# mkdir -p /usr/sap/trans[root@e2e2690 ~]# exportfs -a

4. Mount the NFS share on the application server by adding the below entry to its /etc/fstab and mount it from the command-line.

e2e2690-priv:/sapmnt/C10 /sapmnt/C10 nfs defaults 0 0e2e2690-priv:/usr/sap/trans /usr/sap/trans nfs defaults 0 0

5. Create the target directories on the application server and mount them:

[root@e2e1270 ~]# mkdir -p /sapmnt/C10[root@e2e1270 ~]# mkdir /usr/sap/trans[root@e2e1270 ~]# mount /sapmnt/C10[root@e2e1270 ~]# mount /usr/sap/trans

Your servers are now prepared to host the components of a distributed SAP installation. See Provisioning external storage to your server for information on how to provision external




storage for backup purposes to the database server. Further installation preparation will be performed in Installing your SAP landscape.




Provisioning external storage to your serverExternal storage can be added to your provisioned server(s) if you want to use it as a backup device or use a snapshot to quickly restore your database in a test environment. In the example, block storage will be used for both archiving log files of the database and online and offline backups for the database. The fastest block storage (4 IOPS per GB) was selected to help assure a minimum backup time. Slower block storage may be sufficient for your needs.

External storage is ordered through the SoftLayer Control panel.

1. Open a browser window and log in to https://control.softlayer.com.

2. Click the Log in with IBMid button.

3. Enter your IBMid or email and click the Continue button.

4. Enter your Password and click the Sign in button.

5. Select Storage > Block Storage.

Figure 1. Storage drop-down menu

6. Click the Order Block Storage link on the Block Storage page.

Figure 1. Order Block Storage link

7. Select the specifics for your storage needs. Table 1 contains recommended values, including 4 IOPS/GB for a typical database workload.

Field Value

Select Storage Type Endurance

Location Data center where your device is located.

Select Storage Package 4 IOPS/GB

Select Storage Size Make your selection based on your workload





needs.

Specify Snapshot Space Size 0 GB

Select OS Type LinuxTable 1. Recommended values for block storage

Figure 1. Ordering block storage (Endurance) page

8. Click the Continue button.

9. Click the I have read the Master Service Agreement checkbox and click the Place Order button.




Figure 1. Placing order for block storage

10. Click the Actions drop-down menu to the right of your LUN and select Authorize Host to access the provisioned storage.

Figure 1. Block Storage page

11. Select Devices; the Device Type will default to Bare Metal Service. Click the Hardware drop-down menu and select the hostnames of your devices.




Figure 1. Authorizing your hosts for storage

12. Click the Submit button.

13. Check the status of your provisioned storage under Devices > (select your device) > Storage tab.

14. Note the Target Address and iSCSI Qualified Name (IQN) for your server (iSCSI initiator) as well as the username and password for authorization with the iSCSI server. You will need that information in the following steps.

Now you would follow the steps in Accessing Block Storage on Linux under https://knowledgelayer.softlayer.com/procedure/block-storage-linux to make your storage accessible from your provisioned server. For your convenience, all the required steps are available in this guide.



https://knowledgelayer.softlayer.com/procedure/block-storage-linux


In the sample deployment, the data retrieved from the SoftLayer Storage tab was

Target IP: 10.2.62.78

IQN: iqn.2005-05.com.softlayer:SL01SU276540-H896345

User: SL01SU276540-H896345

Password: EtJ79F4RA33dXm2q

1. Enter the following based on the retrieved information:

[root@e2e2690 ~]# cat /etc/iscsi/initiatorname.iscsi InitiatorName=iqn.2005-05.com.softlayer:SL01SU276540-H896345

An existing entry might have to be replaced in /etc/iscsi/initiatorname.iscsi.

2. Add the following lines to the bottom of /etc/iscsi/iscsid.conf:

[root@e2e2690 ~]# tail /etc/iscsi/iscsid.conf # it continue to respond to R2Ts. To enable this uncomment this line# node.session.iscsi.FastAbort = No

node.session.auth.authmethod = CHAPnode.session.auth.username = SL01SU276540-H896345node.session.auth.password = EtJ79F4RA33dXm2qdiscovery.sendtargets.auth.authmethod = CHAPdiscovery.sendtargets.auth.username = SL01SU276540-H896345discovery.sendtargets.auth.password = EtJ79F4RA33dXm2q

3. Replace the username and password values (in italics) with those that you noted during the last step of the previous section

4. Discover the iSCSI target by entering the following:

[root@e2e2690 ~]# iscsiadm -m discovery -t sendtargets -p "10.2.62.78"10.2.62.78:3260,1031 iqn.1992-08.com.netapp:tor010110.2.62.87:3260,1032 iqn.1992-08.com.netapp:tor0101

5. Set the host to automatically log into the iSCSI array

[root@e2e2690 ~]# iscsiadm -m node -L automatic

6. Install and start the multipath daemon.

[root@e2e2690 ~]# yum install device-mapper-multipath

…

[root@e2e2690 ~]# chkconfig multipathd on

[root@e2e2690 ~]# service multipathd start




After completing all the commands in Accessing Block Storage on Linux, another LUN will appear in the multipath output.

[root@e2e2690 ~]# multipath -ll

…

3600a098038303452543f464142755a42 dm-9 NETAPP,LUN C-Modesize=500G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw|-+- policy='round-robin 0' prio=50 status=active| `- 10:0:0:169 sde 8:64 active ready running`-+- policy='round-robin 0' prio=10 status=enabled `- 9:0:0:169 sdf 8:80 active ready running…

You can now use the multipath device as you would use any disk device. A device path will appear under /dev/mapper/3600a098038303452543f464142755a42.

Take the sample, /etc/multipath.conf, under step 2.1 in Accessing Block Storage on Linux or from Appendix A, and create it accordingly on your server. Be aware that special characters or DOS-like carriage returns and line-feed entries wrongly transferred from the document might lead to unexpected behaviour. Make sure you have an ASCII Unix file after copying the contents.

Adapt the multipath block from /etc/multipath.conf to create an alias of the path to access the device under /dev/mapper/mpath1.

multipaths {multipath {

wwid 3600a098038303452543f464142755a42alias mpath1

}}

5. Restart multipathd; you can now create the /backup filesystem and mount on the block device.

[root@e2e2690 ~]# service multipathd restart

[root@e2e2690 ~]# mkfs.ext4 /dev/mapper/mpath1

[root@e2e2690 ~]# mkdir /backup[root@e2e2690 ~]# mount /dev/mapper/mpath1 /backup

6. Check the file systems on both servers; you should see output like the following:

[root@e2e1270 ~]# df -hFilesystem Size Used Avail Use% Mounted on/dev/sda3 879G 1,5G 833G 1% /tmpfs 16G 0 16G 0% /dev/shm/dev/sda1 248M 63M 173M 27% /boot/dev/sdb2 849G 201M 805G 1% /usr/sapdb2690-priv:/usr/sap/trans 165G 59M 157G 1% /usr/sap/transdb2690-priv:/sapmnt/C10




165G 59M 157G 1% /sapmnt/C10

[root@e2e2690 ~]# df -hFilesystem Size Used Avail Use% Mounted on/dev/sda3 549G 2,3G 519G 1% /tmpfs 127G 0 127G 0% /dev/shm/dev/sda1 248M 63M 173M 27% /boot/dev/mapper/mpath1 493G 70M 468G 1% /backup/dev/mapper/datavg-datalv 1,2T 71M 1,1T 1% /db2/dev/mapper/datavg-saplv 165G 60M 157G 1% /usr/sap/dev/mapper/datavg-sapmntlv 165G 60M 157G 1% /sapmnt

If you install an SAP NetWeaver-based SAP application on DB2, you must create sub-directories under /backup owned by the database admin user (db2SID) for full backups and archived log files. For automatic archiving of the log files, you will want to set LOGMETH1 in your DB2 database. Refer to the DB2 documentation (http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0051344.html) for details:



http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0051344.html

http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0051344.html


Installing your SAP landscapeRPM package prerequisitesAn SAP installation requires certain prerequisites with regards to the packages installed on the OS and the OS daemons running. Please refer to the latest installation guides and support notes from SAP for an up-to-date list of these prerequisites. As of the writing of this guide, two additional packages were required for an SAP NetWeaver installation:

compat-sap-c++: Achieves compatibility of the C++ runtime with the compilers used by SAP

uuidd: Maintains OS support for the creation of UUIDs

1. Check if uuid daemon (uuidd) is installed. If it’s not, install and start it.

[root@e2e2690 ~]# rpm -qa | grep uuidd[root@e2e2690 ~]# yum install uuidd[root@e2e2690 ~]# chkconfig uuidd on[root@e2e2690 ~]# service uuidd start

2. Follow SAP note 2195019 and install package compat-sap-c++ and create a specific soft-link, which is required by the SAP binaries.

[root@e2e2690 ~]# yum install compat-sap-c++....

[root@e2e2690 ~]# mkdir -p /usr/sap/lib[root@e2e2690 ~]# ln -s /opt/rh/SAP/lib64/compat-sap-c++.so /usr/sap/lib/libstdc++.so.6

Download your SAP softwareLog in to the SAP Service Marketplace (https://support.sap.com/swdc) and download the required digital versatile discs (DVDs) to a local share drive and then transfer them to your provisioned server. Another option is to download the SAP Software Download Manager, install it on your target server and directly download the DVD images to the server. See http://service.sap.com for more information on the SAP Software Download Manager.

Note that you will need an S-User ID and the Download Software authorization when downloading the DVDs from the SAP Service Marketplace. See https://websmp106.sap-ag.de/~sapidp/012002523100008495752016E/ if you need to request an S-User ID.

Preparation for SAP’s Software Provisioning Manager (SWPM) graphical user interface (GUI)Depending on your network bandwidth and latency, you may want to run the SAP SWPM GUI remotely in a virtual network computing (VNC session). Another option is to have the GUI running locally and connect to SWPM on the target machine.

For the second option, please consult the SWPM documentation; the first option is demonstrated below. This option installs a VNC server, which might not be in line with hardening your operating system. You will want to make sure you are meeting your security measures. Please refer to the VNC documentation to get an overview on its functionality in case you are not familiar with it.



https://websmp106.sap-ag.de/~sapidp/012002523100008495752016E/

https://websmp106.sap-ag.de/~sapidp/012002523100008495752016E/

http://service.sap.com/

https://support.sap.com/swdc


1. Use the following command to install a VNC server, an X11 window manager and a console tool to run SWPM’s GUI in a remote session.

[root@e2e2690 ~]# yum install tigervnc-server

...

The command in step 1 will install several dependent packages on your server. Next, you will need an X11 window manager—the smallest, lightest and oldest of which is twm; it is included in every Linux distribution.

2. Use the following command to install the window manager.

[root@e2e2690 ~]# yum install twm

3. Install a terminal emulator (e.g., xterm):

[root@e2e2690 ~]# yum install xterm

4. Start the VNC server from the command-line:

[root@e2e2690 ~]# vncserver

You will now require a VNC client program; there are multiple implementations available for all operating systems at no cost. Typically, you will need port 590X (where X is the number of the servers running, starting at 1) to be accessible from your client. If you connect to your server’s public IP, you will see a screen similar to Figure 1. You might have to start an xterm from the background menu of twm.

You can now start SWPM (sapinst) from the xterm.

Figure 1. Connecting to the server’s IP




Installing SAP softwareAfter downloading the installation media, follow the standard SAP installation procedure documented in the SAP installation guide for your SAP version and components, and the corresponding SAP notes.

You can start SAP SWPM from the xterm, and execute the installation steps. Figure 1 shows the SAP SWPM for a standard installation.

Figure 1. SAP SWPM

Figure 1 provides the steps for a three-tier setup. Begin by selecting Distributed System and execute the first two steps in the list shown in Figure 1 on the database server. The third step can be executed on the application server(s). Make sure that you use the private addresses for the ASCS and the database hostnames during installation of the application servers. This will assure that network traffic between the application server and ASCS, or database, will path through the private network and not through the public network.




Figure 1. SAP SWPM




Appendix AFollowing is a sample multipath.conf for Red Hat 6.X and NetApp-based iSCSI LUNs.

defaults { user_friendly_names no max_fds max flush_on_last_del yes queue_without_daemon no dev_loss_tmo infinity fast_io_fail_tmo 5}# All data under blacklist must be specific to your system.blacklist { wwid "SAdaptec*" devnode "^hd[a-z]" devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^cciss.*"}devices { device { vendor "NETAPP" product "LUN" path_grouping_policy group_by_prio features "3 queue_if_no_path pg_init_retries 50" prio "alua" path_checker tur failback immediate path_selector "round-robin 0" hardware_handler "1 alua" rr_weight uniform rr_min_io 128 }}

# Sample multipath.conf multipaths extension for ‘human readable’ device paths:

multipaths {multipath {

wwid XXXXYYYZZZalias pathname

}}




TrademarksIBM, the IBM logo, ibm.com, DB2 and Bluemix are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

SoftLayer® is a registered trademark of SoftLayer, Inc., an IBM Company.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, In-tel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Cor-poration in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

SAP® and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries.

This document is current as of the initial date of publication and may be changed by IBM at any time. Not all offerings are available in every country in which IBM operates.

It is the user’s responsibility to evaluate and verify the operation of any other products or programs with IBM products and programs. THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM products are warranted according to the terms and conditions of the agreements under which they are provided.

Actual available storage capacity may be reported for both uncompressed and compressed data and will vary and may be less than stated.

© Copyright International Business Machines Corporation 2017. All rights reserved. This document may not be reproduced in whole or in part without the prior written permission of IBM. Note to US Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.



purpose of this guidewpc.c320.edgecastcdn.net/00c320/sap netweaver quick... · web viewsubmit order...

Documents