We discussed this, brainstormed and got amazing answers… Here is summary of discussion
In normal situation we will calculate network availability based on the uptime of the Internet connection, because if the Internet goes down, it will affect both internal and external applications. But on other side in reality - a failure of the VPN tunnel would still impact the access to internal applications but not external applications (partial outage).
- Both VPN and Internet will have its own availability measures different technology even if they are network related. Best would be to divide and measure them.
- E2E business KPI's is what customers are looking at.. as we have business processes.. we have to link infrastructure and software components associated and measure business KPI's rather than SLA.
- One of approach to calculate network availability can be weighted average between the availability of the Internet connection and the availability of the VPN tunnel: “Network Network Availability = Weight external_apps x Network Availability Internet + Weight Internal_apps x Network Availability VPN"
- The two weights values should be set and discussed with the business architect considering business criticalness.
- For example, let’s assume that 80% of the business applications used by the users are external (Internet) and that the remaining 20% are internal (VPN). If in one-year time interval, the Internet connection never failed, while the VPN tunnel was unavailable for 1 day, then the value of the overall network availability for that location is:
- Network Availability = 80% * 100% + 20% * (99.726%) = 99.945%
