CN115460139A

CN115460139A - Network intercommunication method and device

Info

Publication number: CN115460139A
Application number: CN202210860929.6A
Authority: CN
Inventors: 王伟
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-07-21
Filing date: 2022-07-21
Publication date: 2022-12-09

Abstract

The application provides a network intercommunication method and a device, the method is applied to a first network device, the first network device has deployed a first network service, the first network device has established a first tunnel with a second network device, the second network device has deployed a second network service, the method comprises the following steps: receiving, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first egress identifier of the first tunnel; if the first egress identifier belongs to a first identifier of a locally established EVPN HUB service model and the first egress identifier is associated with the first network service, sending the first service packet to the first network service, so that the first network service forwards the first service packet according to a forwarding strategy of the service of the first network service.

Description

Network intercommunication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a network interworking method and apparatus.

Background

L2VPN is a two-layer VPN (Virtual Private Network) technology based on MPLS. L2VPN encapsulates two-layer data (e.g., ethernet data frames) into packets that can be transported in an IP or MPLS network, and forwarded through an IP path or MPLS tunnel. The receiving end carries out the decapsulation operation on the packet and then restores the original two-layer data, thereby realizing the transparent transmission of the two-layer data among different sites across the IP or MPLS network.

Currently, L2 VPNs can provide both point-to-point and multipoint connectivity technologies. For example, the point-to-point connection technology is called Virtual Private Wire Service (VPWS), and the point-to-multipoint connection technology is called Virtual Private LAN Service (VPLS), virtual extended LAN (VXLAN).

In recent years, due to the rise of Software Defined Network (SDN) technology and the development of 5G technology, operators generally need to expand or upgrade the original core Network to support a new Network structure. In the process of upgrading the core network, a scenario of network interworking of multiple service types may exist.

As shown in fig. 1, fig. 1 is a schematic diagram of interworking between existing multiple service type networks. In fig. 1, an Ethernet Virtual Private Network (EVPN) VPWS Network is deployed as an a-Leaf side Network device, a plurality of servers and other devices need to be accessed to meet SDN Network requirements as a B-Leaf side Network device, an EVPN VPLS Network is deployed, and multi-server access is completed by using the point-to-multipoint characteristic of the EVPN VPLS Network.

When the networks of the two service types need to realize intercommunication, a two-layer switching technology is preferentially adopted, a two-layer switch is deployed between the VPWS network and the VPLS network, the flow of the VPWS network side and the flow of the VPLS network side are introduced into the two-layer switch, and the flow of the two network sides is switched in a two-layer switching mode.

Even though the above scheme can implement interworking of networks of multiple service types, the following drawbacks are caused: the intercommunication of the existing multi-service type network inevitably introduces fixed equipment, and the network cost is increased.

Disclosure of Invention

In view of this, the present application provides a network interworking method and apparatus, so as to solve the problem that fixed equipment is introduced and network cost is increased in the existing multiple service type network interworking scheme.

In a first aspect, the present application provides a network interworking method, where the method is applied to a first network device, the first network device has deployed a first network service, the first network device has established a first tunnel with a second network device, and the second network device has deployed a second network service, and the method includes:

receiving, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first egress identifier of the first tunnel;

if the first exit identifier belongs to a first identifier of a locally established EVPN HUB service model and the first exit identifier is associated with the first network service, sending the first service message to the first network service so that the first network service forwards the first service message according to a forwarding strategy of the service per se;

the first network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, the second network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, and the first network service is different from the second network service.

In a second aspect, the present application provides a network interworking apparatus, where the apparatus is applied to a first network device, the first network device has deployed a first network service, the first network device has established a first tunnel with a second network device, and the second network device has deployed a second network service, and the apparatus includes:

a receiving unit, configured to receive, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first exit identifier of the first tunnel;

a sending unit, configured to send the first service packet to the first network service if the first egress identifier belongs to a first identifier of a locally established EVPN HUB service model and the first egress identifier is associated with the first network service, so that the first network service forwards the first service packet according to a forwarding policy of its own service;

In a third aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.

Therefore, by applying the network interworking method and apparatus provided by the present application, through a first tunnel, a first network device receives a first service packet sent by a second network device, where the first service packet includes a first egress identifier of the first tunnel; if the first exit identifier belongs to a first identifier of a locally established EVPN HUB service model and the first exit identifier is associated with the first network service, the first network device sends a first service message to the first network service, so that the first network service forwards the first service message according to a forwarding strategy of the service of the first network device.

Therefore, a tunnel is established between network devices supporting different network services by using the EVPN HUB service model constructed locally. The exit identifier of the tunnel is encapsulated on the outer layer of the service message, so that the receiving end can identify the exit identifier and process the message different from the local network service. The problem that fixed equipment is introduced to increase network cost in the existing multi-type service network intercommunication scheme is solved. The purpose of network intercommunication of various service types can be achieved without adding extra equipment in the network.

Drawings

Fig. 1 is a schematic diagram of interworking between networks of multiple service types in the prior art;

fig. 2 is a flowchart of a network interworking method according to an embodiment of the present application;

fig. 3 is a schematic diagram of interworking between networks of multiple service types according to an embodiment of the present application;

fig. 4 is a structural diagram of a network interworking apparatus according to an embodiment of the present application;

fig. 5 is a hardware structure of a network device according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the exemplary embodiments below do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.

A network interworking method provided in an embodiment of the present application is described in detail below. Referring to fig. 2, fig. 2 is a flowchart of a network interworking method provided in the embodiment of the present application. The method is applied to the first network equipment. The network interworking method provided by the embodiment of the application can comprise the following steps.

Step 210, receiving, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first egress identifier of the first tunnel;

specifically, the first network device, the second network device, and the third network device have implemented IP interworking and established BGP EVPN neighbors.

Different network services are respectively deployed in the first network device, the second network device and the third network device. For example, the first network service is EVPN VPWS, the second network service is EVPN VPLS, and the third network service is EVPN VXLAN.

The method comprises the steps that a first tunnel is established between first network equipment and second network equipment; similarly, the first network device also establishes a second tunnel with the second network device. And through the established tunnel, the network equipment realizes the intercommunication of the networks with various service types.

Through the first tunnel, the first network device receives a first service packet sent by the second network device, where the first service packet includes a first exit identifier of the first tunnel.

Optionally, before this step, a process of constructing an EVPN centralized exchange (HUB) service model, synchronizing EVPN route advertisement messages, establishing a tunnel with an opposite end, and sending a service message to the opposite end by using the tunnel is further included in the first network device.

It is understood that the second network device and the third network device both need to perform the above optional processes, and the first network device is taken as an example for description below.

The EVPN HUB function is started in the first network device, that is, the EVPN HUB service model is built in the first network device. Service members are included in the EVPN HUB service model, and a service member may represent a certain network service supported by a network device (e.g., service member 1 supports EVPN VPWS service, or service member 1 supports EVPN VPLS service, or service member 1 supports EVPN VXLAN service). And each service member in different network equipment and belonging to the same EVPN HUB service model can realize network intercommunication of multiple service types according to rules defined in the EVPN HUB service model.

In the embodiment of the present application, the EVPN HUB service model has an identifier, that is, an EVPN HUB ID, and is used to identify, at the network device, the EVPN HUB service model to which the network service supported by the network device belongs. Meanwhile, according to the network service supported by the first network device, an EVPN HUB mark (FLAG) is configured for the network service, and the EVPN HUB mark of each network service is associated with a service member in the EVPN HUB service model.

For example, if the first network device supports EVPN VPWS service, the EVPN HUB flag is 1, and a service member in the EVPN HUB service model is associated with EVPN HUB flag 1; the first network equipment supports EVPN VPLS service, the EVPN HUB mark is 2, service members in the EVPN HUB service model are associated with the EVPN HUB mark 2; and if the first network equipment supports EVPN VXLAN service, the EVPN HUB mark is 3, service members in the EVPN HUB service model are associated with the EVPN HUB mark 3.

The EVPN HUB flag may also be used to distinguish network traffic supported by the peer network device. When the network devices at two ends support the same type of network service, the EVPN HUB marks are the same. Therefore, no intercommunication requirement exists between the two end network devices, and the EVPN HUB service model building process cannot be entered.

It can be appreciated that since the first network device can support multiple network services simultaneously, multiple service members may be configured within the EVPN HUB service module, each associated with one EVPN HUB tag, that is, each associated with one network service supported. Of course, a plurality of EVPN HUB service models may also be established in the first network device, each EVPN HUB service model is configured with one service member, and the plurality of EVPN HUB service models are applicable to a scenario in which the first network device includes a plurality of VMs and each VM supports different network services.

After completing the function starting of the EVPN HUB, configuring the EVPN HUB ID and the EVPN HUB mark of the network service, the first network equipment generates and issues an EVPN route notification message to BGP EVPN neighbors. The EVPN route advertisement message includes an EVPN HUB ID and an EVPN HUB flag, so that the opposite end determines the network service supported by the first network device and the EVPN HUB service model to which the network service belongs, and establishes a corresponding tunnel with the first network device under the same EVPN HUB service model.

The Tunnel may be a novel Tunnel defined in the embodiment of the present application, that is, an ethernet virtual private network centralized switching Tunnel (EVPN HUB Tunnel, abbreviated as EHT). The EHT is used for shielding the message encapsulation difference of different service types and realizing concise message exchange.

It can be understood that each network device generates and issues different types of EVPN route advertisement messages to BGP EVPN neighbors according to the network services supported by itself.

For example, if the first network device supports the EVPN VPWS service, the first network device generates and issues an EVPN 1-class route advertisement message to the outside; if the second network equipment supports the EVPN VPLS service, the second network equipment generates and externally issues an EVPN 1/2/3 type route notification message; if the third network equipment supports the EVPN VXLAN service, the third network equipment generates and externally issues an EVPN 1/2/3 type route notification message.

In this embodiment of the present application, a first network device generates a first EVPN route advertisement message, where the first EVPN route advertisement message includes an EVPN HUB ID (also referred to as a first identifier) of a locally established EVPN HUB service model, and an EVPN HUB flag (also referred to as a first EVPN HUB flag) corresponding to a first network service.

The first network equipment adds a portable field in an Ext-Community attribute (extended Community attribute) included in an EVPN route notification message: EVPN HUB attribute field. This field takes 4 bytes and has the format: < EVPN HUB: id xxx, flag xxx >.

Wherein, ID and FLAG refer to the above definitions, ID occupies 3 bytes (value range 0-16777215), and FLAG occupies 1 byte (value range 0-256).

The first network equipment sends a first EVPN route notification message to the second network equipment and the third network equipment respectively. After receiving the first EVPN route notification message, the second network device and the third network device acquire a first identifier and a first EVPN HUB mark from the first EVPN route notification message.

The second network device is taken as an example for explanation.

The second network device identifies whether the first identity matches a locally established EVPN HUB ID (also referred to as a second identity). And if so, identifying whether the first EVPN HUB mark is matched with an EVPN HUB mark (also called as a second EVPN HUB mark) corresponding to a second network service supported by the first EVPN HUB mark.

If not, the second network device determines that the network service supported by the first network device is different from the network service supported by the second network device, and the second network device establishes the first tunnel by taking the second network device as a starting point and the first network device as an end point.

