Difference between revisions of "Information Systems:Wired Network (LAN) Infrastructure Redesign"
Jump to navigation
Jump to search
m |
m (→Spanning Tree) |
||
| Line 18: | Line 18: | ||
=Spanning Tree= |
=Spanning Tree= |
||
| + | A spanning tree topology should be implemented to provide redundancy during a switch failure and to prevent broadcast storms from mis-plugging of ports. |
||
| + | |||
| + | Root bridges will be the server room switches. |
||
[[Category: Networking]] |
[[Category: Networking]] |
||
Revision as of 11:58, 15 July 2016
VLANs
The entire uniPHARM network is currently a single, very large broadcast domain. It is of utmost priority upon the purchase of new switches to segment the LAN into VLANs. Here are the proposed VLANs:
- VLAN 1 - Management VLAN, no devices
- VLAN 10 - Corporate LAN - desktops, printers/print servers, RF guns, outbound NAT through Telus, Terago
- VLAN 20 - Storage LAN (for SAN iSCSI traffic), separate L3 domain, no default gateway, no outbound internet access
- VLAN 21 - Backup traffic
- VLAN 30 - Guest VLAN, outbound NAT through Telus, Terago, no access to corporate intranet
- VLAN 50 - Telus Corporate WAN, /27 (Superman WAN, Bart (public), Mail (public), Infoblox)
- VLAN 51 - Terago Corporate WAN, /29 (Superman WAN, Bart (public), Mail (public), Infoblox)
- VLAN 60 - DHL/Loomis LAN
It is important to note that routing will be needed to route traffic between some of our VLANs.
Spanning Tree
A spanning tree topology should be implemented to provide redundancy during a switch failure and to prevent broadcast storms from mis-plugging of ports.
Root bridges will be the server room switches.