MPLS Lab

burbankmarc

I hate to blow up the forum, but there's not a whole lot of activity in the CCIP...so whatever.

I'm working on this lab:

Advanced MPLS VPN | MPLS

I'm stuck on the COCO customer section. Particularly this part:

Configure router PE2 so AS3 will accept it's own AS number.
Configure router CocoHQ so it will accept it's own AS number.

The second part is easy, just add the allowas-in to bgp. But I'm not sure how to do that from the PE router to a specific AS. Once I get to that section BGP and EIGRP start getting weird. I'm pushing routes through BGP to the PE, and the PE gets the routes but it doesn't put them in the RIB.

Here's an example:

PE2#sh ip bgp vpnv4 vrf COCO neighbors 192.168.57.7 received-routes 
BGP table version is 30, local router ID is 55.55.55.55
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 333:333 (default for vrf COCO)
*  77.77.77.0/24    192.168.57.7             0             0 3 i
*  192.168.57.0     192.168.57.7             0             0 3 i

Total number of prefixes 2 
PE2#sh ip route vrf COCO 77.77.77.0 255.255.255.0                   
% Network not in table

Has anyone completed this lab successfully?

networker050184

I haven't done the lab, but it sounds like they may be looking for AS-override on PE2. That won't force the other router to accept its own AS though. May just be wording.

Not sure about the rest though. I'd have to lab it up, but no time right now. A debug of the updates might give you some hints on it though.

deth1k

"Configure router PE2 so AS3 will accept it's own AS number"

yep, what they mean is use as-override

burbankmarc

networker050184 wrote: »

A debug of the updates might give you some hints on it though.

Good advice. This is what I saw:

*Mar  1 03:44:34.255: BGP(2): no valid path for 333:333:77.77.77.0/24

I've seen this before with iBGP and synchronization problems, but I've never seen this happen with eBGP peers before.

Heero

Damn. Started this lab a couple weeks ago, still not done though cause i took a couple breaks. I'm at the COCO section as well when i get the time to do some more.

Just interesting to see a tread about a lab i'm doing right now.

burbankmarc

Heero wrote: »

Damn. Started this lab a couple weeks ago, still not done though cause i took a couple breaks. I'm at the COCO section as well when i get the time to do some more.

Just interesting to see a tread about a lab i'm doing right now.

Yeah this is my first foray into MPLS so this lab is killing me. I've restarted it about 6 times now. I'm just skipping straight to the COCO section now since I didn't have a problem with the rest of it.

I got the route inserted into the RIB finally. I just decided to blow up the PE2 config and just start from scratch, which now it works.

PE2#sh ip bgp vpn vrf COCO neighbors 192.168.57.7 received-routes
BGP table version is 33, local router ID is 55.55.55.55
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 333:333 (default for vrf COCO)
*  77.77.77.0/24    192.168.57.7             0             0 3 i
*  192.168.57.0     192.168.57.7             0             0 3 i
*  192.168.78.0     192.168.57.7             0             0 3 i

Total number of prefixes 3 
PE2#
PE2#
PE2#
PE2#
PE2#sh ip route vrf COCO 77.77.77.0 255.255.255.0
Routing entry for 77.77.77.0/24
  Known via "bgp 1", distance 20, metric 0
  Tag 3, type external
  Redistributing via eigrp 3
  Advertised by eigrp 3 metric 10000 20 250 50 1500
  Last update from 192.168.57.7 00:00:32 ago
  Routing Descriptor Blocks:
  * 192.168.57.7, from 192.168.57.7, 00:00:32 ago
      Route metric is 0, traffic share count is 1
      AS Hops 1
      Route tag 3

I think I was applying a route-map that didn't exist to the BGP neighbors (SOO-COCO instead of COCO-SOO).

Well, time to finish this bad boy off.

tomaifauchai

Have you done all the previous labs?

MPLS | Table

burbankmarc

I did them all except for the AToM since it isn't on the test. If they had some LC-ATM i'd do those.

mikej412

burbankmarc wrote: »

I did them all except for the AToM since it isn't on the test.

It's specifically mentioned in the blueprint Exam Description. It's probably safer to do the lab then hope that the luck of draw on questions favors your decision not to do AToM.

The exam will certify that the successful candidate has knowledge and skills necessary to gather information from the technology basics to some of the more updated features and functions such as Traffic Engineering, Fast Reroute and any Transport over MPLS (AToM). The exam covers topics on MPLS Concepts, MPLS Label Assignment and Distribution, Frame-Mode/Cell-Mode MPLS Implementation on Cisco IOS Platforms, MPLS Virtual Private Networks Technology, MPLS VPN Implementation, Complex MPLS VPNs, and Internet Access from a MPLS VPN.

burbankmarc wrote: »

If they had some LC-ATM i'd do those.

I found it useful to study, at least back in the old days.

burbankmarc

mikej412 wrote: »

It's specifically mentioned in the blueprint Exam Description. It's probably safer to do the lab then hope that the luck of draw on questions favors your decision not to do AToM.

Ha, I guess I should read the "Exam Description" section. It's not listed in the "Exam Topics" section, but LC-ATM is, which is why I didn't think AToM was on the test.

Well, looks like I added an extra couple days to my timeline, plus it's probably a good thing to know anyways. Thanks for the reality check!

networker050184

You are going to see a lot more AToM in the real world rather than LC-ATM so its worth learning whether its on the exam or not.