WO2022127284A1 - 信息处理方法、节点及计算机可读存储介质 - Google Patents

信息处理方法、节点及计算机可读存储介质 Download PDF

Info

Publication number
WO2022127284A1
WO2022127284A1 PCT/CN2021/121761 CN2021121761W WO2022127284A1 WO 2022127284 A1 WO2022127284 A1 WO 2022127284A1 CN 2021121761 W CN2021121761 W CN 2021121761W WO 2022127284 A1 WO2022127284 A1 WO 2022127284A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
sub
routing information
data packet
routing
Prior art date
Application number
PCT/CN2021/121761
Other languages
English (en)
French (fr)
Inventor
王玉保
陈然
刘冬梅
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020237017216A priority Critical patent/KR20230093015A/ko
Priority to US18/254,238 priority patent/US12034634B2/en
Priority to EP21905214.9A priority patent/EP4236126A4/en
Priority to JP2023528519A priority patent/JP2023549512A/ja
Publication of WO2022127284A1 publication Critical patent/WO2022127284A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • H04L45/04Interdomain routing, e.g. hierarchical routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/58Association of routers
    • H04L45/586Association of routers of virtual routers
    • 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
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/12Shortest path evaluation
    • H04L45/125Shortest path evaluation based on throughput or bandwidth
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/22Alternate routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/24Multipath
    • H04L45/243Multipath using M+N parallel active paths
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Routing or path finding of packets in data switching networks using route fault recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/32Flooding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/34Source routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/50Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/66Layer 2 routing, e.g. in Ethernet based MAN's
    • 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
    • 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/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • 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/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L2012/4629LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of communications technologies, and in particular, relate to an information processing method, a node, and a computer-readable storage medium.
  • Ethernet segment identifier (Ethernet Segment Identifier, ESI) is based on the provider edge router (Provider Edge, PE)
  • the main interface is configured.
  • B-MAC Backbone Media Access Control Address
  • a circuit (Attachment Circuit, AC) is often not the main interface itself, but a sub-interface of the main interface.
  • the embodiments of the present application provide an information processing method, a node, and a computer-readable storage medium, which can solve the problem of data packet detour or packet loss caused by failure of a sub-interface of PE in the related art.
  • an embodiment of the present application provides an information processing method, which is applied to a first device, the first device and the second device have a dual-homing relationship, the first device is provided with a first sub-interface, the The second device is provided with a second sub-interface corresponding to the first sub-interface, and the method includes:
  • the first routing information corresponding to the first sub-interface is advertised in the network, so that the first sub-interface is in a normal state.
  • the third device sends the data packet to the first sub-interface according to the first routing information.
  • an embodiment of the present application further provides a node, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the first above when executing the computer program
  • a node including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the first above when executing the computer program
  • embodiments of the present application further provide a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to execute the above-mentioned information processing method.
  • FIG. 1 is a schematic diagram of a network topology for executing an information processing method provided by an embodiment of the present application
  • FIG. 3 is a flowchart of an information processing method provided by another embodiment of the present application.
  • FIG. 5 is a specific flowchart of forwarding a data packet to a sub-interface in an information processing method provided by another embodiment of the present application.
  • FIG. 6 is a specific flowchart of forwarding a data packet to a sub-interface in an information processing method provided by another embodiment of the present application.
  • the present application provides an information processing method, a node, and a computer-readable storage medium, aiming at a first device and a second device that have a dual homing relationship, and the first device is provided with a first sub-interface, and the second device is provided with a A second sub-interface corresponding to a sub-interface, when the first device determines that the second sub-interface of the second device is in a failed state but the main interface to which the second sub-interface belongs is still in a normal state, the first device is in the network
  • the first routing information corresponding to the first sub-interface is advertised, so that the third device can send the data packet to the first sub-interface of the first device according to the first routing information, thereby solving the problem in the related art due to certain problems of the device.
  • FIG. 1 is a schematic diagram of a network topology for executing an information processing method provided by an embodiment of the present application.
  • the network topology includes a first Customer Edge (CE) 110 , a first PE 120 , a second PE 130 , a third PE 140 , a first core router 150 and a second core router 160 .
  • the first CE110 is dual-homed to the first PE120 and the second PE130, the first PE120 and the second PE130 are both connected to the first core router 150, and the first core router 150, the second core router 160 and the third PE140 are connected in sequence.
  • the first PE 120 , the second PE 130 and the third PE 140 each include one first functional component 210 and two second functional components 220 , wherein the first functional component 210 is associated with each of the second functional components 220 connections.
  • the first PE120 further includes a first main interface 121, a first sub-interface 122, and a third sub-interface 123. The first sub-interface 122 and the third sub-interface 123 belong to the first main interface 121.
  • the two second functional components 220 are bound to the first sub-interface 122 and the third sub-interface 123 correspondingly; the second PE 130 also includes a second main interface 131, a second sub-interface 132 and a fourth sub-interface 133, the second sub-interface 133 132 and the fourth sub-interface 133 belong to the second main interface 131, and the two second functional components 220 in the second PE 130 are bound to the second sub-interface 132 and the fourth sub-interface 133 correspondingly.
  • the first sub-interface 122 and the second sub-interface 132 are associated based on the dual-homing relationship between the first PE120 and the second PE130, and the third sub-interface 123 and the fourth sub-interface 133 are based on the dual-homing relationship between the first PE120 and the second PE130 rather related.
  • first sub-interface 122 and the second sub-interface 132 can receive packets with the same virtual local area network (Virtual Local Area Network, VLAN) encapsulation
  • VLAN Virtual Local Area Network
  • each PE the main interface and each sub-interface are allocated with corresponding routing information, which can be Internet Protocol (Internet Protocol, IP) address, Media Access Control Address (Media Access Control Address, MAC) An address or an Ethernet Segment Identifier (Ethernet Segment Identifier, ESI), etc., are not specifically limited in this embodiment. It is worth noting that multiple sub-interfaces associated due to the dual-homing relationship between devices, for example, between the first sub-interface 122 of the first PE 120 and the second sub-interface 132 of the second PE 130, have the same route information.
  • IP Internet Protocol
  • MAC Media Access Control Address
  • ESI Ethernet Segment Identifier
  • the second functional component 220 is a service instance of forwarding data packets according to the C-MAC, wherein the second functional component 220 can forward data packets between PEs by using encapsulation formats such as VXLAN, PBB, MPLS, SRv6, etc.
  • the second functional component 220 may be respectively referred to as a VXLAN EVPN instance, a PBB EVPN instance, an MPLS EVPN instance, an SRv6 EVPN instance, and the like.
  • the first functional component 210 is used to carry a service instance (corresponding to the second functional component 220).
  • the first functional component 210 can advertise routing information corresponding to the main interface or routing information corresponding to the sub-interface in the network. It should be noted that when both the first PE 120 and the second PE 130 in the dual-homing relationship work normally, the first functional component 210 in the first PE 120 and the first functional component 210 in the second PE 130 can only be in the network Advertise the routing information corresponding to the main interface; when a certain sub-interface in the first PE120 is in a failed state, the routing information corresponding to the sub-interface corresponding to the failed sub-interface of the first PE120 in the second PE130 will be displayed.
  • the first functional component 210 in the second PE130 advertises in the network; when a certain sub-interface in the second PE130 is in a failed state, the sub-interface in the first PE120 corresponding to the failed sub-interface of the second PE130 corresponds to The routing information will be advertised in the network by the first functional component 210 in the first PE120.
  • the first functional component 210 in the first PE 120 will not advertise the routing information of the sub-interface of the first PE 120 in the network;
  • the PE 130 determines that the main interface of the first PE 120 is in a failed state, and the first functional component 210 in the second PE 130 will not advertise the routing information of the sub-interface of the second PE 130 in the network.
  • the network topology and application scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • topology shown in FIG. 1 does not constitute a limitation on the embodiments of the present application, and may include more or less components than shown, or combine some components, or different components layout.
  • FIG. 2 is a flowchart of an information processing method provided by an embodiment of the present application.
  • the information processing method is applied to a first device (for example, the first PE 120 in the network topology shown in FIG. 1 ).
  • a device and a second device (for example, the second PE130 in the network topology shown in FIG. 1 ) have a dual-homing relationship and are in the same Ethernet segment (Ethernet Segment, ES).
  • the first device is provided with a first sub-interface
  • the second device is provided with a second sub-interface corresponding to the first sub-interface.
  • the information processing method includes but is not limited to the following steps:
  • Step S100 in the case of determining that the second sub-interface is in a failed state and the main interface to which the second sub-interface belongs is in a normal state, advertise the first routing information corresponding to the first sub-interface to the network, so that the third device according to the first sub-interface is in a normal state.
  • a routing information sends the data packet to the first sub-interface.
  • the first routing information corresponding to the first sub-interface may be an IP address, a B-MAC address, or other custom identifiers that can uniquely mark the first sub-interface on the data plane. It is not specifically limited.
  • the first device determines that the second sub-interface of the second device is in a failed state and the main interface to which the second sub-interface belongs is in a normal state, it means that other sub-interfaces of the second device can still work normally, but the second sub-interface is the only one. Data packets can no longer be forwarded. However, since all sub-interfaces of the second device are associated with the B-MAC entry bound to the same main interface, the B-MAC entry cannot be simply due to the failure of the second sub-interface. Therefore, if the third device still sends a data packet according to the routing information corresponding to the main interface, the data packet will be distributed to the second sub-interface of the second device, which will cause packet loss.
  • the first device determines that the second sub-interface is in a failed state and the main interface to which the second sub-interface belongs is in a normal state
  • the first routing information corresponding to the first sub-interface is advertised in the network.
  • the third device After receiving the first routing information, the third device can accurately send the data packet to the first routing information according to the first routing information.
  • a sub-interface ensures the normal forwarding of data packets by the first sub-interface of the first device; in addition, since the second device does not publish routing information corresponding to the second sub-interface, it also avoids the need for data packets due to Packet loss caused by being sent to the second sub-interface of the second device.
  • the packet loss result can be optimized through other nodes through the egress link protection technology.
  • a long-time bypass process will still waste network bandwidth.
  • this embodiment can quickly cancel the bypass process on the data packet before the second sub-interface is restored. Thereby, network bandwidth resources can be saved.
  • the technical effect of solving the packet loss problem and the technical effect of removing the bypassing of data packets may be based on the same technical means, and whether to implement bypassing can be determined based on whether it is combined with other technical means. line processing.
  • the first device only announces the first sub-interface corresponding to the first sub-interface in the network when it determines that the second sub-interface is in a failed state and the main interface to which the second sub-interface belongs is in a normal state. Routing information, that is to say, when both the first device and the second device are in normal working state, the first device does not need to advertise the first routing information corresponding to the first sub-interface. In this state, the first device only sends the first routing information to the first sub-interface corresponding to the second sub-interface, and does not send routing information to all sub-interfaces.
  • the routing information corresponding to the sub-interface can therefore reduce the number of routing information published for the sub-interface in the network, thereby reducing the routing pressure on the network, especially under normal conditions (that is, before any sub-interface on the ES fails).
  • No routing information specific to any sub-interface on the ES eg, routing information having the same nature as the first routing information
  • is advertised outside the ES eg, a third device.
  • the first routing information includes a common routing part and a unique routing part
  • the common routing part corresponds to the routing information of the main interface to which the first sub-interface belongs
  • the unique routing part is used to distinguish the routing information belonging to the main interface. subinterface.
  • the first routing information may be composed of a shared routing part in a high position and a unique routing part in a low position, wherein the shared routing part may be an IPv6 prefix or other custom that can uniquely mark the host on the data plane.
  • the identifier of the interface, etc., the bit length of the common routing part can be appropriately selected according to the actual application; and the unique routing part can be the globally unique Ethernet virtual private network global discriminator (EVPN Global Discreminator, EGD), local Discriminator or other custom identifiers that can be used to distinguish sub-interfaces, etc.
  • EGD globally unique Ethernet virtual private network global discriminator
  • the bit length of the unique routing part can be appropriately selected according to the actual application; the specific content of the common routing part and the unique routing part can be based on the actual application.
  • the first routing information is an IPv6 address
  • the upper 104 bits of the first routing information are the shared routing part
  • the shared routing part is an IPv6 prefix
  • the lower 24 bits of the first routing information are the unique routing part
  • the unique routing part is an EGD.
  • the unique routing part may be EGD, and the EGD can uniquely identify the sub-interface.
  • the first routing information corresponding to the first sub-interface is composed of the above-mentioned shared routing part and unique routing part.
  • the corresponding routing information contains a common routing part but not a unique routing part.
  • the first routing information corresponding to the first sub-interface and the routing information corresponding to the main interface are both IP routes of the IP-VRF instance.
  • the unique routing part of the first routing information corresponding to the first sub-interface only needs to contain a marker that can uniquely identify the first sub-interface.
  • the interface identifier of a sub-interface, etc., and the specific value of the interface identifier can be appropriately selected according to the actual application situation (for example, the VLAN identification information of the sub-interface can be selected, etc.), this embodiment does not apply to this.
  • the EGD uses other fields for transmission (such as the VNI field) so that the unique part of the first routing information corresponding to the first sub-interface does not need to include EGD
  • the first routing information based on the interface distinguisher can be used, which can have It is beneficial to make the routing information corresponding to the main interface have more valid bits, so it is more suitable for the application of devices that do not support IPv6.
  • the information processing method may further include, but is not limited to, the following steps:
  • Step S200 when receiving the route revocation message sent by the second device, and the route revocation message is only for the second sub-interface, it is determined according to the route revocation message that the second sub-interface is in an invalid state and the address to which the second sub-interface belongs.
  • the primary interface is in normal state.
  • step S100 if the first device receives the route revocation message sent by the second device, and the route revocation message is only for the second sub-interface, the first device may determine the second sub-interface The interface is in a failed state. At this time, if the route corresponding to the main interface to which the second sub-interface belongs has not been revoked, that is, the main interface to which the second sub-interface belongs is in a normal state, so it can trigger the execution of advertisements in the network and the first interface. An operation of the first routing information corresponding to a sub-interface.
  • route revocation message when the sub-interface or the main interface of the PE in the network fails, the route revocation message will be flooded in the network.
  • route revocation packets There are two types of route revocation packets, namely, route revocation packets corresponding to routes on the main interface (such as RT-1 per ES routes) and routes corresponding to routes on sub-interfaces (such as RT-1 per EVI routes).
  • Revocation message in which, when the sub-interface of the PE fails, the PE will flood the network with the route revocation message corresponding to the sub-interface; when the main interface of the PE fails, the PE will flood the network corresponding to the sub-interface.
  • the first device When the first device receives the route revocation message corresponding to the sub-interface (that is, the route revocation message is only for the second sub-interface), it means that the second device only has the second sub-interface in a failed state, and the second device's The other sub-interfaces are in a normal working state, so the first device can determine that the second sub-interface is in a failed state and the main interface to which the second sub-interface belongs is in a normal state.
  • the first device receives a route revocation message corresponding to the main interface (that is, the route revocation message is directed to the main interface), it means that the main interface of the second device and all sub-interfaces subordinate to the main interface are in an invalid state.
  • the first device can determine that the main interface itself on the second device has failed. It should be noted that when the main interface on the second device itself has failed, that is, the second device does not work on the main interface in the network, at this time, the starting node (such as the third device) that sends the data packet will communicate with the main interface. The routing information corresponding to the main interface of the second device is deleted. Therefore, the starting node that sends the data packet will not select the second device as the destination node, nor will the second device be counted in the forwarding path. Therefore, the first The device does not need to trigger and execute the operation of advertising the first routing information corresponding to the first sub-interface in the network, which does not cause the problem of data packet detour or packet loss.
  • the route revocation message in this embodiment may be any route message that can announce the failure state of the corresponding first routing information, and does not necessarily need to be related to the MP_UNREACH_NLRI attribute in BGP.
  • the advertising of the first routing information corresponding to the first sub-interface in the network in step S100 may include, but is not limited to, the following steps:
  • a Border Gateway Protocol (BGP) routing packet is flooded in the network to advertise the first routing information corresponding to the first sub-interface, wherein the BGP routing packet includes the first routing information and a device used to identify the first device
  • the first device identification, the first device identification is used to make the third device use the first segment identification (Segment ID, SID) list to carry the first routing information and the first device identification under the situation of sending a data message, and,
  • the processing logic position of the first routing information in the first SID list is after the processing logic position identified by the first device in the first SID list.
  • the first device identifier is an address used to uniquely identify the first device, and its value may be appropriately selected according to actual application conditions, which is not specifically limited in this embodiment.
  • the first device floods the first routing information corresponding to the first sub-interface in the network
  • the interior gateway protocol Interior Gateway Protocol, IGP
  • IGP Interior Gateway Protocol
  • the core routers in the network such as the first core router 150 and the second core router 160 in FIG. 1
  • the BGP routing message is used to flood the first routing information corresponding to the first sub-interface, so as to prevent the core router from perceiving the first routing information.
  • the BGP routing packet when used to flood the first routing information corresponding to the first sub-interface, the BGP routing packet may also carry a first device identifier for identifying the first device.
  • the third device After the third device receives the BGP routing packet, the third device can obtain the first device identifier corresponding to the first device and the first routing information corresponding to the first sub-interface.
  • the third device can use the first SID list to carry the first routing information and the first device identifier, and the first SID list , the SID where the first routing information is located is in the inner layer of the SID where the first device identifier is located.
  • the first routing information is hidden in the segment routing header (Segment Routing Header, SRH) corresponding to the first SID list, and the core router perceives Without the first routing information, the first routing information will be exposed only after the data packet reaches the first device, that is, the first device does not need to notify the core when flooding the first routing information Therefore, the first device can use the BGP routing message to flood the first routing information corresponding to the first sub-interface, so as to reduce the routing pressure on the core router and achieve the purpose of light weight.
  • Segment Routing Header Segment Routing Header
  • the first routing information may be routing information in a global routing table, a certain IP-VRF instance, or a certain MAC-VRF instance. Meanwhile, the first routing information and the routing information of the main interface are routing information in the same routing table.
  • the BGP routing packet may further include bandwidth information, where the bandwidth information is used to enable the third device to determine the first device identifier according to the bandwidth information.
  • the bandwidth information in the BGP routing packet reflects the bandwidth processing capability of the device that advertises the BGP routing packet. Therefore, after the third device receives the BGP routing packet including the bandwidth information from each device, when the third device sends the data packet, the third device may firstly communicate between multiple devices corresponding to the target routing information. , load sharing is performed proportionally according to the bandwidth information advertised by these devices, and then the final device identifier is determined according to the load sharing result, and then the data packet is forwarded with the determined final device identifier as the destination address.
  • the third device After the third device receives the BGP routing packet carrying the first routing information and bandwidth information, when the third device needs to When the routing information forwards the data packet, the third device will firstly perform proportional transmission between the first device and the second device corresponding to the first routing information according to the bandwidth information advertised by the first device and the second device.
  • Load sharing Since the first device has the largest bandwidth processing capability, the result of load sharing will be that the first device shares a larger amount of data forwarding. Therefore, the third device will select the first device identifier used to identify the first device. The data packet is forwarded to the first device as the destination address.
  • the information processing method may further include, but is not limited to, the following steps:
  • Step S300 receiving a first data packet sent by a third device, wherein the first data packet carries first routing information
  • Step S400 forward the first data packet to the first sub-interface according to the first routing information and the local forwarding entry.
  • the third device can send the first routing information to the third device according to the first routing information.
  • a device sends a first data packet, and the first data packet carries the first routing information. After the first device receives the first data packet, it can forward the first data packet to the first sub-interface according to the first routing information in the first data packet and the local forwarding entry. Thus, the service transmission from the third device to the first device is realized.
  • the packet format of the first data packet may have different types, for example, the first data packet may be an SRv6 packet type or a Multi-Protocol Label Switching (MPLS) packet type etc., which are not specifically limited in this embodiment.
  • the local forwarding table entries may also have different types. For example, when the first data packet is an SRv6 packet type, the local forwarding table entry The entry is the local segment identifier forwarding entry, and when the first data packet is of the MPLS packet type, the local forwarding entry is the label forwarding entry.
  • the first data packet sent by the third device may also carry first MAC information, where the first MAC information is the destination node that the first data packet needs to reach (for example, FIG. 1 ).
  • the information processing method may also include but not limited to the following steps:
  • the information constructs the first data message.
  • the first device will also send a second data packet to the third device, where the second data packet carries the first route information and second MAC information, the second MAC information is the MAC information of the user equipment (for example, the first CE110 in FIG. 1 ) (that is, the source MAC information of the user equipment).
  • the third device receives the second data packet After that, the relationship between the first routing information and the second MAC information can be learned and saved from the second data packet. Therefore, when the third device needs to send data to the user equipment (for example, the first CE110 in FIG.
  • the stored second MAC information can be obtained according to the destination address information (that is, the first MAC information), and the first device in the forwarding path can be obtained according to the relationship between the second MAC information and the first routing information address information (such as the first device identifier), and then the first data packet in the embodiment shown in FIG. 4 may be constructed according to the first MAC information and the first routing information.
  • the steps in this embodiment may be performed before step S100 is performed.
  • the third device may also replace the first routing information with the second routing information.
  • the first device also needs to determine, through the first MAC address, that the egress of the first data packet is the first sub-interface.
  • step S400 may include but is not limited to the following steps:
  • Step S410 obtaining the first routing information from the destination address field of the first data packet
  • Step S420 when it is determined that the next hop is the first sub-interface according to the first routing information and the local forwarding entry, the first data packet is forwarded to the first sub-interface.
  • the first device after the first device receives the first data packet from the third device, the first device first obtains the information of the destination address field in the first data packet, and then determines the information in the destination address field. Whether the information hits the local forwarding entry, when the information in the destination address field hits the local forwarding entry, the first data packet can be processed according to the relevant information recorded in the local forwarding entry. Therefore, in this embodiment, after receiving the first data packet, the first device first obtains the first routing information from the destination address field of the first data packet, and then determines whether the first routing information hits the local forwarding information.
  • the first data packet can be forwarded to the first sub-interface.
  • the sub-interface implements the related processing of the first data packet.
  • the destination MAC address of the first data packet must also be determined. to proceed. For example, when the unique part of the first routing information is EGD, and the ESI has multiple sub-interfaces in the EVPN instance identified by the EGD, since these sub-interfaces use the same first routing information, it is necessary to additionally pass the destination MAC chooses between these subinterfaces.
  • step S400 may also be Including but not limited to the following steps:
  • Step S430 obtaining the current segment identifier from the segment identifier list in the first SRH;
  • Step S440 when the current segment is identified as the first routing information, and the next hop is determined as the first sub-interface according to the first routing information and the local forwarding entry, the first data packet is forwarded to the first sub-interface.
  • the embodiment shown in FIG. 6 and the above-mentioned embodiment shown in FIG. 5 are parallel technical solutions, and the difference between the two is that in the above-mentioned embodiment shown in FIG. 5 , the first data The message is not encapsulated with SRH, and the first routing information is filled in the destination address field of the first data message; in the embodiment shown in FIG. 6 , the first data message is encapsulated with the first SRH, and the first route Information is populated in the first SRH.
  • the first device after the first device receives the first data packet from the third device, the first device first determines that the first data packet contains Whether the information in the destination address field matches the device, when matching, the first device will obtain the current segment identifier from the segment identifier list of the first SRH, and then judge whether the current segment identifier hits the local forwarding entry, if the current segment identifier The identification hits the local forwarding entry, that is, the first data packet can be processed relatedly according to the relevant information recorded in the local forwarding entry.
  • the first device when the first device determines that the information in the destination address field in the first data packet matches its own device, the first device obtains the current Segment identifier, when the current segment identifier is the first routing information, and it is determined that the first routing information hits the local forwarding entry, and the next hop is determined to be the first sub-interface according to the hit local forwarding entry, that is, The first data packet may be forwarded to the first sub-interface to implement related processing of the first data packet.
  • an embodiment of the present application also provides a node, the node includes: a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor and memory may be connected by a bus or otherwise.
  • the memory can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.
  • the memory may optionally include memory located remotely from the processor, which may be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the node in this embodiment may be applied as the first PE 120 or the second PE 130 in the network topology of the embodiment shown in FIG. 1 , and the node in this embodiment is the same as the one in the embodiment shown in FIG.
  • the first PE 120 or the second PE 130 in the network topology has the same inventive concept, and therefore these embodiments have the same implementation principle and technical effect, which will not be described in detail here.
  • the non-transitory software programs and instructions required to implement the information processing method of the above embodiment are stored in the memory, and when executed by the processor, the information processing method in the above embodiment is executed, for example, the above-described FIG. 2 is executed.
  • node embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor or controller, for example, by the above-mentioned Executed by a processor in the node embodiment, the above-mentioned processor can execute the information processing method in the above-mentioned embodiment, for example, execute the above-described method step S100 in FIG. 2 , method step S200 in FIG. method steps S300 to S400 in FIG. 5 , method steps S410 to S420 in FIG. 5 , and method steps S430 to S440 in FIG. 6 .
  • the embodiments of the present application of the present invention include: for a first device and a second device that have a dual homing relationship, and the first device is provided with a first sub-interface, and the second device is provided with a second sub-interface corresponding to the first sub-interface,
  • the first device determines that the second sub-interface of the second device is in a failed state and the main interface to which the second sub-interface belongs is in a normal state
  • the first device advertises the first route corresponding to the first sub-interface in the network information, so that the third device sends the data packet to the first sub-interface according to the first routing information.
  • the first device when the first device determines that the second sub-interface of the second device is in an invalid state and the main interface to which the second sub-interface belongs is still in a normal state, the first device notifies the network with The first routing information corresponding to the first sub-interface enables the third device to send the data packet to the first sub-interface of the first device according to the first routing information, thereby solving the problem of a certain sub-interface of the device in the related art.
  • the problem of data packet loss caused by failure occurs.
  • Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and can include any information delivery media, as is well known to those of ordinary skill in the art .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种信息处理方法、节点及计算机可读存储介质,其中信息处理方法应用于设置有第一子接口且与第二设备存在双归属关系的第一设备,第二设备设置有与第一子接口对应的第二子接口。该信息处理方法包括:在确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态的情况下,在网络中通告与第一子接口对应的第一路由信息,使得第三设备根据第一路由信息将数据报文发送至第一子接口(S100)。

Description

信息处理方法、节点及计算机可读存储介质
相关申请的交叉引用
本申请基于申请号为202011479889.8、申请日为2020年12月15日的中国专利申请提出,并要求该中国专利申请的优先权,该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信技术领域,尤其涉及一种信息处理方法、节点及计算机可读存储介质。
背景技术
在运营商骨干桥接技术以太虚拟专用网(Provider Backbone Bridge Ethernet Virtual Private Network,PBB EVPN)中,以太分段标识符(Ethernet Segment Identifier,ESI)都是基于运营商边缘路由器(Provider Edge,PE)的主接口进行配置的,对应的,在数据面代表该ESI的骨干媒体存取控制地址(Backbone Media Access Control Address,B-MAC),也是由该主接口所绑定的,但实际作为EVPN的附件电路(Attachment Circuit,AC),往往都不是该主接口本身,而是该主接口的子接口。
由于在数据面代表ESI的B-MAC条目由主接口所绑定,因此,该主接口的其它子接口也依赖于该B-MAC条目,而且,针对同一主接口的不同子接口之间,子接口失效事件常常是独立发生的,比如,当其中一个子接口被管理员关闭(Shutdown)时,其它子接口仍然可以正常转发报文,因此,当存在个别子接口失效时,无法因为该子接口的失效而撤销相应的B-MAC条目,所以,当数据报文的目的用户MAC(Customer MAC,C-MAC)被关联到该B-MAC条目时,该数据报文仍然会被负荷分担到发生子接口失效的PE节点上,从而造成丢包的问题。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种信息处理方法、节点及计算机可读存储介质,能够解决相关技术中由于PE的子接口失效而导致的数据报文绕行或者丢包的问题。
第一方面,本申请实施例提供了一种信息处理方法,应用于第一设备,所述第一设备与第二设备存在双归属关系,所述第一设备设置有第一子接口,所述第二设备设置有与所述第一子接口对应的第二子接口,所述方法包括:
在确定所述第二子接口处于失效状态且所述第二子接口所归属的主接口处于正常状态的情况下,在网络中通告与所述第一子接口对应的第一路由信息,使得第三设备根据所述第一路由信息将数据报文发送至所述第一子接口。
第二方面,本申请实施例还提供了一种节点,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现如上第一方面所述的信息处理方法。
第三方面,本申请实施例还提供了一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令用于执行如上所述的信息处理方法。
本申请的其它特征和优点将在随后的说明书中阐述,并且,部分地从说明书中变得显而 易见,或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解,并且构成说明书的一部分,与本申请的实施例一起用于解释本申请的技术方案,并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的用于执行信息处理方法的网络拓扑的示意图;
图2是本申请一个实施例提供的信息处理方法的流程图;
图3是本申请另一实施例提供的信息处理方法的流程图;
图4是本申请另一实施例提供的信息处理方法的流程图;
图5是本申请另一实施例提供的信息处理方法中转发数据报文至子接口的具体流程图;以及
图6是本申请另一实施例提供的信息处理方法中转发数据报文至子接口的具体流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处所描述的具体实施例仅用以解释本申请,并不用于限定本申请。
需要说明的是,虽然在装置示意图中进行了功能模块划分,在流程图中示出了逻辑顺序,但是在某些情况下,可以以不同于装置中的模块划分,或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
本申请提供了一种信息处理方法、节点及计算机可读存储介质,针对存在双归属关系的第一设备与第二设备,并且第一设备设置有第一子接口,第二设备设置有与第一子接口对应的第二子接口,在第一设备确定第二设备的第二子接口处于失效状态但第二子接口所归属的主接口仍然处于正常状态的情况下,第一设备在网络中通告与该第一子接口对应的第一路由信息,使得第三设备能够根据该第一路由信息将数据报文发送至第一设备的第一子接口,从而解决了相关技术中由于设备的某个子接口出现失效而导致的数据报文丢包的问题。
下面结合附图,对本申请实施例作进一步阐述。
如图1所示,图1是本申请一个实施例提供的用于执行信息处理方法的网络拓扑的示意图。在图1的示例中,该网络拓扑包括第一用户网络边缘设备(Customer Edge,CE)110、第一PE120、第二PE130、第三PE140、第一核心路由器150和第二核心路由器160。其中,第一CE110双归属于第一PE120和第二PE130,第一PE120和第二PE130均连接到第一核心路由器150,第一核心路由器150、第二核心路由器160和第三PE140依次连接。
在图1的示例中,第一PE120、第二PE130和第三PE140均包括有一个第一功能组件210和两个第二功能组件220,其中,第一功能组件210与每一个第二功能组件220连接。另外,第一PE120还包括有第一主接口121、第一子接口122和第三子接口123,第一子接口122和第三子接口123归属于第一主接口121,第一PE120中的两个第二功能组件220对应绑定第一子接口122及第三子接口123;第二PE130还包括有第二主接口131、第二子接口132和第四子接口133,第二子接口132和第四子接口133归属于第二主接口131,第二PE130中的两个第二功能组件220对应绑定第二子接口132及第四子接口133。第一子接口122与第二子 接口132基于第一PE120和第二PE130的双归属关系而相关联,第三子接口123与第四子接口133基于第一PE120和第二PE130的双归属关系而相关联。
值得注意的是,第一子接口122与第二子接口132可以接收具有相同的虚拟局域网(Virtual Local Area Network,VLAN)封装的报文,第三子接口123与第四子接口133可以接收具有相同的VLAN封装的报文。
在各个PE中,分别为主接口以及各个子接口分配有对应的路由信息,该路由信息可以为网际互连协议(Internet Protocol,IP)地址、媒体存取控制地址(Media Access Control Address,MAC)地址或者以太分段标识符(Ethernet Segment Identifier,ESI)等,本实施例对此并不作具体限定。值得注意的是,由于设备之间的双归属关系而相关联的多个子接口之间,例如第一PE120的第一子接口122和第二PE130的第二子接口132之间,具有相同的路由信息。
第二功能组件220是根据C-MAC转发数据报文的业务实例,其中,第二功能组件220可以采用VXLAN、PBB、MPLS、SRv6等封装格式在各PE之间转发数据报文,此时,可以分别称第二功能组件220为VXLAN EVPN实例、PBB EVPN实例、MPLS EVPN实例和SRv6EVPN实例等。
第一功能组件210用于承载业务实例(对应于第二功能组件220),另外,第一功能组件210可以在网络中通告与主接口对应的路由信息或者与子接口对应的路由信息。需要说明的是,当存在双归属关系的第一PE120和第二PE130均正常工作时,第一PE120中的第一功能组件210和第二PE130中的第一功能组件210均只会在网络中通告与主接口对应的路由信息;当第一PE120中的某一个子接口处于失效状态时,第二PE130中的与第一PE120的失效子接口对应的子接口所对应的路由信息,才会被第二PE130中的第一功能组件210在网络中进行通告;当第二PE130中的某一个子接口处于失效状态时,第一PE120中的与第二PE130的失效子接口对应的子接口所对应的路由信息,才会被第一PE120中的第一功能组件210在网络中进行通告。值得注意的是,如果第一PE120确定第二PE130的主接口处于失效状态,第一PE120中的第一功能组件210并不会在网络中通告第一PE120的子接口的路由信息;如果第二PE130确定第一PE120的主接口处于失效状态,第二PE130中的第一功能组件210也不会在网络中通告第二PE130的子接口的路由信息。
本申请实施例描述的网络拓扑以及应用场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域技术人员可知,随着网络拓扑的演变和新应用场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
本领域技术人员可以理解的是,图1中示出的拓扑结构并不构成对本申请实施例的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
基于上述网络拓扑的结构,提出本申请的信息处理方法的各个实施例。
如图2所示,图2是本申请一个实施例提供的信息处理方法的流程图,该信息处理方法应用于第一设备(例如图1所示的网络拓扑中的第一PE120),该第一设备与第二设备(例如图1所示的网络拓扑中的第二PE130)存在双归属关系,并处于同一以太网段(Ethernet Segment,ES),该第一设备设置有第一子接口,该第二设备设置有与该第一子接口对应的第二子接口。该信息处理方法包括但不限于有以下步骤:
步骤S100,在确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态 的情况下,向网络通告与第一子接口对应的第一路由信息,使得第三设备根据第一路由信息将数据报文发送至第一子接口。
需要说明的是,与第一子接口对应的第一路由信息,可以为IP地址、B-MAC地址或者其他自定义的能够在数据面唯一标记第一子接口的标识符,本实施例对此并不作具体限定。
当第一设备确定第二设备的第二子接口处于失效状态,并且第二子接口所归属的主接口处于正常状态,说明了第二设备的其他子接口仍然能够正常工作,只是第二子接口不能再对数据报文进行转发,但是,由于第二设备的所有子接口都关联到同一个主接口所绑定的B-MAC条目,而该B-MAC条目无法仅因为第二子接口的失效而被撤销,因此,如果第三设备仍然按照主接口所对应的路由信息发送数据报文,则该数据报文会被分担到第二设备的第二子接口,从而会造成丢包的问题。为了解决上述问题,并且不影响第一设备的第一子接口对数据报文的正常转发,在第一设备确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态的情况下,将与第一子接口对应的第一路由信息在网络中进行通告,当第三设备接收到该第一路由信息后,可以根据该第一路由信息将数据报文准确的发送至第一子接口,保证了第一设备的第一子接口对数据报文的正常转发;此外,由于第二设备并不会发布与第二子接口对应的路由信息,因此还避免了由于数据报文被发送到第二设备的第二子接口而导致的丢包问题。
值得注意的是,当出现由于第三设备将数据报文发送到已经失效的第二子接口而导致出现丢包问题的情况,可以通过出口链路保护技术将丢包结果优化为经过其它节点进行绕行的结果,但是,长时间的绕行处理仍然会对网络带宽造成浪费,在这种情况下,本实施例可以在第二子接口恢复之前,快速解除对数据报文的绕行处理,从而可以节省网络带宽资源。对于本实施例来说,解决丢包问题的技术效果和解除对数据报文进行绕行的技术效果,可以以相同的技术手段作为基础,并基于是否与其它技术手段相结合而确定是否实现绕行处理。
值得注意的是,第一设备是在确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态的情况下,才会在网络中通告与第一子接口对应的第一路由信息,即是说,当第一设备和第二设备均处于正常工作状态下,第一设备并不需要通告与第一子接口对应的第一路由信息,此外,在第二子接口处于失效状态下,第一设备仅针对与该第二子接口对应的第一子接口发送第一路由信息,并不会针对全部子接口均发送路由信息,而且,第二设备也不会通告与第二子接口对应的路由信息,因此,能够降低网络中针对子接口的路由信息的发布数量,从而能够降低网络的路由压力,尤其是在常态(即该ES上的任何子接口发生故障之前)下,并没有向该ES之外(比如第三设备)发布特定于该ES上的任何子接口的路由信息(如与第一路由信息具有相同性质的路由信息)。
在一实施例中,第一路由信息包括共有路由部分和独有路由部分,共有路由部分对应于第一子接口所归属的主接口的路由信息,独有路由部分用于区分归属于主接口的子接口。
在一实施例中,第一路由信息可以由处于高位的共有路由部分和处于低位的独有路由部分构成,其中,共有路由部分可以为一个IPv6前缀或者其他自定义的能够在数据面唯一标记主接口的标识符等,共有路由部分的位长可以根据实际应用情况而适当选择;而独有路由部分则可以为网络中全局唯一的以太虚拟私有网络全局区分符(EVPN Global Discreminator,EGD)、本地区分符或者其他自定义的能够用于区分子接口的标识符等,独有路由部分的位长可以根据实际应用情况而适当选择;共有路由部分和独有路由部分的具体内容均可以根据实 际应用情况而适当选择,本实施例对此并不作具体限定。例如,当第一路由信息为IPv6地址时,该第一路由信息的高104位为共有路由部分,该共有路由部分为一个IPv6前缀,而第一路由信息的低24位则为独有路由部分,该独有路由部分为一个EGD。
值得注意的是,当对应于同一个第一路由信息(如ESI)的同一EVPN实例中只有一个子接口,此时独有路由部分可以为EGD,该EGD能够唯一标识该子接口。
需要说明的是,当第一设备的第一功能组件210承载SRv6EVPN实例,则第一子接口所对应的第一路由信息由上述的共有路由部分和独有路由部分构成,此时,主接口所对应的路由信息包含共有路由部分而不包含独有路由部分。当第一设备的第一功能组件承载IP-VRF实例,则第一子接口所对应的第一路由信息和主接口所对应的路由信息,均为该IP-VRF实例的I P路由,此时,第一子接口所对应的第一路由信息的独有路由部分,只需要包含能够唯一标识第一子接口的标记符即可,例如可以为能够在第一设备所属的ES内唯一标识该第一子接口的接口区分符等,而该接口区分符的具体取值,均可以根据实际应用情况而进行适当选择(比如,可以选取该子接口的VLAN标识信息等),本实施例对此并不作具体限定。在EGD采用其它字段传输(比如VNI字段)从而使得第一子接口所对应的第一路由信息的独有部分不需要包含EGD的情况下,可以采用基于接口区分符的第一路由信息,能够有利于使主接口所对应的路由信息具有更多的有效位,从而更适用于不支持I Pv6的设备的应用。
另外,在一实施例中,如图3所示,该信息处理方法还可以包括但不限于有以下步骤:
步骤S200,当接收到由第二设备发送的路由撤销报文,并且路由撤销报文仅针对第二子接口,根据路由撤销报文确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态。
需要说明的是,在执行步骤S100之前,如果第一设备接收到由第二设备发送的路由撤销报文,并且该路由撤销报文仅针对第二子接口,则第一设备可以确定第二子接口处于失效状态,此时,如果与第二子接口所属的主接口对应的路由还没有被撤销,即第二子接口所归属的主接口处于正常状态,因此可以触发执行在网络中通告与第一子接口对应的第一路由信息的操作。
值得注意的是,当网络中的PE出现子接口失效或者主接口失效的情况,均会在网络中泛洪路由撤销报文。路由撤销报文包括有两种类型,分别为对应于主接口的路由(如RT-1 per ES路由)的路由撤销报文和对应于子接口的路由(如RT-1 per EVI路由)的路由撤销报文,其中,当PE的子接口失效,则该PE会在网络中泛洪对应于子接口的路由撤销报文;当PE的主接口失效,则该PE会在网络中泛洪对应于主接口的路由撤销报文和对应于子接口的路由撤销报文。当第一设备接收到对应于子接口的路由撤销报文(即路由撤销报文仅针对第二子接口)时,即说明第二设备仅有第二子接口处于失效状态,而第二设备的其他子接口均处于正常工作状态,因此,第一设备能够确定第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态。当第一设备接收到对应于主接口的路由撤销报文(即路由撤销报文针对主接口)时,即说明第二设备的主接口以及该主接口下属的全部子接口均处于失效状态,因此,第一设备能够确定第二设备上主接口自身已经失效。需要说明的是,当第二设备上主接口自身已经失效,即第二设备在网络中对主接口不起作用,此时,发送数据报文的起始节点(比如第三设备)会将与第二设备的主接口对应的路由信息删除,因此,发送数据报文的起始节点不会选择第二设备作为目的节点,也不会将第二设备计算在转发路径之中,所以,第一设 备不需要触发执行在网络中通告与第一子接口对应的第一路由信息的操作,这并不会引起数据报文绕行或者丢包的问题。
需要说明的是,本实施例中的路由撤销报文,可以是能够通告相应第一路由信息的失效状态的任何路由报文,并不一定需要与BGP中的MP_UNREACH_NLRI属性相关。
另外,在一实施例中,步骤S100中的在网络中通告与第一子接口对应的第一路由信息,可以包括但不限于有以下步骤:
在网络中泛洪边界网关协议(Border Gateway Protocol,BGP)路由报文以通告与第一子接口对应的第一路由信息,其中,BGP路由报文包括第一路由信息和用于标识第一设备的第一设备标识,第一设备标识用于使第三设备在发送数据报文的情况下,利用第一段标识(Segment ID,SID)列表携带第一路由信息和第一设备标识,并且,第一路由信息于第一SID列表中的处理逻辑位置在第一设备标识于第一SID列表中的处理逻辑位置的后面。
需要说明的是,第一设备标识是用于唯一标识第一设备的地址,其取值可以根据实际应用情况而进行适当的选择,本实施例对此并不作具体限定。
需要说明的是,当第一设备(如图1中的第一PE120)在网络中泛洪与第一子接口对应的第一路由信息,例如采用内部网关协议(Interior Gateway Protocol,IGP)泛洪该第一路由信息,则网络中的核心路由器(如图1中的第一核心路由器150和第二核心路由器160)都会感知到该第一路由信息,此时,会增加核心路由器的路由压力。为了避免核心路由器感知到该第一路由信息而达到轻量化的目的,本实施例中利用BGP路由报文泛洪第一子接口对应的第一路由信息,避免核心路由器感知到第一路由信息。
需要说明的是,在利用BGP路由报文泛洪第一子接口所对应的第一路由信息时,还可以在该BGP路由报文中携带用于标识第一设备的第一设备标识。当第三设备接收到该BGP路由报文后,第三设备能够获取到第一设备所对应的第一设备标识和第一子接口所对应的第一路由信息。当第三设备需要向第一设备的第一子接口发送数据报文,第三设备可以利用第一SID列表携带该第一路由信息和该第一设备标识,并且,在该第一SID列表中,第一路由信息所在的SID在第一设备标识所在的SID的内层。因此,在该数据报文从第三设备传输至第一设备的过程中,第一路由信息被隐藏在与第一SID列表对应的分段路由头(Segment Routing Header,SRH)中,核心路由器感知不到该第一路由信息,仅当该数据报文到达第一设备后,第一路由信息才会暴露出来,即是说,第一设备在泛洪第一路由信息时,不需要通告给核心路由器,因此,第一设备可以利用BGP路由报文泛洪第一子接口所对应的第一路由信息,减轻核心路由器的路由压力,达到轻量化的目的。
需要说明的是,采用BGP路由报文泛洪第一路由信息时,第一路由信息可以是全局路由表、某个IP-VRF实例或某个MAC-VRF实例中的路由信息。同时,第一路由信息与主接口的路由信息是同一路由表中的路由信息。
需要说明的是,BGP路由报文中还可以包括有带宽信息,该带宽信息用于使第三设备根据带宽信息确定第一设备标识。
需要说明的是,BGP路由报文中的带宽信息,体现了通告该BGP路由报文的设备的带宽处理能力。因此,在第三设备接收到来自各个设备的包括有带宽信息的BGP路由报文后,当第三设备发送数据报文时,第三设备可以先在与目标路由信息对应的多个设备之间,按照这些设备所通告的带宽信息按比例进行负荷分担,而后根据负荷分担结果确定最终的设备标识, 接着,以该确定的最终的设备标识作为目的地址转发数据报文。例如,假设第一设备的带宽信息表示第一设备的带宽处理能力最大,在第三设备接收到携带有第一路由信息和带宽信息的BGP路由报文后,当第三设备需要根据该第一路由信息进行数据报文的转发时,第三设备会先在与该第一路由信息对应的第一设备和第二设备之间,按照第一设备和第二设备所通告的带宽信息按比例进行负荷分担,由于第一设备的带宽处理能力最大,因此,负荷分担的结果会是第一设备分担更大的数据转发量,所以,第三设备会选择用于标识第一设备的第一设备标识作为目的地址而向第一设备转发数据报文。
另外,在一实施例中,如图4所示,该信息处理方法还可以包括但不限于有以下步骤:
步骤S300,接收由第三设备发送的第一数据报文,其中,第一数据报文携带第一路由信息;
步骤S400,根据第一路由信息和本地的转发表项将第一数据报文转发至第一子接口。
需要说明的是,当第一设备在网络中通告与第一子接口对应的第一路由信息,而第三设备接收到该第一路由信息后,第三设备可以根据该第一路由信息向第一设备发送第一数据报文,并且,该第一数据报文携带有该第一路由信息。当第一设备接收到该第一数据报文后,即可以根据该第一数据报文中的第一路由信息和本地的转发表项,将该第一数据报文转发至第一子接口,从而实现了从第三设备到第一设备的业务传输。
需要说明的是,第一数据报文的报文格式可以有不同的类型,例如,第一数据报文可以为SRv6报文类型或者多协议标签交换(Multi-Protocol Label Switching,MPLS)报文类型等,本实施例对此并不作具体限定。值得注意的是,随着第一数据报文的报文格式的不同,本地的转发表项也可以有不同的类型,例如,当第一数据报文为SRv6报文类型时,本地的转发表项为本地段标识转发表项,而当第一数据报文为MPLS报文类型时,本地的转发表项则为标签转发表项。
另外,在一实施例中,由第三设备发送的第一数据报文,还可以携带有第一MAC信息,该第一MAC信息为第一数据报文所需要到达的目的节点(例如图1中的第一CE110)的MAC信息(即目的MAC信息),在这种情况下,在执行步骤S100之前,或者在执行步骤S300之前,该信息处理方法还可以包括但不限于有以下步骤:
向第三设备发送携带有第一路由信息和与第一MAC信息相同的第二MAC信息的第二数据报文,使得第三设备根据第二数据报文中的第一路由信息和第二MAC信息构建第一数据报文。
需要说明的是,在第三设备向第一设备发送第一数据报文之前,第一设备还会向第三设备发送第二数据报文,其中,该第二数据报文携带有第一路由信息和第二MAC信息,该第二MAC信息为用户设备(例如图1中的第一CE110)的MAC信息(即用户设备的源MAC信息),当第三设备接收到该第二数据报文后,能够从该第二数据报文中学习并保存第一路由信息和第二MAC信息之间的关系,因此,当第三设备需要向用户设备(例如图1中的第一CE110)发送数据报文时,可以根据目的地址信息(即第一MAC信息)得到所保存的第二MAC信息,并且可以根据第二MAC信息和第一路由信息之间的关系得到处于转发路径中的第一设备的地址信息(如第一设备标识),继而可以根据第一MAC信息和第一路由信息构建如图4所示实施例中的第一数据报文。
需要说明的是,当第一路由信息为IPv6地址时,由于IPv6地址具有最长匹配特性,因此,本实施例中的步骤可以在执行步骤S100之前执行。
需要说明的是,当根据第一路由信息可以获取到其它能够使该第一设备确定该第一数据报文所属的EVPN实例(即与第二功能组件对应的业务实例)的第二路由信息(比如VNI或者End.DT2U类型的SID)时,该第三设备也可以用该第二路由信息取代该第一路由信息。这种情况下,第一设备还需要通过该第一MAC地址确定该第一数据报文的出口为该第一子接口。
另外,在一实施例中,第一路由信息填充在第一数据报文的目的地址字段之中,在这种情况下,如图5所示,步骤S400可以包括但不限于有以下步骤:
步骤S410,从第一数据报文的目的地址字段中获取第一路由信息;
步骤S420,当根据第一路由信息和本地的转发表项确定下一跳为第一子接口,将第一数据报文转发至第一子接口。
需要说明的是,当第一设备接收到来自第三设备的第一数据报文后,第一设备首先获取该第一数据报文中的目的地址字段的信息,然后判断该目的地址字段中的信息是否命中本地的转发表项,当目的地址字段中的信息命中本地的转发表项,即可以根据本地的转发表项中所记载的相关信息对该第一数据报文进行相关的处理。因此,在本实施例中,第一设备在接收到第一数据报文后,先从第一数据报文的目的地址字段中获取第一路由信息,接着判断第一路由信息是否命中本地的转发表项,当确定第一路由信息命中了本地的转发表项,并且根据所命中的本地的转发表项确定下一跳为第一子接口,即可将该第一数据报文转发至第一子接口,实现对第一数据报文的相关处理。
需要说明的是,在某些情况下,要确定第一数据报文的下一跳为该第一子接口,除了根据该第一路由信息以外,还要根据该第一数据报文的目的MAC来进行。比如,在该第一路由信息的独有部分为EGD,且ESI在该EGD所标识的EVPN实例中存在多个子接口时,由于这些子接口采用了相同的第一路由信息,就必须额外通过目的MAC而在这些子接口之间进行选择。
另外,在一实施例中,当第一数据报文包括有第一SRH,并且该第一SRH携带有该第一路由信息,则在这种情况下,如图6所示,步骤S400还可以包括但不限于有以下步骤:
步骤S430,从第一SRH中的段标识列表获取当前段标识;
步骤S440,当当前段标识为第一路由信息,并且根据第一路由信息和本地的转发表项确定下一跳为第一子接口,将第一数据报文转发至第一子接口。
需要说明的是,如图6所示的实施例与上述如图5所示的实施例互为并列的技术方案,两者的区别在于:上述如图5所示的实施例中,第一数据报文没有封装SRH,并且第一路由信息填充在第一数据报文的目的地址字段之中;如图6所示的实施例中,第一数据报文封装有第一SRH,并且第一路由信息填充在第一SRH之中。
需要说明的是,在第一数据报文封装有第一SRH的情况下,当第一设备接收到来自第三设备的第一数据报文后,第一设备首先判断该第一数据报文中的目的地址字段的信息是否匹配本设备,当匹配时,第一设备会从第一SRH的段标识列表中获取当前段标识,然后判断该当前段标识是否命中本地的转发表项,如果当前段标识命中本地的转发表项,即可以根据本地的转发表项中所记载的相关信息对该第一数据报文进行相关的处理。因此,在本实施例中,当第一设备确定第一数据报文中的目的地址字段的信息匹配本设备,第一设备会从第一数据报文的第一SRH的段标识列表中获取当前段标识,当该当前段标识为第一路由信息,并且确定该第一路由信息命中了本地的转发表项,而且根据所命中的本地的转发表项确定下一跳为第一子接口,即可将该第一数据报文转发至第一子接口,实现对第一数据报文的相关处理。
另外,本申请的一个实施例还提供了一种节点,该节点包括:存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
存储器作为一种非暂态计算机可读存储介质,可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外,存储器可以包括高速随机存取存储器,还可以包括非暂态存储器,例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中,存储器可选包括相对于处理器远程设置的存储器,这些远程存储器可以通过网络连接至该处理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
需要说明的是,本实施例中的节点,可以应用为如图1所示实施例的网络拓扑中的第一PE120或第二PE130,本实施例中的节点和如图1所示实施例的网络拓扑中的第一PE120或第二PE130具有相同的发明构思,因此这些实施例具有相同的实现原理以及技术效果,此处不再详述。
实现上述实施例的信息处理方法所需的非暂态软件程序以及指令存储在存储器中,当被处理器执行时,执行上述实施例中的信息处理方法,例如,执行以上描述的图2中的方法步骤S100、图3中的方法步骤S200、图4中的方法步骤S300至S400、图5中的方法步骤S410至S420、图6中的方法步骤S430至S440。
以上所描述的节点实施例仅仅是示意性的,其中作为分离部件说明的单元可以是或者也可以不是物理上分开的,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外,本申请的一个实施例还提供了一种计算机可读存储介质,该计算机可读存储介质存储有计算机可执行指令,该计算机可执行指令被一个处理器或控制器执行,例如,被上述节点实施例中的一个处理器执行,可使得上述处理器执行上述实施例中的信息处理方法,例如,执行以上描述的图2中的方法步骤S100、图3中的方法步骤S200、图4中的方法步骤S300至S400、图5中的方法步骤S410至S420、图6中的方法步骤S430至S440。
本发明本申请实施例包括:针对存在双归属关系的第一设备与第二设备,并且第一设备设置有第一子接口,第二设备设置有与第一子接口对应的第二子接口,在第一设备确定第二设备的第二子接口处于失效状态且第二子接口所归属的主接口处于正常状态的情况下,第一设备在网络中通告与第一子接口对应的第一路由信息,使得第三设备根据第一路由信息将数据报文发送至第一子接口。根据本发明本申请实施例提供的方案,当第一设备确定第二设备的第二子接口处于失效状态而第二子接口所归属的主接口仍然处于正常状态,第一设备在网络中通告与该第一子接口对应的第一路由信息,使得第三设备能够根据该第一路由信息将数据报文发送至第一设备的第一子接口,从而解决了相关技术中由于设备的某个子接口出现失效而导致的数据报文丢包的问题。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器,如中央处理器、数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据 结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外,本领域普通技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据,并且可包括任何信息递送介质。
以上是对本申请的较佳实施进行了具体说明,但本申请并不局限于上述实施方式,熟悉本领域的技术人员在不违背本申请精神的前提下还可做出种种的等同变形或替换,这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (11)

  1. 一种信息处理方法,应用于第一设备,所述第一设备与第二设备存在双归属关系,所述第一设备设置有第一子接口,所述第二设备设置有与所述第一子接口对应的第二子接口,所述方法包括:
    在确定所述第二子接口处于失效状态且所述第二子接口所归属的主接口处于正常状态的情况下,向网络通告与所述第一子接口对应的第一路由信息,使得第三设备根据所述第一路由信息将数据报文发送至所述第一子接口。
  2. 根据权利要求1所述的方法,其中,所述第一路由信息包括共有路由部分和独有路由部分,所述共有路由部分对应于所述第一子接口所归属的主接口的路由信息,所述独有路由部分用于区分归属于所述主接口的子接口。
  3. 根据权利要求1所述的方法,还包括:
    当接收到由所述第二设备发送的路由撤销报文,并且所述路由撤销报文仅针对所述第二子接口,根据所述路由撤销报文确定所述第二子接口处于失效状态且所述第二子接口所归属的主接口处于正常状态。
  4. 根据权利要求1所述的方法,其中,所述向网络通告与所述第一子接口对应的第一路由信息,包括:
    在网络中泛洪边界网关协议BGP路由报文以通告与所述第一子接口对应的第一路由信息,其中,所述BGP路由报文包括所述第一路由信息和用于标识所述第一设备的第一设备标识,所述第一设备标识用于使所述第三设备在发送数据报文的情况下,利用第一段标识SID列表携带所述第一路由信息和所述第一设备标识,并且,所述第一路由信息于所述第一SID列表中的处理逻辑位置在所述第一设备标识于所述第一SID列表中的处理逻辑位置的后面。
  5. 根据权利要求4所述的方法,其中,所述BGP路由报文还包括带宽信息,所述带宽信息用于使所述第三设备根据所述带宽信息确定所述第一设备标识。
  6. 根据权利要求1至5任意一项所述的方法,还包括:
    接收由所述第三设备发送的第一数据报文,其中,所述第一数据报文携带所述第一路由信息;以及
    根据所述第一路由信息和本地的转发表项将所述第一数据报文转发至所述第一子接口。
  7. 根据权利要求6所述的方法,其中,所述第一数据报文还携带第一媒体存取控制地址MAC信息,在向网络通告与所述第一子接口对应的第一路由信息之前,或者在接收由所述第三设备发送的第一数据报文之前,所述方法还包括:
    向所述第三设备发送携带有所述第一路由信息和与所述第一MAC信息相同的第二MAC信息的第二数据报文,使得所述第三设备根据所述第二数据报文中的所述第一路由信息和所述第二MAC信息构建所述第一数据报文。
  8. 根据权利要求6所述的方法,其中,所述第一路由信息填充于所述第一数据报文的目的地址字段,所述根据所述第一路由信息和本地的转发表项将所述第一数据报文转发至所述第一子接口,包括:
    从所述第一数据报文的目的地址字段中获取所述第一路由信息;
    当根据所述第一路由信息和本地的转发表项确定下一跳为所述第一子接口,将所述第一 数据报文转发至所述第一子接口。
  9. 根据权利要求6所述的方法,其中,所述第一数据报文包括第一分段路由头SRH,所述第一SRH携带所述第一路由信息,所述根据所述第一路由信息和本地的转发表项将所述第一数据报文转发至所述第一子接口,包括:
    从所述第一SRH中的段标识列表获取当前段标识;以及
    当所述当前段标识为所述第一路由信息,并且根据所述第一路由信息和本地的转发表项确定下一跳为所述第一子接口,将所述第一数据报文转发至所述第一子接口。
  10. 一种节点,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,其中,所述处理器执行所述计算机程序时实现如权利要求1至9中任意一项所述的信息处理方法。
  11. 一种计算机可读存储介质,存储有计算机可执行指令,所述计算机可执行指令用于执行权利要求1至9中任意一项所述的信息处理方法。
PCT/CN2021/121761 2020-12-15 2021-09-29 信息处理方法、节点及计算机可读存储介质 WO2022127284A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237017216A KR20230093015A (ko) 2020-12-15 2021-09-29 정보 처리 방법, 노드 및 컴퓨터 판독 가능한 저장 매체
US18/254,238 US12034634B2 (en) 2020-12-15 2021-09-29 Information processing method, node, and computer-readable storage medium
EP21905214.9A EP4236126A4 (en) 2020-12-15 2021-09-29 INFORMATION PROCESSING METHOD, NODE AND COMPUTER READABLE STORAGE MEDIUM
JP2023528519A JP2023549512A (ja) 2020-12-15 2021-09-29 情報処理方法、ノード及びコンピュータ読み取り可能な記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011479889.8 2020-12-15
CN202011479889.8A CN114697263A (zh) 2020-12-15 2020-12-15 信息处理方法、节点及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2022127284A1 true WO2022127284A1 (zh) 2022-06-23

Family

ID=82060050

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/121761 WO2022127284A1 (zh) 2020-12-15 2021-09-29 信息处理方法、节点及计算机可读存储介质

Country Status (6)

Country Link
US (1) US12034634B2 (zh)
EP (1) EP4236126A4 (zh)
JP (1) JP2023549512A (zh)
KR (1) KR20230093015A (zh)
CN (1) CN114697263A (zh)
WO (1) WO2022127284A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090010171A1 (en) * 2007-07-05 2009-01-08 Cisco Technology, Inc. Scaling BFD sessions for neighbors using physical / sub-interface relationships
CN110391951A (zh) * 2018-04-17 2019-10-29 中兴通讯股份有限公司 以太网段标识邻接检测处理方法及装置、存储介质
CN111935013A (zh) * 2020-09-17 2020-11-13 南京中兴软件有限责任公司 流量转发控制方法及装置、流量转发方法及芯片、交换机

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8665886B2 (en) 2009-03-26 2014-03-04 Brocade Communications Systems, Inc. Redundant host connection in a routed network
US10666500B2 (en) 2016-03-30 2020-05-26 Juniper Networks, Inc. Failure handling for active-standby redundancy in EVPN data center interconnect
US10671590B2 (en) * 2016-05-27 2020-06-02 Cisco Technology, Inc. Delta database synchronization
US10110470B2 (en) * 2016-09-14 2018-10-23 Juniper Networks, Inc. Preventing data traffic loops associated with designated forwarder selection
US10320658B2 (en) * 2016-10-18 2019-06-11 Cisco Technology, Inc. Method and system for asymmetric redundancy mechanisms in multi-homed network access topologies
US10536370B2 (en) 2017-08-08 2020-01-14 Dell Products Lp Method and system to avoid temporary traffic loss with BGP ethernet VPN multi-homing with data-plane MAC address learning
CN111277482B (zh) 2020-01-13 2022-01-18 新华三大数据技术有限公司 一种报文处理方法及装置
CN116827855A (zh) * 2020-11-23 2023-09-29 华为技术有限公司 一种通告网络设备处理能力的方法、设备和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090010171A1 (en) * 2007-07-05 2009-01-08 Cisco Technology, Inc. Scaling BFD sessions for neighbors using physical / sub-interface relationships
CN110391951A (zh) * 2018-04-17 2019-10-29 中兴通讯股份有限公司 以太网段标识邻接检测处理方法及装置、存储介质
CN111935013A (zh) * 2020-09-17 2020-11-13 南京中兴软件有限责任公司 流量转发控制方法及装置、流量转发方法及芯片、交换机

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4236126A4 *

Also Published As

Publication number Publication date
JP2023549512A (ja) 2023-11-27
KR20230093015A (ko) 2023-06-26
CN114697263A (zh) 2022-07-01
US20240007394A1 (en) 2024-01-04
US12034634B2 (en) 2024-07-09
EP4236126A1 (en) 2023-08-30
EP4236126A4 (en) 2024-01-10

Similar Documents

Publication Publication Date Title
US11799773B2 (en) EVPN packet processing method, device, and system
US10880203B2 (en) Centralized segment routing dataplane based backup path validation
EP3582449B1 (en) Route processing in a vxlan
CN109218178B (zh) 一种报文处理方法及网络设备
US9369347B2 (en) Service to node resolution
US9832097B2 (en) Method and apparatus for MPLS label allocation for a BGP MAC-VPN
US8953590B1 (en) Layer two virtual private network having control plane address learning supporting multi-homed customer networks
WO2021258754A1 (zh) 报文指示方法、装置、设备和存储介质
US7483387B2 (en) Hierarchical label distribution for inter-area summarization of edge-device addresses
US8121032B2 (en) Efficient convergence of grouped VPN prefixes
JP7176095B2 (ja) 通信方法、通信機器、および通信システム
CA3104756C (en) Loop avoidance communications method, device, and system
WO2018103099A1 (zh) 发送和接收消息的方法、设备和系统
CN113228572A (zh) 用于分段路由(sr)代理段标识(sid)的内部网关协议(igp)
US11362954B2 (en) Tunneling inter-domain stateless internet protocol multicast packets
US9350654B1 (en) Microloop protection for multi-protocol label switching paths
WO2022121466A1 (zh) 以太虚拟专用网的数据处理方法、设备及存储介质
WO2023016550A1 (zh) 一种路由发送方法及设备
CN110620715B (zh) 虚拟扩展局域网通信方法、隧道端点和控制器
WO2022127284A1 (zh) 信息处理方法、节点及计算机可读存储介质
WO2022174789A1 (zh) 信息发布方法及装置、计算机可读存储介质
WO2022227940A1 (zh) Df选举模式切换方法、信息发送方法、pe设备和介质
US11212221B1 (en) Methods to improve ECMP for BGP services and BGP for provider edges with hybrid label distribution
US9853881B2 (en) Autonomous system border router (ASBR) advertising routes with a same forwarding label
WO2022042610A1 (zh) 信息处理方法、网络控制器、节点及计算机可读存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2023528519

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 20237017216

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 18254238

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2021905214

Country of ref document: EP

Effective date: 20230523

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21905214

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE