Method for obtaining port path and apparatus

• US 10,454,711 B2
• Filed: 08/07/2017
• Issued: 10/22/2019
• Est. Priority Date: 02/05/2015
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Wang, Yang, Yuan, Feng, Xia, Liang, Chen, Guang, Fan, Duoliang
• Primary Examiner(s): Duong, Frank
• Application Number:
  US15/670,724
• Publication Number:
  US 20170338976A1
• Time in Patent Office: 806 Days
• CPC Class Codes: H04L 12/56 Packet switching systems
• CPC Class Codes: H04L 2012/5609 Topology
• CPC Class Codes: H04L 2012/562 Routing
• CPC Class Codes: H04L 2012/5624 Path aspects, e.g. path bundling
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04L 45/488 using root node determination
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/602 Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

A method for obtaining a port path and an apparatus to improve a network capacity, where the method includes receiving, by a controller, a request message from a first server, where the request message requests port path information, and the port path information includes a port that a logical link from the first server to a second server passes through, obtaining, by the controller, a first absolute port path (APP) and a second APP according to network topology information, where the first APP includes a port that a logical link from a root node to the first server passes through, and the second APP includes a port that a logical link from the root node to the second server passes through, obtaining, by the controller, the port path information according to the first APP and the second APP, and sending the port path information to the first server.

Claims

1. A method for obtaining a port path, comprising:

receiving, by a controller, a request message from a first server, wherein the request message comprises an identifier of the first server and an identifier of a second server, wherein the request message requests port path information from the controller, and wherein the port path information comprises a port that a logical link from the first server to the second server passes through;

obtaining, by the controller, a first absolute port path (APP) and a second APP according to network topology information, the identifier of the first server, and the identifier of the second server, wherein the network topology information comprises information about a port connection between the first server and a first forwarding device configured to communicate with the first server, wherein the network topology information further comprises information about a port connection between the second server and a second forwarding device configured to communicate with the second server, wherein the first APP comprises a port that a logical link from a root node to the first server passes through, and wherein the second APP comprises a port that a logical link from the root node to the second server passes through;

obtaining, by the controller, the port path information according to the first APP and the second APP; and

sending, by the controller, the port path information to the first server.

2. The method according to claim 1, wherein obtaining the first APP and the second APP comprises:

obtaining, by the controller, information about the root node, wherein the root node is a node serving as a root of a tree, and wherein leaf nodes of the tree comprise the first forwarding device and the second forwarding device, wherein the information about the root node comprises an identifier of the root node, a seventh port number, and an eighth port number, wherein a port identified by the seventh port number is a port of the root node for communicating with the first server, and wherein a port identified by the eighth port number is a port of the root node for communicating with the second server,

obtaining, by the controller, the first APP according to the network topology information, the identifier of the first server, and the information about the root node; and

obtaining, by the controller, the second APP according to the network topology information, the identifier of the second server, and the information about the root node.

3. The method according to claim 2, wherein obtaining the first APP comprises:

obtaining, by the controller, a first APP set according to the network topology information, the identifier of the first server, and the information about the root node, wherein the first APP set comprises at least one first APP, and wherein the at least one first APP corresponds to the first server; and

selecting, by the controller, one first APP from the first APP set as the first APP.

4. The method according to claim 3, wherein selecting the one first APP from the first APP set as the first APP comprises selecting, by the controller, the first APP from the first APP set according to link status information of a logical link corresponding to the at least one first APP, wherein the link status information identifies whether congestion occurs on the logical link, and wherein the first APP does not comprise a congested link.

5. The method according to claim 3, wherein obtaining the second APP comprises:

obtaining, by the controller, a second APP set according to the network topology information, the identifier of the second server, and the information about the root node, wherein the second APP set comprises at least one second APP, and wherein the at least one second APP corresponds to the second server; and

selecting, by the controller, one second APP from the second APP set as the second APP.

6. The method according to claim 5, wherein selecting the one second APP from the second APP set as the second APP comprises selecting, by the controller, one second APP from the second APP set as the second APP according to the first APP, wherein the second APP and the first APP comprise a same port number, and wherein the same port number is the seventh port number or the eighth port number.

