Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




23 posts

Geek
+1 received by user: 2


# 214085 27-Apr-2017 11:43
Send private message

Hi,

 

I am trying to figure out an ongoing issue with my cable modem service.  For a while now I have monitored it with AWS's route53 alarm service, and I see outages (and experience them).  I also get DNS failures where for some minutes, my bind9 server cannot seem to get any results for 5 or so minutes then works fine it serves cached info no issues.  So while new web connections fail, at the same time however existing connections continue to work fine.   Right now I am a bit stumped but I know as soon as I ring Vodafone they will say nothing is wrong (they always do) as I am trying to collect some evidence/proof.   So is anyone else in the Wellington area seeing something similar?

 

 

 

 

 

 

 

 


Create new topic
2867 posts

Uber Geek
+1 received by user: 501

Trusted

  # 1771179 27-Apr-2017 11:46
Send private message

Are you on the oldschool cable service or FibreX (DOCSIS 3.1)?


298 posts

Ultimate Geek
+1 received by user: 52


  # 1771192 27-Apr-2017 12:11
Send private message

Where are you located? Island Bay for instance has had major ongoing problems for years.

 

I suspect you are more likely to have problems with the new FibreX service, as my old cable connection had no problems but the new one has relatively frequent dropouts.

 

If you are on FibreX, do you have a dynamic or static IP?

 

 


 
 
 
 




23 posts

Geek
+1 received by user: 2


  # 1771213 27-Apr-2017 12:33
Send private message

"cable" since about 1999 or so, Ngaio.   We were supposed to get Fibre in June2016 but now apparently its 2020 and that is a maybe.

 

Smokeping isnt really showing an issue.  I installed it many years ago and pinged each of Clear's routers all the way to the west coast but these days much of it is now prevented.  Clear then were painful, I had them back numerous times and the techie finally told me the router at the end of the street was designed for 600ppl and there were 2500+ on it so I was wasting their time. 

 

http://202.78.148.43/cgi-bin/smokeping.cgi?target=_charts

 

Whatever is going on its getting worse ie more frequent.

 

 

 

 

 

 


49 posts

Geek
+1 received by user: 11


  # 1774276 2-May-2017 14:18
Send private message

We are in Northland, Wellington and been on the VF cable for about a year. (Switched from Spark adsl, which was rubbish. Cable speeds far superior)

 

Had largely been OK, but in recent months have experienced intermittent bursts of service outage for typically 1-5 mins. The supplied modem/router (Technicolor) pretty much always shows it is connected 'downstream'. I have periodically reset it, and usually after it revives, it reconnects - although this is likely a coincidence of timing.

 

I have not made any support calls to VF. The outages are never for very long, and there is no discernible pattern. So it is more of an annoyance, especially if i'm working from home, than anything severe.

 

Roll on the fibre!

 

 


1907 posts

Uber Geek
+1 received by user: 458

Trusted
Subscriber

  # 1774298 2-May-2017 15:05
Send private message

Its pretty clear reading these conversations in this forum and others, that the connection between the modem and the core cable network is being dropped and re-established on demand. This is ok for pull traffic - typical web stuff - but for anything working on a permanent open inbound connection not so good.

 

Key thing is that the connection isnt being 'dropped' per se, just going dormant, and what people are seeing is something akin to an 'outage'.

 

This feels to me like vodafone needs to take a different approach to diagnosing the experience and finding out why the sessions are being dropped. Normal fault processes deal with things like line breaks, disabled services and so on.

 

Intermittent behaviour is trickier and not something for basic level 2 support to address.

 

@mikehales.... over to you

 

 





________

 

Antonios K

 

Click to see full size


615 posts

Ultimate Geek
+1 received by user: 215

Trusted
Vodafone NZ

  # 1774304 2-May-2017 15:12
Send private message

It's a fair question and funnily enough I've had 2 conversations about this very thing today. So, while I may not have an answer now, we're definitely aware of it and exploring how to address.





Channel Manager, Help & Support @ Vodafone NZ




23 posts

Geek
+1 received by user: 2


  # 1774575 2-May-2017 20:29
Send private message

99% sure it isnt going dormant from lack of use, I odnt think my wife and son ever get off it, LOL.  It is certainly random, the strange thing is I'd expect smokeping to pick it up but it isnt yet AWS does.  Its got me wondering if the issue is more "backbone" than local, hence why I asked "aloud".  

 

@jimmy  "Had largely been OK, but in recent months have experienced intermittent bursts of service outage for typically 1-5 mins"

 

That is an interesting comment, Ive looked at each break I still have an email for and its 60seconds or 900 seconds, no other variation.

 

========

 

You are receiving this email because your Amazon CloudWatch Alarm "graywitch-test" in the US East - N. Virginia region has entered the ALARM state, because "Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0)." at "Sunday 30 April, 2017 04:19:03 UTC".

View this alarm in the AWS Management Console:
https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#s=Alarms&alarm=graywitch-test

Alarm Details:
- Name:                       graywitch-test
- Description:                graywitch-test
- State Change:               OK -> ALARM
- Reason for State Change:    Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0).
- Timestamp:                  Sunday 30 April, 2017 04:19:03 UTC
- AWS Account:                40xxxxxx
Threshold:
- The alarm is in the ALARM state when the metric is LessThanThreshold 1.0 for 900 seconds.

