[j-nsp] Collapsed MPLS CE/PE/P configuration

[Hugo Slabbert]

The original config also doesn't show any of your BGP config from inet.0, 
so it's hard to say what's missing.

IIRC, if you have vrf-target, you don't need vrf-export:

     vrf-export export-direct;
     vrf-target target:7849:13;

If you want to do explicit export policy via vrf-export, I believe you need 
to drop the vrf-target and instead create a vrf-import policy as well.

-- 
Hugo

hugo at slabnet.com: email, xmpp/jabber
PGP fingerprint (B178313E):
CF18 15FA 9FE4 0CD1 2319 1D77 9AB1 0FFD B178 313E

(also on Signal)

On Mon 2015-Dec-21 15:57:40 +0000, Phil Mayers <p.mayers at imperial.ac.uk> wrote:

>On 21/12/15 15:42, Matthew Crocker wrote:
>
>>A ‘show run bgp sum’    bgp.l3vpn.0  with 0 routes
>
>That's what you want to focus on. Check the output of "show bgp nei" 
>to ensure the inet-vpn-unicast is *actually* present on "NLRI for 
>this session"; if not then correct this.
>
>Remember if you're using a route-reflector you need to have it setup there.
>
>If the NLRI is present then "show route receive-proto bgp <nei> table 
>bgp.l3vpn.0 all extensive" to check you're actually getting any 
>routes but maybe rejecting them.
>
>If there are no routes present, check "show route 
>advertising-protocol bgp <nei> table VRF.inet.0" at the sending side 
>to check they're actually being redistributed.
>
>Showing your full BGP config might help.
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20151221/68ada9a9/attachment-0001.sig>