Abstract:
A controller generates a Software Defined Network (SDN) entry for a Virtual eXtensible Local Area Network (VXLAN) Tunnel End Point (VTEP). A Match field in the generated SDN entry contains a VXLAN Network Identifier (VNI) corresponding to the SDN entry. The controller sends the generated SDN entry to the VTEP.

Description:
BACKGROUND 
       [0001]    Virtual eXtensible Local Area Network (VXLAN) is an overlay network technology, in which a message is encapsulated according to a Media Access Control (MAC) in User Datagram Protocol (UDP) method. For example, an original message may be encapsulated into a UDP message. 
         [0002]    A VXLAN includes VXLAN Tunnel End Points (VTEPs) and a tenant network composed of multiple hosts. A VTEP is an edge device of the VXLAN, and may be implemented by a physical switch or a virtual switch. Any two VTEPs may be connected by a layer 3 network and communicate with each other through establishing a tunnel between them. In a VXLAN, the tenant network is identified by a VXLAN Network identifier (VNI). A source VTEP encapsulates a message received from a source host in a tenant network into a VXLAN message, and then sends the VXLAN message to a destination VTEP via a tunnel. The destination VTEP decapsulates the received VXLAN message into the message and sends the message to a destination host. 
         [0003]    Software Defined Network (SDN) is a new type of network which may separate a control plane of a network device from a forwarding plane. In a SDN VXLAN combining a SDN and a VXLAN, a connection between a controller and a VTEP may be established according to an Openflow protocol or another SDN protocol. The controller distributes an SDN entry to the VTEP to control the forwarding of data flow on the VTEP. The controller distributes a generated SDN entry to the VTEP, and the VTEP converts the SDN entry into a routing forwarding entry and adds the routing forwarding entry to a routing forwarding table corresponding to a VNI in the SDN entry. A connection between the controller and the VTEP is established according to a Network Configuration (Netconf) protocol, and the controller configures the VTEP according to the Netconf protocol. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0004]    Features of the present disclosure are illustrated by way of example and not limited in the following figure(s), in which like numerals indicate like elements, in which: 
           [0005]      FIG. 1  is a diagram illustrating the structure of a SDN VXLAN according to an example of the present disclosure. 
           [0006]      FIG. 2  is a flowchart illustrating a method for processing a flow entry in a VXLAN according to an example of the present disclosure. 
           [0007]      FIG. 3  is a flowchart illustrating a method for processing a flow entry in a VXLAN according to another example of the present disclosure. 
           [0008]      FIG. 4  is a diagram illustrating the structure of an apparatus for processing a flow entry in a VXLAN according to an example of the present disclosure. 
           [0009]      FIG. 5  is a diagram illustrating the structure of an apparatus for processing a flow entry in a VXLAN according to another example of the present disclosure. 
           [0010]      FIG. 6  is a diagram illustrating a hardware structure of a controller according to an example of the present disclosure. 
           [0011]      FIG. 7  is a diagram illustrating a hardware structure of a VTEP according to an example of the present disclosure. 
       
    
    
     DETAILED DESCRIPTION 
       [0012]    For simplicity and illustrative purposes, the present disclosure is described by referring mainly to an example thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure. Throughout the present disclosure, the terms “a” and “an” are intended to denote at least one of a particular element. As used herein, the term “includes” means includes but not limited to, the term “including” means including but not limited to. The term “based on” means based at least in part on. 
         [0013]    A VXLAN supports overlapping of addresses of different tenants, and thus addresses of hosts belonging to different tenant networks may be the same. When addresses of N hosts that are connected to a VTEP but belongs to different tenant networks are the same, a controller generates N SDN entries for the VTEP. N is a natural number larger than 1, the addresses of N hosts are all called address  1 , and the N SDN entries may direct the forwarding of data flows whose destination addresses are address  1 . Contents in Match fields in the N SDN entries are the same, and priorities of the N SDN entries are the same. The SDN entries may for example be Openflow entries. From here on this disclosure SDN entries refer to Openflow entries for convenience, but it is to be understood that the Openflow entries may be substituted by entries according to another SDN protocol. 
         [0014]    According to the Openflow protocol, an Openflow entry is identified by its Match field and priority. Accordingly, after the controller distributes the N Openflow entries to the VTEP, the VTEP is unable to differentiate the N Openflow entries on an Openflow protocol plane. Consequently, when converting each of the N Openflow entries into a routing forwarding entry, the VTEP is unable to determine a VNI corresponding to the Openflow entry, and thus is unable to determine that the routing forwarding entry converted from the Openflow entry can be added to a routing forwarding table corresponding to which VNI. 
         [0015]      FIG. 1  is a diagram illustrating the structure of a SDN VXLAN according to an example of the present disclosure. In the SDN VXLAN shown in  FIG. 1 , VTEP 1  is connected to Host 1  via Port 1  and is connected to Host 3  via Port 2 . VTEP 2  is connected to Host 2  via Port 1  and is connected to Host 4  via Port 2 . Host 1  and Host 2  belong to a tenant network, for example, a VXLAN of VNI  10000 . Host 3  and Host 4  belong to a tenant network, for example, a VXLAN of VNI  10001 . Internet Protocol (IP) addresses of Host 1  and Host 3  are the same, and are both 10.1.1.1/24. IP addresses of Host 2  and Host 4  are the same, and are both 10.1.1.2/24. 
         [0016]    The controller establishes VXLAN Tunnel ports called VXLAN Tunnel  1  on VTEP 1  and VTEP 2  respectively according to the Netconf protocol. The controller sets a remote IP address for each VXLAN Tunnel port. For example, the controller sets a destination IP address of VXLAN Tunnel  1  on VTEP 1  is the IP address of VTEP 2 , and sets a destination IP address of VXLAN Tunnel  1  on VTEP 2  is the IP address of VTEP 1 , so as to establish a tunnel connection between VTEP 1  and VTEP 2 . After establishing the tunnel connection between VTEP 1  and VTEP 2 , VTEP 1  adds a tunnel header to an original message which is to be sent out from VXLAN Tunnel  1  on VTEP 1 , encapsulates the original message into a VXLAN message, and forwards the VXLAN message. The tunnel header is a UDP message header having multiple bytes on an outer layer. VTEP 2  adds a tunnel header to an original message which is to be sent out from VXLAN Tunnel  1  on VTEP 2 , encapsulates the original message into a VXLAN message, and forwards the VXLAN message. The tunnel header is also a UDP message header having multiple bytes on an outer layer. VTEP 1  pops up the tunnel header of the VXLAN message received from VXLAN Tunnel  1  on VTEP 1 , and forwards the obtained original message. VTEP 2  pops up the tunnel header of the VXLAN message received from VXLAN Tunnel  1  on VTEP 2 , and forwards the obtained original message. 
         [0017]    In order to implement data inter-communication among hosts belong to a tenant network, VETP 1  and VTEP 2  both save a routing forwarding table corresponding to VNI  10000  and a routing forwarding table corresponding to VNI  10001 . In various examples, routing forwarding tables saved by VTEP 1  are described. 
         [0018]    The routing forwarding table corresponding to VNI  10000  on VTEP 1  is shown in Table 1, and the routing forwarding table corresponding to VNI  10001  on VTEP 1  is shown in Table 2. 
         [0000]    
       
         
               
             
               
               
               
               
             
           
               
                 TABLE 1 
               
             
             
               
                   
               
               
                 Routing forwarding table corresponding to VNI 10000 
               
             
          
           
               
                 Serial 
                 DIP (Destination IP 
                   
                   
               
               
                 number 
                 address) 
                 Output port 
                 VNI 
               
               
                   
               
               
                 1 
                 10.1.1.1/32 
                 Port1 
                 N/A (invalid or null) 
               
               
                 2 
                 10.1.1.2/32 
                 VXLAN Tunnel 1 
                 10000 
               
               
                   
               
             
          
         
       
     
         [0000]    
       
         
               
             
               
               
               
               
               
             
           
               
                 TABLE 2 
               
             
             
               
                   
               
               
                 Routing forwarding table corresponding to VNI 10001 
               
             
          
           
               
                   
                 Serial 
                   
                   
                   
               
               
                   
                 number 
                 DIP 
                 Output port 
                 VNI 
               
               
                   
                   
               
               
                   
                 1 
                 10.1.1.1/32 
                 Port2 
                 N/A 
               
               
                   
                 2 
                 10.1.1.2/32 
                 VXLAN Tunnel 1 
                 10001 
               
               
                   
                   
               
             
          
         
       
     
         [0019]    On VTEP 1 , Port 1  is set to add to VNI  10000 , and Port 2  is set to add to VNI  10001 . 
         [0020]    Since the routing forwarding entry on the VTEP is converted from the Openflow entry distributed to the VTEP by the controller, the controller generates four Openflow entries for VTEP 1 . Openflow entries corresponding to the routing forwarding entries shown in Table 1 are shown in Table 3, and Openflow entries corresponding to the routing forwarding entries shown in Table 2 are shown in Table 4. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 3 
               
               
                   
               
               
                 Serial 
                   
                   
               
               
                 number 
                 Match 
                 Action 
               
               
                   
               
             
             
               
                 1 
                 DIP: 10.1.1.1/32 
                 OutputPort: Port1 
               
               
                 2 
                 DIP: 10.1.1.2/32 
                 OutputPort: VXLAN Tunnel 1 
               
               
                   
                   
                 Set TunnelId: 10000 
               
               
                   
               
             
          
         
       
     
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 4 
               
               
                   
               
               
                 Serial number 
                 Match 
                 Action 
               
               
                   
               
             
             
               
                 1 
                 DIP: 10.1.1.1/32 
                 OutputPort: Port2 
               
               
                 2 
                 DIP: 10.1.1.2/32 
                 OutPutPort: VXLAN Tunnel 1 
               
               
                   
                   
                 Set TunnelId: 10001 
               
               
                   
               
             
          
         
       
     
         [0021]    Contents in a Match field in an Openflow entry with serial number 1 shown in Table 3 are the same as contents in a Match field in an Openflow entry with serial number 1 shown in Table 4. Contents in a Match field in an Openflow entry with serial number 2 shown in Table 3 are the same as contents in a Match field in an Openflow entry with serial number 2 shown in Table 4. Priorities of the four Openflow entries are the same. 
         [0022]    According to the Openflow protocol, an Openflow entry is identified by its Match field and priority. Accordingly, the Openflow entry with serial number 1 shown in Table 3 is unable to be differentiated from the Openflow entry with serial number 1 shown in Table 4 on an Openflow protocol plane. The Openflow entry with serial number 2 shown in Table 3 is also unable to be differentiated from the Openflow entry with serial number 2 shown in Table 4 on the Openflow protocol plane. Consequently, after the controller distributes the four Openflow entries shown in Tables 3 and 4 to VTEP VTEP 1  is unable to differentiate the Openflow entry with serial number 1 shown in Table 3 from the Openflow entry with serial number 1 shown in Table 4, Further, when converting the two Openflow entries into routing forwarding entries, VTEP 1  is unable to determine VNIs corresponding to the two Openflow entries. Accordingly, VTEP 1  is unable to determine that the routing forwarding entries converted from the two Openflow entries should be added to routing forwarding tables corresponding to which VNIs respectively. Similarly, it is also unable to determine that the routing forwarding entries converted from the Openflow entry with serial number 2 shown in Table 3 and the Openflow entry with serial number 2 shown in Table 4 should be added to routing forwarding tables corresponding to which VNIs respectively. 
         [0023]    A method and apparatus for processing a flow entry are provided according to various examples of the present disclosure. The method may be applicable to the VXLAN shown in  FIG. 1 . 
         [0024]      FIG. 2  is a flowchart illustrating a method for processing a flow entry in a VXLAN according to an example of the present disclosure. As shown in  FIG. 2 , the method includes following blocks. 
         [0025]    At block S 201 , a controller generates an Openflow entry for a VTEP. A Match field in the generated Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0026]    At block S 202 , the controller sends the generated Openflow entry to the VTEP. 
         [0027]    In an example, the method further includes a following process. After receiving the Openflow entry from the controller, the VTEP converts the Openflow entry into a routing forwarding entry, and adds the routing forwarding entry to a routing forwarding table corresponding to the VNI contained in the Match field in the Openflow entry. The VNI may be contained in an idle field specified in the Openflow protocol, for example, an OXM_OF_PBB_ISID field. 
         [0028]    In an application scenario of the above method, addresses of N hosts that are connected to a VTEP but belongs to different VXLANs are the same. The VTEP is called a first VTEP, N is a natural number larger than 1 and the addresses of N hosts are called a first address. Based on the above application scenario,  FIG. 3  shows a flowchart illustrating a method for processing a flow entry in a VXLAN according to another example of the present disclosure. As shown in  FIG. 3 , the method includes following blocks. 
         [0029]    At block S 102 , a controller generates N Openflow entries for the first VTEP, where the N Openflow entries may direct the forwarding of data flows whose destination addresses are the first address. An OXM_OF_PBB_ISID field of a Match field in each Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0030]    In the Openflow protocol, the Match field includes an OXM_OF_PBB_ISID filed. The OXM_OF_PBB_ISID filed is optional, and has not been defined in the VXLAN. Accordingly, in various examples of the present disclosure, the OXM_OF_PBB_ISID field may be used to contain the VNI corresponding to the Openflow entry. 
         [0031]    In another example, the VNI corresponding to the Openflow entry may be contained by a field similar to the OXM_OF_PBB_ISID field or an extended self-defined field. 
         [0032]    At block S 104 , the controller sends the generated N Openflow entries to the first VTEP. 
         [0033]    At block S 106 , the first VTEP receives the N Openflow entries from the controller. 
         [0034]    At block S 108 , the first VTEP converts each of the received Openflow entries into a routing forwarding entry, and adds the routing forwarding entry to a routing forwarding table corresponding to the VNI contained in the OXM_OF_PBB_ISID field. 
         [0035]    In an example of block S 108 , the first VTEP extracts the OXM_OF_PBB_ISID field in the Match field in each of the received Openflow entries, obtains the routing forwarding entry according to remained fields in the Openflow entry, and adds the obtained routing forwarding entry to the routing forwarding table corresponding to the VNI contained in the OXM_OF_PBB_ISID field. 
         [0036]    The term “first” in “the first VTEP” and “the first address” is unrelated to a sequence, and is named for convenient and clear description. 
         [0037]    In the solution of the above examples of the present disclosure, the Match field in the Openflow entry contains the VNI corresponding to the Openflow entry. When addresses of N hosts that are connected to a VTEP but belongs to different VXLANs are the same, the Match field in each of N Openflow entries generated by the controller for the VTEP contains the VNI corresponding to the Openflow entry. N is a natural number larger than 1, the addresses of N hosts are called address  1 , and the N Openflow entries may direct the forwarding of data flows whose destination addresses are address  1 . After the controller distributes the generated N Openflow entries to the VTEP, the VTEP is able to differentiate the N Openflow entries on the Openflow protocol plane according to the VNIs contained the Match fields. Further, when converting each of the Openflow entries into a routing forwarding entry, the VTEP is able to determine that the routing forwarding entry converted from the Openflow entry corresponds to the VNI contained in the Match field, and adds the routing forwarding entry to the routing forwarding table corresponding to the VNI. 
         [0038]    The method is described by taking VTEP 1  in the VXLAN shown in  FIG. 1  as an example. The controller generates four Openflow entries for VTEP 1  according to block S 102 , as shown in Table 5. 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 5 
               
               
                   
               
               
                 Serial 
                   
                   
               
               
                 number 
                 Match 
                 Action 
               
               
                   
               
             
             
               
                 1 
                 DIP: 10.1.1.1/32 
                 OutPutPort: Port1 
               
               
                   
                 OXM_OF_PBB_ISID: 10000 
               
               
                 2 
                 DIP: 10.1.1.2/32 
                 OutputPort: VXLAN Tunnel 1 
               
               
                   
                 OXM_OF_PBB_ISID: 10000 
                 Set TunnelId: 10000 
               
               
                 3 
                 DIP: 10.1.1.1/32 
                 OutPutPort: Port2 
               
               
                   
                 OXM_OF_PBB_ISID: 10001 
               
               
                 4 
                 DIP: 10.1.1.2/32 
                 OutputPort: VXLAN Tunnel 1 
               
               
                   
                 OXM_OF_PBB_ISID: 10001 
                 Set TunnelId: 10001 
               
               
                   
               
             
          
         
       
     
         [0039]    In Table 5, an OXM_OF_PBB_ISID field is introduced into the Match field to contain a VNI corresponding to an Openflow entry. Since values of OXM_OF_PBB_ISID fields in Match fields in Openflow entries corresponding to different VNIs are different, Openflow entries having the same destination addresses are easy to be differentiated on the Openflow protocol plane. 
         [0040]    The controller distributes the four Openflow entries as shown in Table 5 to VTEP 1 . After receiving the four Openflow entries, VTEP 1  may differentiate the four Openflow entries according to the OXM_OF_PBB_ISID fields in the Match fields. VTEP 1  may convert each of the Openflow entries into a routing forwarding entry corresponding to the VNI in the Openflow entry. A method for converting each of the Openflow entries may be implemented as follows. The OXM_OF_PBB_ISID field in the Match field in the Openflow entry is extracted, and the value of the OXM_OF_PBB_ISID field is set as the value of the VNI. The other fields in the Openflow entry are converted into corresponding fields in the routing forwarding entry, and the routing forwarding entry is added to the routing forwarding table corresponding to the VNI. After VTEP 1  converts the Openflow entries with serial numbers 1 and 2. shown in Table 5, two routing forwarding entries corresponding to VNI 10000 may be obtained, as shown in Table 3, After VTEP 1  converts the Openflow entries with serial numbers 3 and 4 shown in Table 5, two routing forwarding entries corresponding to VNI  10001  may be obtained, as shown in Table 4. 
         [0041]      FIG. 4  is a diagram illustrating the structure of an apparatus for processing a flow entry in a VXLAN according to an example of the present disclosure. The apparatus may be applied to a controller. As shown in  FIG. 4 , the apparatus includes an entry generating module  301  and a sending module  302 . 
         [0042]    The entry generating module  301  may generate an Openflow entry for a VTEP. A Match field in the generated Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0043]    The sending module  302  may send the Openflow entry generated by the entry generating module  301  to the VTEP. 
         [0044]    In an example, the VNI is contained in an OXM_OF_PBB_ISID field specified in an Openflow protocol. 
         [0045]      FIG. 5  is a diagram illustrating the structure of an apparatus for processing a flow entry in a VXLAN according to another example of the present disclosure. The apparatus may be applied to a VTEP. As shown in  FIG. 5 , the apparatus includes a receiving module  401  and a converting and adding module  402 . 
         [0046]    The receiving module  401  may receive an Openflow entry generated for the VTEP by a controller. A Match field in the received Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0047]    The converting and adding module  402  may convert the Openflow entry received by the receiving module  401  into a routing forwarding entry, and add the routing forwarding entry to a routing forwarding table corresponding to the VNI contained in the Match field in the Openflow entry. 
         [0048]    in an example, the VNI is contained in an OXM_OF_PBB_ISID field specified in an Openflow protocol. 
         [0049]    In an example, the converting and adding module  402  includes an extracting unit  4021 , a processing unit  4022  and an entry adding unit  4023 . 
         [0050]    The extracting unit  4021  may extract the OXM_OF_PBB_ISID field in the Match field in the Openflow entry received by the receiving module  401 . 
         [0051]    The processing unit  4022  may obtain the routing forwarding entry according to remained fields in the Openflow entry after the extracting unit  4021  extracts the OXM_OF_PBB_ISID field in the Match field in the Openflow entry. 
         [0052]    The entry adding unit  4023  may add the routing forwarding entry obtained by the processing unit  4022  to the routing forwarding table corresponding to the VNI contained in the OXM_OF_PBB_ISID field extracted by the extracting unit  4021 . 
         [0053]    In various examples, the controller and the VTEP in the VXLAN may be programmable devices. A hardware structure of the controller may refer to  FIG. 6 , and a hardware structure of the VTEP may refer to  FIG. 7 . 
         [0054]      FIG. 6  is a diagram illustrating a hardware structure of a controller according to an example of the present disclosure. The controller includes a non-transitory storage  501 , a processor  502  (for example, a CPU) communicating with the non-transitory storage  501 , and a forwarding chip  503 . 
         [0055]    The non-transitory storage  501  may store machine readable instructions, including entry generating instructions and sending instructions that can be executed by the processor  502 . 
         [0056]    The processor  502  may communicate with the forwarding chip  503  to send a generated Openflow entry to the forwarding chip  503 . 
         [0057]    The processor  502  may read the entry generating instructions stored in the non-transitory storage  501  to perform a process of: 
         [0058]    generating an Openflow entry for a VTEP, where a Match field in the generated Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0059]    The processor  502  may read the sending instructions stored in the non-transitory storage  501  to perform a process of: 
         [0060]    sending the generated Openflow entry to the VTEP. 
         [0061]    In an example, the VNI is contained in an OXM_OF &#39; PBB_ISID field specified in an Openflow protocol. 
         [0062]    The forwarding chip  503  may send the Openflow entry received from the processor  502  to the VTEP. 
         [0063]      FIG. 7  is a diagram illustrating a hardware structure of a VTEP according to an example of the present disclosure. The VTEP includes a non-transitory storage  601 , a processor  602  (for example, a CPU) communicating with the non-transitory storage  601 , and a forwarding chip  603 . 
         [0064]    The non-transitory storage  601  may store machine readable instructions, including receiving instructions and converting and adding instructions that can be executed by the processor  602 . 
         [0065]    The processor  602  may communicate with the forwarding chip  603  to receive an Openflow entry from the forwarding chip  503 . 
         [0066]    The processor  602  may read the receiving instructions stored in the non-transitory storage  601  to perform a process of: 
         [0067]    receiving an Openflow entry generated for the VTEP by a controller, where a Match field in the received Openflow entry contains a VNI corresponding to the Openflow entry. 
         [0068]    The processor  602  may read the converting and adding instructions stored in the non-transitory storage  601  to perform a process of: 
         [0069]    converting the received Openflow entry into a routing forwarding entry, and adding the routing forwarding entry to a routing forwarding table corresponding to the VNI contained in the Match field in the Openflow entry. 
         [0070]    The forwarding chip  503  may send the Openflow entry received from the controller to the processor  602 . 
         [0071]    In an example, the VNI is contained in an OXM_OF_PBB_ISID field specified in an Openflow protocol. 
         [0072]    In an example, the converting and adding instructions may include extracting instructions, processing instructions and entry adding instructions. 
         [0073]    The processor  602  may read the extracting instructions stored in the non-transitory storage  601  to perform a process of: 
         [0074]    extracting the OXM_OF_PBB_ISID field in the Match field in the received Openflow entry. 
         [0075]    The processor  602  may read the processing instructions stored in the non-transitory storage  601  to perform a process of: 
         [0076]    obtaining the routing forwarding entry according to remained fields in the Openflow entry after the OXM_OF_PBB_ISID field in the Match field in the received Openflow entry is extracted. 
         [0077]    The processor  602  may read the entry adding instructions stored in the non-transitory storage  601  to perform a process of: 
         [0078]    adding the routing forwarding entry to the routing forwarding table corresponding to the VNI contained in the extracted OXM_OF_PBB_ISID field. 
         [0079]    In the solution of the above examples of the present disclosure, the Match field in the Openflow entry contains the VNI corresponding to the Openflow entry. When addresses of N hosts that are connected to a VTEP but belongs to different VXLANs are the same, the Match field in each of N Openflow entries generated by the controller for the VTEP contains the VNI corresponding to the Openflow entry. N is a natural number larger than 1, the addresses of N hosts are called address  1 , and the N Openflow entries may direct the forwarding of data flows whose destination addresses are address  1 . After the controller distributes the generated N Openflow entries to the VTEP, the VTEP is able to differentiate the N Openflow entries on the Openflow protocol plane according to the VNIs contained the Match fields. Further, when converting each of the Openflow entries into a routing forwarding entry, the VTEP is able to determine that the routing forwarding entry converted from the Openflow entry corresponds to the VNI contained in the Match field, and adds the routing forwarding entry to the routing forwarding table corresponding to the VNI. 
         [0080]    Although described specifically throughout the entirety of the instant disclosure, representative examples of the present disclosure have utility over a wide range of applications, and the above discussion is not intended and should not be construed to be limiting, but is offered as an illustrative discussion of aspects of the disclosure. 
         [0081]    What has been described and illustrated herein is an example along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Many variations are possible within the spirit and scope of the subject matter, which is intended to be defined by the following claims—and their equivalents—in which all terms are meant in their broadest reasonable sense unless otherwise indicated.