Hi,
The NHLFE needs the next hop for encapsulating the MAC address.
The reason why ILM needs the inbound interface: The labels on different interfaces are different when the interface-based label space is used. However, the number of incoming labels on each interface is large. Therefore, it is difficult for the router to search for labels.
The two entries need to be queried in the diagnosis view.
The disp mpls ilm command displays ILM entries.
The display mpls nhlfe command displays NHLFE entries.
[sysname] diagnose
[sysname-diagnose] display mpls nhlfe 5
Total = 1
OUTINTERFACE TUNNELID OPER NEXTHOP DEEP STACK
------------------------------------------------------------------------
Vlanif210 0x5 PUSH 10.1.1.1 1 3
1 Record(s) Found
[sysname-diagnose] display mpls ilm 900 verbose
ILM[1]:
LSP type : LDP
Label operation : SWAP
In interface : GigabitEthernet1/0/1
In Label : 1025
Swap label : 1026
VPN index : 0
6PE ilm flag : IPv4
Is Outgoing tunnel id : no
Load-balance count : 1
Tunnel id[0] : 0x800010df
Out interface[0] : GigabitEthernet1/0/1
Nexthop[0] : 192.168.1.1
Has FRR LSP : no
FRR inner label : --
FRR tunnel id : --
FRR out interface : --
FRR nexthop : --
CC : 0x00
CV : 0x00
Secondary : primary
Ctrlword : disable
Frag flag : no
Switch flag : AC
Copy flag : no
Send flow label : no
Receive flow label : no
Key type : ckey
SPT type : NHP_GROUP
SPT key : 2
SPT handle : 0x024d225e
SPT nexthop handle : 0x0322455d
Backup SPT type : --
Backup SPT key : --
Backup SPT handle : --
Backup SPT nexthop handle : --
VPLS forward flag : yes
VPLS peer address : 192.168.1.2
VPLS VC or site id : 13
VPLS PW type : martini
VPLS id : 1
VPLS Statistics flag : disable
VPLS action : create
VPLS redundancy flag : disable
VPLS redundancy label : 0
VPLS PBB flag : disable
Ring local search NHLFE : yes
Ring switch flag : work
Ring id : 1
Ring destination node id : 44
Ring TTL mode : pipe
Time stamp : 456
Hardware handle : 0x064d2312
1 Record(s) Found
