If anyone cares, I figured it out.
In short, I was overthinking the problem and came to the anti-climactic
conclusion that you can import/export whatever the hell you want as long
as it's in the RIB. I was under the incorrect assumption that the prefix
being imported/exported had to be in BGP somehow.
After tweaking my route-policies, I'm a happy camper.
Thanks to everyone who responded both on- and off-list.
Cheers!
- bryan
On 1/3/20 8:36 PM, Joe Loiacono wrote:
I take it back -- I misspoke.
These prefixes are advertised via BGP, but they are generated locally
('network' statement), which means their next-hop is 0.0.0.0. I do
believe that is the underlying issue.
So to answer your question, I think it's yes: I'm trying to leak IGP
prefixes (or in this case, a static in the "default" VRF) into the
"peering" VRF.
Is this possible?
>
I recall this frustrating difficulty on the Nexux 7K. In some situations
it would work if I used the destination VLAN ID option instead of the
destination VLAN interface IP address (for some VLAN in the destination
VRF)
Joe
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
