- 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:

- Vue.js 3.x快速入門
- C# 7 and .NET Core Cookbook
- Unreal Engine Physics Essentials
- Java 開發(fā)從入門到精通(第2版)
- Python數(shù)據(jù)分析基礎
- Mastering OpenCV Android Application Programming
- Instant Zepto.js
- jQuery從入門到精通 (軟件開發(fā)視頻大講堂)
- Python機器學習經(jīng)典實例
- 高級語言程序設計(C語言版):基于計算思維能力培養(yǎng)
- Asynchronous Android Programming(Second Edition)
- Rust游戲開發(fā)實戰(zhàn)
- Natural Language Processing with Python Quick Start Guide
- Arduino電子設計實戰(zhàn)指南:零基礎篇
- 游戲設計的底層邏輯