 digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | [LA] Connection problems Looks like the idiot down the road is blowing the node up. Confirmed with 2 neighbors(one is about half a mile away) that their modems are cycling(rebooting) and unable to sync. I'm glad the CB'er is blowing the node up solid now, maybe Cox will actually notice the additional service calls in this area and either have the FCC fix this guy, or move the upstream as far away from the CB band as they can.
--
FWD#297248 |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | And before anyone asks....yes this was confirmed on three modems being down at once.
Frequency 705000000 Hz Locked
Signal to Noise Ratio 38 dB
Power Level -3 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 4
Frequency 26992000 Hz Ranged
Power Level 40 dBmV
--
FWD#297248 |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to digiblur
Think we are going to start coordinating calling in at the same time while it's down.
--
FWD#297248 |
|
 imtim83Premium
join:2001-06-03
Kenner, LA | reply to digiblur
I am having the same problems. It started a few hours ago as well. |
|
| Been like this since I got home from work.
Is there any way to merge all these posts... there are 4 different posts about the same thing.
Anyway, I can't believe Cox techs are acting like there's something they can do. Us Cox HSI users go through this every few weeks. I think they're just playing some sort of game... let's see how long we can screw with these people until they realize they're getting ripped off on their internet service. |
|
dzlpwr
join:2004-01-05
Brooklyn, NY | And what would they gain by doing that? |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to andytseng
I can guarantee when anyone from LA thinks about using Cox HSI service and they see all this, they will change their mind pretty quick. Word of mouth is a bad thing for this. Kinda like the news, you don't hear the good, you just hear the bad. Seems that's all I'm hearing around this part of town from several people.
--
FWD#297248 |
|
|
|
| reply to andytseng
andytseng
Do you still experience your service issue? IM me your cable modem's HFC MAC address and I will take a look at your connection. Thank you! |
|
imtim83Premium
join:2001-06-03
Kenner, LA | reply to digiblur
said by digiblur:I can guarantee when anyone from LA thinks about using Cox HSI service and they see all this, they will change their mind pretty quick. Word of mouth is a bad thing for this. Kinda like the news, you don't hear the good, you just hear the bad. Seems that's all I'm hearing around this part of town from several people. Yep. I tell everyone I know so they know exactly what they are getting into if they get cox@home.
--
Thank God i am not getting married, having kids, going on a date, etc! Oh Thank God! |
|
RAVEN72
join:2003-10-27
Greenwell Springs, LA | Cox would rather waste there money sending a truck to your house knowing that they cant fix your problem then to fix ther own damn network. My advise is to go with Bellsouth dsl. I switched to DSL about a month ago and I am very happy I did. Rock solid connection now. |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to digiblur
Another monday and like clock work it's back. I called to report an outage but as soon as I punched in my last four of my social it said there was an outage in my area so I hung up.
--
FWD#297248 |
|
| reply to digiblur
Digi, have you pinpointed where it's coming from? I got a solution for ya if you have. It involves some underhanded-ness and a couple of straight pins. |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana
1 edit | said by Phaetos:Digi, have you pinpointed where it's coming from? I got a solution for ya if you have. It involves some underhanded-ness and a couple of straight pins. LOL... I'm pretty sure he's a street or two over from me. I confirmed with a friend 2 miles away that he's shutting him down too. Modems just start cycling until the node recovers. Not sure why he's shutting down the entire node now, maybe he just wore it out with his "1.21 jigawatts" of power.
I'll pass on trespassing on someone's property. This is Cox's problem. I'm glad he's blowing it up now though, maybe Cox will realize there really is a problem with putting the upstream inside of the CB band! That's just crazy within itself! Doesn't DOCSIS run from 5-40mhz?
--
FWD#64466 - »[Sipura] Make your Sipura Speak! - Step by Step |
|
| said by digiblur:said by Phaetos:I'll pass on trespassing on someone's property. This is Cox's problem. I'm glad he's blowing it up now though, maybe Cox will realize there really is a problem with putting the upstream inside of the CB band! That's just crazy within itself! Doesn't DOCSIS run from 5-40mhz? Within that 5-42Mhz range, only 20Mhz - 38Mhz is realistically usable in most cable systems; you're centered at 26.9Mhz which is pretty typical. Also, I'm assuming your signal details posted above on 2/21 were not produced during the time you were experiencing an outage. If the outage lasts for an extended period (is not short and bursty) and is caused by excessive ingress noise entering at the node as you suspect, I would expect to see your upstream power maxing out and modem recycles. The timestamps on those log entries should correspond closely with the pingplotter graphs you're gathering. |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | said by nixnick5:Within that 5-42Mhz range, only 20Mhz - 38Mhz is realistically usable in most cable systems; you're centered at 26.9Mhz which is pretty typical. Also, I'm assuming your signal details posted above on 2/21 were not produced during the time you were experiencing an outage. If the outage lasts for an extended period (is not short and bursty) and is caused by excessive ingress noise entering at the node as you suspect, I would expect to see your upstream power maxing out and modem recycles. The timestamps on those log entries should correspond closely with the pingplotter graphs you're gathering. Cool... crank us up to 38mhz then. 
I'd love to look at the signal levels while the modem is cycling but the 192.168.100.1 page is non-responsive and we can't access the modem via SNMP since Cox locked the user side out 100% on that avenue.
The log on the modem is too long and just gets truncated. I'll post it next time if you like.
--
FWD#64466 - »[Sipura] Make your Sipura Speak! - Step by Step |
|
| I skimmed over your previous thread in the interim. My suggestion to you is to skip calling the front end modem help desk and call the local office directly. See if you can't get in touch with the plant manager for Baton Rouge. Barring a phone call, gather up your data and pay the Cox office on Florida Blvd a visit and see if you can meet with the plant manager or engineer to discussion what you think may represent evidence of a significant source of ingress and/or signal leakage. |
|
1 edit | reply to digiblur
said by digiblur:LOL... I'm pretty sure he's a street or two over from me. I confirmed with a friend 2 miles away that he's shutting him down too. Modems just start cycling until the node recovers. Not sure why he's shutting down the entire node now, maybe he just wore it out with his "1.21 jigawatts" of power. Well that depends on where his antenna is, it's not trespassing if it's close enough to public property, like, a back ditch or the corner of the street. 
Edit:
On 2nd thought, that's just a personal opinion of "not trespassing", not a lawfully correct one. |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to nixnick5
said by nixnick5:I skimmed over your previous thread in the interim. My suggestion to you is to skip calling the front end modem help desk and call the local office directly. See if you can't get in touch with the plant manager for Baton Rouge. Barring a phone call, gather up your data and pay the Cox office on Florida Blvd a visit and see if you can meet with the plant manager or engineer to discussion what you think may represent evidence of a significant source of ingress and/or signal leakage. I have to work during the times they are open, by the time I'd get down there they are closed. I was hoping for a Cox techs here read these threads, call the BR market office to see if they have any logs of the service being down, then point the line techs to the problem. Fix the guy via the FCC, which in my eyes will never happen, or move the upstream. Or lose customers in this area to BellSouth.
--
FWD#64466 - »[Sipura] Make your Sipura Speak! - Step by Step |
|
digiblurGot Sipura?Premium
join:2002-06-03
Louisiana | reply to digiblur
2005-03-02 22:31:41 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2005-03-02 22:06:52 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2005-03-02 22:06:51 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2005-03-02 22:06:50 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response
2005-03-02 22:06:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:05:27 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:05:27 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:05:20 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:05:20 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:05:11 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:05:11 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:04:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 22:04:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 22:04:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 22:04:37 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:04:37 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:04:13 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:04:13 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:03:49 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:03:49 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:03:30 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:03:30 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:03:09 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:03:09 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:02:46 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:02:46 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:02:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 22:02:08 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:02:08 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:02:02 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:02:02 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:01:55 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:01:55 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:01:47 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:01:47 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:01:39 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:01:39 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:01:31 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 22:01:31 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 22:01:21 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2005-03-02 22:00:48 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2005-03-02 21:25:16 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2005-03-02 21:25:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2005-03-02 21:25:01 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:24:40 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:24:40 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:24:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:24:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:24:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:24:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:24:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:24:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:24:21 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:24:21 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:24:15 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:24:15 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:24:09 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:24:09 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:23:47 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:23:47 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:23:35 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:23:35 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:23:15 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:23:15 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:22:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:51 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:49 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:48 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:48 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:22:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:22:38 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:22:38 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:22:17 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:22:17 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:21:58 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:21:58 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:21:37 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:21:37 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:21:14 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:21:14 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:20:49 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2005-03-02 21:20:49 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2005-03-02 21:20:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-03-02 21:20:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-03-02 21:20:13 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
Event Log has reached maximum size. Older log entries are lost.
--
FWD#64466 - »[Sipura] Make your Sipura Speak! - Step by Step |
|
| reply to digiblur
said by digiblur:said by nixnick5:I have to work during the times they are open, by the time I'd get down there they are closed. I was hoping for a Cox techs here read these threads, call the BR market office to see if they have any logs of the service being down, then point the line techs to the problem. Fix the guy via the FCC, which in my eyes will never happen, or move the upstream. Or lose customers in this area to BellSouth. That would be ideal. The logs you posted along with the other data are ample evidence of an intermmitent upstream RF problem. Try calling the BR regional office if you don't get an IM soon or other indication from a tech here on BBR. Some of their corporate folks read and even post here so perhaps one of them will see this thread and pass it on to the locals. I wouldn't mention the FCC as that's just going to be a distraction. I would just present the symptoms you have gathered thus far and emphasize the intermittent, time-specific nature of the problem. The only Cox techs I've seen from LA here cover the New Orleans metro area which I believe is managed separately within Cox. Perhaps one of them will see this and pass a message on to their counterparts in BR. |
|
