System availability

System availability

System Availability

• The percentage of time that the system can perform its intended function

System Availability = 1 – System Downtime


Downtime per year

Availability	Nines	Downtime
90%	1	36.5	days/year
99%	2	3.65	DAys/year
99.9%	3	8.78	hours/year
99.99%	4	52	minutes/year
99.999%	5	5	minutes/year

System Downtime

Many events causes system downtime:

• HW fault
• Software fault
• Vandalism
• Extreme conditions (fire, flooding etc)
• Power outage
• IP network failure
• Planned system maintenance

System Downtime = ∑ P * S * MTTR

P	= Probability of event taken place
S	= Severity of event
	= Percentage of service affected by fault
MTTR	= Mean Time To Repair
	= mean time to detect fault + mean time to fix fault

HW failure

MTBF

• Probability of HW faults calculated using MTBF figures
• MTBF ≠ System Availability

MTBF calculations

• Emperical method
• MIL-HDBK-217
• Telcordia

Emperical methods

• Based on statistics from the field

MIL-HDBK-217 and Telcordia

• All component entered in database with set environmental condition
• Provides usually lower MTBF figure than emperical methods
  • Does include real usage conditions
  • Use worst case environmental conditions

*More components gives higher MTBF
*MTBF and single points of failure

Other failures

Software fault

• Automatic watch dog functions
• Automatic recovery functions
• Maturity of system
• Structured software design and test

Vandalism and Extreme conditions

• Robustness to vandalism and extreme conditions
• IP and IK class
• IP security functions to hinder denial of service attacks (DOS)

Power outage

• UPS and redundant power supplier

IP network failure

• Network service level
• Redundant and switchover functions

Planned system maintenance

• Expansion, add users etc
• Ability to do maintenance without service interruptions

Redundancy

Redundancy is about parallelism and removing single point of failures

Redundancy usually gives lower MTBF figures

• Require more components

Redundancy usually provides significant higher service availability

• A single failure shall have minimum or no impact on service availability

STENTOFON System Availability

Redundancy

• Control room redundancy and parallel call handling
• Power supply redundancy
• Alternative AlphaNet routing
• Control card redundancy
• ….

Reduced MTTR

• AlphaNet supervision
• Station supervision and tone test
• Network monitoring (SNMP, Syslog, OPC)

Software failures and recovery

• HW watchdog
• SW process watchdog
• Automatic recovery

System maintenance

• Centralized and remote firmware upgrade
• Hot insert and removal of cards
• Control card redundancy

Some MTBF figures

Zenitel USA has been keeping statistics about failures and the reasons for failures

Zenitel USA actively encourages repairs and the estimate is that 95% of failures is reported, even failures of equipment installed before the AlphaCom was introduced

The following figures are based on the Zenitel USA statistics; for new equipment a comparison is made to figures from known equipment

Data used are the sales figures from Zenitel USA and the fault reports over an 8 year period

Empirical MTBF data – based on Zenitel USA data

Item Number	MTBF
1007001210	3200000
1007001310 / 1007070090	2400000
1007034210	3100000
1007034310 / 1007072090	2500000
1007036210	3000000
1007036310 / 1007071090	2800000
1007006101	950000
1007036600	1100000
1007061000 / 1007063000	1500000
Analogue substations	2100000
1008031000	1300000
1008041100	1400000
1009101010	3000000
1009202000	1400000
1009301000	5500000
1009303001	> 10000000
1009304005	1300000
1009305000	1000000
1009703000	1400000