Avaya Application Solutions Deployment Manual page 267

Table 59: Case Study II: Cleveland and Boston Local Availability values are
improved by LSP. Atlanta's Availability value is improved by N+1 IP resources.
Site
Atlanta
Boston
Cleveland
Table 60: Weighted System Availability with LSP and N+1 IP resources.
Full Solution Availability Projected
% of traffic generated in Atlanta
downtime minutes in Atlanta
% of traffic generated in Boston
downtime minutes in Boston
% of traffic between Atlanta and Boston
downtime minutes due to failure in Atlanta, WAN,
and in Boston
% of traffic generated in Cleveland
downtime minutes in Cleveland
% of traffic between Atlanta and Cleveland
Annual downtime minutes due to failure in Atlanta,
WAN, and in Cleveland
% of traffic between Boston and Cleveland
Annual downtime minutes due to failure in Boston,
WAN, and in Cleveland
Aggregated Downtime
System Availability = 99.6%
As reflected in Table 60: Weighted System Availability with LSP and N+1 IP resources.
page 267, the highest downtime is contributed by the WAN link between the headquarters in
Atlanta and the two branch offices.
Avaya Product
Availability Annual
Downtime
Minutes
99.99% 53
99.95% 263
99.99% 53
Annual
Annual
Annual
Design for High Availability
Complete Solution including
data network Availability
Availability Per Site Annual
Downtime
Minutes
99.99% 53 (4.3 hrs)
99% 5260 (88 hrs)
99.99% 53
Weighted Downtime
minutes.
(43.3% + 14.2%)
(16% + 2%)
Annual (5.2% + 5.2%)
(7% + 0.4%)
(2.7% + 2.2%)
(0.9% + 0.9%)
1874.5 minutes
(30.5 + 940 + 547 + 4 + 258 +
95)
Issue 3.4.1 June 2005
53 = 30.5
5260 = 940
5260 = 547
53 = 4
5260 = 258
5260 = 95
on
267