The first EVPN route advertisement packet further includes a first egress identifier, where the first egress identifier is used to enable the opposite end to distinguish the service type to which the service packet belongs, that is, the network service supported by the network device that sends the service packet. After the second network device establishes the first tunnel, the first exit identifier and the first EVPN HUB flag are also associated with the first tunnel.

Similarly, the third network device establishes a second tunnel and associates the first egress identifier, the first EVPN HUB flag, and the second tunnel.

In the embodiment of the present application, the egress identifier is associated with EVPN HUB ID, EHT. The significance lies in that: the service message sent out locally through the EHT will encapsulate the egress identifier outside the service message. And after receiving the service message, the opposite terminal acquires the exit identifier and determines whether a corresponding EVPN HUB ID exists locally. If the service message exists locally, the service message can be delivered to a service member corresponding to the exit identifier in the EVPN HUB service model indicated by the EVPN HUB ID (the network service associated with the service member is the same as the network service corresponding to the exit identifier) for further processing, so that network intercommunication of multiple service types is realized.

The egress identifier may be specifically an identifier already existing in an existing EVPN route, and the identifier may be specifically an attribute identifier representing an attribute of the network device. It can be understood that, when issuing an existing EVPN route, the attribute identifier of the network device is already sent to the peer, and in this embodiment, the peer may use the attribute identifier as an egress identifier.

In different networks, the egress identifier may be implemented by different attribute identifications. For example, in an IPv4 network, the egress identifier may be specifically a LABEL MPLS LABEL of the network device, in an IPv6 network, the egress identifier may be specifically an address SRv6 SID of the network device, and in a VXLAN network, the egress identifier may be specifically a VXLAN ID of a VXLAN to which the network device belongs.

It should be noted that, because the services supported by the network device are different, the network device may simultaneously send multiple types of EVPN route advertisements, and after the opposite end obtains the multiple types of EVPN route advertisements, the opposite end may preferentially obtain attribute identifier representations included in a certain type of EVPN route advertisements as the egress identifiers.

For example, the home terminal supports EVPN VPWS service, and the opposite terminal supports EVPN VPLS/VXLAN service. If the local terminal establishes the EHT tunnel to the opposite terminal, the exit identifier is obtained by the EVPN 1/2/3 type route issued by the opposite terminal, and the local terminal preferentially obtains the attribute representation included by the EVPN1 type route as the exit identifier.

The local terminal supports the EVPN VPLS service, and the opposite terminal supports the EVPN VPWS service. If the local terminal establishes the EHT tunnel to the opposite terminal, the exit identifier is acquired by the EVPN1 type route issued by the opposite terminal.

It is understood that the network device sends multiple types of EVPN route advertisements, each including an EVPN HUB ID, an EVPN HUB flag, and an egress identifier.

The home terminal supports EVPN VPLS service, and the opposite terminal supports EVPN VXLAN service. If the local terminal establishes the EHT tunnel to the opposite terminal, the exit identifier is obtained by the EVPN 1/2/3 type route issued by the opposite terminal, and the local terminal preferentially obtains the attribute representation included by the EVPN1 type route as the exit identifier.

The local terminal supports EVPN VXLAN service, and the opposite terminal supports EVPN VPWS service. If the local terminal establishes the EHT tunnel to the opposite terminal, the exit identifier is obtained by the EVPN1 type route issued by the opposite terminal.

The home terminal supports EVPN VXLAN service, and the opposite terminal supports VPLS service. If the local terminal establishes the EHT tunnel to the opposite terminal, the exit identifier is obtained by the EVPN 1/2/3 type route issued by the opposite terminal, and the local terminal preferentially obtains the attribute representation included by the EVPN1 type route as the exit identifier.

Similarly, the first network device also receives EVPN route advertisement messages issued by the second network device and the third network device, and establishes an EHT tunnel.

The process of generating the EVPN route advertisement message by the second network device and the third network device is the same as the process of generating the EVPN route advertisement message by the first network device, and will not be repeated here.

Optionally, the first network device receives a second EVPN route advertisement message sent by the second network device, where the second EVPN route advertisement message includes a second identifier of an EVPN HUB service model that has been established locally by the second network device and a second EVPN HUB flag corresponding to the second network service.

The first network device identifies whether the second identity matches the first identity. If the first EVPN HUB mark is matched with the second EVPN HUB mark, the first network equipment continues to identify whether the second EVPN HUB mark is matched with the first EVPN HUB mark. If not, the first network device determines that the network service supported by the second network device is different from the first network device. The first network device establishes a first tunnel with itself as a starting point and the second network device as an ending point.

Similarly, the first network device receives a third EVPN route advertisement message sent by the third network device, where the third EVPN route advertisement message includes a third identifier of an EVPN HUB service model established locally by the third network device and a third EVPN HUB flag corresponding to the third network service.

The first network device identifies whether the third identity matches the first identity. If so, the first network device continues to identify whether the third EVPN HUB flag matches the first EVPN HUB flag. And if not, the first network equipment determines that the network service supported by the third network equipment is different from the first network equipment. And the first network equipment takes the first network equipment as a starting point and takes the third network equipment as an end point to establish a second tunnel.

Optionally, the second EVPN route advertisement message further includes a third egress identifier (referred to as a third egress identifier sent by the second network device herein in order to correspond the second egress identifier to the second tunnel), and the third EVPN route advertisement message further includes the second egress identifier.

After the first network device establishes the first tunnel and the second tunnel, the first network device associates a third egress identifier and a second EVPN HUB mark with the first tunnel and associates a second egress identifier and a third EVPN HUB mark with the second tunnel.

Subsequently, the first network device may send the service packet to the second network device and the third network device by using the first tunnel and the second tunnel.

The first network device sends a service packet to the third network device.

