dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2235
share rss forum feed

Nemo888

join:2005-12-25
Canada

Constant Ottawa Disconnects, DHCP Issues Not Resolved.

Nov 3 03:13:27 WAN Connection: WAN was restored.
Nov 3 03:15:12 WAN Connection: WAN was restored.
Nov 3 11:39:23 WAN Connection: WAN was restored.
Nov 3 20:03:37 WAN Connection: WAN was restored.
Nov 4 03:37:18 WAN Connection: WAN was restored.
Nov 4 12:03:48 WAN Connection: WAN was restored.

Nov 4 12:06:39 WAN Connection: ISP's DHCP did not function properly.
Nov 4 12:06:39 notify_rc : stop_nat_rules
Nov 4 12:06:39 stop_nat_rules: apply the redirect_rules!
Nov 4 12:06:40 dnsmasq[505]: read /etc/hosts - 3 addresses
Nov 4 12:06:40 dnsmasq[505]: using nameserver 206.248.154.170#53
Nov 4 12:06:40 dnsmasq[505]: using nameserver 206.248.154.22#53
Nov 4 12:06:40 notify_rc : start_nat_rules
Nov 4 12:06:40 start_nat_rules: apply the nat_rules!
Nov 4 12:06:41 notify_rc : stop_upnp
Nov 4 12:06:41 notify_rc : start_upnp
Nov 4 12:06:41 rc_service: start_upnp is waitting stop_upnp...
Nov 4 12:06:41 miniupnpd[31889]: received signal 15, good-bye
Nov 4 12:06:42 syslog: SNet version started
Nov 4 12:06:42 miniupnpd[1108]: HTTP listening on port 42759
Nov 4 12:06:42 miniupnpd[1108]: Listening for NAT-PMP traffic on port 5351
Nov 4 12:06:42 dhcp client: bound 24.246.2.44 via 24.246.2.33
Nov 4 12:06:43 notify_rc : restart_diskmon
Nov 4 12:06:43 disk monitor: be idle
Nov 4 12:06:44 WAN Connection: WAN was restored.

7 disconnects in 2 days. Teksavvy, get your sh%t together. How many months do we have to put up with this???



TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33

You may want to remove your IP from there.

And if you wouldn't mind posting in the »TekSavvy Direct forum so we can look at this.

We have notice lot's of maintenance in Ottawa as of late. It could very well be you are being affected by this.

Martin
--
TSI Martin (Escalations / Social Media) - TekSavvy Solutions Inc.
Authorized TSI employee ( »»TekSavvy FAQ »Official support in the forum )
Follow me on Twitter : @TSIMartin



jmck
formerly 'shaded'

join:2010-10-02
Ottawa, ON

for what it's worth, my area in Ottawa near the market hasn't had any of these disconnects.



NytOwl

join:2012-09-27
canada

I reside in Gloucester on the St. Laurent2 POI and haven't had any issues here in weeks, myself.

Funny enough, though... On a hunch I checked the Event Log in my firewall and found numerous DHCP renewals on its WAN interface on November 2nd. 31 of them, to be exact. Bunch more on November 1st, too.

My partner and I never noticed any problems, though, and the same IP kept getting re-assigned for each renewal, strangely enough.


Nemo888

join:2005-12-25
Canada

I'm on the Richmond Road POI. So there is a pattern developing. What good would taking this to the direct forums do other than letting Teksavvy hide the problem? We have been putting up with this crap for a long time. In August the internet was unusable. Not only was it annoying the outages would often crash my old router so I had to upgrade.

Here would be a great place to explain what is wrong with the DHCP server. The problem has been hidden away for months. Time for a little more openness.



ChuckcZar

@teksavvy.com
reply to jmck

We've seen the recent stories and all the stories from long ago. Conclusion without a doubt Ottawa is the number one city in southern Ontario for internet problems of all types per capita.



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13
Reviews:
·WIND Mobile
·TekSavvy Cable
reply to Nemo888

There is NOTHING wrong with the DHCP server.

This is all to do with the way Rogers has chosen to implement TPIA addressing services.

When a modem is powered up on the cable it sends its MAC address to the CMTS to validate it. For Rogers customers, this is easy peasy ... they have their own central database of Rogers customers and Rogers modems can connect anywhere across Rogers footprint. BUT For TPIA customers, there's another database held with the CMTS (so that TPIA's devices are unique to the CMTS they are provisioned on - there's other reasons for that including the lack of access across Rogers network).

Now after being acknowledged the modem then is permitted to ask for its OWN IP address based on its MAC by a commn DHCP server. This is a Rogers internal IP so they can operate the modem and send the provisioning data.

