republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
413
Share Topic
Posting?
Post a:
Post a:
Links: ·Cox HSI Forum FAQ ·Cox HSI forum Links ·WEB Mail ·Cable and Sat TV forum
AuthorAll Replies


liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

[AZ] degrading service

For the last several days my cox connection has been sporadic at best, especially with speeds. However, yesterday and today its bad enough that the modem is just like "hell with this" and just reboots every few minutes. I've checked the connections to the wall and the splitter in the wall and they are all gravy. I keep getting this nice info in my logs.

2012-02-10 11:01:42 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2012-02-10 11:01:40 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2012-02-10 11:01:40 6-Notice I401.0 TLV-11 - unrecognized OID
2012-02-10 11:01:40 7-Information SEC: Co-Signer CVC from configuration file was verified
2012-02-10 11:01:39 7-Information B401.0 Authorized
2012-02-10 11:01:39 7-Information REGISTRATION COMPLETE - Waiting for Operational status
2012-02-10 11:01:39 7-Information REG: Capability type isn't supported by CMTS
2012-02-10 11:01:39 7-Information Registration file - downloaded
2012-02-10 11:01:37 7-Information Trying to download Configuration file ...
2012-02-10 11:01:37 7-Information Time of day - retrieved
2012-02-10 11:01:36 7-Information DHCP - parameters acquired
2012-02-10 11:01:36 7-Information DHCP: ACK: Setting (*) CM TFTP Boot file: DEF001_vm2.0_d.cfg
2012-02-10 11:01:36 7-Information DHCP: Setting CM IP address to: 10.85.15.250
2012-02-10 11:01:33 7-Information DHCP: Setting (*) CM Syslog Server address to: 10.254.254.254
2012-02-10 11:01:33 7-Information DHCP: Setting (*) CM Time Server address to: 172.19.73.19
2012-02-10 11:01:33 7-Information DHCP: Setting (*) CM Subnet mask to: 255.255.240.0
2012-02-10 11:01:33 7-Information DHCP: Setting (*) CM Gateway address to: 10.85.0.1
2012-02-10 11:01:33 7-Information DHCP: OFFER: Setting (*) CM TFTP Boot file: DEF001_vm2.0_d.cfg
2012-02-10 11:01:33 7-Information DHCP select: Setting (*) CM TFTP Server address to: 172.29.24.53
2012-02-10 11:01:33 7-Information DHCP: Offered (*) CM IP address to: 10.85.15.250

And here are my signals, they look a bit low, but nothing *too* drastic. They have fluctuated a bit over the last 6 months.

Frequency 849000000 Hz
Signal to Noise Ratio 34 dB
QAM QAM256
Network Access Control Object ON
Power Level 5 dBmV

Upstream Value
Channel ID 1
Frequency 36100000 Hz
Ranging Service ID 162
Symbol Rate 5.120 Msym/s
Power Level 38 dBmV

I sure hope its not my ancient 5120 causing an issue. I don't even think D3 is supported out here yet (85253)...

I've power cycled everything and it'll be good for a bit, then ping times go up and speeds slow down and it all reboots again.
--
werd


Fubar

join:2001-02-20
Phoenix, AZ
kudos:2

That 34db SNR is definitely low for that signal strength.

That log info shows nothing except a normal modem bootup log.

If the 5120 is over 3 years old I would definitely upgrade to a D3 modem. And all of Mesa should def have D3. Even if D3 isn't live you can still use a D3 modem.



liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

1 edit

oops, forgot to update my location info, I'm not in mesa anymore, paradise valley.

Yeah that was what I was afraid of with the log, it seemed "okay" to me. The issue is that it is rebooting on its own and the log file doesn't seem to be big enough to hold the errors it might get before the log.

What do you suggest for the SNR issue?

Also, here is an updated log (this happened a bit after the log above)

