Quote:
Originally Posted by Masque
It is a Docsis 3 modem so it will not retune and work on a Docsis 1/2 CMTS as that is the way it is designed, it is backwards compatible with regards the speed tiers but nothing else.  |
Although strictly speaking is that not just a VM imposed restriction in both the configuraton file (viz VM choose not to release a DOCSIS1/2 file for a D3 compliant CM,which is capable of backwards compatability and operating in D1/2 mode) but more importantly because "often" the physical re-segmentation means that only a D3 compliant CMTS is available anyway?. Assuming there's no load balancing/rf switching deployed between say D3 Cisco10k's/Motorola 64ks and legacy D1/2 VXR's?
Using mixed (DOCSIS) mode on same linecard/D3 chassis is surely more inefficient in CMTS overheads so increasing the number of D1/2 (mode) CM's would be obviously counter-productive in that scenario?
Returning back to topic, interestingly as my "L"/10-1 tier provisioned on D1/2 via a current D3 compliant chassis suffices more than adequately my own usage requirements, will VM provide a config upto 20mbps on existing Ambit256 or use this "upgrade" to encourage legacy users to request D3 CM replacements in order to reduce the mixed (DOCSIS) mode overheads?
Unless "modem mode" is also released prior to that latter scenario for VMDG280 std hub then that could produce a few more "gotcha's" to add to the disgruntled number of new L/10 tier users already disappointed with that specific hub's limitations?