|
|||||||||||||||||||||||||||||||||||||||||||||||||
| Nederlands | French |
|
Docsis 3.0 Compliancy testingThe Shenick DiversifEye system offers unique capabilities for the verification and test of Docsis 3.0 systems. DiversifEye’s award winning ‘Per flow’ architecture is the only platform that delivers stateful application emulation and performance analysis on a per individual CPE, per application flow basis for DOCSIS 3.0. diversifEye is a flexible and scalable solution enabling Cable Providers emulate anything from a single flow to several thousand CPEs and flows, providing real-world usage test scenarios. diversifEye’s functionality includes both CPE and server side application emulation, providing the complete test structure for CMCI to CMTS-NSI.
Transition testing for DOCSIS 3.0 Performance test DOCSIS 3.0 through emulated CPE flows and application types connecting over DOCSIS 3.0 (I-CMTS or M-CMTS) architectures and CMs. Examine legacy issues (pre DOCSIS 3.0 CMs). Evaluate new enhancements such as multicast behaviour and potential issues such as channel cross over. Ultimately define end-user Quality of Experience using mixed IPv4 and IPv6 enabled CPEs, running multiple applications connecting to emulated application servers (voice, video, data, gaming, etc) in DOCSIS 3.0. Define performance from CMTS-NSI to CMCI.
CPE’s are shipping with IPv6 enabled today. Efficacy test DHCPv6 server address assignments for single address requests, examine DOCSIS 3.0 CM and CMTS performance under extreme conditions or large volume requests. Analyze application quality on emulated CPEs using IPV6 versus IPv4. Analyze traffic mixes, including dual stack enabled applications.
IPv4 and IPV6 enabled CPEs runnning different multicast protocols. An effective means of defining multicast capability in DOCSIS 3.0 is to test with IPv4 only, IPv6 only and then a mix of IPv4 an IPv6 CPE flows. Examine the CMTS control responsiveness to individual IGMPv3 and/or MLDv3 leave and join requests. Examine backward compatibility of IGMPv1,2 and MLDv2 multicast protocols. Multicast applications may not perform as well over legacy CMs, therefore it’s advisable to include pre-DOCSIS 3.0 CMs.
By mixing multiple emulated application traffic flows (Voice, Multicast Media, Web, Email, etc) on the CMCI, its possible to examine the effectiveness of DOCSIS 3.0 enabled CM to identify and prioritize the traffic types. CMTS testing includes large volumes of CMs with stateful traffic flows enabling performance testing of end user QoE during heavy usage periods.
Data application performance test P2P, FTP or HTPP on both the DOCSIS 3.0 Upstream and Downstream channels, effectively stretch test the channel bonding mechanism of the CMTS. Examine latency and responsiveness of the CMTS, especially to load balance under varying network conditions and loads. In addition Cable Operators should examine the conditions and performance of existing traffic flows such as voice when a CM comes online, and when channel adjustments occur.
Don’t miss the unmissable, the relevance of near live statistical analysis becomes apparent when the propagation delays associated with DOCSIS 3.0 are accounted for. Per flow analysis offers the most advanced statistical analysis possible with live results on a per second, per emulated CPE, per application flow basis.
In modern networking both good and bad/illegal traffic flows are present. DOCSIS 3.0 is no different, attack types include mail virus/worm attacks, real spam generation, DDoS attacks on servers. A serious problem in DOCSIS 3.0 is the malicious exploitation of protocols e.g. IGMP weaknesses, channel change requests and membership reports. diversifEye’s unique per flow architecture not only enables emulation of regular CPE and server side applications, but also provides for the insertion of malicious attack content.
* Bi-directional, high throughput stateful data tests
|
|
 |
|||||||
 |
 |
 |
 |
||||