7. The method according to claim 5, wherein selecting the one second APP from the second APP set as the second APP comprises:

selecting, by the controller, N second APPs from the second APP set according to the first APP, wherein N is an integer greater than or equal to 1, wherein any second APP of the N second APPs and the first APP comprise a same port number, and wherein the same port number is the seventh port number or the eighth port number; and

selecting, by the controller, the second APP from the N second APPs according to link status information of a logical link corresponding to the N second APPs, wherein the link status information identifies whether congestion occurs on the logical link, and wherein the second APP does not comprise a congested link.

8. The method according to claim 1, wherein the root node is a physical node, wherein the port path information is a packet transport port path (PTPP), and wherein obtaining the port path information comprises:

removing, by the controller, a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through;

removing, by the controller, a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through;

reversing, by the controller, the third APP to obtain a reversed third APP; and

splicing, by the controller, the reversed third APP and the fourth APP to obtain the PTPP.

9. The method according to claim 1, wherein the port path information is a packet transport port path (PTPP), and wherein obtaining the port path information comprises:

removing, by the controller, a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through;

removing, by the controller, a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through;

removing, by the controller, a same prefix in the third APP and the fourth APP to obtain a fifth APP and a sixth APP, wherein the same prefix is a same port sequence comprised in the third APP and the fourth APP, wherein the fifth APP is a port sequence obtained after the same prefix is removed from the third APP, and wherein the sixth APP is a port sequence obtained after the same prefix is removed from the fourth APP;

reversing, by the controller, the fifth APP to obtain a reversed fifth APP; and

splicing, by the controller, the reversed fifth APP and the sixth APP to obtain the PTPP.

10. The method according to claim 9, wherein splicing the reversed fifth APP and the sixth APP to obtain the PTPP comprises:

splicing, by the controller, the reversed fifth APP and the sixth APP to obtain a seventh APP; and

removing, by the controller, a port in an odd-numbered location in a port sequence comprised in the seventh APP to obtain the PTPP.

11. The method according to claim 1, wherein the network topology information further comprises information about a port connection between the first forwarding device and a third forwarding device configured to communicate with the first forwarding device and the second forwarding device, and wherein the network topology information further comprises information about a port connection between the third forwarding device and the second forwarding device.

12. The method according to claim 11, further comprising:

receiving, by the controller, a first Link Layer Discovery Protocol (LLDP) message from the third forwarding device, wherein the first LLDP message comprises a third port number, a fourth port number, an identifier of the third forwarding device, and an identifier of the first forwarding device, wherein a port identified by the third port number is a port of the first forwarding device for communicating with the third forwarding device, and wherein a port identified by the fourth port number is a port of the third forwarding device for communicating with the first forwarding device;

receiving, by the controller, a second LLDP message from the third forwarding device, wherein the second LLDP message comprises a fifth port number, a sixth port number, the identifier of the third forwarding device, and an identifier of the second forwarding device, wherein a port identified by the fifth port number is a port of the third forwarding device for communicating with the second forwarding device, and wherein a port identified by the sixth port number is a port of the second forwarding device for communicating with the third forwarding device;

obtaining, by the controller, the information about the port connection between the third forwarding device and the first forwarding device according to the third port number, the fourth port number, the identifier of the third forwarding device, and the identifier of the first forwarding device comprised in the first LLDP message; and

obtaining, by the controller, the information about the port connection between the third forwarding device and the second forwarding device according to the fifth port number, the sixth port number, the identifier of the third forwarding device, and the identifier of the second forwarding device comprised in the second LLDP message.

13. The method according to claim 1, further comprising:

receiving, by the controller, a first packet from the first forwarding device, wherein the first packet comprises a first port number, the identifier of the first server, and an identifier of the first forwarding device, and wherein a port identified by the first port number is a port of the first forwarding device for communicating with the first server;

