|

Network / Server Availability Report
Four reports are presented below. The reports show overall availability
and downtime for the ATM switches, VLANs (network segments), and servers on
the network. Please read the note below before viewing the
reports.
2010
2009
- December, 2009 data & voice
- Movember, 2009 data & voice
- October, 2009 data & voice
- September, 2009 data & voice
- August, 2009 data & voice
- July, 2009 data & voice
- June, 2009 data & voice
- May, 2009 data & voice
- April, 2009 data & voice
- March, 2009 data & voice
- February, 2009 data & voice
- January, 2009 data & voice
2008
- December, 2008 data & voice
- November, 2008 data & voice
- October, 2008 data & voice
- September, 2008 data & voice
- August, 2008 data & voice
- July, 2008 data & voice
- June, 2008 data & voice
- May, 2008 data & voice
- April, 2008 data & voice
- March, 2008 data & voice
- February, 2008 data & voice
- January, 2008 data & voice
2007
- December, 2007 data & voice
- November, 2007 data & voice
- October, 2007 data & voice
- September, 2007 data & voice
- August, 2007 data & voice
- July, 2007 data & voice
- June, 2007 data & voice
- May, 2007 data & voice
- April, 2007 data & voice
- March, 2007 data & voice
- February, 2007 data &
voice reports
- January, 2007 data &
voice reports
2006
- December, 2006 data &
voice reports
- November, 2006 data &
voice reports
- October, 2006 data &
voice reports
- September, 2006 data &
voice reports
- August, 2006 data &
voice reports
- July, 2006 data &
voice reports
- June, 2006 data &
voice reports
- May, 2006 data &
voice reports
- April, 2006 data &
voice reports
- March, 2006 data &
voice reports
- January, 2006 data &
voice reports
2005
- December, 2005 data &
voice reports
- November, 2005 data &
voice reports
- October, 2005 data &
voice reports
- September, 2005 data &
voice reports
- August, 2005 data &
voice reports
- July, 2005 data &
voice reports
- June, 2005 data &
voice reports
- May, 2005 data &
voice reports
- April, 2005 data &
voice reports
- March, 2005 data &
voice reports
- February, 2005 data &
voice reports
- January, 2005 data &
voice reports
2004
- December, 2004 data &
voice reports
- November, 2004 data &
voice reports
- October, 2004 data &
voice reports
- September, 2004 data &
voice reports
- August, 2004 data &
voice reports
- July, 2004 data &
voice reports
- June, 2004 data &
voice reports
- May, 2004 data &
voice reports
- April, 2004 data &
voice reports
- March, 2004 data &
voice reports
- February, 2004 data &
voice reports
- January, 2004 data &
voice reports
2003
- December, 2003 data &
voice reports
- November, 2003 data &
voice reports
- October, 2003 data &
voice reports
- September, 2003 data &
voice reports
- August, 2003 data &
voice reports
- July, 2003 data &
voice reports
- June, 2003 data &
voice reports
- May, 2003 data &
voice reports
- April, 2003 data &
voice reports
- March, 2003 data &
voice reports
- February, 2003 data &
voice reports
2002
- December, 2002 data &
voice reports
- November, 2002 adata &
voice reports
- October, 2002 data &
voice reports
- September, 2002 data &
voice reports
- August, 2002 data &
voice reports
- July, 2002 data &
voice reports
- June, 2002 data &
voice reports
- May, 2002 data &
voice reports
- April, 2002 data &
voice reports
- March, 2002 data &
voice reports
- Febuary, 2002 data &
voice reports
- January, 2002 data &
voice reports
2001
- December, 2001 data &
voice reports
- November, 2001 data &
voice reports
- October, 2001 data &
voice reports
- September, 2001 data &
voice reports
- August, 2001 data &
voice reports
- July, 2001 report
- June, 2001 report
- May, 2001 report
- April, 2001 report
- March, 2001 report
- February, 2001 report (does not reflect
Feb 17 power-down at Central Office)
- January, 2001 report
2000
The detail section of each report has two collums per type of device or
network segment. Devices or segments are listed by name with their
cumulative down time next to the name. Down times are shown in seconds.
This is done to make math easier.
The summary section of each report (at the top) shows the number of days in
the report period, number of devices monitored, the number of "device
seconds", and the total down time for all devices. "Device seconds" is the
number of seconds in that period times the number of devices managed. It is
a measure of the maximum amount of time that a device could be available during
that time period. Last is the percent availability. Percent availability is
computed using the following formula:
device seconds - total down
100
|
=
|
availability %
|
The overall average is computed similarly across all time periods. The
averages present availability in a 7x24 working environment. Attempting to
separate events based on working hours vs. off hours is simply too difficult
with the tools available. To get a "worst case" working hours availability
figure, run the formula given above with double the number of down seconds.
This will give an availability percentage with all down time incidents
effectively placed within the 7 AM - 7 PM window we consider "working hours".
A note about these statistics: These statistics are not derived from
Divine Truth. They are approximations calculated as carefully and precisely
as possible. These statistics are good enough for duscussions of trending
and general availability. They are not an absolute accounting. There are
several ways in which the statistics could be influenced. One station on
the network captures the availability data; if some thing between that
station and a managed device is down, then that managed device will be
reported as down when it may not be. Also, the report generation algorithm
will throw out corrupt data, so downtime events might not be counted.
Examination of the report generator error log shows that this happens
periodically. In summary, these statistics are a good representation of
what is going on in the network but they are not a perfect
representation.
|