[j-nsp] MPLS VPN LAYER 3 translation from cisco to M20

[Juan C. Crespo R.]

It seems to work Ok :)

jc at WAAAAAAAAAAA> show bgp summary
Groups: 1 Peers: 2 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    
Pending
inet.0            211845     211823          0          0          
0          0
bgp.l3vpn.0          127        121          0          0          
0          0
bgp.l3vpn.2            0          0          0          0          
0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
State|#Active/Received/Damped...
a.b.c.d    ASASA        809        739       0       1     6:06:42 Establ
  inet.0: 5/5/0
  bgp.l3vpn.0: 3/3/0
  L3VPN.inet.0: 3/3/0
e.f.g.h    ASASA      83796        741       0       1     6:07:49 Establ
  inet.0: 211818/211840/0
  bgp.l3vpn.0: 118/124/0
  L3VPN.inet.0: 116/123/0
 
Thanks so much :D


Georgi Yalamov escribió:
> Juan C. Crespo R. wrote:
>> Dears
>>
>>     Anyone could help me translating this config from a Cisco to a 
>> Juniper M20?
>>
>> STATIC ROUTE
>> ip route X.X.X.X 255.255.255.252 Serial0 name L3VPN
>>
>>
>> ip vrf L3VPN
>>  rd ASASA:000000001
>>  route-target export ASASA:000000001
>>  route-target import ASASA:000000002
>>
>>
>> address-family vpnv4
>> neighbor a.b.c.d peer-group iBGP-GROUP
>>
>> address-family ipv4 vrf L3VPN
>> redistribute connected
>> redistribute static
>> no auto-summary
>> no synchronization
>> exit-address-family
>>
>> Thanks
>>
>> JC
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>   
> Hi,
>
>
> Try something like this:
>
> # show protocols bgp
>
> show protocols bgp
> group iBGP-GROUP {
>    type internal;
>    local-address A.A.A.A.;
>    mtu-discovery;
>    family inet {
>        unicast;
>    }
>    family inet-vpn {
>        unicast;
>        any;
>    }
>    peer-as 8866;
>    neighbor a.b.c.d;
>    neighbor a.b.c.e;
> }
>
>
> #show routing-instances L3VPN
> description L3VPN;
> instance-type vrf;
> interface ge-0/2/1.....;
> route-distinguisher ASASA:00000000001
> vrf-import l3vpn-imp;
> vrf-export l3vpn-exp;
> vrf-table-label;
> routing-options {
>    static {
>        route X.X.X.X/30 next-hop Y.Y.Y.Y;
> }
>
> # show policy-options policy-statement l3vpn-imp
> term a {
>    from {
>        protocol bgp;
>        community l3vpn-comm-imp;
>    }
>    then accept;
> }
> term b {
>    then reject;
> }
>
> [edit]
> # show policy-options policy-statement l3vpn-exp
> term a {
>    from protocol [ direct static ];
>    then {
>        community add l3vpn-comm-exp;
>        accept;
>    }
> }
> term b {
>    then reject;
> }
>
> # show policy-options community ..
> community l3vpn-comm-exp members target:ASASA:00000000001
> community l3vpn-comm-imp members target:ASASA:00000000002
>
>
> Kind regards,
>
> -- 
> George Yalamov
> Bulgarian Telecommunications Company AD
> Senior Engineer Core/Metro Technologies
> tel: 359 2 949 6844
>
>
>
>
>