- Software-Defined Networking with OpenFlow(Second Edition)
- Oswald Coker Siamak Azodolmolky
- 170字
- 2021-07-02 15:50:02
Timeouts
Timeouts in a flow entry are used to determine when a flow entry should be removed from the OpenFlow table. Timeouts in a flow entry could either be an idle timeout or a hard timeout. The idle timeout is a fixed value attached to a flow entry, which tells the switch to remove the entry if no packet hits the flow for a certain time. The hard timeout is a fixed value in which the flow is removed from the device irrespective of whether a packet hits a flow or not. If the timeout is nonzero, the switch takes note of the time of arrival of the flow entry in the scenario; it is required to be deleted in the future.
The hard and idle timeout ranges from the value from 0 to 65535. A syslog is always generated when a flow gets deleted due to either a hard or idle timeout.
The following table shows the behavior of a nonzero and zero idle and hard time outgoing:

- JavaScript前端開發(fā)模塊化教程
- Raspberry Pi for Secret Agents(Third Edition)
- C/C++常用算法手冊(cè)(第3版)
- SEO實(shí)戰(zhàn)密碼
- 深入分布式緩存:從原理到實(shí)踐
- Learning Concurrency in Kotlin
- Python項(xiàng)目實(shí)戰(zhàn)從入門到精通
- 大話Java:程序設(shè)計(jì)從入門到精通
- Java圖像處理:基于OpenCV與JVM
- Extending Unity with Editor Scripting
- 從零開始學(xué)Android開發(fā)
- 人人都能開發(fā)RPA機(jī)器人:UiPath從入門到實(shí)戰(zhàn)
- Practical Time Series Analysis
- Python網(wǎng)絡(luò)運(yùn)維自動(dòng)化
- JSP程序設(shè)計(jì)與案例教程