Method, apparatus, and system for sending packet and receiving packet to perform OAM
A method to perform operations, administrative, and maintenance (OAM) includes a controller generating a policy configuration packet, where the policy configuration packet includes OAM configuration information and information about a first path, and the information about the first path is used to identify the first path. The controller sends the policy configuration packet to a head node of the first path, where the policy configuration packet is used to indicate the head node to perform OAM on the first path based on the OAM configuration information.
1 . A controller comprising:
one or more memories configured to store programming instructions; and
at least one processor coupled to the one or more memories and configured to execute the programming instructions to cause the controller to:
generate a segment routing (SR) policy configuration packet, wherein the SR policy configuration packet comprises in-situ flow information telemetry (iFIT) configuration information, first information about a candidate path, and identification information, wherein the candidate path comprises a plurality of segments, and wherein the identification information instructs a head node of the candidate path to perform, based on the iFIT configuration information, iFIT on the candidate path comprising the plurality of segments when the candidate path is an active path; and
send the SR policy configuration packet to the head node.
2 . The controller of claim 1 , wherein the candidate path comprises a segment list identifying the plurality of segments.
3 . The controller of claim 1 , wherein the at least one processor is further configured to execute the programming instructions to cause the controller to receive an iFIT data packet, and wherein the iFIT data packet is based on performing the iFIT on the candidate path.
4 . The controller of claim 1 , wherein the SR policy configuration packet is a Border Gateway Protocol (BGP) packet or a Path Computation Element Communication Protocol (PCEP) packet.
5 . The controller of claim 1 , wherein the iFIT configuration information comprises an iFIT manner, an iFIT object, an iFIT granularity, or an iFIT frequency.
6 . The controller of claim 1 , wherein the plurality of segments identifies a path between the head node and a tail node.
7 . The controller of claim 6 , wherein each of the plurality of segments corresponds to at least one sub-type length value (TLV).
8 . The controller of claim 7 , wherein the at least one sub-TLV indicates an in-situ operations, administration and maintenance (IOAM) pre-allocated trace option sub-TLV.
9 . The controller of claim 7 , wherein the at least one sub-TLV indicates an in-situ operations, administration and maintenance (IOAM) incremental trace option sub-TLV.
10 . The controller of claim 7 , wherein the at least one sub-TLV indicates an in-situ operations, administration and maintenance (IOAM) edge-to-edge option sub-TLV.
11 . A network device comprising:
one or more memories configured to store programming instructions; and
at least one processor coupled to the one or more memories and configured to execute the programming instructions to cause the network device to:
receive a segment routing (SR) policy configuration packet, wherein the SR policy configuration packet comprises in-situ flow information telemetry (iFIT) configuration information, first information about a candidate path, and identification information, wherein the candidate path comprises a plurality of segments, and wherein the identification information instructs a head node of the candidate path to perform, based on the iFIT configuration information, iFIT on the candidate path comprising the plurality of segments when the candidate path is an active path; and
perform, based on the iFIT configuration information, iFIT on the candidate path comprising the plurality of segments when the candidate path is the active path.
12 . The network device of claim 11 , wherein the candidate path comprises a segment list identifying the plurality of segments.
13 . The network device of claim 11 , wherein the at least one processor is further configured to execute the programming instructions to cause the network device to:
obtain, based on the iFIT configuration information, iFIT execution information;
receive a first packet;
add the iFIT execution information to the first packet to obtain a second packet; and
send the second packet through the candidate path.
14 . The network device of claim 11 , wherein the at least one processor is further configured to execute the programming instructions to cause the network device to:
generate, based on the iFIT configuration information, a first packet, wherein the first packet comprises iFIT execution information; and
send the first packet through the candidate path.
15 . The network device of claim 11 , wherein the at least one processor is further configured to execute the programming instructions to cause the network device to:
perform the iFIT on the candidate path to obtain an iFIT data packet; and
send the iFIT data packet to a controller.
16 . The network device of claim 11 , wherein the SR policy configuration packet is a Border Gateway Protocol (BGP) packet or a Path Computation Element Communication Protocol (PCEP) packet.
17 . A system comprising:
a controller configured to:
generate a segment routing (SR) policy configuration packet, wherein the SR policy configuration packet comprises in-situ flow information telemetry (iFIT) configuration information, first information about a candidate path, and identification information, wherein the candidate path comprises a plurality of segments, and wherein the identification information instructs a head node of the candidate path to perform, based on the iFIT configuration information, iFIT on the candidate path comprising the plurality of segments when the candidate path is an active path; and
send the SR policy configuration packet to the head node of the candidate path; and
the head node configured to:
receive the SR policy configuration packet; and
perform, based on the iFIT configuration information, iFIT on the candidate path comprising the plurality of segments when the candidate path is the active path.
18 . The system of claim 17 , wherein the candidate path comprises a segment list identifying the plurality of segments.
19 . The system of claim 17 , wherein the SR policy configuration packet is a Border Gateway Protocol (BGP) packet or is a Path Computation Element Communication Protocol (PCEP) packet.
20 . The system of claim 17 , wherein the iFIT configuration information comprises an iFIT manner, an iFIT object, an iFIT granularity, or an iFIT frequency.