CN109936503B - Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance - Google Patents
Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance Download PDFInfo
- Publication number
- CN109936503B CN109936503B CN201711353986.0A CN201711353986A CN109936503B CN 109936503 B CN109936503 B CN 109936503B CN 201711353986 A CN201711353986 A CN 201711353986A CN 109936503 B CN109936503 B CN 109936503B
- Authority
- CN
- China
- Prior art keywords
- vpws
- devices
- identifier
- peer
- instance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure provides a mesh VPWS system based on EVPN and a method and equipment for establishing a mesh VPWS instance based on EVPN. The VPWS system includes: a plurality of CE devices; a plurality of PE devices for interconnecting the plurality of CE devices to form a mesh or partially mesh VPWS instance, the VPWS instance having a globally unique VPWS ID, and each of the plurality of CE devices having a unique identifier in the VPWS instance, wherein each of the PE devices participating in the VPWS instance assigns a corresponding MPLS traffic label to a CE device that is downstream of other peer PE devices in the VPWS instance by distributing EVPN VPWS routing messages.
Description
Technical Field
The present disclosure relates to the field of wired communication, and more particularly, to a Virtual Private Wire Service (VPWS) system based on Ethernet Virtual Private Network (EVPN) mesh (including full mesh and partial mesh), and a method and device for establishing a mesh VPWS instance based on EVPN.
Background
Rfc (request For comments)8214 describes a method For establishing a point-to-point VPWS (EVPN-VPWS) service based on EVPN, which can support two access link redundancy modes, i.e., single-active redundancy and flow-based load balancing on all access links (i.e., all-active redundancy).
Disclosure of Invention
The above EVPN-VPWS scheme described in RFC 8214 requires that each pair of Customer Edge (CE) devices be assigned a globally unique VPWS service instance identifier (abbreviated as VPWS identifier or VPWS ID). From the VPWS service operation point of view, it has the following disadvantages:
(1) compared with the conventional VPWS based on the L2VPN (Layer 2Virtual Private Area Network) specified in RFC 6074 or RFC 6624, the VPWS service connecting a plurality of customer sites (more than three) needs to allocate a plurality of VPWS IDs;
(2) when a new CE site is to be added to an existing fully meshed VPWS instance, not only the configuration of the Provider Edge (PE) devices to which the new CE site is directly connected is updated, but also all PE devices participating in the VPWS instance need to update the additional VPWS ID associated with the new CE site to their configuration.
In view of at least one of the above problems, the present disclosure suggests a mesh VPWS system and a method and apparatus for establishing a mesh VPWS instance, which provides a mesh VPWS service based on EVPN. The mesh VPWS service proposed by the present disclosure can support not only simplified VPWS service configuration model comparable to the traditional L2 VPN-based VPWS service configuration model, but also two access link redundancy modes of main/standby link redundancy and load balancing on all access links based on flow.
According to a first aspect of the present disclosure, there is provided an EVPN-based mesh VPWS system. The VPWS system includes: a plurality of CE devices; a plurality of PE devices for interconnecting the plurality of CE devices to form a mesh or partially mesh VPWS instance, the VPWS instance having a globally unique VPWS ID, and each of the plurality of CE devices having a unique identifier in the VPWS instance, wherein each of the PE devices participating in the VPWS instance assigns a corresponding MPLS traffic label to a CE device that is downstream of other peer PE devices in the VPWS instance by distributing EVPN VPWS routing messages.
According to a second aspect of the present disclosure, a method of establishing a mesh VPWS instance based on EVPN is provided. The method comprises the following steps: at one PE device, issuing a first VPWS message to a plurality of PE devices different from the PE device, the plurality of PE devices interconnecting the plurality of CE devices, the first VPWS message containing an identifier of a CE device that the PE device downlinks but not an identifier of a CE device that a plurality of peer PE devices of the PE device downlinks, and the first VPWS message containing a same VPWS ID as the plurality of PE devices; receiving a second VPWS message from a peer PE device of the PE devices, where the second VPWS message includes an identifier of a CE device to which the peer PE device is connected and MPLS service labels that the peer PE device allocates to the CE devices to which the PE device is connected; and respectively allocating MPLS service labels to the CE devices that the PE device at the peer is connected to in the downlink and transmitting a third VPWS message to the PE device at the peer, where the third VPWS message includes an identifier of the CE device that the PE device is connected to in the downlink and an MPLS service label allocated to the CE device that the PE device is connected to in the downlink.
According to a third aspect of the present disclosure, there is provided a method of establishing a mesh VPWS instance based on EVPN, the VPWS instance comprising a plurality of CE devices and a plurality of PE devices interconnecting the plurality of CE devices. The method comprises the following steps: allocating a common VPWS ID for all PE devices related to the VPWS instance; configuring an identifier of a subordinate CE device for each PE, wherein if the subordinate CE device of the PE device is a first subordinate connected CE device of the subordinate PE device, the identifier of the first subordinate connected CE device is configured as a system IP address of the PE device by default, if the subordinate CE device of the PE device is a non-first subordinate connected CE device of the subordinate PE device, the identifier of the non-first subordinate connected CE device is configured as a VF ID which is not repeated and is specific to the CE device, and if the subordinate CE device of the PE device is a multi-subordinate connected CE device, the identifier of the multi-subordinate connected CE device is configured as an ESI; and transmitting, by each PE device, an EVPN VPWS routing message to a peer PE device of the PE device to establish the VPWS instance, wherein the EVPN VPWS routing message includes an identifier of the CE device that the PE device is downlinked and a list of MPLS service labels that the PE device allocates to the CE device that each peer PE device is downlinked.
According to a fourth aspect of the present disclosure, there is provided an apparatus for establishing a mesh VPWS instance based on EVPN, the apparatus acting as a PE device. The apparatus comprises: a processor configured to: issuing a first VPWS message to a plurality of PE devices different from the PE device, the plurality of PE devices interconnecting the plurality of CE devices, the first VPWS message including an identifier of a CE device that the PE device is downlinked and not including identifiers of CE devices that a plurality of peer PE devices of the PE device are downlinked, and the first VPWS message including a same VPWS ID as the plurality of PE devices; receiving a second VPWS message from a peer PE device of the PE devices, where the second VPWS message includes an identifier of a CE device to which the peer PE device is connected and MPLS service labels that the peer PE device allocates to the CE devices to which the PE device is connected; and respectively allocating MPLS service labels to the CE devices that the peer PE device is connected to, and sending a third VPWS message to the peer PE device, where the third VPWS message includes an identifier of the CE device that the PE device is connected to, and an MPLS service label allocated to the CE device that the PE device is connected to.
According to a fifth aspect of the present disclosure, there is provided an apparatus for establishing a mesh VPWS instance based on EVPN, the VPWS instance comprising a plurality of CE devices and a plurality of PE devices interconnecting the plurality of CE devices. The apparatus comprises: a processor configured to: allocating a common VPWS ID for all PE devices related to the VPWS instance; and configuring an identifier of a CE device which is connected with each PE device in a downlink for each PE, wherein if the CE device which is connected with the PE device in the downlink is a first single-homed CE device which is connected with the PE device in the downlink, the identifier of the first single-homed CE device is configured as a system IP address of the PE device by default, if the CE device which is connected with the PE device in the downlink is a non-first single-homed CE device which is connected with the PE device in the downlink, the identifier of the non-first single-homed CE device is configured as a VF ID which is not repeated and is specific to the CE device, and if the CE device which is connected with the PE device in the downlink is a multi-homed CE device, the identifier of the multi-homed CE device is configured as an ESI, wherein each PE device sends an EVPN VPWS routing message to a peer PE device of the PE device to establish the VPWS instance, wherein the EVPN VPWS routing message comprises the identifier of the CE device which is connected with the PE device in the downlink and a business label which is allocated to the MPLS PE device in the peer device in the PE device in the downlink A list of tags.
Drawings
The disclosure will be better understood and other objects, details, features and advantages thereof will become more apparent from the following description of specific embodiments of the disclosure given with reference to the accompanying drawings in which:
fig. 1 shows a schematic diagram of an EVPN-based VPWS system according to the present disclosure;
FIG. 2 illustrates a schematic diagram of one embodiment of an EVPN VPWS message in accordance with the present disclosure;
fig. 3 shows a schematic diagram of a process for MPLS traffic label allocation in a fully active access link redundancy mode according to the present disclosure; and
fig. 4 illustrates a block diagram of a device suitable for implementing embodiments of the present disclosure.
Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a schematic diagram of an EVPN-based VPWS system 100 according to the present disclosure. As shown in FIG. 1, VPWS system 100 includes a plurality (two or more) of CE devices 1101、1102And 1103(collectively referred to as CE devices 110 or CE 110) and a plurality of PE devices 1201、1202、1203、1204And 1205(collectively referred to as PE devices 120 or PEs 120). Unlike conventional VPWS instances that assign a separate VPWS ID for each pair of CEs, in the VPWS system 100 shown in fig. 1, multiple PEs 120 interconnect the multiple CEs 110 to form a meshed (including fully-meshed and partially-meshed) VPWS instance having a globally unique VPWS ID. The VPWS system 100 shown in fig. 1 is based on EVPN, and the following description describes the VPWS system 100 as being based on EVPN, but those skilled in the art will appreciate that the present disclosure is not limited thereto, and can be applied to other support for constructing a mesh VPWS instanceUnderlying network or system. Further, three CEs 110 and five PEs 120 are shown in fig. 1, but those skilled in the art will appreciate that the present disclosure is not limited thereto, and may be readily applied to the case of other numbers of CEs 110 and other numbers of PEs 120.
In FIG. 1, CE 1101Via PE1202And 1203Multi-homed to the VPWS instance, and CE 1102Via PE1204And 1205Multiple homes are connected to the VPWS instance. CE 1103Only with PE1201Connected, called single homed connection.
To implement a meshed VPWS instance, each CE device 110 should be configured with an identifier unique in the VPWS instance in addition to the common unique VPWS ID, and each PE120 participating in the VPWS instance assigns a corresponding MPLS traffic label to the CE device whose peer PE is down-linked.
The VPWS instance has one (or more) VPWS Forwarder (VF) instances on each PE, each VF instance corresponding to a set of access links (ACs) connecting one CE to the VPWS instance. Thus, there are different implementations of the identifiers of CEs that each PE downlinks depending on whether the CE connected to it is a single-homed connection or a multi-homed connection. In one implementation, for a PE120 (e.g., PE 120)1) Single homed connected CE 1103The CE 1103The corresponding Ethernet Segment Identifier (ESI) is 0, and thus is in PE1201Uses the corresponding VF identifier (VF ID) as the CE 1103An identifier in the VPWS instance. For multiple PEs 120 (e.g., PE 120)3And PE1202) Multi-homed connected CEs (e.g., CE 110)1) At the plurality of PEs 120 (e.g., PE 120)3And PE1202) Wherein the same ESI (e.g., ESI1) is used as the multi-homed CE (e.g., CE 110)1) Identifiers in the VPWS instance, and the multi-homed connected CEs (e.g., CE 110)1) The corresponding VF ID is set to 0. In other words, in the VPWS control plane, a single-homed CE is represented by a non-zero VF ID (its associated ESI is 0), and a multi-homed CE is represented by a non-zero ESI (its associated VF ID is 0)。
Note that: VF in this disclosure is equivalent to a pool in RFC 6074 or VPWS edge in RFC 6624.
The process of establishing a mesh VPWS instance is described below in conjunction with fig. 1.
As described above, each PE in a VPWS instance should know the common unique VPWS ID, the identifier of the CE it downlinks, and the identifier of the CE it downlinks to a peer PE in the VPWS instance, so as to be able to assign and receive from the peer PE an MPLS traffic label assigned by the peer PE for the CE it downlinks. Accordingly, in order to establish a VPWS instance, each involved PE needs to distribute the corresponding information to the other PEs involved in the VPWS instance. These configurations of the PEs may be achieved through automatic discovery or manual configuration.
For an implementation of auto-discovery, consider the case where a new PE joins a VPWS instance. First, the new PE issues a first VPWS message to existing PEs constituting a VPWS instance, the first VPWS message including an identifier of a CE that the new PE downlinks but not including an identifier of a CE device that a peer PE of the new PE downlinks (and thus not including an MPLS service label that the new PE allocates for CEs that other PEs downlinks), and the first VPWS message including the same VPWS ID as the existing PEs.
All other PEs participating in the VPWS instance (i.e., peer PEs of the new PE) allocate MPLS traffic labels to the downstream CEs of the new PE in response to receiving the first VPWS message, and send a second VPWS message to the new PE. The second VPWS message sent by each peer PE includes the identifier of the CE that the peer PE has downlinked and the MPLS service label that the peer PE has allocated for the CE that the new PE has downlinked.
In response to receiving the second VPWS message, the new PE allocates MPLS traffic labels to the downstream CEs of each peer PE and sends a third VPWS message to the peer PEs. The third VPWS message contains an identifier of the CE that the new PE downlinked and a list of MPLS service labels that the new PE allocated for the CE that each peer PE downlinked.
For a manual configuration implementation, each PE in the VPWS instance is first configured with a common VPWS ID, and each PE is configured with an identifier of its downstream CE and identifiers of its downstream CEs of all its peer PEs. The VPWS ID is the same for each PE participating in the VPWS instance, and the identifiers of all CEs are non-zero values that are unique with respect to the VPWS instance. If a CE that a PE downlinks is the first singly-connected CE that the PE downlinks, the identifier of that CE is configured by default as the system IP address of that PE. On the other hand, if a CE that a PE downlinks is a non-first single-homed connected CE that the PE downlinks, the identifier of that CE is configured as the other non-duplicate VF ID (i.e., the VF ID specific to that CE). Alternatively, if the CE that the PE downlinks is a multi-homed CE, the identifier of the CE is configured as the ESI.
After each PE is manually configured with the VPWS ID, the identifier of its downstream CE, and the identifiers of its all peer PEs downstream CEs, each PE need only send an EVPN VPWS routing message to its peer PE to establish the VPWS instance. Wherein the EVPN VPWS routing message includes an identifier of the CE that the PE has downlinked and a list of MPLS traffic labels that the PE has assigned to the CE that each of its peer PEs has downlinked. That is, only one EVPN VPWS routing message needs to be sent in the manually configured implementation, which is similar to the third VPWS message in the auto-discovery implementation.
Also, depending on whether the CE connected to each PE is a single-homed connection or a multi-homed connection, there are different implementations of the identifier of the CE that each PE downlinks. In one implementation, for a PE120 (e.g., PE 120)1) Single homed connected CE 1103The CE 1103The corresponding Ethernet Segment Identifier (ESI) is 0, and thus is in PE1201Uses the corresponding VF identifier (VF ID) as the CE 1103An identifier in the VPWS instance. For multiple PEs 120 (e.g., PE 120)3And PE1202) Multi-homed connected CEs (e.g., CE 110)1) At the plurality of PEs 120 (e.g., PE 120)3And PE1202) Wherein the same ESI (e.g., ESI1) is used as the multi-homed CE (e.g., CE 110)1) Identifiers in the VPWS instance, and the multi-homed connected CEs (e.g., CE 110)1) Correspond toIs set to 0.
According to one implementation of the present invention, at least one of the first VPWS message, the second VPWS message, and the third VPWS message in the above automatic discovery implementation or the VPWS message in the above manual configuration implementation may be an EVPN VPWS Network Layer Reachability Information (NLRI) message (also referred to as an EVPN VPWS route) dedicated to automatic discovery and signaling.
A standard EVPN NLRI is defined in the standard EVPN "Route Type/Length/Route Type specific" section as specified in section 7 of RFC 7432. The VPWS message of the present disclosure conforms to the standard EVPN NLRI format, but needs to assign a new routing Type code (Type _ EVPN _ VPWS) to be dedicated to the automatic discovery and signaling of the EVPN VPWS. Note: the routing type code may be distributed publicly in the EVPN routing type registry by the Internet Assigned Numbers Authority (IANA) or configured locally on all involved PEs as a vendor proprietary function.
Fig. 2 shows a schematic diagram of one embodiment of an EVPN VPWS message 200 according to the present disclosure. Here VPWS message 200 conforms to the standard EVPN NLRI format. As shown in fig. 2, VPWS message 200 may include the following fields:
routing type field 210: this field must contain the routing TYPE code (TYPE _ EVPN _ VPWS) assigned to the VPWS message 200. The field length is 1 byte.
Length field 220: this field indicates that the VPWS message 200 does not include a length other than the routing type field 210 and the length field 220 in bytes. The field length is 1 byte.
Route Distinguisher (RD) field 230: RD is a globally unique 8-byte value assigned to one EVPN instance (EVI) at each PE's local entity. Reference is made to RFC 4364 for a standard encoding format for RD.
ESI field 240: this field contains an identifier of the set of ethernet links connecting the multi-homed connection CE to a set of redundant PEs. The present disclosure requires that the ESI value must be unique with respect to the VPWS ID. The ESI associated with a single homed connection CE is 0. The standard ESI encoding format is 10 bytes in length. Reference is made to RFC 7432, section 5, for standard encoding formats for ESI.
Ethernet Tag (Ethernet Tag) ID field 250: this field contains the VPWS ID. All PEs participating in the same VPWS instance must issue the same VPWS ID value. This field may be 32 bits, for example. If a 24-bit value, such as a Virtual Extensible local area Network (VXLAN) Network Identifier (VNI), is used as the VPWS ID, it is included in the 24 least significant bits of the field, and the 8 most significant bits that are not used are set to 0.
VF ID length field 260: this field indicates the length of the following VF ID field in bytes. This field may be, for example, 1 byte. Depending on the system IP address format of the PE (4 bytes of IPv4 or 16 bytes of IPv6), its value is 4 or 16.
VF ID field 270: the length of this field is 4 or 16 bytes as indicated by the VF ID length field. This field contains the VF ID for which the PE issued the auto-discovery and signaling messages. If the VF is associated with a single generic connection CE, then the VF ID must be a unique non-zero value with respect to the VPWS ID. The VF ID is 0 if the VF is associated with a multi-homed connection CE. For convenience, the VF ID of each EVI at each PE's first VPWS forwarder is automatically set to the PE system IP address.
Assigned MPLS traffic label field 280: the variable length field is optional. If this field does not exist, this VPWS message 200 is only used for auto-discovery, such as the first VPWS message in the auto-discovery implementation described above; if this field exists, the VPWS message 200 is used for auto-discovery and traffic label signaling, such as the second and third VPWS messages in the auto-discovery implementation described above and the EVPN VPWS routing message in the manual configuration implementation described above.
If present, field 280 contains a list of MPLS traffic label assignments. Each MPLS traffic label assignment contains three subfields: a peer ID type subfield 282, a peer ID value subfield 284, and an MPLS traffic label subfield 286 indicate that a particular MPLS traffic label 286 is assigned to a particular peer identified by a peer ID type 282-value 284 tuple, such as a downstream CE of peer PE1, … …, peer PE, etc. Here, the length of the peer ID value subfield 282 is implicitly determined by the peer ID type subfield 284, as shown in table 1 below.
TABLE 1 Peer ID type-value tuple
| Peer ID type | Peer ID value |
| 1 | 4-byte VF ID value associated with a single-homed connection CE |
| 2 | 10 byte ESI values associated with multi-homed connected CEs |
| 3 | 16-byte VF ID value associated with a single-homed CE |
Note 1: all peer IDs in table 1 must belong to the same VPWS instance as the VF ID or ESI for which the PE issued the auto-discovery and signaling messages.
Note 2: when a PE issues this VPWS message 200 for a multi-homed CE site, i.e., the ESI field 240 contains a non-zero value and the VF ID field 270 contains a 0, the same ESI value may appear in the ESI field 240 and the assigned MPLS traffic label field 280 (more specifically in the peer ID value subfield 284). In this way, the signaling message issuing PE may assign traffic labels to other PEs of the multi-homed connected redundancy group so that they can install backup routes for fast reroute, thereby enabling traffic flow to the CE to be temporarily switched fast to the signaling message issuing PE in the event of a PE-CE link failure.
Those skilled in the art will understand that the format of the VPWS message 200 is not limited thereto, and may be other reused messages or newly defined messages as long as the message can support a PE to issue the local ID of the PE downlink CE to other PEs in the VPWS instance and the PE to allocate the MPLS service label to the CE downlink by other PEs.
In addition, in the routing process of the Border Gateway Protocol (BGP), only the ESI field 240, the ethernet label ID field 250, the VF ID length field 260, and the VF ID field 270 in the VPWS message 200 are regarded as a part of the route, and the MPLS service label field 280 is regarded as a routing attribute, not a part of the route.
When the EVI is used to carry VPWS traffic, it is no longer used to carry any other type of EVPN-based L2/L3 (layer 2/3) traffic. For EVI carrying VPWS traffic only, the PE only issues and receives EVPN route type 1 (as described in RFC 8214) and the new EVPN route type defined in this disclosure, dedicated to auto-discovery and signaling. An EVI carrying only VPWS traffic may contain one or more VPWS instances, each identified by a different 32-bit VPWS identifier (VPWS ID).
The EVPN layer 2 attribute extended community attribute is used to control L2MTU (Maximum Transmission Unit), control words, and multi-homed connections, and its use in this disclosure is the same as that specified in section 3.1 of RFC 8214. Reference may be made to RFC 8214, section 3.1 for more details.
The route target extended community attribute is used to control the topology of the established VPWS instance. Reference may be made to RFC 4363, section 4.3.1 for more details.
Fig. 3 shows a schematic diagram of the process of MPLS traffic label assignment 300 in a fully active access link redundancy mode (load balancing across all access links based on flow) according to the present disclosure.
PE 1203VPWS messages are issued to assign the service tag Label1 from ESI1 to ESI 2. After receiving the VPWS message, PE1201And PE1202It is known that ESI2 can be used via a next hop PE120 using Label13To arrive. Similarly, PE1201And PE1202It is known that ESI2 can also be used to pass through next hop PE120 using Label24To arrive. When CE 110 is in use1To CE 1102When sending packets, the flow-based load balancing is performed on both access links (the set of ethernet access links is identified as ESI1), one for each PE1201And PE1202The packet is transmitted. At PE1201In this regard, the destination ESI2 can be routed via two routes<PE 1203,Label1>And<PE 1204,Label2>arrive, therefore, PE1201Traffic to the ESI2 will be carried equally through both routes. Similarly, PE1202Traffic to the ESI2 is also carried equally over the other two routes. At PE1203And PE1204From PE1201And PE1202Traffic (with the same next hop and traffic label) is forwarded indifferently to ESI 2. Slave CE 1102To CE 1101The same applies to the reverse forwarding of (1).
The fast convergence mechanism employed by the present disclosure is based on standard ethernet segment ethernet auto discovery NLRI, the same as that described in RFC 8214, section 6.2.
Fig. 4 illustrates a block diagram of a device 400 suitable for implementing embodiments of the present disclosure. Device 400 may be used to implement PE120 in both an auto discovery implementation and a manual configuration implementation.
As shown in fig. 4, the device 400 includes a processor 410. Processor 410 controls the operation and functions of device 400. For example, in some embodiments, processor 410 may perform various operations by way of instructions 430 stored in memory 420 coupled thereto. The memory 420 may be of any suitable type suitable to the local technical environment and may be implemented using any suitable data storage technology, including but not limited to semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems. Although only one memory unit is shown in FIG. 4, there may be multiple physically distinct memory units in device 400.
The processor 410 may be of any suitable type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microcontrollers, digital signal controllers (DSPs), and controller-based multi-core controller architectures, but is not limited to. The device 400 may also include a plurality of processors 410. The processor 410 is coupled to a transceiver 440, and the transceiver 440 may enable the reception and transmission of information over a wired or wireless medium.
When device 400 is used to implement PE120 in an auto-discovery implementation or a manual configuration implementation, processor 410, transceiver 440, and/or other components may be configured (e.g., by instructions 430 in memory 420) to implement the functionality of PE120 described above with reference to fig. 1-3. All of the features described above with reference to fig. 1-3 apply to the apparatus 400 and are not described in detail herein.
In summary, the mesh VPWS system and the method for establishing the mesh VPWS instance proposed by the present disclosure can support both a primary/standby link redundancy (i.e., single-active redundancy) and an all-active redundancy mode for load balancing on all access links based on flows. Compared with the EVPN-VPWS service provision specified in the existing RFC 8214, the proposed method requires much fewer configuration parameters when deploying multi-site (three or more customer sites) VPWS services.
More than multi-site VPWS services, the EVPN-VPWS service provisioning method described in RFC 8214 requires a considerable amount of manual configuration, which requires the assignment of a separate VPWS ID for each different pair of CE sites. When a new CE site joins an existing VPWS service, all PEs participating in the VPWS service need to manually update their configuration. The new EVPN-VPWS service providing method of the present disclosure solves these problems, and each VPWS instance only needs to be assigned one VPWS ID; when a new CE site joins an existing VPWS instance, only the PE that the CE is directly up-linked to needs to manually update its configuration.
In one or more exemplary designs, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. For example, if implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
The units of the apparatus disclosed herein may be implemented using discrete hardware components, or may be integrally implemented on a single hardware component, such as a processor. For example, the various illustrative logical blocks, modules, and circuits described in connection with the disclosure may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (15)
1. A mesh virtual private service (VPWS) system based on Ethernet Virtual Private Network (EVPN), comprising:
a plurality of Customer Edge (CE) devices;
a plurality of operator edge (PE) devices to interconnect the plurality of CE devices to form one fully or partially meshed VPWS instance, the VPWS instance having a globally unique VPWS identifier (VPWS ID) and each of the plurality of CE devices having a unique identifier in the VPWS instance,
wherein each PE device participating in the VPWS instance of the plurality of PE devices allocates a corresponding multi-protocol label switching (MPLS) service label to a CE device that is downlinked by another peer PE device in the VPWS instance by distributing an EVPN VPWS routing message.
2. The meshed VPWS system according to claim 1, wherein a first one of the plurality of CE devices is only single homed with one of the plurality of PE devices, a VPWS forwarder identifier (VF ID) is used in the first PE device as an identifier of the first CE device, and an Ethernet Segment Identifier (ESI) of the first CE device is set to 0.
3. The meshed VPWS system of claim 2 wherein a second one of the plurality of CE devices is multi-homed with a plurality of second one of the plurality of PE devices, the same ESI being used in the plurality of second PE devices as an identifier of the second CE device, and the VF ID of the second CE device is set to 0.
4. The meshed VPWS system according to claim 2 or 3 wherein the VPWS ID is 32 bits long.
5. The meshed VPWS system of claim 4, wherein the 24 least significant bits of the VPWS ID comprise a virtual extensible local area network identifier (VNI) and the 8 most significant bits of the VPWS ID are set to 0.
6. A method of establishing a mesh Virtual Private Wire Service (VPWS) instance based on an Ethernet Virtual Private Network (EVPN), comprising:
at one operator edge (PE) device,
issuing a first VPWS message to a plurality of PE devices different from the PE device, the plurality of PE devices interconnecting a plurality of Customer Edge (CE) devices to form one fully-meshed or partially-meshed VPWS instance, the first VPWS message including identifiers of CE devices that the PE device downlinks but not identifiers of CE devices that a plurality of peer PE devices of the PE device downlinks, and the first VPWS message including a same VPWS identifier (VPWS ID) as the plurality of PE devices;
receiving a second VPWS message from a peer PE device of the plurality of PE devices, the second VPWS message including an identifier of a CE device to which the peer PE device is connected and multi-protocol label switching (MPLS) service labels respectively allocated by the peer PE device to the CE device to which the PE device is connected; and
respectively allocating MPLS service labels to the CE devices of the peer PE device downlink and sending a third VPWS message to the peer PE device, where the third VPWS message includes an identifier of the CE device of the PE device downlink and the MPLS service label allocated by the PE device to the CE device of the peer PE device downlink.
7. The method of claim 6, wherein a first one of the plurality of CE devices is only single-homed with one of the plurality of PE devices, a VPWS forwarder identifier (VF ID) is used in the first PE device as an identifier of the first CE device, and an Ethernet Segment Identifier (ESI) of the first CE device is set to 0.
8. The method of claim 7, wherein a second CE device of the plurality of CE devices is multi-homed with a plurality of second PE devices of the plurality of PE devices, a same ESI is used in the plurality of second PE devices as an identifier of the second CE device, and a VF ID of the second CE device is set to 0.
9. The method of claim 7 or 8, wherein at least one of the first VPWS message, the second VPWS message, and the third VPWS message is an EVPN VPWS routing message dedicated for auto discovery,
the first VPWS message includes an Ethernet tag ID field to indicate the VPWSID; and a VFID field and an ESI field for identifying CE devices for single-homed and multi-homed connections, respectively,
the second VPWS message comprises an ethernet tag ID field to indicate the VPWSID; a VFID field and an ESI field, which are respectively used for identifying the CE equipment with single-homing connection and multi-homing connection; and an allocated MPLS traffic label field for indicating an MPLS traffic label allocated by the peer PE device for a CE device that the PE device is subordinate to,
the third VPWS message comprises an ethernet tag ID field to indicate the VPWSID; a VFID field and an ESI field, which are respectively used for identifying the CE equipment with single-homing connection and multi-homing connection; and the allocated MPLS service label field is used for indicating the MPLS service label allocated to the CE equipment which is connected with the peer PE equipment in a downlink manner by the PE equipment.
10. A method of establishing a mesh virtual private service (VPWS) instance based on an Ethernet Virtual Private Network (EVPN), the VPWS instance comprising a plurality of Customer Edge (CE) devices and a plurality of operator edge (PE) devices, the plurality of PE devices interconnecting the plurality of CE devices to form one fully or partially meshed VPWS instance, the method comprising:
allocating a common VPWS identifier (VPWS ID) to all PE devices involved in the VPWS instance;
configuring an identifier of a subordinate CE device for each PE, wherein if the subordinate CE device of the PE device is a first subordinate single-connection CE device of the subordinate PE device, the identifier of the first subordinate single-connection CE device is configured as a system IP address of the PE device by default, if the subordinate CE device of the PE device is a non-first subordinate single-connection CE device of the subordinate PE device, the identifier of the non-first subordinate single-connection CE device is configured as a VPWS forwarder identifier (VF ID) specific to the CE device, and if the subordinate CE device of the PE device is a multi-subordinate single-connection CE device, the identifier of the multi-subordinate single-connection CE device is configured as an Ethernet Segment Identifier (ESI);
transmitting, by each PE device, an EVPN VPWS routing message to a peer PE device of the PE devices to establish the VPWS instance, wherein the EVPN VPWS routing message includes an identifier of a CE device that the PE device is downlinked and a list of multiprotocol label switching (MPLS) traffic labels assigned by the PE device to the CE device that each peer PE device is downlinked.
11. The method of claim 10, wherein a first CE device of the plurality of CE devices is only single-homed with one of the plurality of PE devices, the first PE device using a VPWS forwarder identifier (VF ID) as an identifier of the first CE device, and an Ethernet Segment Identifier (ESI) of the first CE device is set to 0.
12. The method of claim 11, wherein a second CE device of the plurality of CE devices is multi-homed with a plurality of second PE devices of the plurality of PE devices, a same ESI is used in the plurality of second PE devices as an identifier of the second CE device, and a VF ID of the second CE device is set to 0.
13. The method of claim 10 or 11, wherein the VPWS message is an EVPN VPWS routing message dedicated to auto discovery and MPLS traffic label assignment,
the VPWS message includes an Ethernet tag ID field to indicate the VPWS ID; a VFID field and an ESI field, which are respectively used for identifying the CE equipment with single-homing connection and multi-homing connection; and an allocated MPLS service label field, configured to indicate that the PE device is an MPLS service label allocated to a CE device that is a peer PE device of the PE device and is connected downstream.
14. An apparatus for establishing a mesh virtual private service (VPWS) instance based on an Ethernet Virtual Private Network (EVPN), the apparatus acting as a carrier edge (PE) device, comprising:
a processor configured to:
issuing a first VPWS message to a plurality of PE devices different from the PE device, the plurality of PE devices interconnecting a plurality of Customer Edge (CE) devices to form one fully-meshed or partially-meshed VPWS instance, the first VPWS message including identifiers of CE devices that the PE device downlinks but not identifiers of CE devices that a plurality of peer PE devices of the PE device downlinks, and the first VPWS message including a same VPWS identifier (VPWS ID) as the plurality of PE devices;
receiving a second VPWS message from a peer PE device of the plurality of PE devices, the second VPWS message including an identifier of a CE device to which the peer PE device is connected and multi-protocol label switching (MPLS) service labels respectively allocated by the peer PE device to the CE device to which the PE device is connected; and
respectively allocating MPLS service labels to the CE devices of the peer PE device downlink and sending a third VPWS message to the peer PE device, where the third VPWS message includes an identifier of the CE device of the PE device downlink and the MPLS service label allocated to the CE device of the peer PE device downlink by the PE device.
15. An apparatus for establishing a mesh virtual private service (VPWS) instance based on an Ethernet Virtual Private Network (EVPN), the VPWS instance comprising a plurality of Customer Edge (CE) devices and a plurality of operator edge (PE) devices, the plurality of PE devices interconnecting the plurality of CE devices to form one fully or partially meshed VPWS instance, the apparatus comprising:
a processor configured to:
allocating a common VPWS identifier (VPWS ID) to all PE devices involved in the VPWS instance; and
configuring an identifier of a CE device which is connected with each PE device in a downlink for each PE, wherein if the CE device which is connected with the PE device in the downlink is a first single-homed CE device which is connected with the PE device in the downlink, the identifier of the first single-homed CE device is configured as a system IP address of the PE device by default, if the CE device which is connected with the PE device in the downlink is a non-first single-homed CE device which is connected with the PE device in the downlink, the identifier of the non-first single-homed CE device is configured as a VPWS Forwarder Identifier (VFID) specific to the CE device, if the CE device which is connected with the PE device in the downlink is a multi-homed CE device, the identifier of the multi-homed CE device is configured as an Ethernet Segment Identifier (ESI),
wherein an EVPN VPWS routing message is sent by each PE device to a peer PE device of the PE devices to establish the VPWS instance, wherein the EVPN VPWS routing message comprises an identifier of a CE device that the PE device is downlinked and a list of multiprotocol label switching (MPLS) service labels that the PE device assigns to the CE device that each peer PE device is downlinked.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711353986.0A CN109936503B (en) | 2017-12-15 | 2017-12-15 | Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711353986.0A CN109936503B (en) | 2017-12-15 | 2017-12-15 | Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109936503A CN109936503A (en) | 2019-06-25 |
| CN109936503B true CN109936503B (en) | 2021-04-23 |
Family
ID=66980629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711353986.0A Active CN109936503B (en) | 2017-12-15 | 2017-12-15 | Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109936503B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050213513A1 (en) * | 2004-03-25 | 2005-09-29 | Alcatel | Full mesh LSP and full mesh T-LDP provisioning between provider edge routers in support of Layer-2 and Layer-3 Virtual Private Network services |
| US20070133564A1 (en) * | 2005-12-09 | 2007-06-14 | Chun Kyung G | Method for propagating maintenance signal in VPWS network using SDH/SONET |
| CN102413060A (en) * | 2011-12-31 | 2012-04-11 | 杭州华三通信技术有限公司 | User private line communication method and equipment used in VPLS (Virtual Private LAN (Local Area Network) Service) network |
| CN102857400A (en) * | 2012-09-14 | 2013-01-02 | 中兴通讯股份有限公司 | Method and device for establishing broadcasting domain in two-layer virtual dedicated network |
| CN103209125A (en) * | 2013-04-07 | 2013-07-17 | 杭州华三通信技术有限公司 | Label information transmission method and device |
-
2017
- 2017-12-15 CN CN201711353986.0A patent/CN109936503B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050213513A1 (en) * | 2004-03-25 | 2005-09-29 | Alcatel | Full mesh LSP and full mesh T-LDP provisioning between provider edge routers in support of Layer-2 and Layer-3 Virtual Private Network services |
| US20070133564A1 (en) * | 2005-12-09 | 2007-06-14 | Chun Kyung G | Method for propagating maintenance signal in VPWS network using SDH/SONET |
| CN102413060A (en) * | 2011-12-31 | 2012-04-11 | 杭州华三通信技术有限公司 | User private line communication method and equipment used in VPLS (Virtual Private LAN (Local Area Network) Service) network |
| CN102857400A (en) * | 2012-09-14 | 2013-01-02 | 中兴通讯股份有限公司 | Method and device for establishing broadcasting domain in two-layer virtual dedicated network |
| CN103209125A (en) * | 2013-04-07 | 2013-07-17 | 杭州华三通信技术有限公司 | Label information transmission method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109936503A (en) | 2019-06-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108989213B (en) | Transmitting LSP settings using selected fabric paths between virtual nodes | |
| CN108989202B (en) | Fabric path context based forwarding for virtual nodes | |
| CN108574630B (en) | EVPN message processing method, device and system | |
| US9992154B2 (en) | Layer 3 convergence for EVPN link failure | |
| CN107078966B (en) | Method and apparatus for assigning receiver identifiers and automatically determining tree attributes | |
| US8467411B1 (en) | Service-specific forwarding in an LDP-RSVP hybrid network | |
| CN1822570B (en) | The automatic discovering method of the pseudo-circuit peer address carried out in based on the network of Ethernet | |
| CN106656781B (en) | Method, device and system for transmitting message | |
| CN105450437B (en) | SID distribution method and SR node | |
| US20170373973A1 (en) | Signaling ip address mobility in ethernet virtual private networks | |
| EP3249865A1 (en) | Method and apparatus for forwarding label construction and label packet | |
| EP3846409A1 (en) | Offset label for aggregating multicasts from multiple virtual private networks on a single multicast distribution tree | |
| US20180309596A1 (en) | Evpn implicit aliasing | |
| JP6008801B2 (en) | Transmission system, transmission method, and transmission apparatus | |
| JP6030649B2 (en) | Label switch path (LSP) tunneling model signaling | |
| US8891536B2 (en) | Layer-3 services for united router farm | |
| EP3420687B1 (en) | Addressing for customer premises lan expansion | |
| CN106936714B (en) | VPN processing method, PE equipment and system | |
| US11362954B2 (en) | Tunneling inter-domain stateless internet protocol multicast packets | |
| US8988985B2 (en) | Internetworking and IP address management in unified MPLS and IP networks | |
| CN106921573A (en) | It is used to issue the method and device of tenant's route in NVo3 networks | |
| JP2013066135A (en) | Program for redundancy control, information processing device and method, communication apparatus, relay processing metho, and program | |
| US11750507B1 (en) | Assignment of segment identifiers in segment routing | |
| WO2015113456A1 (en) | Method for generating media access control table, and network device | |
| CN109936503B (en) | Mesh VPWS system based on EVPN and method and equipment for establishing mesh VPWS instance |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |