[j-nsp] Logical tunnel encapsulation

[Graham Brown]

Rafael, your memory is spot on. See an earlier post for verification:
https://puck.nether.net/pipermail/juniper-nsp/2011-June/020382.html

-- 
Graham Brown
Twitter - @mountainrescuer <https://twitter.com/#!/mountainrescuer>
LinkedIn <http://www.linkedin.com/in/grahamcbrown>

On Fri, Dec 23, 2011 at 9:37 PM, Rafael Rodriguez <packetjockey at gmail.com>wrote:

> If my memory is correct, 11.x supports IPv6 with lt.
>
> Sent from my iPhone
>
> On Dec 23, 2011, at 8:14, Eric Van Tol <eric at atlantech.net> wrote:
>
> > Hi all,
> > Is frame-relay encapsulation not supported on the MX80 logical tunnel
> interfaces?  I'm on 10.4R8.5 and need to configure IPv6 on an lt- interface:
> >
> > Interface on the default instance:
> >
> > # show interfaces lt-0/0/10
> > unit 1 {
> >    encapsulation frame-relay;
> >    dlci 128;
> >    peer-unit 1;
> >    family inet {
> >        address 192.168.209.201/30;
> >    }
> >    family inet6 {
> >        address 2001:db8::d1c9/64;
> >    }
> > }
> > Interface on my logical-system:
> >
> > # show interfaces lt-0/0/10
> > unit 1 {
> >    encapsulation frame-relay;
> >    dlci 128;
> >    peer-unit 0;
> >    family inet {
> >        address 192.168.209.202/30;
> >    }
> >    family inet6 {
> >        address 2001:db8::d1ca/64;
> >    }
> > }
> >
> > Interface shows 'up' and no flags are set to indicate a problem.
>  However, pinging doesn't work and this shows up in my logs:
> >
> > Dec 23 07:57:12  r1 tfeb0 HALP-trinity_nh_ucast_installnh(690)
> encaps-install failed: unsupported option
> > Dec 23 07:57:12  r1 tfeb0 Failed to create platform state, unsupported
> option
> > Dec 23 07:57:12  r1 /kernel: RT_PFE: NH IPC op 1 (ADD NEXTHOP) failed,
> err 1 (Unknown) peer_class 0, peer_index 0 peer_type 17
> > Dec 23 07:57:12  r1 /kernel: RT_PFE: NH details: idx 690 type 2 ifl 80
> > Dec 23 07:57:12  r1 tfeb0 Failed to install in platform, unsupported
> option
> > Dec 23 07:57:12  r1 tfeb0 Type specific Add failed unsupported option
> nh-id:690
> > Dec 23 07:57:12  r1 /kernel: RT_PFE: NH IPC op 2 (CHANGE NEXTHOP)
> failed, err 1 (Unknown) peer_class 0, peer_index 0 peer_type 17
> > Dec 23 07:57:12  r1 l2cp[1186]: Read acess profile () config
> > Dec 23 07:57:12  r1 /kernel: RT_PFE: NH IPC op 1 (ADD NEXTHOP) failed,
> err 1 (Unknown) peer_class 0, peer_index 0 peer_type 17
> > Dec 23 07:57:12  r1 /kernel: RT_PFE: NH details: idx 692 type 2 ifl 81
> > Dec 23 07:57:13  r1 tfeb0 HALP-trinity_nh_ucast_installnh(690)
> encaps-install failed: unsupported option
> > Dec 23 07:57:13  r1 tfeb0 Failed to create platform state, unsupported
> option
> > Dec 23 07:57:13  r1 tfeb0 Failed to install in platform, unsupported
> option
> > Dec 23 07:57:13  r1 tfeb0 Type specific Add failed unsupported option
> nh-id:690
> > Dec 23 07:57:13  r1 tfeb0 Failed to instantiate new copy for NH(690)
> > Dec 23 07:57:13  r1 tfeb0 Failed to change state
> > Dec 23 07:57:13  r1 tfeb0 HALP-trinity_nh_ucast_installnh(692)
> encaps-install failed: unsupported option
> > Dec 23 07:57:14  r1 tfeb0 Failed to create platform state, unsupported
> option
> > Dec 23 07:57:14  r1 tfeb0 Failed to install in platform, unsupported
> option
> > Dec 23 07:57:14  r1 tfeb0 Type specific Add failed unsupported option
> nh-id:692
> >
> > Also, this all works if I remove 'family inet6' and change encapsulation
> to 'ethernet'.
> >
> > If frame-relay encapsulation isn't supported, how does one use IPv6 on
> the lt- interfaces?
> >
> > Thanks in advance,
> > evt
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>