MPLS-OPS - Discussion of Multiprotocol Label Switching ()

Telmo Javier Di Leva | 1 Aug 2007 23:38

: L2CIRCUIT - Cisco Juniper Interoperability Issue

Dears all:

I have a trouble trying to bring up a L2CIRCUIT between CISCO and JUNIPER.

My Topology is: CE-PE-P-P-PE-CE.
The configuration of the VC on cisco is the following:

interface FastEthernet0/1.513
encapsulation dot1Q 513
no cdp enable
xconnect 200.62.0.39 513 pw-class TEST

The VC status is OK:

#sh mpls l2transport vc 513 detail
Local interface: Fa0/1.513 up, line protocol up, Eth VLAN 513 up
Destination address: 200.62.0.39, VC ID: 513, VC status: up
    Output interface: Gi2/0, imposed label stack {137152 113920}
    Preferred path: not configured
    Default path: active
    Tunnel label: 113920, next hop 200.61.128.254
Create time: 00:31:41, last status change time: 00:07:59
Signaling protocol: LDP, peer 200.62.0.39:0 up
    MPLS VC labels: local 969, remote 137152
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
    packet totals: receive 0, send 460
    byte totals:   receive 0, send 39560
    packet drops: receive 0, send 0

Configugation at Juniper:

> show configuration interfaces ge-0/0/0
vlan-tagging;
mtu 1548;
encapsulation vlan-ccc;

> show configuration interfaces ge-0/0/0 unit 513
encapsulation vlan-ccc;
vlan-id 513;

> show configuration protocols l2circuit
traceoptions {
    file L2CIRCUIT.TXT;
    flag all;
}
neighbor 10.184.1.5 {
    interface ge-0/0/0.513 {
        virtual-circuit-id 513;
        no-control-word;
        mtu 1500;
    }
}

The VC Status is ok too:

> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.184.1.5
    Interface                 Type St     Time last up          # Up trans
    ge-0/0/0.513(vc 513)      rmt   Up     Jul 31 18:43:52 2007           1
      Local interface: ge-0/0/0.513, Status: Up, Encapsulation: VLAN
      Remote PE: 10.184.1.5, Negotiated control-word: No
      Incoming label: 137152, Outgoing label: 969
        Time                  Event                   Interface/Lbl/PE
        Jul 31 18:43:52 2007 status update timer
        Jul 31 18:43:51 2007 PE route changed
        Jul 31 18:43:51 2007 Out lbl Update                       969
        Jul 31 18:43:51 2007 In lbl Update                     137152
        Jul 31 18:43:51 2007 loc intf up                 ge-0/0/0.513

Debugging the L2circuit neighboor i have the following:

Jul 31 18:52:48.828102 ADD      10.184.1.5:NoCtrlWord:4:513:Local/96 L2CKT    pref 7/0 metric <Hidden Int>
Jul 31 18:52:48.828173     Add route for l2ckt intf adv 10.184.1.5:NoCtrlWord:4:513:Local (label: 137152)
Jul 31 18:52:48.828540 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828637 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828803 rt_close: 2 routes proto l2 circuit
Jul 31 18:52:48.828803
Jul 31 18:52:48.828877     Insert/update vc 10.184.1.5:513
Jul 31 18:52:48.828914         new vc
Jul 31 18:52:48.829006         Insert/update vc L2CKT-NO-VC-ID
Jul 31 18:52:48.829064         circuit 0 updated to ge-0/0/0.513
Jul 31 18:52:48.829109         updated circuit 0 to ge-0/0/0.513, status UP
Jul 31 18:52:48.829154         add rti for ifl 268/16
Jul 31 18:52:48.829199         add nhi: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829300        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:48.829414         Ingress label changed to (137152)
Jul 31 18:52:48.829478         add rti for ifl 0 label 137152 op 0/36
Jul 31 18:52:48.829533         add route with prefix ifl 0 label 137152 op 0/36 and nexthop: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829807         updated ingress-label to 137152
Jul 31 18:52:48.829897         Egress VPN label changed to (969)
Jul 31 18:52:48.830001         Route to remote PE updated
Jul 31 18:52:48.830080         add nhi: indirect nexthop: 10.184.1.5, cw action NOOP bw 0bps
Jul 31 18:52:48.830168         add route with prefix ifl 268/16 and indirect nexthop: 10.184.1.5, cw action NOOP, bw 0bps
Jul 31 18:52:48.830784 task_timer_dispatch: returned from l2 circuit_Interface Change, rescheduled in 0
Jul 31 18:52:48.860334 rt_flash_update_callback: flash l2 circuit (l2circuit.0) start
Jul 31 18:52:48.860392 Flash call for L2CKT from l2ckt.0
Jul 31 18:52:48.860443 Flash processing complete for L2CKT from l2ckt.0
Jul 31 18:52:48.860499 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done
Jul 31 18:52:48.862357 Route flash received from mpls.0 : Flash
Jul 31 18:52:48.862435        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:50.756263 Recomputing the status of the VC for interface : ge-0/0/0.513
Jul 31 18:52:50.756434 VC Up for interface : ge-0/0/0.513
Jul 31 18:52:50.757227 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor : 10.184.1.5, VC-ID : 513) changed to UP
Jul 31 18:52:50.757310         vc (Neighbor : 10.184.1.5, VC-ID : 513) UP
Jul 31 18:52:50.758273 Intf ge-0/0/0.513 added to the Kernel VC status update Q
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

