Design Review Template - NETS

More documents

Recommendations

Info

Long Term: AS-Proposed Design This section will detail a design proposal from the AS team. The following design is hierarchical, redundant, and modular. If fully implemented, the design presents a solution where each of the campuses is totally independent from the other from a traffic and fail-over point of views. Mesa/Marshall Fleischman Jeffco Server Farm POTS/WAN 10/100/1000 L3 GEC MESA Si Si Foot Hills Gigabit Core Center Green Si Si Si Si FootHills/Pearl Street/UNAVCO Semi-Fully Meshed Core design A link or Switch failure at any of the buildings will not affect any other building. The design is also optimised for IP Telephony and Multicast and any QoS strategy needed for any technology or application. The above diagram provides an idea of the final design; a phased migration is provided later. The proposed design offers the following advantages and common features: At the Access Layer: - Switches would have unique VLANs (one or several that exist only on that switch). This in return eliminates dependency on Spanning Tree Protocol for convergence. NCAR Design Review and Recommendations v1.2 14
Hierarchical (MultiLayer) Network Design - User ports to be configured with PortFast (See best practices section below) - ISL or dot1Q trunks to the Distribution layer. Allow only Access Layer VLANs on the trunk. - The ability to load-balance traffic over the Access-Distribution trunks. (This is done using HSRP). If VLANs span multiple switches or buildings, then we can achieve load balancing using STP by alternating “Root” configuration between Distribution Switches. - If STP is the choice for redundancy, the UplinkFast feature is utilized to offer almost instantaneous fail-over of uplinks. At the Distribution Layer: - Two Distribution switches per building to provide maximum redundancy and performance. The two distribution switches are also directly connected to the Core using L3 connections. - Terminate and limit the size of broadcast domains. With unique VLANs configured at the Access switches, the link between the two Distribution in every building can be an L3 connections. - A failure in one of the closets will only be limited to that closet. - Configure HSRP with alternating priority levels between the two Distribution-MSFCs to provide redundancy as well as load balancing of the Uplinks. - Easy to manage and troubleshoot - Root bridges are local and known. No Root is across the WAN links. At the Core Layer: - Layer 3 Core - Highly redundant - Simple Design - Point-to-Point L3 connections NCAR Design Review and Recommendations v1.0 15
Page 1 and 2: Cisco Systems Advanced Services Nat
Page 3 and 4: Contents Contents 3 Document Contro
Page 5 and 6: About The Document Document Purpose
Page 7 and 8: About The Document and Foothills. A
Page 9 and 10: Short Term Design Enhancements Foot
Page 11 and 12: Hierarchical (MultiLayer) Network D
Page 13: Hierarchical (MultiLayer) Network D
Page 23: Corporate Headquarters Cisco System

Design Review Template - NETS

Create successful ePaper yourself

Delete template?

Save as template?