This low level design is used as a base as to how the fixed network was developed and implemented. The SlideShare family just got bigger. Home Explore Login Signup. Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. Next SlideShares. You are reading a preview. Create your free account to continue reading. Sign Up. Upcoming SlideShare. Presentation LLD Embed Size px.
Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Download Now Download Download to read offline. Sample lld document v1. Tom Mark Giembicki Follow. Hld and lld. A University Network Design Exercise. HLD Training Course ppt Design of a campus network. Hld lld. High Level Solution Design v1 0. Network Proposal Power Point. Related Books Free with a 30 day trial from Scribd. Uncommon Carriers John McPhee.
The Art of War Sun Tsu. Related Audiobooks Free with a 30 day trial from Scribd. Elizabeth Howell. Shelley Ocampo , Did u try to use external powers for studying? They helped me a lot once. Nicholas Miller. Ajay Singh Kaintura. Naj Naushahi. Show More. Views Total views. Actions Shares. No notes for slide. All rights reserved. This document will cover the core network and the DC environment only specifically the Nexus environment, all other components of the network infrastructure are out of scope.
This low level design will be used for a definitive reference and a base as to how the fixed network will be developed and implemented. The information in this document is conveyed with the assumption that engineers possess CCNP or equivalent knowledge of network protocols and design fundamentals.
Page 4 of 32 5. These obligations shall not apply to information that is published or becomes known legitimately from some source other than Resolution Data Ltd 6. The existing Chassis are at full capacity, out of support and are creating bottlenecks on the corporate network. Resolution have been given the task to design and migrate to a new core network which will meet the growing demands of their user base and business requirements over the next 5 years.
The Core and DC environment will undergo a technology refresh as per this document. The Access Layer, WAN and additional network services refresh such as load balancers and firewalls are out of scope in this design. The design will cover methods of connectivity for these services only.
Approach Due to the risk involved, the new infrastructure will be implemented in two phases: Phase 1: The initial phase will look to replace the existing core Catalyst switch as this is deemed the most critical device to the enterprise infrastructure, the new equipment being installed will be integrated with the existing server estate environment consisting of a Cisco UCS chassis.
These will be configured as a vPC pair and will make links to the newly installed core switches and the Fabric Interconnect FI switches for the server estate. These platforms will provide connectivity for devices that span from the core to the server aggregation layers within the network. The platform selection will offer CUSTOMER the scalability for the long term, superior functionality, and high levels of resilience on purpose built infrastructure that will exhibit extremely low convergence times around link and node failures, as well as higher throughput speeds of 10Gbps utilizing the VSS and vPC technologies.
A FlexPod will be deployed for the server estate. The FlexPod architecture can scale up or out and it can be optimized for a variety of mixed workloads, in both virtualized and non-virtualized environments.
This will be hosting the entire core and DC infrastructure. The network infrastructure will utilize a tiered model providing core, server aggregation and server access. Note: The FlexPod implementation is considered as part of the overall design; however the UCS and Netapp unified storage components are considered out of scope. The network hardware in the new design is as follows: 2. The VSS section is a primer for the new core aggregation technologies that are leveraged heavily in the design which should be understood from a concept and configuration standpoint before moving further through the document.
Common configurations are grouped to save duplication, and explain the best practice configurations for Layer 2 and Layer 3 protocols which should be kept standard across all areas throughout the design. The next sections will detail each sites physical and logical design for that particular network layer. This includes hostnames, IP addressing, device types etc. Page 10 of 32 2.
Page 11 of 32 3 Cisco Hardware 3. With support for VSS the platform provides a single point of management whilst offering up to 1.
Within the new design the two Catalyst X will provide the core infrastructure utilizing a VSS design. Page 12 of 32 3. To maintain proper air circulation through the switch chassis, it is recommended that you maintain a minimum 6-inch 15 cm separation between a wall and the chassis hot air exhaust 3. Two power supplies will be used for each chassis for full redundancy.
Each active PSU requires two power feeds that should be rated not greater than 20A. Feed receptacles should be within 3. Power Recommendations Each power supply should be connected to separate input sources; otherwise the chassis could be susceptible to a power failure 3. This will ensure that the system fans do not need to work excessively to cool the system. The air flow design of the X chassis is front-to-back for the power which suits hot isle cold isle data centres.
This will also allow support for VSS which is required as per the design 3. Shown below is the weight of each switch. Each technology shown in the following sections includes configuration examples that are based on Cisco best practices which should be adhered to throughout the network design unless otherwise stated.
This information will not be mentioned again so it should be known that where remaining parts of the document mentions a technology which is mentioned in this section , the configuration will be more or less the same. The VSS manages the redundant links, which externally act as a single port channel. The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbours and by providing a loop-free Layer 2 topology.
The virtual switch domain is a number between 1 and , and must be unique for each VSS in your network the domain number is incorporated into various identifiers to ensure that these identifiers are unique across the network. Within the VSS, you must configure one switch to be switch number 1 and the other switch to be switch number 2.
To configure the virtual switch domain and switch number on both switches, perform these tasks: Config Example Switch-1 config switch virtual domain Switch-1 config-vs-domain switch 1 Switch-2 config switch virtual domain Switch-2 config-vs-domain switch 2 Page 15 of 32 5. This link is forms a port-channel that is used to pass data and control traffic between the two switches within the domain. To configure the virtual switch link on both switches, perform these tasks:.
Fast Hellos will be configured across the VSS pair to support the dual active failure protection. To convert from a single switch to a VSS on both switches, perform these tasks: Config Example Switch-1 switch convert mode virtual Switch-2 switch convert mode virtual Note After you confirm the command by entering yes at the prompt , the running configuration is automatically saved as the startup configuration and the switch reboots.
When switches are being converted to VSS, you should not set them to ignore startup-config. If done, the switch can be enabled to parse the startup-config at the rommon prompt. Ignoring startup-config in VSS mode, causes a switch to boot in a semi-VSS mode, which can only be corrected by a reboot and by enabling the parsing of startup-config. In the event of a VSL link failure, the VSS system will shut down all ports connected to the operation primary switch.
If the switch that is deemed primary has orphan port connections, then these ports will be shutdown causing a loss of service to these devices. The VSL link failure is a rare scenario, but should be protected against and all devices should be dual homed across each of the VSS member switches. The desired design is to have no orphan ports connected to the VSS domain. Page 16 of 32 5. The downstream device can be a switch, a server, or any other networking device that supports IEEE Benefits of vPC are device level redundancy with faster convergence than using spanning tree, elimination of blocked ports which promotes a loop-free topology, and much better bandwidth utilisation.
Of the vPC peers one is primary and the other is secondary. The system formed by Switch 1 and Switch 2 is referred to as a vPC domain. This is a standard An out-of-band link is used to resolve dual-active scenarios where the peer-link connectivity is lost.
This link is referred to as vPC peer-keepalive or fault-tolerant link. Some devices can be single-attached to the topology, like server 1 and server 3. The ports connecting devices in a non-vPC mode to a vPC topology are called orphaned ports. Design considerations often surround these types of ports — as its extremely important for the design. Page 17 of 32 5.
The lower number in a vPC priority is more preferred — Generally this is should be aligned with the spanning-tree priorities in the topology for ease of management. While mismatched Spanning-Tree and vPC priorities do not any impact on traffic forwarding under normal conditions, it is desirable to keep the priorities matched so as to have Spanning-Tree root and vPC primary on the same device and Spanning-Tree secondary root and vPC secondary on the same device.
For the two switches vPC peers to form a vPC system, the domain-id of these switches need to match. Shown below is the configuration to create and set the vPC domain, and set the matching STP priorities: N5K-1 config feature vpc N5K-1 config vpc domain 1 N5K-1 config-vpc-domain role priority N5K-2 config feature vpc N5K-2 config vpc domain 1 N5K-2 config-vpc-domain role priority It should also be noted that the vPC role is not preemptive, so a device may be operationally primary but secondary from a configuration perspective.
This is not an issue. The keepalive that resolves dual-active scenarios should never be carried as a VLAN on the peer link. Not sure what these mean and when to use which one? Read on. It includes the description of the following parts:. All the data flows, flowcharts, data structures, etc.
Low-Level Design LLD is a component-level design process that follows a step-by-step refinement process. It provides the details and definitions for the actual logic for every system component. It is based on HLD but digs deeper, going into the separate modules and features for every program in order to document their specifications. Detailed Level Design DLD is the most detailed technical document, which describes user stories, error processing algorithms, state transitions, logical sequences, and others.
DLD describes the interaction of every low-level process with each other.
0コメント