Generic selectors
Exact matches only
Search in title
Search in content

Reply To: ALU: DL PDU discarded due to congestion

#68437
pix
Guest

sommer,

i’m afraid i can’t help further on the flow control : i will have to dig into my ALU specs, and today is not the day (i’m going on holidays ๐Ÿ™‚ ).

I am quite certain there are other parameters related to flow control, but maybe they are system parameters. Anyway, do try the values you show. You might be the 1st one on earth to do that ๐Ÿ˜‰

Ater in high load will VERY strongly penalize the GPRS throughput from end user perspective. By default the Ater enters the HIGH LOAD state when the load exceeds 70% (that’s changeable through the “HI ATER LOAD” parameter).
A good thing would be to increase this threshold to 80% and add the 2 extra Ater PS. Indeed, 70% seems a bit harsh when you have many Ater PS / GP board.

after that -> ensure that Ater high load time is < 100s at BH. (for example) As a consequence, more traffic will be handled by the GPU though. So your GPU CPU might get overloaded ! regarding the GSL - yes, there is a very simple calculation based on the GSL messages and volume indicators. I will share it here when i come back from holidays. However, keep in mind that you only need 2 or 3 GSL timeslots per GP board. Just be on the safe side, and put 3 GSL ๐Ÿ™‚ 3 GSL = 3*64kbps, and that is normally plenty enough to handle the BSS paging coordination. Check out the BSCGP indicators -> BSCGP is the protocol carried by the GSL.
In NPO you must find 2 network objects related to GSL. One of them is contains “lapd”, and the other “GSL”. (network object = cell, BSC, TRX, etc, on the left side of the screen)

I’ll give you more info in about 2 weeks, if you can hold on…
regards
pix