Now the modem will come online for TCP/IP communications and the ISP DHCP will assign an IP (Rogers or TPIA) based on the modem MAC, and system MAC. From here, the system will have access to the internet connection ...

Rogers IPs traffic has open access to Rogers network. TPIA IPs traffic are filtered off at the CMTS router to a POI router.

Providing the TPIA's IP addresses are correctly programmed in the CMTS router, all will be good and everybody gets to the internet by Rogers or TekSavvy.

Now all this is good except ...

When Rogers does a nodesplit, users may be moved to another CMTS. If you're a Rogers user, no biggie, but for TPIA clients, the new CMTS must have its allowed MAC database updated. Fall down number 1 ... Rogers forgets to do this. The modem isn't recognized so config and IP address are dropped.

Assuming that gets done properly, the next stumbling block is with the assignment of the internal IP address ... This requires that the central database of MACs is updated correctly ... Sometimes Rogers messes this up.

Assuming that's done properly the DHCP server database must be updated correctly with the new IPs for TPIA customers.

Then the CMTS router must have its routing tables set up correctly to route TPIA traffic tot he POI router. Rogers seems to forget to do that.

All these steps if not done or done properly cause all kinds of problems like this one.

It looks like in this case it looks like a node split, new IPs not updated by Rogers for the DHCP server. It looks like it's at the system IP level (for the router) that it's failed and not the prior levels.

Apart from beating Rogers over the head with a bat to get them to ensure the DHCP servers are correct, there's not a lot TSI can do. The reality is just continuing to hit them with tickets.

It's the risk of using TPIAs.


mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..

said by sbrook:

When a modem is powered up on the cable it sends its MAC address to the CMTS to validate it. For Rogers customers, this is easy peasy ... they have their own central database of Rogers customers and Rogers modems can connect anywhere across Rogers footprint. BUT For TPIA customers, there's another database held with the CMTS (so that TPIA's devices are unique to the CMTS they are provisioned on - there's other reasons for that including the lack of access across Rogers network).

There must be something more to it than just that last sentence -- I can take my TSI Modem to a different CMTS and it still works just fine, thanks. So it's not locked to the CMTS, but perhaps it is locked to the POI instead?

There's another surprising point in there: with aggregated POI for TPIA, one might expect a lot of those fail points to vanish. But according to both TSI (non aggregated) and Start.ca (aggregated POI), the need for CMTS-specific IP addresses and CMTS-specific DHCP still remains. Weird. I'd have thought the aggregated POI would result in everything going to, say, a central MAC database for TPIA just as it does for Rogers clients.

Cheers

mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..

said by mlord:

There must be something more to it than just that last sentence -- I can take my TSI Modem to a different CMTS and it still works just fine, thanks. So it's not locked to the CMTS, but perhaps it is locked to the POI instead?

Actually, on reflection, I bet the answer is "both."
The modems probably are locked (or "local") to specific CMTSs, but not just a single CMTS -- the teksavvy modem database likely gets replicated in part/whole across many CMTSs in the region.

I say this because when I had an 11-day outage here this past summer, my modem did work on other CMTSs off the same POI, just not on my own local CMTS for some reason. So that does support the "local to a CMTS" theory, though likely several CMTSs, not just a single CMTS.

Cheers


sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13
Reviews:
·WIND Mobile
·TekSavvy Cable

So much depends on the specific implementations in the POIs. Wouldn't surprise me at all if each head end is configured differently as they learned, which is why some places don't seem to suffer and others do. In all the things going on, I've not had a single problem out where I am on Fallowfield related to these issues even though I'm now 4 streams up too. Although I know I'm on a comparatively low population node which could have a lot to do with it. They tried combining this area with another into a virtual node several years back and I had 2 weeks of performance hell. They split us back out and it was back to normal.

For a short while I was the only customer on this node and then one of 2 for several months! Back in the days of 1500 kbps down was express and I could only get 1200 flat out!


josh7878

join:2012-11-01
K2J5T2
reply to Nemo888

I am experiencing the same thing. I've had 3 disconnects in the last few hours. Has been happening since mid-last week. Barrhaven area (whichever POI that is).

Is this specifically a Rogers/Teksavvy issue, or does it relate to modem firmware at all?



TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33

What is your Internet IP lease times?


josh7878

join:2012-11-01
K2J5T2
reply to Nemo888

This is what it currently shows:

Lease Obtained. . . . . . . . . . : Monday, November 05, 2012 11:47:33 AM

Lease Expires . . . . . . . . . . : Tuesday, November 06, 2012 11:47:33 AM



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13
reply to Nemo888