The problem is that i can't have conectivity end to end.
Everything looks great but i dont't have IP traffic.

Can sambody tell me if the following line can cause this issue?
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

Thanks a lot to all.

-- -- Telmo Javier Di Leva

headers

Sanjeewa Alahakone (sanjeewa | 2 Aug 2007 02:34

RE: : L2CIRCUIT - Cisco Juniper Interoperability Issue

Hi Telmo,

It seems that from far end you are not receiving traffic

VC statistics:
    packet totals: receive 0, send 460 <---
    byte totals:   receive 0, send 39560 <---
    packet drops: receive 0, send 0

For me, the control plane looks good, so you need to troubleshoot the forwarding plane, also check the l2 device connecting to far-end specifically whether arp is correctly populating.

HTH

Regards

Sanjeewa

From: Telmo Javier Di Leva [mailto:tdileva <at> ifxcorp.com]
Sent: Thursday, 2 August 2007 7:39 AM
To: mpls-ops <at> mplsrc.com
Subject: [MPLS-OPS]: L2CIRCUIT - Cisco Juniper Interoperability Issue

Dears all:

I have a trouble trying to bring up a L2CIRCUIT between CISCO and JUNIPER.

My Topology is: CE-PE-P-P-PE-CE.
The configuration of the VC on cisco is the following:

interface FastEthernet0/1.513
encapsulation dot1Q 513
no cdp enable
xconnect 200.62.0.39 513 pw-class TEST

The VC status is OK:

#sh mpls l2transport vc 513 detail
Local interface: Fa0/1.513 up, line protocol up, Eth VLAN 513 up
Destination address: 200.62.0.39, VC ID: 513, VC status: up
    Output interface: Gi2/0, imposed label stack {137152 113920}
    Preferred path: not configured
    Default path: active
    Tunnel label: 113920, next hop 200.61.128.254
Create time: 00:31:41, last status change time: 00:07:59
Signaling protocol: LDP, peer 200.62.0.39:0 up
    MPLS VC labels: local 969, remote 137152
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
    packet totals: receive 0, send 460
    byte totals:   receive 0, send 39560
    packet drops: receive 0, send 0

Configugation at Juniper:

> show configuration interfaces ge-0/0/0
vlan-tagging;
mtu 1548;
encapsulation vlan-ccc;

> show configuration interfaces ge-0/0/0 unit 513
encapsulation vlan-ccc;
vlan-id 513;

> show configuration protocols l2circuit
traceoptions {
    file L2CIRCUIT.TXT;
    flag all;
}
neighbor 10.184.1.5 {
    interface ge-0/0/0.513 {
        virtual-circuit-id 513;
        no-control-word;
        mtu 1500;
    }
}

The VC Status is ok too:

> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.184.1.5
    Interface                 Type St     Time last up          # Up trans
    ge-0/0/0.513(vc 513)      rmt   Up     Jul 31 18:43:52 2007           1
      Local interface: ge-0/0/0.513, Status: Up, Encapsulation: VLAN
      Remote PE: 10.184.1.5, Negotiated control-word: No
      Incoming label: 137152, Outgoing label: 969
        Time                  Event                   Interface/Lbl/PE
        Jul 31 18:43:52 2007 status update timer
        Jul 31 18:43:51 2007 PE route changed
        Jul 31 18:43:51 2007 Out lbl Update                       969
        Jul 31 18:43:51 2007 In lbl Update                     137152
        Jul 31 18:43:51 2007 loc intf up                 ge-0/0/0.513

Debugging the L2circuit neighboor i have the following:

Jul 31 18:52:48.828102 ADD      10.184.1.5:NoCtrlWord:4:513:Local/96 L2CKT    pref 7/0 metric <Hidden Int>
Jul 31 18:52:48.828173     Add route for l2ckt intf adv 10.184.1.5:NoCtrlWord:4:513:Local (label: 137152)
Jul 31 18:52:48.828540 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828637 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828803 rt_close: 2 routes proto l2 circuit
Jul 31 18:52:48.828803
Jul 31 18:52:48.828877     Insert/update vc 10.184.1.5:513
Jul 31 18:52:48.828914         new vc
Jul 31 18:52:48.829006         Insert/update vc L2CKT-NO-VC-ID
Jul 31 18:52:48.829064         circuit 0 updated to ge-0/0/0.513
Jul 31 18:52:48.829109         updated circuit 0 to ge-0/0/0.513, status UP
Jul 31 18:52:48.829154         add rti for ifl 268/16
Jul 31 18:52:48.829199         add nhi: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829300        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:48.829414         Ingress label changed to (137152)
Jul 31 18:52:48.829478         add rti for ifl 0 label 137152 op 0/36
Jul 31 18:52:48.829533         add route with prefix ifl 0 label 137152 op 0/36 and nexthop: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829807         updated ingress-label to 137152
Jul 31 18:52:48.829897         Egress VPN label changed to (969)
Jul 31 18:52:48.830001         Route to remote PE updated
Jul 31 18:52:48.830080         add nhi: indirect nexthop: 10.184.1.5, cw action NOOP bw 0bps
Jul 31 18:52:48.830168         add route with prefix ifl 268/16 and indirect nexthop: 10.184.1.5, cw action NOOP, bw 0bps
Jul 31 18:52:48.830784 task_timer_dispatch: returned from l2 circuit_Interface Change, rescheduled in 0
Jul 31 18:52:48.860334 rt_flash_update_callback: flash l2 circuit (l2circuit.0) start
Jul 31 18:52:48.860392 Flash call for L2CKT from l2ckt.0
Jul 31 18:52:48.860443 Flash processing complete for L2CKT from l2ckt.0
Jul 31 18:52:48.860499 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done
Jul 31 18:52:48.862357 Route flash received from mpls.0 : Flash
Jul 31 18:52:48.862435        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:50.756263 Recomputing the status of the VC for interface : ge-0/0/0.513
Jul 31 18:52:50.756434 VC Up for interface : ge-0/0/0.513
Jul 31 18:52:50.757227 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor : 10.184.1.5, VC-ID : 513) changed to UP
Jul 31 18:52:50.757310         vc (Neighbor : 10.184.1.5, VC-ID : 513) UP
Jul 31 18:52:50.758273 Intf ge-0/0/0.513 added to the Kernel VC status update Q
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

