HUAWEI TV Station HD Playout Solution Reliability Test Report

/ HUAWEI TV Station HD Playout Solution Reliability Test Report / CONFIDENTIAL

HUAWEI TV Station HD Playout Solution Reliability Test Report

Huawei Technologies CO., LTD.

2012-12-01 / Huawei confidential. No spreading without permission. / Page 1 of 13
/ HUAWEI TV Station HD Playout Solution Reliability Test Report / CONFIDENTIAL

Contents

1 Network Test Scenario Analysis 3

1.1 Scenario Requirements 3

1.2 Scenario Topology 3

1.3 Test Environment 4

1.4 Test Topology 5

1.5 Test Focuses 5

2 Scenario Verification 6

2.1 Verification Summary 6

2.2 Specific Use Case Verification 6

3 Summary 13

3.1 Verification Result Summary 13

2012-12-01 / Huawei confidential. No spreading without permission. / Page 1 of 13
/ HUAWEI TV Station HD Playout Solution Reliability Test Report / CONFIDENTIAL

1 Network Test Scenario Analysis

1.1 Scenario Requirements

1.2 Scenario Topology

1.3 Test Environment

1. Required Materials

In a test environment, the physical topology needs to be deployed based on the actual scenario.

Test environment / Detailed requirements
Device in the test environment / Two CE12800 devices
Three CE5800 devices
Test instrument / Ixia test instrument
Test component and material
Test tool / Ping Tester (pingtester_cn)
Other requirements / Two PCs

2. Material Version

CE12800

<CE128>display version

Huawei Versatile Routing Platform Software

VRP (R) software, Version 8.60 (CE12800 V100R002C00SPC200)

CE5800

[CE58-CSS]disk version

Huawei Versatile Routing Platform Software

VRP (R) software, Version 8.60 (CE5850 V100R002C00SPC200)

Dual-network adapter bonding (link to stacked switches)

HP Z820 intel(R)Xeon(R)E5-2609 @2.4GHz (two processors), RAM: 14 GB

Network adapter: Intel (R) 82574L Gigabit network connection (two)

Windows 7 Ultimate 32-bit

Associated devices

Dell T7600 Intel (R) Xeon (R) E5-2609 @2.4GHz (one processor) RAM: 32 GB

Network adapter: Intel (R) 82574L Gigabit network connection (two)

Windows 7 Ultimate 32-bit

1.4 Test Topology

1.5 Test Focuses

No. / Quality / Scenario Test Focus / Remarks /
1 / Function / Dual network adapters: Dual network adapters are bonded in primary/secondary mode. During a service switchover, they can ping through each other. The File Transfer Protocol-based (FTP-based) uploading and downloading services are not interrupted.
Port isolation: Port isolation is implemented by using the multiplexer (MUX) Virtual Local Area Network (VLAN) technology. Ports in a group can communicate with each other but ports in different groups cannot communication with each other. Servers can communicate with remote devices.
2 / Reliability / Link switchover time
Device switchover time

2 Scenario Verification

2.1 Verification Summary

2.2 Specific Use Case Verification

1. Port isolation/MUX-VLAN

