#include <lbm.h>
Data Fields | |
| lbm_ulong_t | msgs_sent |
| lbm_ulong_t | bytes_sent |
| lbm_ulong_t | txw_msgs |
| lbm_ulong_t | txw_bytes |
| lbm_ulong_t | nak_pckts_rcved |
| lbm_ulong_t | naks_rcved |
| lbm_ulong_t | naks_ignored |
| lbm_ulong_t | naks_shed |
| lbm_ulong_t | naks_rx_delay_ignored |
| lbm_ulong_t | rxs_sent |
| lbm_ulong_t | rctlr_data_msgs |
| lbm_ulong_t | rctlr_rx_msgs |
| lbm_ulong_t | rx_bytes_sent |
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::msgs_sent |
Number of LBT-RM datagrams sent. Depending on batching settings, a single LBT-RM datagram may contain one or more messages, or a fragment of a larger message. With LBT-RM, larger messages are split into fragment sizes limited by configuration option transport_lbtrm_datagram_max_size (default 8KB).
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::bytes_sent |
Number of LBT-RM datagram bytes sent, i.e., the total of lengths of all LBT-RM packets including UM header information.
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::txw_msgs |
Number of LBT-RM datagrams currently in the transmission window. Each source transport session maintains a transmission window buffer (the size of which is set by transport_lbtrm_transmission_window_size, default 24MB). When the source transport receives a NAK, the corresponding message for retransmission must be found in this transmission window.
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::txw_bytes |
Number of bytes currently in the transmission window. See txw_msgs (above) for a description of the transmission window. Typically, this count approaches its window size or exceeds it by a small amount.
Number of NAK packets received by this source transport. UM batches NAKs into NAK packets to save network bandwidth. This should always be less than or equal to naks_rcved (below).
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::naks_rcved |
Number of individual NAKs received by the source transport. When a source transport receives a NAK from a receiver transport, it may respond by re-transmitting the requested LBT-RM datagram, or it may send an NCF. The NAKing receiver transport responds to the NCF by waiting (timeout set by transport_lbtrm_nak_suppress_interval, default 1000 ms), then re-sending the NAK.
Number of NAKs this source transport ignored and sent an NCF with reason code "ignored". A source transport ignores a NAK for a datagram it has already recently retransmitted. How "recently" is determined by the configuration option source transport_lbtrm_ignore_interval (default 500ms). If this count is high, a receiver transport may be having trouble receiving retransmissions, or the ignore interval may be set too long.
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::naks_shed |
Number of NAKs this source transport has shed by sending an NCF with reason code "shed". When a source transport's retransmit rate limiter and retransmit queue are both at maximum, it responds to a NAK by sending an "NCF shed", and does not retransmit. The receiver transport should wait, then send another NAK. If this count is high, one or more crybaby receiver transports may be clogging the source transport's retransmit queue.
Number of NAKs this source transport has not yet processed because doing so would exceed its retransmit rate limit (set by configuration option transport_lbtrm_retransmit_rate_limit, default 5Mbps). For each of these NAKs, the source transport immediately sends an NFC rx_delay, then queues the retransmission for a later send within the rate limit. If this count is high, one or more crybaby receiver transports may be clogging the source transport's retransmit queue.
| lbm_ulong_t lbm_src_transport_stats_lbtrm_t_stct::rxs_sent |
Number of LBT-RM datagrams retransmitted by this source transport (incremented under the same circumstances as rx_bytes_sent, below). In a normal, light-loss scenario, most NAKs induce a retransmission. When losses becomes heavy and/or many receiver transports begin losing the same LBT-RM datagrams, NCF-related no-retransmit counts (naks_ignored, naks_shed and naks_rx_delay_ignored) may begin to inflate, and retransmissions (rxs_sent/rx_bytes_sent counts) may become significantly lower than NAKS received (naks_rcved).
Number of LBT-RM datagrams currently queued by the data rate limiter. When a source transport attempts to send messages (any type) faster than its data rate limiter allows (set by configuration option transport_lbtrm_data_rate_limit, default 10Mbps), the data rate limiter queues the messages until they can be sent within the data rate limit.
Number of LBT-RM transport retransmission datagrams currently queued by the retransmit rate limiter. When a source transport attempts to send retransmissions faster that its retransmit rate limiter allows (set by configuration option transport_lbtrm_retransmit_rate_limit, default 5Mbps), the retransmit rate limiter queues retransmissions until they can be sent within the rate limit. naks_rx_delay_ignored (above) will generally also rise if this count is high.
Number of LBT-RM transport total bytes retransmitted by this source transport (triggered under the same circumstances as rxs_sent, above). In a normal, light-loss scenario, most NAKs induce a retransmission. When losses becomes heavy and/or many receiver transports begin losing the same LBT-RM datagrams, NCF-related no-retransmit counts (naks_ignored, naks_shed and naks_rx_delay_ignored) may begin to inflate, and retransmissions (rxs_sent/rx_bytes_sent counts) may become significantly lower than NAKS received (naks_rcved).
1.5.2