Trabalho de mtbf

Disponível somente no TrabalhosFeitos
  • Páginas : 44 (10776 palavras )
  • Download(s) : 0
  • Publicado : 23 de novembro de 2011
Ler documento completo
Amostra do texto
AVAILABILITY MEASUREMENT
SESSION NMS-2201

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

1

Agenda
• Introduction • Availability Measurement Methodologies
Trouble Ticketing Device Reachability: ICMP (Ping), SA Agent, COOL SNMP: Uptime, Ping-MIB, COOL, EEM, SA Agent Application

• Developing an Availability ‘Culture’

NMS-2201 9627_05_2004_c2

© 2004Cisco Systems, Inc. All rights reserved.

2

© 2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr

Associated Sessions
• NMS-1N01: Intro to Network Management • NMS-1N02: Intro to SNMP and MIBs • NMS-1N04: Intro to Service Assurance Agent • NMS-1N41: Introduction to Performance Management • NMS-2042: Performance Measurement with Cisco IOS® • ACC-2010:Deploying Mobility in HA Wireless LANs • NMS-2202: How Cisco Achieved HA in Its LAN • RST-2514: HA in Campus Network Deployments • NMS-4043: Advanced Service Assurance Agent • RST-4312: High Availability in Routing
NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

3

INTRODUCTION WHY MEASURE AVAILABILITY?

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rightsreserved.

4

© 2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr

Why Measure Availability?
1. Baseline the network 2. Identify areas for network improvement 3. Measure the impact of improvement projects

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

5

Why Should We Care About Network Availability?
• Where are we now?(baseline) • Where are we going? (business objectives) • How best do we get from where we are not to where we are going? (improvements) • “What if, we can’t get there from here?”

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

6

© 2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr

Why Should We Care About Network Availability?Recent Studies by Sage Research Determined That US-Based Service Providers Encountered: • Percent of downtime that is unscheduled: 44% • 18% of customers experience over 100 hours of unscheduled downtime or an availability of 98.5% • Average cost of network downtime per year: $21.6 million or $2,169 per minute!

Downtime—Costs too Much!!!
SOURCE: Sage Research, IP Service Provider DowntimeStudy: Analysis of Downtime Causes, Costs and Containment Strategies, August 17, 2001, Prepared for Cisco SPLOB
NMS-2201 9627_05_2004_c2
© 2004 Cisco Systems, Inc. All rights reserved.

7

Cause of Network Outages
• Change management • Process consistency
Technology • Hardware • Links 20%

• Design • Environmental issues • Natural disasters •Software issues •Performance and load •ScalingUser Error and Process 40%

Source: Gartner Group
NMS-2201 9627_05_2004_c2
© 2004 Cisco Systems, Inc. All rights reserved.

Software and Application 40%

8

© 2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr

Top Three Causes of Network Outages
• Congestive degradation • Capacity (unanticipated peaks) • Solutions validation • Software quality •Inadvertent configuration change • Change management • Network design • WAN failure (e.g., major fiber cut or carrier failure) • Power • Critical services failure (e.g. DNS/DHCP) • Protocol implementations and misbehavior • Hardware fault

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

9

Method for Attaining a Highly-Available Network
Or a Road to Five Nine’s
•Establish a standard measurement method • Define business goals as related to metrics • Categorize failures, root causes, and improvements • Take action for root cause resolution and improvement implementation

NMS-2201 9627_05_2004_c2

© 2004 Cisco Systems, Inc. All rights reserved.

10

© 2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr

Where Are We...
tracking img