<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Disagree with adding suppression/gas systems all over the place.<br>
<br>
I suspect a lesson-learnt should be to not mix network equipment
rooms with general office-type rooms in the same building, or at
least the same air-circulation environment.<br>
<br>
In general, there is very little to burn or cause fire to spread in
a equipment hosting environment - racks and concrete floors don't
burn, cabling is often 'plenum grade' which means difficult to get
burning and won't keep burning when the heat is removed. In a
datacentre equipment room Its usually better to have no fire
suppression system, but lots of heat/smoke detection to get an alarm
triggered, plus some portable extinguishers near the door for people
to use. A sprinkler system (even a dry-pipe system) fired off
because of some smoke from a blown power supply or fried
printed-circuit-board in a single rack would cause more damage to
the rest of the equipment in the room than if the rack was left to
smoulder for a while.<br>
I'm fine with the exchange equipment spaces having VESDA systems,
and no suppression, just like this Warrnambool exchange.<br>
<br>
This fire started in or above an office room, filled with paper,
boxes, wooden furniture, etc - a very different type of fish from a
suite of humming steel equipment racks. The network damage was to
melted cabling which was run over the office room, plus smoke damage
to the equipment hosting space as the A/C and open fire doors
allowed smoke through to the equipment spaces. While its not listed
in the report, I'll bet the VESDA system was only monitoring the
equipment spaces, so by the time the smoke drifted through to
trigger it, the office room was already well ablaze.<br>
<br>
In office spaces with lots of flammable material, absolutely have
fire suppression. In equipment rooms, don't.<br>
And between the two - don't allow them to share air circulation
systems, and keep the bloody doors shut.<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAHgLLqYCKzM3OrkdwdtJ+gyexo5ZV_+ugDg-gFyt4TRmvmUosQ@mail.gmail.com"
type="cite">
<div>
<div>
<div><br>
</div>
<div>Certainly the legislation doesn't compel telstra todo
anything. </div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">On Tue, Apr 2, 2013 at 9:41 AM,
Matthew Moyle-Croft <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:mmc@mmc.com.au"
target="_blank">mmc@mmc.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">It's more complex than that - a lot of
POIs are, in fact, Telstra exchanges. So we may in
fact need Telstra to install fire suppression not
NBNCo or we'll still lose (one O) a POI in future ...<span
class="HOEnZb"><font color="#888888">
<div>
<br>
</div>
<div>MMC</div>
<div><br>
</div>
</font></span></div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Apr 1, 2013 at
4:34 PM, Jake Anderson <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:yahoo@vapourforge.com"
target="_blank">yahoo@vapourforge.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>I imagine with the benefit of hindsight
they are now doing a cost/benefit on each
exchange and seeing if its worth putting
in.<br>
Its probably cheaper for them to loose
service for a while and fix it rather than
put eleventy million halon systems in.<br>
<br>
I do hope NBNco is doing a lessons learnt
from this though, their concentration
feels like its going to be much higher,
loosing a POI for a couple of weeks would
be a "bad thing".<br>
I wonder at what point in the network it
would be feasible to slap a
wireless/satellite/whatever on top of a
box and replace the POI (at a reduced
rate) until the POI is back up.
<div>
<div><br>
<br>
On 02/04/13 02:29, Tom Storey wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">No, but cant say I was
particularly looking for them. I
suppose I kind of assumed there
might be something like a gas based
system in there though. I mean,
theres a lot of expensive gear,
you'd think you'd want to avoid
damaging it, and/or losing the
building. Imagine if they had to
rebuild, the outage would have
lasted months, instead of the weeks
they managed to restore service in.
<div> <br>
</div>
<div>Ignorance aside, and apart from
the obvious "it would cost a shit
load to add it to them all", are
there any particular reasons why
major regional
exchanges wouldn't have fire
suppression?</div>
<div><br>
</div>
<div>To me it seems that places like
Warrnambool and sites with similar
significance (the ones Telstra
refer to as KTPs) could probably
benefit from some kind of
suppression. These events might be
rare, but they have a big impact
when they happen.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 31 March
2013 23:46, Mark Newton <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:newton@atdot.dotat.org"
target="_blank">newton@atdot.dotat.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="auto">
<div>
<div><br>
</div>
<div><br>
On 30/03/2013, at 6:19,
Tom Storey <<a
moz-do-not-send="true"
href="mailto:tom@snnap.net"
target="_blank">tom@snnap.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p dir="ltr">Is it just
me, or are there zero
mentions of fire
suppression systems?</p>
</div>
</blockquote>
</div>
There were unlikely to be
any.
<div><br>
</div>
<div>You've been in country
telephone exchanges before.
Do you recall ever seeing a
sprinkler head?<span><font
color="#888888"><br>
<div><br>
</div>
<div>
<div> - mark</div>
<div><br>
</div>
</div>
</font></span></div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<div>
<pre>_______________________________________________
AusNOG mailing list
<a moz-do-not-send="true" href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a>
<a moz-do-not-send="true" href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</div>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net"
target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</body>
</html>