PDA

View Full Version : Modem resetting problems again


Welshchris
08-02-2009, 01:55
Last weekend i had the same problem but seemed to correct itself, the problem is every few hrs my modem resets. the ready light goes out and the sync light flashes and it disconnects for about 45 secs. Anyone have any ideas from whats below?

Here is the modem error log and power levels..

Sun Feb 08 01:42:10 2009 Sun Feb 08 01:42:10 2009 Information (7)
The s/w filename specified in the config file is the same as ...
Sun Feb 08 01:42:10 2009 Sun Feb 08 01:42:10 2009 Information (7) A
software upgrade filename was specified in the config file.
Sun Feb 08 01:42:10 2009 Sun Feb 08 01:42:10 2009 Information (7)
Authorized
Sun Feb 08 01:42:10 2009 Sun Feb 08 01:42:10 2009 Information (7)
Registration complete!
Sun Feb 08 01:42:09 2009 Sun Feb 08 01:42:09 2009 Information (7) We
registered with a DOCSIS 1.0 config file!
Sun Feb 08 01:42:09 2009 Sun Feb 08 01:42:09 2009 Information (7)
Received a REG-RSP message from the CMTS...
Sun Feb 08 01:42:09 2009 Sun Feb 08 01:42:09 2009 Information (7)
Sending a REG-REQ to the CMTS...
Sun Feb 08 01:42:09 2009 Sun Feb 08 01:42:09 2009 Information (7)
CableModem SNMP configure complete
Sun Feb 08 01:42:08 2009 Sun Feb 08 01:42:08 2009 Information (7) IP
init completed ok
Sun Feb 08 01:42:08 2009 Sun Feb 08 01:42:08 2009 Information (7)
CableModem TFTP init ok
Sun Feb 08 01:42:06 2009 Sun Feb 08 01:42:06 2009 Error (4) ToD
request sent- No Response received
Sun Feb 08 01:42:06 2009 Sun Feb 08 01:42:06 2009 Information (7)
CableModem DHCP client init ok
Sun Feb 08 01:42:06 2009 Sun Feb 08 01:42:06 2009 Critical (3) DHCP
WARNING - Non-critical field invalid in response.
Sun Feb 08 01:41:59 2009 Sun Feb 08 01:41:59 2009 Information (7)
MAP w/initial maintenance region received
Sun Feb 08 01:41:59 2009 Sun Feb 08 01:41:59 2009 Information (7)
Downstream sync ok
Sun Feb 08 01:41:59 2009 Sun Feb 08 01:41:59 2009 Information (7)
Beginning initial ranging...
Sun Feb 08 01:41:59 2009 Sun Feb 08 01:41:59 2009 Information (7)
downstream time sync acquired...
Sun Feb 08 01:41:59 2009 Sun Feb 08 01:41:59 2009 Information (7)
Downstream sync ok
Sun Feb 08 01:41:58 2009 Sun Feb 08 01:41:58 2009 Information (7)
starting ds time sync acquisition...
Sun Feb 08 01:41:55 2009 Sun Feb 08 01:41:55 2009 Information (7)
MAP w/initial maintenance region received
Sun Feb 08 01:41:55 2009 Sun Feb 08 01:41:55 2009 Information (7)
Downstream sync ok
Sun Feb 08 01:41:55 2009 Sun Feb 08 01:41:55 2009 Information (7)
Beginning initial ranging...
Sun Feb 08 01:41:55 2009 Sun Feb 08 01:41:55 2009 Information (7)
downstream time sync acquired...
Sun Feb 08 01:41:55 2009 Sun Feb 08 01:41:55 2009 Information (7)
Downstream sync ok
Sun Feb 08 01:41:54 2009 Sun Feb 08 01:41:54 2009 Information (7)
starting ds time sync acquisition...
Sun Feb 08 01:41:51 2009 Sun Feb 08 01:41:51 2009 Information (7)
Locked on the downstream. Waiting for UCDs...
Sun Feb 08 01:41:51 2009 Sun Feb 08 01:41:51 2009 Information (7)
Downstream lock ok
Sun Feb 08 01:41:50 2009 Sun Feb 08 01:41:50 2009 Critical (3) SYNC
Timing Synchronization failure - Failed to acquire QAM/Q...
Sun Feb 08 01:41:45 2009 Sun Feb 08 01:41:45 2009 Information (7)
MAP w/initial maintenance region received
Sun Feb 08 01:41:45 2009 Sun Feb 08 01:41:45 2009 Information (7)
Downstream sync ok
Sun Feb 08 01:41:45 2009 Sun Feb 08 01:41:45 2009 Information (7)
Beginning initial ranging...
Sun Feb 08 01:41:45 2009 Sun Feb 08 01:41:45 2009 Information (7)
downstream time sync acquired...