receiving, by the controller, a second packet from the second forwarding device, wherein the second packet comprises a second port number, the identifier of the second server, and an identifier of the second forwarding device, and wherein a port identified by the second port number is a port of the second forwarding device for communicating with the second server;

obtaining, by the controller, the information about the port connection between the first server and the first forwarding device according to the first port number, the identifier of the first server, and the identifier of the first forwarding device comprised in the first packet;

obtaining, by the controller, the information about the port connection between the second server and the second forwarding device according to the second port number, the identifier of the second server, and the identifier of the second forwarding device comprised in the second packet; and

obtaining, by the controller, the network topology information according to the information about the port connection between the first server and the first forwarding device and the information about the port connection between the second server and the second forwarding device.

14. The method according to claim 1, further comprising:

obtaining, by the controller, first Dynamic Host Configuration Protocol (DHCP) information allocated by the controller to the first server, wherein the first DHCP information comprises a first port number, the identifier of the first server, and an identifier of the first forwarding device, and wherein a port identified by the first port number is a port of the first forwarding device for communicating with the first server;

obtaining, by the controller, second DHCP information allocated by the controller to the second server, wherein the second DHCP information comprises a second port number, the identifier of the second server, and an identifier of the second forwarding device, and wherein a port identified by the second port number is a port of the second forwarding device for communicating with the second server;

obtaining, by the controller, the information about the port connection between the first server and the first forwarding device according to the first port number, the identifier of the first server, and the identifier of the first forwarding device comprised in the first DHCP information;

obtaining, by the controller, the information about the port connection between the second server and the second forwarding device according to the second port number, the identifier of the second server, and the identifier of the second forwarding device comprised in the second DHCP information; and

obtaining, by the controller, the network topology information according to the information about the port connection between the first server and the first forwarding device and the information about the port connection between the second server and the second forwarding device.

15. A method for obtaining a port path, the method comprising:

sending, by a first server, a request message to a controller, wherein the request message comprises an identifier of the first server and an identifier of a second server, wherein the request message requests port path information from the controller, and wherein the port path information comprises a port that a logical link from the first server to the second server passes through;

receiving, by the first server, the port path information from the controller; and

obtaining, by the first server, a packet transport port path (PTPP) according to the port path information,

wherein the PTPP is a port sequence that the logical link from the first server to the second server passes through,

wherein the port path information comprises a first absolute port path (APP) and a second APP, wherein the first APP comprises a port that a logical link from a root node to the first server passes through, wherein the second APP comprises a port that a logical link from the root node to the second server passes through,

wherein obtaining the PTPP comprises;

removing, by the first server, a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through; and

removing, by the first server, a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through,

wherein the root node is a physical node, and wherein obtaining the PTPP further comprises;

reversing, by the first server, the third APP to obtain a reversed third APP; and

splicing, by the first server, the reversed third APP and the fourth APP to obtain the PTPP, or,

wherein the root node is a physical node or a virtual node, and wherein obtaining the PTPP comprises;

removing, by the first server, a same prefix in the third APP and the fourth APP to obtain a fifth APP and a sixth APP, wherein the same prefix is a same port sequence comprised in the third APP and the fourth APP, wherein the fifth APP is a port sequence obtained after the same prefix is removed from the third APP, and wherein the sixth APP is a port sequence obtained after the same prefix is removed from the fourth APP;

reversing, by the first server, the fifth APP to obtain a reversed fifth APP; and

splicing, by the first server, the reversed fifth APP and the sixth APP to obtain the PTPP.

16. The method according to claim 15, further comprising:

adding, by the first server, the PTPP to a first packet to obtain a second packet,

wherein the first packet is a packet from the first server to the second server; and

sending, by the first server, the second packet to the second server.

17. The method according to claim 16, wherein adding the PTPP to the first packet to obtain the second packet comprises:

obtaining, by the first server, a path hop count corresponding to the PTPP, wherein a packet header of the first packet comprises a media access control (MAC) field, and wherein the path hop count identifies a location, in the PTPP, of a port that sends the second packet; and

adding, by the first server, the PTPP, the path hop count, and a type identifier to the MAC field, and