The problem is that i can't have conectivity end to end.
Everything looks great but i dont't have IP traffic.

Can sambody tell me if the following line can cause this issue?
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

Thanks a lot to all.

-- Telmo Javier Di Leva

------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

headers

J S Grewal | 2 Aug 2007 06:27

Re: : L2CIRCUIT - Cisco Juniper Interoperability Issue

Which Cisco box you are using? I faced same issue with Cisco 7600. But same thing works fine with Cisco 7200. Its Control-word negotiation issue. I observed Cisco 7600 send cbit:0 whereas Cisco 7200 sends cbit:1. If you can send me the details of your boxes i can try your config at my end and might able to give you more details.

rgds,

J.Grewal

----- Original Message -----

From: Telmo Javier Di Leva

To: mpls-ops <at> mplsrc.com

Sent: Thursday, August 02, 2007 3:08 AM

Subject: [MPLS-OPS]: L2CIRCUIT - Cisco Juniper Interoperability Issue

Dears all:

I have a trouble trying to bring up a L2CIRCUIT between CISCO and JUNIPER.

My Topology is: CE-PE-P-P-PE-CE.
The configuration of the VC on cisco is the following:

interface FastEthernet0/1.513
encapsulation dot1Q 513
no cdp enable
xconnect 200.62.0.39 513 pw-class TEST

The VC status is OK:

#sh mpls l2transport vc 513 detail
Local interface: Fa0/1.513 up, line protocol up, Eth VLAN 513 up
Destination address: 200.62.0.39, VC ID: 513, VC status: up
    Output interface: Gi2/0, imposed label stack {137152 113920}
    Preferred path: not configured
    Default path: active
    Tunnel label: 113920, next hop 200.61.128.254
Create time: 00:31:41, last status change time: 00:07:59
Signaling protocol: LDP, peer 200.62.0.39:0 up
    MPLS VC labels: local 969, remote 137152
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
    packet totals: receive 0, send 460
    byte totals:   receive 0, send 39560
    packet drops: receive 0, send 0

Configugation at Juniper:

> show configuration interfaces ge-0/0/0
vlan-tagging;
mtu 1548;
encapsulation vlan-ccc;

> show configuration interfaces ge-0/0/0 unit 513
encapsulation vlan-ccc;
vlan-id 513;

> show configuration protocols l2circuit
traceoptions {
    file L2CIRCUIT.TXT;
    flag all;
}
neighbor 10.184.1.5 {
    interface ge-0/0/0.513 {
        virtual-circuit-id 513;
        no-control-word;
        mtu 1500;
    }
}

The VC Status is ok too:

> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.184.1.5
    Interface                 Type St     Time last up          # Up trans
    ge-0/0/0.513(vc 513)      rmt   Up     Jul 31 18:43:52 2007           1
      Local interface: ge-0/0/0.513, Status: Up, Encapsulation: VLAN
      Remote PE: 10.184.1.5, Negotiated control-word: No
      Incoming label: 137152, Outgoing label: 969
        Time                  Event                   Interface/Lbl/PE
        Jul 31 18:43:52 2007 status update timer
        Jul 31 18:43:51 2007 PE route changed
        Jul 31 18:43:51 2007 Out lbl Update                       969
        Jul 31 18:43:51 2007 In lbl Update                     137152
        Jul 31 18:43:51 2007 loc intf up                 ge-0/0/0.513

Debugging the L2circuit neighboor i have the following:

Jul 31 18:52:48.828102 ADD      10.184.1.5:NoCtrlWord:4:513:Local/96 L2CKT    pref 7/0 metric <Hidden Int>
Jul 31 18:52:48.828173     Add route for l2ckt intf adv 10.184.1.5:NoCtrlWord:4:513:Local (label: 137152)
Jul 31 18:52:48.828540 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828637 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828803 rt_close: 2 routes proto l2 circuit
Jul 31 18:52:48.828803
Jul 31 18:52:48.828877     Insert/update vc 10.184.1.5:513
Jul 31 18:52:48.828914         new vc
Jul 31 18:52:48.829006         Insert/update vc L2CKT-NO-VC-ID
Jul 31 18:52:48.829064         circuit 0 updated to ge-0/0/0.513
Jul 31 18:52:48.829109         updated circuit 0 to ge-0/0/0.513, status UP
Jul 31 18:52:48.829154         add rti for ifl 268/16
Jul 31 18:52:48.829199         add nhi: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829300        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:48.829414         Ingress label changed to (137152)
Jul 31 18:52:48.829478         add rti for ifl 0 label 137152 op 0/36
Jul 31 18:52:48.829533         add route with prefix ifl 0 label 137152 op 0/36 and nexthop: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829807         updated ingress-label to 137152
Jul 31 18:52:48.829897         Egress VPN label changed to (969)
Jul 31 18:52:48.830001         Route to remote PE updated
Jul 31 18:52:48.830080         add nhi: indirect nexthop: 10.184.1.5, cw action NOOP bw 0bps
Jul 31 18:52:48.830168         add route with prefix ifl 268/16 and indirect nexthop: 10.184.1.5, cw action NOOP, bw 0bps
Jul 31 18:52:48.830784 task_timer_dispatch: returned from l2 circuit_Interface Change, rescheduled in 0
Jul 31 18:52:48.860334 rt_flash_update_callback: flash l2 circuit (l2circuit.0) start
Jul 31 18:52:48.860392 Flash call for L2CKT from l2ckt.0
Jul 31 18:52:48.860443 Flash processing complete for L2CKT from l2ckt.0
Jul 31 18:52:48.860499 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done
Jul 31 18:52:48.862357 Route flash received from mpls.0 : Flash
Jul 31 18:52:48.862435        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:50.756263 Recomputing the status of the VC for interface : ge-0/0/0.513
Jul 31 18:52:50.756434 VC Up for interface : ge-0/0/0.513
Jul 31 18:52:50.757227 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor : 10.184.1.5, VC-ID : 513) changed to UP
Jul 31 18:52:50.757310         vc (Neighbor : 10.184.1.5, VC-ID : 513) UP
Jul 31 18:52:50.758273 Intf ge-0/0/0.513 added to the Kernel VC status update Q
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

The problem is that i can't have conectivity end to end.
Everything looks great but i dont't have IP traffic.

Can sambody tell me if the following line can cause this issue?
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

Thanks a lot to all.

-- Telmo Javier Di Leva
------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

headers

Telmo Javier Di Leva | 3 Aug 2007 20:36

Re: : L2CIRCUIT - Cisco Juniper Interoperability Issue

Hi mr. Grewal/Sanjeewa :
My cisco box is a 7206 VXR NPE 300, and my juniper is a JM20.
The debug looks like this:
Aug 3 16:20:40.290603 Intf ge-0/0/0.513 (VC-ID 513) updated from signalled info: label 1033, encaps VLAN, cw-bit 1, mtu 1500, cb-size 0, vlan-id 65535

The cw-bit:1

Is really strange, because sometimes i can see the remote mac address, and the packets whit destination BROADCAST pass thru the l2circuit.... really srtange.....

The same configuration was checked in a 2821 cisco box and i have the same problem.
If you can help i'll really apreciate.
Best Regards

J S Grewal wrote:

Which Cisco box you are using? I faced same issue with Cisco 7600. But same thing works fine with Cisco 7200. Its Control-word negotiation issue. I observed Cisco 7600 send cbit:0 whereas Cisco 7200 sends cbit:1. If you can send me the details of your boxes i can try your config at my end and might able to give you more details.

rgds,

J.Grewal

----- Original Message -----

From: Telmo Javier Di Leva

