01/23/2003 Status Monitor

Just a quick update because I'm not sure if this was covered elsewhere.
For those that monitor the network via IPMonitor, it has been on a roller-coaster and showing 'false' alerts since the Unix router was put in place. Currently, anything that comes up in orange has been determined to be an issue with the new routing/router configuration, and not a problem with the servers or network access. We are trying to resolve this but continue to hold as our highest priority, the network stability with the new router in place.
Red alerts have been determined to be legitimate issues with the server in question, and we are responding to those appropriately as they arise. If there are any questions about the Staus Monitor, please feel free to post them here. We do not yet know specifically, where the issue lies, so I am unable to clarify what that is at this time. Thank you.......

[Brangwyn]

Shouldnt the new unix router be set as a dependancy on the other server monitors ? that way they wouldn't (or at least shouldnt) come up as failures if ipMonitor realises that the router actually goes red/orange first.

From what I've been seeing the last few hours (prior to the last tweaks to the router) high packet loss was corresponding with the ipmonitor going orange for a bunch of servers as well.

edit, like right now for instance, the forum took 18 seconds to load this page, usually takes < 1 sec ipmonitor showing a bunch of orange alerts,

If I understand correctly, what you saw a few hours ago was just prior to recompiling the router kernel in response to an approximate 10% packet loss. When Alex & James left 5 hours ago, I was advised that packet integrity was 'clean as a whistle'. Haven't thought about checking behind them, as I was busy clearing the ticket queue for quite awhile.......

[Brangwyn]

That few hours was about 70 minutes ago actually when I last started getting lag on sites including the forum here

My distance from the servers could be compounding things too, but usually things are pretty sweet.

Half an hour of monitoring traffic reveals a .0053789% packet loss.

Thinking I should clarify......

.0053789%= 5/1000ths of one percent however, I double checked and that doesnt reflect actual "packet loss". Only 5/10000ths of one percent were lost, the other 45/10000ths of one percent arrived, but were somehow corrupted





....I wish he'd just tell us that only 1 packet was lost out of 2045 tested...