<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-AU" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Apparently the outage window has been cancelled ??? </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] <b>On Behalf Of </b>Sam Silvester<br><b>Sent:</b> Friday, 11 August 2017 9:23 AM<br><b>To:</b> John Duffin <<a href="mailto:jduffin@uptimeinstitute.com">jduffin@uptimeinstitute.com</a>><br><b>Cc:</b> <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br><b>Subject:</b> Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance - 15th</span></p><p class="MsoNormal"> </p><div><div><p class="MsoNormal">Hi John,</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">There's nothing about an ATS that makes it generally 'large' or small relative to an STS.<br><br>Here's a 1RU, 10A ATS: <a href="http://www.apc.com/shop/au/en/products/RACK-ATS-10A-230V-12A-208V-C14-IN-12-C13-OUT/P-AP7721">http://www.apc.com/shop/au/en/products/RACK-ATS-10A-230V-12A-208V-C14-IN-12-C13-OUT/P-AP7721</a></p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I've got many dozen of these deployed in racks right by single corded equipment right now, and I often recommend them to customers who need to put single corded equipment on both the A and B feed to their rack.<br><br>Meanwhile, to pick an example at one of our data centres, we have use a 1500A three phase ATS on the inputs to our UPS.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Cheers,</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Sam</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div><div><div><p class="MsoNormal">On Fri, Aug 11, 2017 at 3:54 AM, John Duffin <<a href="mailto:jduffin@uptimeinstitute.com" target="_blank">jduffin@uptimeinstitute.com</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal">Hi,<br><br>Please do not take this as expert Electrical Engineering advice!<br><br>A quick word on ATS/STS.<br><br>ATS are essentially automated mechanical switches. They can “Make Before Break” or they can “Break Before Make” depending on their design and whichever arrangement is used is dictated by the Electrical Design as determined by the Electrical Engineer. Case and Situation Specific, I would warn against generalising. STS are Solid State devices which have no moving parts. There are reasons why you would use either and it is best not to think of them as interchangeable.<br><br>ATS will normally live in a DC deep in the Electrical Distribution, if you don’t go to the Power Rooms, you many never see one. STS tends to have smaller current carrying capacity and live nearer the IT. For the case of Single Cord Equipment in a Dual Cord DC then, if it’s odd items in a rack, Rack Mount STS are usable. If there’s lots of odd Single Cord Equipment within a DC then a 3rd Supply can be considered but then you have to wonder why the customer is paying for Dual Cord in the first place…<br><br>The point of a real Dual Cord Environment is that Operators like NextDC, can do routine maintenance work and still maintain at least one supply to the IT load. You need to consider single cord equipment in that context and, under the SLA, It is probably going be your problem to keep it powered, not theirs…<br><br>John<br><br>On 10/8/17, 4:26 PM, "AusNOG on behalf of <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>" <<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a> on behalf of <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>> wrote:<br><br> Send AusNOG mailing list submissions to<br> <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br><br> To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> or, via email, send a message with subject or body 'help' to<br> <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a><br><br> You can reach the person managing the list at<br> <a href="mailto:ausnog-owner@lists.ausnog.net">ausnog-owner@lists.ausnog.net</a><br><br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of AusNOG digest..."<br><br><br> Today's Topics:<br><br> 1. Re: NextDC Melbourne - Scheduled Power Maintenance - 15th<br> August (Sam Silvester)<br> 2. Re: NextDC Melbourne - Scheduled Power Maintenance -, 15th<br> August (Peter Tiggerdine)<br> 3. Re: NextDC Melbourne - Scheduled Power Maintenance -, 15th<br> August (Chad Kelly)<br> 4. Re: NextDC Melbourne - Scheduled Power Maintenance - 15th<br> August (James Hodgkinson)<br><br><br> ----------------------------------------------------------------------<br><br> Message: 1<br> Date: Thu, 10 Aug 2017 15:38:14 +0930<br> From: Sam Silvester <<a href="mailto:sam.silvester@gmail.com">sam.silvester@gmail.com</a>><br> To: James Braunegg <<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>><br> Cc: "<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>" <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>><br> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> 15th August<br> Message-ID:<br> <CAAAhk6-CMRyG2xY0Q7i0-dZ-=<a href="mailto:pOcC_PspDmLeGEs23jpP_R9bg@mail.gmail.com">pOcC_PspDmLeGEs23jpP_R9bg@mail.gmail.com</a>><br> Content-Type: text/plain; charset="utf-8"<br><br> Hi James,<br><br> A quick Google tells me APC ATS are break before make, so that is certainly<br> not the defining feature of an ATS vs. STS.<br><br> For cost effective provision of a 'C feed' in racks to catch those pesky<br> single corded devices you just can't live without I see no reason at all to<br> go to the expense of typically larger and more expensive STS, happy to<br> learn more though.<br><br> Sam<br><br><br><br> On Thursday, 10 August 2017, James Braunegg <<a href="mailto:james.braunegg@micron21.com">james.braunegg@micron21.com</a>><br> wrote:<br><br> > Dear All<br> ><br> ><br> ><br> > Anyone with single power supply devices please do not look at getting an<br> > ATS, get a STS !!!<br> ><br> ><br> ><br> > *Short version*<br> ><br> ><br> ><br> > ATS (Automatic Transfer Switch) will typically break power before it<br> > makes, thus the connected device could reboot !!<br> ><br> ><br> ><br> > STS (Static Transfer Switch) will make power before it breaks, providing<br> > no break to the power !<br> ><br> ><br> ><br> > An example of a recommended device is below<br> ><br> ><br> ><br> > <a href="https://www.vertivco.com/en-asia/products-catalog/" target="_blank">https://www.vertivco.com/en-asia/products-catalog/</a><br> > critical-power/power-transfer-switches/liebert-lts-63-to-400a/<br> ><br> ><br> ><br> > Kindest Regards,<br> ><br> ><br> ><br> > *James Braunegg*<br> ><br> > [image: <a href="cid:image001.png@01D280A4.01865B60">cid:image001.png@01D280A4.01865B60</a>]<br> ><br> > 1300 769 972 / 0488 997 207 <1300%20769%20972><br> ><br> > *<a href="mailto:james@micron21.com">james@micron21.com</a> <javascript:_e(%7B%7D,'cvml','<a href="mailto:james@micron21.com">james@micron21.com</a>');>*<br> ><br> > <a href="http://www.micron21.com/" target="_blank">www.micron21.com/</a><br> ><br> > [image: <a href="cid:image002.png@01D280A4.01865B60">cid:image002.png@01D280A4.01865B60</a>] <<a href="http://www.micron21.com/" target="_blank">http://www.micron21.com/</a>><br> ><br> > [image: <a href="cid:image003.png@01D280A4.01865B60">cid:image003.png@01D280A4.01865B60</a>]<br> > <<a href="https://www.facebook.com/micron21/" target="_blank">https://www.facebook.com/micron21/</a>><br> ><br> > [image: <a href="cid:image004.png@01D280A4.01865B60">cid:image004.png@01D280A4.01865B60</a>] <<a href="https://twitter.com/micron21" target="_blank">https://twitter.com/micron21</a>><br> ><br> > Follow us on Twitter <<a href="https://twitter.com/micron21" target="_blank">https://twitter.com/micron21</a>> for important service<br> > and system updates.<br> ><br> > This message is intended for the addressee named above. It may contain<br> > privileged or confidential information. If you are not the intended<br> > recipient of this message you must not use, copy, distribute or disclose it<br> > to anyone other than the addressee. If you have received this message in<br> > error please return the message to the sender by replying to it and then<br> > delete the message from your computer.<br> ><br> ><br> ><br> ><br> ><br> > *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>');>] *On<br> > Behalf Of *Matthew Smee<br> > *Sent:* Thursday, 10 August 2017 12:00 PM<br> > *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>');><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > +1<br> ><br> > Every DC agreement I?ve seen (3) have mentioned that you are responsible<br> > for supplying it with power and they aren?t responsible if it loses power<br> > (i.e. use an ATS).<br> ><br> ><br> ><br> > *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>');>] *On<br> > Behalf Of *Sam Silvester<br> > *Sent:* Thursday, 10 August 2017 10:14 AM<br> > *To:* Shaun McGuane <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>');>><br> > *Cc:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>');><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > If you have single fed equipment in your rack that needs planning before<br> > it can be shut down, do you not run a totally forseeable and preventable<br> > risk then should that one feed trip?<br> ><br> ><br> ><br> > This is what ATS are for.<br> ><br> ><br> ><br> > Sam<br> ><br> ><br> ><br> ><br> ><br> > On Thursday, 10 August 2017, Shaun McGuane <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a><br> > <javascript:_e(%7B%7D,'cvml','<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>');>> wrote:<br> ><br> > HI Simon,<br> ><br> ><br> ><br> > Thank you for your input to the list.<br> ><br> ><br> ><br> > While you may have provided notifications well in advance, your schedule<br> > provided has been changed multiple times and this creates confusion.<br> ><br> > Without asking for further clarification last night I would never have<br> > received the following updated schedule from Craig Armstrong today.<br> ><br> ><br> ><br> > Data Hall 2 ? B feed (west/blue PDU side) Tuesday 15th Aug, A feed has<br> > been pushed back to later date around November, you will receive official<br> > notice once new date confirmed.<br> ><br> > Data Hall 3 ?A and B feed has been pushed back to later date around<br> > October/November, you will receive official notice once new date confirmed.<br> ><br> > Data Hall 4 ?A and B feed has been pushed back to later date around<br> > October/November, you will receive official notice once new date confirmed.<br> ><br> ><br> ><br> > From the latest update today, It appears that most of the works are being<br> > postponed for the time being<br> ><br> ><br> ><br> > Not all devices within racks support 2 feeds and planning is involved with<br> > these devices, which is why it is crucial to receive accurate information<br> > about any pending outages or upgrades<br> > to the NextDC DataCentres which affect services.<br> ><br> ><br> ><br> > Additionally, I have not received these updates via the normal NextDC<br> > E-Mail communication method, so I am sure other customers will be wondering<br> > whats happening too.<br> ><br> ><br> ><br> > Happy to have a conversation offline about this feel free to give me a<br> > call on my mobile.<br> ><br> ><br> ><br> > Regards<br> ><br> > Shaun<br> ><br> ><br> ><br> ><br> ><br> ><br> ><br> > *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] *On Behalf Of *Simon<br> > Cooper<br> > *Sent:* Thursday, 10 August 2017 8:39 AM<br> > *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > Thanks guys, appreciate the feedback.<br> ><br> ><br> ><br> > At NEXTDC we work very hard to keep critical infrastructure maintenance<br> > that impacts racks or the environment within the data hall to an absolute<br> > minimum.<br> ><br> ><br> ><br> > However, some works are required to happen from time to time by law and<br> > one of those activities is a de-energisation and inspection of each of our<br> > major switchboards. This is all about ensuring that the electrical system<br> > is safe, and is an unavoidable piece of work. Rightly so.<br> ><br> ><br> ><br> > Every rack in a NEXTDC data centre has 2N power feeds offered to it, and<br> > we highly recommend that they are used for every device in the rack. This<br> > occasional maintenance is one of the many reasons we provide this<br> > capability. Any device using the 2N supplies (aka A & B feeds) will simply<br> > see its power swing from one feed to the other. Any rack that is drawing<br> > no more that its contracted power level will have no issue when all devices<br> > move from A to B or vice versa.<br> ><br> ><br> ><br> > Our notifications were made well in advance, as we want to give customers<br> > time to consider the management of these works and we don't assume that<br> > every rack is perfectly deployed: We are here 24/7 to assist customers<br> > with rack inspections or specific circuit down tests or maybe a controlled<br> > move prior to the day (e.g. for devices that are single fed).<br> ><br> ><br> ><br> > Also, as we work though those discussions with customers we understand the<br> > timing in relation to their businesses, and we work very hard to coordinate<br> > schedules despite each switch board supporting many different customers and<br> > customer instances across the data centre. Occasionally that means we have<br> > to make a difficult decisions which may result in schedule changes. When<br> > that does happen, we do not compromise our notification periods.<br> ><br> ><br> ><br> > I'll be happy to discuss these works with anyone - probably best offline<br> > or on the phone - but trust me when I say we are doing our absolute best to<br> > keep your data centre operating safely and reliably for many years to come.<br> ><br> ><br> ><br> > Thanks,<br> ><br> > Simon<br> ><br> > COO, NEXTDC<br> ><br> ><br> ><br> > -----Original Message-----<br> > *From:* <a href="mailto:nathan@nightsys.net">nathan@nightsys.net</a><br> > *Sent:* Thu, 10 Aug 2017 05:39:02 +1000<br> > *To:* <a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> > This seems reasonable? As long as no single Data Hall has both A and B<br> > feeds removed simultaneously, that seems normal. Doing B on Hall 2 and A on<br> > Hall 3 on the same day does seem slightly adventurous, but not entirely<br> > unreasonable (mostly in terms of if something goes bad in both, staff get<br> > stretched thin remediating issues).<br> ><br> ><br> ><br> > A and B feeds are designed to provide redundancy to equipment, allowing<br> > one feed to fail and systems to continue on the other. Anything mission<br> > critical should be able to draw from either feed as required (dual PSU),<br> > and if there is a power deficit on one feed (causing circuits to trip),<br> > that would imply the circuits are incorrectly sized?<br> ><br> ><br> ><br> > In addition, anything mission critical with a single power supply would be<br> > on an ATS you would assume, or a pair of equivalent devices installed with<br> > one on each rail?<br> ><br> ><br> ><br> > Things break in datacentres, planned maintenance happens sometimes, better<br> > than no maintenance at all :) The fact they are notifying you is better<br> > than not, and it being scheduled is probably still better than unscheduled<br> > :) (easier to ensure sufficient staffing to keep a close eye on things)<br> ><br> ><br> ><br> > Nathan.<br> ><br> ><br> ><br> > On Wed, Aug 9, 2017 at 3:43 PM, Shaun McGuane <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>><br> > wrote:<br> ><br> > Here is the entire scheduled maintenance windows for all the halls we<br> > occupy.<br> ><br> ><br> ><br> > DataHall 2<br> ><br> > A Feed - Tuesday 8th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> > B Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> ><br> ><br> ><br> > DataHall 3<br> ><br> > A Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10<br> > B Feed - Monday 14th August 2017 07:00 UTC +10 until 16:00 UTC +10<br> ><br> ><br> ><br> > DataHall 4<br> ><br> > B Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> ><br> ><br> ><br> > ? So looks like no power on 3 data halls B feeds on the same day.<br> ><br> > ? Data Hall 2 was scheduled for A rail on the 8th of August but<br> > has been re-scheduled with no new date of works.<br> ><br> > ? Data Hall 3 was scheduled for A rail on the<br> ><br> ><br> ><br> > Problem is that I have 3x separate dates on 3 separate e-mails for Data<br> > Hall 3 and I have requested a revised clarification<br> ><br> > Just now on the above as there has already been re-schedules for Data Hall<br> > 2 and 3.<br> ><br> ><br> ><br> > This feels like it?s going sideways and it has not even started.<br> ><br> ><br> ><br> > Regards<br> ><br> > Shaun<br> ><br> ><br> ><br> ><br> ><br> > *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] *On Behalf Of *Murat<br> > Sener<br> > *Sent:* Wednesday, 9 August 2017 3:20 PM<br> > *To:* Matthew VK3EVL <<a href="mailto:hitman@itglowz.com">hitman@itglowz.com</a>>; <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> ><br> ><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > We have been told only Feed B in Data hall 2 will be effected as per<br> > original schedule and Feed A is yet to be rescheduled.<br> ><br> ><br> ><br> ><br> ><br> ><br> ><br> > *Murat Sener* Datacentre Manager<br> ><br> > *PREMIER* Technology Solutions<br> > *P. *1300 76 76 48 *F. *1300 76 76 49 *M. *0450 604 350<br> ><br> ><br> ><br> > *How am I doing? Let us know!*<br> > SIMPLY CLICK ON A FACE TO GIVE FEEDBACK<br> ><br> > *GREAT*<br> ><br> > *AVERAGE*<br> ><br> > *BAD*<br> ><br> > <<a href="https://protect-au.mimecast.com/s/ZXg4BxUQRobS3?domain=crewhu.com" target="_blank">https://protect-au.mimecast.com/s/ZXg4BxUQRobS3?domain=crewhu.com</a>><br> ><br> > <<a href="https://protect-au.mimecast.com/s/m4kKB9UQ4mAS1?domain=crewhu.com" target="_blank">https://protect-au.mimecast.com/s/m4kKB9UQ4mAS1?domain=crewhu.com</a>><br> ><br> > <<a href="https://protect-au.mimecast.com/s/krZGBXug3DJiw?domain=crewhu.com" target="_blank">https://protect-au.mimecast.com/s/krZGBXug3DJiw?domain=crewhu.com</a>><br> ><br> ><br> ><br> > *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] *On Behalf Of *Matthew<br> > VK3EVL<br> > *Sent:* Wednesday, 9 August 2017 3:13 PM<br> > *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > What about both feeds happening on the same day at the same time?<br> ><br> ><br> ><br> > On 9/08/2017 2:55 PM, Shaun McGuane wrote:<br> ><br> > HI Damien,<br> ><br> ><br> ><br> > My apologies that?s correct ? but isn?t anyone concerned about the works<br> > being completed during business hours?<br> ><br> > What about increased loading of the active rail once one of them is<br> > switched off for these works?<br> ><br> ><br> ><br> > Regards<br> ><br> > Shaun<br> ><br> ><br> ><br> ><br> ><br> > *From:* Damien Gardner Jnr [mailto:<a href="mailto:rendrag@rendrag.net">rendrag@rendrag.net</a>]<br> > *Sent:* Wednesday, 9 August 2017 2:39 PM<br> > *To:* <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>> <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>>; Shaun McGuane<br> > <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>><br> > *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> > 15th August<br> ><br> ><br> ><br> > It says 7am -> 4pm in what you quoted? (UTC+10 is AEST)<br> ><br> ><br> ><br> > On Wed, 9 Aug 2017 at 2:36 pm, Shaun McGuane <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>><br> > wrote:<br> ><br> > HI Noggers,<br> ><br> ><br> ><br> > Has anyone seen this scheduled maintenance notification happening next<br> > week?<br> ><br> > They maybe upgrading feeds or boards throughout the datacentre ? has<br> > everyone seen this notification of works?<br> ><br> > It appears to be happening starting 5PM through to 2AM AEST for all<br> > Datahalls on the same date.<br> ><br> ><br> ><br> ><br> ><br> > *WHAT:*<br> > NEXTDC M1 Melbourne data centre, with the assistance of specialist<br> > contractors, will conduct offline preventative electrical maintenance work<br> > on high-voltage and low-voltage main isolators. This will affect A and B<br> > feeds to the racks in Data Hall 2/3/4 on the 15th of August.<br> ><br> > *WHEN:*<br> > A Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> > B Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> ><br> > *HOW AM I AFFECTED?*<br> > Due to the nature of the work a single feed will be removed as per the<br> > dates and times above. We recommend that customers balance the power<br> > between both power rails to minimise impact during this period. If you have<br> > single feed devices we recommend you:<br> ><br> ><br> ><br> > Regards<br> ><br> > Shaun<br> ><br> ><br> ><br> ><br> ><br> ><br> ><br> > _______________________________________________<br> > AusNOG mailing list<br> > <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> > <<a href="https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net" target="_blank">https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net</a>><br> ><br> > --<br> ><br> > Damien Gardner Jnr<br> > VK2TDG. Dip EE. GradIEAust<br> > <a href="mailto:rendrag@rendrag.net">rendrag@rendrag.net</a> - <a href="http://www.rendrag.net/" target="_blank">http://www.rendrag.net/</a><br> > <<a href="https://protect-au.mimecast.com/s/Ld1wBKUl1AwIG?domain=rendrag.net" target="_blank">https://protect-au.mimecast.com/s/Ld1wBKUl1AwIG?domain=rendrag.net</a>><br> > --<br> > We rode on the winds of the rising storm,<br> > We ran to the sounds of thunder.<br> > We danced among the lightning bolts,<br> > and tore the world asunder<br> ><br> ><br> ><br> > _______________________________________________<br> ><br> > AusNOG mailing list<br> ><br> > <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> ><br> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a> <<a href="https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net" target="_blank">https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net</a>><br> ><br> ><br> ><br> ><br> > MESSAGE PROTECTED BY *PREMIER TECHNOLOGY SOLUTIONS*<br> > <<a href="https://protect-au.mimecast.com/s/GN1YBofq1r8tD?domain=premiertech.com.au" target="_blank">https://protect-au.mimecast.com/s/GN1YBofq1r8tD?domain=premiertech.com.au</a>><br> > - POWERED BY *MAILGUARD*<br> > <<a href="https://protect-au.mimecast.com/s/YZ5qB0uDN27IX?domain=mailguard.com.au" target="_blank">https://protect-au.mimecast.com/s/YZ5qB0uDN27IX?domain=mailguard.com.au</a>>.<br> ><br> > Report this message as spam<br> > <<a href="https://protect-au.mimecast.com/s/K410BnUo1JOHd?domain=console.mailguard.com.au" target="_blank">https://protect-au.mimecast.com/s/K410BnUo1JOHd?domain=console.mailguard.com.au</a>><br> ><br> ><br> ><br> ><br> > MESSAGE PROTECTED BY *PREMIER TECHNOLOGY SOLUTIONS*<br> > <<a href="https://protect-au.mimecast.com/s/GN1YBofq1r8tD?domain=premiertech.com.au" target="_blank">https://protect-au.mimecast.com/s/GN1YBofq1r8tD?domain=premiertech.com.au</a>><br> > - POWERED BY *MAILGUARD*<br> > <<a href="https://protect-au.mimecast.com/s/YZ5qB0uDN27IX?domain=mailguard.com.au" target="_blank">https://protect-au.mimecast.com/s/YZ5qB0uDN27IX?domain=mailguard.com.au</a>>.<br> ><br> ><br> ><br> ><br> > _______________________________________________<br> > AusNOG mailing list<br> > <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> > <<a href="https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net" target="_blank">https://protect-au.mimecast.com/s/pLG0B1fQrxkS1?domain=lists.ausnog.net</a>><br> ><br> ><br> ><br> ><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0001.html" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0001.html</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image012.png<br> Type: image/png<br> Size: 3771 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0008.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0008.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image005.png<br> Type: image/png<br> Size: 1047 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0009.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0009.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image006.png<br> Type: image/png<br> Size: 4219 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0010.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0010.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image009.png<br> Type: image/png<br> Size: 3738 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0011.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0011.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image011.png<br> Type: image/png<br> Size: 4714 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0012.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0012.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image008.png<br> Type: image/png<br> Size: 1246 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0013.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0013.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image007.png<br> Type: image/png<br> Size: 1137 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0014.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0014.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image010.png<br> Type: image/png<br> Size: 3778 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0015.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/c64e2595/attachment-0015.png</a>><br><br> ------------------------------<br><br> Message: 2<br> Date: Thu, 10 Aug 2017 16:11:48 +1000<br> From: Peter Tiggerdine <<a href="mailto:ptiggerdine@gmail.com">ptiggerdine@gmail.com</a>><br> To: Chad Kelly <<a href="mailto:chad@cpkws.com.au">chad@cpkws.com.au</a>><br> Cc: "<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>" <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>>,<br> "<a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>" <<a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>><br> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance<br> -, 15th August<br> Message-ID:<br> <<a href="mailto:CAHgLLqb789cBEYY50QyFjGc1Zr4sWbc3nXkG_AVnsg6uCO_1SA@mail.gmail.com">CAHgLLqb789cBEYY50QyFjGc1Zr4sWbc3nXkG_AVnsg6uCO_1SA@mail.gmail.com</a>><br> Content-Type: text/plain; charset="UTF-8"<br><br> disagree.<br><br> Outside of business hours costs more with limited staff around to<br> assist. They're doing you a favour by doing this because if your PSU<br> fails on server, you'll have time raise tickets with vendor and get<br> same day resolution.<br><br><br> Regards,<br><br> Peter Tiggerdine<br><br> GPG Fingerprint: 2A3F EA19 F6C2 93C1 411D 5AB2 D5A8 E8A8 0E74 6127<br><br><br> On Thu, Aug 10, 2017 at 3:14 PM, Chad Kelly <<a href="mailto:chad@cpkws.com.au">chad@cpkws.com.au</a>> wrote:<br> ><br> > Hmm yes actually deciding to do this during business hours does appear to be<br> > an odd choice, even with two PSU in the server, they would be better off<br> > doing this out of business hours I would of thought.<br> > Regards Chad.<br> ><br> ><br> > On 8/10/2017 2:56 PM, Nathan Brookfield wrote:<br> >><br> >> Chad,<br> >><br> >> That's all well and good but when you're paying a premium price for<br> >> services of this fashion you expect a certain level of service. There is a<br> >> risk no matter what when switching from power supplies taking extra load<br> >> they would not usually take as well as swing load issues with PDU's.<br> >><br> >> I completely agree with your sentiment but the risk is not to be ignored<br> >> especially during those times.<br> >><br> >> Kindest Regards,<br> >> Nathan Brookfield (VK2NAB)<br> >><br> >> -----Original Message-----<br> >> From: AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Chad<br> >> Kelly<br> >> Sent: Thursday, August 10, 2017 2:54 PM<br> >> To: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>; <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a><br> >> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -,<br> >> 15th August<br> >><br> >><br> >><br> >> On 8/10/2017 10:13 AM, <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a> wrote:<br> >>><br> >>> From the latest update today, It appears that most of the works are<br> >>> being postponed for the time being<br> >>><br> >>> Not all devices within racks support 2 feeds and planning is involved<br> >>> with these devices, which is why it is crucial to receive accurate<br> >>> information about any pending outages or upgrades to the NextDC DataCentres<br> >>> which affect services.<br> >><br> >> If these services are mission critical then you really should have duel<br> >> PSU units, so that when one feed gets taken offline the equipment<br> >> automatically switches to the other feed. They won't just disconnect both<br> >> feeds at once because that would be stupid and if the entire DC was offline<br> >> for too much time then that would put the owners in a rather awkward<br> >> situation legally, as after say 8 or 10 hours of downtime it wouldn't be<br> >> good for the owners lets put it that way.<br> >> If the single PSU units are a part of a customers co-located equipment<br> >> then really your terms of service agreement should exclude liability under<br> >> your maintenance clauses.<br> >> I don't understand why anyone would be using single PSU equipment in a DC<br> >> environment now a days when you can buy refurbished servers that come with<br> >> two PSU as standard even when you buy them without raid.<br> >> Also for anything that is really really mission critical you should have<br> >> it hosted in multiple datacentres anyway so if something stupid does happen<br> >> that you can't control you at least still have services online as the load<br> >> balanced services would just switch.<br> >> Regards Chad.<br> >><br> >> --<br> >> Chad Kelly<br> >> Manager<br> >> CPK Web Services<br> >> Phone 03 5273 0246<br> >> Web <a href="http://www.cpkws.com.au" target="_blank">www.cpkws.com.au</a><br> >><br> >> _______________________________________________<br> >> AusNOG mailing list<br> >> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> >> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> ><br> ><br> > --<br> > Chad Kelly<br> > Manager<br> > CPK Web Services<br> > Phone 03 5273 0246<br> > Web <a href="http://www.cpkws.com.au" target="_blank">www.cpkws.com.au</a><br> ><br> > _______________________________________________<br> > AusNOG mailing list<br> > <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br><br><br> ------------------------------<br><br> Message: 3<br> Date: Thu, 10 Aug 2017 16:41:08 +1000<br> From: Chad Kelly <<a href="mailto:chad@cpkws.com.au">chad@cpkws.com.au</a>><br> To: Peter Tiggerdine <<a href="mailto:ptiggerdine@gmail.com">ptiggerdine@gmail.com</a>><br> Cc: "<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>" <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>>,<br> "<a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>" <<a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a>><br> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance<br> -, 15th August<br> Message-ID: <<a href="mailto:945c1e17-7406-e4d3-3340-bee89f4d586b@cpkws.com.au">945c1e17-7406-e4d3-3340-bee89f4d586b@cpkws.com.au</a>><br> Content-Type: text/plain; charset=utf-8; format=flowed<br><br> Yeah bit of a dammed if you do, dammed if you don't type situation.<br><br><br><br> On 8/10/2017 4:11 PM, Peter Tiggerdine wrote:<br> > disagree.<br> ><br> > Outside of business hours costs more with limited staff around to<br> > assist. They're doing you a favour by doing this because if your PSU<br> > fails on server, you'll have time raise tickets with vendor and get<br> > same day resolution.<br> ><br> ><br> > Regards,<br> ><br> > Peter Tiggerdine<br> ><br> > GPG Fingerprint: 2A3F EA19 F6C2 93C1 411D 5AB2 D5A8 E8A8 0E74 6127<br> ><br> ><br> > On Thu, Aug 10, 2017 at 3:14 PM, Chad Kelly <<a href="mailto:chad@cpkws.com.au">chad@cpkws.com.au</a>> wrote:<br> >> Hmm yes actually deciding to do this during business hours does appear to be<br> >> an odd choice, even with two PSU in the server, they would be better off<br> >> doing this out of business hours I would of thought.<br> >> Regards Chad.<br> >><br> >><br> >> On 8/10/2017 2:56 PM, Nathan Brookfield wrote:<br> >>> Chad,<br> >>><br> >>> That's all well and good but when you're paying a premium price for<br> >>> services of this fashion you expect a certain level of service. There is a<br> >>> risk no matter what when switching from power supplies taking extra load<br> >>> they would not usually take as well as swing load issues with PDU's.<br> >>><br> >>> I completely agree with your sentiment but the risk is not to be ignored<br> >>> especially during those times.<br> >>><br> >>> Kindest Regards,<br> >>> Nathan Brookfield (VK2NAB)<br> >>><br> >>> -----Original Message-----<br> >>> From: AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Chad<br> >>> Kelly<br> >>> Sent: Thursday, August 10, 2017 2:54 PM<br> >>> To: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>; <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a><br> >>> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -,<br> >>> 15th August<br> >>><br> >>><br> >>><br> >>> On 8/10/2017 10:13 AM, <a href="mailto:ausnog-request@lists.ausnog.net">ausnog-request@lists.ausnog.net</a> wrote:<br> >>>> From the latest update today, It appears that most of the works are<br> >>>> being postponed for the time being<br> >>>><br> >>>> Not all devices within racks support 2 feeds and planning is involved<br> >>>> with these devices, which is why it is crucial to receive accurate<br> >>>> information about any pending outages or upgrades to the NextDC DataCentres<br> >>>> which affect services.<br> >>> If these services are mission critical then you really should have duel<br> >>> PSU units, so that when one feed gets taken offline the equipment<br> >>> automatically switches to the other feed. They won't just disconnect both<br> >>> feeds at once because that would be stupid and if the entire DC was offline<br> >>> for too much time then that would put the owners in a rather awkward<br> >>> situation legally, as after say 8 or 10 hours of downtime it wouldn't be<br> >>> good for the owners lets put it that way.<br> >>> If the single PSU units are a part of a customers co-located equipment<br> >>> then really your terms of service agreement should exclude liability under<br> >>> your maintenance clauses.<br> >>> I don't understand why anyone would be using single PSU equipment in a DC<br> >>> environment now a days when you can buy refurbished servers that come with<br> >>> two PSU as standard even when you buy them without raid.<br> >>> Also for anything that is really really mission critical you should have<br> >>> it hosted in multiple datacentres anyway so if something stupid does happen<br> >>> that you can't control you at least still have services online as the load<br> >>> balanced services would just switch.<br> >>> Regards Chad.<br> >>><br> >>> --<br> >>> Chad Kelly<br> >>> Manager<br> >>> CPK Web Services<br> >>> Phone 03 5273 0246<br> >>> Web <a href="http://www.cpkws.com.au" target="_blank">www.cpkws.com.au</a><br> >>><br> >>> _______________________________________________<br> >>> AusNOG mailing list<br> >>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> >>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> >><br> >> --<br> >> Chad Kelly<br> >> Manager<br> >> CPK Web Services<br> >> Phone 03 5273 0246<br> >> Web <a href="http://www.cpkws.com.au" target="_blank">www.cpkws.com.au</a><br> >><br> >> _______________________________________________<br> >> AusNOG mailing list<br> >> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> >> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br><br> --<br> Chad Kelly<br> Manager<br> CPK Web Services<br> Phone 03 5273 0246<br> Web <a href="http://www.cpkws.com.au" target="_blank">www.cpkws.com.au</a><br><br><br><br> ------------------------------<br><br> Message: 4<br> Date: Thu, 10 Aug 2017 18:26:45 +1000<br> From: James Hodgkinson <<a href="mailto:yaleman@ricetek.net">yaleman@ricetek.net</a>><br> To: Sam Silvester <<a href="mailto:sam.silvester@gmail.com">sam.silvester@gmail.com</a>>, Jared Hirst<br> <<a href="mailto:jared.hirst@serversaustralia.com.au">jared.hirst@serversaustralia.com.au</a>><br> Cc: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br> Subject: Re: [AusNOG] NextDC Melbourne - Scheduled Power Maintenance -<br> 15th August<br> Message-ID:<br> <<a href="mailto:1502353605.3647578.1068981528.3F4D0403@webmail.messagingengine.com">1502353605.3647578.1068981528.3F4D0403@webmail.messagingengine.com</a>><br> Content-Type: text/plain; charset="utf-8"<br><br> We have a tech on site tomorrow morning in Brisbane to do live works on<br> a major DC panel, they need a look out with a torch, insulating matting<br> and a few other things but it's legal.<br> James<br><br><br> On Thu, 10 Aug 2017, at 16:04, Sam Silvester wrote:<br> > I also am unaware of such a law. Simon, can you advise?<br> ><br> > I'm told in QLD that live works are not permitted, but I am in SA so I<br> > have not really bothered too much to check if that is hearsay or true.><br> > On Thursday, 10 August 2017, Jared Hirst<br> > <<a href="mailto:jared.hirst@serversaustralia.com.au">jared.hirst@serversaustralia.com.au</a>> wrote:>><br> >> Hi Simon,<br> >><br> >> Maybe it could be helpful to the Ausnog list to point us to that law<br> >> you refer too?>><br> >> As I personally have never heard or seen this done in any DC in<br> >> Australia, or the world in the past 15 years I have been housing gear<br> >> in Data Centres.>><br> >> I agree that gear should have 2N, and it doesn?t affect me, but there<br> >> are people that have equipment that have single fed devices, and I<br> >> believe you don?t allow self installed STS devices to be installed? I<br> >> could be wrong.>><br> >> In any case, it would be interesting to see the law the requires you<br> >> to shut down boards.>><br> >> Regards,<br> >><br> >> Jared Hirst<br> >> Servers Australia Pty Ltd<br> >> Phone: <a href="tel:%2B61%202%208115%208801">+61 2 8115 8801</a><br> >> Email: <a href="mailto:jared.hirst@serversaustralia.com.au">jared.hirst@serversaustralia.com.au</a><br> >><br> >> *From:* AusNOG <<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>> on behalf of Simon<br> >> Cooper <<a href="mailto:spgc@inbox.com">spgc@inbox.com</a>> *Sent:* Thursday, August 10, 2017 8:39:13 AM<br> >> *To:* <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a> *Subject:* Re: [AusNOG] NextDC<br> >> Melbourne - Scheduled Power Maintenance - 15th August>><br> >> Thanks guys, appreciate the feedback.<br> >><br> >> At NEXTDC we work very hard to keep critical infrastructure<br> >> maintenance that impacts racks or the environment within the data<br> >> hall to an absolute minimum.>><br> >> However, some works are required to happen from time to time by law<br> >> and one of those activities is a de-energisation and inspection of<br> >> each of our major switchboards. This is all about ensuring that the<br> >> electrical system is safe, and is an unavoidable piece of work.<br> >> Rightly so.>><br> >> Every rack in a NEXTDC data centre has 2N power feeds offered to it,<br> >> and we highly recommend that they are used for every device in the<br> >> rack. This occasional maintenance is one of the many reasons we<br> >> provide this capability. Any device using the 2N supplies (aka A & B<br> >> feeds) will simply see its power swing from one feed to the other.<br> >> Any rack that is drawing no more that its contracted power level will<br> >> have no issue when all devices move from A to B or vice versa.>><br> >> Our notifications were made well in advance, as we want to give<br> >> customers time to consider the management of these works and we don't<br> >> assume that every rack is perfectly deployed: We are here 24/7 to<br> >> assist customers with rack inspections or specific circuit down tests<br> >> or maybe a controlled move prior to the day (e.g. for devices that<br> >> are single fed).>><br> >> Also, as we work though those discussions with customers we<br> >> understand the timing in relation to their businesses, and we work<br> >> very hard to coordinate schedules despite each switch board<br> >> supporting many different customers and customer instances across the<br> >> data centre. Occasionally that means we have to make a difficult<br> >> decisions which may result in schedule changes. When that does<br> >> happen, we do not compromise our notification periods.>><br> >> I'll be happy to discuss these works with anyone - probably best<br> >> offline or on the phone - but trust me when I say we are doing our<br> >> absolute best to keep your data centre operating safely and reliably<br> >> for many years to come.>><br> >> Thanks,<br> >> Simon<br> >> COO, NEXTDC<br> >><br> >>> -----Original Message-----<br> >>> *From:* <a href="mailto:nathan@nightsys.net">nathan@nightsys.net</a><br> >>> *Sent:* Thu, 10 Aug 2017 05:39:02 +1000<br> >>> *To:* <a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a><br> >>> *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power<br> >>> Maintenance - 15th August>>><br> >>> This seems reasonable? As long as no single Data Hall has both A and<br> >>> B feeds removed simultaneously, that seems normal. Doing B on Hall 2<br> >>> and A on Hall 3 on the same day does seem slightly adventurous, but<br> >>> not entirely unreasonable (mostly in terms of if something goes bad<br> >>> in both, staff get stretched thin remediating issues).>>><br> >>> A and B feeds are designed to provide redundancy to equipment,<br> >>> allowing one feed to fail and systems to continue on the other.<br> >>> Anything mission critical should be able to draw from either feed as<br> >>> required (dual PSU), and if there is a power deficit on one feed<br> >>> (causing circuits to trip), that would imply the circuits are<br> >>> incorrectly sized?>>><br> >>> In addition, anything mission critical with a single power supply<br> >>> would be on an ATS you would assume, or a pair of equivalent devices<br> >>> installed with one on each rail?>>><br> >>> Things break in datacentres, planned maintenance happens sometimes,<br> >>> better than no maintenance at all :) The fact they are notifying you<br> >>> is better than not, and it being scheduled is probably still better<br> >>> than unscheduled :) (easier to ensure sufficient staffing to keep a<br> >>> close eye on things)>>><br> >>> Nathan.<br> >>><br> >>> On Wed, Aug 9, 2017 at 3:43 PM, Shaun McGuane<br> >>> <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>> wrote:>>><br> >>>> Here is the entire scheduled maintenance windows for all the halls<br> >>>> we occupy.____>>>> __ __<br><br><br> >>>> DataHall 2____<br><br><br> >>>> A Feed - Tuesday 8th August 2017 07:00 UTC +10 until 16:00 UTC +10.<br> >>>> B Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC<br> >>>> +10.____>>>> __ __<br><br><br> >>>> DataHall 3____<br><br><br> >>>> A Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC +10<br> >>>> B Feed - Monday 14th August 2017 07:00 UTC +10 until 16:00 UTC<br> >>>> +10____>>>> __ __<br><br><br> >>>> DataHall 4____<br><br><br> >>>><br> >>>> B Feed - Tuesday 15th August 2017 07:00 UTC +10 until 16:00 UTC<br> >>>> +10.____>>>> __ __<br><br><br> >>>><br> >>>> __? __So looks like no power on 3 data halls B feeds on the<br> >>>> same day. ____>>>> __? __Data Hall 2 was scheduled for A rail on the 8th of<br> >>>> August but has been re-scheduled with no new date of works.____>>>> __? __Data Hall 3 was scheduled for A rail on the ____<br><br><br> >>>> __ __<br><br><br> >>>> Problem is that I have 3x separate dates on 3 separate e-mails for<br> >>>> Data Hall 3 and I have requested a revised clarification ____>>>> Just now on the above as there has already been re-schedules for<br> >>>> Data Hall 2 and 3.____>>>> __ __<br><br><br> >>>> This feels like it?s going sideways and it has not even<br> >>>> started.____>>>> __ __<br><br><br> >>>> Regards____<br><br><br> >>>> Shaun____<br><br><br> >>>> __ __<br><br><br> >>>> __ __<br><br><br> >>>> *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] *On Behalf<br> >>>> Of *Murat Sener *Sent:* Wednesday, 9 August 2017 3:20 PM *To:*<br> >>>> Matthew VK3EVL <<a href="mailto:hitman@itglowz.com">hitman@itglowz.com</a>>; <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>>>>><br> >>>> *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power<br> >>>> Maintenance - 15th August____>>>><br><br><br> >>>> __ __<br><br><br> >>>> We have been told only Feed B in Data hall 2 will be effected as<br> >>>> per original schedule and Feed A is yet to be rescheduled.____>>>> __ __<br><br><br> >>>> __ __<br><br><br> >>>> __ __<br><br><br> >>>> ____<br><br><br> >>>> *Murat Sener* Datacentre Manager____<br><br><br> >>>> *PREMIER* Technology Solutions *P. *1300 76 76 48 *F. *1300 76<br> >>>> 76 49 *M. *0450 604 350 ____>>>> __ __<br><br><br> >>>> *How am I doing? Let us know!* SIMPLY CLICK ON A FACE TO GIVE<br> >>>> FEEDBACK ____>>>> *GREAT____*<br><br><br> >>>> *AVERAGE____*<br><br><br> >>>> *BAD____*<br><br><br> >>>> ____<br><br><br> >>>> ____<br><br><br> >>>> ____<br><br><br> >>>> __ __<br><br><br> >>>> *From:* AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] *On Behalf<br> >>>> Of *Matthew VK3EVL *Sent:* Wednesday, 9 August 2017 3:13 PM *To:*<br> >>>> <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a> *Subject:* Re: [AusNOG] NextDC Melbourne -<br> >>>> Scheduled Power Maintenance - 15th August____>>>> __ __<br><br><br> >>>> What about both feeds happening on the same day at the same<br> >>>> time?____>>>> __ __<br><br><br> >>>> On 9/08/2017 2:55 PM, Shaun McGuane wrote:____<br><br><br> >>>>> HI Damien,____<br><br><br> >>>>> ____<br><br><br> >>>>> My apologies that?s correct ? but isn?t anyone concerned about the<br> >>>>> works being completed during business hours?____>>>>> What about increased loading of the active rail once one of them<br> >>>>> is switched off for these works?____>>>>> ____<br><br><br> >>>>> Regards____<br><br><br> >>>>> Shaun____<br><br><br> >>>>> ____<br><br><br> >>>>> ____<br><br><br> >>>>> *From:* Damien Gardner Jnr [mailto:<a href="mailto:rendrag@rendrag.net">rendrag@rendrag.net</a>] *Sent:*<br> >>>>> Wednesday, 9 August 2017 2:39 PM *To:* <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>><br> >>>>> <<a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a>>; Shaun McGuane <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>><br> >>>>> *Subject:* Re: [AusNOG] NextDC Melbourne - Scheduled Power<br> >>>>> Maintenance - 15th August____>>>>> ____<br><br><br> >>>>> It says 7am -> 4pm in what you quoted? (UTC+10 is AEST)____<br><br><br> >>>>> ____<br><br><br> >>>>> On Wed, 9 Aug 2017 at 2:36 pm, Shaun McGuane<br> >>>>> <<a href="mailto:shaun@rackcentral.com">shaun@rackcentral.com</a>> wrote:____>>>>>> HI Noggers,____<br><br><br> >>>>>> ____<br><br><br> >>>>>> Has anyone seen this scheduled maintenance notification happening<br> >>>>>> next week?____>>>>>> They maybe upgrading feeds or boards throughout the datacentre ?<br> >>>>>> has everyone seen this notification of works?____>>>>>> It appears to be happening starting 5PM through to 2AM AEST for<br> >>>>>> all Datahalls on the same date.____>>>>>> ____<br><br><br> >>>>>> ____<br><br><br> >>>>>> *WHAT:*<br> >>>>>> NEXTDC M1 Melbourne data centre, with the assistance of<br> >>>>>> specialist contractors, will conduct offline preventative<br> >>>>>> electrical maintenance work on high-voltage and low-voltage main<br> >>>>>> isolators. This will affect A and B feeds to the racks in Data<br> >>>>>> Hall 2/3/4 on the 15th of August.<br> >>>>>><br> >>>>>> *WHEN:* A Feed - Tuesday 15th August 2017 07:00 UTC +10 until<br> >>>>>> 16:00 UTC +10. B Feed - Tuesday 15th August 2017 07:00 UTC +10<br> >>>>>> until 16:00 UTC +10.>>>>>><br> >>>>>> *HOW AM I AFFECTED?* Due to the nature of the work a single feed<br> >>>>>> will be removed as per the dates and times above. We recommend<br> >>>>>> that customers balance the power between both power rails to<br> >>>>>> minimise impact during this period. If you have single feed<br> >>>>>> devices we recommend you:____>>>>>> ____<br><br><br> >>>>>> Regards____<br><br><br> >>>>>> Shaun____<br><br><br> >>>>>> ____<br><br><br> >>>>>> ____<br><br><br> >>>>>> ____<br><br><br> >>>>>> _______________________________________________<br> >>>>>> AusNOG mailing list<br> >>>>>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> >>>>>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog____" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog____</a><br><br><br> >>>>> -- ____<br><br><br> >>>>> Damien Gardner Jnr<br> >>>>> VK2TDG. Dip EE. GradIEAust<br> >>>>> <a href="mailto:rendrag@rendrag.net">rendrag@rendrag.net</a> - <a href="http://www.rendrag.net/_" target="_blank">http://www.rendrag.net/_</a><br> _--<br> >>>>> We rode on the winds of the rising storm,<br> >>>>> We ran to the sounds of thunder.<br> >>>>> We danced among the lightning bolts,<br> >>>>> and tore the world asunder____<br><br><br> >>>>><br> >>>>> ____<br><br><br> >>>>> ___________________________________________________<br> >>>>> AusNOG mailing list____ <a href="mailto:AusNOG@lists.ausnog.net____">AusNOG@lists.ausnog.net____</a><br> >>>>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog____" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog____</a>>>>> __ __<br><br><br> >>>><br> >>>> MESSAGE PROTECTED BY *PREMIER TECHNOLOGY SOLUTIONS*[1] - POWERED<br> >>>> BY *MAILGUARD*[2]. Report this message as spam[3]<br> >>>> ____>>>><br> >>>> MESSAGE PROTECTED BY *PREMIER TECHNOLOGY SOLUTIONS*[4] - POWERED<br> >>>> BY *MAILGUARD*[5].<br> >>>> ____>>>><br> >>>> _______________________________________________<br> >>>> AusNOG mailing list<br> >>>> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> >>>> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br> >>>><br> > _________________________________________________<br> > AusNOG mailing list<br> > <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> > <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br><br><br> Links:<br><br> 1. <a href="http://www.premiertech.com.au" target="_blank">http://www.premiertech.com.au</a><br> 2. <a href="http://www.mailguard.com.au/mg" target="_blank">http://www.mailguard.com.au/mg</a><br> 3. <a href="https://console.mailguard.com.au/ras/1RqQHQIE5J/6DWUZjiMDnlts7JYyCLNB3/0" target="_blank">https://console.mailguard.com.au/ras/1RqQHQIE5J/6DWUZjiMDnlts7JYyCLNB3/0</a><br> 4. <a href="http://www.premiertech.com.au" target="_blank">http://www.premiertech.com.au</a><br> 5. <a href="http://www.mailguard.com.au/mg" target="_blank">http://www.mailguard.com.au/mg</a><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment.html" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment.html</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image001.png<br> Type: image/png<br> Size: 3738 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image002.png<br> Type: image/png<br> Size: 3778 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0001.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0001.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image003.png<br> Type: image/png<br> Size: 4714 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0002.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0002.png</a>><br> -------------- next part --------------<br> A non-text attachment was scrubbed...<br> Name: image004.png<br> Type: image/png<br> Size: 3771 bytes<br> Desc: not available<br> URL: <<a href="http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0003.png" target="_blank">http://lists.ausnog.net/pipermail/ausnog/attachments/20170810/7eff6cb5/attachment-0003.png</a>><br><br> ------------------------------<br><br> Subject: Digest Footer<br><br> _______________________________________________<br> AusNOG mailing list<br> <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br> <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br><br><br> ------------------------------<br><br> End of AusNOG Digest, Vol 66, Issue 14<br> **************************************<br><br><br><br><br><br>_______________________________________________<br>AusNOG mailing list<br><a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br><a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a></p></blockquote></div><p class="MsoNormal"> </p></div></div></div></body></html>