Reset Search
 

 

Article

Ping fails over L3VPN tunnel, when the corresponding ARP's are present in the extended hash tables

« Go Back

Information

 
TitlePing fails over L3VPN tunnel, when the corresponding ARP's are present in the extended hash tables
Symptoms
Ping fails over L3VPN tunnel, when the corresponding ARP's are present in the extended hash tables.

Use example below to check in what tables entries are installed 
 
X670G2-48x-4q.1 # Debug hal show ipv4adj slot 1
                            HAL IPv4 Adjacencies:

VrId Gateway          MAC                Intf  RCnt  Flags
================================================================
  10 010.006.000.001  00:00:00:00:00:00  0     1     ----L---------
  10 010.006.000.022  00:1F:CE:FA:64:ED  5     0     RS-------E----
  10 010.006.000.025  A8:F9:4B:26:32:50  5     0     RS-------P----
  10 010.006.000.253  AC:F1:DF:94:E2:03  5     0     RS-------P----
 
IP Adj Flags: R = Resolved,  S = Setup in hdw,  D = Delete in progress
              I = Invalidated, L = Local (direct),  B = Blackhole
              H = Hash Table,  E = Extended Hash,  P = LPM Table
              p = PBR, F = Flow Redirect, T = Tunnel
              N = Native to slot,  d = Distributed,  l = Int+Ext. LPM,  c = Consumes NH

Total IP Adjacencies = 4


 
Environment
  • Summit X670G2 
  • Summit X770
  • EXOS all
  • MPLS
  • L3VPN
Cause
This issue is tracked under CR xos0065571.
Resolution
Workaround : Use next command and ARP's will never use the extended mode.

<configure forwarding internal-tables more l2>  
(Please note that the above would require a save and reboot)
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255