Optionally, the first network device receives a private network packet sent by the virtual machine. And determining an output interface for forwarding the private network message according to the first network service characteristics deployed by the user. And when the outlet interface for forwarding the private network message is determined to be the second tunnel, the first network equipment acquires a second outlet identifier of the second tunnel.

And the first network equipment encapsulates a second outlet identifier on the outer layer of the private network message and encapsulates the public network tunnel information on the outer layer of the second outlet identifier to obtain a second service message. And the first network equipment sends the second service message to the third network equipment through the second tunnel.

It should be noted that, the process of encapsulating the second egress identifier in the outer layer of the private network packet is to encapsulate the second egress identifier as a header in the outer layer of the private network packet. For example, in an IPv4 network, the egress identifier may be encapsulated as an MPLS header in the outer layer of the private network packet, in an IPv6 network, the egress identifier may be encapsulated as an IPv6 header in the outer layer of the private network packet, and in a VXLAN network, the egress identifier may be encapsulated as a VXLAN header in the outer layer of the private network packet.

In the embodiment of the present application, after the EVPN HUB flag is associated with the EHT, the EHT further has an attribute of a network service. The attribute of the network service is the same as that of the EVPN HUB flag, that is, the network service is used to distinguish the type of the peer network service.

For example, if the home terminal supports EVPN VPWS service and the opposite terminal supports EVPN VPLS service, the tunnel service attribute of the EHT established by the home terminal is 2, which indicates that the EHT opposite terminal supports EVPN VPLS service, and meanwhile, the home terminal associates the EHT with the EVPN HUB ID of the EVPN HUB service model.

If the local end supports the EVPN VPWS service and the opposite end supports the EVPN VXLAN service, the tunnel service attribute of the EHT established by the local end is 3, which indicates that the EHT opposite end supports the EVPN VXLAN service, and meanwhile, the local end also associates the EHT with the EVPN HUB ID of the EVPN HUB service model.

In the embodiment of the present application, the EHT is further provided with a learning attribute, i.e., learning the MAC address. For example, the EVPN VPWS service is a point-to-point service, and is forwarded through the binding relationship between the AC and the PW instead of through the lookup MAC table in the process of forwarding the packet. That is, no MAC table is established within a network device supporting the EVPN VPWS service.

Therefore, in the EVPN HUB service model, after receiving a service message sent by an opposite end from an EHT, the EVPN VPLS service/VXLAN service determines that the opposite end is an EVPN VPWS service through the service attribute of the EHT, learns the source MAC address of the service message to the EHT, and issues an EVPN 2-type route advertisement message corresponding to the MAC address. And if the opposite end is determined to be EVPN VPLS service/EVPN VXLAN service through the service attribute of the EHT, the source MAC address is not learned.

Step 220, if the first egress identifier belongs to a first identifier of a locally established EVPN HUB service model and the first egress identifier is associated with the first network service, sending the first service packet to the first network service, so that the first network service forwards the first service packet according to a forwarding policy of its own service.

Specifically, according to the description in step 210, after acquiring the first egress identifier of the first tunnel, the first network device identifies whether the first egress identifier belongs to the first identifier of the locally established EVPN HUB service model.

If so, the first network device continues to identify whether the first egress identifier is associated with the first network traffic. If yes, the first network device determines that the network service supported by the first network device can process the first service message. The first network equipment sends a first service message to a first network service, so that the first network service forwards the first service message according to a forwarding strategy of the first network service.

In this embodiment of the present application, the

steps

210 and 220 may be performed by an EVPN HUB VIRTUAL tunnel ENDPOINT (EHVE ENDPOINT for short) configured in the first network device.

The EHVE endpoint is a virtual endpoint in the EVPN network, is a protocol level or a logic level, is non-physically present, is used for corresponding to network services supported by an opposite end but not supported by a home end, establishes EHT and realizes communication of cross-network services.

Therefore, by applying the network interworking method provided by the present application, through the first tunnel, the first network device receives the first service packet sent by the second network device, where the first service packet includes the first exit identifier of the first tunnel; if the first exit identifier belongs to a first identifier of a locally established EVPN HUB service model and the first exit identifier is associated with the first network service, the first network device sends a first service message to the first network service, so that the first network service forwards the first service message according to a forwarding strategy of the service of the first network device.

The first network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, the second network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, and the first network service is different from the second network service; the EVPN HUB service model comprises a plurality of service members, and each service member corresponds to an exit identifier associated with one network service.

Therefore, a tunnel is established between network devices supporting different network services by using the EVPN HUB service model constructed locally. By encapsulating the exit identifier of the tunnel in the outer layer of the service message, the receiving end can identify the exit identifier and process the message different from the local network service. The problem that fixed equipment is introduced to increase network cost in the existing multi-type service network intercommunication scheme is solved. The purpose of network intercommunication of various service types can be achieved without adding extra equipment in the network.

The following describes the network interworking method provided in the embodiment of the present application in detail. Referring to fig. 3, fig. 3 is a schematic diagram of interworking between networks of multiple service types according to an embodiment of the present application. In fig. 3, three network devices a, B, and C are included, and each network device is respectively connected to 1 VM.

Assume that network device a deploys EVPN VXLAN services, network device B deploys EVPN VPWS services, and network device C deploys EVPN VPLS services. EVPN services of the network equipment A, B and C are communicated through an EVPN HUB service model.

The EVPN route announcement message issuing process comprises the following steps:

network devices a, B, C have implemented IP interworking and all establish BGP EVPN neighbors with each other.

Network device a configures EVPN VXLAN service, specifies RD (100)/RT (100). At this point EVPN HUB FLAG is 3, indicated as VXLAN service tag. The network device attribute for network device a is identified as 200 (which identifies the egress identifier that can be used by the peer as a tunnel). The network equipment A issues an EVPN 3 type route notification message.