Monitored Metric:
- MetricNamespace:                     AWS/Route53
- MetricName:                          HealthCheckStatus
- Dimensions:                          [HealthCheckId = 8131282d-ce05-4830-8fa9-66ebc03257ef]
- Period:                              900 seconds
- Statistic:                           Minimum
- Unit:                                not specified



State Change Actions:
- OK:
- ALARM: [arn:aws:sns:us-east-1:402xxxxxxx:graywitch]
- INSUFFICIENT_DATA:

 

========

 

========

 

You are receiving this email because your Amazon CloudWatch Alarm "grwaywitch2-awsroute53-88ab54f0-8578-44ec-b1fa-8d657fd01039-Low-HealthCheckStatus" in the US East - N. Virginia region has entered the ALARM state, because "Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0)." at "Monday 20 March, 2017 23:37:32 UTC".

View this alarm in the AWS Management Console:
https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#s=Alarms&alarm=grwaywitch2-awsroute53-88ab54f0-8578-44ec-b1fa-8d657fd01039-Low-HealthCheckStatus

Alarm Details:
- Name:                       grwaywitch2-awsroute53-88ab54f0-8578-44ec-b1fa-8d657fd01039-Low-HealthCheckStatus
- Description:               
- State Change:               OK -> ALARM
- Reason for State Change:    Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0).
- Timestamp:                  Monday 20 March, 2017 23:37:32 UTC
- AWS Account:                402xxxxxx

Threshold:
- The alarm is in the ALARM state when the metric is LessThanThreshold 1.0 for 60 seconds.

Monitored Metric:
- MetricNamespace:                     AWS/Route53
- MetricName:                          HealthCheckStatus
- Dimensions:                          [HealthCheckId = 88ab54f0-8578-44ec-b1fa-8d657fd01039]
- Period:                              60 seconds
- Statistic:                           Minimum
- Unit:                                not specified



State Change Actions:
- OK:
- ALARM: [arn:aws:sns:us-east-1:402xxxxxxxxxxxx:graywitch]
- INSUFFICIENT_DATA:

 

========

 

 

 

========

 

You are receiving this email because your Amazon CloudWatch Alarm "graywitch-test" in the US East - N. Virginia region has entered the ALARM state, because "Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0)." at "Friday 18 November, 2016 01:20:03 UTC".

View this alarm in the AWS Management Console:
https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#s=Alarms&alarm=graywitch-test

Alarm Details:
- Name:                       graywitch-test
- Description:                graywitch-test
- State Change:               OK -> ALARM
- Reason for State Change:    Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0).
- Timestamp:                  Friday 18 November, 2016 01:20:03 UTC
- AWS Account:                4025xxxxxxxxxx

Threshold:
- The alarm is in the ALARM state when the metric is LessThanThreshold 1.0 for 900 seconds.

Monitored Metric:
- MetricNamespace:            AWS/Route53
- MetricName:                 HealthCheckStatus
- Dimensions:                 [HealthCheckId = 8131282d-ce05-4830-8fa9-66ebc03257ef]
- Period:                     900 seconds
- Statistic:                  Minimum
- Unit:                       not specified

State Change Actions:
- OK:
- ALARM: [arn:aws:sns:us-east-1:402xxxxxxx7:graywitch]
- INSUFFICIENT_DATA:

 

=======

 

This 60 or 900sec might however just be a function of AWS in some way but I cant immediately see how, Im not that experienced with it.

 

For these sort of breaks smokeping should show a break also,

 

http://202.78.148.43/cgi-bin/smokeping.cgi?target=DNS.Vodafone

 

So I smokeping vodafone's DNS server so if it was my local link I think I'd see that 15min break but I do not, hence head scratch time.

 

 


Create new topic



Twitter and LinkedIn »



Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

New Zealand government unveils new digital service to make business easier
Posted 16-Jul-2019 17:35


Scientists unveil image of quantum entanglement
Posted 13-Jul-2019 06:00


Hackers to be challenged at University of Waikato
Posted 12-Jul-2019 21:34


OPPO Reno Z now available in New Zealand
Posted 12-Jul-2019 21:28


Sony introduces WF-1000XM3 wireless headphones with noise cancellation
Posted 8-Jul-2019 16:56


Xero announces new smarter tools, push into the North American market
Posted 19-Jun-2019 17:20


New report by Unisys shows New Zealanders want action by social platform companies and police to monitor social media sites
Posted 19-Jun-2019 17:09


ASB adds Google Pay option to contactless payments
Posted 19-Jun-2019 17:05


New Zealand PC Market declines on the back of high channel inventory, IDC reports
Posted 18-Jun-2019 17:35


Air New Zealand uses drones to inspect aircraft
Posted 17-Jun-2019 15:39


TCL Electronics launches its first-ever 8K TV
Posted 17-Jun-2019 15:18


E-scooter share scheme launches in Wellington
Posted 17-Jun-2019 12:34


Anyone can broadcast with Kordia Pop Up TV
Posted 13-Jun-2019 10:51


Volvo and Uber present production vehicle ready for self-driving
Posted 13-Jun-2019 10:47


100,000 customers connected to fibre broadband network through Enable
Posted 13-Jun-2019 10:35



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.