GJR5251400R0202模塊備件,GJR5251400R0202使用速度
開放式以太網(wǎng)問題統(tǒng)計的SRTP請求數(shù)可能會有所不同當(dāng)運(yùn)行多個SRTP通道時，客戶端和服務(wù)器報告的請求數(shù)，連接之間可能有所不同。重復(fù)IP地址的報告當(dāng)CPU374檢測到PLC上的重復(fù)IP地址時，不會記錄PLC中的異常或故障網(wǎng)絡(luò)（與CPU364不同）。重復(fù)的IP地址僅在STAT F輸出中報告。如果客戶端丟失，則CPU374服務(wù)器上的TCP連接可能保持半開放狀態(tài)如果與CPU374服務(wù)器的連接打開的SRTP客戶端斷電或重置，則服務(wù)器的TCP一旦客戶端啟動
GJR5251400R0202模塊備件，連接可能會保持打開狀態(tài)很長一段時間（直到TCP保持活動計時器過期）重新啟動并嘗試重新打開通信。如果需要快速恢復(fù)連接，AUP對于TCP，應(yīng)使用keep alive將keep alive計時器調(diào)整到所需的最長時間保持?jǐn)嚅_的連接。在CPU 374之間的大PING上發(fā)生大量IP重新組裝故障當(dāng)發(fā)送的ping足夠大，需要一個以上的IP數(shù)據(jù)包（1466字節(jié)或更大）時，一個更大的將在客戶端上看到超過預(yù)期的IP ReasmFai計數(shù)，并顯示相應(yīng)的“否”數(shù)字“及時響應(yīng)”將在PING結(jié)果中看到錯誤。大型SRTP傳輸不具有相同的特性行為EGD消息始終適合單個數(shù)據(jù)包，因此不受此類問題的影響。REPP不保存中止PING的結(jié)果station manager REPP命令不會保留由于錯誤而中止的PING的結(jié)果。這個PING中止時會報告PING結(jié)果，但后續(xù)REPP命令會給出以下結(jié)果：最后一個成功終止PING。STAT C命令報告機(jī)架/插槽位置無效station manager STAT C命令報告CPU374位于機(jī)架0插槽15中，而不是機(jī)架0插槽1。多個日志事件以太網(wǎng)接口有時會生成多個異常日志事件和PLC故障表條目當(dāng)出現(xiàn)單一錯誤情況時。在重復(fù)錯誤條件下，異常日志和/或PLC故障表中可以完全填充重復(fù)的錯誤消息。間歇性SNTP失步在中等重型EGD流量負(fù)載下，以太網(wǎng)接口偶爾可能會失去與的同步其SNTP時間服務(wù)器并生成異常日志事件29，條目2=bH。
Open Ethernet Problems
Number of SRTP Requests Tallied May Vary
When running multiple SRTP channels, the number of requests, as reported by the client and the server,
may differ between the connections.
Reporting of Duplicate IP Address
The CPU374 does not log an exception or a fault in the PLC when it detects a duplicate IP address on the
network (unlike the CPU364). The duplicate IP address is reported in the STAT F output only.
TCP Connections May Remain Half-Open on CPU374 Server if Client is Lost
If an SRTP client with open connections to a CPU374 server is power cycled or reset, the server’s TCP
connection may remain open for a long time (until the TCP keep-alive timer expires) once the client is
restarted and attempts to reopen the communication. If quick recovery of the connection is needed, the AUP
for TCP keep alive should be used to adjust the keep alive timer down to the desired maximum time for
holding open the broken connection.
Large Number of IP Re-assembly Failures on Large PING Between CPU374s
When sending PINGs large enough to require more than one IP packet (1466 bytes or larger), a larger
number than expected of IP ReasmFai tallies will be seen on the client and a corresponding number of “no
timely response” errors will be seen in the PING results. Large SRTP transfers do not exhibit the same
behavior. EGD messages always fit in a single packet and thus are not subject to this kind of problem.
REPP Does Not Save Results of Aborted PING
The station manager REPP command does not retain the results of a PING that is aborted due to error. The
PING results are reported when the PING is aborted, but subsequent REPP commands give the results of
the last successfully terminated PING.
STAT C Command Reports Invalid Rack/Slot Location
The station manager STAT C command reports the CPU374 as being located in Rack 0 Slot 15 instead of
Rack 0 Slot 1.
