The 3002 is a hardware version of the Cisco VPN software client. Like the software client, it is easy to use, but provides much more scalability where a large number of SOHO sites need to connect to a central site. It is easy to deploy and support; most IPsec functionality is hidden from the user who has to deploy and manage it, just as is the case with the Cisco VPN Client software. The 3002 fully supports Cisco Easy VPN Remote technologies and is used as a remote access device, protecting traffic for users behind it.
Because the 3002 is an Easy VPN Remote, you can centralize policies on an Easy VPN Server and push them down to the 3002. The 3002 supports two modes for protecting users' traffic to a central site: client and network extension modes (these will be discussed later in the "Connection Modes" section). The following sections will discuss the features, models, and deployment options for the 3002.
3002 Features
The 3002 is easy to deploy and support. It already is a DHCP client on its public interface, acquiring addressing information dynamically from the ISP (the 3002 also supports PPPoE on its public interface in addition to static IP addressing). It has a static IP address on its private interface and is a DHCP server on the private interface, giving out addressing information to internal devices. It supports a Quick Configuration process similar to the VPN 3000 concentrators, making it easy to set it up to connect to an Easy VPN Server. Here are some of the 3002's many features:
Note
Due to limited room for storing transforms on the 3002, it does not support AES-192 for encryption.
3002 Models
There are two 3002 models, as shown in Figure 14-1 (rear of the chassis).
Figure 14-1. 3002 Models
In the figure, both models have an external power supply, a hardware reset button, an RJ-45 console interface (uses a roll-over cable), and a 10/100BaseTX public interface. The only difference between the two models is that the 3002 has a single 10/100BaseTX private interface and the 3002-8E has an 8-port 10/100BaseTX auto-sensing private interface. The front of the 3002 chassis has three LEDs. Table 14-1 explains the status of the LEDs.
LED |
Color |
Description |
---|---|---|
PWR |
Off |
3002 is powered off |
Green |
3002 is powered on |
|
SYS |
Green |
3002 is operational |
Flashing green |
3002 is negotiating on its public interface using DHCP or PPPoE |
|
Flashing amber |
3002 is performing diagnostic tests |
|
Solid amber |
3002 has failed diagnostic tests |
|
VPN |
Off |
No VPN tunnel has been established |
Amber |
Establishing a VPN tunnel has failed |
|
Green |
A VPN tunnel is established |
Deployment of the 3002
Normally small remote offices or SOHO environments use remote access solutions to provide secure connections to a central site. Deploying a VPN gateway for an L2L connection is typically not necessary and cost-prohibitive. Therefore, there are four choices for VPN solutions in small remote office or SOHO environments:
The following sections will discuss the advantages and disadvantages of using software and hardware clients.
Software Client Option
The main advantage that VPN software client solutions have over hardware solutions is that software clients are typically free, like the Cisco VPN Client and Microsoft's L2TP/IPsec client. However, they have many disadvantages:
The software client commonly is used for the home user and, more commonly, mobile users.
Hardware Client Option
Hardware clients can handle the limitations that software clients have:
If a VPN-enabled hardware appliance is a better fit for many sites in your network, you now need to decide which type of hardware appliance to use: security appliances (like the PIX 501 or 506E), routers (like the Cisco IOS 830s, UBR900s, and 1700s), or VPN 3002s. Table 14-2 displays when each type of hardware appliance should be deployed.
Device |
Best for these purposes |
---|---|
IOS Router |
Need a non-Ethernet interface connection to the ISP, such as ISDN, xDSL, or serial Need enhanced QoS Need voice support |
PIX |
Need a hardware-based stateful firewall Implements split tunneling Need complex address translation policies, especially with protocols that have problems with address translation (For non-Ethernet ISP connections, you'll still need a router) |
3002 |
Need ease of implementation, upgrades, and support Requires little training since the GUI interface is the same as the VPN 3000 concentrators (For non-Ethernet ISP connections, you'll still need a router) |
TIP
In most cases, if I needed to support voice connections or I needed a non-Ethernet-based ISP connection, I would use a router; for enhanced throughput, I'd get a 1700 series router with the VPN encryption module. If I needed to allow for split tunneling at the remote access site, or had need of complex address-translation policies, I would use a small-end PIX security appliance. If I had none of these concerns, then I would prefer to use a 3002 hardware client, because, of the three solutions, it is the easiest to install, upgrade, and maintain.
Part I: VPNs
Overview of VPNs
VPN Technologies
IPsec
PPTP and L2TP
SSL VPNs
Part II: Concentrators
Concentrator Product Information
Concentrator Remote Access Connections with IPsec
Concentrator Remote Access Connections with PPTP, L2TP, and WebVPN
Concentrator Site-to-Site Connections
Concentrator Management
Verifying and Troubleshooting Concentrator Connections
Part III: Clients
Cisco VPN Software Client
Windows Software Client
3002 Hardware Client
Part IV: IOS Routers
Router Product Information
Router ISAKMP/IKE Phase 1 Connectivity
Router Site-to-Site Connections
Router Remote Access Connections
Troubleshooting Router Connections
Part V: PIX Firewalls
PIX and ASA Product Information
PIX and ASA Site-to-Site Connections
PIX and ASA Remote Access Connections
Troubleshooting PIX and ASA Connections
Part VI: Case Study
Case Study
Index