cable modem does not come online. settings ok! is the same as two others that have CMTS. I've had this problem and was solved by upgrading the FPGA. anyone knows how.
I'm trying to enable BPI + with a SB5100 modem and am having a problem ... He is on the status of online (pt). Theoretically everything is ok, but do not get IP and CPE modem is not stable (reboot after some time synchronized).
He is with the firmware-ga-2_3_9_0 00_sb5100_nosh and provisioned with DOCSIS 1.1 and BPI +
I do not know exactly what might be missing ...
Does anyone have any tips about the problem?
Thanks !
We have recently upgraded our Arris C4 CMTSs from version 5 to version 7 Docsis3.0
We already have a large number of Dcosis2.0 emtas deployed and we have noticed that since the upgrade, the subscribers are not rate limited to their subscribed service according to the service flow definition in their CM config files (eg. 10M down, 20M down etc), but all emtas, irrespective of CM config, achieve download speeds in excess of 40Mbit
We have tested the same SFs in config files for Docsis3.0 emtas, and on Docsis3.0 emtas rate limiting works with no problem
After I do clear cable modem reset over ubr modem itself soft resets but ethernet connection keeps up, so the client behind the modem itself don't ask for new ip address. Same thing would happen if for some reason the modem would loose CMTS connectivity. Now the thing is after the modem comes back online cpe count on it keep saying 0. Of course we are forcing dhcp verify on cable interface
If I do it via SNMP 1.3.6.1.2.1.69.1.1.3.0 ethernet is disabled and reeanbled and client gets his ip renewed.
we are using Arris C3 CMTS and have found out that with Thomson and Motorola CMs it happens that after they have uptime of litlle more than a day, they are starting to allow data transfers more than 30 MBit in downlink (speed limit in config file is set to 10240000 in downstream and 1024000 in upstream).
If you get this error on your ARRIS CMTS 1000 or 1500:
EH_event: fatal event: CMTS hardware failure: downstream frequency could not lock
One possible cause is that it's too stinkin' cold in your Head End! I've discovered the hard way that these CMTSs do not work below 59 degrees F. Coincidently, either I do. :) I hope this helps someone. Darn it's cold in Michigan today!!!!
I just started to have modems randomly reset. It does not appear to be a upstream noise problem nor a downstream SN problem.
The only thing in the modem log is:
Unicast Ranging Received Abort Response - Re- initializing MAC
Modems are SB5101.
Anybody have some thoughts as to what could be the problem ?