Got it

MPLS entry

Created: Jun 30, 2020 13:14:30Latest reply: Jul 2, 2020 00:34:02 109 5 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hello,

MPLS packets are forwarded through label mapping, then why does the NHLFE entry contain the next hop and the ILM entry contains the inbound interface? What do these two elements do?

What commands can be used to query ILM and NHLFE entries? I do not find these commands in the product documentation.

Thanks.

  • x
  • convention:

Featured Answers
Popeye_Wang
Admin Created Jun 30, 2020 13:19:40 Helpful(1) Helpful(1)

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



View more
  • x
  • convention:

All Answers
Popeye_Wang
Popeye_Wang Admin Created Jun 30, 2020 13:19:40 Helpful(1) Helpful(1)

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



View more
  • x
  • convention:

GladysP
GladysP Created Jun 30, 2020 22:40:06 Helpful(2) Helpful(2)

Thank you for your support
View more
  • x
  • convention:

GladysP
GladysP Created Jun 30, 2020 22:40:13 Helpful(0) Helpful(0)

excellent
View more
  • x
  • convention:

Danielarab
Danielarab Created Jul 2, 2020 00:33:55 Helpful(0) Helpful(0)

very useful, thanks!!MPLS entry-3359035-1
View more
  • x
  • convention:

Danielarab
Danielarab Created Jul 2, 2020 00:34:02 Helpful(0) Helpful(0)

well done
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

My Followers

Login and enjoy all the member benefits

Login

Huawei Enterprise Support Community
Huawei Enterprise Support Community
Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.