Network device B configures EVPN VPWS service, specifies RD (100)/RT (100). At this time, EVPN HUB FLAG is 1 and is indicated as VPWS service mark. The network device attribute of network device B is identified as 100 (which identifies the egress identifier that can be used by the peer as a tunnel). And the network equipment B issues an EVPN1 type route notification message.

The network equipment C configures EVPN VPLS service, specifies RD (100)/RT (100). At this point EVPN HUB FLAG is 2, denoted VPLS traffic FLAG. The network device attribute of network device C is identified as 300 (which identifies the egress identifier that can be used by the peer as a tunnel). And the network equipment C issues an EVPN 3 type route notification message.

The network equipment receives, identifies, processes and establishes an EHT (Ethernet virtual private network) route notification message:

the network equipment A receives an EVPN1 type route notification message issued by the network equipment B. The network device A identifies that the RT included in the EVPN1 type route announcement message is matched with the attribute of the local Import target, but the EVPN1 type route announcement message does not include the VXLAN ID, and the network device A cannot establish the VXLAN tunnel with the network device B.

The network device A identifies an EVPN HUB ID and an EVPN HUB FLAG which are included in the EVPN1 type route notification message, the EVPN HUB ID is matched with the EVPN HUB ID configured locally, the EVPN HUB FLAG is 1, and the network device B is shown to support EVPN VPWS service, which is different from the locally supported service. The network device A establishes the EHT1 by taking the network device A as an EHVE starting point and taking the network device B as an EHVE end point. The egress identifier of EHT1 may be determined from a network device attribute identification (100) included in the EVPN class 1 route advertisement message. The network device A associates the EHT1 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and the service members are locally supported EVPN VXLAN services.

And the network equipment A receives the EVPN 3 type route notification message issued by the network equipment C. The network device a recognizes that the RT included in the EVPN 3-type route advertisement message matches the local Import target attribute, but the VXLAN ID is not included in the EVPN 3-type route advertisement message, and the network device a cannot establish a VXLAN tunnel with the network device C.

Network equipment A identifies EVPN HUB ID and EVPN HUB FLAG included in EVPN 3 type routing advertisement message, EVPN HUB ID is matched with locally configured EVPN HUB ID, EVPN HUB FLAG is 2, and network equipment C supports EVPN VPLS service, which is different from locally supported service. The network device a establishes an EHT2 with itself as an EHVE starting point and the network device C as an EHVE ending point. The egress identifier of EHT2 may be determined from a network device attribute identification (300) included in the EVPN type 3 route advertisement message. The network device A associates the EHT2 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and the service members are locally supported EVPN VXLAN services.

Similarly, the network device B receives the EVPN 3-type route advertisement message issued by the network device a. The network device B recognizes that the RT included in the EVPN 3-type route advertisement packet matches with the local Import target attribute, but the VPWS service ID is not included in the EVPN 3-type route advertisement packet, and the network device B cannot establish the EVPN PW tunnel with the network device a.

And the network equipment B identifies the EVPN HUB ID and the EVPN HUB FLAG which are included in the EVPN 3 type routing notification message, the EVPN HUB ID is matched with the locally configured EVPN HUB ID, and the EVPN HUB FLAG is 3, which indicates that the network equipment A supports EVPN VXLAN services and is different from locally supported services. And the network equipment B establishes the EHT3 by taking the network equipment B as an EHVE starting point and taking the network equipment A as an EHVE end point. The egress identifier of EHT3 may be determined from a network device attribute identification (200) included in the EVPN type 3 route advertisement message. The network device B associates the EHT3 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and the service members are locally supported EVPN VPWS services.

And the network equipment B receives the EVPN 3 type route notification message issued by the network equipment C. The network device B recognizes that the RT included in the EVPN 3-type route advertisement packet matches with the local Import target attribute, but the VPWS service ID is not included in the EVPN 3-type route advertisement packet, and the network device B cannot establish the EVPN PW tunnel with the network device C.

Network equipment B identifies an EVPN HUB ID and an EVPN HUB FLAG which are included in the EVPN 3 type routing advertisement message, the EVPN HUB ID is matched with the EVPN HUB ID configured locally, the EVPN HUB FLAG is 2, and the network equipment C is shown to support an EVPN VPLS service, which is different from the locally supported service. And the network equipment B establishes the EHT4 by taking the network equipment B as an EHVE starting point and taking the network equipment C as an EHVE end point. The egress identifier of EHT4 may be determined from a network device attribute identification (300) included in the EVPN class 3 route advertisement message. And the network equipment B associates the EHT4 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and service members are locally supported EVPN VPWS services.

Similarly, the network device C receives the EVPN 1-type route passing message issued by the network device B, and recognizes that the RT included in the EVPN 1-type route advertisement message matches with the local Import target attribute, but the EVPN 1-type route advertisement message does not include a PW label, so that the network device C cannot establish an EVPN PW tunnel with the network device B.

The network equipment C identifies EVPN HUB ID and EVPN HUB FLAG included in the EVPN1 type routing passing message, the EVPN HUB ID is matched with the EVPN HUB ID configured locally, the EVPN HUB FLAG is 1, and the network equipment B supports EVPN VPWS service which is different from locally supported service. And the network equipment C establishes the EHT5 by taking the network equipment C as an EHVE starting point and taking the network equipment B as an EHVE end point. The egress identifier of EHT5 may be determined from a network device attribute identification (100) included in the EVPN class 1 route advertisement message. And the network equipment C associates the EHT5 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and the service members are locally supported EVPN VPLS services.

The network device C receives an EVPN 3 type routing passing message issued by the network device A, identifies that the RT included in the EVPN 3 type routing notification message is matched with the attribute of the local Import target, and if the EVPN 3 type routing notification message does not include a PW label, the network device C cannot establish an EVPN PW tunnel with the network device A.