wherein the type identifier indicates that the second packet comprises the PTPP.

18. The method according to claim 16, wherein the second packet comprises a Multiprotocol Label Switching (MPLS) field, and wherein adding the PTPP to the first packet to obtain the second packet comprises adding, by the first server, the PTPP to the MPLS field to obtain the second packet.

19. The method according to claim 15, wherein splicing the reversed fifth APP and the sixth APP to obtain the PTPP comprises:

splicing, by the first server, the reversed fifth APP and the sixth APP to obtain a seventh APP; and

removing, by the first server, a port in an odd-numbered location in a port sequence comprised in the seventh APP to obtain the PTPP.

20. A controller, comprising:

a processor; and

a non-transitory computer readable medium coupled to the processor and configured to store computer-executable instructions,

wherein when executed, the computer-executable instructions cause the processor to be configured to;

receive a request message from a first server, wherein the request message comprises an identifier of the first server and an identifier of a second server, wherein the request message requests port path information from the controller, and wherein the port path information comprises a port that a logical link from the first server to the second server passes through;

obtain a first absolute port path (APP) and a second APP according to network topology information, the identifier of the first server, and the identifier of the second server, wherein the network topology information comprises information about a port connection between the first server and a first forwarding device and information about a port connection between the second server and a second forwarding device, wherein the first forwarding device communicates with the first server, wherein the second forwarding device communicates with the second server, wherein the first APP comprises a port that a logical link from a root node to the first server passes through, and wherein the second APP comprises a port that a logical link from the root node to the second server passes through;

obtain the port path information according to the first APP and the second APP; and

send the port path information to the first server.

21. The controller according to claim 20, wherein the computer-executable instructions further cause the processor to be configured to:

obtain a first Dynamic Host Configuration Protocol (DHCP) information allocated by the controller to the first server, wherein the first DHCP information comprises a first port number, the identifier of the first server, and an identifier of the first forwarding device, and wherein a port identified by the first port number is a port of the first forwarding device for communicating with the first server;

obtain a second DHCP information allocated by the controller to the second server, wherein the second DHCP information comprises a second port number, the identifier of the second server, and an identifier of the second forwarding device, and wherein a port identified by the second port number is a port of the second forwarding device for communicating with the second server;

obtain the information about the port connection between the first server and the first forwarding device according to the first port number, the identifier of the first server, and the identifier of the first forwarding device comprised in the first DHCP information;

obtain the information about the port connection between the second server and the second forwarding device according to the second port number, the identifier of the second server, and the identifier of the second forwarding device comprised in the second DHCP information; and

obtain the network topology information according to the information about the port connection between the first server and the first forwarding device and the information about the port connection between the second server and the second forwarding device.

22. The controller according to claim 20, wherein the computer-executable instructions further cause the processor to be configured to:

receive a first packet from the first forwarding device, wherein the first packet comprises a first port number, the identifier of the first server, and an identifier of the first forwarding device, and wherein a port identified by the first port number is a port of the first forwarding device for communicating with the first server;

receive a second packet from the second forwarding device, wherein the second packet comprises a second port number, the identifier of the second server, and an identifier of the second forwarding device, and wherein a port identified by the second port number is a port of the second forwarding device for communicating with the second server;

obtain the information about the port connection between the first server and the first forwarding device according to the first port number, the identifier of the first server, and the identifier of the first forwarding device comprised in the first packet;

obtain the information about the port connection between the second server and the second forwarding device according to the second port number, the identifier of the second server, and the identifier of the second forwarding device comprised in the second packet; and

obtain the network topology information according to the information about the port connection between the first server and the first forwarding device and the information about the port connection between the second server and the second forwarding device.

23. The controller according to claim 20, wherein when obtaining the first APP and the second APP, the computer-executable instructions further cause the processor to be configured to:

obtain information about the root node, wherein the root node is a node serving as a root of a tree, and wherein leaf nodes of the tree comprise the first forwarding device and the second forwarding device, wherein the information about the root node comprises an identifier of the root node, a seventh port number, and an eighth port number, wherein a port identified by the seventh port number is a port of the root node for communicating with the first server, and wherein a port identified by the eighth port number is a port of the root node for communicating with the second server;

