Hi angel, Thank you. This is actually a typo, from when I copy/pasted the config. I checked my config again and I do have lt-1/2/0.1 in the routing-instance.
On Fri, 09 Jan 2009 14:50:45 +0200, angel <[email protected]> wrote: > Marcus Eide wrote: >> Hi, >> I don't know if this is even possible, but I thought I'd ask you: Does >> anyone know if it's possible to connect an l2circuit to an vrf type >> routing-instance? >> >> I found some information that stated this could be done with logical >> tunnel >> interfaces, so I tried the following: >> >> >> interface lt-1/2/0 { >> unit 0 { >> encapsulation ethernet-ccc; >> peer-unit 1; >> family ccc; >> } >> unit 1 { >> encapsulation ethernet; >> peer-unit 0; >> family inet { >> address 192.168.3.1/24; >> } >> } >> } >> >> protocol l2circuit { >> neighbor 172.16.0.2 { >> interface lt-1/2/0.0 { >> virtual-circuit-id 7777; >> } >> } >> } >> >> routing-instance VRF1003 { >> instance-type vrf; >> interface lo0.1003; >> interface lt-1/2/0.1003; >> > Marcus, > You misconfigured lt unit numbers - in routing instance configuration > you must specify the peer lt unit number with "family inet" - in your > case it is lt-1/2/0.1 > > regards > >> route-distinguisher 65000:1003; >> vrf-target target:65000:1003; >> vrf-table-label; >> } >> >> The l2circuit shows up, but there's no traffic coming through. >> >> Any thoughts on the subject is appreciated. >> >> /Marcus >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> >> _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