Power Levels are...

Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 7
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 7.4 dBmV
Downstream SNR : 41.6 dB



Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 25800000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 47.0 dBmV
Upstream Mini-Slot Size : 2




Cable Modem Operation Configuration
Network Access : Allowed
Maximum Downstream Data Rate : 20480000
Maximum Upstream Data Rate : 768000
Maximum Upstream Channel Burst : 1600
Maximum Number of CPEs : 1
Modem Capability : Concatenation Enabled,
Fragametation Enabled, PHS Disabled

Peter_
08-02-2009, 06:54
Looks like you need to call up Tech Support and speak to them about this issue, which model is your modem.

Welshchris
08-02-2009, 13:43
its the 255

Peter_
08-02-2009, 15:19
Definitely sounds like an issue with your connection as the modem is quite new and should be fine, I would give them a ring tomorrow or try the newsgroups.

Welshchris
08-02-2009, 19:58
they reckon its a power fluctuation, but as i said to them if this is the case why does it only happen on weekends?

Peter_
08-02-2009, 20:05
they reckon its a power fluctuation, but as i said to them if this is the case why does it only happen on weekends?
A power fluctuation where on the modem or on the uBR, and what have they said is going to happen with regards a fix for you.

Welshchris
08-02-2009, 20:10
they said they will send out an engineer, they said they cannot find a fault on UBR or Modem and couldnt be a power fluctuation they didnt say where tho.

They offered me an engineer but i said its wasting my time to come out when its only happening weekends.

Peter_
08-02-2009, 20:16
they said they will send out an engineer, they said they cannot find a fault on UBR or Modem and couldnt be a power fluctuation they didnt say where tho.

They offered me an engineer but i said its wasting my time to come out when its only happening weekends.
That points towards it being high utilisation on your uBR at the weekend and they can check that if you ring tomorrow and ask them as they have records.

Welshchris
09-02-2009, 01:30
Happened AGAIN! roughtly same time as last nite!

Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) The s/w filename specified in the config file is the same as ...
Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) A software upgrade filename was specified in the config file.
Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) Authorized
Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) Registration complete!
Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) We registered with a DOCSIS 1.0 config file!
Mon Feb 09 01:26:18 2009 Mon Feb 09 01:26:18 2009 Information (7) Received a REG-RSP message from the CMTS...
Mon Feb 09 01:26:17 2009 Mon Feb 09 01:26:17 2009 Information (7) Sending a REG-REQ to the CMTS...
Mon Feb 09 01:26:17 2009 Mon Feb 09 01:26:17 2009 Information (7) CableModem SNMP configure complete
Mon Feb 09 01:26:14 2009 Mon Feb 09 01:26:14 2009 Information (7) IP init completed ok
Mon Feb 09 01:26:14 2009 Mon Feb 09 01:26:14 2009 Information (7) CableModem TFTP init ok
Mon Feb 09 01:26:13 2009 Mon Feb 09 01:26:13 2009 Error (4) ToD request sent- No Response received
Mon Feb 09 01:26:13 2009 Mon Feb 09 01:26:13 2009 Information (7) CableModem DHCP client init ok
Mon Feb 09 01:26:13 2009 Mon Feb 09 01:26:13 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Feb 09 01:26:08 2009 Mon Feb 09 01:26:08 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 01:26:07 2009 Mon Feb 09 01:26:07 2009 Information (7) Downstream sync ok
Mon Feb 09 01:26:07 2009 Mon Feb 09 01:26:07 2009 Information (7) Beginning initial ranging...
Mon Feb 09 01:26:07 2009 Mon Feb 09 01:26:07 2009 Information (7) downstream time sync acquired...
Mon Feb 09 01:26:07 2009 Mon Feb 09 01:26:07 2009 Information (7) Downstream sync ok
Mon Feb 09 01:26:06 2009 Mon Feb 09 01:26:06 2009 Information (7) starting ds time sync acquisition...
Mon Feb 09 01:26:03 2009 Mon Feb 09 01:26:03 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 01:26:01 2009 Mon Feb 09 01:26:01 2009 Information (7) Downstream sync ok
Mon Feb 09 01:26:01 2009 Mon Feb 09 01:26:01 2009 Information (7) Beginning initial ranging...
Mon Feb 09 01:26:01 2009 Mon Feb 09 01:26:01 2009 Information (7) downstream time sync acquired...
Mon Feb 09 01:26:01 2009 Mon Feb 09 01:26:01 2009 Information (7) Downstream sync ok
Mon Feb 09 01:26:01 2009 Mon Feb 09 01:26:01 2009 Information (7) starting ds time sync acquisition...
Mon Feb 09 01:25:57 2009 Mon Feb 09 01:25:57 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 01:25:57 2009 Mon Feb 09 01:25:57 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 01:25:57 2009 Mon Feb 09 01:25:57 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 01:25:55 2009 Mon Feb 09 01:25:55 2009 Information (7) Downstream sync ok
Mon Feb 09 01:25:55 2009 Mon Feb 09 01:25:55 2009 Information (7) Beginning initial ranging...
Mon Feb 09 01:25:55 2009 Mon Feb 09 01:25:55 2009 Information (7) downstream time sync acquired...
Mon Feb 09 01:25:55 2009 Mon Feb 09 01:25:55 2009 Information (7) Downstream sync ok