obtain the first APP according to the network topology information, the identifier of the first server, and the information about the root node; and

obtain the second APP according to the network topology information, the identifier of the second server, and the information about the root node.

24. The controller according to claim 23, wherein when obtaining the first APP, the computer-executable instructions further cause the processor to be configured to:

obtain a first APP set according to the network topology information, the identifier of the first server, and the information about the root node, wherein the first APP set comprises at least one first APP, and wherein the at least one first APP corresponds to the first server; and

select one first APP from the first APP set as the first APP,

wherein when selecting the one first APP from the first APP set as the first APP, the computer-executable instructions further cause the processor to be configured to select the first APP from the first APP set according to link status information of a logical link corresponding to the at least one first APP,

wherein the link status information identifies whether congestion occurs on the logical link, and

wherein the first APP does not comprise a congested link.

25. The controller according to claim 24, wherein when obtaining the second APP, the computer-executable instructions further cause the processor to be configured to:

obtain a second APP set according to the network topology information, the identifier of the second server, and the information about the root node, wherein the second APP set comprises at least one second APP, and wherein the at least one second APP corresponds to the second server; and

select one second APP from the second APP set as the second APP,

wherein when selecting the one second APP from the second APP set as the second APP, the computer-executable instructions further cause the processor to be configured to select one second APP from the second APP set as the second APP according to the first APP,

wherein the second APP and the first APP comprise a same port number, and

wherein the same port number is the seventh port number or the eighth port number.

26. The controller according to claim 20, wherein the root node is a physical node, wherein the port path information is a packet transport port path (PTPP), and wherein when obtaining the port path information, the computer-executable instructions further cause the processor to be configured to:

remove a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through;

remove a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through;

reverse the third APP to obtain a reversed third APP; and

splice the reversed third APP and the fourth APP to obtain the PTPP.

27. The controller according to claim 20, wherein the port path information is a packet transport port path (PTPP), and wherein when obtaining the port path information, the computer-executable instructions further cause the processor to be configured to:

remove a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through;

remove a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through;

remove a same prefix in the third APP and the fourth APP to obtain a fifth APP and a sixth APP, wherein the same prefix is a same port sequence comprised in the third APP and the fourth APP, wherein the fifth APP is a port sequence obtained after the same prefix is removed from the third APP, and wherein the sixth APP is a port sequence obtained after the same prefix is removed from the fourth APP;

reverse the fifth APP to obtain a reversed fifth APP; and

splice the reversed fifth APP and the sixth APP to obtain the PTPP.

28. The controller according to claim 27, wherein when splicing the reversed fifth APP and the sixth APP to obtain the PTPP, the computer-executable instructions further cause the processor to be configured to:

splice the reversed fifth APP and the sixth APP to obtain a seventh APP; and

remove a port in an odd-numbered location in a port sequence comprised in the seventh APP to obtain the PTPP.

29. The controller according to claim 20, wherein the network topology information further comprises information about a port connection between a third forwarding device and the first forwarding device and information about a port connection between the third forwarding device and the second forwarding device, wherein the third forwarding device communicates with both the first forwarding device and the second forwarding device, and wherein the computer-executable instructions further cause the processor to be configured to:

receive a first Link Layer Discovery Protocol (LLDP) message from the third forwarding device, wherein the first LLDP message comprises a third port number, a fourth port number, an identifier of the third forwarding device, and an identifier of the first forwarding device, wherein a port identified by the third port number is a port of the first forwarding device for communicating with the third forwarding device, and wherein a port identified by the fourth port number is a port of the third forwarding device for communicating with the first forwarding device;

receive a second LLDP message from the third forwarding device, wherein the second LLDP message comprises a fifth port number, a sixth port number, the identifier of the third forwarding device, and an identifier of the second forwarding device, wherein a port identified by the fifth port number is a port of the third forwarding device for communicating with the second forwarding device, and wherein a port identified by the sixth port number is a port of the second forwarding device for communicating with the third forwarding device;

