Bandwidth requirement of ISP to connect to SAP server through VPN
A D V E R T I S E M E N T
We are in the process of implementing SAP for our overseas sales
offices. However, the Server will be situated at our country. We want our
overseas sales office to connect to our SAP Server through VPN. What should be
the optimum internet bandwidth that they should use at their place to connect to
our SAP server? Does SAP recommend any standard bandwidth for this process?
From our experience, there is no general rule that one can follow, as several
factors will affect the connectivity
1. No of hops between your ISP and that of the remote site, the more hops the
poorer the performance, even having large bandwidth may not improve the
performance by much if there are numerous hops in between.
2. Is the Internet connectivity solely used for your VPN or other purposes
such as web surfing, email etc, other traffic can consume large amount of
traffic thus causing your SAP performance to be poorer
3. ISP's bandwidth to the public internet - If the ISP is heavily over
subscribed, and has limited bandwidth connecting to the international network,
you will find that you will not be able to get the international throughput you
subscribed for as such, performance may be poor even you have paid for a line
with a large bandwidth
4. No of users at your remote office using the VPN - In general the lines we
use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines
with 512kbps connectivity and they enjoy close to local Lan performance for SAP.
See from which network IP address and host name a user has logged on
To see the network IP address from which a user has
perform the following steps:
Call transaction OS01,
"Change View" button.
If you are using Citrix, you will not be able to view
the user individual IP address as it will be the same Citrix IP address.
To check the speed and quality of the user's network
select the desired presentation server and click
"10 X Ping" button.
No System name and transaction code in SM04
If you have more than one application server, use
AL08 instead of SM04.
It is because they are at the logon screen which has established a
You will notice that the transaction code shown when there is no user name is
This shows you which workstations out there have the login screen up but have
not yet entered a user name and password.
The transaction column shows the Last executed transaction code.
Sometimes your users will have multiple sessions open. If they do, to the
system, it is the same as multiple logins as it relates to the resources used
So the user name will show up more than once in AL08.
Under the application server they are logged into, each instance of that user
name on that application server represents a session open.
For instance if you run AL08, you will
have your name show up at least twice on the application server you are logged
One will show AL08 and the other will not
have a transaction next to it.
Then you will notice your user name showing up on all other application
servers with no transaction. This is because you are using