A three-step guide to help you understand your customer's remote-access VPN technology, and create a roadmap for supporting, modifying, updating or optimizing an installed solution. This tip originally appeared on SearchNetworking.com.
So you are new to the virtual private network (VPN) world and you have just been assigned the duties of supporting your company's remote-access VPN solution due to the last administrator quitting. You consider yourself a pretty savvy customer when it comes to technology and IT solutions, but you have no experience with remote-access VPNs. You want to make sure you can execute the job of supporting the deployed remote access solution so you can impress your boss as to your ability to handle this assignment.
This is not an uncommon scenario, nor is it uncommon for folks to be thrown into the fire to support technology they do not necessarily understand. The initial reaction is to immediately jump into the education process. This is done via a variety of methods including Internet research, publications and for-fee training. While all of these may seem like a logical first step, I want to propose a different approach. The approach presented here follows a logical progression to understanding technology so that a roadmap can be developed for supporting, modifying, updating or optimizing an installed solution.
First things first: Understand the requirements:
This step entails understanding what purpose the VPN solution serves and the scope of the VPN services offered. Try to answer the following questions:
- Who currently utilizes the VPN solution?
- Who may need to use the VPN solution in the future?
- What areas of the environment do VPN users have access to?
- What areas of the environment will VPN users need to access?
- From where do users need to access the network? Home? Hotels? Domestic? International?
Second: Understand the deployed solution -- component level
This is the process of discovering what products and technologies are currently in place to provide VPN services and how those products integrate into the environment. Most VPN solutions are client and server based, so documenting the aspects of this will help you understand the different areas that may require focus when isolating trouble spots. Try to gather the following at a minimum:
- What VPN client hardware and software is deployed?
- What VPN server hardware and software is deployed?
- How does the equipment interconnect into the backend network?
- Where do VPN users enter the network?
- What maintenance and support agreements are in place for any of the above?
Third: Understand the services supported
This is the process of discovering services are available via the technology and components that are deployed. Basically, this is a "what can the products I have purchased provide?" type question. This is a very critical step as it can provide you with the areas that you need to educate yourself on to support the VPN solution that is deployed within your environment. To understand the services supported, the best places to start are the user guides and Web pages for the vendors that have supplied the equipment.
As you can see, this approach is a structured approach that facilitates gaining an understanding of the VPN solution prior to determining how to educate yourself on troubleshooting it. It is amazing how folks just dive right into the manual and learn about things totally irrelevant to their environment. By executing the basic steps above, you will be much better prepared to troubleshoot the VPN environment as you will actually understand the solution from a component level, from a service/functionality level and from a perspective of what requirements or capabilities it is providing.
About the author
Robbie Harrell (CCIE#3873) is the National Practice Lead for Advanced Infrastructure Solutions for SBC Communications. He has over ten years of experience providing strategic, business and technical consulting services. Robbie resides in Atlanta, and is a graduate of Clemson University. His background includes positions as a Principal Architect at International Network Services, Lucent, Frontway and Callisma.
This tip originally appeared on SearchNetworking.com.