Test Item / Port isolation
Objective / To verify that the MUX VLAN technology can be used to implement the port isolation function
Environment / See 1.4 Test Topology.
Procedure / Basic configuration:
1. On the S5800-CSS, configure MUX VLAN for VLAN10. The corresponding Group VLAN is 11, and Separate VLAN is 12. All ports can use the MUX VLAN function.
2. The following table lists the logical port mappings.
Role / Corresponding VLAN ID / Corresponding Port
MUX VLAN / 10 / 10G1/0/1, 10G2/0/1
Group VLAN / 11 / G1/0/1, G1/0/2, G2/0/1, G2/0/2
Separate VLAN / 12 / G1/0/3, G1/0/4, G2/0/3, G2/0/4
Group VLAN / 13 / G1/0/5, G1/0/6, G2/0/5, G2/0/6
MUX VLAN / 10 / G1/0/7, G1/0/8, G2/0/7, G2/0/8
Hardware mappings:
Slot / 10G1/0/1
10G2/0/1
Corresponding VLAN / VLAN 10
Slot / G1/0/1 / G1/0/3 / G1/0/5 / G1/0/7
G1/0/2 / G1/0/4 / G1/0/6 / G1/0/8
G2/0/1 / G2/0/3 / G2/0/5 / G2/0/7
G2/0/2 / G2/0/4 / G2/0/6 / G2/0/8
Corresponding VLAN / VLAN 11 / VLAN 12 / VLAN 13 / VLAN 10
Test item configurations:
1. Connectivity between ports on each local VLAN
On Group VLAN 11, respectively connect PC-1 and PC-2 to any two of four CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, and G2/0/2, and ping the two PCs. The result corresponds to expected result 1. On Group VLAN 13, respectively connect PC-1 and PC-2 to any two of four CE5800-CSS ports: G1/0/5, G1/0/6, G2/0/5, and G2/0/6, and ping the two PCs. Check whether the result corresponds to expected result 1.
On MUX VLAN 10, respectively connect PC-1 and PC-2 to any two of four CE5800-CSS ports: G1/0/7, G1/0/8, G2/0/7, and G2/0/8, and ping the two PCs. Check whether the result corresponds to expected result 2.
On Separate VLAN 13, respectively connect PC-1 and PC-2 to any two of four CE5800-CSS ports: G1/0/3, G1/0/4, G2/0/3, and G2/0/4, and ping the two PCs. Check whether the result corresponds to expected result 3.
2. Connectivity between local VLANs
Between Group VLAN 11 and Group VLAN 13, connect PC-1 to any one of four CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, and G2/0/2, connect PC-2 to any one of four CE5800-CSS ports: G1/0/5, G1/0/6, G2/0/5, and G2/0/6, and ping the two PCs. Check whether the result corresponds to expected result 4.
Between a Group VLAN and Separate VLAN, connect PC-1 to any one of eight CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, G2/0/2, G1/0/5, G1/0/6, G2/0/5, and G2/0/6, connect PC-2 to any one of four CE5800-CSS ports: G1/0/3, G1/0/4, G2/0/3, and G2/0/4, and ping the two PCs. Check whether the result corresponds to expected result 5.
Between a MUX VLAN and Group VLAN/Separate VLAN, connect PC-1 to any one of four CE5800-CSS ports: G1/0/7, G1/0/8, G2/0/7, and G2/0/8, connect PC-2 to any one of 12 CE5800-CSS ports: G1/0/1 to G1/0/6 and G2/0/1 to G2/0/4, and ping the two PCs. Check whether the result corresponds to expected result 6.
3. Connectivity between a local VLAN and remote device
Connect PC-1 to any one of 16 CE5800-CSS ports: G1/0/1 to G1/0/8 and G2/0/1 to G2/0/8, connect PC-2 to the remote CE5800-03, and ping the two PCs. Check whether the result corresponds to expected result 7.
Expected Result / 1. Connectivity between ports on each local VLAN
(1). On a Group VLAN, PCs can ping through each other.
(2). On a MUX VLAN, PCs can ping through each other.
(3). On a Separate MUX VLAN, PCs cannot ping through each other.
(4). Connectivity between local VLANs
(5). Between Group VLAN 11 and Group VLAN 13, PCs cannot ping through each other.
(6). Between a Group VLAN and Separate VLAN, PCs cannot ping through each other.
(7). Between a MUX VLAN and Group VLAN/Separate VLAN, PCs can ping through each other.
2. Connectivity between a local VLAN and remote device
(1). Between a local MUX VLAN/Group VLAN/Separate VLAN and remote device, PC on the VLAN and the remote PC can ping through each other.
Actual Result / 1. Connectivity between ports on each local VLAN: On the Group VLAN and MUX VLAN, PC-1 and PC2 can ping through each other. On the Separate VLAN, PC-1 and PC-2 cannot ping through each other. Details are as follows:
(1). On Group VLAN 11, PC-1 and PC-2 respectively connect to any two of four CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, and G2/0/2, and the two PCs can ping through each other. On Group VLAN 13, PC-1 and PC-2 respectively connect to any two of four CE5800-CSS ports: G1/0/5, G1/0/6, G2/0/5, and G2/0/6, and the two PCs can ping through each other.
(2). On MUX VLAN 10, PC-1 and PC-2 respectively connect to any two of four CE5800-CSS ports: G1/0/7, G1/0/8, G2/0/7, and G2/0/8, and the two PCs can ping through each other.
(3). On Separate VLAN 13, PC-1 and PC-2 respectively connect to any two of four CE5800-CSS ports: G1/0/3, G1/0/4, G2/0/3, and G2/0/4, and the two PCs cannot ping through each other.
2. Connectivity between local VLANs: Different Group VLANs cannot ping through each other. A Group VLAN and Separate VLAN cannot ping through each other. A Group VLAN and MUX VLAN can ping through each other. A Separate VLAN and MUX VLAN can ping through each other.
(1). Between Group VLAN 11 and Group VLAN 13, PC-1 connects to any one of four CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, and G2/0/2, PC-2 connects to any one of four CE5800-CSS ports: G1/0/3, G1/0/4, G2/0/3, and G2/0/4, and the two PCs cannot ping through each other.
(2). Between a Group VLAN and Separate VLAN, PC-1 connects to any one of eight CE5800-CSS ports: G1/0/1, G1/0/2, G2/0/1, G2/0/2, G1/0/5, G1/0/6, G2/0/5, and G2/0/6, PC-2 connects to any one of four CE5800-CSS ports: G1/0/3, G1/0/4, G2/0/3, and G2/0/4, and the two PCs cannot ping through each other.
(3). Between a MUX VLAN and Group VLAN/Separate VLAN, PC-1 connects to any one of four CE5800-CSS ports: G1/0/7, G1/0/8, G2/0/7, and G2/0/8, PC-2 connects to any one of 12 CE5800-CSS ports: G1/0/1 to G1/0/6 and G2/0/1 to G2/0/4, and the two PCs can ping through each other.
3. Connectivity between a local VLAN and remote device: A PC on a MUX VLAN/Group VLAN/Separate VLAN and a remote PC can ping through each other.
(1). On a local MUX VLAN/Group VLAN/Separate VLAN, PC-1 connects to any one of 16 CE5800-CSS ports: G1/0/1 to G1/0/8 and G2/0/1 to G2/0/8, PC-2 connects to the remote CE5800-03, and the two PCs can ping through each other.
Conclusion / OK
Test Configuration
Remarks