2012-02-10 20:40:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2012-02-10 13:06:32 7-Information Channel Change Complete - Enabling Bridge
2012-02-10 13:06:32 7-Information C203.0 DCC arrive new
2012-02-10 13:06:31 7-Information Starting Ranging On Channel 3
2012-02-10 13:06:31 7-Information C203.0 DCC arrive new
2012-02-10 13:06:31 7-Information Upstream Channel Change Requested - Disabling Bridge
2012-02-10 13:06:31 7-Information C202.0 DCC depart old



liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

1 edit

reply to liht
Now its doing it again...hasn't rebooted yet, but pretty bad packet loss and my SNR is jumping between 29 and 35dB.

Well this is silly


2012-02-10 22:33:26 3-Critical R02.0 No Ranging Response received - T3 time-out
2012-02-10 22:32:39 7-Information Channel Change Complete - Enabling Bridge
2012-02-10 22:32:39 7-Information C203.0 DCC arrive new
2012-02-10 22:32:38 7-Information Starting Ranging On Channel 1
2012-02-10 22:32:38 7-Information C203.0 DCC arrive new
2012-02-10 22:32:38 7-Information Upstream Channel Change Requested - Disabling Bridge
2012-02-10 22:32:38 7-Information C202.0 DCC depart old



liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

reply to liht

Click for full size
Click for full size
Click for full size
Click for full size
Well it rebooted at least once again last night. And of course this morning. Woke up to find this...

2012-02-11 10:56:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2012-02-11 09:42:19 7-Information Time of day - retrieved
2012-02-11 09:41:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2012-02-11 09:40:53 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2012-02-11 09:40:51 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2012-02-11 09:40:51 7-Information B401.0 Authorized
2012-02-11 09:40:51 6-Notice I401.0 TLV-11 - unrecognized OID
2012-02-11 09:40:51 7-Information SEC: Co-Signer CVC from configuration file was verified
2012-02-11 09:40:49 7-Information REGISTRATION COMPLETE - Waiting for Operational status
2012-02-11 09:40:49 7-Information REG: Capability type isn't supported by CMTS
2012-02-11 09:40:49 7-Information Registration file - downloaded
2012-02-11 09:40:38 7-Information Trying to download Configuration file ...
2012-02-11 09:40:38 5-Warning TOD - tod failed - go on trying in the background
2012-02-11 09:40:38 5-Warning D04.1 ToD request sent - No Response received
2012-02-11 09:40:38 5-Warning TOD: select failed
2012-02-11 09:40:32 7-Information DHCP - parameters acquired
2012-02-11 09:40:32 7-Information DHCP: ACK: Setting (*) CM TFTP Boot file: DEF001_vm2.0_d.cfg
2012-02-11 09:40:32 7-Information DHCP: Setting CM IP address to: 10.85.15.250
2012-02-11 09:40:29 7-Information DHCP: Setting (*) CM Syslog Server address to: 10.254.254.254
2012-02-11 09:40:29 7-Information DHCP: Setting (*) CM Time Server address to: 172.19.73.19

Signal levels seem "okay"...SNR a little low.

Frequency 849000000 Hz
Signal to Noise Ratio 35 dB
QAM QAM256
Network Access Control Object ON
Power Level 5 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 1
Frequency 36100000 Hz
Ranging Service ID 162
Symbol Rate 5.120 Msym/s
Power Level 38 dBmV

However, packet loss up the wazoo.
--
werd

lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

Well seeing as you mention your SNR jumping between 29-35db, it sounds like it may be time for a cox tech visit to your place to check over things. Since when your SNR is at its best at 35db, its only meeting cox's minimum requirements for SNR. Also your upstream power level is rather low at 38db to me, for the simple fact where you live, and the warmer temps there. Because the upstream power level only goes up the warmer it gets outside.