The network equipment C identifies the EVPN HUB ID and the EVPN HUB FLAG which are included in the EVPN 3 type routing passing message, the EVPN HUB ID is matched with the EVPN HUB ID configured locally, the EVPN HUB FLAG is 3, and the network equipment A supports EVPN VXLAN services which are different from the locally supported services. The network device C establishes an EHT6 with itself as the EHVE starting point and the network device a as the EHVE ending point. The egress identifier of EHT6 may be determined from a network device attribute identification (200) included in the EVPN class 3 route advertisement message. The network equipment C associates the EHT6 with a local EVPN HUB service model, the ID of the EVPN HUB service model is 123, and service members are locally supported EVPN VPLS services.

Up to this point, EVPN HUB service models between network devices a, B, and C are all created, and 3 EVPN services between network devices a, B, and C can be intercommunicated through the EVPN HUB service models:

the network equipment A establishes 2 EHTs, wherein EHT1 leads to the direction of network equipment B, and EHT2 leads to the direction of network equipment C; the network device B establishes 2 EHTs, wherein the EHT3 leads to the direction of the network device A, and the EHT4 leads to the direction of the network device C; network device C establishes 2 EHTs, with EHT5 leading in the direction of network device B and EHT6 leading in the direction of network device a.

And a service message forwarding process:

the forwarding behaviors among the network devices a, B, and C are similar, and the following description will take the forwarding between the network device a and the network device B as an example.

The network device A sends a service message to the network device B:

the network equipment A receives a private network message X sent by the VM1. Because the network device A deploys the EVPN VXLAN service, the network device A learns the source MAC address included in the private network message X and establishes the MAC table. The network equipment A issues an EVPN2 type route announcement message to BGP EVPN neighbors, and then queries a local MAC table according to the forwarding rule of an EVPN VXLAN service. And if the item corresponding to the destination MAC address included in the private network message X is found in the local MAC table, forwarding according to an output interface indicated by the found MAC item, otherwise, broadcasting and forwarding in the EVPN VXLAN. In this example, the network device a finds the MAC entry corresponding to the destination MAC address, and the output interface indicated by the MAC entry is EHT1. And the network equipment A encapsulates the exit identifier of the EHT1 on the outer layer of the private network message X, and encapsulates the public network tunnel information on the outer layer of the exit identifier to obtain the service message. And forwarding the service message to the network equipment B through the EHT1.

After receiving the service message through the EHT1, the network device B first strips the public network tunnel encapsulation. Then, the network device B identifies the egress identifier included in the traffic packet. The exit identifier belongs to ID 123 of the EVPN HUB service model created locally by network device B, and a service member of the EVPN HUB service model supports EVPN VPWS service, and network device B forwards the private network packet X to the locally supported EVPN VPWS service for forwarding processing. After receiving the private network message X, the EVPN VPWS service determines an AC1 port associated with the EHT1, and forwards the private network message X to the VM2 through the AC1 port.

The network device B sends a service message to the network device A:

the network device B receives the private network message Y sent by the VM2 through the AC1 port, and determines the EHT for forwarding the private network message Y through the incidence relation between the AC1 port for receiving the private network message Y and the EHT as the network device B deploys the EVPN VPWS service. In this example, AC1 port is associated with EHT1, i.e., forwarded to network device a. And the network equipment B encapsulates the export identifier of the EHT1 on the outer layer of the private network message Y, and encapsulates the public network tunnel information on the outer layer of the export identifier to obtain the service message. And forwarding the service message to the network equipment A through the EHT1.

After receiving the service message through the EHT1, the network device A first strips the public network tunnel encapsulation. Then, the network device a identifies the egress identifier included in the traffic packet. The exit identifier belongs to the ID 123 of the EVPN HUB service model created locally by the network device a, and the service member of the EVPN HUB service model supports the EVPN VXLAN service, and the network device a forwards the private network packet Y to the locally supported EVPN VXLAN service for forwarding processing. After receiving the private network message Y, the EVPN VXLAN service determines the opposite end of the EHT1, namely the network equipment B supports the VPWS service according to the EVPN HUB mark associated with the EHT1, the EVPN VXLAN service learns the source MAC address of the private network message Y, establishes an MAC table and issues an EVPN2 type route notification message to BGP EVPN neighbors. The EVPN VXLAN service firstly inquires a local MAC table according to the forwarding rule of the VXLAN service. And if the table entry corresponding to the destination MAC address included in the private network message Y is inquired in the local MAC table, forwarding is carried out according to the outlet interface indicated by the searched MAC table entry, otherwise, the forwarding is carried out in a broadcast mode in the EVPN VXLAN. In this example, the network device a finds the MAC entry corresponding to the destination MAC address and the output interface indicated by the MAC entry is an interface connected to the VM1, and then the network device a forwards the private network packet Y to the VM1 through the interface.

It should be noted that the EVPN 2-type route advertisement message issued by the EVPN VXLAN service includes, in addition to the content included in the existing EVPN 2-type route advertisement message, an EVPN HUB ID and an EVPN HUB FLAG. Wherein, EVPN HUB FLAG is 1, and is used to indicate that the MAC address learned from EHT1 is obtained from a service packet sent by a network device supporting EVPN VPWS service.

Based on the same inventive concept, the embodiment of the application also provides a network intercommunication device corresponding to the network intercommunication method. Referring to fig. 4, fig. 4 is a network interworking apparatus provided in this embodiment of the present application, where the apparatus is applied to a first network device, the first network device has deployed a first network service, the first network device has established a first tunnel with a second network device, and the second network device has deployed a second network service, and the apparatus includes:

a receiving unit 410, configured to receive, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first egress identifier of the first tunnel;