Welshchris
09-02-2009, 15:06
Here is what tech support came back with this morning....

I have a plausible explanation for these occurrences. Whilst viewing the
graphs displaying online device count vs time one can see that these events
occur at roughly the same time in the early morning. One can also see that a
chunk of around 30 modems will go offline from the most utilised upstream
channel and come online on the least utilised channel. Due to the uniform
nature of this and the repeated nature of it in geographically separate
areas, I believe it to be the action of automatic load balancing which is
active on most (if not all) UBRs.

Peter_
09-02-2009, 20:17
Here is what tech support came back with this morning....

I have a plausible explanation for these occurrences. Whilst viewing the
graphs displaying online device count vs time one can see that these events
occur at roughly the same time in the early morning. One can also see that a
chunk of around 30 modems will go offline from the most utilised upstream
channel and come online on the least utilised channel. Due to the uniform
nature of this and the repeated nature of it in geographically separate
areas, I believe it to be the action of automatic load balancing which is
active on most (if not all) UBRs.
Did he translate it for you or just blinded you with science:D

RAY0711
09-02-2009, 20:53
Moldova ,
" Here , Here "

Welshchris
09-02-2009, 20:54
Did he translate it for you or just blinded you with science:D

i just took it as he was talking rubbish as most of them do lol

Peter_
09-02-2009, 20:59
i just took it as he was talking rubbish as most of them do lol
Sounds like something from 2nd line support as 1st line would not such access.

Welshchris
09-02-2009, 23:30
IT happened again. This time the connection didnt reset and i was without a connection for 5 mins until i manually reset the modem myself... Here is the error log.

Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) The s/w filename specified in the config file is the same as ...
Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) A software upgrade filename was specified in the config file.
Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) Authorized
Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) Registration complete!
Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) We registered with a DOCSIS 1.0 config file!
Mon Feb 09 23:18:13 2009 Mon Feb 09 23:18:13 2009 Information (7) Received a REG-RSP message from the CMTS...
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Information (7) Sending a REG-REQ to the CMTS...
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Information (7) CableModem SNMP configure complete
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Information (7) IP init completed ok
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Information (7) CableModem TFTP init ok
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Error (4) ToD request sent- No Response received
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Information (7) CableModem DHCP client init ok
Mon Feb 09 23:18:12 2009 Mon Feb 09 23:18:12 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Feb 09 23:18:04 2009 Mon Feb 09 23:18:04 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:18:01 2009 Mon Feb 09 23:18:01 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:18:01 2009 Mon Feb 09 23:18:01 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:58 2009 Mon Feb 09 23:17:58 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:58 2009 Mon Feb 09 23:17:58 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:57 2009 Mon Feb 09 23:17:57 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:57 2009 Mon Feb 09 23:17:57 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:56 2009 Mon Feb 09 23:17:56 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:56 2009 Mon Feb 09 23:17:56 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:55 2009 Mon Feb 09 23:17:55 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:55 2009 Mon Feb 09 23:17:55 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:53 2009 Mon Feb 09 23:17:53 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:53 2009 Mon Feb 09 23:17:53 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:53 2009 Mon Feb 09 23:17:53 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:53 2009 Mon Feb 09 23:17:53 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:52 2009 Mon Feb 09 23:17:52 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:52 2009 Mon Feb 09 23:17:52 2009 Information (7) MAP w/initial maintenance region received
Mon Feb 09 23:17:49 2009 Mon Feb 09 23:17:49 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Feb 09 23:17:49 2009 Mon Feb 09 23:17:49 2009 Information (7) MAP w/initial maintenance region received

Its getting to a point where its really starting to take the micky now, they even claim they do this sort of thing everynight to everyones connections.