Also if none of the AZ techs pop in your thread by tomorrow, you can send CoxTech1 See Profile a PM he should be back on here tomorrow. Send your modems mac# to him, and he will be able to look over things from his end. He will also probably mention a tech visit needed to get them signal levels better. So see what he can find out for you, and take it from there. I also recommend thinking about upgrading your modem to a newer D3 modem, as I told someone else recently. Yes these older D2 modems are still on cox's modem support page. But that doesn't mean much, because these older D2 modems may not play very well with the newer D3 equipment cox has put to use. To provide better, and more reliable service to you.



liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

Thanks. I think it might be time for a visit to. I hate when they come out, last time they came to "run a cable" and ended up NOT doing it because the building would not allow it, and charged me anyhow.

During the summer when it was 115*, it worked fine. Its 68* now...so...not sure if that has anything to do with it. I'll think about upgrading to a D3...money is tight so that won't happen soon.
--
werd


lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

said by liht:

Thanks. I think it might be time for a visit to. I hate when they come out, last time they came to "run a cable" and ended up NOT doing it because the building would not allow it, and charged me anyhow.

During the summer when it was 115*, it worked fine. Its 68* now...so...not sure if that has anything to do with it. I'll think about upgrading to a D3...money is tight so that won't happen soon.

Well I suggest discussing your problem with one of the techs on here, and like I said if no AZ tech post in your thread by tomorrow. CoxTech1 See Profile should be back on here tomorrow, and you can discuss it with him, and what he suggest you to do. But as I said before your Downstream SNR should not be going from 35db to 29db. With changes in temps outside you should see maybe 1db or 2db max change in SNR from the coldest point in the year to the warmest. With the changes your seeing, its one of two things. One your modem could be going bad, which will cause it to act up, and signal levels jump around. Second thing is bad cable or connection(aka bad splitter/loose fitting) somewhere that needs to be fixed.


liht
Acryllicht

join:2000-07-11
Paradise Valley, AZ
Reviews:
·Cox HSI

So...I decided to run down to the cox store before it closed and picked up a DCP3010. All 4 channels lit up.

Downstream
Power Level Signal to Noise Ratio
Channel 1: 2.2 dBmv 39.4 dBmv
Channel 2: 1.5 dBmv 38.9 dBmv
Channel 3: 1.7 dBmv 39.0 dBmv
Channel 4: 1.9 dBmv 39.1 dBmv

Upstream

Power Level
Channel 1: 39.7 dBmv

Speeds are back to 20/5. Looks like my 5120 was deeead.

This thing has firmware from 2009 though; the tech on the phone said he had new stuff but was unable to push it to my modem for some reason.

Current Software Revision: dpc3010-v302r12901-091119a
Firmware Name: dpc3010-v302r12901-091119a.bin
Firmware Build Time: Nov 19 2009 22:12:51

I'm sure there is something newer than that around.



Thanks for the help by the way.
--
werd


lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

said by liht:

So...I decided to run down to the cox store before it closed and picked up a DCP3010. All 4 channels lit up.

Downstream
Power Level Signal to Noise Ratio
Channel 1: 2.2 dBmv 39.4 dBmv
Channel 2: 1.5 dBmv 38.9 dBmv
Channel 3: 1.7 dBmv 39.0 dBmv
Channel 4: 1.9 dBmv 39.1 dBmv

Upstream

Power Level
Channel 1: 39.7 dBmv

Speeds are back to 20/5. Looks like my 5120 was deeead.

This thing has firmware from 2009 though; the tech on the phone said he had new stuff but was unable to push it to my modem for some reason.

Current Software Revision: dpc3010-v302r12901-091119a
Firmware Name: dpc3010-v302r12901-091119a.bin
Firmware Build Time: Nov 19 2009 22:12:51

I'm sure there is something newer than that around.



Thanks for the help by the way.

Well your downstream SNR looks way better with the Cisco DPC3010, so the modem could of def been on its last leg. As for the firmware on your modem, cox has a maintenance period most the time around 2-4am. Which if your modem isn't up to date on its firmware, cox will push the latest firmware to your modem. So leave it online tonight, and it will most likely update overnight.

Sunday, 03-Jun 22:29:00 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics