Test Case Name Status 18 Pre-TRR 11 Pre-TRR 10 Pre-TRR 1 SYS06_017_Traffic Scenario 7 Failed 23 Post-TRR 13 Pre-TRR 17 Pre-TRR 2 SYS06_016_Traffic Scenario 6 Failed Sr. No.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Test Case Name Status
18 Pre-TRR
11 Pre-TRR
10 Pre-TRR
1 SYS06_017_Traffic Scenario 7 Failed
23 Post-TRR
13 Pre-TRR
17 Pre-TRR
2 SYS06_016_Traffic Scenario 6 Failed
Sr. No.
3 SYS06_015_Traffic Scenario 5 Failed
27 Post-TRR
4 SYS06_014_Traffic Scenario 4 Failed
5 SYS06_013_Traffic Scenario 3 Failed
6 SYS06_012_Traffic Scenario 2 Failed
7 SYS06_011_Traffic Scenario 1 Failed
16 Pre-TRR
8 Failed
21 Post-TRR
22 Post-TRR
SYS06_005 - UDP BI-DIRECTIONAL CONNECTIVITY CHECK
12 Pre-TRR
14 Pre-TRR
15 Pre-TRR
20 Post-TRR
24 Post-TRR
19 Pre-TRR
25 Post-TRR
26 Post-TRR
Open Idirect Issues Idirect Issues Status
Debugging this
16-06-2015-ISS-00125565-[Hub#6]:TCP Throughput Curves on Forward Link are problematic
1.05-08-15:ISS-00127508-[Hub#6][SYS06_017-Traffic Scenario 7 - FAILED]-TCP FL & RL Throughput is much lower than expectedOB: Traffic never starts on Ixia (regardless of rate)IB: Traffic decreases from 12Mbps to 0Mbps after ~7-8mins on Ixia (not tested over different rates) (NB no TCP ramp-up problem); pings on mgmt VLAN stop at the same time. This was also demonstrated using iPerf TCP using the filesize criterion (rather than duration), per FTP (cf Ixia - total throughput objective)Move to iPerf TCP on PCs. All tests with 8PSK 6/7 on V3905. Spoofing enabled with queue depth 20ms
Debugging this - iDirect have not accepted any TCP problem in OB, but recently accepted IB problem
ISS-00128935-[Hub#6]:Starting TCP Iperf Traffic causes the ACM_519 to lose the network
08-07-15:ISS-00126502-[Hub#6]:TCP Queue Depth Setting: 250 ms + Spoofing Disabled as against 20ms + Spoofing Enabled
Claimed to be fix - verifying as part of SYS06_017
19-06-2015-ISS-00125725-[Hub#6]:UDP Performance regression observed
1.05-08-15:ISS-00127503-[Hub#6][SYS06_016-Traffic Scenario 6 - FAILED]-High PER of 22.5% for UDP (RL)2.05-08-15:ISS-00127502-[Hub#6][SYS06_016-Traffic Scenario 6 - FAILED]-High PER of 5.04% for UDP (FL)3.05-08-15:ISS-00127500-[Hub#6][SYS06_016-Traffic Scenario 6 - FAILED]-Pinging stopped on SVN-3905 during IXIA throughput test4.05-08-15:ISS-00127499-[Hub#6]:Return link throughput is approx. 7.2 Mbps for PER 5.6% (a lot less than the required 12Mbps) [Test=SYS06_016-Traffic Scenario 6]Run at the target rates, and note the PER
ISS-00127610-Closed
ISS-00127610-Closed
1.06-08-15:ISS-00127554:[Hub#6][SYS06_015-Traffic Scenario 5-FAILED]-Forward link throughput is lower than expected after very slow ramp up2.06-08-15:ISS-00127553:[Hub#6][SYS06_015-Traffic Scenario 5-FAILED]-Return link throughput is lower than expected (but no ramp-up problem)3.06-08-15:ISS-00127552:[Hub#6][SYS06_015-Traffic Scenario 5-FAILED]-Forward link throughput ramp up is extremely slow
ISS-00129457-[Hub#6]:SYS06_015_Traffic Scenario 5-Failed-Upstream traffic suddenly stops after 7 minutes and pings stop on Management VLAN
06-08-15:ISS-00127569-[Hub#6][SYS06_014-Traffic Scenario 4-FAILED]-Return link data rate is close to zero
07-08-15: ISS-00127610-[Hub#6]-SYS06_013_Traffic Scenario 3 + SYS06_012_Traffic Scenario 2 + SYS06_011_Traffic Scenario 1 + SYS06_005 - UDP BI-DIRECTIONAL CONNECTIVITY CHECK - All Failed - 8PSK 6/7 Falls Out of the NetworkPointless scenario without Multicast
07-08-15: ISS-00127610-[Hub#6]-SYS06_013_Traffic Scenario 3 + SYS06_012_Traffic Scenario 2 + SYS06_011_Traffic Scenario 1 + SYS06_005 - UDP BI-DIRECTIONAL CONNECTIVITY CHECK - All Failed - 8PSK 6/7 Falls Out of the NetworkRun 50 x VoIPs on own (OK since over 1 VLAN)
ISS-00127610-Closed
ISS-00127610-Closed
Closed
Closed
1. 07-08-15: ISS-00127610-[Hub#6]-SYS06_013_Traffic Scenario 3 + SYS06_012_Traffic Scenario 2 + SYS06_011_Traffic Scenario 1 + SYS06_005 - UDP BI-DIRECTIONAL CONNECTIVITY CHECK - All Failed - 8PSK 6/7 Falls Out of the Network2. 26-06-15:ISS-00126063-[Hub#6]:[Tests:SYS06_011 et al.] failed as enabling Spoofing causes failed Ethernet Frame Check Sequence errors.Fails since multiple VoIPs don't work over a trunk on Ixia
26-06-13-ISS-00126063-[Hub#6]:[Tests:SYS06_011 et al.] failed as enabling Spoofing causes failed Ethernet Frame Check Sequence errors.
07-08-15: ISS-00127610-[Hub#6]-SYS06_013_Traffic Scenario 3 + SYS06_012_Traffic Scenario 2 + SYS06_011_Traffic Scenario 1 + SYS06_005 - UDP BI-DIRECTIONAL CONNECTIVITY CHECK - All Failed - 8PSK 6/7 Falls Out of the NetworkRun at the target rates, and note the PER
27-08-2015-ISS-00128343-[Hub#6]:ACM does not re-acquire network after falling out but immediately re-acquires after it has been power cycled
ISS-00128916-[Hub#6]:ACM does not re-acquire network after falling out but immediately re-acquires after it has been power cycled. Seen in SW 1.1.1.0.9.To make 8PSK 6/7 (required for all throughput tests SYS06_011-017) work reliably and re-acq easily without changing modcod and/or power cycling, the following settings are adopted on the Hub:Return Ref sym rate changed to 1000ksps (instead of 5875ksps)Return Ref C/N changed to 8.6dB (instead of 10.8dB) InitTxPower (for rftermtype 4001) changed to 20dBm (instead of 40dBm) - set by a process of reducing the instantaneous IB C/No until less than the "Max C/No" = "C/No??" + headroom (14.00) - M3. If more than this max C/No, the ACQ burst will be rejectedIn the iNet Profile, M1/M2/M3 changed to 0.5/0.5/0.5dB instead of 0.6/1/3dBEDK keys added on PP: atmel_auth_required=0, ucp_update_rate_s=2, ucp_out_of_network_count=10EDK keys added on terminal: ucp_out_of_network_count=10Under Terminal Components in NMS: Mobility Type=Aeronautical, Enable Doppler Prediction=disabled (only temporarily enabled but was unstable), max_burst_interval=125ms, ucp_update_rate=2
08-07-15:ISS-00126503-[Hub#6]:Link Encryption and its impact on the Throughput Performance-Clarification Required
28-05-15-ISS-00124757-[Hub#6]:8PSK 4/5- End to end Pings do not work
Closed in conjunction with Idirect
19-06-15-ISS-00125745-[Hub#6] No FTP data transfer when used with IPSec
28-08-2015-ISS-00128403-[Hub#6]:Automatic deletion of the IF_Calibration file resulting in both ACM’s falling out of the network.
ISS-00129028-[Hub#6]:ACM_501 automatically reverts to older build Idirect is trying to simulate the problem in the Lab
27-05-2015-ISS-00124697-[Hub#6]:PER is significantly higher for low packet size
ISS-00129457 [Hub#6]:Small Size Packets have higher PER (UDP/OutBound)
ISS-00129458-[Hub#6]:Small Size Packets have higher PER (UDP/InBound)
Open IXIA Issues IXIA Issues Status Core of the core of the core test cases to perform formally - prepare for Delta-TRR
Blocking factors on test cases
Closed by IXIA since works B2B
Outstanding
Closed
30-06-2015-Slow FTP/TCP ramp up issue
29-06-2015-3 Technical clarifications required to clarify test setup((a) TCP Windows Scaling and Timestamps related settings (RFC1323),(b) Compound TCP (Is it Enabled/Disabled),(c) Windows Auto-Tuning (Is it Enabled/Disabled), (d) Performance Acceleration and Throughput Acceleration)
1.05-08-2015-675562:Drill Down Views of the throughput Objective do not capture the individual throughput objectives as is captured in the Test Report (Page 4)
Closed
Closed
1.05-08-2015-675589-Clarification about the PER required for Traffic Scenario 52.06-08-2015-675723-Clarification Required on PER calculation in light of perceived discrepancies in my observations - Refer the two screenshots
1.06-08-2015-675748-Clarification required to explain why "frames sent" and "frames received" are so HIGH on L2-3 Stats for Client/Server Ports when throughput objectives shows nearly "no traffic" on the return channel
02-07-2015-IXIA not reporting MOS/Jitter info for VOIP calls when VOIP + IMIX traffic scenario is executed
High Risk Issue: Fix available only in December (Refer Karim's email about contractual obligations)
02-07-2015-IXIA not reporting MOS/Jitter info for VOIP calls when VOIP + IMIX traffic scenario is executed
High Risk Issue: Fix available only in December (Refer Karim's email about contractual obligations)
Outstanding21-07-2015-Issue while using Trunk Ports with SIP calls for Multiple VLAN's
Core of the core of the core test cases to perform formally - prepare for Delta-TRR
Blocking factors on test cases
Issue ID670919 ### ###
671033 ###671204 ###
675965 7/2/2015
675963 ###
675562 8/5/2015
675589 8/5/2015
675723 8/6/2015
675748 8/6/2015
Date opened
Date closed
DescriptionFor training material
Slow FTP/TCP ramp up issue
IXIA not reporting MOS/Jitter info for VOIP calls when VOIP + IMIX traffic scenario is executed
Issue while using Trunk Ports with SIP calls for Multiple VLAN's
Clarification about the PER required for Traffic Scenario 5
3 Technical clarifications required to clarify test setup((a) TCP Windows Scaling and Timestamps related settings (RFC1323),(b) Compound TCP (Is it Enabled/Disabled),(c) Windows Auto-Tuning (Is it Enabled/Disabled), (d) Performance Acceleration and Throughput Acceleration)
Drill Down Views of the throughput Objective do not capture the indiviual throughput objectives as is captured in the Test Report (Page 4)
Clarification Required on PER calculation in light of perceived discrepancies in my observations - Refer the two screenshots
Clarification required to explain why "frames sent" and "frames received" are so HIGH on L2-3 Stats for Client/Server Ports when throughput objectives shows nearly "no traffic" on the return channel
StatusClosed
OpenOpen
Open
Open
Open
Open
Open
Open
Related Documents
