MSN
join:2004-05-15
Osgoode, ON
| reply to TomS_
Re: [Config] Configuring More Than 1 VPN Tunnel (871w)
This was all good advice. I talked to DocLarge last night and we sorted it out. I teach this stuff for Cisco and he and I arrived at a good analogy:
Essentially the crypto map is a virtual IPsec interface. All VPNs (both site-to-site and remote access) terminate on this virtual interface. If you think of the crypto map as the hub in a hub-and-spoke arrangement with the spokes being the VPN peers this makes sense. In the example above (thanks TomS_ !) the IPsec interface is identified as "ipsec-maps" The different VPN "spokes" are identified by their numbers. For example, "crypto map ipsec-maps 30 ipsec-isakmp" creates "spoke" 30, and the different components of the IPsec policy for moving traffic to/from the peer are grouped by that number:
The key, then, is remembering that you only have one IPsec interface tied to any one physical interface. Once you have created this crypto map, you link it to a "reall" interface like this:
In TomS_ 's config it is done with this command:
/Eric |
|
DocLarge
Premium
join:2004-09-08
4 edits | Thanks for the replies, gents...
As MSN said, we came to an understanding and all is running.
Where MSN calls it "hub and spoke," it (hub and spoke) can also be explained as the "anchor" crypto map (connectivity originates from it). Said differently, imagine the below map as my "first" crypto map:
crypto mapanchormap 110 ipsec-isakmp
Every other crypto map created needs to include the above crypto map as the "baseline" crypto map for vpn connectivity to take place (example given):
crypto map anchormap 111 ipsec-isakmp
set peer 22.33.44.55
match address 120 (Previously configured access-list)
etc...
crypto map anchormap 112 ipsec-isakmp
set peer 11.33.55.44
match address 140 (Previously configured access-list)
etc...
By approaching it from this standpoint, MSN helped bridge the gap 
*Heh* it makes since now...
Jay |
|
