[AusNOG] Switch installation in data centre racks - front facing, or rear facing?

Paul Wilkins paulwilkins369 at gmail.com
Thu Oct 5 14:54:19 EST 2017


Just so. If you care about configuration control and change management,
you'll be using structured cabling with access from the front of the rack.
You really don't need to be fiddling around in the back of a rack,
wondering about which port goes where.

Kind regards

Paul Wilkins

On 4 October 2017 at 16:51, Sam Silvester <sam.silvester at gmail.com> wrote:

> I _think_ I am starting to understand what you are on about:
>
> On Wed, Oct 4, 2017 at 3:36 PM, Paul Wilkins <paulwilkins369 at gmail.com>
> wrote:
>
>> Sam,
>> In an SP environment, you may well have whole rows dedicated to a single
>> service - email, or web say. In the rack itself, you'll have web_node_5007,
>> web_node_5008 etc.
>>
>
> Are you saying that in a given rack you don't care that web_node_5007 went
> into port 1 and web_node_5008 into port 2 before you replace the faulty
> switch, whilst afterwards if they are arse-about because you can just throw
> any ol server into any ol port (same firewall zone/VLAN/whatever)? Hence,
> easier compared to this:
>
>
>> In the enterprise, you'll have a few email blades, internal web, external
>> web, next to a bunch of file and print etc etc etc. These then likely are
>> all on different firewall interfaces/firewalls in different zones requiring
>> different routing and security.
>>
>
> In which case you have to carefully make sure each cable goes back in the
> same port it came out of, as when the config to the replacement switch is
> pushed down it'll all obviously not work great if you've mixed it up from
> where it was.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20171005/f3d2ae7c/attachment.html>


More information about the AusNOG mailing list