Cisco Catalyst SD-WAN Troubleshooting Guide

PDF

Cisco Catalyst SD-WAN Troubleshooting Guide

Debug to match IPv4 and IPv6 traffic over MPLS using the CLI

Updated: September 28, 2026

Want to summarize with AI?

Log in

Configure debug conditions to match IPv4 and IPv6 traffic over MPLS networks using various filtering conditions and label specifications.

Use the debug platform condition MPLS match-inner command to match IPv4 and IPv6 traffic over MPLS using various filtering conditions such as match-inner ipv4 , match-inner ipv6 , and allow-no-label .

Specify the MPLS label information, inner IPv4 and IPv6 address based on the debugging requirement.

Procedure

  1. Debug the MPLS network.

    Example:

    debug platform condition mpls

  2. Specify the debugging conditions as per your requirement.

    • Use this condition to debug IPv4 traffic over an MPLS network without specifying the MPLS label:

      match-inner ipv4

    • Use this condition to debug IPv6 traffic over an MPLS network without specifying the MPLS label:

      match-inner ipv6

    • Use allow-no-label condition to match IPv4 or IPv6 packets irrespective of the MPLS labels being encapsulated or not. Use the allow-no-label condition when you want the decapsulated router traffic from the MPLS network to be transmitted as IPv4 or IPv6 packets:

      match-inner ipv4{ipv4-source-prefix | any | host | payload-offset | protocol}{ipv4-destination-prefix | any | host} {application | both | ingress | egress}[bidirection] [allow-no-label]

      or

      match-inner ipv6{ipv6-source-prefix | any | host | payload-offset | protocol}{ipv4-destination-prefix | any | host} {application | both | ingress | egress}[bidirection] [allow-no-label]

    • Specify the MPLS label and depth to filter IPv4 packets flowing through a particular MPLS interface:

      [interfaceinterface-name interface-number] mpls depth-of-mpls-label match-inner ipv4 {ipv4-source-prefix | any | host | payload-offset | protocol}{ipv4-destination-prefix | any | host}{application | both | ingress | egress}[bidirection] [allow-no-label]

    • Specify the MPLS label and depth to filter IPv6 packets flowing through a particular MPLS interface:

      [interfaceinterface-name interface-number] mpls depth-of-mpls-label match-inner ipv6 {ipv6-source-prefix | any | host | payload-offset | protocol}{ipv6-destination-prefix | any | host}{application | both | ingress | egress}[bidirection] [allow-no-label]

  3. Exit the privileged EXEC mode.

    Example:

    exit

The debug conditions are configured to match IPv4 and IPv6 traffic over MPLS networks based on your specified filtering criteria.

Examples

This example shows how to use the debug condition debug platform condition MPLS command to enable matching of IPv4 or IPv6 traffic over MPLS networks:

Device# debug platform condition mpls match-inner ipv4
Device# debug platform condition mpls match-inner ipv4 any any
Device# debug platform condition mpls match-inner ipv4 any any both
Device# debug platform condition mpls match-inner ipv4 any any both allow-no-label

For more information see, debug platform condition MPLS command page.

This example shows how to use the debug condition debug platform condition interface MPLS command to enable matching of IPv4 or IPv4 traffic over MPLS networks for a specific interface:

Device# debug platform condition interface
Device# debug platform condition interface Loopback 3 mpls
Device# debug platform condition interface Loopback 3 mpls match-inner ipv6 host 2001:db8:3333:4444:5555:6666:7777:8888
Device# debug platform condition interface Loopback 3 mpls match-inner ipv6 host 2001:db8:3333:4444:5555:6666:7777:8888 any both
Device# debug platform condition interface Loopback 3 mpls match-inner ipv6 host 2001:db8:3333:4444:5555:6666:7777:8888 any both allow-no-label