It probably does NOT relate to modem firmware and is a Rogers signal issue.


mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..
reply to josh7878

said by josh7878:

Is this specifically a Rogers/Teksavvy issue, or does it relate to modem firmware at all?

If you have a DCM-475 running Stac.02.08 firmware, then get it upgraded (to 02.16). That combination is trouble (resets, disconnects) for 8/4 channel bonding. I can do the upgrade here in Bells Corners for a very modest $5.

Cheers

Nemo888

join:2005-12-25
Canada
reply to Nemo888

It's still happening. Not really seeing any pattern yet except it is often a double disconnect. Do other people get the disconnects at the same time? We need a few people's logs here.

Latest disconnects,
Nov 4 20:28:21 WAN Connection: WAN was restored.
Nov 5 05:06:17 WAN Connection: WAN was restored.
Nov 5 05:07:38 WAN Connection: WAN was restored.
Nov 5 13:32:33 WAN Connection: WAN was restored.
Nov 5 22:00:01 WAN Connection: WAN was restored.
Nov 5 22:02:21 WAN Connection: WAN was restored.
Nov 6 06:38:38 WAN Connection: WAN was restored.


mlord

join:2006-11-05
Nepean, ON
kudos:13

Those logs appear to all be from a router. Best to look for logs in the modem itself here.


Nemo888

join:2005-12-25
Canada

Wed Nov 07 03:20:58 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=00:26:24:b...
Wed Nov 07 04:39:47 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Oct 19 07:06:13 2012 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC S...
Wed Nov 07 03:21:03 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Nov 07 21:40:30 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Fri Oct 19 07:03:40 2012 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:26:24:b6...

The logs on the modem aren't great. New router logs are very easy to read.
Nov 6 15:05:04 WAN Connection: WAN was restored.
Nov 6 23:38:24 WAN Connection: WAN was restored.
Nov 7 08:13:40 WAN Connection: WAN was restored.
Nov 7 08:14:41 WAN Connection: WAN was restored.
Nov 7 16:38:42 WAN Connection: WAN was restored.


mlord

join:2006-11-05
Nepean, ON
kudos:13

Are you sure it's not just a router bug?
The modem logs you posted look "normal".



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13
reply to Nemo888

The modem log looks as if it lost RF signal momentarily and no amount of looking at modem logs or signal strengths unless you look at the right moment, is going to reveal that to be the case.



TSILiz
Premium
join:2012-08-20
kudos:6
reply to Nemo888

just to confirm, what is the firmware on your modem?


Nemo888

join:2005-12-25
Canada

I was on 2.08 till 9:30 this morning. Now on 2.16. It will be interesting to see conclusively if that was the problem.

Thanks MLord.



d4m1r

join:2011-08-25
Reviews:
·Start Communicat..
reply to Nemo888

Apart from a hard reset initiated by Rogers on my modem last week (for 4 upstream channel bonding), I have been 100% online on the Richmond POI for the past week.
--
www.613websites.com Budget Canadian Web Design and Hosting


Nemo888

join:2005-12-25
Canada
reply to Nemo888

I should go to my bro's house and check his logs. Haven't we had 4 stream bonding for months?

I was getting multiple daily disconnects so if it is ok now that would be very concrete proof that 2.08 is buggy enough to knock you off the internet.


Nemo888

join:2005-12-25
Canada
reply to Nemo888

So no disconnects so far after upgrading to 2.16. Would have been nice to know that was the source of the problem while it was still under warranty.


Nemo888

join:2005-12-25
Canada

24 hours and no disconnects. Upstream transmit power is stronger as well.

2.08 is all bad.



d4m1r

join:2011-08-25
Reviews:
·Start Communicat..
reply to Nemo888

said by Nemo888:

Haven't we had 4 stream bonding for months?

Like I said, I'm on the Fallowfield POI and I only got it last week, would it be possible for people on the same POI as me to get it sooner?
--
www.613websites.com Budget Canadian Web Design and Hosting


sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13

Yes ... it's done cable segment by segment and the CMTS.


Nemo888

join:2005-12-25
Canada
reply to Nemo888

It just went down for an hour and ten minutes. Me and my brother are on the Richmond Rd. hub in Westboro not Fallowfield.



TSI Support1
TSI Support
Premium
join:2009-09-28
Chatham, ON
kudos:1

Hi there,

You were likely part of the outage - please keep an eye on the connection, and if the firmware doesn't fix it we will have to dig a little bit deeper on this one.

Really sorry about this.

Regards,
TSI-Ashley