Method and system for inserting an openflow flow entry into a flow table using openflow protocol
A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.
1. A method for inserting an OpenFlow flow entry into a flow table using OpenFlow protocol, the method comprising:
receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field;
decoding an OpenFlow flow entry from the flow mod message;
identifying a flow table from the cookie field; and
inserting the decoded flow entry into the identified flow table.
2. The method of claim 1 , wherein the flow table is a system flow table.
3. The method of claim 1 , wherein the OpenFlow flow entry is decoded from at least one of the cookie field and additional fields of the flow mod message.
4. The method of claim 1 , wherein the OpenFlow flow entry is for a global routing service instance.
5. The method of claim 1 , wherein the OpenFlow flow entry is for all service instances facilitated across a software defined network.
6. The method of claim 1 , wherein at least some bits from the cookie field indicate a type of OpenFlow flow entry encoded in the flow mod message.
7. The method of claim 6 , wherein at least some bits from the cookie field indicate additional information of the OpenFlow flow entry.
8. A non-transitory computer-readable storage medium that stores computer readable instructions, which when executed by at least one processor, implement a method for inserting an OpenFlow flow entry into a flow table using OpenFlow protocol, the method comprising:
receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field;
decoding an OpenFlow flow entry from the flow mod message;
identifying a flow table from the cookie field; and
inserting the decoded flow entry into the identified flow table.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the flow table is a system flow table.
10. The non-transitory computer-readable storage medium of claim 8 , wherein the OpenFlow flow entry is decoded from at least one of the cookie field and additional fields of the flow mod message.
11. The non-transitory computer-readable storage medium of claim 8 , wherein the OpenFlow flow entry is for a global routing service instance.
12. The non-transitory computer-readable storage medium of claim 8 , wherein at least some bits from the cookie field indicate a type of OpenFlow flow entry encoded in the flow mod message.
13. The non-transitory computer-readable storage medium of claim 12 , wherein at least some bits from the cookie field indicate additional information of the OpenFlow flow entry.
14. An OpenFlow-enabled switch, the OpenFlow-enabled switch comprising:
an OpenFlow client configured to:
receive a flow mod message, the flow mod message including a cookie field;
decode an OpenFlow flow entry from the flow mod message;
identify a flow table from the cookie field; and
insert the decoded OpenFlow flow entry into the identified flow table.
15. The OpenFlow-enabled switch of claim 14 , wherein the flow table is a system flow table.
16. The OpenFlow-enabled switch of claim 14 , wherein the OpenFlow flow entry is decoded from at least one of the cookie field and additional fields of the flow mod message.
17. The OpenFlow-enabled switch of claim 14 , wherein the OpenFlow flow entry is for a global routing service instance.
18. The OpenFlow-enabled switch of claim 14 , wherein the OpenFlow flow entry is for a service instance identified by bits of the cookie field.
19. The OpenFlow-enabled switch of claim 14 , wherein the OpenFlow flow entry is for all service instances across an SDN.
20. The OpenFlow-enabled switch of claim 14 , wherein the cookie field is divided into a first range of bits indicating a type of OpenFlow flow entry encoded in the flow mod message and a second range of bits indicating additional information of the OpenFlow flow entry.