检验Catalyst 9000交换机上SDA中的第2层LISP连接

已更新: 2023 年 6 月 14 日

文档 ID:220515

非歧视性语言

此产品的文档集力求使用非歧视性语言。在本文档集中，非歧视性语言是指不隐含针对年龄、残障、性别、种族身份、族群身份、性取向、社会经济地位和交叉性的歧视的语言。由于产品软件的用户界面中使用的硬编码语言、基于 RFP 文档使用的语言或引用的第三方产品使用的语言，文档中可能无法确保完全使用非歧视性语言。深入了解思科如何使用包容性语言。

关于此翻译

思科采用人工翻译与机器翻译相结合的方式将此文档翻译成不同语言，希望全球的用户都能通过各自的语言得到支持性的内容。请注意：即使是最好的机器翻译，其准确度也不及专业翻译人员的水平。 Cisco Systems, Inc. 对于翻译的准确性不承担任何责任，并建议您总是参考英文原始文档（已提供链接）。

简介

本文档介绍如何在Catalyst 9000交换机上的软件定义接入(SDA)中验证第2层LISP。

要求

Cisco 建议您了解以下主题：

了解SDA解决方案和组件。
了解定位器/ID分离协议(LISP) — 控制平面 — 和虚拟可扩展局域网(VxLAN) — 数据平面 — 协议。
熟悉Catalyst 9000架构。

使用的组件

本文档中的信息基于以下软件和硬件版本：

Catalyst 9300
Cisco IOS® XE 16.9.8及更高版本

本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始（默认）配置。如果您的网络处于活动状态，请确保您了解所有命令的潜在影响。

背景信息

SD-Access架构受园区实施的交换矩阵技术的支持。它支持使用在物理网络（底层网络）顶部运行的虚拟网络（重叠网络），以创建用于连接设备的备用拓扑。有关思科SD-Access解决方案不同组件的详细信息，请访问：

Cisco SD-Access解决方案设计指南

交换矩阵中的第2层

完整的以太网帧封装在VxLAN中并通过SDA交换矩阵传输。
交换矩阵中的第2层流量通过第2层LISP实例发送。
原始第2层报头保留在VxLAN封装的数据包中。
MAC地址在控制平面(CP)节点中注册为连接到特定RLOC（路由定位器，例如边缘节点）的EID（终端ID）。
边缘节点解析并缓存远程MAC地址。

网络图

SDA topology

验证

L2-LISP实例扩展

L2-LISP实例的实际可用数量比SDM模板上的最大数量少64:

EDGE-1#show plat hardware fed switch active fwd-asic resource tcam utilization 
CAM Utilization for ASIC  [0]
 Table                                              Max Values        Used Values
 --------------------------------------------------------------------------------
 Unicast MAC addresses                               32768/1024        44/21  
 L3 Multicast entries                                 8192/512          4/10  
 L2 Multicast entries                                 8192/512          1/9   
 Directly or indirectly connected routes             24576/8192        33/81  
 QoS Access Control Entries                           5120            153
 Security Access Control Entries                      5120            180
 Ingress Netflow ACEs                                  256              8
 Policy Based Routing ACEs                            1024             20
 Egress Netflow ACEs                                   768              8
 Flow SPAN ACEs                                       1024             13
 Control Plane Entries                                 512            255
 Tunnels                                               512             18
 Lisp Instance Mapping Entries                         512             16
 Input Security Associations                           256              4
 Output Security Associations and Policies             256              5
 SGT_DGT                                              8192/512          0/1   
 CLIENT_LE                                            4096/256          0/0   
 INPUT_GROUP_LE                                       1024              0
 OUTPUT_GROUP_LE                                      1024              0
 Macsec SPD                                            256              2

在这种情况下，加载了Cisco IOS® XE 16.9.8的边缘节点的L2-LISP实例的实际可用数量为448(512 - 64)。

位于同一VN（虚拟网络）的两台主机，相同的VLAN/子网，但连接到不同的边缘交换机。如拓扑图所示，两台边缘交换机属于同一SDA交换矩阵云。两台主机Client-1和Client-2属于连接到VLAN 1021/子网10.90.10.1/24的同一VN Campus_VN。 ICMP数据包(ping)用于测试两台主机之间的连通性。

Client-1>ping 10.90.10.20

Pinging 10.90.10.20 with 32 bytes of data:
Reply from 10.90.10.20: bytes=32 time=4ms TTL=128
Reply from 10.90.10.20: bytes=32 time<1ms TTL=128
Reply from 10.90.10.20: bytes=32 time<1ms TTL=128

Ping statistics for 10.90.10.20:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 1ms


Client-2>ping 10.90.10.10

Pinging 10.90.10.10 with 32 bytes of data:
Reply from 10.90.10.10: bytes=32 time<1ms TTL=128
Reply from 10.90.10.10: bytes=32 time<1ms TTL=128
Reply from 10.90.10.10: bytes=32 time<1ms TTL=128

Ping statistics for 10.90.10.10:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

由于两个边缘交换机属于同一个SDA交换矩阵，因此需要对边缘1和边缘2之间的所有生产流量进行VxLAN封装。在这种情况下，边缘交换机使用L3实例ID(IID)4100和L2实例ID 8191来封装流量。

控制平面

您首先需要确认控制平面信息是否正确。如果来自控制平面的信息（软件状态）看起来正常，则需要验证数据平面（硬件状态）。

步骤1:适当的SVI调配

如前所述，我们第一个场景中的两台主机都驻留在VLAN 1021上，此VLAN/子网在SDA交换矩阵中延伸。首先，您需要从数字网络架构中心（DNA中心，或DNAC）在每个边缘交换机上自动调配的VLAN 1021中检查SVI的配置：

EDGE-1#show run int vlan 1021  
Building configuration...

Current configuration : 618 bytes
!
interface Vlan1021
 description Configured from Cisco DNA-Center
 mac-address 0000.0c9f.f55e
 vrf forwarding Campus_VN
 ip address 10.90.10.1 255.255.255.0
 ip helper-address 10.122.150.179
 no ip redirects
 ip route-cache same-interface
 no lisp mobility liveness test
 lisp mobility CAMPUS-WIRED-IPV4
end  

EDGE-2#show run int vlan 1021
Building configuration...

Current configuration : 618 bytes
!
interface Vlan1021
 description Configured from Cisco DNA-Center
 mac-address 0000.0c9f.f55e
 vrf forwarding Campus_VN
 ip address 10.90.10.1 255.255.255.0
 ip helper-address 10.122.150.179
 no ip redirects
 ip route-cache same-interface
 no lisp mobility liveness test
 lisp mobility CAMPUS-WIRED-IPV4
end