2. Dual network adapters (primary/secondary)

Test Item / Ping, FTP-based uploading and downloading, and copy upon the uplink interruption of dual network adapters
Objective / To verify that the ping, FTP-based uploading and downloading, and copy are not affected upon the uplink interruption of dual network adapters
Environment / See 1.4 Test Topology.
Procedure / Test item configurations:
1. Bond two network adapters of PC-1 in team1 that is in primary/secondary mode. The two network adapters correspond to port #1 and port #2. Check whether the result corresponds to expected result 1.
2. Assume that the primary link resides on port #1. Run the shutdown and undo shutdown commands. Check whether the result corresponds to expected result 2.
3. Run the shutdown command and recover the primary CE5800-CSS device. Check whether the result corresponds to expected result 3.
4. Set the mode of team1 to load balancing. Check whether the result corresponds to expected result 4.
5. Run the shutdown and undo shutdown commands on port #1 and port #2. Check whether the result corresponds to expected result 5.
6. Run the shutdown command and recover the primary CE5800-CSS device. Check whether the result corresponds to expected result 6.
Expected Result / 1. Two network adapters are enabled. One is primary and the other is secondary. After PC-1 and PC-2 are pinged, no packet loss occurs. FTP from PC-1 to PC-2 is running correctly. The MD5 value of the source file is the same as that of the target file. Files can be copied correctly.
2. After PC-1 and PC-2 are pinged, packet loss occurs. The point in time of packet loss is recorded. FTP from PC-1 to PC-2 is running correctly. Files can be copied correctly.
3. After PC-1 and PC-2 are pinged, packet loss occurs. The point in time of packet loss is recorded. FTP from PC-1 to PC-2 is running correctly. Files can be copied correctly.
4. Two network adapters are enabled and in load balancing mode. After PC-1 and PC-2 are pinged, no packet loss occurs. FTP from PC-1 to PC-2 is running correctly. Files can be copied correctly.
5. After PC-1 and PC-2 are pinged, packet loss occurs. The point in time of packet loss is recorded. FTP from PC-1 to PC-2 is running correctly. Files can be copied correctly.
6. After PC-1 and PC-2 are pinged, packet loss occurs. The point in time of packet loss is recorded. FTP from PC-1 to PC-2 is running correctly. Files can be copied correctly.
Actual Result / 1. In primary/secondary mode (adapter fault tolerance), after a port or device is shut down and recovered, packet loss occurs temporarily. For details, see the following table. After FTP-based file uploading or downloading and file copy, the MD5 value is correct.
After the primary network adapter is shut down, the average time of packet loss is 30 ms. No packet loss occurs upon a switchback.
After the secondary network adapter is shut down or a switchback is performed, no packet loss occurs.
After the CE5800-CSS is shut down, the average time of packet loss is 27 ms. The average time of packet loss is 17 ms upon a switchback.
After FTP-based file uploading or downloading and file copy, the MD5 value of the source file is the same as that of the copy. Although the network is interrupted temporarily, FTP-based file uploading or downloading and file copy are not affected.
2. In primary/secondary mode (static link aggregation), after a port or device is shut down and recovered, packet loss occurs temporarily. For details, see the following table. After FTP-based file uploading or downloading and file copy, the MD5 value is correct.
After the primary and secondary network adapters are shut down, the average time of packet loss ranges from 20 ms to 30 ms. No packet loss occurs upon a switchback.
After the CE5800-CSS is shut down, the average time of packet loss is 30 ms. The average time of packet loss is 10 ms upon a switchback.
Conclusion / OK
Test Configuration
Remarks / IP addresses of dual network adapters and MAC address