a sending unit 420, configured to send the first service packet to the first network service if the first egress identifier belongs to a first identifier of a locally established EVPN HUB service model and the first egress identifier is associated with the first network service, so that the first network service forwards the first service packet according to a forwarding policy of its own service;

Optionally, the first network device has established a second tunnel with a third network device, where the third network device has deployed a third network service;

the receiving unit 410 is further configured to receive a private network message sent by the virtual machine;

the device further comprises: an obtaining unit (not shown in the figure), configured to obtain a second egress identifier of the second tunnel when it is determined that an egress interface used for forwarding the private network packet is the second tunnel;

a processing unit (not shown in the figure), configured to encapsulate the second egress identifier on an outer layer of the private network packet, and encapsulate public network tunnel information on an outer layer of the second egress identifier, to obtain a second service packet;

the sending unit 420 is further configured to send the second service packet to the third network device through the second tunnel;

the first network service is any one of an EVPN VPWS, an EVPN VPLS and an EVPN VXLAN, the third network service is any one of an EVPN VPWS, an EVPN VPLS and an EVPN VXLAN, and the first network service is different from the third network service.

Optionally, the sending unit 420 is further configured to send a first EVPN route advertisement message to the second network device and the third network device, where the first EVPN route advertisement message includes the first identifier, a first EVPN HUB flag corresponding to the first network service, and the first egress identifier, so that the second network device or the third network device establishes the first tunnel and the second tunnel respectively, and associates the first egress identifier and the first EVPN HUB flag with the corresponding tunnel, using itself as a starting point, and using the first network device as an ending point after determining that an EVPN HUB service model matching the first identifier is established locally and that the local network service is not matched with the first EVPN HUB flag.

Optionally, the receiving unit 410 is further configured to receive a second EVPN route advertisement message sent by the second network device, where the second EVPN route advertisement message includes a second identifier of an EVPN HUB service model that has been locally established by the second network device and a second EVPN HUB flag corresponding to the second network service;

the device further comprises: a building unit (not shown in the figure), configured to build the first tunnel with the first network device as a starting point and the second network device as an ending point if the second identifier matches the first identifier and the second EVPN HUB flag does not match the first EVPN HUB flag;

alternatively, the first and second liquid crystal display panels may be,

the receiving unit 410 is further configured to receive a third EVPN route advertisement message sent by the third network device, where the third EVPN route advertisement message includes a third identifier of an EVPN HUB service model locally established by the third network device and a third EVPN HUB flag corresponding to the third network service;

the device further comprises: a building unit (not shown in the figure), configured to build the second tunnel with the first network device as a starting point and the third network device as an ending point if the third identifier matches the first identifier and the third EVPN HUB flag does not match the first EVPN HUB flag.

Optionally, the second EVPN route advertisement message further includes a third egress identifier;

the device further comprises: an associating unit (not shown in the figure) for associating the third egress identifier, the second EVPN HUB flag and the first tunnel;

the third EVPN route advertisement message further includes the second egress identifier;

the associating unit (not shown) is further configured to associate the second egress identifier, the third EVPN HUB flag, and the second tunnel.

Therefore, by applying the network interworking apparatus provided by the present application, through the first tunnel, the first network device receives the first service packet sent by the second network device, where the first service packet includes the first egress identifier of the first tunnel; if the first exit identifier belongs to a first identifier of a locally established EVPN HUB service model and the first exit identifier is associated with the first network service, the first network device sends a first service message to the first network service, so that the first network service forwards the first service message according to a forwarding strategy of the service of the first network device.

Therefore, a tunnel is established between network devices supporting different network services by using the locally constructed EVPN HUB service model. By encapsulating the exit identifier of the tunnel in the outer layer of the service message, the receiving end can identify the exit identifier and process the message different from the local network service. The problem that fixed equipment is introduced to increase network cost in the existing multi-type service network intercommunication scheme is solved. The purpose of network intercommunication of various service types can be achieved without adding extra equipment in the network.

Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 5, including a processor 510, a transceiver 520, and a machine-readable storage medium 530, where the machine-readable storage medium 530 stores machine-executable instructions capable of being executed by the processor 510, and the processor 510 is caused by the machine-executable instructions to perform the network interworking method provided by the embodiment of the present application. The network interworking apparatus shown in fig. 4 can be implemented by using a hardware structure of a network device shown in fig. 5.

The computer-readable storage medium 530 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Optionally, the computer-readable storage medium 530 may also be at least one memory device located remotely from the processor 510.

The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In the embodiment of the present application, the processor 510, by reading the machine executable instructions stored in the machine readable storage medium 530, is caused by the machine executable instructions to implement the processor 510 itself and the call transceiver 520 to perform the network interworking method described in the foregoing embodiment of the present application.

In addition, the embodiment of the present application provides a machine-readable storage medium 530, where the machine-readable storage medium 530 stores machine executable instructions, and when the machine executable instructions are called and executed by the processor 510, the machine executable instructions cause the processor 510 itself and the calling transceiver 520 to execute the network interworking method described in the embodiment of the present application.

The specific details of the implementation process of the functions and actions of each unit in the above device are the implementation processes of the corresponding steps in the above method, and are not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

As for the embodiments of the network interworking apparatus and the machine-readable storage medium, the contents of the related methods are basically similar to the foregoing embodiments of the methods, so that the description is relatively simple, and reference may be made to the partial description of the embodiments of the methods for the related points.

The above description is only a preferred embodiment of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A network interworking method applied to a first network device, the first network device having deployed a first network service, the first network device having established a first tunnel with a second network device, the second network device having deployed a second network service, the method comprising:

2. The method of claim 1, wherein the first network device has established a second tunnel with a third network device, and wherein the third network device has deployed third network traffic, the method further comprising:

