Information Systems:Network redesign implementation

Overview

This page is a scratchpad for the re-design of the network, to be done March 3, 2017.

Notes

• 4 x 3870 switches in a stack will serve as the network core. 5th switch to be put in the rack pending another cable, but perhaps shouldn't be stacked anyway (unnecessary overhead for master stacking unit, and we do not need the ports).

• Multi-switch LAG / cross-stack LAG for some of the LAGs, where applicable and where necessary. For example, for a LAG from a server to the stack, each of the two cables coming from the server will be connected to a different switch in the stack.

• VLANs:

• 1 - Main LAN, default VLAN for all ports = untagged
• 2 - uniPHARM WAN traffic, all ports untagged, switched-only/not routed
• 3 - Guest VLAN, tagged on access point ports
• 4 - Loomis Intranet, routed through Sophos Interface, tagged on trunk to Narc cage
• 5 - vMotion traffic

• Stacking preference: Units in a stack will enter master election mode by default. We can influence the election to select a particular master unit by staggering on the power times, but perhaps the best would be to order them by lowest to highest MAC address, which is the ultimate criterion for a master.

• Stacking mode: All switches must be of the same firmware level to enter normal stacking mode. Otherwise, stack will enter special stacking mode, which sounds desirable but actually appears to be a non-functional state whereby only the master unit is up (and thereby indicating