Thank you, this fixed the issue / On Wed, Mar 11, 2009 at 12:02 AM, Arda Balkanay <ardabalka...@gmail.com>wrote:
> You have configured interface fe-5/2/2.100 but used fe-5/2/2.600 at > l2circuit that's why you get " Mar 10 16:52:06.832065 [l2ckt_vc_update] > Failure to create/update vc 2.2.2.2:999 --> interface not present" error. > It says "interface does not exist" ... > > > On Wed, Mar 11, 2009 at 2:14 AM, Dinesh <dineshbs...@gmail.com> wrote: > >> just attaching the interface config.. >> >> fe-5/2/2 { >> vlan-tagging; >> encapsulation vlan-ccc; >> fastether-options { >> loopback; >> } >> unit 100 { >> encapsulation vlan-ccc; >> vlan-id 600; >> } >> } >> >> >> On Tue, Mar 10, 2009 at 4:57 PM, Dinesh <dineshbs...@gmail.com> wrote: >> >> > Hi i am trying to bring up a l2-circuit from Juniper m40 to a cisco... i >> > see cisco fine... but i get this error on m40 ... >> > >> > >> > neighbor 2.2.2.2 { >> > interface fe-5/2/2.600 { >> > virtual-circuit-id 999; >> > } >> > } >> > >> > 10 16:52:06.831491 [l2ckt_intf_change_process] Change processing for >> intf >> > fe-5/2/2.600: >> > Mar 10 16:52:06.832065 [l2ckt_vc_update] Failure to create/update vc >> > 2.2.2.2:999 --> interface not present >> > Mar 10 16:54:53.521672 [l2ckt_intf_change_process] Change processing >> for >> > intf fe-5/2/2.600: >> > Mar 10 16:54:53.522137 [l2ckt_vc_update] Failure to create/update vc >> > 2.2.2.2:999 --> interface not present >> > Mar 10 16:54:54.711437 [l2ckt_intf_change_process] Change processing >> for >> > intf fe-5/2/2.600: >> > Mar 10 16:54:54.711864 [l2ckt_vc_update] Failure to create/update vc >> > 2.2.2.2:999 --> interface not present >> > >> > >> > >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp