Comtech EF Data MIDAS Version 4.X Basic Configuration User Manual
Page 122
MIDAS 4.2 Basic Configuration, Rev. 0
3–14 MIDAS
Reports
T
T
X
X
F
F
a
a
i
i
l
l
u
u
r
r
e
e
s
s
Displays the number of times the specified control channel could not send a
message from the controller server, due to hardware problems on the control
channel card.
K
K
e
e
e
e
p
p
A
A
l
l
i
i
v
v
e
e
O
O
v
v
e
e
r
r
h
h
e
e
a
a
d
d
Indicates the amount of time involved in maintaining status information on
remote nodes. The specific value entered tunes this to provide the desired
overhead. A higher amount of overhead is expected when it is critical to
quickly establish the status of faulty nodes.
R
R
e
e
t
t
r
r
y
y
R
R
a
a
t
t
e
e
Indicates the percentage of re-transmissions happening on the control channel.
A percentage less than 50 is normal. A percentage greater than 50 indicates
extended call setup times and heavy network loading.
N
N
o
o
d
d
e
e
R
R
e
e
t
t
r
r
y
y
S
S
t
t
a
a
t
t
i
i
s
s
t
t
i
i
c
c
s
s
A message sent from a node may not always get to the controller server on the
first transmission from a node. The node may have to re-send the message a
number of times before the controller server successfully receives the
message. An attempt to re-send a message is called a retry.
On the left side of the Control Channel Statistics window is a box containing
two columns of numbers. The columns can be scrolled to view all the retry
quantities and counts.
The left number is a retry quantity, ranging from 0 to 100, and “100+” (100+
represents retries in excess of one hundred times). To the right of each retry
quantity is the total number of retries that matched the quantity. For example,
if nodes made one retry 72 times, a partial view of the columns would look
similar to the following illustration:
Typically, there will be a high number of retries at the zero retry quantity,
indicating that messages were indeed received by the controller server on the
first transmission.
If nodes are re-sending messages more than six or seven times, there is heavy
traffic on the control channel, or the nodes’ messages are not getting to the
controller server for some other reason. There could be many reasons for
excessive re-send attempts, but the most common reason is congestion of the
control channel.