The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] RE: L2Circuit - Cisco Juniper Interoperability
> Hmmmmmm.......... OOPS! Not quite working.
>
> On the Juniper side, everything looks great. Cisco still reports the tunnel
> as down.
Have you made the Martini tunnel to use the LSP (your Tunnel1)? Either
by using a pseudowire-class for the xconnect:
pseudowire-class l2c
encapsulation mpls
preferred-path interface Tunnel1 disable-fallback
!
interface FastEthernet0/1/0.5
encapsulation dot1Q 55
xconnect 4.4.4.4 55 pw-class l2c
or by using "tunnel mpls traffic-eng autoroute announce" on Tunnel1.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
>
> Cisco:
> PE.JFK#show mpls l2transport vc 55 detail
> Local interface: Fa0/1/0.5 up, line protocol up, Eth VLAN 55 up
> Destination address: 4.4.4.4, 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:08:34, last status change time: 00:04:27
> Signaling protocol: LDP, peer 4.4.4.4:0 up
> MPLS VC labels: local 22, remote 102496
> Group ID: local 0, remote 0
> MTU: local 1500, remote 1500
> Remote interface description:
> Remote VLAN id: 55
> 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
>
>
> Juniper:
> codaware@PE.SFO> 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: 28.28.28.28
> Interface Type St Time last up # Up trans
> fe-0/1/0.5(vc 55) rmt Up Sep 28 21:41:54 2004 1
> Local interface: fe-0/1/0.5, Status: Up, Encapsulation: VLAN
> Remote PE: 28.28.28.28, Negotiated control-word: Yes (Null)
> Incoming label: 102496, Outgoing label: 22
> Time Event Interface/Lbl/PE
> Sep 28 21:41:54 2004 status update timer
> Sep 28 21:41:52 2004 PE route changed
> Sep 28 21:41:52 2004 Out lbl Update 22
> Sep 28 21:41:52 2004 In lbl Update 102496
> Sep 28 21:41:52 2004 loc intf up fe-0/1/0.5
>
>
>
>
> Thanks,
> David
>
>
>
>
> >From: "David Carver" <david_a_carver@hotmail.com>
> >To: r.amos@zahav.net.il
> >CC: mpls-ops@mplsrc.com
> >Subject: RE: [MPLS-OPS]: L2Circuit - Cisco Juniper Interoperability
> >Date: Mon, 27 Sep 2004 22:18:54 +0000
> >
> >Thanks! It worked.
> >
> >I changed the l2circuit to be between loopback interfaces and it all works
> >now.
> >
> >(Regarding the IP addresses - that is another oops... ;) - Thanks!)
> >
> >David
> >
> >
> >>From: "Amos Rosenboim" <r.amos@zahav.net.il>
> >>To: "David Carver" <david_a_carver@hotmail.com>
> >>Subject: RE: [MPLS-OPS]: L2Circuit - Cisco Juniper Interoperability
> >>Date: Tue, 28 Sep 2004 00:03:57 +0200
> >>
> >>Couple of comments that I cannot say for sure that are relevant
> >>specifically to this problem but they might are:
> >>Why is the l2circuit configuration not between loopback interfaces ip
> >>addresses? It's a good practice to initiate such sessions (ldp sessions
> >>actually) from a loopback.
> >>
> >>Second issue - according to the configs you sent the routers are on the
> >>same ethernet segments but are configured with different subnetmasks -
> >>/16 for the juniper and a /24 for the cisco. This has probably nothing
> >>to do with the problem but anyway it's not so good.
> >>
> >>Amos
> >>
> >>
> >>-----Original Message-----
> >>From: David Carver [mailto:david_a_carver@hotmail.com]
> >>Sent: Monday, September 27, 2004 11:57 PM
> >>To: Amos Rosenboim; mpls-ops@mplsrc.com
> >>Subject: RE: [MPLS-OPS]: L2Circuit - Cisco Juniper Interoperability
> >>
> >>
> >>OOPS!
> >>
> >>Here is the l2circuit config from the Juniper:
> >>
> >>l2circuit {
> >> neighbor 166.164.4.17 {
> >> interface ge-0/2/0.5 {
> >> virtual-circuit-id 55;
> >> }
> >> }
> >>}
> >>
> >>Thanks,
> >>David
> >>
> >> >From: "Amos Rosenboim" <r.amos@zahav.net.il>
> >> >To: "David Carver" <david_a_carver@hotmail.com>,<mpls-ops@mplsrc.com>
> >> >Subject: RE: [MPLS-OPS]: L2Circuit - Cisco Juniper Interoperability
> >> >Date: Mon, 27 Sep 2004 23:51:06 +0200
> >> >
> >> >Hi,
> >> >
> >> >First you didn't enclose any l2circuit configuration from the juniper
> >> >side.
> >> >From looking at the cisco show command outputs you can clearly see that
> >> >the direct ldp session between the routers is down.
> >> >Try and debug ldp adjacency on either side.
> >> >Since I didn't see the l2circuit config for the juniper I could not
> >>tell
> >> >weather it's configured ok. The cisco config looks just fine.
> >> >
> >> >Hope this helps somewhat.
> >> >
> >> >Amos
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: David Carver [mailto:david_a_carver@hotmail.com]
> >> >Sent: Monday, September 27, 2004 11:08 PM
> >> >To: mpls-ops@mplsrc.com
> >> >Subject: [MPLS-OPS]: L2Circuit - Cisco Juniper Interoperability
> >> >
> >> >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
> >>
> >>_________________________________________________________________
> >>Express yourself instantly with MSN Messenger! Download today - it's
> >>FREE!
> >>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >>
> >
> >_________________________________________________________________
> >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
>
> _________________________________________________________________
> Don’t just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
> -------
> 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
|
|