This action might not be possible to undo. Are you sure you want to continue?
Creating an MPLS VPN - Packet Life
Ads by Google
Creating an MPLS VPN
By stretch Monday, May 16, 2011 at 1:17 a.m. UTC
Today we're going to look at the configuration required to create a basic MPLS VPN servicing two customers, each with a
presence at two physical sites. If you're unfamiliar with the concepts of MPLS switching and VRFs on Cisco IOS, you may
want to check out a few of my past articles before continuing:
Intro to VRF lite
InterVRF Routing with VRF Lite
Getting to know MPLS
Our lab topology looks like this:
As a review, recall that
P (provider) routers are ISP core routers which don't connect to customer routers and typically run only MPLS
PE (provider edge) routers connect to customer sites and form the edge of a VPN
CE (customer edge) routers exist at the edge of a customer site; they have no VPN awareness
an IGP running among all P and PE routers is used to support LDP and BGP adjacencies within the provider network
MPBGP is run only among PE routers
you may want to grab the finished router configurations if you'd like to duplicate the lab on your own. Although plenty of CLI outputs are shown below. 3. OSPF processes have also been preconfigured on the CE routers; however. Enable MPLS on the provider backbone.05/04/2012 Creating an MPLS VPN . P1(c fig)# interface f0/1 P1(c figif)# mpls ip P1(c figif)# interface f1/0 P1(c figif)# mpls ip P1(c figif)# do show mpls interfaces I e face IP T e O e a i a Fa E he e 0/1 Ye ( d ) N Ye Fa E he e 1/0 Ye ( d ) N Ye P2(c P2(c P2(c P2(c fig)# interface f0/1 figif)# mpls ip figif)# interface f1/0 figif)# mpls ip PE1(c fig)# interface f1/0 PE1(c figif)# mpls ip PE2(c fig)# interface f1/0 PE2(c figif)# mpls ip LDP adjacencies can be verified with the command show mpls ldp neighbor: packetlife.Packet Life an IGP (typically) is run between each CE router and its upstream PE router In our lab. Enable route redistribution between the customer sites and the backbone. 5. Create VRFs and assign routed interfaces to them. just plain IP routing. Enable MPLS First we need to enable MPLS on all PP and PPE links with the mpls ip interface command. 2.net/blog/2011/ma /16/creating-mpls-vpn/ 2/14 . OSPF is already in operation as the provider network IGP. MPLS is no enabled on any CEfacing interfaces; CE routers do not run MPLS. We can verify the configuration of MPLS interfaces with show mpls interfaces. LDP typically runs between loopback addresses not directly reachable by LDP peers. LDP is enabled automatically as the default label distribution protocol (versus Cisco's legacy TDP). these OSPF topologies will remain separate from the provider OSPF. Configure MPBGP between the PE routers. There are five core tasks we need to accomplish to get an MPLS VPN up and running: 1. Configure OSPF between each PE router and its attached CE routers. 4. which is why it's important to configure an IGP in the core before enabling MPLS.
0.0.2.1.2 Pee LDP Ide : 10.1 e ed d e e ab i g VRF C PE1(c figif)# ip address 10.0.0.0.0.3:0; L ca LDP Ide 10. PE1(c fig)# interface f0/0 PE1(c figif)# ip vrf forwarding Customer_A % I e face Fa E he e 0/0 IP add e 10.646 S a e: O e ; M g e / c d: 12/12; D ea U i e: 00:02:25 LDP di c e ce : Fa E he e 1/0. S c IP add : 10.0. VRF configuration must be performed on both PE routers.252 packetlife.126.96.36.199.1:0 TCP c ec i : 10.0.0.0.0.0.646 S a e: O e ; M g e / c d: 12/13; D ea U i e: 00:02:43 LDP di c e ce : Fa E he e 0/1.2:0; L ca LDP Ide 10. We need to assign each VRF a route distinguisher (RD) to uniquely identify prefixes as belonging to that VRF and one or more route targets (RTs) to specify how routes should be imported to and exported from the VRF.0.0.05/04/2012 Creating an MPLS VPN .0.0.9 10.0.0.) The command show ip vrf interfaces can be used to verify interface VRF assignment and addressing.188.8.131.52 255.2 Add e e b d ee LDP Ide : 10.45114 10.1. We'll use a route distinguisher for each VRF in the form of <ASN>:<c ome n mbe >. we'll reuse the same value as both an import and export route target within each VRF (though we are free to choose a different or additional route targets if we prefer).3 Create and Assign VRFs Our next step is to create customer VRFs on our PE routers and assign the customerfacing interfaces to them.184.108.40.206.6 10.net/blog/2011/ma /16/creating-mpls-vpn/ e _A 3/14 . S c IP add : 10.0.0.0. For simplicity.6 Add e e b d ee LDP Ide : 10.1:0 TCP c ec i : 10.Packet Life P1# show mpls ldp neighbor Pee LDP Ide : 10. (Assigning an interface to a VRF automatically wipes it of any configured IP addresses.1. PE1(c PE1(c PE1(c PE1(c PE1(c PE1(c fig)# ip vrf Customer_A fig f)# rd 65000:1 fig f)# routetarget both 65000:1 fig f)# ip vrf Customer_B fig f)# rd 65000:2 fig f)# routetarget both 65000:2 PE2(c PE2(c PE2(c PE2(c PE2(c PE2(c fig)# ip vrf Customer_A fig f)# rd 65000:1 fig f)# routetarget both 65000:1 fig f)# ip vrf Customer_B fig f)# rd 65000:2 fig f)# routetarget both 65000:2 The command routetarget both is used as a shortcut for the two commands routetarget import and route target export.9.20327 10. Now we need to assign the appropriate interfaces to each VRF and reapply their IP addresses.2 10.3. Your version of IOS may or may not inform you of this when it happens.9. which appear separately in the running configuration.0.
Minimal MPBGP configuration is pretty straightforward.0.2.0.Packet Life PE1(c figif)# interface f0/1 PE1(c figif)# ip vrf forwarding Customer_B % I e face Fa E he e 0/1 IP add e 10.2. PE1(c PE1(c PE1(c PE1(c PE1(c fig)# router bgp 65000 fig e )# neighbor 10.1.255. we notice that a bit more configuration than we provided has appeared: packetlife.0.0.1 255.0.4 remoteas 65000 fig e )# neighbor 10.0.g.0.0.5 255.0.5 e ed d e e ab i g VRF C e _B PE2(c figif)# ip address 10.0.0.0.4 updatesource loopback 0 fig e )# addressfamily vpnv4 fig e af)# neighbor 10.0.252 PE1(c figif)# ^Z PE1# show ip vrf interfaces I e face IPAdd e VRF P c Fa0/0 10.5 C e _B Configure MP-BGP on the PE Routers This is where things start to get interesting.1 C e _A Fa0/1 10. which are longer than normal routes due to the addition of a 64bit route distinguisher (which we assigned under VRF configuration). MPBGP runs only on the PE routers: P routers rely entirely on the provider IGP and MPLS to forward traffic through the provider network.4 activate PE2(c PE2(c PE2(c PE2(c PE2(c fig)# router bgp 65000 fig e )# neighbor 10.255.2.1.0.0. IPv4 and IPv6) over a common BGP adjacency.1 C e _A Fa0/1 10.2. and CE routers have no knowledge of routes outside their own VRF.2.255.252 PE2(c figif)# interface f0/1 PE2(c figif)# ip vrf forwarding Customer_B % I e face Fa E he e 0/1 IP add e 10.255.2.1.5 e ed d e e ab i g VRF C e _B PE1(c figif)# ip address 10.1 e ed d e e ab i g VRF C e _A PE2(c figif)# ip address 10.net/blog/2011/ma /16/creating-mpls-vpn/ 4/14 .3 remoteas 65000 fig e )# neighbor 10. Both PE routers exist in BGP AS 65000. It also supports the advertisement of VPN routes.0.1.5 255.0.0.0.05/04/2012 Creating an MPLS VPN . we must configure multiprotocol BGP (MPBGP).0.252 PE2(c figif)# ^Z PE2# show ip vrf interfaces I e face IPAdd e VRF P c Fa0/0 10.0.3 updatesource loopback 0 fig e )# addressfamily vpnv4 fig e af)# neighbor 10.255.0.3 activate If we look at the running configuration of the BGP process on either PE router. In order to advertise VRF routes from one PE router to the other. MPBGP is a little different from legacy BGP in that it supports multiple add e familie (e.255.5 C e _B PE2(c fig)# interface f0/0 PE2(c figif)# ip vrf forwarding Customer_A % I e face Fa E he e 0/0 IP add e 10.
Configure PE-CE OSPF We just configured MPBGP between the two PE routers.0.Packet Life PE1# show runningconfig section router bgp e bg 65000 ch i a i bg g eighb cha ge eighb 10.0. these OSPF processes are isolated from the provider OSPF topology. Now. ai i g ab e e i 1 Neighb V AS M gRc d M gSe Tb Ve I Q O Q U /D S a e/Pf Rcd 10.3.0.0.4 4 65000 12 12 1 0 0 00:06:05 0 Currently.05/04/2012 Creating an MPLS VPN . Verify that the MPBGP adjacency between PE1 and PE2 was formed successfully with the command show bgp vpnv4 unicast all summary: PE1# show bgp vpnv4 unicast all summary BGP e ide ifie 10. but we could just as easily use another IGP like EIGRP or RIP.4 ac i a e eighb 10. support for extended community strings has been added to the VPNv4 neighbor configuration. Also. The overall routing topology will look like this: packetlife. Remember that although we're using OSPF between each of the CE routers and its upstream PE router.0. let's configure an IGP between each PE router and its attached CE routers to exchange routes with the customer sites.0.0.0. Singlearea OSPF has already been configured on the CE routers; all CE interfaces are in area 0.0.0. We're going to use OSPF for this lab.4 e ea 65000 eighb 10.net/blog/2011/ma /16/creating-mpls-vpn/ 5/14 . because we have not specified anything to be advertised or redistributed.0. address families for the two customer VRFs have been created automatically. ca AS be 65000 BGP ab e e i i 1. but we'll get to that after this next step.4 e dc i e e ded e i add e fa i ! add e fa i i 4 f C e _B ch i a i e i add e fa i ! add e fa i i 4 f C e _A ch i a i e i add e fa i In addition to our VPNv4 address family.0. there are no routes in the BGP table.4 da e ce L bac 0 a a ! add e fa i 4 eighb 10.
Whereas the provider OSPF process exists in the global routing table. the two CE processes will each be assigned to their respective customer VRFs. PE1# show ip route vrf Customer_A packetlife.220.127.116.11 fig e )# interface f0/0 figif)# ip ospf 2 area 0 figif)# router ospf 3 vrf Customer_B fig e )# routerid 10.5 fig e )# interface f0/1 figif)# ip ospf 3 area 0 We should see each PE router form an OSPF adjacency with both of its attached CE routers. Each PE router will then have three OSPF processes total: one for the provider network.Packet Life The provider OSPF process has already been configured on the PE routers as process 1.2.0. PE1(c PE1(c PE1(c PE1(c PE1(c PE1(c PE1(c PE1(c fig)# router ospf 2 vrf Customer_A fig e )# routerid 10.1.1 fig e )# interface f0/0 figif)# ip ospf 2 area 0 figif)# router ospf 3 vrf Customer_B fig e )# routerid 10.05/04/2012 Creating an MPLS VPN .0. and the customer routes should appear in the VRF tables on the PE routers.net/blog/2011/ma /16/creating-mpls-vpn/ 6/14 . We'll configure an addi ional OSPF process for each CE router on each PE router.1.5 fig e )# interface f0/1 figif)# ip ospf 3 area 0 PE2(c PE2(c PE2(c PE2(c PE2(c PE2(c PE2(c PE2(c fig)# router ospf 2 vrf Customer_A fig e )# routerid 10. and one for each CE router.
0.1.0.2.18.104.22.168.2/32 10. e _A 172.05/04/2012 Creating an MPLS VPN .1. First we'll configure redistribution of CE routes in each VRF into MPBGP.0. Fa E he e 0/0 10..0/30 10.17.1. e _B 172. Fa E he e 0/1 Configure Route Redistribution We're almost done! We have our MPLS and MPBGP backbone up and running. PE1(c PE1(c PE1(c PE1(c PE1(c fig)# router bgp 65000 fig e )# addressfamily ipv4 vrf Customer_A fig e af)# redistribute ospf 2 fig e af)# addressfamily ipv4 vrf Customer_B fig e af)# redistribute ospf 3 PE2(c PE2(c PE2(c PE2(c PE2(c fig)# router bgp 65000 fig e )# addressfamily ipv4 vrf Customer_A fig e af)# redistribute ospf 2 fig e af)# addressfamily ipv4 vrf Customer_B fig e af)# redistribute ospf 3 This enables redistribution of OSPF routes into BGP for transport across the provider network between the two sites..0.0.0.0/16 networks) now appear in the BGP tables for their respective VRFs.0.0.0 0 32768 ? *>i10. 00:04:21.0.0/30 0.0.17.4 11 100 0 ? packetlife.16. Fa E he e 0/0 O 172.1/32 10. PE1# show ip bgp vpnv4 vrf Customer_A ..1/32 [110/11] ia 10.1.0.Packet Life R i g Tab e: C . and our CE routers are sending routes to our PE routers within their VRFs.0/16 i a iab b e ed.0. 00:03:03.0. Fa E he e 0/1 O 172. 2 b e ..22.214.171.124.2 11 32768 ? *>i172.4 i di ec c ec ed. 00:03:04. 1 b e C 10.0.0/30 i b e ed..net/blog/2011/ma /16/creating-mpls-vpn/ 7/14 .0 i di ec c ec ed. 2 b e .0.0/24 [110/11] ia 10. Fa E he e 0/1 10.16. 2 a O 172.16.1. Ne Ne H Me ic L cP f Weigh Pa h R e Di i g i he : 65000:1 (defa f f C e _A) *> 10.2.0/30 i b e ed.0.6.1.16.1/32 [110/11] ia 10.0.2. We can verify that the routes learned from the customer sites (the 126.96.36.199/24 [110/11] ia 10. 1 b e C 10.0.4 0 100 0 ? *> 172.17. The last step is to glue everything together by turning on route redistribution from the customer side OSPF processes into MPBGP and vice versa on the PE routers. Fa E he e 0/0 PE1# show ip route vrf Customer_B R i g Tab e: C . 00:04:21. This is done under the BGP IPv4 address family for each VRF.0.1.0/16 i a iab b e ed.0.0.0.17.0. 2 a O 172.0/16 and 172..
0.0.0.4/30 0.16.0.16.16.0.0/24 [110/21] ia 10.16. 00:03:188.8.131.52.2.0/24 i di ec c ec ed. Fa E he e 0/0 C 10.2 11 32768 ? *>i184.108.40.206.2/32 10.16..1.0. 2 b e O IA 10. Fa E he e 0/0 10.1/32 [110/21] ia 10. Fa E he e 0/0 CE2A# show ip route .0/30 i b e ed.0..Packet Life *> 172. we should now have endtoend connectivity between the CE routers within each VRF.1.0/24 10.0.0.0. 2 a C 172. (We don't have to specify any VRF information in the redistribution statement because each customer OSPF process is already assigned to a VRF.1. 172.0.net/blog/2011/ma /16/creating-mpls-vpn/ 8/14 . If you're accustomed to route redistribution. L bac 0 O IA 172.4 11 100 0 ? The last step is to complete the redistribution in the opposite direction: from BGP into the customer OSPF processes.0.1. 00:02:220.127.116.11.0 i di ec c ec ed.1.0 [110/11] ia 10. 172. Both routers for each customer should now have complete routing tables.18.104.22.168.0/24 10.0.0..4 0 100 0 ? *> 172. 00:02:49. Fa E he e 0/0 O IA 172..4/30 10.0.0. 4 b e .16.0/16 i a iab b e ed.0.2.1.0.6 11 32768 ? *>i172.17.0.6 11 32768 ? *>i22.214.171.124.0/24 10.4 11 100 0 ? PE1# show ip bgp vpnv4 vrf Customer_B . Ne Ne H Me ic L cP f Weigh Pa h R e Di i g i he : 65000:2 (defa f f C e _B) *> 10.1. 2 a O IA 172. L bac 1 packetlife..0.0.1.17. Fa E he e 0/0 C 172.0.0 0 32768 ? *>i10. there's nothing new here.2. 4 b e .16.05/04/2012 Creating an MPLS VPN ..1/32 10. Here are customer A's routes: CE1A# show ip route .0/24 [110/21] ia 10.2/32 [110/21] ia 10.0.0/16 i a iab b e ed.1.4 11 100 0 ? *> 172.0. L bac 1 C 172.2. Fa E he e 0/0 O IA 172.0/24 i di ec c ec ed.0.1.16.1.16.2.1/32 i di ec c ec ed.2.0/24 10.17.) PE1(c PE1(c PE1(c PE1(c fig)# router ospf 2 fig e )# redistribute bgp 65000 subnets fig e )# router ospf 3 fig e )# redistribute bgp 65000 subnets PE2(c PE2(c PE2(c PE2(c fig)# router ospf 2 fig e )# redistribute bgp 65000 subnets fig e )# router ospf 3 fig e )# redistribute bgp 65000 subnets Testing and Confirmation If has gone well.1. 00:03:50. 00:03:50.
2 1 10. i e i 2 ec d : !!!!! S cce a e i 100 e ce (5/5).0. T aci g he e 172.16. on the edge of the Washington. And again. L bac 0 10.9.05/04/2012 Creating an MPLS VPN .1. 2 b e C 10.2/32 i di ec c ec ed.2 T e e ca e e e ce ab .1 4 ec 4 ec 8 ec 2 10.0. (Remember that we don't need to specify a VRF when doing so because CE routers have no knowledge that they're in a VRF.1. and the maintainer of PacketLife.9. Although primarily an R&S guy. d i i /a g/ a = 12/21/32 We can perform a traceroute to verify the path taken as well as the MPLS labels used to traverse the provider network.126.96.36.199.0/30 i b e ed.net/blog/2011/ma /16/creating-mpls-vpn/ 9/14 . he likes to get into everything.0 [110/11] ia 10. each site exists as a separate linkstate topology connected by the MPLS VPN. DC metro area. (Thanks to Ivan Pepelnjak of Cisco IOS Hints helping revise this article!) Abo he A ho Jeremy Stretch is a freelance networking engineer. Virginia.2. Fa E he e 0/0 O IA 10.0. and runs a free network training lab out of his basement for fun. CE1A# traceroute 172.16. here are the the finished router configurations if you'd like to replicate the lab yourself.0. Fa E he e 0/0 You may notice that OSPF routes sent between two sites belonging to the same customer appear as interarea routes.2 T e e ca e e e ce ab . You can contact him by email or follow him on Twitter.0.0.2.0.5 [MPLS: Labe 19/22 E 0] 16 ec 12 ec 24 ec 3 10.0 i di ec c ec ed.0.0.1 [MPLS: Labe 22 E 0] 20 ec 16 ec 24 ec 5 10.2 [MPLS: Labe 19/22 E 0] 24 ec 20 ec 16 ec 4 10. instructor. Se di g 5. 00:02:49.2. 100b e ICMP Ech 172.2 16 ec * 36 ec Here's a packet capture of the above traceroute if you're interested in how the MPLS label information is returned. He currently lives in Fairfax.) CE1A# ping 188.8.131.52.Packet Life C 172. Remember that although OSPF area 0 is being used at both sites. We should be able to ping from one CE router to the other.16.0.net.16. Posted in MPLS.0. VPN packetlife.1.
05/04/2012 Creating an MPLS VPN .m. UTC Thanks. May 16. UTC Hi Jeremy. UTC An excellent post. 1111oneoneone (guest) commented on Monday.net/blog/2011/ma /16/creating-mpls-vpn/ 10/14 . that's what the RT is for. May 16. Alain Trey (guest) commented on Monday.. its much easier to add if you use "vrf definition " instead of "ip vrf " f defi i i f2 packetlife. May 16. Could just be a misunderstanding from my part or you should rewrite that sentence.m. Daniel (guest) commented on Monday. Good post." This could be due to english not being my native language but this sounds like you're saying that RD defines the VPN and this is not true. UTC Stretch.m. 2011 at 3:59 a. 2011 at 8:53 a. 2011 at 7:31 a. As always there is only one word to describe this post: excellent ! Regards. I'm having some problems with this sentence: "We need to assign each VRF a route distinguisher (RD) to uniquely identify prefixes as belonging to that VRF and one or more route targets (RTs) to specify how routes should be imported to and exported from the VRF. UTC If you ever plan to implement IPv6.Packet Life Comments Ace (guest) commented on Monday.m. May 16.. The RD only makes prefixes unique but does not in any way define the VPN. Alain commented on Monday. May 16. Thanks Jeremy. 2011 at 1:12 p. 2011 at 6:14 a.m. I'm surprised Ivan didn't catch this if he read the article.
m. me_rahawan82 commented on Tuesday. It simply means that the RD is used to make routes unique (e.m. 2011 at 6:30 p. giving people the false impression that this is required. Hussain (guest) commented on Monday.m. UTC Yes. RD does nothing more than make the routes unique so that BGP will distribute them correctly.My hero packetlife. UTC Thanks Jeremy.m. UTC thanks stretch commented on Monday. May 16. 2011 at 5:20 p. May 16. 2011 at 11:39 a. 2011 at 2:09 p. May 17. You can just as easily use one RD per VRF per PE. People often get confused about the RD because nearly all cisco examples I have seen use the same RD on both PE routers.g. Thats what I usually do in examples just to remind people that RT and RD are two different things.Packet Life d 2:2 ! add e fa i i 4 e a ge e 2:2 e a ge i 2:2 e i add e fa i Trey Rob (guest) commented on Monday. May 16. May 16.05/04/2012 Creating an MPLS VPN .net/blog/2011/ma /16/creating-mpls-vpn/ 11/14 . UTC @Daniel: It must be a language barrier thing. 2011 at 3:12 p. UTC Many thanks !! Bart (guest) commented on Monday. when customers use overlapping address space).m.
May 17. regards. There are only 32. May 17. You are the best. OmiPR commented on Tuesday.. May 18.. May 19. That means you can not connect more than 30 unique CE to one PE (http://www.m.m.m. i read your your posts almoust two years and i must say THANK YOU. May 19.shtml#q46) Thats why OSPF isn't the best choise for ISIS is not supported there at all.net/blog/2011/ma /16/creating-mpls-vpn/ 12/14 .cisco. Thanx for this short and concise post.05/04/2012 Creating an MPLS VPN . UTC .m. UTC THANK YOU for the post man. 2011 at 9:38 p.we are waiting :) yelfathi (guest) commented on Thursday. 2011 at 4:49 p. 2011 at 3:37 a. UTC Thanks Stretch! It helped me a lot for MPLS config understanding! alpi (guest) commented on Tuesday.Packet Life reca (guest) commented on Tuesday.com/en/US/tech/tk365/technologies_q_and_a_item09186a0080094704. Hope you will discuss L2 VPN (Martini & Kompella) soon. Alen abulanov commented on Wednesday.and sometimes you want to use only MPBGP and do not carry any prefixes and then you add "no bgp default ipv4unicast" under the "router bgp 65001" context. amitabha commented on Thursday...m. UTC Hi.m. May 17. 2011 at 6:23 p. 2011 at 8:15 p.. 2011 at 7:26 a. UTC Using OSPF on PECE is limited by a number of OSPF processes on PE router. UTC packetlife.
October 6. UTC Your network topology looks great.m.4 send-communit e tended packetlife. and I'm still "raw" regarding the issue.net/blog/2011/ma /16/creating-mpls-vpn/ 13/14 . 2012 at 6:48 p. It is an excellent introductory config to understand basics of mpls. UTC dear Jeremy Stretch Thanks for your awesome scenario. waleed143 commented on Friday. January 13.m. A guest commented on Friday. 2011 at 2:54 p..m. June 20. I am Brazilian and my CBT is on this issue.! Selasi (guest) commented on Monday. but 1 thing is missing. UTC thank you so much Jeremy. Wish me well! US vpn (guest) commented on Thursday.m. Writing BGP+MPLS in 3 weeks. 2011 at 2:35 p. I would like your help. November 4. UTC Thanks Jeremy. May 22. This example has really helped me understand the concept even further.m.0.0.Packet Life Good introduction i will add two remarks : check ip cef before enabling mpls because mpls needs it create dedicated loopbacks and force the mpls routerid to them Those avoid you from potential problems you will see after more practices :) kammu commented on Sunday. 2011 at 6:07 a. Thank you for sharing this. You are great. i was working on this topology for 4 to 5 hours but my VRF sites was not able to communicate with each other and you said on this scenario that neighbor 10..05/04/2012 Creating an MPLS VPN . UTC great post Jeremy. 2011 at 7:07 p. but my doubt is how can I improve the using MPLS VPNs.
m.05/04/2012 Creating an MPLS VPN . Sastrt (guest) commented on Tuesday.What's the difference? Lea e a Commen packetlife. March 3. but i didn't. 2012 at 8:04 p..net/blog/2011/ma /16/creating-mpls-vpn/ 14/14 .. pswolfwind commented on Saturday.m.this may be a issue in regards to the ios version.Packet Life will generate automatically.but is must be configured. then i contacted with my friend he told that put that command manually then it worked. UTC Simply supub!!! Thanks for your post.Another question about this command is my practice lab book stated that it must be configured to sendcommunity both. UTC hi waleed143. 2012 at 3:47 a. January 24.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.