WO2020029928A1 - Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau - Google Patents

Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau Download PDF

Info

Publication number
WO2020029928A1
WO2020029928A1 PCT/CN2019/099329 CN2019099329W WO2020029928A1 WO 2020029928 A1 WO2020029928 A1 WO 2020029928A1 CN 2019099329 W CN2019099329 W CN 2019099329W WO 2020029928 A1 WO2020029928 A1 WO 2020029928A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
node
inline
interface address
data
Prior art date
Application number
PCT/CN2019/099329
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Publication of WO2020029928A1 publication Critical patent/WO2020029928A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/26—Special purpose or proprietary protocols or architectures

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and network device for establishing a BGP session and sending an interface address and an alias.
  • a data center network (data center network, DCN) is a network used for data transmission.
  • DCN data center network
  • the mainstream DCN usually adopts the spine-leaf architecture.
  • the DCN is composed of multiple leaf nodes (ie, leaf nodes) and multiple spine nodes (ie, spine nodes).
  • DCN uses Virtual Extensible LAN (VxLAN) as a service data bearing protocol.
  • VxLAN is a tunneling technology that virtualizes the DCN network into an underlay network and an overlay network.
  • the Overlay network After receiving the data packet to be transmitted, the Overlay network iterates the data packet to the VxLAN tunnel, encapsulates the VxLAN tunnel header in the data packet, obtains the encapsulated VxLAN tunnel packet, and the Underlay network Skip transmission of encapsulated VxLAN tunnel packets.
  • the Underlay network can establish a session between the leaf node and the spine node through the Open Shortest Path First (OSPF) protocol or the Border Gateway Protocol (BGP), so as to realize the leaf node and spine node.
  • OSPF Open Shortest Path First
  • BGP Border Gateway Protocol
  • Connectivity which enables data transmission between nodes in the Underlay network.
  • each leaf node and spine node in DCN determines link state information such as the interface addresses of other nodes connected to itself, and creates a link state database containing the link state information (Link State Data Base, LSDB) calculates the shortest path between its own node and other nodes according to the LSDB, and establishes a session between the leaf node and the spine node through the shortest path.
  • Link State Data Base LSDB
  • each node needs to periodically flood its link state information, which greatly limits the size of the DCN, resulting in that the OSPF protocol is only applicable to small DCNs. Therefore, currently, BGP is usually used to establish a session between a leaf node and a spine node to achieve the connectivity between the leaf node and the spine node, that is, BGP is used as the routing protocol of the Underlay network.
  • a session between a leaf node and a spine node established through BGP can be called a BGP session.
  • a technician when establishing a BGP session, a technician first configures its own interface address for each node in DCN ’s Underlay network, and then, a technician configures the interface address of the peer node for each node, thereby establishing each node and peer. BGP session between end nodes.
  • the embodiment of the present application discloses a method and network equipment for establishing a BGP session, and sending interface addresses and aliases, so as to solve the problems of tedious establishment process, which consumes a lot of time and manpower when establishing a BGP session through the existing technology.
  • an embodiment of the present application provides a method for establishing a border gateway protocol BGP session, including: applying to a bottom layer network of a data center network DCN, wherein the bottom layer network of the DCN includes a first node and a second node, the method include:
  • the first node uses the first interface address between the second inline interface and the first inline interface. Establish BGP sessions between them;
  • the second inline interface of the first node and the first inline interface of the second node are internally interconnected interfaces of the DCN's underlying network.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect whether the second interface address alias configured by the second inline interface is the same as the first interface address alias. An interface address alias matches. If they match, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address. In this case, it is only necessary to configure a first interface address alias for the first inline interface and an interface address alias that matches the first interface address alias for the second inline interface to establish a BGP session. Compared with the prior art, the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the method further includes:
  • the detecting whether the second interface address alias of the second inline interface of the second interface inline with the first interface address alias includes:
  • the first node When the second autonomous system number is different from the first autonomous system number, the first node performs the detection to check whether the second interface address alias of the second inline interface of the first autonomous system is the same as the first interface address alias. Matching operation
  • the first node determines whether the data priority of the data to be interacted is a high priority according to the data parameters of the data to be interacted, Data parameters include data traffic and / or data importance;
  • the first node When the data priority is a high priority, the first node performs the operation of detecting whether a second interface address alias of a second inline interface of the first node matches the first interface address alias.
  • the corresponding processing of the BGP session can be realized according to the data priority of the data to be exchanged, so that the case where the data priority is not a high priority In this case, BGP sessions are no longer established, to avoid subsequent data interactions due to incorrect allocation of autonomous system numbers, and to establish high-priority BGP sessions to transmit high-priority data through BGP sessions.
  • the method further includes:
  • the first node After the first node receives the interface address and the interface address alias again, when the interface address alias matches the second interface address alias, the first node according to the data parameter of the current interaction data of the BGP session To determine whether the data priority of the current interaction data is high priority, and the data parameters include data traffic and / or data importance;
  • the first node keeps the BGP session unchanged
  • the first node When the data priority is not a high priority, the first node re-establishes a BGP session between the second inline interface and the first inline interface according to the first interface address received again.
  • the corresponding processing of the BGP session can be realized according to the data priority of the current interactive data of the BGP session, so that the data can be prioritized.
  • the priority is high, the BGP session is kept unchanged to maintain data transmission.
  • the data priority is low, the BGP session with the first node is re-established.
  • the method further includes:
  • the first node After the first node receives the first autonomous system number transmitted by the second node again, the first node detects whether the second autonomous system number is the same as the first autonomous system number received again;
  • the first node keeps the BGP session unchanged
  • the first node judges the data priority of the current interactive data according to the data parameters of the current interactive data of the BGP session Whether it is high priority, the data parameters include data traffic and / or data importance;
  • the first node keeps the BGP session unchanged
  • the first node interrupts the BGP session.
  • the corresponding processing of the BGP session can be realized according to the data priority of the current interactive data of the BGP session, thereby
  • the data priority is high
  • the BGP session can be maintained to maintain data transmission.
  • the data priority is low
  • the BGP session can be interrupted to avoid the impact of the autonomous system number allocation error. Subsequent data interaction.
  • the fourth possible The implementation also includes:
  • an embodiment of the present application provides a method for establishing a BGP session, which is applied to a low-level network of a data center network DCN.
  • the low-level network of the DCN includes a first node and a second node, and the method includes:
  • the second node generates a first interface address of a first inline interface of the second node according to an automatic address generation mechanism
  • the first inline interface of the second node is an internal interconnection interface of the DCN's underlying network.
  • the method further includes:
  • the second node transmits the first autonomous system number to the first node.
  • the method further includes:
  • the second node regenerates the first interface address of the first inline interface, and sends the first interface address to the first inline interface.
  • the first node transmits the first interface address alias and the regenerated first interface address.
  • the method further includes:
  • the second node transmits the changed first autonomous system number to the first node.
  • the method further includes:
  • the second node generates a third interface address of its own third inline interface according to the automatic address generation mechanism, and transmits the third interface address to the first node.
  • the present invention provides a network device that is used as a first node and is applied to a lower layer network of a data center network DCN.
  • the lower layer network of the DCN includes the first node and the second node, and the network device Method for performing the first aspect or any possible implementation of the first aspect.
  • the network device includes a module for performing the first aspect or the method in any possible implementation manner of the first aspect.
  • the present invention provides a network device that is used as a second node and is applied to a lower layer network of a data center network DCN.
  • the lower layer network of the DCN includes the first node and the second node, and the network device Method for performing the second aspect or any possible implementation of the second aspect.
  • the network device includes a module for performing the second aspect or the method in any possible implementation manner of the second aspect.
  • the present invention provides a network device that is used as a first node and is applied to a bottom layer network of a data center network DCN.
  • the bottom layer network of the DCN includes the first node and the second node, and the network device
  • the processor includes a processor and a transceiver.
  • the network device may further include a random access memory, a read-only memory, and a bus.
  • the processor is respectively coupled to the transmitter, the random access memory, and the read-only memory through a bus.
  • the booting system is booted by a basic input / output system fixed in a read-only memory or a bootloader in an embedded system to guide the first node into a normal operating state.
  • the application program and the operating system are run in the random access memory, so that the processor executes the method in the first aspect or any possible implementation manner of the first aspect.
  • the present invention provides a network device that is used as a second node and is applied to a lower layer network of a data center network DCN.
  • the lower layer network of the DCN includes the first node and the second node, and the network device
  • the processor includes a processor and a transceiver.
  • the network device may further include a random access memory, a read-only memory, and a bus. The processor is respectively coupled to the transmitter, the random access memory, and the read-only memory through a bus.
  • the basic input / output system or the bootloader in the embedded system which is solidified in the read-only memory, is used to boot the system, and the second node is guided to enter a normal operating state.
  • the application program and the operating system are run in the random access memory, so that the processor executes the second aspect or the method in any possible implementation manner of the second aspect.
  • an embodiment of the present application provides a computer-readable medium.
  • the computer-readable storage medium stores instructions.
  • the computer-readable storage medium runs on the computer, the computer executes the first aspect or any possible design of the first aspect. Methods.
  • an embodiment of the present application provides a computer-readable medium.
  • the computer-readable storage medium stores instructions.
  • the computer-readable storage medium runs the computer, the computer executes the first aspect or any possible design of the first aspect. Methods.
  • an embodiment of the present application provides a BGP session establishment system, which is applied to an underlying network of a data center network DCN.
  • the system includes the network equipment of any one of the third aspect to the fifth aspect and the sixth aspect to the first aspect. Network equipment of any of the eight aspects.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect whether the second interface address alias configured by the second inline interface is the same as The first interface address aliases match. If they match, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address. In this case, it is only necessary to configure a first interface address alias for the first inline interface and an interface address alias that matches the first interface address alias for the second inline interface to establish a BGP session. Compared with the prior art, the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the interface address of the inline interface needs to be configured for the inline interface, and Configure the interface address of the b inline interface for the a inline interface, and also need to configure the interface address of the b inline interface and the interface address of the a inline interface for the b inline interface, at least four configuration operations are required.
  • an inline interface a in the second node and an inline interface b in the first node need to establish M (M is a positive integer greater than 1) BGP sessions
  • M is a positive integer greater than 1
  • an inline for a Configure M interface addresses for a inline interface and M interface addresses for b inline interface for a inline interface and also need to configure M interface addresses for b inline interface for b inline interface, and a M interface addresses of an inline interface require at least 4M configuration operations.
  • M interface address aliases need to be configured for a inline interface, and M interface address aliases that match the interface address aliases of a inline interface can be configured for b inline interface. That is, only 2M configuration operations are required. Compared with the prior art, configuration operations are greatly reduced.
  • DCN ’s Underlay network often contains a large number of nodes.
  • the effect of reducing the configuration operation in the embodiment of the present application is more obvious.
  • each node actively generates the interface address of its own interface and transmits it to the peer node, without the need to manually configure the interface address.
  • the possibility of configuration errors is greatly reduced, which can improve the BGP session. Accuracy.
  • FIG. 1 (a) is a schematic diagram of a network topology architecture of a DCN Underlay network disclosed in the prior art
  • FIG. 1 (b) is a schematic diagram of a network topology architecture of a DCN Underlay network disclosed in the prior art
  • FIG. 2 is a schematic flowchart of a BGP session establishment method disclosed in an embodiment of the present application
  • FIG. 3 is a schematic flowchart of another BGP session establishment method disclosed in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an RA message in a BGP session establishment method disclosed in an embodiment of the present application
  • FIG. 5 is a schematic flowchart of another BGP session establishment method disclosed in an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another BGP session establishment method disclosed in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method for sending an interface address and an alias according to an embodiment of the present application
  • FIG. 8 is a schematic structural diagram of a network device disclosed in an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of still another network device disclosed in an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device disclosed in an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of still another network device disclosed in an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of still another network device disclosed in an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of still another network device disclosed in an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a BGP session establishment system disclosed in an embodiment of the present application.
  • the embodiment of the present application discloses a method and network device for establishing a BGP session and sending interface addresses and aliases.
  • each spine node needs to be connected to all leaf nodes, and each leaf node requires Connects to all spine nodes for data interaction between spine and leaf nodes.
  • the first node can be considered as the opposite node of the second node, and the second node is the opposite node of the first node, and the first node and the second node There is a neighbor relationship.
  • the DCN ’s Underlay network shown in Figure 1 (a) is a two-layer architecture, where one layer is a leaf node, and the other is One layer is a spine node, and the DCN's Underlay network shown in 1 (b) has a three-layer architecture, the middle layer is a spine node, and the other two layers are leaf nodes.
  • DCN's Underlay network contains more nodes, which can often reach hundreds of nodes.
  • Underlay The number of nodes contained in the network is even tens of thousands. In this case, each node of the DCN's Underlay network can establish a BGP session by using the solution disclosed in the embodiment of the present application to implement data interaction with other nodes.
  • the first embodiment of the present application discloses a method for establishing a border gateway protocol BGP session.
  • the method is applied to an underlay network of a data center network DCN.
  • the underlay network of the DCN includes a first node and a second node, as shown in FIG. 2 Schematic diagram of the workflow, the BGP session establishment method includes the following steps:
  • Step S11 The first node receives a first interface address and a first interface address alias from a first inline interface of the second node, and the first inline interface is an inline of the second node. interface.
  • the first node may be a leaf node in an Underlay network of the DCN.
  • a second node that establishes a BGP session with the first node is a spine in the Underlay network of the DCN.
  • the first node may be a spine node in an Underlay network of the DCN.
  • a second node that establishes a BGP session with the first node is a leaf node in the Underlay network of the DCN.
  • the inline interface refers to the internal interconnection interface of DCN's Underlay network. That is, the nodes in the Underlay network of DCN are interconnected through an inline interface, that is, the leaf node in the Underlay network is interconnected with the inline interface of the spine node through its own inline interface.
  • the spine node is interconnected with the inline interface of the leaf node through its own inline interface.
  • the inline interface may be a physical interface or a virtual interface, which is not limited in the embodiment of the present application.
  • the second node can automatically generate the first interface address of its first inline interface according to the automatic address generation mechanism, that is, the second node can automatically generate the first interface address of the first inline interface.
  • the second node transmits the first interface address and the alias of the first interface address (that is, the first interface address alias) to the first node.
  • the interface address of the first inline interface automatically generated by the second node may be a link-local address (LLA) that complies with Internet Protocol Version 6 (IPv6), or a unique local address. Address (unique local address, ULA).
  • LLA link-local address
  • IPv6 Internet Protocol Version 6
  • ULA unique local address
  • Step S12 The first node detects whether a second interface address alias of a second inline interface of the first node matches the first interface address alias.
  • a second interface address alias is configured for the second inline interface in advance, and the second interface is enabled during configuration
  • the address alias matches the first interface address alias.
  • the first node After receiving the first interface address and the first interface address alias, the first node performs detection through step S12. If it is detected that the second interface address alias matches the first interface address alias, it indicates that it is currently required A BGP session is established between the second inline interface and the first inline interface.
  • the second interface address alias matches the first interface address alias, which can be a variety of situations. For example, when the second interface address alias is set to be exactly the same as the first interface address alias, the second interface address alias is considered to be the same as The first interface address alias matches, or if the first N characters in the second interface address alias are the same as the first N characters in the first interface address alias, it is determined that the second interface address alias matches the first interface address alias. Match, N is a positive integer greater than 0.
  • the configuration can be completed.
  • the first interface address alias of the second node is copied to the first node and used as the second address alias of the second inline interface in the first node to implement the configuration of the second interface address alias of the second inline interface.
  • a node can establish multiple BGP sessions with different inline interfaces of the same peer node through the same inline interface of itself, and can also establish multiple interface addresses with the same inline interface of the peer node by generating multiple interface addresses. Multiple BGP sessions.
  • the interface address alias is unique between two nodes having a neighbor relationship. In this case, if a certain inline interface establishes multiple BGP sessions with the same inline interface of the peer node, the interface The address alias can distinguish each interface address and further distinguish each BGP session.
  • Step S13 When the second interface address alias matches the first interface address alias, the first node uses the first interface address between the second inline interface and the first internal interface. A BGP session is established between the connected interfaces.
  • the second inline interface of the first node and the first inline interface of the second node are internally interconnected interfaces of the DCN's underlying network.
  • the first node establishes a BGP session between the second inline interface and the first inline interface according to the first interface address, thereby implementing the establishment of a BGP session between the first node and the second node.
  • the interface address alias of each inline interface is usually pre-configured, and the interface address alias is unique between two nodes having a neighbor relationship to distinguish each BGP session. Further, for simplicity, the interface address alias of each inline interface can be configured to be unique in the DCN.
  • the embodiment of the present application discloses a BGP session establishment method applied to DCN, which is applied to a bottom layer network of a data center network DCN.
  • the bottom layer network of the DCN includes a first node and a second node.
  • the first node receives A first interface address and a first interface address alias from a first inline interface of the second node, the first inline interface being an inline interface of the second node; the first node detecting itself Whether the second interface address alias of the second inline interface matches the first interface address alias; when the second interface address alias matches the first interface address alias, the first node
  • the first interface address establishes a BGP session between the second inline interface and the first inline interface, wherein the second inline interface of the first node and the first An inline interface interconnects.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect whether the second interface address alias configured by the second inline interface is the same as The first interface address aliases match, and if they match, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address.
  • the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the interface address of the inline interface needs to be configured for the inline interface, and Configure the interface address of the b inline interface for the a inline interface, and also need to configure the interface address of the b inline interface and the interface address of the a inline interface for the b inline interface, at least four configuration operations are required.
  • an inline interface a in the second node and an inline interface b in the first node need to establish M (M is a positive integer greater than 1) BGP sessions
  • M is a positive integer greater than 1
  • an inline for a Configure M interface addresses for a inline interface and M interface addresses for b inline interface for a inline interface and also need to configure M interface addresses for b inline interface for b inline interface, and a M interface addresses of an inline interface require at least 4M configuration operations.
  • M interface address aliases need to be configured for a inline interface, and M interface address aliases that match the interface address aliases of a inline interface can be configured for b inline interface. That is, only 2M configuration operations are required. Compared with the prior art, configuration operations are greatly reduced.
  • DCN ’s Underlay network often contains a large number of nodes.
  • the effect of reducing the configuration operation in the embodiment of the present application is more obvious.
  • each node actively generates the interface address of its own interface and transmits it to the peer node, without the need to manually configure the interface address.
  • the possibility of configuration errors is greatly reduced, which can improve the BGP session. Accuracy.
  • the amount of modification to the inline interface of each node is small, which is convenient to implement.
  • the nodes included in DCN's Underlay network can belong to the same autonomous system, and can also belong to different autonomous systems. If each node included in the Underlay network belongs to the same autonomous system, the BGP session established between each node is an Internal Border Gateway Protocol (Internal Border Gateway Protocol) session. Further, if each node included in the Underlay network belongs to different autonomous systems, the BGP session established between each node is an External Border Gateway Protocol (External Gateway Protocol) session. In this case, the present application discloses a second embodiment.
  • Internal Border Gateway Protocol Internal Border Gateway Protocol
  • External Gateway Protocol External Border Gateway Protocol
  • the BGP session establishment method disclosed in the embodiment of the present application includes the following steps:
  • Step S21 The first node receives a first interface address and a first interface address alias from a first inline interface of the second node, and the first inline interface is an inline interface of the second node.
  • step S21 is the same as the operation process of step S11, which can be referred to each other, and will not be repeated here.
  • Step S22 The first node receives a first autonomous system number of a first autonomous system to which the second node belongs.
  • the first autonomous system number is usually transmitted from the second node to the first node.
  • each autonomous system will be assigned a unique number within the DCN, which is the Autonomous System Number (ASN).
  • ASN Autonomous System Number
  • the autonomous system to which the second node belongs is referred to as a first autonomous system
  • the number of the first autonomous system is referred to as a first autonomous system number.
  • Step S23 The first node detects whether the second autonomous system number of the second autonomous system to which it belongs is the same as the first autonomous system number. If they are the same, perform the operation of step S24; if they are different, perform the operation of step S25.
  • Step S24 When the second autonomous system number is the same as the first autonomous system number, the first node determines whether the data priority of the data to be interacted is a high priority according to the data parameters of the data to be interacted with The data parameters include data traffic and / or data importance. If yes, perform the operation of step S25.
  • step S25 if the data to be exchanged has a high priority, the operation of step S25 is performed, that is, if the data to be exchanged has a high priority, the first node executes a second inline interface that detects itself. Whether the second interface address alias matches the first interface address alias.
  • priorities may be set for the data in advance, wherein two priorities are usually set, that is, a high priority and a low priority. If the data traffic to be exchanged is large, and / or the data is important If the data is high, it is determined that the data to be interacted is a high priority. If the data flow of the data to be interacted is small and / or the data is of low importance, the data to be interacted is determined to be a low priority.
  • the first node can continue to perform subsequent operations to establish a BGP session to ensure that the data interaction can proceed smoothly.
  • Step S25 The first node detects whether the second interface address alias of the second inline interface of the first node matches the first interface address alias.
  • Step S26 When the second interface address alias matches the first interface address alias, the first node uses the first interface address between the second inline interface and the first internal interface. A BGP session is established between the connected interfaces.
  • the second inline interface of the first node and the first inline interface of the second node are internally interconnected interfaces of the DCN's underlying network.
  • step S24 if it is determined by the operation of step S24 that the data priority of the data to be interacted is not a high priority, the following steps may be further included:
  • Step S27 When the data priority is not a high priority, the first node terminates the establishment of a BGP session with the first inline interface.
  • the first node will determine a processing measure according to the data priority of the data to be exchanged. Wherein, if the data flow of the data to be exchanged is large and / or the data is of high importance, it is determined that the data to be exchanged is of high priority, and the subsequent operations of establishing a BGP session are continued. In this case, when a BGP session is established, related information about the BGP session can also be recorded and used as diagnostic information for subsequent problem location.
  • the first node terminates the establishment of the BGP session. A BGP session with the second node is no longer established.
  • the first node will continue to perform the check whether the second interface address alias of the second inline interface of the first autonomous system matches the first interface address alias. operating.
  • the first node receives the first autonomous system number after receiving the first interface address and the first interface address alias transmitted by the second node.
  • the operation of the first node receiving the first interface address and the alias of the first interface address is not in strict sequence with the operation of receiving the first autonomous system number.
  • the first autonomous system number may be received first, and then the first interface address and the first interface address alias may be received.
  • the second node loads the first autonomous system number, the first interface address, and the first interface address alias in the same packet, the first node may also receive the first autonomous system number, the first interface address, and the first interface at the same time. Address alias.
  • the message may be an extended router. Advertisement (Router, Advertisement, RA) message.
  • FIG. 4 discloses a schematic format of an RA message.
  • the RA message complies with Internet Protocol Version 6 (IPv6).
  • IPv6 Internet Protocol Version 6
  • the fields in the message include: Type, Length, ASN, Type, Reserved1, Reserved2, IPv6 address, ASN, and alias-name, where the "Type” field is used to load the type of the RA message, which is usually 1 byte; the "Length” field is used to load the "Type, Length,
  • the lengths of the eight fields: ASN, Type1, Reserved1, Reserved2, IPv6 address, ASN, and alias-name are usually in the range of [24,255] bytes; the "ASNtype” field is used to load the first autonomous system number.
  • Type usually 1 byte.
  • the first autonomous system number is usually a fixed length of 2 bytes.
  • the first autonomous system number is usually a 4-byte fixed length; the "IPv6 address” field is used to load the first interface address of the first inline interface, which is usually 16 bytes; the "ASN” field is used to load the first Autonomous system number, the The segment can be 2 bytes or 4 bytes. If the field is 4 bytes, it is often not necessary to set the "Reserved 2" field in the message shown in Figure 4, and only load the first autonomous system number through the "ASN” field.
  • the "Reserved 2" field can be set, and the "Reserved 2" field is 2 bytes.
  • the first autonomous system number is loaded together through the "ASN” field and the "Reserved 2" field; " The "alias-name” field is used to load the first interface address alias of the first inline interface.
  • the length of the "alias-name” field the length of the "Length” field is 24 bytes.
  • the "alias-name” field loads the first interface address alias, which can be obtained by encoding in the form of American Standard Code (Information Interchange, ASCII).
  • the second node does not transmit the first autonomous system number simultaneously with the first interface address and the first interface address alias, in order for the first node to determine the first autonomous system number after receiving the first autonomous system number For the inline interface to which it belongs, when the second node transmits the first autonomous system number, it needs to transmit the alias of the first interface address at the same time, or transmit the first interface address at the same time, so that the first node receives the first autonomous system. After the system number, the BGP session corresponding to the received first autonomous system number is determined according to the first interface address alias or the first interface address transmitted simultaneously.
  • the state of the first inline interface of the second node may change, and the first interface address may also change .
  • the second node regenerates the first interface address of the first inline interface, and transmits the first interface address alias to the first node And the regenerated first interface address.
  • the state of the first inline interface may change, from an up state to a down state.
  • the second node will regenerate the first interface address of the first inline interface and transmit it to the first node.
  • the first interface address of the first inline interface may also change.
  • the second node also regenerates the first interface address of the first inline interface and transmits the first interface address to the first node.
  • the first interface address is aliased and the regenerated first interface address.
  • Step S31 After the first node receives the interface address and the interface address alias again, when the interface address alias is the same as the second interface address alias, the first node according to the current interaction data of the BGP session. Data parameter to determine whether the data priority of the current interaction data is high priority.
  • the data parameters include data traffic and / or data importance.
  • the interface address alias received again by the first node matches the second interface address alias, it indicates that the interface address alias received again is the first interface address alias, and the interface address received again is the interface of the first inline interface.
  • the BGP session established with the first inline interface can be determined according to the first interface address alias, and further based on the data parameters of the current interactive data of the BGP session, it is determined whether the data priority of the current interactive data is high priority.
  • Step S32 When the data priority is a high priority, the first node keeps the BGP session unchanged.
  • Step S33 When the data priority is not high priority, the first node re-establishes between the second inline interface and the first inline interface according to the first interface address received again. BGP session.
  • priorities may be set for the data in advance, wherein two priorities are usually set, that is, a high priority and a low priority. If the current interactive data has a large data flow, and / or the data is important If it is high, it is determined that the current interaction data is of high priority. If the data flow of the current interaction data is small and / or the data is of low importance, it is determined that the current interaction data is of low priority.
  • the data priority is set to a high priority.
  • the first node may keep the BGP session that has been established with the first inline interface unchanged to avoid interruption of the BGP session, thereby affecting data interaction.
  • diagnostic information may also be recorded. The diagnostic information records related information of the BGP session, so that problem location can be performed later.
  • the first node may The interface address, and re-establish the BGP session with the first inline interface to keep the BGP session updated.
  • a BGP session between nodes is created by manual configuration. If the interface address of an inline interface in one of the nodes changes, the interface address of the inline interface needs to be reconfigured, and the interface address must be modified. The configuration of the peer node of the node is relatively tedious. With the solution disclosed in this application, after the first interface address of the first inline interface changes, the second node regenerates the first interface address, and transmits the first interface address alias and the regenerated first interface to the first node. interface address.
  • the first node After the first node establishes a BGP session with the first inline interface, if the interface address and the interface address alias are received again, it is detected whether the received interface address alias matches the second interface address alias. If they match, It means that the interface address alias received again is the first interface address alias, and the interface address received again is the interface address of the first inline interface. In this case, the first node determines whether the BGP session with the second node needs to be re-established according to the data parameters of the current interaction data of the BGP session established with the first inline interface. Compared with the prior art, this solution reconfigures, simplifies operations, further saves time and labor required for BGP session establishment, and improves BGP session establishment efficiency.
  • the second node will also resend the interface of the first inline interface to the first node.
  • the first node can establish a BGP session between the second inline interface and the first inline interface again after the first inline interface transitions to the up state, So that after the state of the first inline interface changes to the up state, the first node can establish a BGP session with the first inline interface in time to ensure data interaction.
  • the RA message shown in FIG. 4 may also be used for transmission.
  • other types of messages may also be used. This application implements Examples do not limit this.
  • the autonomous system number of the node may also change.
  • the method further includes:
  • Step S41 After the first node receives the first autonomous system number transmitted by the second node again, the first node detects the second autonomous system number and the first autonomous system number received again. Is it the same. If not, perform the operation of step S42, and if so, perform the operation of step S43.
  • the second node transmits the changed first autonomous system number to the first node after the first autonomous system number changes.
  • the BGP session corresponding to the received first autonomous system number is determined according to the first interface address alias or the first interface address transmitted simultaneously.
  • Step S42 The first node keeps the BGP session unchanged.
  • Step S43 When the second autonomous system number is the same as the first autonomous system number received again, the first node judges the current interaction data according to the data parameters of the current interaction data of the BGP session. Whether the data priority is high priority, and the data parameters include data traffic and / or data importance. If yes, go back to step S42, if no, go to step S44.
  • different priorities may be set for the data in advance, wherein two priorities are usually set, that is, a high priority and a low priority. If the current interactive data has a large data flow, and / or the data is important If it is high, it is determined that the current interaction data has a high priority. If the data flow of the current interaction data is small and / or the data is of low importance, it is determined that the current interaction data is a low priority.
  • Step S44 When the data priority is not a high priority, the first node interrupts the BGP session.
  • the autonomous system number may change. If the second node and the first node belong to different autonomous systems, after the first autonomous system number of the second node changes, the second node also transmits the changed first autonomous system number to the first node.
  • the first node if it establishes a BGP session between the second inline interface and the first inline interface, and then receives the first autonomous system number transmitted by the second node again, it detects Whether its own second autonomous system number is the same as the first autonomous system number received again. If it is determined through inspection that the second autonomous system number is different from the first autonomous system number received again, the first node keeps the BGP session unchanged.
  • the first node will determine the processing measures according to the business requirements. Among them, if the data exchanged by the first node through the BGP session established with the first inline interface is more important, and / or the data traffic is large, the data is set. The priority is high priority. In this case, the first node can keep the BGP session that has been established with the first inline interface unchanged, so as to avoid interruption of the BGP session and affect data interaction. In addition, diagnostic information may also be recorded. The diagnostic information records related information of the BGP session, so that problem location can be performed later.
  • the first node may An interface address to re-establish a BGP session between the second inline interface and the first inline interface to keep the BGP session updated.
  • the first node can still maintain The BGP session that has been established with the second node remains unchanged. Further, the first node can also record diagnostic information. The diagnostic information records relevant information about the BGP session for subsequent problem location; or, if the first inline interface The data currently interacting with the first node is not important and / or the data flow is small. The first node can disconnect the BGP session with the first inline interface to avoid the error of autonomous system number assignment during data interaction. The impact.
  • this application also discloses another embodiment. Compared with the above embodiment, the embodiment of this application further includes the following steps:
  • the first node receives a third interface address from a third inline interface of the second node.
  • the first node detects whether to generate a second interface address of its second inline interface according to the automatic address generation mechanism, and whether to obtain a second interface address alias.
  • the first node according to the third interface address, in the second inline interface and the The establishment of a BGP session between the third inline interfaces is described.
  • the first node After receiving the message from the second node, the first node usually detects whether an interface address alias is loaded in the message. If an interface address alias is loaded, the operations in steps S12 to S13 are performed. In addition, if it is determined that the interface address alias is not loaded in the received message, then the operations of the embodiment of the present application are performed, that is, if the first node determines that the interface address alias is not loaded in the received message, only the interface address alias is loaded.
  • the third interface address of the third inline interface performs an operation of detecting whether to generate the second interface address of the second inline interface of itself according to the automatic address generation mechanism, and whether to obtain an alias of the second interface address.
  • the second node transmits information to the first node through the RA message shown in FIG. 4, when the second node detects that no bytes are loaded in the "alias-name" field, it may determine that the received message is in the received message. No interface address alias is loaded.
  • the third inline interface of the second node only establishes a BGP session with the second inline interface of the first node, since there is no need to distinguish the BGP session, in this case, the second node is generating the third inline interface After transmitting the third interface address, the third interface address is transmitted to the first node without transmitting the interface address alias of the third inline interface.
  • the first node if the first node receives the interface address of the first inline interface, but does not receive the first interface address alias, the first node will detect whether to generate its own first address according to the automatic address generation mechanism. A second interface address of the two inline interfaces, and whether to obtain a second interface address alias of the second inline interface.
  • the first node determines to generate the second interface address of the second inline interface according to the automatic address generation mechanism, and obtains the second interface address alias, it indicates that the first node can currently use the first interface of the first inline interface. Address to establish a BGP session with the first inline interface.
  • the first node does not generate the second interface address of the second inline interface according to the automatic address generation mechanism, or the second interface address alias of the second inline interface is not obtained, or the first If a node neither generates the second interface address of the second inline interface nor obtains the second interface address alias of the second inline interface according to the automatic address generation mechanism, it indicates that the first node is currently unsuitable to establish a connection with the first internal interface. For a BGP session with an interconnected interface, a BGP session with a third inline interface is no longer established.
  • the second node can generate an interface address of the first inline interface of the second node according to an automatic address generation mechanism.
  • the interface address of the first inline interface may be an LLA or ULA that complies with IPv6.
  • LLA is an IPv6 unicast address with the prefix "FE80 :: / 10", which is unique on the local link
  • ULA is an IPv6 unicast address with the prefix "FC00 :: / 7", which is unique within the local network.
  • Both LLA and ULA support the automatic address generation mechanism, that is, the nodes in the DCN can actively generate LLA or ULA according to the automatic address generation mechanism.
  • the ULA automatically generated by the algorithm defined in the RFC 4193 file often has a very low collision probability. Therefore, when the second node applies the BGP session establishment method applied to DCN disclosed in the embodiments of this application, The interface address can be preferentially selected from the ULA automatically generated by the algorithm defined in the RFC 4193 file.
  • the interface address applied by the second node may also be another address that supports an automatic address generation mechanism, which is not limited in this embodiment of the present application.
  • a method for transmitting an interface address and an alias is disclosed.
  • the method is applied to an underlying network Underlay network of a data center network DCN.
  • the Underlay network of the DCN includes a first node and a first node. Two nodes. Referring to the schematic diagram of the workflow shown in FIG. 7, the method includes:
  • Step S51 The second node generates a first interface address of a first inline interface of the second node according to an automatic address generation mechanism.
  • the interface address of the first inline interface automatically generated by the second node may be an LLA or ULA that complies with IPv6.
  • LLA Low-latency Integrated Circuit
  • ULA User Service
  • IPv6 IP Security
  • Step S52 The second node obtains a first interface address alias of the first inline interface.
  • the alias of the first interface address is the alias of the first interface address.
  • a node can establish multiple BGP sessions with different inline interfaces of the same peer node through the same inline interface of itself, and can also establish multiple interface addresses with the same inline interface of the peer node by generating multiple interface addresses. Multiple BGP sessions.
  • the interface address alias is unique between two nodes having a neighbor relationship. In this case, the interface address alias can distinguish each interface address and further distinguish each BGP session.
  • a first interface address alias may be configured for the first inline interface in advance. In this case, after the first interface address of the first inline interface is generated, a pre-configured first interface address alias can be obtained.
  • Step S53 The second node transmits the first interface address and the first interface address alias to the first node.
  • the first inline interface of the second node is an internal interconnection interface of the DCN's underlying network.
  • a second interface address alias is configured for the second inline interface in advance, and, during configuration, the The second interface address alias matches the first interface address alias.
  • the first node After receiving the first interface address and the first interface address alias of the first inline interface, the first node detects whether the second interface address alias of the second inline interface matches the first interface address alias.
  • the second interface address alias matches the first interface address alias, and the first node establishes BGP between the second inline interface and the first inline interface according to the first interface address. Conversation.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect the second interface address alias configured for the second inline interface in advance. Whether it matches the first address alias of the first interface, and if it matches, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address. In this case, you only need to configure an interface address alias for the second inline interface that matches the first inline interface to establish a BGP session. Compared with the prior art, the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • each node actively generates the interface address of its own interface and transmits it to the peer node, without the need to manually configure the interface address.
  • the possibility of configuration errors is greatly reduced, which can improve the BGP session. Accuracy.
  • first node and the second node may belong to the same autonomous system, and may also belong to different autonomous systems. If the first node and the second node belong to the same autonomous system, the BGP session established between the first node and the second node is an Internal Border Gateway Protocol (Internal Border Gateway Protocol) session. Further, if the first node and the second node belong to different autonomous systems, the BGP session established between the first node and the second node is an External Border Gateway Protocol (External Border Gateway Protocol) session.
  • Internal Border Gateway Protocol Internal Border Gateway Protocol
  • External Border Gateway Protocol External Border Gateway Protocol
  • the method for establishing a BGP session applied to DCN disclosed in the embodiments of the present application further includes:
  • the second node transmits the first autonomous system number to the first node.
  • the operation of the first node receiving the first interface address and the alias of the first interface address is not in strict sequence with the operation of receiving the first autonomous system number.
  • the first autonomous system number may be received first, and then the first interface address and the first interface address alias may be received.
  • the second node loads the first autonomous system number, the first interface address, and the first interface address alias in the same packet, the first node may also receive the first autonomous system number, the first interface address, and the first interface at the same time. Address alias.
  • the message may be an extended router.
  • An advertisement (Router, Advertisement, RA) message The format of the RA message is shown in Figure 4.
  • the second node After the second node transmits the first interface address and the first interface address alias to the first node, the state of the first inline interface of the second node may change, and the first interface address may also change .
  • the second node transmits the first interface address and the first node to a first node in an underlying network of the DCN.
  • the interface address alias it also includes:
  • the second node regenerates the first interface address of the first inline interface, and sends the first interface address to the first inline interface.
  • the first node transmits the first interface address alias and the regenerated first interface address.
  • the autonomous system number of the node may also change.
  • the method further includes:
  • the second node transmits the changed first autonomous system number to the first node.
  • the method further includes: the second node generates a third interface address of a third inline interface of the second node according to an automatic address generation mechanism, and transmits the third interface to the first node. address.
  • the second node after receiving the third interface address of the third inline interface, the second node detects whether to generate the second interface address of its second inline interface according to the automatic address generation mechanism, and whether to obtain the second interface. Address alias.
  • the first node according to the third interface address, in the second inline interface and the The establishment of a BGP session between the third inline interfaces is described.
  • a network device is disclosed and used as the first node.
  • the network device is applied to a lower layer network of a data center network DCN, and the lower layer network of the DCN includes a first node and a second node.
  • the first node may be a leaf node in an Underlay network of the DCN.
  • a second node that establishes a BGP session with the first node is a spine in the Underlay network of the DCN.
  • the first node may be a spine node in an Underlay network of the DCN.
  • a second node that establishes a BGP session with the first node is a leaf node in the Underlay network of the DCN.
  • the network device disclosed in the embodiment of the present application includes a transceiver unit 110 and a processing unit 120.
  • the transceiver unit 110 is configured to receive a first interface address and a first interface address alias from a first inline interface of the second node, where the first inline interface is the second node's Inline interface
  • the processing unit 120 is configured to detect whether a second interface address alias of a second inline interface of the second interface address alias matches the first interface address alias, and when the second interface address alias matches the first interface, When the address alias matches, a BGP session is established between the second inline interface and the first inline interface according to the first interface address;
  • the second inline interface of the first node and the first inline interface of the second node are internally interconnected interfaces of the DCN's underlying network.
  • the second node can automatically generate the first interface address of the first inline interface according to the automatic address generation mechanism, that is, the second node can automatically generate the first interface address of the first inline interface.
  • the second node transmits the first interface address and the alias of the first interface address (that is, the first interface address alias) to the first node.
  • a second interface address alias is configured for the second inline interface in advance, and the first The second interface address alias matches the first interface address alias.
  • the first node After receiving the first interface address and the first interface address alias, the first node performs detection through step S12. If it is detected that the second interface address alias matches the first interface address alias, it indicates that it is currently required A BGP session is established between the second inline interface and the first inline interface.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect the second interface address alias configured by the second inline interface. Whether it matches the alias of the first interface address, and if it matches, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address. In this case, it is only necessary to configure a first interface address alias for the first inline interface and an interface address alias that matches the first interface address alias for the second inline interface to establish a BGP session. Compared with the prior art, the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the transceiver unit when the first node and the second node belong to different autonomous systems, the transceiver unit is further configured to receive the second node to which the second node belongs.
  • the performing, by the processing unit, the operation of detecting whether a second interface address alias of a second inline interface of the processing unit matches the first interface address alias includes:
  • the second autonomous system number determines whether the data priority of the data to be interacted is a high priority according to the data parameter of the data to be interacted, and the data parameter includes data traffic And / or data importance;
  • each autonomous system will be assigned a unique number within the DCN, which is the Autonomous System Number (ASN).
  • ASN Autonomous System Number
  • the autonomous system to which the second node belongs is referred to as a first autonomous system
  • the number of the first autonomous system is referred to as a first autonomous system number.
  • the first A node will determine the processing measures according to the data priority of the data to be exchanged. Wherein, if the data flow of the data to be exchanged is large and / or the data is of high importance, it is determined that the data to be exchanged is of high priority, and the subsequent operations of establishing a BGP session are continued. In this case, when a BGP session is established, related information about the BGP session can also be recorded and used as diagnostic information for subsequent problem location.
  • the first node terminates the establishment of the BGP session and does not establish A BGP session with the second node.
  • the processing unit is further configured to establish a BGP session between the second inline interface and the first inline interface, and receive the interface address again.
  • the interface address alias when the interface address alias matches the second interface address alias, determine whether the data priority of the current interaction data is high priority according to the data parameters of the current interaction data of the BGP session Level, the data parameters include data traffic and / or data importance;
  • the processing unit is further configured to keep the BGP session unchanged;
  • the processing unit is further configured to re-establish BGP between the second inline interface and the first inline interface according to the first interface address received again. Conversation.
  • the processing unit is further configured to establish a BGP session between the second inline interface and the first inline interface, and receive the BGP session again. After the first autonomous system number transmitted by the second node, detecting whether the second autonomous system number is the same as the first autonomous system number received again;
  • the processing unit is further configured to keep the BGP session unchanged;
  • the processing unit is further configured to determine data of the current interaction data according to data parameters of the current interaction data of the BGP session. Whether the priority is high priority, and the data parameters include data traffic and / or data importance;
  • the processing unit is further configured to keep the BGP session unchanged;
  • the processing unit is further configured to interrupt the BGP session.
  • the transceiver unit is further configured to receive a third interface address from a third inline interface of the second node;
  • the processing unit is further configured to detect whether to generate a second interface address of its second inline interface according to an automatic address generation mechanism, and whether to obtain a second interface address alias;
  • the processing unit is further configured to trigger the BGP session establishment module to enable the BGP session establishment module Establishing a BGP session between the second inline interface and the third inline interface according to the third interface address.
  • BGP sessions it is not necessary to distinguish BGP sessions. For example, if the third inline interface in the second node only needs to establish a BGP session with the second inline interface in the first node, there is no need to establish a BGP session between the third inline interface and the second inline interface. Make a distinction. In this case, a BGP session between the second inline interface and the third inline interface may be established through the foregoing embodiment.
  • a network device is also disclosed and used as the second node.
  • the network device is applied to an underlay network of a data center network DCN.
  • the underlay network of the DCN includes a first node and a second node.
  • the network device disclosed in the embodiment of the present application includes a processing unit 210 and a transceiver unit 220.
  • the processing unit 210 is configured to generate a first interface address of a first inline interface of itself according to an automatic address generation mechanism, and obtain a first interface address alias of the first inline interface;
  • the transceiver unit 220 is configured to transmit the first interface address and the first interface address alias to the first node;
  • the first inline interface of the second node is an internal interconnection interface of the DCN's underlying network.
  • the interface address of the first inline interface automatically generated by the second node may be an LLA or ULA that complies with IPv6.
  • LLA Low-latency Integrated Circuit
  • ULA User Service
  • IPv6 IP Security
  • the network device disclosed in the embodiments of the present application only needs to configure an interface address alias for the second inline interface that matches the first inline interface to establish a BGP session.
  • the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the processing unit is further configured to obtain a first autonomous system to which the first node belongs.
  • An autonomous system number; the transceiver unit is further configured to transmit the first autonomous system number to the first node.
  • the processing unit is further configured to regenerate the first interface address of the first inline interface
  • the transceiver unit is further configured to transmit the first interface address alias and the regenerated first interface address to the first node.
  • the transceiver unit is further configured to: When the first autonomous system number changes, the changed first autonomous system number is transmitted to the first node.
  • FIG. 10 shows a possible structural diagram of a network device as a first node involved in the foregoing embodiment.
  • the first node is applied to the DCN's Underlay network and includes: a main control board 310, an interface board 330, a switching network board 320, and an interface board 340.
  • the main control board 310 is used to perform functions such as system management, equipment maintenance, and protocol processing.
  • the switching network board 320 is used to complete data exchange between interface boards (the interface board is also called a line card or a service board).
  • the interface boards 330 and 340 are used to provide various service interfaces (for example, an Ethernet interface, a POS interface, etc.) and implement data packet forwarding.
  • the main control board 310, the interface boards 330 and 340, and the switching network board 320 are connected to the system backplane through a system bus to achieve intercommunication.
  • the central processing unit 331 on the interface board 330 is used to control and manage the interface board and communicate with the central processing unit 311 on the main control board 310.
  • the first node receives the first interface address and the first interface address alias from the first inline interface of the second node, and may also receive the first autonomous system number of the first autonomous system to which the second node belongs.
  • the inline interface of the first node can establish a BGP session with the inline interface of the second node.
  • the inline interface may be a physical interface and / or a logical interface.
  • the first node receives the message information transmitted by the second node from the physical interface card 333 (the message information is the first interface address and the first interface address alias of the first inline interface, and may also Including the first autonomous system number of the first autonomous system to which the second node belongs), and the physical interface card 333 sends the received message information to the network processor 332, and the network processor 332 according to the message information
  • the destination address (which is the IP address of the first node) searches the forwarding entry memory 334, and the matching result indicates that it is a local message. Therefore, the network processor 332 performs the operation of establishing a BGP session performed by the first node disclosed in the foregoing embodiment of the present application. For specific operations, refer to the related descriptions above, and details are not described herein again.
  • the first node receives the message information transmitted by the second node through the main control board 310 (the message information is the first interface address and the first interface address alias of the first inline interface) Moreover, the first autonomous system number of the first autonomous system to which the second node belongs may also be included, and the message information received by the main control board 310 is sent to the central processor 311 of the control plane. Therefore, the central processing unit 311 on the main control board 310 performs the operation of establishing a BGP session performed by the first node disclosed in the foregoing embodiments of the present application. For specific operations, refer to the related descriptions above, and details are not described herein again. .
  • the operation on the interface board 340 in the embodiment of the present invention is consistent with the operation of the interface board 330, and for the sake of brevity, details are not described again.
  • the first node in the embodiment of the present invention may correspond to the network device in the foregoing embodiment of the BGP session establishment method, and each module in the first node and the other operations and / or functions described above are implemented to implement FIG. 2 respectively.
  • Various steps and methods implemented by the network device in the embodiments corresponding to FIG. 3, FIG. 5, and FIG. 6 are omitted here for brevity.
  • the main control board may have one or more. When there are multiple, the main control board and the standby main control board may be included. There may be one or more interface boards. The stronger the data processing capability of the first node, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. The switching network board may not be available, or there may be one or more, and when there are multiple, the load sharing redundant backup can be implemented together. Under the centralized forwarding architecture, the first network device may not need to exchange the network board, and the interface board is responsible for the service data processing function of the entire system.
  • the first network device may have at least one switching network board, and the data exchange between multiple interface boards is realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the first network device in the distributed architecture are greater than those in the centralized architecture.
  • the form of the first node may also be only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on the board.
  • the central processor and the main board of the interface board The central processing unit on the control board can be combined into one central processing unit on the board and perform the functions of the two superimposed.
  • This type of equipment has low data exchange and processing capabilities (for example, low-end switches or routers, etc. Internet equipment). Which architecture is used depends on the specific network deployment scenario and is not limited here.
  • FIG. 11 illustrates a possible structural diagram of a network device as a second node involved in the foregoing embodiment.
  • the second node is applied to the DCN's Underlay network and includes: a main control board 410, an interface board 430, a switching network board 420, and an interface board 440.
  • the main control board 410 is used to perform functions such as system management, equipment maintenance, and protocol processing.
  • the switching network board 420 is used to complete data exchange between interface boards (the interface board is also called a line card or a service board).
  • the interface boards 430 and 440 are used to provide various service interfaces (for example, an Ethernet interface, a POS interface, etc.) and implement data packet forwarding.
  • the main control board 410, the interface boards 430 and 440, and the switching network board 420 are connected to the system backplane through a system bus to achieve intercommunication.
  • the central processing unit 431 on the interface board 430 is used to control and manage the interface board and communicate with the central processing unit 411 on the main control board 410.
  • the second node can obtain the first interface address of the first inline interface and the first interface address alias of the first inline interface, and can also obtain the first autonomous system number of the first autonomous system to which the second node belongs.
  • the inline interface of the first node can establish a BGP session with the inline interface of the second node.
  • the inline interface may be a physical interface and / or a logical interface.
  • the second node If the inline interface is a physical interface, the second node generates message information through the network processor 432 (the message information is the first interface address and the first interface address alias of the first inline interface, and may further include The first autonomous system number of the first autonomous system to which the second node belongs) is transmitted to the second node through the physical interface card 433, so that the second node establishes a BGP session. That is, the network processor 432 performs the operations of the sending interface address and the alias performed by the second node disclosed in the foregoing embodiments of the present application. For specific operations, refer to the related descriptions above, and details are not described herein again.
  • the second node if the inline interface is a logical interface, the second node generates message information through the central processing unit 411 on the main control board 410 (the message information is the first interface address and the first inline interface of the first inline interface).
  • the interface address alias may further include the first autonomous system number of the first autonomous system to which the second node belongs, and then the packet is newly transmitted to the second node through the main control board, so that the second node establishes a BGP session. That is, the central processing unit 411 performs the operations of the sending interface address and the alias performed by the second node disclosed in the foregoing embodiments of the present application. For specific operations, refer to the related descriptions above, and details are not described herein again.
  • the operation on the interface board 440 in the embodiment of the present invention is consistent with the operation of the interface board 430, and for the sake of brevity, details are not described again.
  • the second node in the embodiment of the present invention may correspond to the network device in the foregoing sending interface address and alias method embodiment, and each module in the first node and the other operations and / or functions described above are respectively implemented to implement the diagram. The various steps and methods implemented by the network device in the embodiment corresponding to 7 are not repeated here for brevity.
  • the main control board may have one or more. When there are multiple, the main control board and the standby main control board may be included. There may be one or more interface boards. The stronger the data processing capability of the first node, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. The switching network board may not be available, or there may be one or more, and when there are multiple, the load sharing redundant backup can be implemented together. Under the centralized forwarding architecture, the first network device may not need to exchange the network board, and the interface board is responsible for the service data processing function of the entire system.
  • the first network device may have at least one switching network board, and the data exchange between multiple interface boards is realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the first network device in the distributed architecture are greater than those in the centralized architecture.
  • the form of the second node may also be only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on the one board.
  • the central processor and the main board of the interface board The central processing unit on the control board can be combined into one central processing unit on the board and perform the functions of the two superimposed.
  • This type of equipment has low data exchange and processing capabilities (for example, low-end switches or routers, etc. Internet equipment). Which architecture is used depends on the specific network deployment scenario and is not limited here.
  • FIG. 12 shows a possible schematic structural diagram of a network device as a first node involved in the foregoing embodiment.
  • the network device is applied to a lower layer network of a data center network DCN, and the lower layer network of the DCN includes the First node and second node.
  • the network device includes a transceiver 510 and a processor 520. Further, the network device may further include a random access memory 530, a read-only memory 540, and a bus 550.
  • the processor 520 is coupled to the receiver 510, the random access memory 530, and the read-only memory 540 through a bus 550, respectively.
  • the basic input output system or the bootloader boot system in the embedded system which is solidified in the read-only memory 540 is used to start the network device serving as the first node to enter the normal operation status.
  • the application program and the operating system are run in the random access memory 530, so that:
  • a transceiver configured to receive a first interface address and a first interface address alias from a first inline interface of the second node, where the first inline interface is an inline interface of the second node;
  • the second inline interface of the first node and the first inline interface of the second node are internally interconnected interfaces of the DCN's underlying network.
  • the network device in this embodiment of the present invention may correspond to the first node in the embodiments corresponding to FIG. 2, FIG. 3, FIG. 5, and FIG. 6, and the processor 520, the transceiver 510, and the like in the network device may implement The functions of the network device and / or various steps and methods implemented in the embodiments corresponding to FIG. 2, FIG. 3, FIG. 5, and FIG. 6. For brevity, I will not repeat them here.
  • this embodiment may also be a network device implemented based on a universal physical server in combination with Network Function Virtualization (NFV) technology.
  • the network device is a virtual network device (such as a virtual host or a virtual router). Or virtual switch).
  • the virtual network device may be a virtual machine (English: Virtual Machine, VM), and the virtual machine is deployed on a hardware device (for example, a physical server).
  • Virtual machine refers to a complete computer system with complete hardware system functions and running in a completely isolated environment simulated by software.
  • FIG. 13 shows a possible structural diagram of a network device as a second node involved in the foregoing embodiment, and the network device is applied to a lower layer network of a data center network DCN, where the lower layer network of the DCN includes the First node and second node.
  • the network device includes a transceiver 610, a processor 620, a random access memory 630, a read-only memory 640, and a bus 650.
  • the processor 620 is coupled to the receiver 610, the random access memory 630, and the read-only memory 640 through a bus 650, respectively.
  • the second network device 600C when the network device needs to be run, the second network device 600C is booted into a normal operating state by booting through a basic input / output system fixed in the read-only memory 640 or a bootloader in an embedded system. After the second network device 600C enters a normal operating state, the application program and the operating system are run in the random access memory 630, so that:
  • a processor 620 configured to generate a first interface address of a first inline interface of the processor according to an automatic address generation mechanism, and obtain a first interface address alias of the first inline interface;
  • a transceiver 610 configured to transmit the first interface address and the first interface address alias to the first node
  • the first inline interface of the second node is an internal interconnection interface of the DCN's underlying network.
  • the network device in the embodiment of the present invention may correspond to the second node in the embodiment corresponding to FIG. 7 described above, and the processor 620, the transceiver 610, and the like in the network device may implement the For the sake of brevity, functions and / or various steps and methods implemented by the second node will not be repeated here.
  • this embodiment may also be a network device implemented based on a universal physical server combined with Network Function Virtualization (NFV) technology.
  • the network device is a virtual network device (such as a virtual host, virtual Router or virtual switch).
  • the virtual network device may be a virtual machine (English: Virtual Machine, VM) running a program for sending an announcement message function, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • Virtual machine refers to a complete computer system with complete hardware system functions and running in a completely isolated environment simulated by software.
  • the embodiment of the present application further provides a computer storage medium.
  • the computer storage medium provided in any device may store a program. When the program is executed, the program may be implemented including FIG. 2, FIG. 3, FIG. 5, and FIG. 6. Some or all steps of the provided BGP session establishment method.
  • the storage medium in any device can be a magnetic disk, a compact disc, a read-only memory (English: read-only memory, referred to as ROM) or a random access memory (English: random access memory, referred to as RAM).
  • the processor may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory may include volatile memory (for example, random-access memory (RAM); the memory may also include non-volatile memory (for example, read-only memory) memory (ROM), flash memory (flash memory), hard disk (HDD) or solid-state drive (SSD); the memory may also include a combination of the above types of memory.
  • volatile memory for example, random-access memory (RAM)
  • non-volatile memory for example, read-only memory
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk
  • SSD solid-state drive
  • the memory may also include a combination of the above types of memory.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium provided in any device may store a program, and when the program is executed, a program including a sending interface address and an alias disclosed in FIG. 7 may be implemented. Part or all of the steps of a method.
  • the storage medium in any device can be a magnetic disk, a compact disc, a read-only memory (English: read-only memory, referred to as ROM) or a random access memory (English: random access memory, referred to as RAM).
  • the processor may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory may include volatile memory (for example, random-access memory (RAM); the memory may also include non-volatile memory (for example, read-only memory) memory (ROM), flash memory (flash memory), hard disk (HDD) or solid-state drive (SSD); the memory may also include a combination of the above types of memory.
  • volatile memory for example, random-access memory (RAM)
  • non-volatile memory for example, read-only memory
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk
  • SSD solid-state drive
  • the memory may also include a combination of the above types of memory.
  • FIG. 14 is a system diagram of a BGP session establishment system according to an embodiment of the present invention.
  • the system includes a first node 710 and a second node 720.
  • the first node 710 is any network device or virtual network device described in FIG. 2, FIG. 3, FIG. 5, and FIG. 6, and the second node 720 is the network device or virtual network device described in FIG. 7.
  • a first node receives a first interface address and a first interface address alias from a first inline interface of the second node, and the first inline interface is an inline interface of the second node
  • the first node detects whether the second interface address alias of its second inline interface matches the first interface address alias; when the second interface address alias matches the first interface address alias
  • the first node establishes a BGP session between the second inline interface and the first inline interface according to the first interface address, wherein the second inline interface of the first node communicates with all The first inline interface of the second node is interconnected.
  • the first node can receive the first interface address and the first interface address alias of the first inline interface transmitted by the second node, and detect the second interface address alias configured by the second inline interface. Whether it matches the alias of the first interface address, and if it matches, the first node establishes a BGP session between the second inline interface and the first inline interface according to the received first interface address. In this case, it is only necessary to configure a first interface address alias for the first inline interface and an interface address alias that matches the first interface address alias for the second inline interface to establish a BGP session. Compared with the prior art, the configuration operation is effectively reduced, the process of establishing a BGP session is simplified, and the time and labor are reduced, thereby improving the efficiency of establishing a BGP session.
  • the system includes the computer-readable medium described in the two embodiments, and the first node and the second node can establish a BGP session by running the computer-readable medium described in the two embodiments, and simplify the process.
  • the BGP session establishment process reduces the time and labor consumption and improves the BGP session establishment efficiency.
  • Various illustrative logic units and circuits described in the embodiments of the present application may be implemented by a general-purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices. Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • a software unit may be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may be provided in an ASIC, and the ASIC may be provided in a UE.
  • the processor and the storage medium may also be provided in different components in the UE.
  • the size of the sequence number of each process does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic.
  • the implementation process constitutes any limitation.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • 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 from a website site, computer, server, or data center Transmission by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • 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, a data center, and the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk (SSD)), and the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (Solid State Disk (SSD)
  • the technology in the embodiment of the present invention can be implemented by means of software plus a necessary universal hardware platform. Based on such an understanding, the technical solutions in the embodiments of the present invention can be embodied in the form of software products that are essentially or contribute to the existing technology.
  • the computer software product can be stored in a storage medium, such as ROM / RAM. , Magnetic disks, optical disks, etc., including a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention or certain parts of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé d'établissement d'une session BGP et d'envoi d'une adresse d'interface et d'un alias, et un dispositif de réseau. Le procédé comprend les étapes suivantes : un premier nœud reçoit une première adresse d'interface et un premier alias d'adresse d'interface d'une première interface en ligne en provenance d'un second nœud ; le premier nœud détecte si un second alias d'adresse d'interface de sa propre seconde interface en ligne correspond au premier alias d'adresse d'interface ; et lorsque le second alias d'adresse d'interface correspond au premier alias d'adresse d'interface, le premier nœud établit une session BGP entre la seconde interface en ligne et la première interface en ligne conformément à la première adresse d'interface. Dans ce cas, il suffit de configurer un premier alias d'adresse d'interface pour la première interface en ligne et de configurer, pour la seconde interface en ligne, un alias d'adresse d'interface correspondant au premier alias d'adresse d'interface pour établir une session BGP. Par comparaison à l'état de la technique, le nombre d'opérations de configuration est efficacement réduit, le processus d'établissement d'une session de BGP est simplifié, et les coûts de temps et de main d'œuvre sont réduits, de telle sorte que l'efficacité d'établissement d'une session de BGP est améliorée.
PCT/CN2019/099329 2018-08-07 2019-08-06 Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau WO2020029928A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810893296.2A CN110830598B (zh) 2018-08-07 2018-08-07 Bgp会话建立、发送接口地址和别名的方法及网络设备
CN201810893296.2 2018-08-07

Publications (1)

Publication Number Publication Date
WO2020029928A1 true WO2020029928A1 (fr) 2020-02-13

Family

ID=69414468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/099329 WO2020029928A1 (fr) 2018-08-07 2019-08-06 Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN110830598B (fr)
WO (1) WO2020029928A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629819A (zh) * 2020-12-10 2022-06-14 中移(苏州)软件技术有限公司 一种网络检测方法及装置、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114338768A (zh) * 2020-09-25 2022-04-12 华为技术有限公司 一种建立会话的方法及网络设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7702765B1 (en) * 2004-03-01 2010-04-20 Cisco Technology, Inc. Techniques for automatically creating an iBGP mesh
CN104092687A (zh) * 2014-07-14 2014-10-08 杭州华三通信技术有限公司 一种bgp会话建立方法和装置
CN104468368A (zh) * 2014-11-10 2015-03-25 杭州华三通信技术有限公司 配置bgp邻居的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030079027A1 (en) * 2001-10-18 2003-04-24 Michael Slocombe Content request routing and load balancing for content distribution networks
CN102739497B (zh) * 2012-06-07 2015-07-08 杭州华三通信技术有限公司 一种路由自动生成方法及其装置
CN103220228A (zh) * 2013-04-10 2013-07-24 杭州华三通信技术有限公司 一种bgp路由的发送方法和设备
CN107959636B (zh) * 2016-10-17 2021-01-26 新华三技术有限公司 Bgp消息的发送方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7702765B1 (en) * 2004-03-01 2010-04-20 Cisco Technology, Inc. Techniques for automatically creating an iBGP mesh
CN104092687A (zh) * 2014-07-14 2014-10-08 杭州华三通信技术有限公司 一种bgp会话建立方法和装置
CN104468368A (zh) * 2014-11-10 2015-03-25 杭州华三通信技术有限公司 配置bgp邻居的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114629819A (zh) * 2020-12-10 2022-06-14 中移(苏州)软件技术有限公司 一种网络检测方法及装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN110830598A (zh) 2020-02-21
CN110830598B (zh) 2021-10-22

Similar Documents

Publication Publication Date Title
US11050586B2 (en) Inter-cloud communication method and related device, and inter-cloud communication configuration method and related device
CN107646185A (zh) 在覆盖数据中心环境中的操作、管理和处理(oam)
WO2021047320A1 (fr) Procédé et appareil pour déterminer un trajet de transfert
EP3787232A1 (fr) Procédé, dispositif et système de configuration de réseau
CN109714238A (zh) 一种用于实现虚拟机间通信的方法及设备
CN114143283B (zh) 一种隧道自适应配置方法、装置，中心端设备及通信系统
WO2020073908A1 (fr) Procédé et dispositif pour envoyer des informations de routage
CN111614505B (zh) 报文处理的方法和网关设备
US11522754B2 (en) Systems and methods for Zero-Touch Provisioning of a switch in intermediate distribution frames and main distribution frames
WO2022105927A1 (fr) Procédé, dispositif et système de notification de capacité de traitement d'un dispositif réseau
JP2022095786A (ja) ループ回避通信方法、ループ回避通信デバイスおよびループ回避通信システム
WO2021139304A1 (fr) Procédé et dispositif d'interconnexion de multiples nuages
WO2020029928A1 (fr) Procédé d'établissement d'une session bgp et d'envoi d'une adresse d'interface et d'alias, et dispositif de réseau
US11929851B2 (en) Gateway selection method, device, and system
WO2022057810A1 (fr) Procédé de transfert de paquet de services, procédé d'envoi de politique sr, dispositif et système
US11804985B2 (en) Packet transmission method, apparatus, and system, and storage medium
US10999151B2 (en) Apparatus, system, and method for topology discovery across geographically redundant gateway devices
CN114765572A (zh) 故障处理方法、控制面网元、切换决策网元及相关设备
JP2020113836A (ja) 情報処理装置、情報処理システム、および設定プログラム
CN110545240B (zh) 基于分布式聚合系统的标签转发表的建立及报文转发方法
US20240163192A1 (en) Fault detection method, apparatus, and system
EP4149062A1 (fr) Procédé et appareil de déploiement de service de réseau virtualisé
US20240056412A1 (en) Underlay path selection in fabric/overlay access networks
WO2023088145A1 (fr) Procédé, appareil et dispositif de traitement de paquets
CN115664920A (zh) 云平台的网络通信管理方法、装置、设备及存储介质

Legal Events

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

Ref document number: 19848481

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19848481

Country of ref document: EP

Kind code of ref document: A1