Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cisco huawei mpls l2vpn

Hi All,

 

While i m doing for the remote ldp formation between this devices of cisco 3600 & huawei 5700,

attached the configs of these 2 nodes.what could be the possible reason for this..

witch(config-router)#do sh mpls l2 vc

Local intf     Local circuit              Dest address    VC ID      Status
-------------  -------------------------- --------------- ---------- ----------
Vl2292         Eth VLAN 2292              10.50.1.1       2292       DOWN
VFI 2293       vfi                        10.50.1.1       2293       DOWN

Switch(config-router)#do sh mpls l2 vc det
Local interface: Vl2292 down, line protocol down, Eth VLAN 2292 down
  Destination address: 10.50.1.1, VC ID: 2292, VC status: down
    Last error: Local peer access circuit is down
    Output interface: none, imposed label stack {}
    Preferred path: not configured
    Default path: no route
    No adjacency
  Create time: 04:16:50, last status change time: 04:20:09
    Last label FSM state change time: 04:16:49
  Signaling protocol: LDP, peer unknown
    Targeted Hello: 10.50.2.2(LDP Id) -> 10.50.1.1, LDP is DOWN, no binding
    Graceful restart: not configured and not enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/None (no remote binding)

Thanks

anand

4 REPLIES
Cisco Employee

Hi Anand,The targeted LDP

Hi Anand,

The targeted LDP session is down between 10.50.1.1 and 10.50.2.2. Can you check the LDP discovery output  and see if the LDP neighbors are reachable?. You can use "show mpls ldp discovery". Try to ping 10.50.1.1 with source as 10.50.2.2. 

In order to have the VC up, you need the T-LDP session up and also the interface (on which you have VFI/xconnect) enabled to be up. 

 

-Nagendra

 

New Member

Hi Nagendra,Couldnt find the

Hi Nagendra,

Couldnt find the neighbor & the ping isnt successful, but there is discovery & binding-local found in;

can you suggest further please.

Switch#sh mpls ldp discovery
 Local LDP Identifier:
    10.50.2.2:0
    Discovery Sources:
    Interfaces:
        Vlan21 (ldp): xmit
    Targeted Hellos:
        10.50.2.2 -> 10.50.1.1 (ldp): active, xmit

Switch#sh mpls ldp neighbo

Switch#sh mpls ldp bindings
  lib entry: 10.50.2.2/32, rev 2
        local binding:  label: imp-null
  lib entry: 10.50.11.48/30, rev 4
        local binding:  label: imp-null
Switch#ping 10.50.11.50(RTO)

Switch#ping 10.50.1.1 source 10.50.2.2(RTO)

Thanks

Kumar

New Member

Hi Nagendra,This is directly

Hi Nagendra,

This is directly connected switch for which i ma trying to establish a remote ldp,

sh mpls interfaces, states the tu1 as down, is there anything wrong in here

Switch# show mpls interfaces
Interface              IP            Tunnel   BGP Static Operational
Vlan21                 Yes (ldp)     No       No  No     Yes
Tunnel1                Yes           No       No  No     No

interface Tunnel1
 ip unnumbered Loopback0
 mpls ip
 mpls label protocol ldp
 tunnel destination 10.50.1.1
end

also the preferre path in

pseudowire-class TEST
 ! Incomplete config [Unconfigured or invalid tunnel interface]
 encapsulation mpls
 preferred-path interface Tunnel1 disable-fallback
  ! Incomplete or invalid tunnel interface
!

Please suggest on this..

Thanks

kumar

 

 

Cisco Employee

Hi,        10.50.2.2 -> 10.50

Hi,

        10.50.2.2 -> 10.50.1.1 (ldp): active, xmit

You are not receiving LDP hellos from huawei. Also since ping itself is failing it appears to have issue with basic connectivity. Please check your routing entries to make sure you have connectivity between these 2 nodes for LDP session establishment.

1402
Views
0
Helpful
4
Replies