A hospital path that had been clean now shows TCP retransmissions climbing toward the imaging archive. What should page the network team about that condition?
Select an answer to reveal the explanation.
Short Explanation
A smoke alarm has to ring, because a chart on the wall does not wake anyone up. You alert on the TCP retransmissions that climbed on a path that had been clean. A CPU page, a silent dashboard, or a later capacity project does not call the network team about that path.
Full Explanation
TCP retransmissions climbing on a path that had been clean are a network condition, and the network team hears about them only when a rule is tied to that behavior and set to notify. An alert rule that pages on that TCP retransmission behavior matches the symptom the hospital observed and turns it into a page. An end-user CPU alert on a single clinical workstation watches an endpoint processor. A busy workstation can page while the path is fine, and a path that starts retransmitting stays silent if the only rule is a CPU rule. A path dashboard that shows the climb but has no alert rule lets someone see the change only if they already have the screen open. It does not page the team. A capacity project that studies the link later and does not page anyone may help a future redesign. It is not an alert, and nobody is notified when the retransmissions rise. Exam caveat: an alert is a rule that fires and notifies, while a chart or a later project does not take the place of that rule. Operational check: during a maintenance window, confirm the TCP rule pages when that retransmission condition is present and clears after the path returns to its prior behavior.