Hi everybody,
I'm doing some MPLS studying and I got a pcap trace between 2 LSR during label exchange (in attached) plus I got some debug from the router's CLI.
As I we can see from the debug, there is an association between label and IP
[...]
P-R4#pr 18 08:40:11.887: LIB: 10.0.4.0/24:: learn binding 23 from 3.3.3.3:0
*Apr 18 08:40:11.887: LIB: find a binding 23 exists, inst 1 -> inst 2
*Apr 18 08:40:11.887: lcon: tibent(10.0.4.0/24): label 23 from 3.3.3.3:0 added
*Apr 18 08:40:11.887: LIB: next hop is zero for route 10.0.4.0/24(0, 0.0.0.0, Lo0), don't program label
*Apr 18 08:40:11.887: LIB: skip label announcement for 10.0.4.0/24
*Apr 18 08:40:11.887: lc_handle_rlbl_prgm handle 3.3.3.3/32
*Apr 18 08:40:11.887: ldpx_fwdg: announced path label info for 3.3.3.3/32
*Apr 18 08:40:11.891: LIB: prefix recurs walk start: 3.3.3.3/32, tableid: 0
*Apr 18 08:40:11.891: ldpx_fwdg: path change upcall event from fwdg
*Apr 18 08:40:11.891: LIB: get path labels for route 3.3.3.3/32
*Apr 18 08:40:11.895: LIB: get path labels: 3.3.3.3/32(0), nh ctx_id: 0, Fa0/0, nh 192.168.34.1
*Apr 18 08:40:11.895: LDP LLAF: 3.3.3.3 accepted, absence of filtering config
*Apr 18 08:40:11.899: tib: Assign 3.3.3.3/32 nh 192.168.34.1 real label
[...]
However, from the pcap attache, I cannot see/understand the same process. I was expecting something like IP/LABEL association (as a kind of OSPF packets with all information carried)
Can you help to understand?
Thanls
