CN116170250A - Route advertising method, SPE, network equipment and storage medium - Google Patents

Route advertising method, SPE, network equipment and storage medium Download PDF

Info

Publication number
CN116170250A
CN116170250A CN202111409613.7A CN202111409613A CN116170250A CN 116170250 A CN116170250 A CN 116170250A CN 202111409613 A CN202111409613 A CN 202111409613A CN 116170250 A CN116170250 A CN 116170250A
Authority
CN
China
Prior art keywords
notification message
blocking
route
next hop
spe
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.)
Pending
Application number
CN202111409613.7A
Other languages
Chinese (zh)
Inventor
张耀坤
王海波
邵明嵩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Huawei Digital Technologies Co Ltd
Original Assignee
Beijing Huawei Digital Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Huawei Digital Technologies Co Ltd filed Critical Beijing Huawei Digital Technologies Co Ltd
Priority to CN202111409613.7A priority Critical patent/CN116170250A/en
Publication of CN116170250A publication Critical patent/CN116170250A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42Loop networks
    • H04L12/437Ring fault isolation or reconfiguration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0631Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0677Localisation of faults
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing

Abstract

The embodiment of the application discloses a route notification method, SPE, network equipment and storage medium, belonging to the technical field of communication. The method is executed by a service side operator edge device SPE in a layered Ethernet virtual private network H-EVPN networking. The method comprises the following steps: the SPE receives a first route notification message carrying a Media Access Control (MAC) address and a next hop. If the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message. The embodiment of the application can detect the MAC route jump in the H-EVPN networking so as to facilitate the subsequent loop detection.

Description

