Status
Not open for further replies.
Same here, power came back on at 16H30 and now at 18H20 still blinking blue power light on CPE and no IP. :mad:
Using phones 4G as hotspot. Brackenfell location.

But vumatel promise that they have backup power and if your CPE is connected during loadshedding the fiber wont be affected. WAHAHAHAHA... utter BS. Same as your situation I had UPS hooked up before loadshedding occurred and during loadshedding network was down.

To me this is all just evidence that Vumatel have no idea what is going on with their own network or they straight up just lie about their network design. Both situations is pisspoor and I might just have to look at mobile data at end of this month because I see no way that this situation will get better in the future rather than worse.
 
Vumatel in my area is properly fked since yesterday. Again I am calling them out on not having any backup power when loadshedding occur.

Today we just have loadshedding stage 2 and the network is not coming back up remotely as quickly as it used to after loadshedding stage 2 outage.

From 12am until 7am vumatel network in my area was up and down every 15minutes and then suddenly for 4hours down. All of this without any loadshedding.

Either equipment got damaged yesterday or there is other issues that just so happen to coincidence at the exact same time as the first loadshedding in months.

If it is Vumatel active ethernet then it is most likely due to too many DHCP requests at the same time after power comes backs on
 
VUMA 200/200

as CISP has obviously no interest to answer my question, I have contacted VUMA. Will see what they have to say:

speedtest-cli --server 2789
Retrieving speedtest.net configuration...
Testing from Cool Ideas Service Provider (Pty) Ltd (155.93.169.XX)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Vodafone UK (London) [9073.28 km]: 260.759 ms
Testing download speed................................................................................
Download: 7.54 Mbit/s
Testing upload speed......................................................................................................
Upload: 9.40 Mbit/s
As mentioned we are dealing with Vumatel on it, Vumatel will tell you to contact your ISP more than likely.
 
If it is Vumatel active ethernet then it is most likely due to too many DHCP requests at the same time after power comes backs on

That does not explain why I lose Fiber access even with my CPE having power during loadshedding. I should not be affected at all with DHCP storm or whatever crap terminology is thrown at this issue.

The only facts from what I can see and many others in my situation.

1. Having power on your CPE when loadshedding occur does not help, the fiber still goes down.
2. Vumatel does not know how their own network operate or they are simply lying.
3. Vumatel have extensive network failures beyond the local peering that goes down at each loadshedding due to pisspoor network design that they only now seem to realize.

No matter what the situation is, we have had more loadshedding than yesterday/today in 2018 that never had these outcomes so something changed in their network that is completely imploding each time there is loadshedding.
 
That does not explain why I lose Fiber access even with my CPE having power during loadshedding. I should not be affected at all with DHCP storm or whatever crap terminology is thrown at this issue.

The only facts from what I can see and many others in my situation.

1. Having power on your CPE when loadshedding occur does not help, the fiber still goes down.
2. Vumatel does not know how their own network operate or they are simply lying.
3. Vumatel have extensive network failures beyond the local peering that goes down at each loadshedding due to pisspoor network design that they only now seem to realize.

No matter what the situation is, we have had more loadshedding than yesterday/today in 2018 that never had these outcomes so something changed in their network that is completely imploding each time there is loadshedding.
The feedback from Vumatel is something to do with battery theft at POPs, if the POP loses power obviously it doesn't help.
 
If it is Vumatel active ethernet then it is most likely due to too many DHCP requests at the same time after power comes backs on

Yes, but what is strange is that we will all be connected at the same time this evening at about 19:45.
 
An easy hack for the UPS thing is take a male to female C13 hack off the female end and get the female end of an extension lead connect up cables. No soldering etc needed.
 
An easy hack for the UPS thing is take a male to female C13 hack off the female end and get the female end of an extension lead connect up cables. No soldering etc needed.

PBCool, having power on the CPE during loadshedding does not help.

It seems in some cases some vumatel users are lucky to be on section with backup power but this is not the case for everyone such as myself and multiple other people reporting the same situation on downdetector comments.

Now if vumatel had backup power as they keep stating it would have been less of an issue but they are spewing bs and misrepresenting their network to people by providing these false claims. I went out just to buy a UPS for the CPE after they kept claiming it would keep the fiber on. Money well wasted cause it did absolutely nothing as loadshedding kicked in, fiber died.
 
But vumatel promise that they have backup power and if your CPE is connected during loadshedding the fiber wont be affected. WAHAHAHAHA... utter BS. Same as your situation I had UPS hooked up before loadshedding occurred and during loadshedding network was down.

To me this is all just evidence that Vumatel have no idea what is going on with their own network or they straight up just lie about their network design. Both situations is pisspoor and I might just have to look at mobile data at end of this month because I see no way that this situation will get better in the future rather than worse.