3. Link reliability

Test Item / Extent of impact on services upon faults of different links
Objective / To verify the extent of impact on services upon faults of different links
Environment / See 1.4 Test Topology.
Procedure / Test item configurations:
1. Enable the two-way unicast stream between Tport-1 and Tport-2 of the test instrument.
2. Assume that the service traffic path is from Tport-1, 5, 3, to Tport-2.
3. Switchover: Disconnect link 3. Check whether the result corresponds to expected result 1.
4. Switchback: Restore link 3. Check whether the result corresponds to expected result 2.
Expected Result / 1. The traffic of the original link (from Tport-1, 5, 3, to Tport-2) is switched to the new link (from Tport-1, 5, 7, 4, to Tport-2). The packet loss time of Tport-2 is recorded.
2. The traffic of the new link (from Tport-1, 5, 7, 4, to Tport-2) is switched back to the original link (from Tport-1, 5, 3, to Tport-2). The packet loss time of Tport-3 is recorded.
Actual Result / After the primary link is shut down, the average time of packet loss is 17 ms. The average time of packet loss is 30 ms upon a switchback.
After the secondary link is shut down or a switchback is performed, no packet loss occurs.

Traffic flow directions before and after a link fault

Conclusion / OK
Test Configuration
Remarks

4. Device reliability