Cloud overlay for operations administration and management
Systems, methods, and computer-readable media are provided for facilitating the implementation of an operations, administration, and management (OAM) protocol in a network overlay environment. In particular, aspects of the technology facilitating the transport of OAM communications across overlay environments of different types. Aspects of the technology can include steps for receiving a packet comprising an OAM payload, and encapsulating the packet with an OAM transport header, wherein the transport header is configured to be read by transit nodes of different overlay types.
1. A method for facilitating operations administration and management (OAM) communications across different network overlay types, the method comprising:
receiving a packet comprising an OAM payload and an overlay header, the OAM payload including an OAM TLV data field, the packet being in a format that can be read by a first transit node with a first overlay type and cannot be read by a second transit node with a second overlay type, the second overlay type being different from the first overlay type; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by both the first and second transit nodes, the transport header comprising a pointer indicating a location of the OAM TLV data field within the payload within the packet; and
receiving and reading the encapsulated packet at the second transit node;
processing, in response to the reading, the encapsulated packet based on the OAM TLV data field.
2. The method of claim 1 , wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM TLV data field.
3. The method of claim 1 , further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapsulation marker comprises an OAM marker that identifies the packet as an OAM packet.
4. The method of claim 3 , wherein the OAM marker corresponds with encapsulation data corresponding with one or more of: IPv4, IPv6, segment routing with multiprotocol label switching (SR/MPLS), SRv6, and Ethernet.
5. A packet encapsulation system comprising:
at least one processor; and a memory device storing instructions that, when executed by the at least one processor, cause the system to perform operations comprising:
receiving a packet comprising an operations administration and management (OAM) payload and an overlay header, the OAM payload including an OAM TLV data field, the packet being in a format that can be read by a first transit node with a first overlay type and cannot be read by a second transit node with a second overlay type, the second overlay type being different from the first overlay type; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by both the first and second transit nodes, the transport header comprising a pointer indicating a location of the OAM TLV data field within the payload within the packet; and
receiving and reading the encapsulated packet at the second transit node;
processing, in response to the reading, the encapsulated packet based on the OAM TLV data field.
6. The system of claim 5 , wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM TLV data field.
7. The system of claim 5 , further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapsulation marker comprises an OAM marker that identifies the packet as an OAM packet.
8. The system of claim 7 , wherein the OAM marker corresponds with encapsulation data corresponding with one or more of: IPv4, IPv6, segment routing with multiprotocol label switching (SR/MPLS), SRv6, and Ethernet.
9. A non-transitory computer-readable storage medium comprising instructions stored therein, which when executed by one or more processors, cause the processors to perform operations comprising:
receiving a packet comprising an OAM payload and an overlay header, the OAM payload including an OAM TLV data field, the packet being in a format that can be read by a first transit node with a first overlay type and cannot be read by a second transit node with a second overlay type, the second overlay type being different from the first overlay type; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by both the first and second transit nodes, the transport header comprising a pointer indicating a location of the OAM TLV data field within the payload within the packet; and
receiving and reading the encapsulated packet at the second transit node;
processing, in response to the reading, the encapsulated packet based on the OAM TLV data field.
10. The storage medium of claim 9 , wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM TLV data field.
11. The storage medium of claim 9 , further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapsulation marker comprises an OAM marker that identifies the packet as an OAM packet.