Urgent: AXAPTA Bandwidth needed between remote sites.

TheWall

Hi, We need to find out what size Bandwidth we need between 2 sites.

There is 2 Sites: "Site A" Will have 2 x AOS Servers, 1 x SQL Server, 1 x EP Server and 70 Clients. "Site B" Will have 15 Clients connecting to
"Site B". Site A and B have are in the same domain.

They currently have a 128k diginet Line. Will That be adequate or what is recommended?

Thanks

rakesh.darge

Hi,
I assume that you have Axapta 3.0 or Axapta 4.0.

Axapta has defined the following:

ASU is the load generated by Axapta 2.5 or 3.0 or 4.0 when creating and invoicing the amount of 10 salesorder with each 5 orderlines processed over the period of 1 hour.
That's a total of 10 Salesorder with a total of 50 salesline in one hour.
Please read at Technet.damgaard.com 'ResourcesHardware Sizing Guide' about the definition of ASU. Please also read about the number of ASU the different Axapta modules produce.

With the above definition of ASU and demand for bandwidth and latency, and not at all having discussed the need for hardware, Navision a/s on the standard Axapta 2.5 or 3.0 or 4.0 gives the following rule of thumb that:

1) ISDN 64kbps is able to handle the throughput of 10 ASU, meaning that you e.g. can produce 100 salesorder with a total of 500 saleslines over a period on 1 hour.
The demand for latency has to be <100ms and preferably <50ms on the communication line.
When the latency is high, it has a huge impact on the speed of the system.
Development gives the following formula to compute the bandwidth requirements.
The formula
ASU x 6,4 kbps = y
If y < 64 kbps then bandwidth = 64 kbps
else bandwidth = y kbps
E.g. The requirement for bandwidth by the load of 20 ASU
20 x 6,4 kbps = 128 kbps
Required bandwidth = 128 kbps
Keep in mind that the above has been tested on a standard Axapta 2.5 installation. If you have been adding to the standard application you have to consider the impact of this.

Recommendations:-
These can be rule of thumb only so please apply your common sense when sizing for a customer.
When talking bandwidth and latency requirements, you will need to agree to a performance level for Axapta with your customer.
Make sure that the bandwidth and latency are measured using Axapta's built-in tool rather than relying on what the network provider promises and measure it periodically over a period of time and particularly at peak hours to ensure that you know what the user will experience. Also make sure that the measurements are done on the production environment with as realistic a load as possible. It is of little value to measure one client loading a line that has to provide for 100.
Preferably Axapta should have a dedicated line to avoid mail, print etc. generating inexplicable sporadic bad performance. If this is not possible, make sure that the connection amply sized.
Bear in mind that due to the client/server architecture of Axapta, Axapta is hit very hard from high latency.

Regards
Rakesh...

TheWall

Thanks, that should work.

If anyone know where is can find the tool that HP created it would still be appreceated?

Regards