Latency VS Free Timeslots

Yes.  You need timeslots to carry IP Payload.  Example: A single timelsot at QPSK .793 (Large block) is capable of 394 Bytes....and there are approximately 78-82 slots associated with a 2048k QPSK/.793 upstream (2048k info rate...not IP Data rate).

On the flipside, small block coding (1k) is not nearly as efficient.  But the answer to your question is - you need to have free slots in the network to move traffic off the remote.    

The reason for the increase latency is due to your management traffic (remote --> NMS reporting) having to wait for a free slot to report into the NMS.

You can view the burst timeplan and number of free timeslots from iMonitor.

let me add few cents to this.

The NMS traffic is running in priority queue, which means that it should be processed before any other traffic, and when you see latency in iMonitor look odd, as you would expect NMS icmp rtt be very stable even if the link (network) is full

The main reason why you high latency when the inroute is full is a "sticky demand allocation" (not a sticky-CIR) - this reserves for the particular host the demanded amount of timeslots for 1 second, and therefore even high priority traffic may suffer.

You may disable sticky demand since version 8, but this should be done carefully.

As for timeslots usage monitoring, it is very poor - the only way is to observe it in iMonitor in real time and unfortunately it is not reported in SQL or SNMP and you cannot get historical data.

Hi,
the latency increases only when all the time slots are allocated.
Speaking with an iDirect technician, I understood that setting the Minimum Information Rate (Upstream QoS tab) = 1/2 slot rate, I can assign one slot to 2 satmodem.
If I well understand, this is a Multitrama allocation.
I do not understand what value I have to set.

Regards,