No.
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
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
21 Post-TRR
22 Post-TRR
Failed
12 Pre-TRR
14 Pre-TRR
15 Pre-TRR
20 Post-TRR
24 Post-TRR
19 Pre-TRR
25 Post-TRR
26 Post-TRR
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 up
2.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
Debugging this
Claimed to be fix - verifying as
part of SYS06_017
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
ISS-00127610-Closed
ISS-00127610-Closed
ISS-00127610-Closed
ISS-00127610-Closed
Closed
Closed
Closed
Closed
Closed
Outstanding
ore of the core test cases to perform formally - prepare for Delta-TRR
Date
Date
Issue ID opened closed
670919 6/29/2015 6/30/2015
671033 6/29/2015
671204 6/30/2015
675965 7/2/2015
675963 7/21/2015
675562 8/5/2015
675589 8/5/2015
675723 8/6/2015
675748 8/6/2015
Description
For training material
3 Technical clarifications required to clarify test setup((a) TCP Windows Scaling and Timestamps relate
settings (RFC1323),(b) Compound TCP (Is it Enabled/Disabled),(c) Windows Auto-Tuning (Is it
Enabled/Disabled), (d) Performance Acceleration and Throughput Acceleration)
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
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 to explain why "frames sent" and "frames received" are so HIGH on L2-3 Stats fo
Client/Server Ports when throughput objectives shows nearly "no traffic" on the return channel
Status
Closed
Open
Open
Open
Open
Open
Open
Open
Open