An LSR will use the implicit-null label for directly connected networks. This means basically in your case: if you create the traffic on R1 there will nothing be tagswitched. The respective entry is "Pop tag".
Second: your output shows "untagged" on R1. This usually means MPLS is not up and running between R1 and R3. Make sure the config looks like this:
mpls ldp router-id Loopback0
ip address 10.1.1.1 255.255.255.252
frame-relay interface-dlci 100
mpls label protocol ldp
mpls MTU 1508
The "mpls" commands might be translated to "tag-switching", which does not modify the functionality. Also adjust the FR config and IPs etc. to your environment.
The relevant commands are:
show mpls ldp discovery
show mpls interfaces
Make sure all (sub-)interfaces interconnecting R1, R2 and R3 are MPLS enabled. Otherwise there will no labels be used. Finally it should look like this on R1:
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
16 Pop tag 220.127.116.11/32 0 Se0/0 18.104.22.168
17 Pop tag 22.214.171.124/32 0 Se0/0 126.96.36.199
If no "untagged" shows up, you should ping Loopback to Loopback from R2 to R3 and get tagswitched Bytes in R1.
mpls ldp neighbor 188.8.131.52 targeted ldp
will start an LDP session even if no MPLS enabled interfaces exist. LDP might be up and running, but the interface settings decide whether labels can be used or not.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...