Automatic setup of reflector instances
A method of establishing a service operations administration and maintenance (OAM) session between an originator and a reflector in a communication network includes continuously monitoring, by the reflector, any test packets transmitted by the originator. The originator transmits to the reflector, at a time indicated by a first timestamp, a test packet. The reflector receives the test packet at a time indicated by a second timestamp and generates a unique flow identifier that identifies the reflector. The reflector transmits the test packet to the originator. The reflector assigns a sequence number to the test packet. The originator receives the test packet at a time indicated by a fourth timestamp. The reflector stores the unique flow identifier at least for the duration of the OAM session.
1. A method of establishing a service operations administration and maintenance (OAM) session between an originator and a reflector in a communication network, comprising:
continuously monitoring, by the reflector, any test protocol data units transmitted by the originator;
receiving a test protocol data unit by the reflector;
generating, by the reflector, a unique flow identifier which identifies the reflector;
relaying the test protocol data unit to the originator by the reflector; and
assigning, by the reflector, a sequence number to the test protocol data unit relayed by the reflector, and
if the reflector does not receive a subsequent test packet from the originator for a predetermined time period, discarding, by the reflector, the unique flow identifier.
2. The method of claim 1 wherein the unique flow identifier is defined automatically by the reflector; via a signaling exchange including a TWAMP control plane or via configuration methods, including CLI, web-based configuration or XML.
3. The method of claim 1 wherein the unique flow identifier is created using various methods, including pair of MAC addresses, unique OAM protocol identifier, using additional OAM fields, IPv4 data or IPv6 data.
4. The method of claim 1 wherein the unique flow identifier is generated without a setup exchange, explicit negotiation or preliminary configuration steps between the originator and the reflector.
5. The method of claim 1 , wherein the reflector includes a first incarnation number associated therewith.
6. The method of claim 5 , further comprising:
incrementing the unique flow identifier after a restart of the reflector;
assigning, by the reflector, a second incarnation number for the incremented flow identifier; and
transmitting, by the reflector to the originator, the second incarnation number.
7. The method of claim 1 further comprising detecting, by the originator, a restart of the reflector.
8. The method of claim 7 , wherein the originator detects the restart of the reflector by examining
a first, second, third and fourth timestamp; and
a sequence number.
9. The method of claim 8 , further comprising:
measuring, by the originator, a gap between the first and the second timestamp; and
if the gap exceeds a predetermined threshold, determining, by the originator, that the reflector has been restarted.
10. The method of claim 1 , wherein the reflector includes a first incarnation number associated therewith prior to a restart of the reflector and wherein the reflector includes a second incarnation number associated therewith after the restart of the reflector, the first incarnation number being different from the second incarnation number.