HIMA F7123產(chǎn)品顏色,F7123模塊
EGD生產(chǎn)的一次延遲（以及可能的消耗）如果超過24個(gè)SRTP服務(wù)器連接已啟動(dòng)同時(shí)如果同時(shí)建立超過24個(gè)SRTP服務(wù)器連接，則EGD每次連接的生產(chǎn)可能會(huì)在第24天之后短暫延遲通電后首先進(jìn)行連接。如果EGD消耗加速度已禁用，則EGD消耗也將延遲。僅延遲在之后首次建立SRTP服務(wù)器連接時(shí)發(fā)生一次通電。前24個(gè)SRTP服務(wù)器連接沒有延遲，不再支持舊參數(shù)名稱；使用過時(shí)參數(shù)名稱將導(dǎo)致配置處理錯(cuò)誤和以太網(wǎng)異常（條目=2，條目2=06）。
HIMA F7123產(chǎn)品顏色使用過時(shí)參數(shù)名稱的現(xiàn)有AUP文件必須更改為使用新的參數(shù)名。SRTP應(yīng)用程序超時(shí)必須適應(yīng)網(wǎng)絡(luò)連接開銷SRTP通道內(nèi)的應(yīng)用超時(shí)還包括建立并維護(hù)底層網(wǎng)絡(luò)和SRTP連接。示例正在為新通道建立TCP連接，建立與遠(yuǎn)程設(shè)備的通信，以及通道期間的TCP重新傳輸操作。如果TCP連接建立或維護(hù)所需的時(shí)間超過用戶指定的通道應(yīng)用程序超時(shí)值，應(yīng)用程序?qū)l(fā)生超時(shí)。通道應(yīng)用超時(shí)是臨時(shí)錯(cuò)誤；海峽繼續(xù)運(yùn)行。操作系統(tǒng)網(wǎng)絡(luò)堆棧掛起與連接關(guān)閉后的一段時(shí)間。此時(shí)間段適用于關(guān)閉的發(fā)起方，它幾乎總是客戶端。這一次被稱為“TCP延遲期”。一旦TCP延遲期到期（60在當(dāng)前操作系統(tǒng)實(shí)現(xiàn)中，TCP資源被釋放。使用客戶端通道的應(yīng)用程序開發(fā)人員需要了解這種行為在設(shè)計(jì)邏輯時(shí)。有限數(shù)量的TCP資源分配給客戶端通道，以及如果通道連接的上下速度如此之快資源耗盡后，應(yīng)用程序可能不得不等待TCP資源釋放以建立另一個(gè)客戶端通道（COMMREQ狀態(tài)為如果當(dāng)前沒有可用的TCP資源，則返回0xA890；應(yīng)用程序應(yīng)等待并重試）。
One-time delay of EGD Production
(and possibly Consumption) if
more than 24 SRTP Server
Connections are started
simultaneously
If more than 24 SRTP Server connections are established simultaneously, EGD
Production may be briefly delayed for each connection after the 24th when the
connections are first made after power is applied. If EGD consume acceleration
has been disabled, then EGD Consumption will also be delayed. The delay only
occurs once when the SRTP Server connection is established for the first time after
Powerup. No delay is experienced for the first 24 SRTP Server connectionsThe old parameter names are no longer supported; use of an obsolete parameter
name will result in a configuration processing error and an Ethernet exception
(Entry = 2, Entry 2 = 06).
Existing AUP files using the obsolete parameter names will have to be changed to
use the new parameter names.
SRTP application timeouts must
accommodate network connection
overhead
The application timeouts within SRTP Channels also include the time needed to
establish and maintain the underlying network and SRTP connection. Examples
are establishing the TCP connection for a new channel, establishing
communication with the remote device, and TCP retransmissions during Channel
operations. If the time needed for TCP connection establishment or maintenance
exceeds the user-specified channel application timeout values, an application
timeout will occur. Channel application timeouts are temporary errors; the channel
continues to run.The OS Network stack hangs on to the TCP resources associated with a
connection for a period of time after the connection is closed. This time period
applies to the initiator of the close, which is almost always the client side. This time
is referred to as the “TCP Linger Period”. Once the TCP Linger Period expires (60
seconds in the current OS implementation), the TCP resources are released.
Application developers using client channels need to be aware of this behavior
when designing their logic. A finite number of TCP resources are allocated to client
channels, and if channel connections are brought up and down so fast that these
resources are depleted, then the application may have to wait until a TCP resource
frees up in order to establish another client channel (a COMMREQ Status of
0xA890 is returned if no TCP resources are currently available; application should
wait and try again).
