System and method for integrating ring-protocol-compatible devices into network configurations that also include non-ring-protocol compatible devices
Various systems and methods for integrating ring-protocol-compatible devices into network configurations that also include non-ring-protocol-compatible devices are disclosed. One such method, which can be performed by a network node that supports a ring protocol, involves generating a ring protocol packet and sending that ring protocol packet to a neighboring node. The ring protocol packet includes information, and the presence of this information within the packet causes a network device that receives the ring protocol packet to drop the ring protocol packet unless the network device supports a ring protocol. The information can include a reserved address (e.g., in the destination address field of the packet) as well as a ring protocol identifier.
1. A method comprising:
generating information, wherein
the information causes a network node that does not support a ring protocol to drop a ring protocol packet comprising the information, upon receiving the ring protocol packet,
the information allows another network node that supports the ring protocol to process a ring protocol packet comprising the information, upon receiving the ring protocol packet,
the information comprises a reserved address and a ring protocol identifier,
the reserved address is configured to trigger parsing of a protocol type field in the ring protocol packet, and
the protocol type field comprises the ring protocol identifier;
generating the ring protocol packet, wherein
the generating is performed by a first network node, and
the first network node supports the ring protocol;
including the information in the ring protocol packet; and
sending the ring protocol packet from the first network node to a second network node, wherein
the second network node is coupled to the first network node by a ring network, and
the second network node does not support the ring protocol.
2. The method of claim 1 , wherein
the reserved address is included in a destination address field of the ring protocol packet.
3. The method of claim 1 , further comprising:
detecting whether a neighboring node implements the ring protocol, wherein
the detecting comprises detecting whether the neighboring node sends any ring protocol packets.
4. The method of claim 3 , further comprising:
selecting to open a designated port, in response to detecting that the neighboring node does not implement the ring protocol.
5. The method of claim 1 , further comprising:
receiving a loop prevention protocol packet from a neighboring node via a first ring port; and
outputting the loop prevention protocol packet from a second ring port paired with the first ring port.
6. The method of claim 5 , wherein the loop prevention protocol packet is a spanning tree protocol packet.
7. A network node, comprising:
a ring port; and
a ring protocol module coupled to the ring port, wherein
the network node supports a ring protocol,
the ring protocol module is configured to generate information that
causes a network node that does not support the ring protocol to drop a ring protocol packet comprising the information, upon receiving the ring protocol packet, and
allows another network node that supports the ring protocol to process a ring protocol packet comprising the information, upon receiving the ring protocol packet,
the information comprises a reserved address and a ring protocol identifier,
the reserved address is configured to trigger parsing of a protocol type field in the ring protocol packet,
the protocol type field comprises the ring protocol identifier,
the ring protocol module is configured to generate the ring protocol packet to be sent via the ring port,
the ring protocol module is configured to include the information in the ring protocol packet, and
the ring protocol module is configured to send the ring protocol packet from the network node to a neighboring network node, wherein
the neighboring network node is coupled to the network node by a ring network, and
the neighboring network node does not support the ring protocol.
8. The network node of claim 7 , wherein the reserved address is included in a destination address field of the ring protocol packet.
9. The network node of claim 7 , wherein the ring protocol module is configured to:
detect that the neighboring node does not implement the ring protocol if the neighboring node fails to send any ring protocol packets within a prespecified amount of time.
10. The network node of claim 9 , wherein the network node is configured to:
receive a loop prevention protocol packet from the neighboring node via the ring port; and
output the loop prevention protocol packet from a second ring port paired with the ring port.
11. The network node of claim 10 , wherein the loop prevention protocol packet is a spanning tree protocol packet.
12. A system comprising:
means for generating information, wherein
the information causes a network node that does not support a ring protocol to drop a ring protocol packet comprising the information, upon receiving the ring protocol packet,
the information allows another network node that supports the ring protocol to process a ring protocol packet comprising the information, upon receiving the ring protocol packet,
the information comprises a reserved address and a ring protocol identifier,
the reserved address is configured to trigger parsing of a protocol type field in the ring protocol packet, and
the protocol type field comprises the ring protocol identifier;
means for generating the ring protocol packet;
means for including the information in the ring protocol packet; and
means for sending the ring protocol packet from a network node to a neighboring node, wherein
the neighboring network node does not support the ring protocol,
the network node supports the ring protocol, and
the neighboring network node is coupled to the network node by a ring network.