Browsing by Author "Hsu, Chun-Hung"

Now showing 1 - 3 of 3

On Campus Beta Site: Architecture Designs, Operational Experience, and Top Product Defects
(2010-12-01)
Lin, Ying-Dar
;
Chen, I-Wei
;
Lin, Po-Ching
;
Chen, Chang-Sheng
;
Hsu, Chun-Hung
Testing network products in a beta site to reduce the possibility of customer found defects is a critical phase before marketing. We design and deploy an innovative beta site on the campus of National Chiao Tung University, Hsinchu, Taiwan. It can be used for developers to test and debug products, while maintaining network quality for network users. To satisfy the needs of developers, we set up environments and mechanisms, such as a variety of test zones for multiple types of products or systems under test (SUTs), remote control, degrees of traffic volume, and traffic profiling. For network users, we set up mechanisms of failure detection, notification, and recovery. The beta site network users are all volunteers. Test results show that beta site testing is good for finding stability and compatibility defects. The period starting from the beginning of a test until the next defect is found is called the time to fail (TTF). We call it converged if the TTF exceeds four weeks, and the convergence ratio is the percentage of SUTs that reach convergence. We find that the TTF increases with longer test duration, meaning that product quality improves through beta site testing. However, the convergence ratios are only 7 and 20 percent for test durations of one month and one year, respectively, meaning that few products operate faultlessly for a long duration. The convergence ratios also indicate that it takes much more time to enhance product quality to be converged. Therefore, if considering both marketing timing and product quality, one month is our suggested minimum TD for low-end and short-life-cycle products. However, we recommend one year as the minimum TD for high-end and long-life-cycle products.
On Campus IPv6 Beta Site: Requirements, Solutions, and Product Defect Evaluation
(2015-12-01)
Lin, Ying-Dar
;
Hwang, Ren-Hung
;
Kulkarni, Raghavendra
;
Tseng, Chinyang Henry
;
Hsu, Chun-Hung
Due to IPv4 address exhaustion, IPv6 deployment has been in progress and the transition from IPv4 to IPv6 has become more imminent. In this article, we report an on-campus IPv6 beta site coexisting with IPv4 networks and designed with requirements from its stakeholders. We conducted a wide range of test cases, from essential functionality tests to advanced stability tests which require complex interoperability tests and cannot be performed in laboratory testing. After one year of operation, tens of defects were observed and seven representative defects in dual-stack tunneling, IPv6 routing table, RIPng, and OSPFv3, are reported. Most defects are reproducible, and some could be fixed by proper configuration while others are caused by flaws in system design, memory management, or protocol implementation. We suggest careful configuration, overloading prevention, limited resource sharing, and robust error handling as the lessons to vendors and administrators of IPv6 devices.
On Campus IPv6 Beta Site: Requirements, Solutions, and Product Defect Evaluation
(2015-12)
Lin, Ying-Dar
;
Hwang, Ren-Hung
;
Kulkarni, Raghavendra
;
Tseng, Chinyang Henry
;
Hsu, Chun-Hung
Due to IPv4 address exhaustion, IPv6 deployment has been in progress and the transition from IPv4 to IPv6 has become more imminent. In this article, we report an on-campus IPv6 beta site coexisting with IPv4 networks and designed with requirements from its stakeholders. We conducted a wide range of test cases, from essential functionality tests to advanced stability tests which require complex interoperability tests and cannot be performed in laboratory testing. After one year of operation, tens of defects were observed and seven representative defects in dual-stack tunneling, IPv6 routing table, RIPng, and OSPFv3, are reported. Most defects are reproducible, and some could be fixed by proper configuration while others are caused by flaws in system design, memory management, or protocol implementation. We suggest careful configuration, overloading prevention, limited resource sharing, and robust error handling as the lessons to vendors and administrators of IPv6 devices.