MPLS forwarding table bug?

Hi,

Is this a bug and has anyone seen it before?

Routing table:

MPLS Forwarding Table RT1:

MPLS Forwarding Table RT2:

This is running in my test VM environment running CHRs on version 6.37.4.

The whole setup works fine, but it’s strange that vrf-customer1 subnets are shown as @main, and vrf-customer2 subnets as @vrf-customer1.

Thanks for your feedback!

No one??

Are both of the VRFs advertised within the VPNv4 community?

Hi. Yes they are both advertised withing VPNv4.

This is definitely a bug. The forwarding table was showing correctly in 6.35.1 though, but there were some other bugs that caused my setup not to work.