Collapse AllExpand All

10.2.7.3. Monitoring Message Throughput Previous topic Parent topic Child topic Next topic

A minimum necessary message throughput can be defined for the signaling connection for every access point. The throughput measurement includes the volume of all messages sent by the CC.
The undershooting of the minimum necessary message throughput only takes account of the times when the specified load at least was used. An undershooting of the minimum message throughput is ignored because the number of messages available for transmission is not sufficient.
If the throughput falls short of the threshold value set, the system outputs the error message F8290 (see Section 2.7.6.2, “Message Throughput Undershot”). The undershooting of the minimum message throughput can also be a criteria for changing from the signaling path to the signaling survivability path (see Section 2.7.4, “Advanced Criteria for Signaling Survivability”).
The message F8291 is output to signal a return by the message throughput to permitted values (see Section 2.7.6.3, “F8291 - Net Weakness End”).
Monitoring the minimum message throughput is only active on the signaling path over LAN. The modem connection is not affected in the case of signaling survivability.

Procedure

Every three seconds the system calculates the number of bytes sent during this interval. The result is then used to calculate the throughput in Kbps. (Bytes sent * 8/3)
The three-second values are used to generate average values over a short (15 seconds: SHORT) and long monitoring time (60 seconds: LONG).
The error message is generated whenever either of the two values (SHORT/LONG) exceeds the limit configured.
The limit is set for the long monitoring duration (LONG). The limit for the short duration (SHORT) is set to 2/3 of the LONG value.
The SHORT interval makes sense with a lower limit because if the network quality jumps, the system can respond faster, that is, within 15 seconds. This interval would be 60 seconds in the case of exact measurement.
The measurement is made at “application level“, in other words, over the TCP/IP stack. On account of stack dynamics, measured values cannot be compared directly with values that are measured directly on the network.

Generation

assistant-2.gif
Configuration Management > System Data > IPDA > Access point
Click Search and enter or change the minimum message throughput on the Quality of Service tab in the Signaling Quality of Service section, then Save.
comwin-2.gif
CHA-STMIB:MTYPE=NCUI2,TYPE=SIGQOS,LTU=99,MINTHRPT=32;
The minimum message throughput is expressed here in Kbps. The value MINTHRPT=0 disables message throughput monitoring. The setting becomes effective immediately.