Abstract Internet access for organizations today is no longer about connectivity for email and web browsing. A stable Internet connection is a vital component in the chain of IT systems required to conduct business. Typically, in the past, the focus around Internet connectivity has been on cost, with vendors providing solutions allowing organizations to spread their traffic across consumer and enterprise products.
This approach is all good and well and can provide significant cost savings, especially when employee traffic is directed over low-cost consumer products such as ADSL, however, when you conduct B2B business through front-end servers hosted in your DMZ, resilience becomes a major concern.
A dead Internet link can mean loss of revenue and even, potentially more serious, brand damage in this scenario. In this paper, we discuss some methods that can improve the resilience of an Internet link. While this sounds like it should be a simple case of connecting to multiple Internet Service Providers, the devil, as they say, is in the detail.
Business networks have been mission-critical for some time now, and the focus on resilience and business continuity has always been top of any CIO’s mind. However, the general areas of interest for this focus were restricted to internal networks and systems. With more and more business being conducted either directly via the web or B2B over Internet links to systems hosted in DMZ’s, it is simply no longer permissible for an Internet link to be down. Loss of access to the Internet can directly impact revenue generation, especially today as the business operating models begin shifting towards off-site cloud computing and software as a service.
A solution to the problem
Multihoming is essentially a method whereby a company can connect to more than one ISP at the same time. The concept was born out of the need to protect Internet access in either an ISP link failure or an ISP internal failure. In the earlier days of Internet access, most traffic was outbound, except email.
An Internet link failure left internal users with no browsing capability and email backing up on inbound ISP mail gateways. Once the link was restored, so was browsing and email delivery. The direct impact to the business was relatively small and mostly not revenue effecting. Early solutions to this problem were to connect multiple links to the same ISP, but while this offered some level of link resilience, it could provide no safeguards against an internal ISP failure.
Related Articles :
- Work At Home Business – Internet Tips For Success
- Top 10 SEO Tips
- Internet Tips and Techniques
- 9 Easy SEO Tips for 2016
- Top 10 SEO Tips for 2011 Rank Higher on Google With These Easy SEO Tips
Today, however, most organizations deploy a myriad of on-site Internet-access services such as VPN’s, voice services, webmail, and secure internal system access while also making use of business-critical off-site services such as software as a service (SaaS) and other cloud-based solutions. Furthermore, while corporate front-end websites are traditionally hosted offsite with web hosting firms, the real-time information on the corporate websites and B2B sites is provided by back-end systems based in the corporate data center or DMZ. Without a good quality Internet connection, these vital links would be severed.
Varied requirements and complexity
The requirement for multihoming is varied and could range from the simple need for geographic link diversity (single ISP) to full link and ISP resilience where separate links are run from separate data centers to different ISP’s. While the complexity varies for each option, the latter forms the most complex deployment option but affords the highest availability. The former provides some degree of protection but does require a higher grade of ISP.