VRF-Lite - Implications of using Loopback not in VRF as the Router-Id
Hi, I have multiple vrf's configured on a device and than a shared vrf. The shared VRF is used to form a ipv4 iBGP session between a redundant horizontal switch and an eBGP session with a downstream switch across a firewall. All the interfaces on this switch will be SVIs and they are in a VRF. I have a Loopback 0 interface configured however I haven't made that part of a VRF and its part of the Global RT. I have a Loopback 1 which I have in the shared VRF which is used for the iBGP peering.
1. Is there any downside to using loopback 0 as the BGP Router-ID even though the other devices cannot reach Loopback 0 since its not being advertised?
2. Since Loopback0 is in the Global RT and the rest of the environment is only reachable via the Shared VRF is there any way to advertise this loopback in the shared VRF? I tried creating a VRF static route with a 'Global' keyword however am not sure what I should specify for the return traffic or what kind of route I should enter in the Global RT. Thx for your help.
Re: VRF-Lite - Implications of using Loopback not in VRF as the
Thanks for the reply. I had read that post however I was more interested in the question which relates to using the loopback0 which is not a part of the VRF as a router-id in BGP even though its not advertised anywhere. What would be the impact of doing this. thx
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...