PDA

View Full Version : WOW Cable Modem Drops?


Liquid_ME
12-13-04, 07:05 PM
Ive been having problems with my cable modem dropping out lately. I cant figure it out. It will work for hours, the disconnect itself. The only way I can get it to reconnect is by resetting the modem itself. I ran the tcpip optimizer & heres some other info...

The modem is a Webstar DPX100 & I am running the connection thru my Linksys Etherfast BEFsr41 router...

Name
WebSTAR DPX100
Modem Serial Number
SM0929680
Cable Modem MAC Address
00:40:7B:72:0B:24
Hardware Version
2.1
Software Version
1.0.5 r1.1.3 (dpx100-v105r113.bin)
Receive Power Level
7.90 dBmV
Transmit Power Level
45.00 dBmV
Cable Modem Status
operational
-----------------------------------------------------------------
Downstream Channel
The data shown in the table below provides information about the signal coming from the network to your cable modem.

Downstream Status
Operational
Channel ID
7
Downstream Frequency
621000000 Hz
Modulation
QAM256
Bit Rate
2254438 bps
Power Level
7.88 dBmV
Signal to Noise Ratio
31 dB


Upstream Channel
The data shown in the table below provides information about the signal being transmitted to the network from your cable modem.

Upstream Status
Operational
Channel ID
3
Upstream Frequency
31500000 Hz
Bit Rate
307200 bps
Power Level
45.00 dBmV
----------------------------------------------------
2004-12-13 16:32:50 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 16:32:50 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 16:26:09 notice Interface index:4 LinkUp
2004-12-13 16:26:09 notice Interface index:3 LinkUp
2004-12-13 16:26:09 notice Interface index:2 LinkUp
2004-12-13 16:26:09 notice SNMP COLD_START(SNMP Nmaccess mode)
2004-12-13 16:26:09 notice Cable Modem Status set to Registration Complete
2004-12-13 16:26:09 information Locked Plan ID : 0 , Locked Frequency = 621000000 Hz
2004-12-13 16:26:09 information Received REG-RSP from CMTS
2004-12-13 16:26:08 information Sending Registration Request
2004-12-13 16:26:08 information Processing Configuration File
2004-12-13 16:25:55 information DHCP: IP complete
2004-12-13 16:25:55 warning DHCP WARNING - Non-critical field invalid in response
2004-12-13 16:25:55 warning DHCP WARNING - Non-critical field invalid in response
2004-12-13 16:25:55 debug DHCP_coldstart() successfully
2004-12-13 16:25:53 information Beginning ranging process. Initial Power=20.00 dBmV
2004-12-13 16:25:52 critical No Ranging Response received -T3 time-out
2004-12-13 16:25:51 critical No Ranging Response received -T3 time-out
2004-12-13 16:25:50 critical No Ranging Response received -T3 time-out
2004-12-13 16:25:50 critical No Ranging Response received -T3 time-out
2004-12-13 16:25:50 information Beginning ranging process. Initial Power= 8.00 dBmV


I think this is my problem...I had to restart right after this
2004-12-13 16:25:50 information Got a map with the new UCD change count, and changed upstream parms



2004-12-13 16:25:45 information Sync recovery loop is locked
2004-12-13 16:25:32 information Scan Downstream Frequency...
2004-12-13 16:25:29 error BPI FLASH: The Mfg CA certificate not found!
2004-12-13 16:16:43 error BPI FLASH: The Mfg CA certificate not found!
2004-12-13 16:11:12 error BPI FLASH: The Mfg CA certificate not found!
2004-12-13 15:58:38 notice Interface index:4 LinkUp
2004-12-13 15:58:38 notice Interface index:3 LinkUp
2004-12-13 15:58:38 notice Interface index:2 LinkUp
2004-12-13 15:58:38 notice SNMP COLD_START(SNMP Nmaccess mode)
2004-12-13 15:58:38 notice Cable Modem Status set to Registration Complete
2004-12-13 15:58:38 information Locked Plan ID : 0 , Locked Frequency = 621000000 Hz
2004-12-13 15:58:38 information Received REG-RSP from CMTS
2004-12-13 15:58:37 information Sending Registration Request
2004-12-13 15:58:37 information Processing Configuration File
2004-12-13 15:58:26 information DHCP: IP complete
2004-12-13 15:58:26 warning DHCP WARNING - Non-critical field invalid in response
2004-12-13 15:58:26 warning DHCP WARNING - Non-critical field invalid in response
2004-12-13 15:58:25 debug DHCP_coldstart() successfully
2004-12-13 15:58:22 critical No Ranging Response received -T3 time-out
2004-12-13 15:58:22 information Beginning ranging process. Initial Power=17.00 dBmV
2004-12-13 15:58:22 critical No Ranging Response received -T3 time-out
2004-12-13 15:58:21 critical No Ranging Response received -T3 time-out
2004-12-13 15:58:20 critical No Ranging Response received -T3 time-out
2004-12-13 15:58:20 information Beginning ranging process. Initial Power= 8.00 dBmV
2004-12-13 15:58:20 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 15:58:18 information Sync recovery loop is locked
2004-12-13 15:58:04 information Scan Downstream Frequency...
2004-12-13 15:58:01 error BPI FLASH: The Mfg CA certificate not found!
2004-12-13 14:55:26 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2004-12-13 14:53:31 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 14:53:31 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 14:49:11 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2004-12-13 14:10:50 error ToD request sent - No Response received
2004-12-13 13:53:52 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 13:53:52 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 13:33:13 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 13:33:13 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 13:11:27 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2004-12-13 13:02:55 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 13:02:55 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 12:35:35 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 12:35:35 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 12:07:27 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 12:07:27 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 05:47:03 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 05:47:03 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 05:32:42 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2004-12-13 04:24:26 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 04:24:26 information Got a map with the new UCD change count, and changed upstream parms
2004-12-13 04:10:40 notice Interface index:4 LinkUp
2004-12-13 04:10:40 notice Interface index:3 LinkUp
2004-12-13 04:10:40 notice Interface index:2 LinkUp
2004-12-13 04:10:40 notice SNMP COLD_START(SNMP Nmaccess mode)

Liquid_ME
12-13-04, 07:19 PM
Heres my routers settings:

Obtain an IP automatically

MTU: Enable Size : 1400


Network Setup
Router IP Local IP Address: 192 168.1.1.
Subnet Mask: 255.255.255.0
Network Address
Server Settings (DHCP) Local DHCP Server: Enable
Start IP Address: 192.168.1.100
Number of Address: 50
DHCP Address Range: 192.168.1.100 to 192.168.1.149
Client Lease Time: minutes (0 means one day)
--------------------------------------------------

MAC Address clone : Enable
DDNS Service: Disable

Liquid_ME
12-14-04, 10:00 AM
Anyonehave any ideas? I notice it happens most when I am downloading large files...

buckifan
12-14-04, 12:42 PM
I also have WOW. A good starting point would be a replacement CM. Call tech support and explain what is happening.

The message "Got a map with the new UCD change count, and changed upstream parms" means that the CMTS(headend) has told your CM to change some upstream parameters and the CM has complied but the changes were not what the CMTS expected. The CM is now offline and a reset temporarily fixes things.

The signal levels are OK.