The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Sep> msg00181



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: L2Circuit - Cisco Juniper Interoperability

  • From: sthaug@nethelp.no
  • Date: Thu, 30 Sep 2004 10:43:39 +0200
  • Cc: david_a_carver@hotmail.com, mpls-ops@mplsrc.com
  • Resent-Date: Thu, 30 Sep 2004 05:11:06 -0400

> VLAN-CCC is Juniper properietry protocol. You need to
> use PWE3 in both sides.

"l2circuit" is Juniper speak for a normal Martini tunnel, which works
fine between Cisco and Juniper. We have many of these in production.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

> 
> Thanks
> Hakeem
> 
> --- David Carver <david_a_carver@hotmail.com> wrote:
> 
> > Hello All,
> > 
> > Would really appreciate any help on this...
> > 
> > I am trying to conifgure a l2circuit between Juniper
> > and Cisco with no luck. 
> >   I get the following output:
> > 
> > Juniper:
> > 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: 166.164.4.17
> >     Interface                 Type  St     Time last
> > up          # Up trans
> >     ge-0/2/0.5(vc 55)         rmt   OL
> > 
> > Cisco:
> > PE.JFK#show mpls l2transport vc 55 detail
> > Local interface: Fa0/1/0.5 up, line protocol up, Eth
> > VLAN 555 up
> >   Destination address: 166.164.4.16, VC ID: 55, VC
> > status: down
> >     Preferred path: Tunnel1,  entry had no valid
> > path
> >     Default path: disabled
> >     Output interface: unknown, imposed label stack
> > {}
> >   Create time: 00:25:42, last status change time:
> > 00:25:42
> >   Signaling protocol: LDP, peer 166.164.4.16:0 down
> >     MPLS VC labels: local 17, remote unassigned
> >     Group ID: local 2, remote unknown
> >     MTU: local 1500, remote unknown
> >     Remote interface description:
> >   Sequencing: receive disabled, send disabled
> >   Sequence number: receive 0, send 0
> >   VC statistics:
> >     packet totals: receive 0, send 0
> >     byte totals:   receive 0, send 0
> >     packet drops:  receive 0, seq error 0, send 0
> > 
> > 
> > 
> > My configuration is as follows:
> > 
> > Juniper:
> > interfaces {
> >     ge-0/2/0 {
> >         vlan-tagging;
> >         encapsulation vlan-ccc;
> >         unit 0 {
> >             vlan-id 3;
> >             family inet;
> >             family iso;
> >             family mpls;
> >         }
> >         unit 5 {
> >             encapsulation vlan-ccc;
> >             vlan-id 555;
> >         }
> >     }
> >     fe-0/1/2 {
> >         unit 0 {
> >             enable;
> >             family inet {
> >                 address 166.164.4.16/16;
> >             }
> >             family iso;
> >             family mpls;
> > }
> > protocols {
> >     ldp {
> >         interface all;
> >     }
> > }
> > 
> > Cisco:
> > ip cef
> > mpls label protocol ldp
> > mpls traffic-eng tunnels
> > pseudowire-class aaa
> > encapsulation mpls
> > preferred-path interface Tunnel1 disable-fallback
> > !
> > interface FastEthernet0/0/0
> > ip address 166.164.4.17 255.255.255.0
> > no ip directed-broadcast
> > ip router isis
> > media-type MII
> > full-duplex
> > mpls label protocol ldp
> > mpls traffic-eng tunnels
> > tag-switching ip
> > !
> > interface FastEthernet0/1/0
> > ip address 10.10.10.28 255.255.255.0
> > no ip directed-broadcast
> > media-type MII
> > mpls label protocol ldp
> > tag-switching ip
> > no clns route-cache
> > !
> > interface FastEthernet0/1/0.5
> > encapsulation dot1Q 555
> > no ip directed-broadcast
> > xconnect 166.164.4.16 55 pw-class aaa
> > !
> > 
> > I do have two tunnels going from the Cisco to the
> > Juniper and vice-versa 
> > (destination of each tunnel is the ip address on the
> > loopback).
> > 
> > Any clues???
> > 
> > Thanks,
> > David
> > 
> >
> _________________________________________________________________
> > Get ready for school! Find articles, homework help
> > and more in the Back to 
> > School Guide!
> > http://special.msn.com/network/04backtoschool.armx
> > 
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe: 
> > http://www.mplsrc.com/mplsops.shtml
> > Archive:
> > http://www.mplsrc.com/mpls-ops_archive.shtml
> > 
> 
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail
> 
> -------
> 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