|
Jul 13th, 2011 at 12:56am
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.
|