mailing list archives
Re: cost of misconfigurations
From: Darius Jahandarie <djahandarie () gmail com>
Date: Wed, 1 Aug 2012 20:13:38 -0400
On Wed, Aug 1, 2012 at 8:08 PM, Diogo Montagner
<diogo.montagner () gmail com> wrote:
A misconfiguration will, at least, impact on two points: network
outage and re-work. For the network outage, you have to use the SLAs
to calculate the cost (how much you lost from the customers' revenue)
due to that outage. On the other hand, there is the time efforts spent
to fix the misconfiguration. Under the fix, it could be removing the
misconfig and applying a new one correct. Or just fixing the misconfig
targeting the correct config. This re-work will translate in time, and
time can be translated in money spent.
Isn't the largest cost omitted (or at least glossed over) here?
Namely, lost customers due to the outage. That's why people have SLAs
and rework the network at all -- to avoid that cost.
Re: UCSF Network Admin?? Henry Stryker (Aug 02)