obtain the information about the port connection between the third forwarding device and the first forwarding device according to the third port number, the fourth port number, the identifier of the third forwarding device, and the identifier of the first forwarding device comprised in the first LLDP message; and

obtain the information about the port connection between the third forwarding device and the second forwarding device according to the fifth port number, the sixth port number, the identifier of the third forwarding device, and the identifier of the second forwarding device comprised in the second LLDP message.

30. A first server, comprising:

a processor; and

a non-transitory computer readable medium coupled to the processor and configured to store computer-executable instructions,

wherein when executed, the computer-executable instructions cause the processor to be configured to;

send a request message to a controller, wherein the request message comprises an identifier of the first server and an identifier of a second server, wherein the request message requests port path information from the controller, and wherein the port path information comprises a port that a logical link from the first server to the second server passes through;

receive the port path information from the controller; and

obtain a packet transport port path (PTPP) according to the port path information, and

wherein the PTPP is a port sequence that the logical link from the first server to the second server passes through,

wherein the port path information comprises a first absolute port path (APP) and a second APP, wherein the first APP comprises a port that a logical link from a root node to the first server passes through, wherein the second APP comprises a port that a logical link from the root node to the second server passes through, and wherein when obtaining the PTPP, the computer-executable instructions further cause the processor to be configured to;

remove a redundant portion of the first APP to obtain a third APP, wherein the redundant portion of the first APP is a portion of the first APP other than a port sequence of the first APP, and wherein the port sequence of the first APP comprises the port that the logical link from the root node to the first server passes through; and

remove a redundant portion of the second APP to obtain a fourth APP, wherein the redundant portion of the second APP is a portion of the second APP other than a port sequence of the second APP, and wherein the port sequence of the second APP comprises the port that the logical link from the root node to the second server passes through,

wherein the root node is a physical node, and wherein when obtaining the PTPP, the computer-executable instructions further cause the processor to be configured to;

reverse the third APP to obtain a reversed third APP; and

splice the reversed third APP and the fourth APP to obtain the PTPP, or,

wherein the root node is a physical node or a virtual node, and wherein when obtaining the PTPP, the computer-executable instructions further cause the processor to be configured to;

remove a same prefix in the third APP and the fourth APP to obtain a fifth APP and a sixth APP, wherein the same prefix is a same port sequence comprised in the third APP and the fourth APP, wherein the fifth APP is a port sequence obtained after the same prefix is removed from the third APP, and wherein the sixth APP is a port sequence obtained after the same prefix is removed from the fourth APP;

reverse the fifth APP to obtain a reversed fifth APP; and

splice the reversed fifth APP and the sixth APP to obtain the PTPP.

31. The first server according to claim 30, wherein the computer-executable instructions further cause the processor to be configured to:

add the PTPP to a first packet to obtain a second packet,

wherein the first packet is a packet from the first server to the second server; and

send the second packet to the second server.

32. The first server according to claim 31, wherein when adding the PTPP to the first packet to obtain the second packet, the computer-executable instructions further cause the processor to be configured to:

obtain a path hop count corresponding to the PTPP, wherein a packet header of the first packet comprises a media access control (MAC) field, and wherein the path hop count identifies a location, in the PTPP, of a port that sends the second packet; and

add the PTPP, the path hop count, and a type identifier to the MAC field, and

wherein the type identifier indicates that the second packet comprises the PTPP.

33. The first server according to claim 31, wherein the second packet comprises a Multiprotocol Label Switching (MPLS) field, and wherein when adding the PTPP to the first packet to obtain the second packet, the computer-executable instructions further cause the processor to be configured to add the PTPP to the MPLS field to obtain the second packet.

34. The first server according to claim 30, wherein when splicing the reversed fifth APP and the sixth APP to obtain the PTPP, the computer-executable instructions further cause the processor to be configured to:

splice the reversed fifth APP and the sixth APP to obtain a seventh APP; and

remove a port in an odd-numbered location in a port sequence comprised in the seventh APP to obtain the PTPP.