1 / 11

Reliable Network/Service Infrastructures

Reliable Network/Service Infrastructures. 1. Availability, Reliability and Survivability. What Is “High Availability”?.

arlais
Download Presentation

Reliable Network/Service Infrastructures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reliable Network/Service Infrastructures 1

  2. Availability, Reliability and Survivability

  3. What Is “High Availability”? • The ability to define, achieve, and sustain “target availability objectives” across services and/or technologies supported in the network that align with the objectives of the business(i.e. 99.9%, 99.99%, 99.999%)

  4. Leading Causes of Downtime • Change management • Process consistency • Communications • Links • Hardware Failure • Design • Environmental issues • Natural disasters Telco/ISP35% Power Failure14% Hardware Failure 12% Human Error 31% Unresolved 8% SOURCE: Graph Data: The Yankee Group, The Road to a Five Nines Network, Feb 2004.

  5. THIS Is Better Than… Enterprise THIS, which Is Better Than… Service Provider Network Enterprise But what is beyond this??? THIS Enterprise Link/Circuit Diversity

  6. Network Point of Presence/Data Center • Cable management • Power: Diversity/UPS • HVAC • Hardware placement • Physical security • Labeling • Environmental control systems 6 6 6

  7. Network Design Network Complexity Technology Can Increase MTBF People, Process, and Politics Can Increase Complexity THIS DECREASES MTBF and Increases MTTR

  8. Network Design Primary Design Considerations • Hierarchical • Modular and consistent • Scalable • Manageable • Reduced failure • Domain (Layer II/III) • Interoperability • Performance • Availability • Security

  9. Examples of Hardware Reliability(Reliability Block Diagrams) Hardware Reliability = 99.938% with 4 Hour MTTR (325 Minutes/Year) Hardware Reliability = 99.961% with 4 Hour MTTR (204 Minutes/Year) Hardware Reliability = 99.9999% with 4 Hour MTTR (30 Seconds/Year)

  10. 3 1 Router Availability R1, R2, R3 and R4 16000/(16000+24) = 0.9985 Can Include Hardware + Software Components Availability of R1, R2 in Parallel with R3, R4 = 1 - ((1-0.997)(1 - 0.997)) = 0.99999104 2 Availability of R1, R2 and R3, R4 in Series = (0.9985´0.9985) = 0.997006 4 Network Availability = 99.999% Only Base on Device Availability Values; Link Availability Not Included Network Availability Calculation R2 R1 Router R1, R2, R3 and R4 MTBF = 16000 Hours MTTR = 24 Hours R3 R4

  11. High Availability - Layered Approach Application Level Resiliency Global Server Load Balancing and positioning Gateways, gatekeepers, SIP servers, DB servers NSF/SSO,HSRP,VRRP, GLBP, IP Event Dampening , Graceful Restart (GR): BGP, ISIS, OSPF, EIGRP, OER, BGP multipath, fast polling, MARP, incremental SPF Protocol Level Resiliency Circuits, SONET APS, RPR, DWDM, Etherchannel, 802.1d, 802.1w, 802.1s, PVST+,Portfast, BPDU guard, PagP, LacP,UDLD, Stackwise technology, PPP, Transport/Link Level Resiliency Device Level Resiliency Redundant Processors (RP), Switch Fabric, Line Cards, Ports, Power, CoPP, ISSU, Config Rollback

More Related