High Availability Design

Slides:



Advertisements
Similar presentations
CCNA3 v3 Module 7 v3 CCNA 3 Module 7 JEOPARDY K. Martin.
Advertisements

Campus Networking Workshop
Q11: Describe how the effects of power supply failures on integrated luminosity will be mitigated. TESLA Response : –Mainly consider two types of magnet.
LAN solutions. 4 Reasons to buy Nortel Networks LANs Provides Business continuity with no single point of failure at the hardware level and faster recovery.
Hi High Availability Design Ram Dantu Slides are adopted from various sources from Cisco and Interwork Inc.,
1 © 2001, Cisco Systems, Inc. IOS Update for SwiNOG 4th Chris Martin Systems Engineer Cisco Switzerland Chris Martin Systems Engineer Cisco Switzerland.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 5: Inter-VLAN Routing Routing & Switching.
1 13-Jun-15 S Ward Abingdon and Witney College LAN design CCNA Exploration Semester 3 Chapter 1.
Modern Distributed Systems Design – Security and High Availability 1.Measuring Availability 2.Highly Available Data Management 3.Redundant System Design.
Network Management 1 School of Business Eastern Illinois University © Abdou Illia, Fall 2006 (Week 16, Tuesday 12/5/2006)
Implementing a Highly Available Network
CCNA 5.0 Planning Guide Chapter 1: Introduction to Scaling Networks.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialBSCI Configuring EIGRP BSCI Module 2-1 – Introduction to EIGRP.
Network Management 1 School of Business Eastern Illinois University © Abdou Illia, Spring 2006 (Week 15, Friday 4/21/2006) (Week 16, Monday 4/24/2006)
© 2009 Cisco Systems, Inc. All rights reserved. SWITCH v1.0—5-1 Implementing a Highly Available Network Understanding High Availability.
Designing Network Topology Week 4. Network Topology Cisco has developed several models to help network designers conceptualize Some of the models we will.
The Network Works 800_105/c _015/c12 Current LAN Technologies 10/100Mbs to the desktop 100Mbs or 1000Mbs to servers Wireless LAN Gigabit between.
Slide 1 Availability Management. Slide 2 Goal – Primary Objective To optimise the capability of the IT infrastructure and supporting organisations to.
Chapter 1: Hierarchical Network Design
LECTURE 9 CT1303 LAN. LAN DEVICES Network: Nodes: Service units: PC Interface processing Modules: it doesn’t generate data, but just it process it and.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.1 Module 7 Spanning Tree Protocol.
Reliable Routing for the Internet Avici Company Confidential Scott Poretsky Avici Systems, Inc. June 3, 2002 Core Router Testing for High Availability.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 7 Spanning-Tree Protocol Cisco Networking Academy.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Implement Spanning Tree Protocols LAN Switching and Wireless – Chapter 5.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Implement Spanning Tree Protocols LAN Switching and Wireless – Chapter 5.
Chapter 2: Non functional Attributes.  It infrastructure provides services to applications  Many of these services can be defined as functions such.
1111 Reliable Network/Service Infrastructures. 222 Availability, Reliability and Survivability AvailabilityReliabilitySurvivability The expected ratio.
BZUPAGES.COM Introduction to Cisco Devices Interfaces and modules –LAN interfaces (Fast Ethernet, Gigabit Ethernet) –WAN interfaces(Basic Rate Interface.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Introducing Network Design Concepts Designing and Supporting Computer Networks.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 1: Introduction to Scaling Networks Scaling Networks.
© Wiley Inc All Rights Reserved. CCNA: Cisco Certified Network Associate Study Guide CHAPTER 7: Layer 2 Switching.
Manufacturing Reliability – What Is It and Why Should I Care Aron Brall, CRE SRS Technologies.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 7 Spanning Tree Protocol.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNP 1 v3.0 Module 1 Overview of Scalable Internetworks.
Network design Topic 4 LAN design. Agenda Modular design Hierarchal model Campus network design Design considerations Switch features.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 7 Spanning Tree Protocol.
1 Version 3.0 Module 7 Spanning Tree Protocol. 2 Version 3.0 Redundancy Redundancy in a network is needed in case there is loss of connectivity in one.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Switching in an Enterprise Network Introducing Routing and Switching in the.
BZUPAGES.COM Introduction to Cisco Devices Interfaces and modules –LAN interfaces (Fast Ethernet, Gigabit Ethernet) –WAN interfaces(Basic Rate Interface.
Rehab AlFallaj.  Network:  Nodes: Service units: PC Interface processing Modules: it doesn’t generate data, but just it process it and do specific task.
Copyright 2003 CCNA 3 Chapter 8 Spanning Tree Protocol By Your Name.
1 LAN switching and Bridges Relates to Lab Outline Interconnection devices Bridges/LAN switches vs. Routers Bridges Learning Bridges Transparent.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 1: Hierarchical Network Design Connecting Networks.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 LAN Design Chapter One.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Troubleshooting an Enterprise Network Introducing Routing and Switching in.
Lecture 11. Switch Hardware Nowadays switches are very high performance computers with high hardware specifications Switches usually consist of a chassis.
Routing and Routing Protocols CCNA 2 v3 – Module 6.
CCNP SWITCH: Implementing Cisco IP Switched Networks
Implement Spanning Tree Protocols
Exams hints The exam will cover the same topics covered in homework. If there was no homework problem on the topic, then there will not be any exam question.
© 2002, Cisco Systems, Inc. All rights reserved.
Campus Communications Fabric
MPE-PE Section Meeting
Characteristics of Systems
Designing Cisco Network Service Architectures Cisco /cisco-question-answers.html.
Implement Spanning Tree Protocols
Chapter 5: Inter-VLAN Routing
Chapter 11 Network Management.
CT1303 LAN Rehab AlFallaj.
CCNA 2 v3.1 Module 6 Routing and Routing Protocols
One Upon A Time Computer Networks
Implement Spanning Tree Protocols
© 2002, Cisco Systems, Inc. All rights reserved.
2018 Real Huawei H Exam Questions Killtest
Availability of IP/MPLS networks
High Availability Design
Implement Spanning Tree Protocols
© 2002, Cisco Systems, Inc. All rights reserved.
Presentation transcript:

High Availability Design Ram Dantu Hi Slides are adopted from various sources from Cisco and Interwork Inc.,

Agenda Definitions Concepts / Calculations Examples Challenges

Availability as a percentage 1 year = 525960 minutes Availability Unscheduled downtime per year 99% 3 days 15 hours 36 minutes 99.9% 8 hours 45 min. 99.99% 52 min. 36 sec. 99.999% 5 min. 15 sec. 99.9999% 32 sec.

Getting downtime from availability 1 year = 525,960 minutes Uptime = availability * Time Annual Uptime = Availability * 525,960 Annual Downtime = 525,960 – Annual Uptime --------------------------------------------------------- Availability = 0.9999 Annual Uptime = .9999 * 525,960 Annual Uptime = 525,907.4 Annual Downtime = 525,960 – 525,907.4 = 52.596 ----------------------------------------------------------- Downtime = (1-Availability) * Time

Availability vs. Reliability Availability = users’ perception Reliability = individual component failures Reliability impacts maintenance costs but doesn’t necessarily have to impact availability

Defects Per Million Availability DPM 99% 10000 99.9% 1000 99.99% 100 99.999% 10 99.9999% 1

Calculating Availability MTBF MTBF + MTTR Example: 6500 Chassis MTBF = 369897 hours (about 42 years) MTTR = 4 hours Availability = 369897 / ( 369897 + 4 ) = 369897 / 369901 = 0.9999892 = 99.99892%

6500 Availability Module Availability Chassis 99.99892% Power Supplies 99.99873% Supervisor - including software 99.99516% GBIC Line Card 99.99577% GBIC 99.99907% 10/100 Line Card

Availability Formulas Serial availability Availability = AvailA × AvailB × AvailC = 99.999% × 99.999% × 99.999% = 99.997% A C B 99.999%

Availability Formulas 99.9% B A Parallel availability Availability = 1 – ((1 – AvailA) × (1 – AvailB)) = 1 – ((1 – 99.9%) × (1 – 99.9%)) = 99.9999%

Availability Formulas Parallel-series availability 99.9% B A D C F E   99.9999% 99.9999% 99.9999% = 99.9997%

Availability Formulas Series-parallel availability 99.9% B A D C F E 99.7% = 1 – ((1 – 99.7%) × (1 – 99.7%)) = 99.9991%

Core Distribution Access

One Core / Distribution 6500 Chassis 99.99892% Dual power 99.99999% Supervisor + software 99.99516% Dual GBIC Line Cards Dual GBICs Single switch availability 99.99405%

Pair of Core / Distribution 6500’s Series-Parallel Availability 99.99405% series availability each Two switches in parallel 1 – ((1 – 99.99405%) × (1 – 99.99405%)) = 99.999999%

Access Layer 6500 Chassis 99.99892% Dual power 99.99999% Dual Supervisors Dual GBIC Line Cards Dual GBICs 10/100 Line Card 99.99577% Switch availability 99.99888% Access port availability 99.99465%

Challenges Improving availability at the access layer “NIC Teaming” in servers Reduce MTTR MTBF = 369897 hours Availability with MTTR of 4 hours = 99.99892% Availability with MTTR of 2 hours = 99.99945%

Challenges Long convergence times Spanning tree Eliminate layer-2 links where possible Avoid layer-2 loops Use STP enhancements where appropriate Routing protocols Use a link-state (or EIGRP) routing protocol Use routing convergence enhancements Minimize routing table sizes Limit convergence scope