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

LDP Error Message--LDP Feature Set Manager: State Initialized

Hello Everyone,

i  ran the LDP on OSPF within BGP, both ospf and bgp connections were up.  the loopback interfaces between two peers were also pingable each other.  but LDP neighbor came never up. With Debug mpls ldp transport  connection was following log output showed

debug mpls ldp transport events

LDP transport connection events debugging is on

switch-1#

*Apr  6 13:15:44.127: ldp: Opening ldp conn; adj 0x4A2AE790, 172.16.249.45 <-> 172.16.249.2; with normal priority

*Apr  6 13:15:44.127: ldp: No MD5 password protection for peer 172.16.249.2:0

*Apr  6 13:15:44.127: ldp: Registered TCB with LDP TCB database tcb 0x54FC8E40 [key 8775], total 1

*Apr  6 13:15:44.139: ldp: ldp conn is up; adj 0x4A2AE790, 172.16.249.45:43370 <-> 172.16.249.2:646

*Apr  6 13:15:44.175: ldp: Close LDP transport conn for adj 0x4A2AE790

*Apr  6 13:15:44.175: ldp: Unregistered from LDP TCB database tcb 0x54FC8E40 [key 8775], total 0

*Apr  6 13:15:44.175: ldp: Closing ldp conn 172.16.249.45:43370 <-> 172.16.249.2:646, adj 0x4A2AE790

*Apr  6 13:16:04.279: ldp: Scan listening TCBs

switch-1#show mpls ldp parameters

LDP Feature Set Manager: State Initialized

  LDP features:

    Basic

    IP-over-MPLS

    TDP

Protocol version: 1

Session hold time: 180 sec; keep alive interval: 60 sec

Discovery hello: holdtime: 15 sec; interval: 5 sec

Discovery targeted hello: holdtime: 90 sec; interval: 10 sec

Downstream on Demand max hop count: 255

LDP for targeted sessions

LDP initial/maximum backoff: 15/120 sec

LDP loop detection: off

switch-1#show mpls ldp neighbor ------

--------------------------------------------this is empty,no neighor

switch-1#

*Apr  6 13:18:01.915: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:04.131: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:04.131: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:04.279: ldp: Scan listening TCBs

*Apr  6 13:18:06.063: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:08.131: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:08.131: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:10.075: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:12.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:12.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:14.047: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:16.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:16.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:19.027: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:20.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:20.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:22.835: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:24.131: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:24.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:27.215: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:28.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:28.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:31.183: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:32.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:32.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:35.087: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:36.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:36.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

*Apr  6 13:18:39.879: ldp: Send ldp hello; GigabitEthernet2/6/3, src/dst 172.16.65.86/224.0.0.2, inst_id 0

*Apr  6 13:18:40.135: ldp: Rcvd ldp hello; GigabitEthernet2/6/3, from 172.16.249.2 (172.16.249.2:0), intf_id 0, opt 0xC

*Apr  6 13:18:40.135: ldp: Ignore LDP Hello from 172.16.249.2, GigabitEthernet2/6/3; backoff from failed session

Everyone's tags (3)
8 REPLIES
New Member

LDP Error Message--LDP Feature Set Manager: State Initialized

switch-1#show mpls ldp disc

Local LDP Identifier:

    172.16.249.45:0

    Discovery Sources:

    Interfaces:

    GigabitEthernet2/6/3 (ldp): xmit

eceiving LDP link hello's from the

neighboring router, on both sides.It only shows "xmit", but not "recv".

I make sure that the loopback0 has  a host route (/32) to the LDP router ID of the

neighboring router

LDP Error Message--LDP Feature Set Manager: State Initialized

what about the passwords?

New Member

LDP Error Message--LDP Feature Set Manager: State Initialized

no Configure any LDP MD5 Password

LDP Error Message--LDP Feature Set Manager: State Initialized

are u sumarizing the routes in between?

are there any ACL's in between?

is the mpls ip configured on all relevant interfaces?

are you using the "mpls ldp router-id loopback0 force" command  on both sides.

check all of above and maybe it should help you find some direction

HTH

Kishore

New Member

Re: LDP Error Message--LDP Feature Set Manager: State Initialize

Check the cef too

Sent from Cisco Technical Support iPhone App

New Member

LDP Error Message--LDP Feature Set Manager: State Initialized

Do you permit targeted LDP by

mpls ldp discovery targeted-hello accept ... ?

Regards,

Sergey

biZ
New Member

Re: LDP Error Message--LDP Feature Set Manager: State Initialized

***
New Member

LDP Error Message--LDP Feature Set Manager: State Initialized

Did you ever fix this problem.  I seem to be having the same problem and can't figure it out.

1817
Views
5
Helpful
8
Replies
CreatePlease to create content