正如您在此输出中所见，L2和L3实例ID(IID)都不是SVI配置的一部分。在SDA环境中，这些实例由DNAC自动配置。因此，为了找到此信息，您必须检查设备LISP running-configuration。但是，如果您有数百个VLAN，则查找要验证的实际的VLAN的信息并非易事

提示：提示：如果您事先不知道L2 ID信息，可以运行此命令查找它(对有问题的VLAN使用“include”过滤器，在本例中为*VLAN 1021*

EDGE-1#show lisp instance-id * ethernet database | include Vlan 1021 LISP ETR MAC Mapping Database for EID-table Vlan 1021 (IID 8191), LSBs: 0x1

第二步：MAC 地址表

首先，您需要确认MAC地址（本地和远程）都存在于边缘交换机的MAC地址表中。对于本地主机的MAC，还必须有一个ARP条目。您需要检查两台设备上的相同信息。

EDGE-1#sh mac address-table | in 1021
1021    0000.0c9f.f55e    STATIC      Vl1021 
1021000c.29ef.34d1    DYNAMIC     Gi1/0/13  <<<< Local host
1021    2cab.eb4f.e6f5    STATIC      Vl1021 
1021000c.297b.3544    CP_LEARN    Tu0       <<<< Remote host

EDGE-2#sh mac address-table | in 1021
1021    0000.0c9f.f55e    STATIC      Vl1021 
1021    000c.297b.3544    STATIC      Gi1/0/13  <<<< Local host
1021    70d3.79be.9675    STATIC      Vl1021 
1021    000c.29ef.34d1    CP_LEARN    Tu0       <<<< Remote host

如图所示，有一个条目将CP_LEARN作为远程主机的地址类型。此条目来自Tu0，将在“解封”一节中详细讨论。它显示CP_LEARN，因为L2转发从LISP控制平面(CP)获取此信息。

第三步：ARP 表

ARP表只包含本地主机的条目，因为远程主机位置通过LISP解析，而不是直接通过ARP解析：

EDGE-1#sh ip arp vrf Campus_VN 10.90.10.10
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.90.10.10             0   000c.29ef.34d1  ARPA   Vlan1021    <<<< Local host

EDGE-1#sh ip arp vrf Campus_VN 10.90.10.20 
EDGE-1# <<<< Empty for remote host

EDGE-2#sh ip arp vrf Campus_VN 10.90.10.10 
EDGE-2# <<<< Empty for remote host

EDGE-2#sh ip arp vrf Campus_VN 10.90.10.20
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.90.10.20             0   000c.297b.3544  ARPA Vlan1021      <<<< Local host

第四步：本地主机的LISP数据库

从MAC地址表获取的信息也会填充到对应硬件状态中，即MAC地址表管理器(MATM)。对于本地主机，交换机集成安全功能（SISF，也称为设备跟踪）监听来自客户端的信息，并将L2-EID(MAC)和L2-AR EID(IP/MAC)信息通知LISP CP，以下是LISP数据库填充的方式：

EDGE-1#show lisp instance-id 8191 ethernet database
LISP ETR MAC Mapping Database for EID-table Vlan 1021 (IID 8191), LSBs: 0x1
Entries total 2, no-route 0, inactive 0000c.29ef.34d1/48, dynamic-eid Auto-L2-group-8191, inherited from default locator-set rloc_497d4d09-992e-4eaa-92c8-5c7e27d08734
  Locator       Pri/Wgt  Source     State
192.168.3.69   10/10   cfg-intf   site-self, reachable

EDGE-2#show lisp instance-id 8191 ethernet database
LISP ETR MAC Mapping Database for EID-table Vlan 1021 (IID 8191), LSBs: 0x1
Entries total 1, no-route 0, inactive 0000c.297b.3544/48, dynamic-eid Auto-L2-group-8191, inherited from default locator-set rloc_ccca08ff-fd0f-42e2-9fbb-a6521bb1b65e
  Locator       Pri/Wgt  Source     State
192.168.3.68   10/10   cfg-intf   site-self, reachable

此外，在LISP数据库中，还可以验证本地主机的地址解析。这样，您可以将L2信息与L3数据相关联。如前所述，远程主机的条目不会填充到设备的常规ARP表中，因此此命令仅显示通过ARP获取的LISP EID信息，仅供本地主机:

提示：在此输出中，您还可以找到与该主机/子网相关联的L3 ID:4100。

EDGE-1#show lisp instance-id 8191 ethernet database address-resolution
LISP ETR Address Resolution for EID-table Vlan 1021 (IID 8191)
(*) -> entry being deleted

Hardware Address       Host Address         L3 InstID
000c.29ef.34d1         10.90.10.10/32            4100

EDGE-2#show lisp instance-id 8191 ethernet database address-resolution
LISP ETR Address Resolution for EID-table Vlan 1021 (IID 8191)
(*) -> entry being deleted

Hardware Address       Host Address         L3 InstID
000c.297b.3544         10.90.10.20/32            4100

第五步：使用LISP Internet Groper(LIG)的远程目标的RLOC

另一个检查是验证远程主机的位置。您可以使用LIG命令解析和标识远程MAC地址所在的RLOC（在这种情况下，您可以通过cli手动触发LIG，但是当交换机需要将帧转发到未知目标MAC时，它会自动发出LISP信号以便解析该未知MAC的位置）：

提示：由于您想要检查L2连接，因此您必须使用L2 ID和远程主机的MAC地址作为LIG的EID。另一方面，如果要检查L3连接，您需要使用L3 ID(本例中为4100)和主机的实际IP作为LIG的EID。

EDGE-1#lig instance 8191 000c.297b.3544
Mapping information for EID 000c.297b.3544 from 192.168.2.2 with RTT 1 msecs
000c.297b.3544/48, uptime: 05:32:34, expires: 23:59:59, via map-reply, complete
  Locator       Uptime    State  Pri/Wgt     Encap-IID
  192.168.3.68  05:32:34  up      10/10        -         <<<< RLOC of Edge-2

EDGE-2#lig instance 8191 000c.29ef.34d1 
Mapping information for EID 000c.29ef.34d1 from 192.168.2.2 with RTT 1 msecs
000c.29ef.34d1/48, uptime: 05:33:14, expires: 23:59:59, via map-reply, complete
  Locator       Uptime    State  Pri/Wgt     Encap-IID
  192.168.3.69  05:33:14  up      10/10        -         <<<< RLOC of Edge-1

第六步：远程主机的LISP映射缓存

来自远程主机的RLOC也存在于LISP映射缓存表中（如果您在此输出中看不到来自远程主机的信息，则尝试先为该主机执行LIG，然后再进行检查）。对于远程主机，LISP使用LISP映射缓存表中的信息更新交换机的L2转发信息，这就是为什么通过Tu0获取CP_LEARN类型时，远程主机的MAC地址显示在交换机的MAC地址表中：

EDGE-1#show lisp instance-id 8191 ethernet map-cache
LISP MAC Mapping Cache for EID-table Vlan 1021 (IID 8191), 1 entries
000c.297b.3544/48, uptime: 05:36:05, expires: 23:56:28, via map-reply, complete
  Locator       Uptime    State  Pri/Wgt     Encap-IID
  192.168.3.68  05:36:05  up      10/10        -         <<<< RLOC of Edge-2 

EDGE-2#show lisp instance-id 8191 ethernet map-cache
LISP MAC Mapping Cache for EID-table Vlan 1021 (IID 8191), 1 entries
000c.29ef.34d1/48, uptime: 05:36:17, expires: 23:56:56, via map-reply, complete
  Locator       Uptime    State  Pri/Wgt     Encap-IID
  192.168.3.69  05:36:17  up      10/10        -         <<<< RLOC of Edge-1

步骤 7.交换机集成安全功能(SISF)数据库（设备跟踪数据库）

SISF参与监听第3层到第2层映射的过程，以方便终端学习（通过DHCP和ARP监听）。在L2-LISP中，边缘节点仅根据第2层信息转发流量。SISF开始发挥作用是因为广播ARP流量不会通过交换矩阵跨入口/出口隧道路由器（xTR — 这是SDA架构中边缘节点的另一个名称）转发。ARP流量通过交换矩阵通过隧道传输，而不是泛洪。

边缘节点的SISF组件在控制平面(CP)节点的映射服务器和映射解析器(MSMR)功能上注册来自其本地主机的ARP解析信息（该信息称为终端ID - EID）。CP/MSMR节点维护由所有边缘节点填充的映射数据库。当主机尝试通过ARP Request解析位于不同边缘节点的远程主机的IP/MAC绑定时，本地边缘节点会截获并缓存广播ARP请求，然后侦听数据包，并查询CP/MSMR以获取IP到MAC的绑定。最后，边缘节点将广播目标Mac重写到单播目标Mac(从CP/MSMR获取作为对查询的响应)，以VxLAN格式封装单播ARP请求数据包，并将其通过交换矩阵发送到包含该目标的远程边缘节点。

SISF不仅帮助监听数据包，而且通过适当使用ARP探测功能在设备跟踪数据库中刷新本地条目。

EDGE-1#sh device-tracking database vlanid 1021
vlanDB has 5 entries for vlan 1021, 2 dynamic  
<snip>
    Network Layer Address  Link Layer Address   Interface   vlan   prlvl  age   state      Time left        
    ARP 10.90.10.20        000c.297b.3544       Tu0         1021   0005   15s   REACHABLE  234s      <<<< Remote host (info from the CP node via MSMR query)         
    ARP 10.90.10.1         0000c.29ef.34d1      Gi1/0/13    1021   0005   15s   REACHABLE  300s      <<<< Local host   

EDGE-1#sh device-tracking database mac
 MAC              Interface      vlan prlvl      state          time left  policy
 <snip>
 000c.29ef.34d1   Gi1/0/13       1021 NO TRUST   MAC-REACHABLE  284s       IPDT_POLICY          <<<< Local host
 000c.297b.3544   Tu0            1021 NO TRUST   MAC-REACHABLE  87s        LISP-DT-GUARD-VLAN   <<<< Remote host (info from the CP node via MSMR query)

EDGE-1#sh device-tracking database address all
    Network Layer Address    Link Layer Address Interface  vlan prlvl  age   state     Time left        
<snip>
    ARP 10.90.10.20          000c.297b.3544     Tu0        1021  0005    2s  REACHABLE  243s   <<<< Remote host (info from the CP node via MSMR query)        
    ARP 10.90.10.10          000c.29ef.34d1     Gi1/0/13   1021  0005    2s  REACHABLE  304s   <<<< Local host

EDGE-2#sh device-tracking database vlanid 1021
vlanDB has 5 entries for vlan 1021, 2 dynamic 
<snip>
    Network Layer Address               Link Layer Address Interface  vlan  prlvl  age  state      Time left        
    ARP 10.90.10.20                     000c.297b.3544     Gi1/0/13   1021  0005    2s  REACHABLE  250s   <<<< Local host           
    ARP 10.90.10.10                     000c.29ef.34d1     Tu0        1021  0005    2s  REACHABLE  244s   <<<< Remote host (info from the CP node via MSMR query)      

EDGE-2#sh device-tracking database mac
 MAC              Interface      vlan prlvl      state          time left policy
<snip> 
 000c.29ef.34d1   Tu0            1021 NO TRUST   MAC-REACHABLE  187s      LISP-DT-GUARD-VLAN   <<<< Remote host (info from the CP node via MSMR query)
 000c.297b.3544   Gi1/0/13       1021 NO TRUST   MAC-REACHABLE  239s      IPDT_POLICY          <<<< Local host 

EDGE-2#sh device-tracking database address all
 Network Layer Address    Link Layer Address Interface   vlan prlvl  age   state      Time left        
<snip>                 
 ARP 10.90.10.20          000c.297b.3544     Gi1/0/13    1021  0005   29s  REACHABLE  211s   <<<< Local host      
 ARP 10.90.10.10          000c.29ef.34d1     Tu0         1021  0005  138s  REACHABLE  108s   <<<< Remote host (info from the CP node via MSMR query)

数据平面（封装路径）

验证控制平面信息完整且正确后，现在即可查看数据平面部分。

步骤1:MAC地址表管理器(MATM)中的条目

MATM代表MAC地址表管理器和常规MAC地址表的硬件抽象。

提示：本节中的命令与设备的硬件抽象层相关。这意味着，如果在堆栈配置中部署了设备，则不仅需要为Active成员，还需要为要验证的成员交换机运行命令（例如，如果主机连接到堆栈的成员2，则还必须在cli上使用“switch 2”）。本文只使用独立交换机，因此只验证活动实例的信息。

EDGE-1#show platform software fed switch active matm macTable vlan 1021
VLAN   MAC                   Type  Seq#   EC_Bi  Flags  machandle           siHandle            riHandle            diHandle              *a_time  *e_time  ports                           
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<snip>          
1021   000c.29ef.34d1         0x1      1      0      0  0x7f9e1caa4358      0x7f9e1caf3fc8      0x0                 0x7f9e1c7b5228            300       21  GigabitEthernet1/0/13
1021   000c.297b.3544   0x1000001      0      0     64  0x7f9e1cded158      0x7f9e1ce092f8      0x7f9e1ce08de8      0x7f9e1c2f4a48              0       16  RLOC 192.168.3.68 adj_id 23     

Total Mac number of addresses:: 1
Summary:  
Total number of secure addresses:: 0
Total number of drop addresses:: 0
Total number of lisp local addresses:: 0
Total number of lisp remote addresses:: 0
*a_time=aging_time(secs)  *e_time=total_elapsed_time(secs)
Type:
MAT_DYNAMIC_ADDR           0x1  MAT_STATIC_ADDR            0x2  MAT_CPU_ADDR               0x4  MAT_DISCARD_ADDR           0x8
MAT_ALL_VLANS             0x10  MAT_NO_FORWARD            0x20  MAT_IPMULT_ADDR           0x40  MAT_RESYNC                0x80
MAT_DO_NOT_AGE           0x100  MAT_SECURE_ADDR          0x200  MAT_NO_PORT              0x400  MAT_DROP_ADDR            0x800
MAT_DUP_ADDR            0x1000  MAT_NULL_DESTINATION    0x2000  MAT_DOT1X_ADDR          0x4000  MAT_ROUTER_ADDR         0x8000
MAT_WIRELESS_ADDR      0x10000  MAT_SECURE_CFG_ADDR    0x20000  MAT_OPQ_DATA_PRESENT   0x40000  MAT_WIRED_TUNNEL_ADDR  0x80000
MAT_DLR_ADDR          0x100000  MAT_MRP_ADDR          0x200000  MAT_MSRP_ADDR         0x400000  MAT_LISP_LOCAL_ADDR   0x800000
MAT_LISP_REMOTE_ADDR 0x1000000  MAT_VPLS_ADDR        0x2000000

如前面的输出所示，远程主机的MAC地址的位映射类型为0x100001：位0x1000000表示LISP远程条目，位0x1设置为动态条目。此表中的其他重要值是machandle、siHandle和riHandle，在下次验证时请随时保存此信息。

第二步：打印“machandle”的资源句柄信息

机用于验证硬件上为此对象编程的信息，本例中为远程MAC地址：

EDGE-1#show platform hardware fed switch active fwd-asic abstraction print-resource-handle 0x7f9e1cded158 1
Handle:0x7f9e1cded158 Res-Type:ASIC_RSC_HASH_TCAM Res-Switch-Num:0 Asic-Num:255 Feature-ID:AL_FID_L2_WIRELESS Lkp-ftr-id:LKP_FEAT_L2_SRC_MAC_VLAN ref_count:1
priv_ri/priv_si Handle: (nil)Hardware Indices/Handles: handle [ASIC: 0]: 0x7f9e1cded368
Features sharing this resource:Cookie length: 12
7b 29 0c 00 44 35 06 80 07 00 00 00 

Detailed Resource Information (ASIC# 0)
----------------------------------------
Number of HTM Entries: 1

Entry 0: (handle 0x7f9e1cded368)

Absolute Index: 4100 
Time Stamp: 231
KEY - vlan:6 mac:0xc297b3544 l3_if:0 gpn:3401 epoch:0 static:0 flood_en:0 vlan_lead_wless_flood_en: 0 client_home_asic: 0 learning_peerid 0, learning_peerid_valid 0 
MASK - vlan:0 mac:0x0 l3_if:0 gpn:0 epoch:0 static:0 flood_en:0 vlan_lead_wless_flood_en: 0 client_home_asic: 0 learning_peerid 0, learning_peerid_valid 0 
SRC_AD - need_to_learn:0 lrn_v:0 catchall:0 static_mac:0 chain_ptr_v:0 chain_ptr: 0 static_entry_v:0 auth_state:0 auth_mode:0 auth_behavior_tag:0 traf_m:0 is_src_ce:0
DST_AD - si:0xd5 bridge:0 replicate:0 blk_fwd_o:0 v4_rmac:0 v6_rmac:0 catchall:0 ign_src_lrn:0 port_mask_o:0 afd_cli_f:0 afd_lbl:0 prio:3 dest_mod_idx:0 destined_to_us:0 pv_trunk:0 smr:1


==============================================================

以下是Edge-1上一输出中最重要的字段：

密钥VLAN(MVID)= 6
组端口号(GPN)= 3401
站点索引(SI)= 0xd5

第三步：密钥VLAN(MVID)

先前输出的Key VLAN ID必须与分配给VLAN 1021的硬件MVID值匹配，您可以在以下命令输出中找到该信息：

EDGE-1#show platform software fed switch active vlan 1021
VLAN Fed Information


Vlan Id  IF Id                LE Handle            STP Handle           L3 IF Handle         SVI IF ID            MVID   
-----------------------------------------------------------------------------------------------------------------------
1021     0x0000000000420010   0x00007f9e1c65d268   0x00007f9e1c65da98   0x00007f9e1c995e18   0x000000000000003a   6

已确认,VLAN 1021的MVID值等于6!

第四步：组端口号(GPN)

要检查L2-LISP Tunnel0使用的GPN值，需要两个命令。首先，您必须确认分配给Tunnel0：的硬件接口ID

EDGE-1#show platform software dpidb l2lisp 8191
Instance Id:8191, dpidx:4325400, vlan:1021, Parent Interface:Tunnel0(if_id:64)

### or alternatively you can use command:

EDGE-1#show platform software fed sw active ifm interfaces l2-lisp
Interface                         IF_ID               State             
----------------------------------------------------------------------
Tunnel0                           0x00000040          READY

现在，您可以在接口功能管理器(IFM)中验证分配给该接口ID的属性：

EDGE-1#show platform software fed switch active ifm if-id 64   <<<< 64 DEC = 0x40 HEX
Interface IF_ID         : 0x0000000000000040
Interface Name          : Tunnel0
Interface Block Pointer : 0x7f9e1c91d5c8
Interface Block State   : READY
Interface State         : Enabled
Interface Status        : ADD, UPD
Interface Ref-Cnt       : 2
Interface Type          : L2_LISP              <<<< Tunnel Type
        Is top interface    : TRUE
        Asic_num            : 0
        Switch_num          : 0
        AAL port Handle     : cc00005d
        Source Ip Address   : 192.168.3.69     <<<< Tunnel Source Address (Lo0), RLOC of Edge-1
        Vlan Id             : 0
        Instance Id         : 0
        Dest Port           : 4789             <<<< VxLAN UDP Port
        SGT                 : Disable          <<<< CTS not configured for this scenario
        Underlay VRF (V4)   : 0
        Underlay VRF (V6)   : 0
        Flood Access-tunnel : Disable
        Flood unknown ucast : Disable
        Broadcast           : Disable
        Multicast Flood     : Disable

Decap Information 

                TT HTM handle     : 0x7f9e1c9c40e8

        Port Information
        Handle ............ [0xcc00005d]
        Type .............. [L2-LISP-top]
        Identifier ........ [0x40]
        Unit .............. [64]
         L2 LISP Topology interface Subblock
                Switch Num        : 1
                Asic Num          : 0
                Encap PORT LE handle    : 0x7f9e1c9befe8
                Decap PORT LE handle    : 0x7f9e1c91d818
                L3IF LE handle    : 0x7f9e1c9bf2b8
                SI handle decap   : 0x7f9e1c9c8568
                DI handle         : 0x7f9e1c2f4a48
                RI handle         : 0x7f9e1c9c4498
                RCP Service ID    : 0x0
                GPN               : 3401         <<<< GPN
                TRANS CATCH ALL handle : 0x7f9e1c2f5698
<snip>

除GPN值3401与对远程MAC的机器进行硬件抽象验证时获得的信息匹配外，在前面的输出中，您还有一些其他有用信息，用于封装通过L2-LISP隧道发送的流量，例如：隧道类型、隧道源IP地址、UDP目标端口等。

第五步：站索引(SI)

使用station index，您可以获取用于通过L2-LISP隧道发送流量的目标索引和重写索引。此信息告诉我们如何和在何处发送数据包：

提示：在此步骤中，您将收集另外两个值，DI（目标索引）和RI（重写索引），以便将来参考。

EDGE-1#show platform hardware fed switch active fwd-asic resource asic all station-index range 0xd5 0xd5
ASIC#0:
Station Index (SI) [0xd5]
RI = 0x28       <<<< Rewrite Index
DI = 0x5012     <<<< Destination Index
stationTableGenericLabel = 0
stationFdConstructionLabel = 0x7
lookupSkipIdIndex = 0
rcpServiceId = 0
dejaVuPreCheckEn = 0
Replication Bitmap: LD 
ASIC#1:
Station Index (SI) [0xd5]
RI = 0x28
DI = 0x5012
stationTableGenericLabel = 0
stationFdConstructionLabel = 0x7
lookupSkipIdIndex = 0
rcpServiceId = 0
dejaVuPreCheckEn = 0
Replication Bitmap: RD CD

第六步：目标索引(DI)

本节的重要内容是，物理端口的端口映射值(pmap)是全零，并且再循环端口映射(rcp_pmap)等于ASIC 0上的一个值。由于这些值使用布尔逻辑，因此此输出实际上意味着交换机不使用物理端口，而是使用逻辑接口(Tunnel0)来转发流量。请注意，仅ASIC 0的rcp_pmap为ON。

提示：用于转发流量的实际ASIC取决于用于建立L2-LISP隧道的物理端口（与上游设备的底层连接），因为每个物理端口都映射到特定ASIC实例。还要考虑交换机上的ASIC数量因型号而异。

EDGE-1#show platform hardware fed switch active fwd-asic resource asic all destination-index range 0x5012 0x5012      
ASIC#0:
Destination Index (DI) [0x5012]
portMap = 0x00000000 00000000   <<<< All bits for physical ports are off
cmi1 = 0
rcpPortMap = 0x1                <<<< Recirculation port-map bit is enabled     

CPU Map Index (CMI) [0]
ctiLo0 = 0
ctiLo1 = 0
ctiLo2 = 0
cpuQNum0 = 0
cpuQNum1 = 0
cpuQNum2 = 0
npuIndex = 0
stripSeg = 0
copySeg = 0

ASIC#1:
Destination Index (DI) [0x5012]
portMap = 0x00000000 00000000   <<<< All bits for physical ports are off
cmi1 = 0
rcpPortMap = 0

CPU Map Index (CMI) [0]
ctiLo0 = 0
ctiLo1 = 0
ctiLo2 = 0
cpuQNum0 = 0
cpuQNum1 = 0
cpuQNum2 = 0
npuIndex = 0
stripSeg = 0
copySeg = 0

步骤 7.重写索引(RI)

要验证此索引，您必须使用与步骤1的MATM表输出上的远程MAC关联的riHandle，在本例中为0x7f9e1ce08de8。重写索引提供在数据包通过L2-LISP隧道发送之前施加到数据包的VxLAN报头的最终详细信息：

提示：此输出的RI值40必须与步骤5(40 DEC = 0x28 HEX)中的RI索引0x28匹配。

EDGE-1#show platform hardware fed switch active fwd-asic abstraction print-resource-handle 0x7f9e1ce08de8 1
Handle:0x7f9e1ce08de8 Res-Type:ASIC_RSC_RI Res-Switch-Num:255 Asic-Num:255 Feature-ID:AL_FID_L2_WIRELESS Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
priv_ri/priv_si Handle: 0x7f9e1cded678Hardware Indices/Handles: index0:0x28  mtu_index/l3u_ri_index0:0x0  index1:0x28  mtu_index/l3u_ri_index1:0x0 
Features sharing this resource:58 (1)]
Cookie length: 56
00 00 00 00 00 00 00 00 fd 03 00 00 00 00 00 00 00 00 00 00 07 00 00 0c 29 7b 35 44 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

Detailed Resource Information (ASIC# 0)
----------------------------------------


Rewrite Data Table Entry, 
ASIC#:0, rewrite_type:116, RI:40      <<<< Must match RI Index 0x28 from Step 5

 Src IP:         192.168.3.69         <<<< VxLAN header (RLOC of the Local Edge node Edge-1)
 Dst IP:         192.168.3.68         <<<< VxLAN header (RLOC of the Remote Edge node Edge-2)
 iVxlan dstMac:  0x0c:0x297b:0x3544   <<<< MAC address of the Remote host
 iVxlan srcMac:  0x00:0x00:0x00
 IPv4 TTL:       0
 iid present:    1
 lisp iid:       0
 lisp flags:     0
 dst Port:       46354
 update only l3if:       0
 is Sgt:         1
 is TTL Prop:    0
 L3if LE:        0 (0)
 Port LE:        276 (0)
 Vlan LE:        6 (0)

Detailed Resource Information (ASIC# 1)
----------------------------------------


Rewrite Data Table Entry, 
ASIC#:1, rewrite_type:116, RI:40 

 Src IP:         192.168.3.69
 Dst IP:         192.168.3.68
 iVxlan dstMac:  0x0c:0x297b:0x3544
 iVxlan srcMac:  0x00:0x00:0x00
 IPv4 TTL:       0
 iid present:    1
 lisp iid:       0
 lisp flags:     0
 dst Port:       46354
 update only l3if:       0
 is Sgt:         1
 is TTL Prop:    0
 L3if LE:        0 (0)
 Port LE:        276 (0)
 Vlan LE:        6 (0)

==============================================================

步骤 8新封装数据包的转发决策

定向到Client-2 - IP:10.90.10.20的原始ICMP数据包的转发决策指向LISP接口：

EDGE-1#sh ip cef vrf Campus_VN 10.90.10.20   
10.90.10.0/24
  attached to LISP0.4100

一旦封装了原始数据包并且在其后附加了正确的VxLAN报头，您现在必须根据排名靠前的VxLAN字段检查转发决策。在本例中，目的IP地址192.168.3.68是来自远程边缘2交换机的RLOC:

EDGE-1#show ip route 192.168.3.68
Routing entry for 192.168.3.68/32
  Known via "isis", distance 115, metric 30, type level-1
  Redistributing via isis
  Advertised by isis (self originated)
  Last update from 192.168.3.74 on TenGigabitEthernet1/1/1, 01:15:14 ago
  Routing Descriptor Blocks:
  * 192.168.3.74, from 192.168.3.68, 01:15:14 ago, via TenGigabitEthernet1/1/1
      Route metric is 30, traffic share count is 1


EDGE-1#show ip cef 192.168.3.68 detail 
192.168.3.68/32, epoch 3, per-destination sharing
  Adj source: IP midchain out of Tunnel0, addr 192.168.3.68 7FEADF30A390
    Dependent covered prefix type adjfib, cover 0.0.0.0/0
  1 RR source [no flags]
  nexthop 192.168.3.74 TenGigabitEthernet1/1/1

EDGE-1#show adjacency 192.168.3.68 detail 
Protocol Interface                 Address
IP       Tunnel0                   192.168.3.68(4)
                                   0 packets, 0 bytes
                                   epoch 0
                                   sourced in sev-epoch 10
                                   Encap length 28
                                   4500000000000000FF113413C0A80345
                                   C0A8034412B512B500000000
                                   Tun endpt              <<<< Adjacency type: Tunnel
                                   Next chain element:
                                     IP adj out of TenGigabitEthernet1/1/1, addr 192.168.3.74  <<<< Upstream connection from Underlay network

为了到达IP 192.168.3.68，流量必须通过接口Te1/1/1上的下一跳192.168.3.74，因此您还需要检查下一跳IP的邻接关系：

EDGE-1#show ip route 192.168.3.74
Routing entry for 192.168.3.74/31
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Advertised by isis level-2
  Routing Descriptor Blocks:
  * directly connected, via TenGigabitEthernet1/1/1
      Route metric is 0, traffic share count is 1

EDGE-1#show ip cef 192.168.3.74 detail 
192.168.3.74/32, epoch 3, flags [attached]
  Interest List:
     - fib bfd tracking
  BFD state up, tracking attached BFD session on TenGigabitEthernet1/1/1
  Adj source: IP adj out of TenGigabitEthernet1/1/1, addr 192.168.3.74 7FEADEADCFA8
    Dependent covered prefix type adjfib, cover 192.168.3.74/31
  1 IPL source [no flags]
  attached to TenGigabitEthernet1/1/1

EDGE-1#show adjacency 192.168.3.74 detail 
Protocol Interface                 Address
IP       TenGigabitEthernet1/1/1   192.168.3.74(40)
                                   0 packets, 0 bytes
                                   epoch 0
                                   sourced in sev-epoch 10
                                   Encap length 14
                                   00A3D14415582CABEB4FE6C60800   <<<< Layer-2 Rewrite Information for the traffic forwarded through this adjacency
                                   L2 destination address byte offset 0
                                   L2 destination address byte length 6
                                   Link-type after encap: ip
                                   ARP

EDGE-1#show interfaces tenGigabitEthernet 1/1/1 | in bia
  Hardware is Ten Gigabit Ethernet, address is 2cab.eb4f.e6c6 (bia 2cab.eb4f.e6c6)

EDGE-1#show ip arp Te1/1/1
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  192.168.3.74           98   00a3.d144.1558  ARPA   TenGigabitEthernet1/1/1

数据平面（解封路径）

步骤1:来自IFM的Decap信息

要验证交换机如何处理传入VxLAN数据包，首先您需要了解在Tunnel0虚拟接口上收到流量时如何解封流量。还记得上一步收集的Interface Manager(IFM)命令吗？那时，您检查了命令输出的第一部分的信息，现在您必须验证命令输出的第二部分，即与Decap Information相关的部分：

EDGE-1#show platform software fed switch active ifm if-id 64
Interface IF_ID         : 0x0000000000000040
Interface Name          : Tunnel0
Interface Block Pointer : 0x7f9e1c91d5c8
<snip>
Decap Information 

                TT HTM handle     : 0x7f9e1c9c40e8

        Port Information
        Handle ............ [0xcc00005d]
        Type .............. [L2-LISP-top]
        Identifier ........ [0x40]
        Unit .............. [64]
         L2 LISP Topology interface Subblock
                Switch Num        : 1
                Asic Num          : 0
                Encap PORT LE handle    : 0x7f9e1c9befe8
                Decap PORT LE handle    : 0x7f9e1c91d818
                L3IF LE handle    : 0x7f9e1c9bf2b8    
                SI handle decap   : 0x7f9e1c9c8568    <<<< Station Index Handle
                DI handle         : 0x7f9e1c2f4a48
                RI handle         : 0x7f9e1c9c4498    <<<< Rewrite Index Handle
                RCP Service ID    : 0x0
                GPN               : 3401
                TRANS CATCH ALL handle : 0x7f9e1c2f5698
        Port L2 Subblock
                Enabled ............. [No]
                Allow dot1q ......... [No]
                Allow native ........ [No]
                Default VLAN ........ [0]
                Allow priority tag ... [No]
                Allow unknown unicast  [No]
                Allow unknown multicast[No]
                Allow unknown broadcast[No]
                Allow unknown multicast[Enabled]
                Allow unknown unicast  [Enabled]
                Protected ............ [No]
                IPv4 ARP snoop ....... [No]
                IPv6 ARP snoop ....... [No]
                Jumbo MTU ............ [0]
                Learning Mode ........ [0]
                Vepa ................. [Disabled]
        Port QoS Subblock
                Trust Type .................... [0x7]
                Default Value ................. [0]
                Ingress Table Map ............. [0x0]
                Egress Table Map .............. [0x0]
                Queue Map ..................... [0x0]
        Port Netflow Subblock
        Port CTS Subblock
                Disable SGACL .................... [0x0]
                Trust ............................ [0x0]
                Propagate ........................ [0x0]
        %Port SGT .......................... [1251474769]
Ref Count : 2 (feature Ref Counts + 1)
IFM Feature Ref Counts
        FID : 95 (AAL_FEATURE_L2_MULTICAST_IGMP), Ref Count : 1
No Sub Blocks Present

您必须考虑此输出中的两个值：Decap Information部分中的L3接口逻辑实体(L3IF LE)句柄和Station Index(SI)句柄。

第二步：通过L3IF LE句柄在隧道接口上编程的功能

为了验证与Tunnel0接口关联的功能，您需要从关联的L3IF LE句柄提取资源句柄信息。在此输出中，您可以在布尔逻辑中看到在该接口上启用的功能，例如：在此隧道接口上启用了LISP_VXLAN_ENABLE_IPV4功能。

EDGE-1#show platform hardware fed switch active fwd-asic abstraction print-resource-handle 0x7f9e1c9bf2b8 1 | in VXLAN  
LEAD_L3IF_LISP_VXLAN_ENABLE_IPV4 value 1 Pass   <<<< ASIC 0
LEAD_L3IF_LISP_VXLAN_ENABLE_IPV6 value 0 Pass 
LEAD_L3IF_LISP_VXLAN_ENABLE_IPV4 value 1 Pass   <<<< ASIC 1
LEAD_L3IF_LISP_VXLAN_ENABLE_IPV6 value 0 Pass

第三步：隧道接口的站索引(SI)句柄（Decap进程）

您需要再次使用resource handle命令，以便检查Station Index(SI Handle)，并获取通过Tunnel0接口接收的流量使用的重写索引(RI)和Destination Index(DI)，该流量需要由交换机解封，然后再通过常规第2层转发（本地MAC地址表）发送到其最终目标：

EDGE-1#show platform hardware fed switch active fwd-asic abstraction print-resource-handle 0x7f9e1c9c8568 1          
Handle:0x7f9e1c9c8568 Res-Type:ASIC_RSC_SI Res-Switch-Num:255 Asic-Num:255 Feature-ID:AL_FID_LISP Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
priv_ri/priv_si Handle: 0x7f9e1c9c4498Hardware Indices/Handles: index0:0xac  mtu_index/l3u_ri_index0:0x0  index1:0xac  mtu_index/l3u_ri_index1:0x0 
Features sharing this resource:109 (1)]
Cookie length: 56
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

Detailed Resource Information (ASIC# 0)
----------------------------------------

Station Index (SI) [0xac]
RI = 0xa800          <<<< Rewrite Index
DI = 0x5012          <<<< Destination Index
stationTableGenericLabel = 0
stationFdConstructionLabel = 0x4
lookupSkipIdIndex = 0
rcpServiceId = 0
dejaVuPreCheckEn = 0
Replication Bitmap: LD 
Detailed Resource Information (ASIC# 1)
----------------------------------------

Station Index (SI) [0xac]
RI = 0xa800
DI = 0x5012
stationTableGenericLabel = 0
stationFdConstructionLabel = 0x4
lookupSkipIdIndex = 0
rcpServiceId = 0
dejaVuPreCheckEn = 0
Replication Bitmap: RD CD 
==============================================================

第四步：隧道接口的目标索引(DI)和重写索引(RI)句柄（Decap进程）

从之前的输出中，您已经知道DI = 0x5012意味着内部重新循环，这是有意义的，因为交换机需要内部重新循环数据包以沉积VxLAN报头。这意味着当交换机在隧道接口上收到VxLAN数据包时，需要重新分发该数据包，以删除VxLAN报头，从而能够使用原始帧中的目的MAC地址将其传送到最终目的地。为了验证重写索引，您必须检查来自本部分步骤1中收集的RI句柄的资源句柄信息：

提示：此输出的RI值43008必须与上一步的RI索引0xa800匹配(43008 DEC = 0xa800 HEX)。

EDGE-1#show platform hardware fed switch active fwd-asic abstraction print-resource-handle 0x7f9e1c9c4498 1   
Handle:0x7f9e1c9c4498 Res-Type:ASIC_RSC_PORT_LE_RI Res-Switch-Num:255 Asic-Num:255 Feature-ID:AL_FID_LISP Lkp-ftr-id:LKP_FEAT_INVALID ref_count:1
priv_ri/priv_si Handle: 0x7f9e1c9c87f8Hardware Indices/Handles: index0:0xa800  mtu_index/l3u_ri_index0:0x0  index1:0xa800  mtu_index/l3u_ri_index1:0x0 
Features sharing this resource:109 (1)]
Cookie length: 56
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

Detailed Resource Information (ASIC# 0)
----------------------------------------


Rewrite Data Table Entry, 
ASIC#:0, rewrite_type:114, RI:43008         <<<< 43008 DEC = 0xa800 HEX

 Port LE handle:         0

 Port LE Index:  275


Detailed Resource Information (ASIC# 1)
----------------------------------------


Rewrite Data Table Entry, 
ASIC#:1, rewrite_type:114, RI:43008 

 Port LE handle:         0

 Port LE Index:  275


==============================================================

故障排除

使用嵌入式数据包捕获(EPC)工具进行数据包捕获

使用EPC工具可以确认通过Tunnel0接口转发数据包时，数据包是否封装有正确的VxLAN信息。为此，您只需在构成Tunnel0（与上游设备的底层连接）的物理接口上设置EPC捕获，并使用过滤器仅捕获发送到另一台边缘交换机的RLOC的信息：

EDGE-1#show ip access-lists TAC 
Extended IP access list TAC
    10 permit ip host 192.168.3.69 host 192.168.3.68
    20 permit ip host 192.168.3.68 host 192.168.3.69

EDGE-1#mon cap tac int te1/1/1 both access-list TAC buffer size 100 
EDGE-1#show mon cap tac

Status Information for Capture tac
  Target Type: 
 Interface: TenGigabitEthernet1/1/1, Direction: BOTH
   Status : Inactive
  Filter Details: 
   Access-list: TAC
  Buffer Details: 
   Buffer Type: LINEAR (default)
   Buffer Size (in MB): 100
  File Details: 
   File not associated 
  Limit Details: 
   Number of Packets to capture: 0 (no limit)
   Packet Capture duration: 0 (no limit)
   Packet Size to capture: 0 (no limit)
   Packet sampling rate: 0 (no sampling)

EDGE-1#mon cap tac start
Started capture point : tac


####  Four ICMP Requests from local host 10.90.10.10 to remote host 10.90.10.20 were sent and then the capture was stopped.

EDGE-1#mon cap tac stop              
Capture statistics collected at software:
        Capture duration - 19 seconds
        Packets received - 12
        Packets dropped - 0
        Packets oversized - 0

Bytes dropped in asic - 0

Capture buffer will exists till exported or cleared

Stopped capture point : tac

EDGE-1#show mon cap tac buffer brief 
Starting the packet display ........ Press Ctrl + Shift + 6 to exit

  1   0.000000 00:0c:29:ef:34:d1 -> 00:0c:29:7b:35:44 ARP 110 Who has 10.90.10.20? Tell 10.90.10.10   <<<< Unicast ARP Request 
  2   0.000744 00:0c:29:7b:35:44 -> 00:0c:29:ef:34:d1 ARP 110 10.90.10.20 is at 00:0c:29:7b:35:44
  3   0.001387  10.90.10.10 -> 10.90.10.20  ICMP 124 Echo (ping) request  id=0x0001, seq=66/16896, ttl=128
  4   0.131122 00:0c:29:7b:35:44 -> 00:0c:29:ef:34:d1 ARP 110 Who has 10.90.10.10? Tell 10.90.10.20   <<<< Unicast ARP Request
  5   0.132059 00:0c:29:ef:34:d1 -> 00:0c:29:7b:35:44 ARP 110 10.90.10.10 is at 00:0c:29:ef:34:d1
  6   0.299394  10.90.10.20 -> 10.90.10.10  ICMP 124 Echo (ping) reply    id=0x0001, seq=66/16896, ttl=128 (request in 3)
  7   0.875191  10.90.10.10 -> 10.90.10.20  ICMP 124 Echo (ping) request  id=0x0001, seq=67/17152, ttl=128
  8   0.875465  10.90.10.20 -> 10.90.10.10  ICMP 124 Echo (ping) reply    id=0x0001, seq=67/17152, ttl=128 (request in 7)
  9   1.889098  10.90.10.10 -> 10.90.10.20  ICMP 124 Echo (ping) request  id=0x0001, seq=68/17408, ttl=128
 10   1.889384  10.90.10.20 -> 10.90.10.10  ICMP 124 Echo (ping) reply    id=0x0001, seq=68/17408, ttl=128 (request in 9)
 11   2.902932  10.90.10.10 -> 10.90.10.20  ICMP 124 Echo (ping) request  id=0x0001, seq=69/17664, ttl=128
 12   2.903234  10.90.10.20 -> 10.90.10.10  ICMP 124 Echo (ping) reply    id=0x0001, seq=69/17664, ttl=128 (request in 11)


#### You can also see the entire packet details with 'buffer detailed' option (use a filter for the appropriate Frame number):

EDGE-1#show mon cap tac buffer detailed | be Frame 7
Frame 7: 124 bytes on wire (992 bits), 124 bytes captured (992 bits) on interface 0
<snip>
    [Protocols in frame: eth:ethertype:ip:udp:vxlan:eth:ethertype:ip:icmp:data]
Ethernet II, Src: 00:00:00:00:00:00 (00:00:00:00:00:00), Dst: 00:00:00:00:00:00 (00:00:00:00:00:00)         <<<< Outer Layer-2 Data (VxLAN header). EPC is collected before outer layer-2 fields are added to the original frame, which is the reason why this section is empty (all-zeroes)
    Destination: 00:00:00:00:00:00 (00:00:00:00:00:00)
        Address: 00:00:00:00:00:00 (00:00:00:00:00:00)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: 00:00:00:00:00:00 (00:00:00:00:00:00)
        Address: 00:00:00:00:00:00 (00:00:00:00:00:00)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv4 (0x0800)
Internet Protocol Version 4, Src: 192.168.3.69, Dst: 192.168.3.68    <<<< Outer IP Data (VxLAN header)
    0100 .... = Version: 4
    .... 0101 = Header Length: 20 bytes (5)
    Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
        0000 00.. = Differentiated Services Codepoint: Default (0)
        .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
    Total Length: 110
    Identification: 0x2204 (8708)
    Flags: 0x02 (Don't Fragment)
        0... .... = Reserved bit: Not set
        .1.. .... = Don't fragment: Set
        ..0. .... = More fragments: Not set
    Fragment offset: 0
    Time to live: 255
    Protocol: UDP (17)
    Header checksum: 0xd1a0 [validation disabled]
        [Good: False]
        [Bad: False]
    Source: 192.168.3.69
    Destination: 192.168.3.68
User Datagram Protocol, Src Port: 65344 (65344), Dst Port: 4789 (4789)
    Source Port: 65344
    Destination Port: 4789          <<<< VxLAN UDP Port
    Length: 90
    Checksum: 0x0000 (none)
        [Good Checksum: False]
        [Bad Checksum: False]
    [Stream index: 0]
Virtual eXtensible Local Area Network
    Flags: 0x8800, GBP Extension, VXLAN Network ID (VNI)
        1... .... .... .... = GBP Extension: Defined
        .... .... .0.. .... = Don't Learn: False
        .... 1... .... .... = VXLAN Network ID (VNI): True
        .... .... .... 0... = Policy Applied: False
        .000 .000 0.00 .000 = Reserved(R): False
    Group Policy ID: 0
    VXLAN Network Identifier (VNI): 8191        <<<< VNI mapped to L2 Instance ID 8191 for L2-LISP
    Reserved: 0

########## Original Frame starts here (Inner headers) ##########
Ethernet II, Src: 00:0c:29:ef:34:d1 (00:0c:29:ef:34:d1), Dst: 00:0c:29:7b:35:44 (00:0c:29:7b:35:44)
    Destination: 00:0c:29:7b:35:44 (00:0c:29:7b:35:44)  <<<< MAC of Remote host
        Address: 00:0c:29:7b:35:44 (00:0c:29:7b:35:44)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: 00:0c:29:ef:34:d1 (00:0c:29:ef:34:d1)       <<<< MAC of Local host
        Address: 00:0c:29:ef:34:d1 (00:0c:29:ef:34:d1)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv4 (0x0800)
Internet Protocol Version 4, Src: 10.90.10.10, Dst: 10.90.10.20
    0100 .... = Version: 4
    .... 0101 = Header Length: 20 bytes (5)
    Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
        0000 00.. = Differentiated Services Codepoint: Default (0)
        .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
    Total Length: 60
    Identification: 0x30b7 (12471)
    Flags: 0x00
        0... .... = Reserved bit: Not set
        .0.. .... = Don't fragment: Not set
        ..0. .... = More fragments: Not set
    Fragment offset: 0
    Time to live: 128
    Protocol: ICMP (1)
    Header checksum: 0xe138 [validation disabled]
        [Good: False]
        [Bad: False]
    Source: 10.90.10.10          <<<< IP of Local host
    Destination: 10.90.10.20     <<<< IP of Remote host
Internet Control Message Protocol
    Type: 8 (Echo (ping) request)
    Code: 0
    Checksum: 0x4d18 [correct]
    Identifier (BE): 1 (0x0001)
    Identifier (LE): 256 (0x0100)
    Sequence number (BE): 67 (0x0043)
    Sequence number (LE): 17152 (0x4300)
    Data (32 bytes)

0000  61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0010  71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
        Data: 6162636465666768696a6b6c6d6e6f707172737475767761...
        [Length: 32]