saprouter installation instructions origiinal

4
SAPROUTER INSTALLATION STEPS The saprouter software can reside on any UNIX node that has a route to all SAP nodes (3.1 and 4.6) and SAP OSS. Pearson is connected to OSS by a Cisco router and ISDN line that connects to SAP in Foster City, CA. The Cisco router allows up to two (2) saprouter nodes to be physically connected simultaneously. It is important to note that the router ports will respond only to the following MAC addresses. These addresses have been set in the router. Therefore, it is necessary to set an alternate Ethernet hardware address in AIX. Be sure to set "Enable Alternate address" to yes. 02:60:8c:e8:a7:13 02:60:8c:f5:14.aa It is also important to note that the primary saprouter must be accessible to the Pearson SAP user community via the address 168.146.11.46. This address is set in SAPGUI and cannot be easily changed. You may need to create an Ethernet alias to accomplish this. Also note that SAP uses 168.146.20.20 as their primary access point (saprouter) and this can be aliased as well. 1. Establish a physical connection to the Cisco router. Set an alternate Ethernet hardware address if necessary. Assign an IP address of 168.146.20.[20-30] to the interface with 255.255.255.128 as the netmask and 168.146.20.1 as the gateway. Ping the Cisco router at 168.146.20.1. If unsuccessful, check to make sure that the alternate Ethernet address has been properly set. 2. Add the following static routes using smitty route (permanent): Type Destination Gateway Hops Netmask Net 204.79.199.0 168.146.20.1 1 255.255.255.128 Net 204.79.195.0 168.146.20.1 1 255.255.255.128 Make sure you can ping 204.79.199.5, 204.79.195.1 and sapserv4. 08/23/22 E. C. Kishkill / document.doc Page: 1 of 4

Upload: venkat

Post on 26-Dec-2014

288 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: SAPROUTER Installation Instructions Origiinal

SAPROUTER INSTALLATION STEPS

The saprouter software can reside on any UNIX node that has a route to all SAP nodes (3.1 and 4.6) and SAP OSS. Pearson is connected to OSS by a Cisco router and ISDN line that connects to SAP in Foster City, CA. The Cisco router allows up to two (2) saprouter nodes to be physically connected simultaneously. It is important to note that the router ports will respond only to the following MAC addresses. These addresses have been set in the router. Therefore, it is necessary to set an alternate Ethernet hardware address in AIX. Be sure to set "Enable Alternate address" to yes.

02:60:8c:e8:a7:1302:60:8c:f5:14.aa

It is also important to note that the primary saprouter must be accessible to the Pearson SAP user community via the address 168.146.11.46. This address is set in SAPGUI and cannot be easily changed. You may need to create an Ethernet alias to accomplish this. Also note that SAP uses 168.146.20.20 as their primary access point (saprouter) and this can be aliased as well.

1. Establish a physical connection to the Cisco router. Set an alternate Ethernet hardware address if necessary. Assign an IP address of 168.146.20.[20-30] to the interface with 255.255.255.128 as the netmask and 168.146.20.1 as the gateway. Ping the Cisco router at 168.146.20.1. If unsuccessful, check to make sure that the alternate Ethernet address has been properly set.

2. Add the following static routes using smitty route (permanent):

Type Destination Gateway Hops NetmaskNet 204.79.199.0 168.146.20.1 1 255.255.255.128Net 204.79.195.0 168.146.20.1 1 255.255.255.128

Make sure you can ping 204.79.199.5, 204.79.195.1 and sapserv4.

3. The saprouter and nipping executables should already exist in /usr/sap/<SID>/SYS/exe/run. Copy them from a working saprouter node if necessary.

4. Create or copy saprouttab (routing table) from an existing saprouter node into /home/<sid>adm. Ensure that the hosts defined in saprouttab can be resolved properly and accurately. You may need to add/change entries in /etc/hosts.

5. Copy the following scripts from an existing saprouter node to /etc:(Make corrections to scripts if necessary and make sure they are executable)- rc.saprouter- rc. saprouter_stop

04/10/23 E. C. Kishkill / document.doc Page: 1 of 4

Page 2: SAPROUTER Installation Instructions Origiinal

- rc.saprouter_refresh (optional)

6. Add the following entry to /etc/inittab: saprouter:2:wait:/etc/rc.saprouter > /dev/console 2>&1

7. Since <sid>adm will be used in executing saprouter, make sure proper user environment is set up and saprouttab is owned by <sid>adm.sapsys.

8. Start up saprouter by running /etc/rc.saprouter (as root).

9. Test functionality using using nipping (see SAPROUTER_INSTALL_UNIX).

10. Have BASIS and SAP test saprouter.

PLEASE SEE THE FOLLOWING PAGE FOR INSTRUCTIONS ON MOVING THE SAPROUTER TO THE ALTERNATE NODE.

04/10/23 E. C. Kishkill / document.doc Page: 2 of 4

Page 3: SAPROUTER Installation Instructions Origiinal

The instructions below assume that the new node has been prepared according to the instructions on the previous pages.

Use the following steps to make the new node the primary saprouter:

Important: Saprouter will be inaccessible during the switchover process.

1. Stop saprouter on the old node: /etc/rc.saprouter_stop

2. Remove the 11.46 IP alias from the old node 11 interface: ifconfig <interface> delete 168.146.11.46.

3. Disable or remove the 20.20 IP alias from the old node 20 interface.Ifconfig <interface> delete 168.146.20.20

4. Copy the most recent saprouttab to the new node. Note that some /etc/hosts entries may need to be manually updated as well.

5. Add the 11.46 IP alias to the new node 11 interface:ifconfig <interface> alias 168.146.11.46 netmask 255.255.255.128

6. Check the .20 interface on the new node to make sure the hardware (MAC) address is valid (see note on page page 1).

lsattr –e –l <device>

Bring down the network interface and change if necessary.

7. Add the 20.20 IP alias to the new node 20 interface or change the IP address of the 20 interface to 20.20.

ifconfig <interface> alias 168.146.20.20 netmask 255.255.255.128

8. Ensure saprouter is up on the new node. You can execute it from the command line as root as follows: nohup /etc/rc.saprouter &

9. Make sure sapserv4 is reachable and SAP can reach the PTC servers using 168.146.20.20. You may need to add the static routes in step 2 of page 1.

10. IMPORTANT:

Remove the following linez from /etc/rc.net from the old node and add to the new:ifconfig <interface> alias 168.146.11.46 netmask 255.255.255.128ifconfig <interface> alias 168.146.20.20 netmask 255.255.255.128

Remove the rc.saprouter inittab entry from the old node and add to the new.

04/10/23 E. C. Kishkill / document.doc Page: 3 of 4

Page 4: SAPROUTER Installation Instructions Origiinal

04/10/23 E. C. Kishkill / document.doc Page: 4 of 4