To: mpls-ops <at> mplsrc.com

Sent: Thursday, August 02, 2007 3:08 AM

Subject: [MPLS-OPS]: L2CIRCUIT - Cisco Juniper Interoperability Issue

Dears all:

I have a trouble trying to bring up a L2CIRCUIT between CISCO and JUNIPER.

My Topology is: CE-PE-P-P-PE-CE.
The configuration of the VC on cisco is the following:

interface FastEthernet0/1.513
encapsulation dot1Q 513
no cdp enable
xconnect 200.62.0.39 513 pw-class TEST

The VC status is OK:

#sh mpls l2transport vc 513 detail
Local interface: Fa0/1.513 up, line protocol up, Eth VLAN 513 up
Destination address: 200.62.0.39, VC ID: 513, VC status: up
    Output interface: Gi2/0, imposed label stack {137152 113920}
    Preferred path: not configured
    Default path: active
    Tunnel label: 113920, next hop 200.61.128.254
Create time: 00:31:41, last status change time: 00:07:59
Signaling protocol: LDP, peer 200.62.0.39:0 up
    MPLS VC labels: local 969, remote 137152
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
    packet totals: receive 0, send 460
    byte totals:   receive 0, send 39560
    packet drops: receive 0, send 0

Configugation at Juniper:

> show configuration interfaces ge-0/0/0
vlan-tagging;
mtu 1548;
encapsulation vlan-ccc;

> show configuration interfaces ge-0/0/0 unit 513
encapsulation vlan-ccc;
vlan-id 513;

> show configuration protocols l2circuit
traceoptions {
    file L2CIRCUIT.TXT;
    flag all;
}
neighbor 10.184.1.5 {
    interface ge-0/0/0.513 {
        virtual-circuit-id 513;
        no-control-word;
        mtu 1500;
    }
}

The VC Status is ok too:

> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.184.1.5
    Interface                 Type St     Time last up          # Up trans
    ge-0/0/0.513(vc 513)      rmt   Up     Jul 31 18:43:52 2007           1
      Local interface: ge-0/0/0.513, Status: Up, Encapsulation: VLAN
      Remote PE: 10.184.1.5, Negotiated control-word: No
      Incoming label: 137152, Outgoing label: 969
        Time                  Event                   Interface/Lbl/PE
        Jul 31 18:43:52 2007 status update timer
        Jul 31 18:43:51 2007 PE route changed
        Jul 31 18:43:51 2007 Out lbl Update                       969
        Jul 31 18:43:51 2007 In lbl Update                     137152
        Jul 31 18:43:51 2007 loc intf up                 ge-0/0/0.513

Debugging the L2circuit neighboor i have the following:

Jul 31 18:52:48.828102 ADD      10.184.1.5:NoCtrlWord:4:513:Local/96 L2CKT    pref 7/0 metric <Hidden Int>
Jul 31 18:52:48.828173     Add route for l2ckt intf adv 10.184.1.5:NoCtrlWord:4:513:Local (label: 137152)
Jul 31 18:52:48.828540 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828637 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828803 rt_close: 2 routes proto l2 circuit
Jul 31 18:52:48.828803
Jul 31 18:52:48.828877     Insert/update vc 10.184.1.5:513
Jul 31 18:52:48.828914         new vc
Jul 31 18:52:48.829006         Insert/update vc L2CKT-NO-VC-ID
Jul 31 18:52:48.829064         circuit 0 updated to ge-0/0/0.513
Jul 31 18:52:48.829109         updated circuit 0 to ge-0/0/0.513, status UP
Jul 31 18:52:48.829154         add rti for ifl 268/16
Jul 31 18:52:48.829199         add nhi: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829300        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:48.829414         Ingress label changed to (137152)
Jul 31 18:52:48.829478         add rti for ifl 0 label 137152 op 0/36
Jul 31 18:52:48.829533         add route with prefix ifl 0 label 137152 op 0/36 and nexthop: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829807         updated ingress-label to 137152
Jul 31 18:52:48.829897         Egress VPN label changed to (969)
Jul 31 18:52:48.830001         Route to remote PE updated
Jul 31 18:52:48.830080         add nhi: indirect nexthop: 10.184.1.5, cw action NOOP bw 0bps
Jul 31 18:52:48.830168         add route with prefix ifl 268/16 and indirect nexthop: 10.184.1.5, cw action NOOP, bw 0bps
Jul 31 18:52:48.830784 task_timer_dispatch: returned from l2 circuit_Interface Change, rescheduled in 0
Jul 31 18:52:48.860334 rt_flash_update_callback: flash l2 circuit (l2circuit.0) start
Jul 31 18:52:48.860392 Flash call for L2CKT from l2ckt.0
Jul 31 18:52:48.860443 Flash processing complete for L2CKT from l2ckt.0
Jul 31 18:52:48.860499 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done
Jul 31 18:52:48.862357 Route flash received from mpls.0 : Flash
Jul 31 18:52:48.862435        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:50.756263 Recomputing the status of the VC for interface : ge-0/0/0.513
Jul 31 18:52:50.756434 VC Up for interface : ge-0/0/0.513
Jul 31 18:52:50.757227 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor : 10.184.1.5, VC-ID : 513) changed to UP
Jul 31 18:52:50.757310         vc (Neighbor : 10.184.1.5, VC-ID : 513) UP
Jul 31 18:52:50.758273 Intf ge-0/0/0.513 added to the Kernel VC status update Q
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