Well my Vuma connection stayed active for 2.3 hours during load-shedding, but then my UPS ran flat just 10min before load shedding ended, hence getting new batteries for it, and I was disconnected and now I sit in this Firestorm crap for 2H16 min waiting to get a IP.

Just got of the line with Vumatel as I have a ticket logged with them via CISP since yesterday, as this also happened yesterday and the guy told me that technicians are working on the switches to make changes to alleviate this "storm" issue.
 
The feedback from Vumatel is something to do with battery theft at POPs, if the POP loses power obviously it doesn't help.

Battery theft at POPs ? I find that laughable. If they are aware of it then replace it or do they actually claim that the criminals are stealing the batteries as fast as they get replaced ?

They love to keep stating "All our POP's have backup gen/batteries" but at the same time they go back on that claiming some POP's batteries were stolen, which is it ?

I find this claim hilarious. All I sense is horrible management from Vumatel on their own network, sorry to say.
 
Well my Vuma connection stayed active for 2.3 hours during load-shedding, but then my UPS ran flat just 10min before load shedding ended, hence getting new batteries for it, and I was disconnected and now I sit in this Firestorm crap for 2H16 min waiting to get a IP.

Just got of the line with Vumatel as I have a ticket logged with them via CISP since yesterday, as this also happened yesterday and the guy told me that technicians are working on the switches to make changes to alleviate this "storm" issue.

Like I stated, some POP's might have backup power such as yours, all of them don't and as PBCool just wrote apparently some POP's batteries were stolen (LMAO).

Even when I got assigned an IP, there was no internet traffic. There is more to this situation than just DHCP storm and we are not given all the actual info that matters.
 
Yeah something must be wrong, or changed, as you say, back in 2018 after load shedding it was a few seconds and the fibre connection was back up. Now at 2h31 min still no connection and just the blinking blue light. There are surely not hundreds of thousands of people in my area that is trying to connect at ones, fibre usage is not that saturated yet. something on there system has been changed since 2018 load shedding and now causes this DHCP storm situation.
 
Yeah something must be wrong, or changed, as you say, back in 2018 after load shedding it was a few seconds and the fibre connection was back up. Now at 2h31 min still no connection and just the blinking blue light. There are surely not hundreds of thousands of people in my area that is trying to connect at ones, fibre usage is not that saturated yet. something on there system has been changed since 2018 load shedding and now causes this DHCP storm situation.

The only thing I suspect that might have changed and they are not doing any full disclosure for. They have multiple sites without backup power that needs to be restarted manually by technicians after each power outage. This is the only thing that would explain the sudden long duration of network recovery after loadshedding.

Basically to me it seems their network is setup in some crappy serial configuration rather than parallel configuration thus if any point fail in the middle every point behind it fails. This is pure speculation but the only plausible reason for the sudden long outage after a power failure.

If this is how they ended up doing things it would help with cutting costs since serial configuration is much cheaper to implement but recovery takes much longer during any failure. I wont put it pass Vumatel to go on some retarded cost cutting venture as they kept rolling out.
 
The only thing I suspect that might have changed and they are not doing any full disclosure for. They have multiple sites without backup power that needs to be restarted manually by technicians after each power outage. This is the only thing that would explain the sudden long duration of network recovery after loadshedding.

Basically to me it seems their network is setup in some crappy serial configuration rather than parallel configuration thus if any point fail in the middle every point behind it fails. This is pure speculation but the only plausible reason for the sudden long outage after a power failure.

If this is how they ended up doing things it would help with cutting costs since serial configuration is much cheaper to implement but recovery takes much longer during any failure. I wont put it pass Vumatel to go on some retarded cost cutting venture as they kept rolling out.
Yeah agree and the fact that different areas get affected at different times causes more issues and then in the case of level 3 or 4 loadshedding, just as you think you are back it hits you again.

Like rolling uphill. All this because of the lack of the 6 x Ps principle from EKSDOM part.
 
3 hours and blinking blue light and still no IP.

#COOL-20190211-217103 - Link Down
 
Last edited:
Logged a support ticket. #COOL-20190212-218147

Effectively down for me 12h now.

Vumatel trenched. 100/100

Durbanville
 
The strangest thing is, during load shedding my UPS turned off every 7 minutes, I then powered it back up and the CPE connected no problem, this happened for 2.3 hours until the UPS battery was flat, then when load shedding was over, the CPE cannot establish a link at all.

So during Load shedding no issue to reconnect every 7 minutes, but now after 3H14 minutes it cannot connect.... how is that for insane!
 
4hrs later, still no sync(sync went down at start of loadshedding even with UPS on CPE)

nearly 48hrs now where fiber briefly worked for 2hrs.

Fantastic network Vumatel, you are giving Octotel a run for the money.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X