Route advertising method, SPE, network equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a route notification method, SPE (solid state imaging device), network equipment and storage medium.
Background
In a Hierarchical ethernet virtual-private network (H-EVPN) networking, a service-side operator edge device (service provider edge, SPE) establishes a neighbor relation with a user-side operator edge device (user-end provider edge, UPE) and a network-side operator edge device (network provider edge, NPE) as a central node to publish routes based on the neighbor relation.
In the related art, when a terminal device suspended at a UPE transmits traffic to the UPE, the UPE learns a source media access control (media access control, MAC) address of the traffic, encapsulates a MAC route based on the source MAC address, and transmits the MAC route to an SPE. The MAC route comprises the MAC address of the terminal equipment and the next hop, wherein the MAC address is the unique identifier of the terminal equipment, and the next hop is UPE. And the SPE receives the MAC route, modifies the next hop in the MAC route into the SPE, and continues to send the modified MAC route to other neighbor devices. In this way, the MAC address of the terminal device can be transferred between the respective devices.
However, in the above-mentioned transfer process, if a loop fault occurs on the UPE side, after learning the MAC route issued by the remote NPE based on the SPE, the UPE may return to the UPE after transmitting in the loop, so that the UPE repackages the MAC route based on the MAC route again, and then sends the repackaged MAC route to the SPE. The SPE as the central node still modifies the next hop in the MAC route to itself and then transfers the modified MAC route to the NPE again. The NPE receives the modified MAC route, discovers that the MAC address in the modified MAC route is the same as the MAC address in the MAC route released before the local current time, and at the moment, the NPE judges that the locally released MAC route is optimal and sends the local MAC route to the SPE again. The SPE modifies the received MAC route and then sends the modified MAC route to the UPE, and the UPE repeats the operation, so that the SPE, the NPE and the continuous jump of the MAC route on the UPE are caused, and waste of network resources is caused.
Disclosure of Invention
The application provides a route advertising method, SPE, network equipment and storage medium, which can solve the problem of continuous jump of MAC routes in the related technology. The technical scheme is as follows:
in a first aspect, a route advertisement method is provided, the method performed by an SPE in an H-EVPN networking. In the method, an SPE receives a first route announcement message, wherein the first route announcement message carries an MAC address and a next hop. If the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
In the application, after receiving the first route notification message, the SPE determines whether the MAC address in the first route notification message is the same as the MAC address in the route notification message received before the current time, and whether the next hop in the first route notification message is the same as the next hop in the route notification message received before the current time. If the MAC address of the second route notification message is the same as the MAC address of the first route notification message and the next hop in the second route notification message is different from the next hop in the first route notification message, the SPE determines that the MAC route jump occurs between the next hop in the second route notification message and the next hop in the first route notification message. That is, the SPE may detect that a MAC route jump occurs in the H-EVPN networking, so as to facilitate subsequent loop detection.
Optionally, after determining that a MAC route hop occurs between a next hop in the first route advertisement packet and a next hop in the second route advertisement packet, the SPE further determines the number of times that a MAC route hop occurs between the next hop in the first route advertisement packet and the next hop in the second route advertisement packet from the start of the detection period to the current time, to obtain the hop number. If the number of hops exceeds the reference number of hops, the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message are looped.
In the application, SPE determines whether loop fault occurs in H-EVPN networking through the number of times of MAC route jump between the next jump in the received first route notice message and the next jump in the second route notice message. If the number of times of MAC route hopping between the next hop in the first route advertisement message and the next hop in the second route advertisement message exceeds the reference hopping number, the SPE can determine that loop faults occur in the networking. Unlike UPE, which needs to learn the MAC address in locally received traffic and the MAC address of the route advertisement message sent by the far end to determine that a loop failure occurs.
Optionally, after determining that one of the next hop in the first route advertisement message or the next hop in the second route advertisement message is looped, the SPE further reports an alarm message, where the alarm message carries the next hop in the first route advertisement message and the next hop in the second route advertisement message, and the alarm message is looped for one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message.
In the application, the SPE can not only detect the loop fault in the H-EVPN networking, but also generate the alarm message under the condition of the loop fault and report the alarm message. The SPE can report the alarm message to the network controller, and the operation and maintenance personnel at the network controller can timely process the PE with loop faults, so that the effect of protecting the H-EVPN networking in real time is achieved.
Optionally, the SPE determines a blocking priority of a next hop in the first route advertisement message and a blocking priority of a next hop in the second route advertisement message. The SPE also determines the next hop in the first route advertisement message and the next hop with higher blocking priority in the next hop in the second route advertisement message, and obtains the blocking peer. And the SPE performs a blocking operation on the blocking peer.
In the application, after detecting that a loop occurs, the SPE determines a blocking peer according to the blocking priority among PEs, and performs blocking operation on the blocking peer. Therefore, the situation that the business message or the route notification message based on the blocking peer is repeatedly transmitted in the H-EVPN networking can not occur, and further the waste of network resources can not be caused.
Optionally, when receiving a service packet sent from a node other than the blocking peer, if the destination MAC address of the service packet is a MAC address learned from the blocking peer, no operation of forwarding the service packet to the blocking peer is performed.
When the blocking peer performs a blocking operation, traffic sent to the blocking peer is blocked at the forwarding layer.
Optionally, when receiving a service message from the blocking peer, no operation is performed to forward the service message to other nodes than the blocking peer.
The present application, when performing blocking operations on blocking peers, blocks traffic from the blocking peers at the forwarding layer.
Optionally, the marking information is added to the route advertisement message sent by the current time blocking peer, and the route advertisement message sent by the current time blocking peer is the first route advertisement message or the second route advertisement message. If the third route notification message sent by the blocking peer is received again and the route notification message marked by the third route notification message and the marking information is the same route notification message, the operation of issuing the route notification message based on the third route notification message is not executed.
When the SPE receives the route notification message sent from the blocking peer again, the SPE does not execute the operation of releasing the modified route notification message based on the route notification message.
Optionally, the H-EVPN further includes a UPE and an NPE, wherein the blocking priority of the UPE is higher than that of the NPE.
In the application, since the importance degree of the NPE is higher than that of the UPE, in order to achieve the effect of protecting the networking, the blocking priority can be set according to the importance degree of the PEs in the networking, and the higher the importance degree, the lower the corresponding blocking priority.
Alternatively, the blocking priorities may be different between different UPEs.
The method and the device are used for setting blocking priorities for different UPEs in the networking based on the importance degree of each UPE, so that when a blocking operation is executed in a scene where a plurality of UPEs exist, the UPE with the high priority is blocked preferentially.
Optionally, the blocking priorities are different between different NPEs.
According to the method and the system, blocking priorities are set for different NPEs in the networking based on the importance degrees of the NPEs, so that when the blocking operation is executed in a scene where a plurality of NPEs exist, the NPEs with high priorities are blocked preferentially.
Optionally, when performing the blocking operation on the blocking peer, counting from the current time, and before the counted time length reaches the blocking time length, performing the blocking operation on the blocking peer.
The blocking time length is set, so that operation and maintenance personnel can maintain networking within the blocking time length.
Optionally, before the timing duration reaches the blocking duration, if the SPE receives the blocking release instruction, the blocking operation is not performed on the blocking peer any more.
In this application, if the operation and maintenance personnel has already processed the PE with the loop failure when the timing duration has not reached the blocking duration, at this time, for example, the network controller may send a blocking release instruction to the SPE, where the blocking release instruction indicates that the failure in the networking has been processed, and the networking may continue to operate.
In a second aspect, an SPE in an H-EVPN networking is provided, where the SPE has a function of implementing the behavior of the route advertisement method in the first aspect. The SPE comprises at least one module for implementing the route advertisement method provided in the first aspect.
In a third aspect, a network device is provided, where the network device includes a processor and a memory, where the memory is configured to store a program for supporting the network device to perform the route advertisement method provided in the first aspect, and store data related to implementing the route advertisement method provided in the first aspect. The processor is configured to execute a program stored in the memory.
In a fourth aspect, there is provided a computer readable storage medium having instructions stored therein, which when run on a computer, cause the computer to perform the route advertisement method according to the first aspect described above.
In a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the route advertisement method of the first aspect described above.
The technical effects obtained in the second, third, fourth and fifth aspects are similar to the technical effects obtained in the corresponding technical means in the first aspect, and are not described in detail herein.
Drawings
FIG. 1 is a schematic diagram of a system architecture provided in an embodiment of the present application;
FIG. 2 is a schematic illustration of an SPE provided in an embodiment of the present application;
fig. 3 is a flowchart of a route advertisement method provided in an embodiment of the present application;
FIG. 4 is a schematic diagram of traffic delivery in a networking according to an embodiment of the present application;
fig. 5 is a flowchart of another route advertisement method provided in an embodiment of the present application;
fig. 6 is a flowchart of another route advertisement method provided in an embodiment of the present application;
fig. 7 is a flowchart of another route advertisement method provided in an embodiment of the present application;
FIG. 8 is a schematic diagram of the structure of an SPE provided in an embodiment of the present application;
fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Before explaining the route advertisement method provided by the embodiment of the application in detail, an application scenario and a system architecture provided by the embodiment of the application are introduced.
In Hierarchical virtual-Virtual Private LAN Service, H-VPLS networking, a signaling protocol is generally used to establish and maintain Pseudowires (PW) between Provider Edge (PE) nodes, so that protocol frames are encapsulated and transmitted and exchanged on the PW, so that a plurality of lans in a wide area are integrated into a network at a data link level, and virtual ethernet services are provided to users. That is, the different PEs in the H-VPLS network are based on established PW communications.
The PW is a virtual bidirectional connection between two PEs, that is, the PW is directional, and for any two PEs, the PW between the two PEs essentially refers to two unidirectional transmission PWs with opposite directions.
In the H-VPLS networking, each PE learns the MAC address based on Broadcast, unknown Unicast, and multicast traffic (BUM) traffic in the networking. Specifically, when the network side facing the NPE transmits the BUM traffic, the NPE learns the MAC address of the terminal device transmitting the BUM traffic based on the BUM traffic. And, the NPE transmits the BUM traffic to the SPE through PW from the NPE to the SPE so that the SPE learns the MAC address of the terminal equipment. The SPE receives the BUM traffic and transmits the BUM traffic to the UPE through PW from the SPE to the UPE so that the UPE learns the MAC address of the terminal equipment.
In this scenario, when a loop occurs on the UPE side, after the UPE receives the BUM traffic, the BUM traffic is transmitted in the loop on the UPE side and then sent to the UPE due to the loop, so that the BUM traffic returns to the UPE again, and at this time, the UPE transmits the BUM traffic to the SPE through the PW from the UPE to the SPE. The SPE can detect that the BUM flow jumps on different PW so as to judge that a loop exists at the UPE, and the PW from the SPE to the UPE is blocked so as to break the loop.
In the H-EVPN networking, the SPE serves as a Route Reflector (RR) to establish a neighbor relation with other different PEs, so that other PEs serve as Reflector clients to issue MAC routes to the Route Reflector SPE, and after receiving the MAC routes, the Route Reflector SPE reflects other issued MAC routes to the neighbors, thereby realizing that each terminal device in the H-EVPN networking learns MAC addresses.
Specifically, the network side that the NPE faces sends traffic to the NPE, which receives the traffic and learns the MAC address of the traffic. The MAC route is then encapsulated based on the MAC address and sent to the SPE. The MAC route includes a MAC address and a next hop, which is NPE. The SPE receives the MAC route, modifies the next hop in the MAC route into the SPE, and continues to send the modified MAC route to the UPE.
From the foregoing, it can be seen that in the H-EVPN network, the PEs no longer establish communication based on PW. However, because there is no PW, in the H-EVPN, the SPE can only receive the MAC route issued by another PE, modify the next hop of the MAC route to itself, issue the modified MAC route again, and cannot find out the problem that a loop failure occurs in a certain PE. That is, the SPE does not have loop detection capability in H-EVPN networking.
It should be noted that, in the H-EVPN networking, UPE may implement a loop detection function through a MAC drift loop detection technique (MAC-mapping-based loop detection, MAC-mapping). In this scenario, if the UPE detects that the source MAC address of the traffic sent by the down-hanging terminal device and the MAC address in the MAC route learned from the remote NPE are the same MAC address, it can be determined that a loop appears on the UPE side. At this point, UPE can directly block the flow of the loop in situ. The blocking implementation process may be: setting the source MAC address of the traffic to a black hole MAC, and subsequently if traffic including the black hole MAC is received, not continuing to issue MAC routes for the black hole MAC.
However, in many cases, UPE does not have a loop detection function. For example, UPE does not have the ability to find black hole MAC, or does not have MAC drift loop detection techniques, or fails to block the function of the loop traffic after detecting the presence of a loop. In these scenarios, UPE still learns the MAC address of traffic comprising the black hole MAC and encapsulates the MAC route based on the MAC address, and then sends the MAC route on to other PEs.
In addition, because the UPE is a PE device in the network that is closer to the user, if the UPE is controlled manually and attacks the SPE or the NPE, the service damage or even paralysis of the whole network will be caused. Thus, the risk of enabling UPE with loop detection capability is relatively high.
Based on the above scenario, in the embodiment of the present application, an SPE serving as a central node in the H-EVPN networking may be enabled to have a function of detecting a loop and blocking loop traffic. The route advertising method provided by the embodiment of the application is used for realizing the function.
The network architecture according to the embodiments of the present application is explained below.
Fig. 1 is a network architecture diagram of an H-EVPN according to an embodiment of the present application. As shown in fig. 1, NPE, SPE, and n UPEs (UPE 1 and UPEn are shown in the example of fig. 1) are deployed in the network. The UPE and the SPE are connected by an access layer network, the SPE and the NPE are connected by a convergence layer network, and the access layer network and the convergence layer network are respectively provided with an independent interior gateway protocol (Interior Gateway Protocol, IGP) protocol to realize intercommunication of respective network layers.
The UPE is a PE directly connected to a user, and the user accesses the UPE through a Customer Edge (CE). The UPE mainly completes the user access function, and may also be referred to as a lower layer PE (under-layer PE) or a backbone network edge device (provider PE). SPE accesses UPE. In fig. 1, SPEs access UPE1, …, and UPEn. The SPE mainly completes the management and release functions of VPN routing, and can also be called upper PE (super-layer PE) or label switching forwarding equipment (switching PE). The NPE connects SPEs and faces the network side, which may also be referred to as remote network devices.
In addition, the NPE and the n UPEs each establish a neighbor relation with the SPE to publish the MAC route based on the neighbor relation. The neighbor relation may be a fourth generation network protocol (Internet Protocol Version, ipv 4) neighbor relation or a sixth generation network protocol (Internet Protocol Version, ipv 6) neighbor relation. When NPE, UPE1 and UPEn all establish IPv4 neighbor relation with SPE, multiprotocol label switching/virtual extensible local area network/Segment Routing (MPLS/VXLAN/SR) tunnel bearing service is deployed between each PE neighbor. When NPE, UPE1, and UPEn all establish IPv6 neighbor relation with SPE, segment routing (segment routing over IPv, SRv) tunnels based on sixth generation network protocol are deployed between the PE neighbors to carry traffic.
In this embodiment of the present application, in order to implement a function of detecting a loop and blocking a loop flow of an SPE serving as a central node in an H-EVPN network, as shown in fig. 2, the SPE may include a detection module, a blocking module, and an alarm module. The detection module is used for detecting the loop. The blocking module is used for executing blocking operation when detecting that a loop appears. The alarm module is used for reporting alarm information to the network controller so as to inform operation and maintenance personnel that a loop currently appears. The detailed functions of these three modules will be described in the following embodiments and will not be explained here.
The modules involved in the SPE are software modules, and the software modules can realize corresponding functions through the method provided by the embodiment of the application.
It should be noted that fig. 1 is an example of one NPE, one SPE, and n UPEs, and the number of NPE, SPE, UPE included in the H-EVPN network in the embodiment of the present application is not limited.
The following explains the route advertisement method provided in the embodiment of the present application in detail.
Fig. 3 is a flowchart of a route advertisement method according to an embodiment of the present application, where the method is applied to H-EVPN networking. Referring to fig. 3, the method includes the following steps.
Step 301: the SPE receives a first route notification message carrying a MAC address and a next hop.
As shown in fig. 1, the H-EVPN network further includes UPE and NPE.
The first route advertisement message is the MAC route. The first routing notification message may be sent by the NPE, where the MAC address in the first routing notification message is the MAC address of the CE1 suspended under the NPE, and the next hop is the NPE. The first routing notification message may also be sent by UPE1, where the MAC address in the first routing notification message is the MAC address of CE2 suspended under UPE, and the next hop is UPE1.
If the first route notification message is sent by the NPE, the transmission process of the first route notification message is: as shown in fig. 4, the CE1 suspended under the NPE sends traffic to the NPE, the NPE receives the traffic and learns the source MAC address of the traffic, and encapsulates the first route advertisement packet based on the MAC address, where the first route advertisement packet carries the MAC address and the next hop. The MAC address is the unique identification of CE1, and the next hop is NPE. The NPE sends the first route notification message to the SPE, the SPE receives the first route notification message, and the corresponding relation between the MAC address in the first route notification message and the next hop is stored in the MAC forwarding table of the SPE.
If the first routing notification message is sent by UPE1, the transmission process of the first routing notification message is as follows: and the CE2 hung under the UPE1 sends the flow to the UPE1, the UPE1 receives the flow and learns the source MAC address of the flow, and then the first route notification message is packaged based on the MAC address, and the first route notification message carries the MAC address and the next hop. The MAC address is a unique identifier of the terminal equipment CE2, and the next hop is UPE1.UPE1 sends the first route notification message to SPE. The SPE receives the first route notification message, and stores the corresponding relation between the MAC address in the first route notification message and the next hop in an MAC forwarding table of the SPE.
In the embodiment of the application, in order to avoid loop faults, after each time a route notification message is received, an SPE judges whether an MAC address in the route notification message received at the current time is the same as an MAC address in the route notification message received before the current time, and whether a next hop in the route notification message received at the current time is the same as a next hop in the route notification message received before the current time, so as to implement an MAC route jump detection function, thereby implementing a subsequent loop detection function.
For convenience of explanation, the route advertisement message received before the current time is referred to as a second route advertisement message, so as to implement the MAC route jump detection function through the following steps. That is, when the SPE receives the first route notification message, it needs to compare the respective MAC addresses and the next hops in the first route notification message and the second route notification message, so as to implement the MAC route hopping detection function, and further implement the subsequent loop detection function.
Step 302: if the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
Based on step 302, the SPE may detect that a MAC routing hop occurs between certain two PEs in the H-EVPN network.
For example, if the MAC addresses in the first routing advertisement packet and the second routing advertisement packet are the same, and the next hop in the second routing advertisement packet is NPE, the next hop in the first routing advertisement packet is UPE1, which indicates that the next hop in the second routing advertisement packet is different from the next hop in the first routing advertisement packet, and at this time, the SPE may determine that a MAC routing hop occurs between the next hop NPE in the second routing advertisement packet and the next hop UPE1 in the first routing advertisement packet in the H-EVPN network.
For example, as shown in fig. 4, assume that CE2 hanging under UPE1 is looped. Under the scene, when the NPE receives the traffic sent by the down-hanging CE1, the source MAC address of the traffic is learned, and if the source MAC address is the MAC address A, the MAC address A is encapsulated in a second route notification message, and the second route notification message is issued to the SPE. And the SPE receives the second routing notification message, compares the MAC addresses in the second routing notification message, and finds that the same MAC address exists in the routing notification message before the current time. At this time, the SPE modifies the next hop in the second route notification message to itself to obtain other route notification messages, and issues other route notification messages to the UPE. When UPE1 receives other route notification messages, because a loop appears in CE2 hung under UPE1, the other route notification messages are returned to UPE1 after being transmitted in the loop, at this time, UPE1 misjudges that traffic sent by CE2 is received, and then learns the MAC address in the traffic (i.e. other route notification messages), so as to learn the MAC address a. UPE1 encapsulates the MAC address A in a first route notification message and issues the first route notification message to SPE. The SPE receives the first route notification message, compares the MAC addresses in the first route notification message, finds that the same MAC address A exists in the second route notification message received before the current time, and the next hop in the second route notification message is different from the next hop in the first route notification message, and can determine that the MAC route jump occurs between the NPE and the UPE 1.
In this embodiment of the present application, after receiving the first route advertisement packet, the SPE determines whether the MAC address in the first route advertisement packet is the same as the MAC address in the route advertisement packet received before the current time, and whether the next hop in the first route advertisement packet is the same as the next hop in the route advertisement packet received before the current time. If the MAC address of the second route notification message is the same as the MAC address of the first route notification message and the next hop in the second route notification message is different from the next hop in the first route notification message, the SPE determines that the MAC route jump occurs between the next hop in the second route notification message and the next hop in the first route notification message. That is, the SPE may detect that a MAC route jump occurs in the H-EVPN networking, so as to facilitate subsequent loop detection.
In the route advertising method of fig. 3, the SPE can detect that a MAC route hops in the H-EVPN network, and in the embodiment of the present application, the SPE can determine whether a loop occurs in the H-EVPN network based on the number of times of the MAC route hops. Referring to fig. 5, the method includes the following steps.
Step 301: the SPE receives a first route notification message carrying a MAC address and a next hop.
As described in the embodiment of fig. 3, the first routing advertisement message may be sent by UPE1 or NPE.
In some scenarios, the overall process of SPE receiving the first route advertisement message is: as shown in fig. 4, the CE1 suspended under the NPE sends traffic to the NPE, the NPE receives the traffic and learns the source MAC address of the traffic, and then encapsulates the route advertisement packet based on the MAC address, where the route advertisement packet carries the MAC address and the next hop. The MAC address is the unique identification of CE1, and the next hop is NPE. The NPE sends the route advertisement message to the SPE. And the SPE receives the route notification message and stores the corresponding relation between the MAC address in the route notification message and the next hop in an MAC forwarding table of the SPE. And recording the route notification message received by the SPE as a second route notification message.
After the SPE receives and stores the route notification message, the SPE modifies the next hop in the route notification message into the SPE and then sends the modified route notification message to UPE1.UPE1 receives the modified route advertisement message. Thus, the MAC address of CE1 can be propagated in the H-EVPN network. If a loop appears in the CE2 suspended under UPE1, at this time, the modified route notification message is returned to UPE1 again after being transmitted in the loop, UPE1 misjudges that the traffic sent by CE2 is received, and then learns the MAC address in the traffic (i.e. the modified route notification message). UPE1 then encapsulates the MAC address in a first route advertisement message and issues the first route advertisement message to the SPE. The SPE receives the first route notification message, wherein the MAC address in the first route notification message is the MAC address of CE1, and the next hop is UPE1.
In other scenarios, the overall process of the SPE receiving the first route advertisement message is: and the CE2 hung under the UPE1 sends the flow to the UPE1, the UPE1 receives the flow and learns the source MAC address of the flow, and then the route notification message is packaged based on the MAC address, and the route notification message carries the MAC address and the next hop. The MAC address is the unique identification of CE2 and the next hop is UPE1.UPE1 sends the route advertisement message to SPE. And the SPE receives the route notification message and stores the corresponding relation between the MAC address in the route notification message and the next hop in an MAC forwarding table of the SPE. And recording the route notification message received by the SPE as a second route notification message.
After the SPE receives and stores the route notification message, the SPE modifies the next hop in the route notification message into the SPE and then sends the modified route notification message to the NPE. The NPE receives the route advertisement message. Thus, the MAC address of CE2 can be propagated in the H-EVPN network. If the CE1 suspended under the NPE has a loop, at this time, the modified route notification message is returned to the NPE again after being transmitted in the loop, the NPE misjudges that the traffic sent by the CE1 is received, and then learns the MAC address in the traffic (i.e. the modified route notification message). The NPE then encapsulates the MAC address in a first route advertisement message and issues the first route advertisement message to the SPE. The SPE receives the first route notification message, wherein the MAC address in the first route notification message is the MAC address of CE2, and the next hop is NPE.
Based on the above two descriptions of the scenario, if a certain PE, such as UPE or NPE, has a loop, the SPE will detect the MAC route jump, so in order to implement loop detection, the SPE needs to detect whether the MAC route has jump. The specific implementation refers to step 302 described below.
Step 302: if the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
The process of the SPE determining that the MAC route jump occurs between the next hop in the first route advertisement packet and the next hop in the second route advertisement packet may refer to the relevant content in the embodiment of fig. 3.
Step 303: the SPE determines the times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the beginning of the detection period to the current time, and obtains the hopping times.
The detection period is a period of detecting networking which is preconfigured by the network controller. For example, the detection period may be set to 10 minutes. That is, the SPE determines the number of MAC route hops between the next hop in the first route advertisement message and the next hop in the second route advertisement message in the period from the start of the detection period to the current time, and obtains the number of hops.
In the embodiment of the application, if the MAC route jump is generated by normal update of the MAC route, the SPE cannot detect that the MAC route jump occurs between two next hops for multiple times in a short time. If the MAC route jump is generated when the PE has a loop failure, the SPE may detect the MAC route jump between two next hops multiple times in a short time.
Based on the above considerations, the network controller presets a reference number of hops. The purpose of presetting the reference jump times by the network controller is as follows: the SPE can distinguish whether the MAC route jump is generated by normal update of the MAC route or when the PE has loop fault, so that the condition that the SPE updates the MAC route normally is avoided from mistaking the PE to have the loop fault. The reference hop count is preset by the network controller, which is not limited in the embodiments of the present application.
Specifically, if the number of hops exceeds the reference number of hops, the loop is judged to appear, and if the number of hops does not exceed the reference number of hops, the MAC route is continuously issued.
In the embodiment of the present application, the excess may be greater than or equal to one another. When the excess is greater than, accordingly, no excess is less than or equal to. When the excess is greater than or equal to, accordingly, no excess is less than.
For example, with reference to a hop count of 3, as shown in fig. 4, assume that CE2 hanging down UPE1 is looped. Under the scene, when the SPE receives a first route notification message sent by the UPE1, the SPE finds that the second route notification message and the first route notification message received before the current time have the same MAC address, and the next hop in the second route notification message is different from the next hop in the first route notification message, at the moment, the SPE can determine that the MAC route jump occurs between the NPE and the UPE1, and records the jump frequency as 1. Because the hop count 1 does not exceed the reference hop count 3, the SPE modifies the next hop in the first route notification message to itself, the modified first route notification message is sent to the NPE, after the NPE receives the modified first route notification message, the NPE finds that the MAC address in the modified first route notification message is the same as the MAC address in the route notification message sent before the local current time, and at this time, the NPE determines that the route notification message issued locally is optimal, and sends the route notification message issued locally to the SPE again. After receiving the route notification message, the SPE finds that the same MAC address exists in the route notification message and the first route notification message before the current time, and the next hop in the route notification message is different from the next hop in the first route notification message, and at the moment, the SPE can determine that MAC route hopping occurs between the NPE and the UPE1 and update the hopping frequency to be 2. Because the hop count 2 does not exceed the reference hop count 3, the next hop in the route announcement message can be modified continuously to be modified to be self, and then the modified route announcement message is sent to the UPE1, and because the CE2 hung under the UPE1 has a loop, at the moment, the modified route announcement message is transmitted in the loop and then returned to the UPE1 again, the UPE1 misjudges that the flow sent by the CE2 is received again, and then the route announcement message packaged based on the MAC address in the flow is sent to the SPE continuously. Thus, two routing advertisement messages with the same MAC address but different next hops jump back and forth on UPE1, SPE and NPE in the H-EVPN networking, and the SPE updates the jump times when detecting the jump each time.
Step 304: if the number of hops exceeds the reference number of hops, the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message are looped.
The number of hops is obtained in step 303, and if the number of hops exceeds the reference number of hops, the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message have loops. That is, the SPE determines that a UPE occurs in a loop, or that an NPE occurs in a loop, or that UPE and NPE occur in a loop.
In addition, when the UPE determines that a loop occurs, whether the MAC address in the currently received flow is the same as the MAC address in the route notification message transmitted by the remote NPE is judged, if the MAC addresses of the MAC address and the MAC address are the same, the UPE determines that the loop fault occurs at the UPE. In the method for determining the occurrence of the loop by the SPE in the embodiment of the application, the received route notification messages are directly compared, the frequency of jumping of the next hop in the route notification messages with the same MAC address in the H-EVPN networking is detected, and whether the PE of the H-EVPN networking has the loop fault is further determined.
In the embodiment of the application, the SPE determines whether a loop fault occurs in the H-EVPN networking through the number of times that the MAC route jump occurs between the next hop in the received first route notification message and the next hop in the second route notification message. If the number of times of MAC route hopping between the next hop in the first route advertisement message and the next hop in the second route advertisement message exceeds the reference hopping number, the SPE can determine that a loop fault occurs. Unlike the method that UPE needs to learn the MAC address in the locally received traffic and the MAC address of the route notification message sent by the far end to judge that the loop fault occurs, the method that the central node SPE is utilized to judge the loop fault in the networking in the embodiment of the application avoids the situation that the H-EVPN networking is possibly damaged by manual operation of UPE.
In the route advertisement method in fig. 5, the SPE may detect a loop fault in the H-EVPN network, and obtain which PEs the loop fault may exist on. In the embodiment of the application, after detecting that the loop fault occurs in the networking, the SPE can report the conditions of which PE the loop fault possibly exists on to the network controller, so that operation and maintenance personnel can maintain the network in time. Referring to fig. 6, the method includes the following steps.
Step 301: the SPE receives a first route notification message carrying a MAC address and a next hop.
In particular, the SPE may refer to the relevant content in the embodiment of fig. 5.
Step 302: if the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
Specifically, the process of the SPE determining that the MAC route jump occurs between the next hop in the first route advertisement packet and the next hop in the second route advertisement packet may refer to the relevant content in the embodiment of fig. 3.
Step 303: the SPE determines the times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the beginning of the detection period to the current time, and obtains the hopping times.
In particular, the SPE may obtain the number of hops by referring to the relevant content in the embodiment of fig. 5.
Step 304: if the number of hops exceeds the reference number of hops, the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message are looped.
In particular, the SPE may refer to the relevant content in the embodiment of fig. 5 described above in determining that a loop occurs.
Step 305: reporting an alarm message on the SPE, wherein the alarm message carries a next hop in the first route notification message and a next hop in the second route notification message, and the alarm message is a loop for one or both of the next hop in the first route notification message and the next hop in the second route notification message.
As described in step 304, when the SPE detects that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message have loops, it generates an alarm message, and reports the alarm message to the network controller, where the loops occur in the network are handled in time by the network controller.
For example, the SPE generates an alarm message when determining that a loop fault occurs in the next hop UPE of the received first route notification message and the next hop NPE of the second route notification message, and reports the alarm message to the network controller. The alarm message is a loop fault occurring in a next hop UPE in the first route notification message and/or a next hop NPE in the second route notification message.
In the embodiment of the application, the SPE can detect the loop fault in the H-EVPN networking, can generate the alarm message under the condition of the loop fault, and reports the alarm message to the network controller, and an operation and maintenance person at the network controller timely processes the PE with the loop fault in the networking, so that the effect of protecting the H-EVPN networking in real time is achieved.
In the route advertisement method in fig. 6, the SPE reports the loop fault to the network controller. In the embodiment of the application, after the SPE detects that the loop fault occurs, the PE with the loop fault can be directly blocked, so that the PE with the loop fault is ensured not to transmit the route notification message or the traffic in the networking again, and the resource waste is avoided. Referring to fig. 7, the method includes the following steps.
Step 301: the SPE receives a first route notification message carrying a MAC address and a next hop.
In particular, the SPE may refer to the relevant content in the embodiment of fig. 5.
Step 302: if the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that the MAC route jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
Specifically, the process of the SPE determining that the MAC route jump occurs between the next hop in the first route advertisement packet and the next hop in the second route advertisement packet may refer to the relevant content in the embodiment of fig. 3.
Step 303: the SPE determines the times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the beginning of the detection period to the current time, and obtains the hopping times.
In particular, the SPE may obtain the number of hops by referring to the relevant content in the embodiment of fig. 5.
Step 304: if the number of hops exceeds the reference number of hops, the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message are looped.
In particular, the SPE may refer to the relevant content in the embodiment of fig. 5 described above in determining that a loop occurs.
Step 305: the SPE determines the blocking priority of the next hop in the first route advertisement message and the blocking priority of the next hop in the second route advertisement message.
It should be noted that, in the foregoing embodiments, one NPE is taken as an example, and in the H-EVPN network, multiple NPEs may exist at the same time, where the processing manner of the route advertisement message on the multiple NPEs is the same as that of the route advertisement message on one NPE.
After the SPE determines that the next hop of the first routing notification message and the next hop of the second routing notification message are in a loop, the blocking priority of each of two next hop PEs in the first routing notification message and the second routing notification message can be determined.
Wherein, since the importance degree of each PE in the H-EVPN networking is different, when the PE is blocked by the SPE, the PE with low importance degree is blocked preferentially, so the blocking priority of the PE can be set based on the importance degree of each PE in the networking. Illustratively, the higher the importance of a PE, the lower the corresponding blocking priority.
Illustratively, the blocking priority of the UPE is higher than the blocking priority of the NPE. The blocking priority of UPE is higher than that of NPE, i.e. it means that UPE is blocked preferentially when SPE blocks PE with loop failure. For example, the SPE may never block the NPE.
Furthermore, the blocking priorities are different between different UPEs and different NPEs.
When a plurality of UPEs occur, the blocking priority of each UPE is different, at this time, the blocking priority of each UPE is set by the network controller according to the importance degree of each UPE in the H-EVPN networking, the blocking priority of the UPE with low importance degree is high, and the SPE also blocks the UPE preferentially.
Similarly, when a plurality of NPEs occur, the blocking priority of each NPE is also different, and at this time, the blocking priority of each NPE is also set by the network controller according to the importance degree of each NPE in the H-EVPN network, and the blocking priority of the NPE with low importance degree is high, so that the SPE also blocks the NPE preferentially.
For example, if there are 3 UPEs and 2 NPEs in the H-EVPN network, UPE1, UPE2, UPE3, NPE1, and NPE2 respectively, the 3 UPEs are in order from high importance: UPE1, UPE2 and UPE3, and the 2 NPEs are sequentially from high to low according to the importance degree: NPE1, NPE2, the 5 PEs are in order of blocking priority from high to low: UPE3, UPE2, UPE1, NPE2, NPE1.
Step 306: the SPE determines the next hop in the first route notification message and the next hop with higher blocking priority in the next hop in the second route notification message, and obtains the blocking peer.
As described in step 305, the higher blocking priority PE, the SPE blocks the PE preferentially, so the SPE compares the blocking priority of the next-hop PE1 in the first route advertisement message with the blocking priority of the next-hop PE2 in the second route advertisement message, determines the PE with the higher blocking priority, and marks the PE as a blocking peer (peer).
For example, for the networking shown in fig. 4, the next hop in the first routing advertisement packet is UPE1, and the next hop in the second routing advertisement packet is NPE, and the UPE is higher than the NPE in blocking priority, so the SPE determines UPE1 as a blocking peer.
For example, for the networking shown in fig. 4, assume that the next hop in the first routing advertisement packet is UPE3 (not shown in fig. 4), and the next hop in the second routing advertisement packet is UPE1, as described in step 305, UPE3 and UPE1 are sequentially from high to low in order of blocking priority: UPE3, UPE1, then SPE determines UPE3 as blocking peer according to the principle that the higher blocking priority PE, SPE blocks the PE preferentially.
In addition, after the SPE determines that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message have loops, the SPE may further generate a first alarm message and send the first alarm message to the network controller. The first alarm message carries the conditions on which PEs a loop failure may be present.
In addition, after the SPE determines to block the peer, a second alarm message may also be sent to the network controller, where the second alarm message carries what PE the SPE specifically blocks, that is, carries the blocking peer.
Step 307: the SPE performs blocking operations on blocking peers.
After determining the blocking peer, the SPE performs corresponding processing on both the forwarding layer and the control layer to perform blocking operation on the blocking peer.
In some embodiments, the implementation of the SPE performing the blocking operation at the forwarding layer may be: when receiving service messages sent from nodes except the blocking peer, if the destination MAC address of the service message is the MAC address learned from the blocking peer, the operation of forwarding the service message to the blocking peer is not performed. Or when receiving the service message from the blocking peer, the operation of forwarding the service message to other nodes except the blocking peer is not executed. That is, after the SPE determines the blocking peer, the SPE will block traffic from or to the blocking peer.
The service message carries a destination address and a source address, the destination address is the MAC address of a destination to which a load (payload) in the service message needs to be sent, and the source address is the MAC address of a node sending the service message to the SPE. Therefore, when the SPE receives the service message, it can determine whether the service message is the service message sent by the blocking peer according to the source address carried in the service message. According to the destination address carried in the service message and the local forwarding table, whether the service message is the service message sent to the blocking peer or not can be determined.
For example, when the SPE receives a service packet sent by a PE other than the blocking peer, it detects a destination MAC address in the service packet, if the destination MAC address in the service packet is learned from the blocking peer, at this time, the SPE may determine that the next hop of the service packet is the blocking peer according to the correspondence between the MAC address in the locally stored forwarding table and the next hop, that is, the service packet is the service packet that needs to be sent to the blocking peer, so the SPE does not forward the service packet to the blocking peer.
For example, corresponding to the networking shown in fig. 4, if the blocking peer is UPE1, when the SPE receives the service packet sent from the NPE, and the destination MAC address in the service packet is the MAC address learned from UPE1, the SPE does not send the service packet to UPE 1.
Also for example, when the SPE receives a service message sent from the blocking peer, the SPE does not forward the service message to the corresponding PE according to the destination MAC address in the service message.
For example, corresponding to the networking shown in fig. 4, if the blocking peer is UPE1, the UPE1 sends a service message to the SPE, the source MAC address of the service message is the MAC address of UPE1, and the SPE does not forward the service message to the NPE after receiving the service message.
In other embodiments, the implementation process of the SPE performing the blocking operation at the control layer may be: and adding mark information to the route notification message sent by the current time blocking peer, wherein the route notification message sent by the current time blocking peer is a first route notification message or a second route notification message. If the third route notification message sent by the blocking peer is received again and the route notification message marked by the third route notification message and the marking information is the same route notification message, the operation of issuing the route notification message based on the third route notification message is not executed.
Illustratively, the SPE, upon detecting the presence of a loop, adds marker information to the route advertisement message sent by the blocking peer, the marker information indicating that the route advertisement message was sent by the blocking peer. If the SPE receives the third route notification message sent from the blocking peer again and the MAC address and the next hop in the third route notification message are the same as those in the route notification message marked by the marking information, the SPE does not execute the operation of issuing the route notification message based on the third route notification message. That is, the SPE does not modify the next hop in the third routing advertisement message and sends the modified third routing advertisement message to other PEs.
For example, for the networking shown in fig. 4, if the blocking peer is UPE1, UPE1 sends a first route notification message to the SPE, where the MAC address in the first route notification message is the MAC address of CE2 suspended under UPE1, and the next hop is UPE1. The SPE receives the first route notification message, and the SPE adds mark information to the first route notification message when detecting a loop. If the SPE receives the third route notification message sent by the UPE1 again, the MAC address in the third route notification message is the MAC address of the CE2, and the next hop is the UPE1, namely, the MAC address and the next hop in the third route notification message are the same as the MAC address and the next hop in the route notification message marked by the marking information, at the moment, the SPE does not modify the next hop in the third route notification message into the SPE, and sends the modified third route notification message to the NPE.
In addition, when the blocking operation is performed on the blocking peer, the current time can be counted, and before the counted time length reaches the blocking time length, the blocking operation is performed on the blocking peer.
The current time is the starting time of the blocking operation of the SPE on the blocking peer, namely, the moment when the SPE detects the loop. The blocking duration is set in advance by the network controller. For example, the blocking duration may be a duration required for a default operation and maintenance person to maintain the networking. In this scenario, when the timing duration reaches the blocking duration, the SPE default networking is already maintained, i.e. has been broken, so the SPE can discard the blocking operation at this time. That is, the SPE continues to forward traffic from or to the blocking peer at the forwarding level and continues to forward route advertisement messages from or to the blocking peer at the control level.
Of course, the blocking duration can also be infinite, i.e. the SPE permanently blocks the blocking peer, in which case it is necessary for the operation and maintenance personnel at the network controller to manually release the blocking after manually removing the loop fault in the networking.
In addition, if the time duration has not reached the blocking time duration, the operation and maintenance personnel at the network controller may already process the PE with the loop fault, at this time, the network controller may send a blocking and releasing instruction to the SPE, where the blocking and releasing instruction indicates that the fault in the networking has been processed, and the networking may continue to operate. In this scenario, in some embodiments, after performing the blocking operation on the blocking peer, if the SPE receives the blocking release instruction before the timing duration reaches the blocking duration, the SPE does not perform the blocking operation on the blocking peer any more.
For example, for the networking shown in fig. 4, if the blocking peer is UPE1, the SPE receives the first routing advertisement packet sent from UPE1, and the SPE does not perform the operation of sending the first routing advertisement packet when detecting the loop, and starts timing from the current time. If the blocking period is 5 minutes. When the time duration reaches 4 minutes, the SPE receives a blocking release instruction sent by the network controller, and at the moment, the SPE gives up blocking operation. After the SPE gives up blocking operation, if the SPE receives the route notification message sent from the UPE1 again, the SPE modifies the next hop in the route notification message into the SPE and sends the modified route notification message to the NPE.
Furthermore, it is the blocking peer that is determined based on the blocking priority between PEs. Alternatively, in the embodiment of the present application, a pair of PEs when a loop failure occurs may also be set as blocking peers, that is, both the relevant traffic and MAC routes of the two PEs are blocked at the same time. For example, if the SPE detects that UPE and NPE are looped, both UPE and NPE may be set to block the peer and block traffic and MAC routing from or to both UPE and NPE.
In the H-EVPN networking in the embodiment of the present application, the SPE performs loop detection, and compared with the UPE performing loop detection, the SPE is far from the user, so that the SPE is manually controlled and modified with a small probability, thereby improving the success rate of loop detection. In addition, the number and variety of UPEs in the H-EVPN networking are more, if the loop detection function is enabled on the UPEs, a large number of UPEs of different types are required to enable the loop detection function respectively, so that the loop detection function in the whole networking is not sound enough easily, and in the embodiment of the application, the network complexity is simplified by enabling the loop detection function of the central node SPE, and therefore the waste of network resources is avoided. In addition, when a loop appears, the success rate of the central node SPE for blocking the flow from the loop is higher than the success rate of the UPE for blocking the flow from the loop.
In the embodiment of the application, the SPE determines a blocking peer according to the blocking priority among PEs after determining that the next hop of the first routing notification message or the next hop of the second routing notification message appears in a loop by detecting the next hop of the received first routing notification message and the next hop of the second routing notification message, and executes blocking operation on the blocking peer. Therefore, the situation that the business message or the route notification message based on the blocking peer is repeatedly transmitted in the H-EVPN networking can not occur, and further the waste of network resources can not be caused. And PE with loop fault is reported to the network controller by SPE, namely blocking peer, and the PE with loop fault is processed in time by operation and maintenance personnel at the network controller, so that the effect of protecting networking in time is achieved.
Fig. 8 is a schematic structural diagram of an SPE in an H-EVPN networking provided in an embodiment of the present application. Referring to FIG. 8, the SPE comprises: a transceiver module 801 and a processing module 802.
The transceiver module 801 is configured to receive a first route advertisement packet, where the first route advertisement packet carries a MAC address and a next hop. The transceiver module is specifically described with reference to step 301 in the embodiment of fig. 3.
A processing module 802, configured to determine that a MAC route jump occurs between a next hop in the first route advertisement packet and a next hop in the second route advertisement packet if the MAC address in the first route advertisement packet is the same as the MAC address in the second route advertisement packet received before the current time, and the next hop in the first route advertisement packet is different from the next hop in the second route advertisement packet. Wherein the specific implementation of the processing module refers to step 302 in the embodiment of fig. 3.
Optionally, the processing module 802 is further configured to:
determining the number of times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the beginning of the detection period to the current time, and obtaining the hopping number;
if the number of hops exceeds the reference number of hops, determining that one or both of the next hop in the first route advertisement message and the next hop in the second route advertisement message are looped.
Optionally, the processing module 802 is further configured to:
reporting an alarm message, wherein the alarm message carries a next hop in a first route notification message and a next hop in a second route notification message, and the alarm message is one or both of the next hop in the first route notification message and the next hop in the second route notification message and loops.
Optionally, the processing module 802 is further configured to:
determining the blocking priority of the next hop in the first route notification message and the blocking priority of the next hop in the second route notification message;
determining the next hop in the first route notification message and the next hop with higher blocking priority in the next hop in the second route notification message to obtain a blocking peer;
a blocking operation is performed on the blocking peer.
Optionally, the processing module 802 is further configured to:
when receiving service messages sent from nodes except the blocking peer, if the destination MAC address of the service message is the MAC address learned from the blocking peer, the operation of forwarding the service message to the blocking peer is not performed.
Optionally, the processing module 802 is further configured to:
when receiving the service message from the blocking peer, the operation of forwarding the service message to other nodes except the blocking peer is not executed.
Optionally, the processing module 802 is further configured to:
adding mark information to the route notification message sent by the current time blocking peer, wherein the route notification message sent by the current time blocking peer is a first route notification message or a second route notification message;
If the third route notification message sent by the blocking peer is received again and the route notification message marked by the third route notification message and the marking information is the same route notification message, the operation of issuing the route notification message based on the third route notification message is not executed.
Optionally, the H-EVPN further includes a UPE and an NPE, wherein the blocking priority of the UPE is higher than that of the NPE.
Alternatively, the blocking priorities may be different between different UPEs.
Optionally, the blocking priorities are different between different NPEs.
Optionally, the processing module 802 is further configured to:
starting timing from the current time;
and before the timing duration reaches the blocking duration, performing a blocking operation on the blocking peer.
Optionally, the processing module 802 is further configured to:
before the timing duration reaches the blocking duration, if a blocking release instruction is received, the blocking operation is not performed on the blocking peer.
In this embodiment of the present application, after receiving the first route advertisement packet, the SPE determines whether the MAC address in the first route advertisement packet is the same as the MAC address in the route advertisement packet received before the current time, and whether the next hop in the first route advertisement packet is the same as the next hop in the route advertisement packet received before the current time. If the MAC address of the second route notification message is the same as the MAC address of the first route notification message and the next hop in the second route notification message is different from the next hop in the first route notification message, the SPE determines that the MAC route jump occurs between the next hop in the second route notification message and the next hop in the first route notification message. That is, the SPE may detect that a MAC route jump occurs in the H-EVPN networking, so as to facilitate subsequent loop detection.
It should be noted that: when the SPE provided in the above embodiment performs route notification, only the division of each functional module is used for illustration, in practical application, the above functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the SPE provided in the foregoing embodiment and the route advertisement method embodiment belong to the same concept, and the specific implementation process of the SPE is detailed in the method embodiment and will not be described herein.
Fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application. The network device is configured to implement the SPE functionality of the foregoing embodiments. Referring to fig. 9, the network device comprises at least one processor 901, a communication bus 902, a memory 903, and at least one communication interface 904.
Processor 901 may be a general purpose central processing unit (central processing unit, CPU), application Specific Integrated Circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present application.
Communication bus 902 may include a path to transfer information between the aforementioned components.
The Memory 903 may be, but is not limited to, a read-only Memory (ROM) or other type of static storage device that can store static information and instructions, a random access Memory (random access Memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only Memory (electrically erasable programmable read-only Memory, EEPROM), a compact disc (compact disc read-only Memory) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 903 may be separate and coupled to the processor 901 via a communication bus 902. The memory 903 may also be integrated as the processor 901.
The memory 903 is used for storing program codes for executing the embodiments of the present application, and the processor 901 controls the execution. The processor 901 is for executing program code stored in the memory 903. One or more software modules may be included in the program code.
The communication interface 904, uses any transceiver-like means for communicating with other devices or communication networks, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc.
In a particular implementation, as one embodiment, the network device may include multiple processors, such as processor 901 and processor 905 shown in FIG. 9. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, data subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disk (digital versatile disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), etc.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The embodiments described above are not intended to limit the embodiments of the present application, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application are intended to be included in the scope of the embodiments of the present application.

Claims (26)

1. The route advertising method is characterized in that the method is executed by a service side operator edge device SPE in a layered Ethernet virtual private network H-EVPN networking;
the method comprises the following steps:
the SPE receives a first route notification message, wherein the first route notification message carries a Media Access Control (MAC) address and a next hop;
if the MAC address in the first routing notification message is the same as the MAC address in the second routing notification message received before the current time, and the next hop in the first routing notification message is different from the next hop in the second routing notification message, the SPE determines that MAC routing jump occurs between the next hop in the first routing notification message and the next hop in the second routing notification message.
2. The method of claim 1, wherein after the SPE determines that a MAC route hop occurs between a next hop in the first route advertisement message and a next hop in the second route advertisement message, the method further comprises:
the SPE determines the times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the detection period to the current time, and obtains the hopping times;
if the hop count exceeds a reference hop count, the SPE determines that one or both of a next hop in the first route advertisement message and a next hop in the second route advertisement message are looped.
3. The method of claim 2, wherein after the SPE determines that one of a next hop in the first route advertisement message or a next hop in the second route advertisement message is looped, the method further comprises:
reporting an alarm message on the SPE, wherein the alarm message carries a next hop in the first route notification message and a next hop in the second route notification message, and the alarm message is a loop for one or both of the next hop in the first route notification message and the next hop in the second route notification message.
4. A method according to any one of claims 1 to 3, wherein the method further comprises:
the SPE determines the blocking priority of the next hop in the first route notification message and the blocking priority of the next hop in the second route notification message;
the SPE determines the next hop in the first route notification message and the next hop with higher blocking priority in the next hop in the second route notification message to obtain a blocking peer;
the SPE performs blocking operations on the blocking peer.
5. The method of claim 4, wherein the performing a blocking operation on the blocking peer comprises:
when receiving service messages sent by nodes except the blocking peer, if the destination MAC address of the service message is the MAC address learned from the blocking peer, the operation of forwarding the service message to the blocking peer is not performed.
6. The method of claim 4, wherein the performing a blocking operation on the blocking peer comprises:
and when receiving the service message from the blocking peer, not executing the operation of forwarding the service message to other nodes except the blocking peer.
7. The method of claim 4, wherein the performing a blocking operation on the blocking peer comprises:
adding mark information to the route notification message sent by the blocking peer at the current time, wherein the route notification message sent by the blocking peer at the current time is the first route notification message or the second route notification message;
and if the third route notification message sent by the blocking peer is received again and the third route notification message and the route notification message marked by the marking information are the same route notification message, the operation of issuing the route notification message based on the third route notification message is not executed.
8. The method according to any one of claims 4 to 7, wherein the H-EVPN further comprises a user side operator edge device UPE and a network side operator edge device NPE, the UPE blocking priority being higher than the NPE blocking priority.
9. The method of claim 8, wherein blocking priorities are different between different UPEs.
10. The method of claim 8, wherein blocking priorities are different between different NPEs.
11. The method according to any of claims 4 to 10, wherein said performing a blocking operation on said blocking peer comprises:
starting timing from the current time;
and before the timing duration reaches the blocking duration, executing blocking operation on the blocking peer.
12. The method of claim 11, wherein the method further comprises:
and before the timing duration reaches the blocking duration, if the SPE receives a blocking release instruction, the blocking peer is not subjected to blocking operation.
13. A service side operator edge device SPE in a hierarchical ethernet virtual private network H-EVPN networking, the SPE comprising:
the receiving and transmitting module is used for receiving a first route notification message, wherein the first route notification message carries a Media Access Control (MAC) address and a next hop;
and the processing module is used for determining that MAC route jump occurs between the next hop in the first route notification message and the next hop in the second route notification message if the MAC address in the first route notification message is the same as the MAC address in the second route notification message received before the current time and the next hop in the first route notification message is different from the next hop in the second route notification message.
14. The SPE as recited in claim 13, wherein the processing module is further to:
determining the number of times of MAC route hopping between the next hop in the first route notification message and the next hop in the second route notification message from the beginning of the detection period to the current time, and obtaining the hopping number;
and if the hop count exceeds the reference hop count, determining that one or both of the next hop in the first routing advertisement message and the next hop in the second routing advertisement message are looped.
15. The SPE as recited in claim 14, wherein the processing module is further to:
reporting an alarm message, wherein the alarm message carries a next hop in the first route notification message and a next hop in the second route notification message, and the alarm message is a loop for one or both of the next hop in the first route notification message and the next hop in the second route notification message.
16. The SPE as recited in any one of claims 13-15, wherein the processing module is further to:
determining the blocking priority of the next hop in the first route notification message and the blocking priority of the next hop in the second route notification message;
Determining the next hop in the first route notification message and the next hop with higher blocking priority in the next hop in the second route notification message to obtain a blocking peer;
a blocking operation is performed on the blocking peer.
17. The SPE as recited in claim 16, wherein the processing module is to:
when receiving service messages sent by nodes except the blocking peer, if the destination MAC address of the service message is the MAC address learned from the blocking peer, the operation of forwarding the service message to the blocking peer is not performed.
18. The SPE as recited in claim 16, wherein the processing module is to:
and when receiving the service message from the blocking peer, not executing the operation of forwarding the service message to other nodes except the blocking peer.
19. The SPE as recited in claim 16, wherein the processing module is to:
adding mark information to the route notification message sent by the blocking peer at the current time, wherein the route notification message sent by the blocking peer at the current time is the first route notification message or the second route notification message;
And if the third route notification message sent by the blocking peer is received again and the third route notification message and the route notification message marked by the marking information are the same route notification message, the operation of issuing the route notification message based on the third route notification message is not executed.
20. An SPE as claimed in any one of claims 16 to 19 wherein the H-EVPN further comprises a user side operator edge device UPE and a network side operator edge device NPE, the UPE blocking priority being higher than the NPE blocking priority.
21. The SPE of claim 20, wherein the blocking priorities are different between different UPEs.
22. The SPE of claim 20, wherein blocking priorities are different between different NPEs.
23. The SPE as recited in any one of claims 16 to 22, wherein the processing module is to:
starting timing from the current time;
and before the timing duration reaches the blocking duration, executing blocking operation on the blocking peer.
24. The SPE as recited in claim 23, wherein the processing module is further to:
and before the timing duration reaches the blocking duration, if a blocking release instruction is received, no blocking operation is performed on the blocking peer.
25. A network device comprising a memory and a processor;
the memory is configured to store a program for supporting the network device to perform the method of any one of claims 1 to 12, and to store data related to implementing the method of any one of claims 1 to 12;
the processor is configured to execute a program stored in the memory.
26. A computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of any of claims 1-12.
CN202111409613.7A 2021-11-25 2021-11-25 Route advertising method, SPE, network equipment and storage medium Pending CN116170250A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111409613.7A CN116170250A (en) 2021-11-25 2021-11-25 Route advertising method, SPE, network equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111409613.7A CN116170250A (en) 2021-11-25 2021-11-25 Route advertising method, SPE, network equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116170250A true CN116170250A (en) 2023-05-26

Family

ID=86413704

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111409613.7A Pending CN116170250A (en) 2021-11-25 2021-11-25 Route advertising method, SPE, network equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116170250A (en)

Similar Documents

Publication Publication Date Title
US10432514B2 (en) Multiprotocol label switching traffic engineering tunnel establishing method and device
US10554542B2 (en) Label distribution method and device
US9634928B2 (en) Mesh network of simple nodes with centralized control
CN110324165B (en) Network equipment management method, device and system
EP2996290B1 (en) Packet forwarding method, apparatus, and system
US6987727B2 (en) Automatic protection switching using link-level redundancy supporting multi-protocol label switching
US9276898B2 (en) Method and device for link fault detecting and recovering based on ARP interaction
EP3751801A1 (en) Border gateway protocol for communication among software defined network controllers
WO2016115823A1 (en) Method and apparatus for forwarding label construction and label packet
US20110090834A1 (en) Wireless mesh routing protocol utilizing hybrid link state algorithms
US20130223237A1 (en) Diverse paths using a single source route in computer networks
CN109660442B (en) Method and device for multicast replication in Overlay network
CN109218456B (en) Method and device for processing aging time of MAC address table
JP6027688B2 (en) Method and apparatus for automatic label assignment in ring network protection
US11240063B2 (en) Methods, nodes and computer readable media for tunnel establishment per slice
WO2017036180A1 (en) Packet processing method and device
US20220329512A1 (en) Method and Apparatus for Updating Route Information, Computer Device, and Storage Medium
WO2022194023A1 (en) Packet processing method, network device, and controller
WO2020114083A1 (en) Method and apparatus for processing ioam information
CN106878173B (en) Route sending method and device
CN116170250A (en) Route advertising method, SPE, network equipment and storage medium
CN113595915A (en) Method for forwarding message and related equipment
CN108259292B (en) Method and device for establishing tunnel
CN112702263B (en) Method and device for forwarding message
CN117378180A (en) Method and device for path switching management

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