Hello,
Thanks for your reaction.
On Tue, Jan 26, 2010 at 08:47:44AM -0800, Andy Vance wrote:
> Without config snapshots of the VRF, the import policy and the export policy,
>it is difficult to say why you see this behavior, I have some ideas but I don't
> want to guess. Can you provide config snapshots? I don't want to assume and
> head down some road that may not be relevant. >
This is the VRF code
jer...@m120-1-test> show configuration routing-instances
CUST {
instance-type vrf;
interface fe-3/0/1.0;
vrf-target target:100:200;
protocols {
bgp {
group ce-CUST {
type external;
peer-as 200;
as-override;
neighbor 10.30.0.2;
}
}
}
}
The VRF table on the PE
jer...@m120-1-test> show route table CUST.inet.0
CUST.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.30.0.0/30 *[Direct/0] 09:56:57
> via fe-3/0/1.0
10.30.0.1/32 *[Local/0] 09:56:57
Local via fe-3/0/1.0
10.40.0.0/30 *[BGP/170] 00:07:52, localpref 100, from 10.0.0.4
AS path: I
> to 10.10.0.1 via fe-3/0/0.0, label-switched-path
m120.test-to-m20.test
192.168.5.0/24 *[BGP/170] 05:22:45, localpref 100
AS path: 200 I
> to 10.30.0.2 via fe-3/0/1.0
192.168.7.0/24 *[BGP/170] 00:07:52, localpref 100, from 10.0.0.4
AS path: 200 I
> to 10.10.0.1 via fe-3/0/0.0, label-switched-path
m120.test-to-m20.test
On the peer PE I have
jer...@m120-2.test> show route table CUST.inet.0
CUST.inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.20.0.0/30 *[Direct/0] 09:17:56
> via fe-3/0/1.0
10.20.0.1/32 *[Local/0] 09:17:56
Local via fe-3/0/1.0
10.30.0.0/30 *[BGP/170] 04:02:03, localpref 100, from 10.0.0.2
AS path: I
> to 10.10.0.5 via fe-3/0/0.0, label-switched-path
m120-2.test-to-m120.test
10.40.0.0/30 *[BGP/170] 04:02:03, localpref 100, from 10.0.0.4
AS path: I
> to 10.10.0.5 via fe-3/0/0.0, label-switched-path
m120-2.test-to-m20.test
192.168.5.0/24 *[BGP/170] 04:02:03, localpref 100, from 10.0.0.2
AS path: 200 I
> to 10.10.0.5 via fe-3/0/0.0, label-switched-path
m120-2.test-to-m120.test
192.168.6.0/24 *[BGP/170] 05:38:23, localpref 100
AS path: 200 I
> to 10.20.0.2 via fe-3/0/1.0
192.168.7.0/24 *[BGP/170] 04:02:03, localpref 100, from 10.0.0.4
AS path: 200 I
> to 10.10.0.5 via fe-3/0/0.0, label-switched-path
m120-2.test-to-m20.test
I wouldn't expect the 10.30/30 subnet to show up on the peer PE.
I understand from the other reactions that we'll need to create an
import/export vrf policy to accomplish what I want.
Kind regards,
-Jeroen-
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
