Forwarding path determining method and apparatus
This application provides a forwarding path determining method and an apparatus. In determining a forwarding path, a second network device sends a routing update message to a first network device, where the routing update message carries a first identifier list, the first identifier list includes a binding segment identifier, and the first identifier list indicates a first forwarding path that is from the second network device to a third network device. By using the method, a second forwarding path from the first network device to the third network device is determined. According to the method provided in this application, when there is no controller or controllers cannot communicate with each other, routing advertisement of the binding end identifier is implemented, to determine a forwarding path. This helps simplify a packet forwarding control process.
1. A method, comprising:
receiving, by a first network device, a first routing update message that is a Border Gateway Protocol (BGP) routing update message, wherein the first routing update message carries one or more identifiers used to indicate a first forwarding path that is from a second network device to a third network device, and the first network device and the third network device do not belong to a same domain; and
determining, by the first network device, a second forwarding path based on the one or more identifiers carried in the first routing update message, wherein the second forwarding path is a forwarding path that is from the first network device to the third network device, and the second forwarding path comprises the first forwarding path.
2. The method according to claim 1 , wherein the method further comprises:
obtaining, by the first network device, a network requirement identifier,
wherein the second forwarding path corresponds to the network requirement identifier.
3. The method according to claim 2 ,
wherein the first routing update message further comprises the network requirement identifier, the obtaining, by the first network device, a network requirement identifier comprises:
obtaining, by the first network device, the network requirement identifier from the first routing update message; or
wherein the obtaining, by the first network device, a network requirement identifier comprises:
receiving, by the first network device, a control message sent by a controller, and wherein the control message comprises the network requirement identifier; and
obtaining, by the first network device, the network requirement identifier from the control message.
4. The method according to claim 2 , further comprising:
generating, by the first network device, a first mapping relationship, wherein
the first mapping relationship is a mapping relationship between a first binding segment identifier corresponding to the first network device and a segment identifier of the first network device; or
the first mapping relationship is a mapping relationship between a first binding segment identifier corresponding to the first network device and an identifier set, wherein the identifier set comprises a segment identifier of the first network device and the one or more identifiers.
5. The method according to claim 4 , wherein the one or more identifiers are carried in a first type length value (TLV) of the first routing update message.
6. The method according to claim 1 , wherein an identifier of the one or more identifiers comprises a segment identifier or a binding segment identifier.
7. The method according to claim 6 , wherein the segment identifier comprises a Multiprotocol Label Switching (MPLS) label or a Segment Routing over Internet Protocol version 6 (SRv6) identifier.
8. The method according to claim 1 , wherein when the first network device is a transit node in a segment routing network, the method further comprises:
sending, by the first network device, a second routing update message to a fourth network device, wherein the second routing update message carries another identifier or other identifiers.
9. The method according to claim 8 , wherein
when a first mapping relationship is a mapping relationship between a first binding segment identifier and a segment identifier of the first network device, the another identifier or other identifiers comprises the first binding segment identifier and the one or more identifiers; or
when the first mapping relationship is a mapping relationship between the first binding segment identifier and an identifier set, the another identifier or other identifiers comprises only the first binding segment identifier.
10. The method according to claim 8 , wherein the second routing update message further carries a network requirement identifier corresponding to the second forwarding path.
11. A method, comprising:
determining, by a second network device, one or more identifiers, wherein the one or more identifiers are used to indicate a first forwarding path that is from the second network device to a third network device; and
sending, by the second network device, a first routing update message that is a Border Gateway Protocol (BGP) routing update message, wherein the first routing update message carries the one or more identifiers, and a first network device and the third network device do not belong to a same domain, the first routing update message is used to determine a second forwarding path, wherein the second forwarding path is a forwarding path that is from the first network device to the third network device, and the second forwarding path comprises the first forwarding path.
12. The method according to claim 11 , further comprising:
obtaining, by the second network device, a network requirement identifier, wherein the network requirement identifier corresponds to the first forwarding path.
13. The method according to claim 12 , wherein the obtaining, by the second network device, the network requirement identifier comprises:
receiving, by the second network device, a second routing update message, and wherein the second routing update message comprises the network requirement identifier; and
obtaining, by the second network device, the network requirement identifier from the second routing update message; or
wherein the obtaining, by the second network device, the network requirement identifier comprises:
receiving, by the second network device, a control message sent by a controller, and wherein the control message comprises the network requirement identifier; and
obtaining, by the second network device, the network requirement identifier from the control message.
14. A first network device, comprising:
at least one processor;
one or more memories coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions instruct the at least one processor to cause the first network device to:
receive a first routing update message that is a Border Gateway Protocol (BGP) routing update message, wherein the first routing update message carries one or more identifiers used to indicate a first forwarding path that is from a second network device to a third network device, and the first network device and the third network device do not belong to a same domain; and
determine a second forwarding path based on the one or more identifiers carried in the first routing update message, wherein the second forwarding path is a forwarding path that is from the first network device to the third network device, and the second forwarding path comprises the first forwarding path.
15. The first network device according to claim 14 , wherein the instructions further instruct the at least one processor to cause the first network device to:
obtain a network requirement identifier, and wherein the second forwarding path corresponds to the network requirement identifier.
16. The first network device according to claim 15 ,
wherein the first routing update message further comprises the network requirement identifier, and the instructions further instruct the at least one processor to cause the first network device to:
obtain the network requirement identifier from the first routing update message; or
wherein the instructions further instruct the at least one processor to cause the first network device to:
receive a control message sent by a controller, and wherein the control message comprises the network requirement identifier; and
obtain the network requirement identifier from the control message.
17. A second network device, comprising:
at least one processor;
one or more memories coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions instruct the at least one processor to cause the second network device to:
determine one or more identifiers, wherein the one or more identifiers are used to indicate a first forwarding path that is from the second network device to a third network device; and
send a first routing update message that is a Border Gateway Protocol (BGP) routing update message, wherein the first routing update message carries the one or more identifiers, and a first network device and the third network device do not belong to a same domain, the first routing update message is used to determine a second forwarding path, wherein the second forwarding path is a forwarding path that is from the first network device to the third network device, and the second forwarding path comprises the first forwarding path.
18. The second network device according to claim 17 , wherein the instructions further instruct the at least one processor to cause the second network device to:
obtain a network requirement identifier,
wherein the network requirement identifier corresponds to the first forwarding path.
19. The second network device according to claim 18 ,
wherein that instructions further instruct the at least one processor to cause the second network device to:
receive a second routing update message, and wherein the second routing update message comprises the network requirement identifier; and
obtain the network requirement identifier from the second routing update message; or
wherein that instructions further instruct the at least one processor to cause the second network device to:
receive a control message sent by a controller, and wherein the control message comprises the network requirement identifier; and
obtain the network requirement identifier from the control message.