The MPLS-OPS Archive

[<Jack.W.Parks@alltel.com>]

[It looks like] LDP has not formed a neighbor adjacency.  Your routers
are not exchanging labels

-----Original Message-----
From: David Carver [mailto:david_a_carver@hotmail.com] 
Sent: Monday, September 27, 2004 4: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
******************************************************************************************
The information contained in this message, including attachments, may contain 
privileged or confidential information that is intended to be delivered only to the 
person identified above. If you are not the intended recipient, or the person 
responsible for delivering this message to the intended recipient, ALLTEL requests 
that you immediately notify the sender and asks that you do not read the message or its 
attachments, and that you delete them without copying or sending them to anyone else. 


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