kripstoe
Expert Member
...now I sit in the "firestorm" **** waiting for the CPE to connect and get an IP..........
Welcome, and enjoy your stay.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
...now I sit in the "firestorm" **** waiting for the CPE to connect and get an IP..........
Same here, power came back on at 16H30 and now at 18H20 still blinking blue power light on CPE and no IP.
Using phones 4G as hotspot. Brackenfell location.
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.
As mentioned we are dealing with Vumatel on it, Vumatel will tell you to contact your ISP more than likely.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
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
The feedback from Vumatel is something to do with battery theft at POPs, if the POP loses power obviously it doesn't help.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.
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
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.
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.
Yeah looks exactly like that gifWelcome, and enjoy your stay.
The feedback from Vumatel is something to do with battery theft at POPs, if the POP loses power obviously it doesn't help.
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.
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 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.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.