 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
9 messages in net.nether.puck.cisco-nsp[c-nsp] MPLS, L2TPv3 Layer 2/3 VPN Ne...| From | Sent On | Attachments |
|---|---|---|
| Eric Kagan | Jan 4, 2005 6:56 am | |
| John Osmon | Jan 4, 2005 11:39 am | |
| Nick Shah | Jan 4, 2005 6:41 pm | |
| choo...@pacific.net.sg | Jan 4, 2005 9:14 pm | |
| Nick Shah | Jan 4, 2005 9:26 pm | |
| choo...@pacific.net.sg | Jan 4, 2005 10:02 pm | |
| Jon Lewis | Jan 4, 2005 10:51 pm | |
| Oliver Boehmer (oboehmer) | Jan 5, 2005 3:15 am | |
| Chris Cappuccio | Jan 5, 2005 10:15 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [c-nsp] MPLS, L2TPv3 Layer 2/3 VPN Network Options | Actions... |
|---|---|---|
| From: | Nick Shah (Nick...@aapt.com.au) | |
| Date: | Jan 4, 2005 6:41:35 pm | |
| List: | net.nether.puck.cisco-nsp | |
Eric
An excellent beginner/intermediate source of reference would be MPLS & VPN architectures VOL I (for MPLS & fixed tail VPN concepts) and VOLII covers remote access VPN's. To get you started here's a few pointers:
- There are P (essentially CORE routers) and PE (Provider edge) & CE (customer edge) routers - P routers form the core, run TAG SWITCHING, LDP & OSPF (for next hop reachability) - PE routers run OSPF with P routers, TAG SWITCHING on the links connected to P routers, and MP-BGP with other PE routers - CE routers (customer edge) connect to PE routers on a particular interface (or virtual access in case of Remote access), and they are part of VRF. VRF assignment happens on the PE interface (where the CE connects). This VRF is what separates 1 customer from the other. Each VRF has "identifiers" called Route Distinguishers & Route Targets. To simplify, keep RD & RT values unique per VRF. - Finally customer sites wanting to be part of same VPN (or VRF) can connect to any PE, and just by virtue of them being in same VRF they will be able to communicate with each other (and no one else). - The CE routers don't need any MPLS featureset. They run standard IPPLUS (or whatever is needed) image. For P & PE you will need SP (service provider) image.
Get 3-4 routers to be P routers, and 3-4 to be PE and 2-3 as CE, connect them and have a play.
- Make the P & PE routers as part of OSPF area 0. Announce loopbacks (and connected interfaces). Don't announce PE-CE links. - After checking reachability, turn on LDP, TAG SWITCHING. Check that labels are getting assigned etc. - After enabling TS, running traceroutes should show you MPLS LABELS. Most of your troubleshooting may happen here - Finally, turn on BGP between PE loopbacks (ideally). Here you have to use address family VPNV4. Better way would be to nominate route reflectors. However for a small setup, you can use a meshed peering.
The above is a 5000 ft. overview of MPLS core & MPLS VPN.
Rgds
Nick
------------------------------------------------------------------------------ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it.
------------------------------------------------------------------------------