cisco & juniper l2circuit interoperability issue

[diegosaav]

Hi folks,

After reading some docs about configuration options between them I have not connectivity yet.

My topology is as follow:

CEside <> JuniperM20 <> JuniperM20 <> Cisco7606 <> CEside

The configs:

neighbor y.y.y.y {

    interface ge-2/0/0.1950 {

        virtual-circuit-id 1950;

        no-control-word;

        mtu 1500;

        ignore-encapsulation-mismatch;

        ignore-mtu-mismatch;

    }

show configuration interfaces ge-2/0/0.1950

encapsulation vlan-ccc;

vlan-id 1950;

family ccc;

sh run int g1/14.1950

interface GigabitEthernet1/14.1950

description PW-TEST-ING

encapsulation dot1Q 1950

xconnect x.x.x.x 1950 encapsulation mpls

end

Some troubleshooting commands:

Cisco side:

sh mpls l2transport vc detail

Local interface: Gi1/14.1950 up, line protocol up, Eth VLAN 1950 up

  Destination address: x.x.x.x, VC ID: 1950, VC status: down

    Output interface: none, imposed label stack {}

    Preferred path: not configured 

    Default path: no route

    No adjacency

  Create time: 1d18h, last status change time: 1d18h

  Signaling protocol: LDP, peer x.x.x.x: up

    Targeted Hello: y.y.y.y(LDP Id) -> x.x.x.x

    MPLS VC labels: local 1697, remote unassigned

    Group ID: local 0, remote unknown

    MTU: local 1500, remote unknown

    Remote interface description:

  Sequencing: receive disabled, send disabled

  VC statistics:

    packet totals: receive 0, send 0

    byte totals:   receive 0, send 0

    packet drops:  receive 0, send 0

Juniper side:

show l2circuit connections neighbor y.y.y.y | find ^Neighbor   

Neighbor: y.y.y.y

    Interface                 Type  St     Time last up          # Up trans

    ge-2/0/0.1950(vc 1950)    rmt   VC-Dn  -----                          0

      Remote PE: y.y.y.y, Negotiated control-word: No Encapsulation: ETHERNET

      Incoming label: 589520, Outgoing label: 1697

      Local interface: ge-2/0/0.1950, Status: Up, Encapsulation: VLAN

Juniper logs:

Jul 26 15:09:16.063733 [add] l2circuit VC l2ckt_vc_adv_recv (cw-bit 0, encaps ETHERNET, vc-id 1950,label 1697, mtu 1500, cb-size 0, no vlan-id, TDM payload size 0 bytes,  TDM bitrate 0 (xDS0)) received from PE y.y.y.y

Jul 26 15:09:16.063823 [l2ckt_vc_adv_recv] Intf ge-2/0/0.1950 (VC-ID 1950) updated from signalled info: label 1697, encaps ETHERNET, cw-bit 0, mtu 1500, cb-size 0,  TDM payload size 0 (bytes), TDM bitrate 0 (xDS0) no vlan-id

Jul 26 15:09:16.065538        Triggering VC status update timer for intf ge-2/0/0.1950

Jul 26 15:09:16.114307 [vc_intf_vc_status_update] Recomputing the status of the VC for interface : ge-2/0/0.1950

Jul 26 15:09:16.114335 vc_intf_vc_status_update] interface : ge-2/0/0.1950 vc status = intf Up : intf_up = TRUE

Jul 26 15:09:16.114360 [vc_intf_vc_status_update] interface : ge-2/0/0.1950 UP adv_down = 0 : vc_down = 0, ccc_up = 1

Jul 26 15:09:16.114383 vc_intf_vc_status_update] interface : ge-2/0/0.1950 VC PRESENT

Jul 26 15:09:16.114453 [vc_intf_vc_status_update] interface : ge-2/0/0.1950 Done Computing adv, vc down and ccc_up status adv_down = 1, vc_down = 1, ccc_up = 0

Any ideas would be appreciated.

Thx!

-d

[Harold Ritter]

Hi Diego,

Do you have an functionning LSP from the Cisco to the Juniper? Can you do a "show ip cef x.x.x.x int" from the Cisco side.

Regards

[diegosaav]

Hi Harold,

There is the output of "show ip cef x.x.x.x int" command from the Cisco rtr.

#sh ip cef x.x.x.x internal

x.x.x.x/32, epoch 9, RIB[S], refcount 6, per-destination sharing

  sources: RIB

  feature space:

   LFD: x.x.x.x/32 1 local label

   local label info: global/1699

        contains path extension list

        disposition chain 0x547E5088

        label switch chain 0x547E5088

   IPRM: 0x00058000

   Broker: linked

  ifnums:

   GigabitEthernet2/15(35): y.y.y.y <<<< /30 link between c7606 <> jm20

   path_list contains at least one resolved destination(s). HW not notified

  path 53503608, path list 4571D938, share 1/1, type recursive, for IPv4

  recursive via y.y.y.y[IPv4:Default], fib 45615D2C, 1 terminal fib

    path 53504244, path list 4571DD58, share 1/1, type adjacency prefix, for IPv4

      MPLS long path extensions: MOI flags = 0x0 label 300512

    attached to GigabitEthernet2/15 label 300512, adjacency IP adj out of GigabitEthernet2/15, addr y.y.y.y

53747800

  long extension for path if GigabitEthernet2/15 next hop y.y.y.y:

    MPLS long path extensions: MOI flags = 0x0 label 300512

  output chain: label 300512 TAG adj out of GigabitEthernet2/15, addr y.y.y.y 53745E80

and...

#show mpls forwarding-table x.x.x.x

Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop   

Label  Label or VC   or Tunnel Id      Switched      interface             

1699   300512        x.x.x.x/32   51172         Gi2/15     y.y.y.y

Many thx for your time!

-d

[Harold Ritter]

Hi Diego,

What IOS version do you run on the 7606?

Regards

[diegosaav]

Hi Harold,

Sorry for the delay, the IOS version that we're running on the C7606 is:

#sh ver | i IOS

Cisco IOS Software, c7600s3223_rp Software (c7600s3223_rp-ADVIPSERVICESK9-M), Version 12.2(33)SRB7, RELEASE SOFTWARE (fc1)

Thx,

-d

[Harold Ritter]

Hi Diego,

This is a pretty old version of IOS. I would recommend you upgrade to something more recent before proceeding with more troubleshooting.

Regards

[diegosaav]

Hi Harold,

Which version of IOS do you recommend to upgrade based on the following features of the box?

cisco CISCO7606-S (R7000) processor (revision 1.1) with 983040K/65536K bytes of memory.

Processor board ID FOX1340GJxx

R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache

Last reset from power-on

35 Virtual Ethernet interfaces

146 Gigabit Ethernet interfaces

1915K bytes of non-volatile configuration memory.

65536K bytes of Flash internal SIMM (Sector size 512K).

Configuration register is 0x2102

Thx,

-d

[Harold Ritter]

Hi Diego,

I would recommend the latest version (15.3(1)S2). You currently do not have enough flash memory and will therefore need to upgarde.

Regards

[diegosaav]

Thx Harold, we'll be upgrading to the latest version and keep you posted.

-d

[Jerems]

Old thread but new potential answer

On juniper side "encapsulation-type ethernet" instead of "encapsulation-type ethernet-vlan" should help