You are on page 1of 4


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.


It is also important to note that the primary saprouter must be accessible to the Pearson SAP user
community via the address 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 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 as the netmask and as the gateway. Ping the Cisco router at 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 1
Net 1

Make sure you can ping, 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/13/11 E. C. Kishkill / 55763108.doc Page: 1 of 4

- 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.



04/13/11 E. C. Kishkill / 55763108.doc Page: 2 of 4

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

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

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 netmask

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 netmask

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
You may need to add the static routes in step 2 of page 1.


Remove the following linez from /etc/ from the old node and add to the new:
ifconfig <interface> alias netmask
ifconfig <interface> alias netmask

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

04/13/11 E. C. Kishkill / 55763108.doc Page: 3 of 4

04/13/11 E. C. Kishkill / 55763108.doc Page: 4 of 4