Lab 6 Task 3.3

So I wonder if I'm the only one seeing this behavior...

First off, let me say that I have checked my configurations against the solutions, enabled MPLS (TDP) on the ATM interfaces and everything that sould be necessary but I am still running into this problem.

When I configure the aggregate address on R9, the label that gets generated for that route is "unrecognized".

The debug ip bgp mpls output gives me this clue:

BGP: adding MPLS label to 217.1.0.0/22
BGP: check on 217.1.0.0/22 in LDP - failed
BGP-IPv4: Send prefix 217.1.0.0/22, label unrecognized tag type

I'm not sure why I'm seeing this, but it makes the aggregate unreachable from the other side of the ATM cloud, and R2 shows the entry for 217's aggregate with an invalid label, see below

SPRack1R2#sh ip bgp labels
   Network          Next Hop      In label/Out label
   20.1.0.0/22      0.0.0.0         nolabel/nolabel
   20.1.1.1/32      20.1.12.1       20(from LDP)/nolabel
   20.1.2.2/32      0.0.0.0         imp-null(from LDP)/nolabel
   20.1.3.3/32      20.1.23.3       16(from LDP)/nolabel
   20.1.4.4/32      20.1.26.6       22/nolabel
   20.1.5.5/32      20.1.23.3       19(from LDP)/nolabel
   20.1.6.6/32      20.1.26.6       21/nolabel
   192.168.1.0      150.1.9.9       23/exp-null
   217.1.0.0/22     150.1.9.9       24/242616

So is anyone else seeing this behavior?  I haven't done anything fancy, in fact, the only thing I have configured is sections 1-3.3 and then 4.1 (to enable TDP on the ATM interfaces).  I have verified that traffic works by removing the aggregate and allowing the specific 217 networks on the link.  When I do this, four networks with proper labels cross the ATM cloud and I can now ping R9's loopbacks from anywhere in AS200...

I think this may be a bug, but I'm running a diff version of code on another router that shows similar behavior.  Any thoughts???

Thanks


Sign In or Register to comment.