You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, having a table that matches on TCP/UDP packet 5-tuple of (IPv4 source address, IPv4 destination address, IPv4 protocol, TCP source port, TCP dest port), sending PacketIn message from switch to controller on a miss, and the controller responds to those messages by adding a new entry in the table that matches future packets.
The table uses the idle_timeout feature, and so notifications of entries that have not been matched for too long cause IdleTimeout notification messages to be sent to the controller, which responds to those by deleting the idle entry from the table.
For example, having a table that matches on TCP/UDP packet 5-tuple of (IPv4 source address, IPv4 destination address, IPv4 protocol, TCP source port, TCP dest port), sending PacketIn message from switch to controller on a miss, and the controller responds to those messages by adding a new entry in the table that matches future packets.
The table uses the idle_timeout feature, and so notifications of entries that have not been matched for too long cause IdleTimeout notification messages to be sent to the controller, which responds to those by deleting the idle entry from the table.
See here for some more details and discussion:
The text was updated successfully, but these errors were encountered: