Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: V3.9.0.0
-
Fix Version/s: V3.9.0.3, V3.9.1.0 (trunk)
-
Component/s: Core
-
Labels:
-
Account:SPC EthernetIp Core (SPCETHERNET)
Description
With V3.9 we are supporting Large Forward Open. The test procedure for LFO includes a preparatory step in which a high connection size is chosen to intentionally trigger an error saying that the supported connection size has been exceeded (0x127), followed by the maximum supported connection size. Currently we are instead responding with "invalid connection size error" 0x109, which has been deprected previously.
Description:
Expected Result: If the requested connection size for a Forward Open/Large Forward Open exceeds the maximum supported size, respond with 0x127 followed with the maximum supported connection size.
Observed Result: The device responds with 0x109 instead.
Steps to reproduce:
1. Start CT21 test tool.
2. Set a connection size of anything over 1250. (e.g. 4096)
3. Start a test run selecting only Connection Manager->Forward Open.
4. Cancel the test shortly after starting.
5. Check the first visible Error Code in the Forward Open Response in the Wireshark
Acceptance Criteria:
1. Error codes are corrected in the described error case.
2. A python test is added that executes this behavior and automates test
Attachments
Issue Links
- blocks
-
PSEISV3-940 ForwardOpen / LargeForwardOpen responds with incorrect error code when requested connection size exceeds the supported size (certification issue)
-
- Closed
-
-
PSEISV5-529 ForwardOpen / LargeForwardOpen responds with incorrect error code when requested connection size exceeds the supported size (certification issue)
-
- Closed
-
- discovered by
-
PSEIP-915 Add support for Connection Manager Large_Forward_Open Service for Originator Connections
-
- Closed
-