receiving a private network message sent by a virtual machine;

when the outlet interface for forwarding the private network message is determined to be the second tunnel, acquiring a second outlet identifier of the second tunnel;

the second outlet identifier is packaged on the outer layer of the private network message, and public network tunnel information is packaged on the outer layer of the second outlet identifier to obtain a second service message;

sending the second service packet to the third network device through the second tunnel;

the first network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, the third network service is any one of EVPN VPWS, EVPN VPLS and EVPN VXLAN, and the first network service is different from the third network service.

3. The method according to claim 2, wherein before the receiving the first service packet sent by the second network device through the first tunnel, the method further comprises:

sending a first EVPN route advertisement message to the second network device and the third network device, wherein the first EVPN route advertisement message comprises the first identifier, a first EVPN HUB mark corresponding to the first network service and the first egress identifier, so that the second network device or the third network device establishes an EVPN HUB service model matched with the first identifier locally in a determined manner, and after the local network service is not matched with the first EVPN HUB mark, the first network device is used as a starting point, the first network device is used as an end point, the first tunnel and the second tunnel are respectively established, and the first egress identifier and the first EVPN HUB mark are associated with the corresponding tunnels.

4. The method according to claim 3, wherein before the receiving the first service packet sent by the second network device through the first tunnel, the method further comprises:

receiving a second EVPN route advertisement message sent by the second network device, where the second EVPN route advertisement message includes a second identifier of an EVPN HUB service model that has been established locally by the second network device and a second EVPN HUB flag corresponding to the second network service;

if the second identifier is matched with the first identifier and the second EVPN HUB mark is not matched with the first EVPN HUB mark, establishing the first tunnel by taking the first network equipment as a starting point and the second network equipment as an end point;

alternatively, the first and second liquid crystal display panels may be,

before the receiving, through the first tunnel, the first service packet sent by the second network device, the method further includes:

receiving a third EVPN route advertisement message sent by the third network device, where the third EVPN route advertisement message includes a third identifier of an EVPN HUB service model that has been locally established by the third network device and a third EVPN HUB flag corresponding to the third network service;

and if the third identifier is matched with the first identifier and the third EVPN HUB mark is not matched with the first EVPN HUB mark, establishing the second tunnel by taking the first network equipment as a starting point and the third network equipment as an end point.

5. The method of claim 4, wherein the second EVPN route advertisement message further includes a third egress identifier;

after the establishing the first tunnel, the method further comprises:

associating the third egress identifier, the second EVPN HUB flag, with the first tunnel;

after the establishing the second tunnel, the method further comprises:

associating the second egress identifier, the third EVPN HUB flag, with the second tunnel.

6. A network interworking apparatus, applied to a first network device, wherein the first network device has deployed a first network service, the first network device has established a first tunnel with a second network device, and the second network device has deployed a second network service, the apparatus comprising:

a receiving unit, configured to receive, through the first tunnel, a first service packet sent by the second network device, where the first service packet includes a first egress identifier of the first tunnel;

a sending unit, configured to send the first service packet to the first network service if the first egress identifier belongs to a first identifier of an EVPN HUB service model established locally and the first egress identifier is associated with the first network service, so that the first network service forwards the first service packet according to a forwarding policy of its own service;

7. The apparatus of claim 6, wherein the first network device has established a second tunnel with a third network device, the third network device having deployed third network traffic;

the receiving unit is also used for receiving a private network message sent by the virtual machine;

the device further comprises: an obtaining unit, configured to obtain a second egress identifier of the second tunnel when it is determined that an egress interface for forwarding the private network packet is the second tunnel;

the processing unit is used for packaging the second outlet identifier on the outer layer of the private network message and packaging public network tunnel information on the outer layer of the second outlet identifier to obtain a second service message;

the sending unit is further configured to send the second service packet to the third network device through the second tunnel;

8. The apparatus according to claim 7, wherein the sending unit is further configured to send a first EVPN route advertisement packet to the second network device and the third network device, where the first EVPN route advertisement packet includes the first identifier, a first EVPN HUB flag corresponding to the first network traffic, and the first egress identifier, so that the second network device or the third network device, after determining that an EVPN HUB traffic model matching the first identifier has been locally established and that local network traffic does not match the first EVPN HUB flag, establishes the first tunnel and the second tunnel, respectively, with the first network device as a terminal, and associates the first egress identifier and the first EVPN HUB flag with corresponding tunnels.

9. The apparatus according to claim 8, wherein the receiving unit is further configured to receive a second EVPN route advertisement message sent by the second network device, where the second EVPN route advertisement message includes a second identifier of an EVPN HUB service model that has been established locally by the second network device and a second EVPN HUB flag corresponding to the second network service;

the device further comprises: a building unit, configured to build the first tunnel with the first network device as a starting point and the second network device as an ending point if the second identifier matches the first identifier and the second EVPN HUB flag does not match the first EVPN HUB flag;

alternatively, the first and second liquid crystal display panels may be,

the receiving unit is further configured to receive a third EVPN route advertisement packet sent by the third network device, where the third EVPN route advertisement packet includes a third identifier of an EVPN HUB service model locally established by the third network device and a third EVPN HUB flag corresponding to the third network service;

the device further comprises: and the establishing unit is used for establishing the second tunnel by taking the first network equipment as a starting point and the third network equipment as an end point if the third identifier is matched with the first identifier and the third EVPN HUB mark is not matched with the first EVPN HUB mark.

10. The apparatus of claim 9, wherein the second EVPN route advertisement message further comprises a third egress identifier;

the device further comprises: an associating unit, configured to associate the third egress identifier and the second EVPN HUB flag with the first tunnel;

the associating unit is further configured to associate the second egress identifier and the third EVPN HUB flag with the second tunnel.