[j-nsp] 6 VPE in Juno

[Nilesh Khambal]

With ip6-tunneling command (assuming you have that configured), JUNOS 
will convert the v4 LSP route in inet.3 to a 6to4 v6 format in inet6.3. 
This route is just used to resolve the vpn-v6 prefixes received from 
remote PE and not for actual traffic forwarding. Traffic forwarding 
should still happen with v4 LSP.

Assuming 1.1.1.2 is remote v4/v6 PE router, do you have a working v4 LSP 
to 1.1.1.2 in inet.3 table? Do you have any active vpn-v4 routes using 
this LSP and in active state.

Also, all v6 prefixes coming in with 1.1.1.2 as protocol nexthop? (they 
seem to be be but just want to be clear).

Also, if you can send the extensive output for received v6 prefixes in 
the hidden state, it would help.

Thanks,
Nilesh.

janardhan madabattula wrote:
> Hi,
> 
> 
> 
> I am trying to establish 6VPE (V6 over V4 vpn) with Juniper M320, but I
> could see there is some problem in installing V6 routes sent by Redback
> Smart Edge to Juno.
> 
>  Where as the V6 routes sent by Juno are successfully installed in SE
> routing table.
> 
>  I am seeing the following problem in Juno routing table i.e the next hop is
> shown as v6 address rather than V4 address. Should it covert V6 next-hop
> address back to V4 ? Any ideas ?
> 
>  Juno routing table:
> 
>  test at Systest-M320# run show route receive-protocol bgp 1.1.1.2
> logical-system jana hidden
> 
>  inet.0: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)
> 
>  inet.3: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
> 
>  vpn1.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
> 
>  mpls.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)
> 
>  vpn1.inet6.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
> 
>   Prefix                  Nexthop              MED     Lclpref    AS path
> 
>   220::/*64                ::ffff:1.1.1.2*       0       100        ?
> 
>   3ffe::/*64               ::ffff:1.1.1.2*       0       100        ?
> 
>  bgp.l3vpn-inet6.0: 2 destinations, 2 routes (0 active, 0 holddown, 2
> hidden)
> 
>   Prefix                  Nexthop              MED     Lclpref    AS path
> 
>   1.1.1.1:6500:220::/64
> 
>                           ::ffff:1.1.1.2       0       100        ?
> 
>   1.1.1.1:6500:3ffe::/64
> 
>                           ::ffff:1.1.1.2       0       100        ?
> 
> 
> 
> [edit groups MPBN logical-systems jana]
> 
> test at Systest-M320#
> 
> 
> 
> SE routing table:
> 
> [local]JST-PE2#sh bgp route ipv6 vpn neighbor 1.1.1.4 rec | begin 6500
> 
> VPN RD: 1.1.1.4:6500
> 
>    Network            Next Hop                Metric  LocPrf  Weight Path
> 
>> i 120::/64           1.1.1.4                      0     100     100 1000 ?
> 
>> i 200::/64           1.1.1.4                      0     100     100 i
> 
> [local]JST-PE2#
> 
> 
>  Thanks,
> Jana
> 
> Any ideas ?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> .
>