[j-nsp] L2circuit between Juniper and Cisco

Ioan Branet ioan.branet at gmail.com
Wed Feb 10 03:03:19 EST 2010


Hello group,



I am traying to configrure a L2circuit between an MX and a 7600 as PEs
(ethernet-vlan mode).

The problem is that the ping between CE1 and CE2 works only when I use the
same vlan-ids on both PEs.

If I use different vlans ID , on Juniper side CE wont learn ARP .

I use ccc encapsulation (should I use tcc instead ? -I did not find a
relevant example)

The l2circuit is up but I cant ping between CE1 and CE2

If I use tcc should I configure also proxy and remote fields ?

I do not know what are the CE1 and CE2 customers addresses.



Here is my config:



 ge-2/0/4

 flexible-vlan-tagging;
        mtu 9000;
        encapsulation flexible-ethernet-services;

unit 614 {

 encapsulation vlan-ccc;
            vlan-id 614;

protocols

l2circuit {
        neighbor 172.25.224.1 {
            interface ge-2/0/4.614 {
                virtual-circuit-id 4000080;
                encapsulation-type ethernet-vlan
                no-control-word;
                mtu 1500;
                ignore-encapsulation-mismatch;
                ignore-mtu-mismatch;

 show configuration interfaces lo0
description "** ROUTER_ID **";
unit 0 {
    family inet {

        address 127.0.0.1/32;
        address 172.25.231.76/32 {
            primary;
            preferred;



show configuration protocols ldp
interface ae0.50;
interface fxp0.0 {
    disable;
}
interface lo0.0;

 show configuration protocols mpls
log-updown {
    syslog;
    trap;
}
interface fxp0.0 {
    disable;
}
interface all;





interface GigabitEthernet9/21.461
 encapsulation dot1Q 461
 xconnect 172.25.231.76 4000080 encapsulation mpls
end

 Feb  9 20:13:48.522574 Route flash received from mpls.0 : Flash
Feb  9 20:13:48.522596        Triggering VC status update timer for intf
ge-2/0/4.614
Feb  9 20:13:48.560166 [vc_intf_vc_status_update] Recomputing the status of
the VC for interface : ge-2/0/4.614
Feb  9 20:13:48.560210 vc_intf_vc_status_update] interface : ge-2/0/4.614 vc
status = intf Up : intf_up = TRUE
Feb  9 20:13:48.560220 [vc_intf_vc_status_update] interface : ge-2/0/4.614
UP adv_down = 0 : vc_down = 0, ccc_up = 1
Feb  9 20:13:48.560228 vc_intf_vc_status_update] interface : ge-2/0/4.614 VC
PRESENT
Feb  9 20:13:48.560238 [vc_intf_vc_status_update] interface : ge-2/0/4.614
Done Computing adv, vc down and ccc_up status adv_down = 0, vc_down = 0,
ccc_up = 1
Feb  9 20:13:48.560245 [vc_intf_vc_status_update]       Clearing the VC
status vector bit for interface : ge-2/0/4.614
Feb  9 20:13:48.560255 [l2ckt_vc_downstream_status_advertise] adding routes
for Intf ge-2/0/4.614: belonging to instance L2circuit
Feb  9 20:13:48.560302 ADD      172.25.224.1:NoCtrlWord:4:4000080:Local/96
L2CKT    pref 7/0 metric  <Hidden Int>
Feb  9 20:13:48.560314     Add route for l2ckt intf adv
172.25.224.1:NoCtrlWord:4:4000080:Local
(label: 413856)
Feb  9 20:13:48.560416 CHANGE   172.25.224.1:NoCtrlWord:4:4000080:Local/96
gw 89.136.99.97    L2CKT    pref 7/0 metric  <Active Int>
Feb  9 20:13:48.560435 CHANGE   172.25.224.1:NoCtrlWord:4:4000080:Local/96
gw 89.136.99.97    L2CKT    pref 7/0 metric  <Active Int>
Feb  9 20:13:48.560449 rt_close: 2 routes proto l2 circuit
Feb  9 20:13:48.560449
Feb  9 20:13:48.560466 [vc_intf_vc_status_update]       VC Up for interface
: ge-2/0/4.614
Feb  9 20:13:48.560523 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor :
172.25.224.1, VC-ID : 4000080) changed to UP
Feb  9 20:13:48.560533         vc (Neighbor : 172.25.224.1, VC-ID : 4000080)
UP
Feb  9 20:13:48.560664 [vc_intf_vc_status_update]       CCC status Up,
changed for interface : ge-2/0/4.614
Feb  9 20:13:48.560709  Intf ge-2/0/4.614 added to the Kernel VC status
update Q
Feb  9 20:13:48.560765 rt_flash_update_callback: flash l2 circuit
(l2circuit.0) start
Feb  9 20:13:48.560774 Flash call for L2CKT from l2ckt.0
Feb  9 20:13:48.560784 [l2ckt_handle_local_adv_rt_status_change]
VC-interface ge-2/0/4.614 transport LSP state transition to UP
Feb  9 20:13:48.560797 task_timer_reset: reset l2 circuit_Interface Change
Feb  9 20:13:48.560809 task_timer_set_oneshot_latest: timer l2
circuit_Interface Change interval set to 0.044473
Feb  9 20:13:48.560817 Flash processing complete for L2CKT from l2ckt.0
Feb  9 20:13:48.560826 rt_flash_update_callback: flash l2 circuit
(l2circuit.0) done
Feb  9 20:13:48.606160 task_timer_dispatch: calling l2 circuit_Interface
Change, late by 0.000
Feb  9 20:13:48.606186  [l2ckt_intf_change_process] Change processing for
intf ge-2/0/4.614:
Feb  9 20:13:48.606194 l2ckt_intf_create_mib2d_notify: Not a TDM VC
Feb  9 20:13:48.606204 ge-2/0/4.614 OP state transition to UP
Feb  9 20:13:48.606215 task_timer_dispatch: returned from l2
circuit_Interface Change, rescheduled in 0
Feb  9 20:13:48.611141  Kernel not updated with VC status for intf
ge-2/0/4.614

Any hint?

Thank you,
John


More information about the juniper-nsp mailing list