does anyone know why an unspecified route originated via a neighbor default-originate command in a 6PE environment does not have a label sent along with it?
no label makes it unusable in the 6PE environment as the receiving router sees the prefix as inaccessible, so is this a bug or am i missing something?
see the comparison of an unspecified prefix and gloabl unicast advertised over a 6PE session
thnaks
*Mar 1 00:21:16.295: BGP(1): 1.1.1.1 rcvd UPDATE w/ attr: nexthop ::FFFF:1.1.1.1, origin i, localpref 100, metric 0
*Mar 1 00:21:16.303: BGP(1): 1.1.1.1 rcvd ::/0
*Mar 1 00:21:16.335: BGP(1): 1.1.1.1 rcvd UPDATE w/ attr: nexthop ::FFFF:1.1.1.1, origin i, localpref 100, metric 0, path 2
*Mar 1 00:21:16.339: BGP(1): 1.1.1.1 rcvd 2002::/16
*Mar 1 00:21:16.351: BGP(1): no valid path for ::/0
*Mar 1 00:21:16.355: BGP(1): nettable_walker ::/0 no best path
*Mar 1 00:21:16.363: BGP(1): Revise route installing 2002::/16 -> ::FFFF:1.1.1.1 (::) to main IPv6 table
PE2#sh ip bgp ipv6 uni ::/0
BGP routing table entry for ::/0, version 2
Paths: (1 available, no best path)
Not advertised to any peer
Local
::FFFF:1.1.1.1 (inaccessible) from 1.1.1.1 (1.1.1.1)
Origin IGP, metric 0, localpref 100, valid, internal
PE2#sh ip bgp ipv6 uni 2002::/16
BGP routing table entry for 2002::/16, version 4
Paths: (1 available, best #1, table Global-IPv6-Table)
Advertised to update-groups:
1
2
::FFFF:1.1.1.1 (metric 3) from 1.1.1.1 (1.1.1.1)
Origin IGP, metric 0, localpref 100, valid, internal, best
mpls labels in/out nolabel/20