The problem is that i can't have conectivity end to end.
Everything looks great but i dont't have IP traffic.

Can sambody tell me if the following line can cause this issue?
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

Thanks a lot to all.

-- Telmo Javier Di Leva
------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-- Telmo Javier Di Leva Coordinador NOC Regional IFX Networks Personal mail: tdileva <at> ifxcorp.com NOC mail: noc <at> ifxnetworks.com Voice: (54-11) 5252-2003

headers

Sanjeewa Alahakone (sanjeewa | 6 Aug 2007 02:47

RE: : L2CIRCUIT - Cisco Juniper Interoperability Issue

Hi Telmo,

- What do you see for "show mpls l2 binding" in Cisco end?

- If I am not mistaken, the output taken from the Juniper end shows that the CW is not negotiated, is that correct ?

- What if you configure Juniper end to negotiate the CW ?

- Can you obtain an Ethereal capture ? as you are seeing strange behavior.

Thanks

Sanjeewa

From: Telmo Javier Di Leva [mailto:tdileva <at> ifxcorp.com]
Sent: Saturday, 4 August 2007 4:37 AM
To: J S Grewal
Cc: mpls-ops <at> mplsrc.com; sanjeewa <at> cisco.com; Ezequiel Carson; Elian Scrosoppi
Subject: Re: [MPLS-OPS]: L2CIRCUIT - Cisco Juniper Interoperability Issue

Hi mr. Grewal/Sanjeewa :
My cisco box is a 7206 VXR NPE 300, and my juniper is a JM20.
The debug looks like this:
Aug 3 16:20:40.290603 Intf ge-0/0/0.513 (VC-ID 513) updated from signalled info: label 1033, encaps VLAN, cw-bit 1, mtu 1500, cb-size 0, vlan-id 65535

The cw-bit:1

Is really strange, because sometimes i can see the remote mac address, and the packets whit destination BROADCAST pass thru the l2circuit.... really srtange.....

The same configuration was checked in a 2821 cisco box and i have the same problem.
If you can help i'll really apreciate.
Best Regards

J S Grewal wrote:

Which Cisco box you are using? I faced same issue with Cisco 7600. But same thing works fine with Cisco 7200. Its Control-word negotiation issue. I observed Cisco 7600 send cbit:0 whereas Cisco 7200 sends cbit:1. If you can send me the details of your boxes i can try your config at my end and might able to give you more details.

rgds,

J.Grewal

----- Original Message -----

From: Telmo Javier Di Leva

To: mpls-ops <at> mplsrc.com

Sent: Thursday, August 02, 2007 3:08 AM

Subject: [MPLS-OPS]: L2CIRCUIT - Cisco Juniper Interoperability Issue

Dears all:

I have a trouble trying to bring up a L2CIRCUIT between CISCO and JUNIPER.

My Topology is: CE-PE-P-P-PE-CE.
The configuration of the VC on cisco is the following:

interface FastEthernet0/1.513
encapsulation dot1Q 513
no cdp enable
xconnect 200.62.0.39 513 pw-class TEST

The VC status is OK:

#sh mpls l2transport vc 513 detail
Local interface: Fa0/1.513 up, line protocol up, Eth VLAN 513 up
Destination address: 200.62.0.39, VC ID: 513, VC status: up
    Output interface: Gi2/0, imposed label stack {137152 113920}
    Preferred path: not configured
    Default path: active
    Tunnel label: 113920, next hop 200.61.128.254
Create time: 00:31:41, last status change time: 00:07:59
Signaling protocol: LDP, peer 200.62.0.39:0 up
    MPLS VC labels: local 969, remote 137152
    Group ID: local 0, remote 0
    MTU: local 1500, remote 1500
    Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
    packet totals: receive 0, send 460
    byte totals:   receive 0, send 39560
    packet drops: receive 0, send 0

Configugation at Juniper:

> show configuration interfaces ge-0/0/0
vlan-tagging;
mtu 1548;
encapsulation vlan-ccc;

> show configuration interfaces ge-0/0/0 unit 513
encapsulation vlan-ccc;
vlan-id 513;

> show configuration protocols l2circuit
traceoptions {
    file L2CIRCUIT.TXT;
    flag all;
}
neighbor 10.184.1.5 {
    interface ge-0/0/0.513 {
        virtual-circuit-id 513;
        no-control-word;
        mtu 1500;
    }
}

The VC Status is ok too:

> show l2circuit connections extensive
Layer-2 Circuit Connections:

Legend for connection status (St)
EI -- encapsulation invalid      NP -- interface h/w not present
MM -- mtu mismatch               Dn -- down
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down
CM -- control-word mismatch      Up -- operational
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          XX -- unknown
NC -- intf encaps not CCC/TCC
CB -- rcvd cell-bundle size bad

Legend for interface status
Up -- operational
Dn -- down
Neighbor: 10.184.1.5
    Interface                 Type St     Time last up          # Up trans
    ge-0/0/0.513(vc 513)      rmt   Up     Jul 31 18:43:52 2007           1
      Local interface: ge-0/0/0.513, Status: Up, Encapsulation: VLAN
      Remote PE: 10.184.1.5, Negotiated control-word: No
      Incoming label: 137152, Outgoing label: 969
        Time                  Event                   Interface/Lbl/PE
        Jul 31 18:43:52 2007 status update timer
        Jul 31 18:43:51 2007 PE route changed
        Jul 31 18:43:51 2007 Out lbl Update                       969
        Jul 31 18:43:51 2007 In lbl Update                     137152
        Jul 31 18:43:51 2007 loc intf up                 ge-0/0/0.513

Debugging the L2circuit neighboor i have the following:

Jul 31 18:52:48.828102 ADD      10.184.1.5:NoCtrlWord:4:513:Local/96 L2CKT    pref 7/0 metric <Hidden Int>
Jul 31 18:52:48.828173     Add route for l2ckt intf adv 10.184.1.5:NoCtrlWord:4:513:Local (label: 137152)
Jul 31 18:52:48.828540 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828637 CHANGE   10.184.1.5:NoCtrlWord:4:513:Local/96 gw 200.62.x.y     L2CKT    pref 7/0 metric <Active Int>
Jul 31 18:52:48.828803 rt_close: 2 routes proto l2 circuit
Jul 31 18:52:48.828803
Jul 31 18:52:48.828877     Insert/update vc 10.184.1.5:513
Jul 31 18:52:48.828914         new vc
Jul 31 18:52:48.829006         Insert/update vc L2CKT-NO-VC-ID
Jul 31 18:52:48.829064         circuit 0 updated to ge-0/0/0.513
Jul 31 18:52:48.829109         updated circuit 0 to ge-0/0/0.513, status UP
Jul 31 18:52:48.829154         add rti for ifl 268/16
Jul 31 18:52:48.829199         add nhi: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829300        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:48.829414         Ingress label changed to (137152)
Jul 31 18:52:48.829478         add rti for ifl 0 label 137152 op 0/36
Jul 31 18:52:48.829533         add route with prefix ifl 0 label 137152 op 0/36 and nexthop: ifl ge-0/0/0.513, cw action NOOP
Jul 31 18:52:48.829807         updated ingress-label to 137152
Jul 31 18:52:48.829897         Egress VPN label changed to (969)
Jul 31 18:52:48.830001         Route to remote PE updated
Jul 31 18:52:48.830080         add nhi: indirect nexthop: 10.184.1.5, cw action NOOP bw 0bps
Jul 31 18:52:48.830168         add route with prefix ifl 268/16 and indirect nexthop: 10.184.1.5, cw action NOOP, bw 0bps
Jul 31 18:52:48.830784 task_timer_dispatch: returned from l2 circuit_Interface Change, rescheduled in 0
Jul 31 18:52:48.860334 rt_flash_update_callback: flash l2 circuit (l2circuit.0) start
Jul 31 18:52:48.860392 Flash call for L2CKT from l2ckt.0
Jul 31 18:52:48.860443 Flash processing complete for L2CKT from l2ckt.0
Jul 31 18:52:48.860499 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done
Jul 31 18:52:48.862357 Route flash received from mpls.0 : Flash
Jul 31 18:52:48.862435        Triggering VC status update timer for intf ge-0/0/0.513
Jul 31 18:52:50.756263 Recomputing the status of the VC for interface : ge-0/0/0.513
Jul 31 18:52:50.756434 VC Up for interface : ge-0/0/0.513
Jul 31 18:52:50.757227 RPD_LAYER2_VC_UP: State of Layer 2 VC (Neighbor : 10.184.1.5, VC-ID : 513) changed to UP
Jul 31 18:52:50.757310         vc (Neighbor : 10.184.1.5, VC-ID : 513) UP
Jul 31 18:52:50.758273 Intf ge-0/0/0.513 added to the Kernel VC status update Q
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

The problem is that i can't have conectivity end to end.
Everything looks great but i dont't have IP traffic.

Can sambody tell me if the following line can cause this issue?
Jul 31 18:52:50.859059 Kernel not updated with VC status for intf ge-0/0/0.513, NO IFL

Thanks a lot to all.

-- Telmo Javier Di Leva
------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-- Telmo Javier Di Leva Coordinador NOC Regional IFX Networks Personal mail: tdileva <at> ifxcorp.com NOC mail: noc <at> ifxnetworks.com Voice: (54-11) 5252-2003 ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

headers

Irwin Lazar | 13 Aug 2007 19:51

: MPLScon/FutureNet Presentations now available for download

FYI:

http://www.networkworld.com/newsletters/frame/2007/0806wan2.html

headers

Andrew Walding | 13 Aug 2007 21:30

Re: : MPLScon/FutureNet Presentations now available for download

Irwin,
I looked and looked - and this is an article on the fact you can download
them, but nowhere OBVIOUS was the link to download.  Can you clarify?
Thanks!
Andy

On Mon, August 13, 2007 12:51 pm, Irwin Lazar wrote:
> FYI:
>
> http://www.networkworld.com/newsletters/frame/2007/0806wan2.html
>
>
>

--

-- 
Regards,

Andy Walding
cell: 214-405-3708
google talk: awalding
Skype: awalding

headers

Natale, Bob | 13 Aug 2007 22:25

RE: : MPLScon/FutureNet Presentations now available for download

http://www.webtorials.com/main/FutureNet2007/index.htm 

-----Original Message-----
From: Andrew Walding [mailto:andyw <at> cellstream.com] 
Sent: Monday, August 13, 2007 3:30 PM
To: Irwin Lazar
Cc: mpls-ops <at> mplsrc.com
Subject: Re: [MPLS-OPS]: MPLScon/FutureNet Presentations now available
for download

Irwin,
I looked and looked - and this is an article on the fact you can
download
them, but nowhere OBVIOUS was the link to download.  Can you clarify?
Thanks!
Andy

On Mon, August 13, 2007 12:51 pm, Irwin Lazar wrote:
> FYI:
>
> http://www.networkworld.com/newsletters/frame/2007/0806wan2.html
>
>
>

--

-- 
Regards,

Andy Walding
cell: 214-405-3708
google talk: awalding
Skype: awalding

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

headers

Andrew Walding | 14 Aug 2007 00:30

RE: : MPLScon/FutureNet Presentations now available for download

Excellent - I actually did figure that out - by clicking on all the links,
one led to this.  Thanks!

On Mon, August 13, 2007 3:25 pm, Natale, Bob wrote:
> http://www.webtorials.com/main/FutureNet2007/index.htm
>
> -----Original Message-----
> From: Andrew Walding [mailto:andyw <at> cellstream.com]
> Sent: Monday, August 13, 2007 3:30 PM
> To: Irwin Lazar
> Cc: mpls-ops <at> mplsrc.com
> Subject: Re: [MPLS-OPS]: MPLScon/FutureNet Presentations now available
> for download
>
> Irwin,
> I looked and looked - and this is an article on the fact you can
> download
> them, but nowhere OBVIOUS was the link to download.  Can you clarify?
> Thanks!
> Andy
>
>
> On Mon, August 13, 2007 12:51 pm, Irwin Lazar wrote:
>> FYI:
>>
>> http://www.networkworld.com/newsletters/frame/2007/0806wan2.html
>>
>>
>>
>
>
> --
> Regards,
>
> Andy Walding
> cell: 214-405-3708
> google talk: awalding
> Skype: awalding
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>

--

-- 
Regards,

Andy Walding
cell: 214-405-3708
google talk: awalding
Skype: awalding

headers

Akshay Balhara | 17 Aug 2007 14:20

: Enabling Internet in MPLS Network

Dear All,

Tell me How I enable Internet in MPLS Network.

Regards,
Akshay Balhara

8	May 2011
27	April 2011
3	April 2010
6	November 2009
1	October 2009
1	September 2009
13	August 2009
4	July 2009
1	June 2009
3	May 2009
3	April 2009
12	March 2009
4	February 2009
9	January 2009
4	November 2008
6	October 2008
2	September 2008
3	August 2008
2	July 2008
11	June 2008
1	May 2008
1	April 2008
3	March 2008
13	February 2008
10	January 2008
16	December 2007
15	November 2007
19	October 2007
27	September 2007
37	August 2007
15	July 2007
24	June 2007
41	May 2007
27	April 2007
17	March 2007
11	February 2007
14	January 2007
7	December 2006
13	November 2006
1	October 2006
20	August 2006
1	July 2006
3	May 2006
5	April 2006
4	March 2006
1	February 2006
7	January 2006
39	December 2005
35	November 2005
14	October 2005
27	September 2005
12	August 2005
25	July 2005
15	June 2005
55	May 2005
65	April 2005
27	March 2005
55	February 2005
58	January 2005
20	December 2004
61	November 2004
60	October 2004
182	September 2004
159	August 2004
50	July 2004
47	June 2004

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31