[j-nsp] iBGP and IPv6

Mark Tinka mark.tinka at seacom.mu
Wed Apr 15 14:38:18 EDT 2015


Your pasting is not formatting well. Makes it hard to help you.

Mark.

On 15/Apr/15 20:23, Jonathan Call wrote:
> OSPF/OSPFv3 are the IGP, which apparently are feeding back into IBGP:
> With OSPFv3 enabled: 2001:db8:4000::1/128*[Direct/0] 1w0d 21:13:49    
>                > via lo0.1                     [OSPF3/10] 1w0d
> 21:13:44, metric 0                    > via lo0.1                    
> [BGP/170] 00:00:18, MED 1, localpref 100, from 2001:db8:4000::2      
>                 AS path: I                    > to fe80:db8:4000:1::3
> via ge-0/0/8.0 With OSPFv3 disabled: vr-1.inet6.0: 8 destinations, 9
> routes (8 active, 0 holddown, 0 hidden) + = Active Route, - = Last
> Active, * = Both 2001:db8:4000::1/128*[Direct/0] 1w0d 21:10:41        
>            > via lo0.1                     [OSPF3/10] 1w0d 21:10:36,
> metric 0                    > via lo0.1 Limiting IBGP to only export
> directly connected routes would prevent this. It still does not
> explain why router1 will mark the IPv4 loopback route it received as
> hidden/unusable but the IPv6 loopback route is not. Jonathan Subject:
> Re: [j-nsp] iBGP and IPv6 To: lordsith49 at hotmail.com;
> juniper-nsp at puck.nether.net From: mark.tinka at seacom.mu Date: Wed, 15
> Apr 2015 18:02:30 +0200 On 15/Apr/15 17:43, Jonathan Call wrote:
> Correct.  The BGP route for the router's IPv4 loopback is marked as
> hidden/unusable. It does not show up in show route extensive output.
> Is this Loopback IPv4 address known by any other routing protocol,
> e.g., an IGP? Mark.



More information about the juniper-nsp mailing list