Where do you need to change the IP address on the oss site, and how can you configure the saprouter?
You need to check your RFC connections in SM59 and your hosts file.
If you have set up any external ftp connections to your system, you also need to check if they use IP address or hostname.
If the SAProuter runs on the server you are changing the IP address, you must create a customer message for SAP and ask them to change the IP at their site. The IP address of a SAProuter must be from an official range. You must also update your SAProuter data and change the IP on SAPNet (system-data).
In saprouttab you need to adjust the IP as well.
How to Connect to your SAP System via SAPRouter?
On your SAPRouter, edit your saproutab file,
add P xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzzz password) example:
P 192.168.145.130 10.240.7.10 3200 basis ---> Where 192.168.145.130 is your computer ip address on the internet, change this to * so that your saprouter will accept any ipaddress from the internet.
10.240.7.10 ---> is your SAP Server IP Address
3200 ---> 32 is constant, 00 is your PRD system number
basis ---> is the your password.
P * * * * ---> entry if you permit all
issue comman saprouter -n to reload the new saproutab file.
On your SAPGui logon screen (Remote Computer)
Description : Production Server
Application Server : 10.240.7.10
SAP Router String : /H/192.168.240.35/W/basis/H/
System number : 00
Changing the IP address of your SAP Server
How SAP Router Works?
SAProuter examines any incoming data packets, checks the route and authorization and then sends them to their specified targets. The partner that sets up the connection specifies the route (from SAProuter to SAProuter and to the target). This procedure is known as source routing.
If you want a connection, from a SAPgui to an R/3 System for example, to run through a SAProuter, then you need to enter the route in the SAPgui command line.
You can use SAProuter if there is no direct IP connection between the communication partners. SAProuter must be running on a host that is connected to both IP networks. It can then receive data from the SAPgui in one IP network and relay it to the R/3 server in another IP network, and vice versa. Normal IP routing is used between the application programs and the SAProuters.
Connections established using SAProuter have the additional advantage that no end-to-end connections between the participating system are necessary on network level. For example, if accessing a frontend PC on an R/3 server with an intermediate SAProuter, it is not necessary to define the complete path between the two systems at TCP/IP level. It is
sufficient if both parties can reach the SAProuter. From an SAP communication viewpoint, this represents a point of concentration in your network that serves as a starting point for each subconnection.
Each subnetwork stored logically behind a SAProuter is therefore reduced to the network address of the SAProuter.
Without SAProuter, the Internet Protocol (IP) addresses must be unique, which cannot always be guaranteed, particularly on international networks.
With SAProuter it is possible to connect two points that have unofficial,or even identical, IP addresses. Therefore, it is rarely
necessary to adapt existing address topologies using official IP addresses.
SAP Online Service & Support now only supports SAProuter connections due to these advantages. Because SAP routes all accesses to internal systems (such as SAPNet - R/3 Frontend) and all service connections via SAProuter, the connection between SAP and the customer is reduced to a single SAProuter - SAProuter connection.
