<HTML xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<HEAD><!-- Template generated by Exclaimer Mail Disclaimers on 05:34:44 Thursday, 5 October 2017 -->
<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:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@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:11.0pt;
font-family:"Calibri",sans-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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</HEAD>
<BODY bgcolor="white" lang="EN-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose"><span style=mso-fareast-language:EN-US>This. We try to keep all the ports on the same side of the rack – (most?) network gear has the ports on the front, servers have the ports on the back – but make sure you
don’t get the airflow backwards. Switches don’t like it when they are sucking air from the hot aisle (or so I hear …)<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style=mso-bookmark:_MailEndCompose><span style=mso-fareast-language:EN-US><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style=mso-bookmark:_MailEndCompose><span style=mso-fareast-language:EN-US>--<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style=mso-bookmark:_MailEndCompose><span style=mso-fareast-language:EN-US>Chris Ford<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style=mso-bookmark:_MailEndCompose><span style=mso-fareast-language:EN-US>Inabox Group<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style=mso-bookmark:_MailEndCompose><span style=mso-fareast-language:EN-US><o:p> </o:p></span></span></p>
<span style=mso-bookmark:_MailEndCompose></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> AusNOG [mailto:ausnog-bounces@lists.ausnog.net]
<b>On Behalf Of </b>David Hooton<br/>
<b>Sent:</b> Wednesday, 4 October 2017 12:55 PM<br/>
<b>To:</b> ausnog@lists.ausnog.net<br/>
<b>Subject:</b> Re: [AusNOG] Switch installation in data centre racks - front facing, or rear facing?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">> On 3/10/17, 10:34 pm, "AusNOG on behalf of Ken Wilson" <<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a> on behalf of
<a href="mailto:ken.wilson@opengear.com">ken.wilson@opengear.com</a>> wrote:<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style=margin-bottom:12.0pt><span lang="EN-GB">> Tagging onto this - does the same go for your out-of-band equipment? (those that have it)<br/>
><o:p></o:p></span></p>
<p class="MsoNormal" style=margin-bottom:12.0pt><span lang="EN-GB">Yes absolutely, as Nick has mentioned for his IPMI switches we generally use rear facing OOB everywhere. Most servers and other non networking equipment generally put their network ports on
the back of their devices, it just makes sense to keep network patching all on one side of the rack so we don’t have cables running from front to rear. I am surprised how many vendors still don’t offer rear to front airflow boxes.<o:p></o:p></span></p>
<p class="MsoNormal" style=margin-bottom:12.0pt><span lang="EN-GB">DJH<o:p></o:p></span></p>
</div>
</BODY>
</HTML>