• Skip to main content
  • Skip to header right navigation
  • Skip to site footer

Roger Perkin

Network Automation Architect

  • Network Automation
    • Network Automation Courses
    • What is NetDevOps?
    • Workflow Orchestration
    • Ansible Automation Platform
    • Ansible Workshop
    • What is Network Automation?
    • Network Automation Tools
    • ContainerLab
    • Ansible Training
      • What is Ansible?
      • Ansible Tutorial for Beginners
      • Ansible Network Automation
      • Ansible Inventory Example
    • Python Network Automation
      • Nornir
      • Python Network Automation Course
      • Python for Network Engineers
      • Python VENV / Virtual Environment Tutorial
      • Python Tutorial for Beginners
      • pyATS
    • Network Source of Truth
      • NetBox
      • Infrahub
      • NautoBot
    • NetDevops
    • DevOps Tutorial
      • Git Training
      • Terraform Training
      • Linux Training
      • Kubernetes Training
      • Devops Training Course
      • Azure Devops Training
    • Terraform
    • GIT
      • Git Commands
      • What is GitHub?
    • Docker Training
    • Confluence
    • Microsoft Azure
  • Cisco
    • ISE
    • SD WAN Training
    • Password Recovery
    • Software-Upgrade-Guides
    • BGP
    • Data Center
    • WIRELESS
  • CCIE
  • Blog
  • About
    • My Red Special Guitar
  • Contact

MPLS LDP Troubleshooting

Home » CCIE Certification » MPLS

When faced with a troubleshooting ticket involving MPLS you need to clear the basics first to ensure that everything is working from a Label Distribution perspective.

  1. First establish IGP connectivity between all the routers. 
  2. Can you ping all the loopbacks?
  3. Are there /32 loopbacks configured on every router and advertised into IGP?
  4. Is CEF enabled?
  5. Is MPLS IP enabled on the required interfaces?
  6. Have the routers discovered any LDP neighbors?

I have put together this quick list of commands that I would run on each router to quicky verify that Label Distribution is working

sh run | inc ip cef
sh run | inc mpls ip
sh mpls interface
sh mpls ldp disco
sh mpls ldp neigh

When applied to a router in a working MPLS Core the output should look like below

R21#sh run | inc mpls ip
 mpls ip
 mpls ip
 mpls ip
 mpls ip
 R21#sh run | inc ip cef
 ip cef
 R21#sh run | inc mpls ip
 R21#sh mpls interface
 Interface IP Tunnel Operational
 FastEthernet0/0 Yes (ldp) No Yes
 FastEthernet0/1 Yes (ldp) No Yes
 FastEthernet1/0 Yes (ldp) No Yes
 FastEthernet2/0 Yes (ldp) No Yes
 R21#sh mpls ldp neigh
 Peer LDP Ident: 22.22.22.22:0; Local LDP Ident 21.21.21.21:0
 TCP connection: 22.22.22.22.24740 - 21.21.21.21.646
 State: Oper; Msgs sent/rcvd: 294/292; Downstream
 Up time: 04:02:51
 LDP discovery sources:
 FastEthernet0/1, Src IP addr: 172.16.1.2
 Addresses bound to peer LDP Ident:
 172.16.1.0 172.16.1.2 22.22.22.22
 Peer LDP Ident: 172.16.1.9:0; Local LDP Ident 21.21.21.21:0
 TCP connection: 172.16.1.9.51621 - 21.21.21.21.646
 State: Oper; Msgs sent/rcvd: 210/213; Downstream
 Up time: 02:48:22
 LDP discovery sources:
 FastEthernet1/0, Src IP addr: 172.16.1.9
 Addresses bound to peer LDP Ident:
 172.16.1.9 24.24.24.24 172.16.1.10
 Peer LDP Ident: 26.26.26.26:0; Local LDP Ident 21.21.21.21:0
 TCP connection: 26.26.26.26.43548 - 21.21.21.21.646
 State: Oper; Msgs sent/rcvd: 118/119; Downstream
 Up time: 01:27:44
 LDP discovery sources:
 FastEthernet2/0, Src IP addr: 172.16.1.15
 Addresses bound to peer LDP Ident:
 172.16.1.15 26.26.26.26 172.16.1.13
 Peer LDP Ident: 23.23.23.23:0; Local LDP Ident 21.21.21.21:0
 TCP connection: 23.23.23.23.62234 - 21.21.21.21.646
 State: Oper; Msgs sent/rcvd: 28/28; Downstream
 Up time: 00:11:03
 LDP discovery sources:
 FastEthernet0/0, Src IP addr: 172.16.1.4
 Addresses bound to peer LDP Ident:
 172.16.1.4 23.23.23.23 172.16.1.6
 R21#sh run | inc ip cef
 ip cef
 R21#sh run | inc mpls ip
 R21#sh mpls interface
 Interface IP Tunnel Operational
 FastEthernet0/0 Yes (ldp) No Yes
 FastEthernet0/1 Yes (ldp) No Yes
 FastEthernet1/0 Yes (ldp) No Yes
 FastEthernet2/0 Yes (ldp) No Yes
 R21#sh mpls ldp disco
 Local LDP Identifier:
 21.21.21.21:0
 Discovery Sources:
 Interfaces:
 FastEthernet0/0 (ldp): xmit/recv
 LDP Id: 23.23.23.23:0
 FastEthernet0/1 (ldp): xmit/recv
 LDP Id: 22.22.22.22:0
 FastEthernet1/0 (ldp): xmit/recv
 LDP Id: 172.16.1.9:0; no host route
 FastEthernet2/0 (ldp): xmit/recv
 LDP Id: 26.26.26.26:0

This LDP Troubleshooting was taken from an MPLS L3VPN Tutorial which I posted here – MPLS L3VPN Configuration Tutorial –

Category: MPLS
ansible course for network engineers
Get Access to my Ansible Course NOW
Previous Post:How to Shutdown Port Juniper EX4200
Next Post:How to Study for the CCIE Lab Exam

Sidebar

Hi I'm Roger Perkin,
Based in the UK working as a Network Automation Architect, CCIE #50038
About Roger | Twitter | Linkedin

python course for network engineers

Topics

Network Automation
Ansible
Python for Network Automation
CCIE
Cisco ISE
F5 Certification
BGP
OSPF
Network Automation Conferences
auvik promo banner
Pluralsight Trial

Git for Network Engineers

Ansible vs Nornir

Start learning today with my Network Automation Courses

Master Ansible, Python, Git, Nornir, Jenkins and more..


Buy me a coffeeBuy me a coffee

ansible network automation course

Have you seen my YouTube Channel?

YouTube Subscribe

Let’s get started

Take a look at my premium courses on Ansible, Nornir & Git or buy them all with the Network Automation Bundle!

Network Automation Courses

Navigation

Python VENV Tutorial
Python for Network Engineers

Network Automation
Network Automation Courses
Network Discovery Tools
Network Automation Conferences
Ansible Training
What is Ansible?
Devops Tutorial
Network Source of Truth
DevOps Glossary
Network Monitoring Software

Contact

Contact

Get in touch with me here

[email protected]

  • Twitter
  • LinkedIn
  • YouTube
Buy me a coffeeBuy me a coffee

Copyright © 2026 · Roger Perkin · All Rights Reserved · Privacy Policy – Terms