hio77:
Pretty map, Done real fast so i haven't colour coded dates or anything.
When you see it mapped, you see the impressive scope on rollout - 10 days to hit all those dslams isn't bad!
Where did you get the GPS locations for all the cabinets?
|
|
|
hio77:
Pretty map, Done real fast so i haven't colour coded dates or anything.
When you see it mapped, you see the impressive scope on rollout - 10 days to hit all those dslams isn't bad!
Where did you get the GPS locations for all the cabinets?
atomeara:
Where did you get the GPS locations for all the cabinets?
gps sourcing is available in multiple places, i took a much larger list and joined the values with what's actually been notified.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:
https://sp.chorus.co.nz/product-update/vectoring-rollout-increase-speed-and-stability-vdsl
Chorus have also put out their own discussion on this now.
The graph they have presented, i would say lines up with my personal findings - unlike what was experienced with the previous PR. @ChorusNZ well done! :)
Some of those outliers are mental. Imagine being the guy who's used to syncing at 9Mbps and waking up to 110Mbps!
hio77:
atomeara:
Where did you get the GPS locations for all the cabinets?
gps sourcing is available in multiple places, i took a much larger list and joined the values with what's actually been notified.
Yeah, I mean where did you find that list, all the ones I can find are rather old now
allio:
Some of those outliers are mental. Imagine being the guy who's used to syncing at 9Mbps and waking up to 110Mbps!
Indeed there has been some insane growths.
I've conditionally anaylised quite a few of these...
atomeara:
Yeah, I mean where did you find that list, all the ones I can find are rather old now
most of those cabinets are rather old now too ;)
There are some kept right up todate though..
I have a few data issues in the locations for my mapping - don't look at ant.
Suspect this is where i was cleaning up data and rounded a figure though rather than the data itself.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
atomeara:
Interesting that they aren't doing Whangarei! Give it is other LFC
We did Whangarei (and others!) as part of the trial, earlier in April.
Keep in mind the notifications we have sent (so the map Hio77 created) is for the main rollout - where we have, or will have Vectoring cards.
It doesn't include the trial sites of the cabinets where cards will be added during/after the main rollout.
BMarquis:
We did Whangarei (and others!) as part of the trial, earlier in April.
Keep in mind the notifications we have sent (so the map Hio77 created) is for the main rollout - where we have, or will have Vectoring cards.
It doesn't include the trial sites of the cabinets where cards will be added during/after the main rollout.
Yes, i forgot to mention that caveat.
I'm also somewhat assuming cards deployed after will just be instantly enabled etc but it's hard to confirm that with confidence from my end!
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Following on from this thread here:
https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=222828
Has anyone had any experience with Cisco G.993.5 (vectoring) and G.INP?
I have updated my firmware to the 2014 release A2pv6C039m.d24h - but am not able to find complete information on it's specifications relative to how Chorus is deploying this.
Some on the ground feedback would be much appreciated, thanks.
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
MichaelNZ:
Following on from this thread here:
https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=222828
Has anyone had any experience with Cisco G.993.5 (vectoring) and G.INP?
I have updated my firmware to the 2014 release A2pv6C039m.d24h - but am not able to find complete information on it's specifications relative to how Chorus is deploying this.
Some on the ground feedback would be much appreciated, thanks.
long as your firmware supports it, should just work.
Chorus are doing the whole zero touch thing (not a fan) so even if your not vectored it won't just stop working.
i'd wait and see what happens
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:
long as your firmware supports it, should just work.
Chorus are doing the whole zero touch thing (not a fan) so even if your not vectored it won't just stop working.
That wouldn't be any fun now, would it?
I am a rural user who has been advised our exchange is being upgraded in a few days. I'm certainly keen on extra speed.
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
MichaelNZ:
That wouldn't be any fun now, would it?
I am a rural user who has been advised our exchange is being upgraded in a few days. I'm certainly keen on extra speed.
Depending on crosstalk, you might not even see any noticeable gains tbh.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
MichaelNZ:
Following on from this thread here:
https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=222828
Has anyone had any experience with Cisco G.993.5 (vectoring) and G.INP?
I have updated my firmware to the 2014 release A2pv6C039m.d24h - but am not able to find complete information on it's specifications relative to how Chorus is deploying this.
Some on the ground feedback would be much appreciated, thanks.
We have found that some cisco software/firmware releases have issues. Specifically 887VA and 867
Any firmware which says it supports vectoring, reports vectoring capable to the DSLAM, but it constantly resyncs (every 20 seconds)
If the firmware is older (I think whatever was bundled with 15.1), it reports to the DSLAM as not vectoring capable, and Zero-Touch takes care if it - it syncs fine. (with no vectoring gain)
If we detect flapping services when deploying vectoring, we will force the port into normal VDSL mode so it syncs but does not see any vectoring gain.
My understanding is that a case is open with Cisco (via Spark).
ios 15.6 includes the option to disable vectoring: (we used c860vae-advsecurityk9-mz.156-3.M4.bin)
controller VDSL 0
operating mode vdsl2
vectoring none
-Brent
BMarquis:
My understanding is that a case is open with Cisco (via Spark).
ios 15.6 includes the option to disable vectoring: (we used c860vae-advsecurityk9-mz.156-3.M4.bin)
Thanks @BMarquis
Which modem firmware are you using?
Have you tried a modem firmware update?
WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET
MichaelNZ:
Thanks @BMarquis
Which modem firmware are you using?
Have you tried a modem firmware update?
@MichaelNZ I'm not - I work for Chorus so this was discovered part of our vectoring testing/trials.
The only help I can be at the moment is that when we enable vectoring for your cabinet, we'll try to ensure you aren't impacted.
If you notice you are resyncing every 20seconds, make sure you are on 15.6 and use the commands I provided above to disable vectoring on the cisco.
(Download 15.6 now just in case! )
Note that we've only seen the issue with 887VA and 867VAE
BMarquis:
MichaelNZ:
Following on from this thread here:
https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=222828
Has anyone had any experience with Cisco G.993.5 (vectoring) and G.INP?
I have updated my firmware to the 2014 release A2pv6C039m.d24h - but am not able to find complete information on it's specifications relative to how Chorus is deploying this.
Some on the ground feedback would be much appreciated, thanks.
We have found that some cisco software/firmware releases have issues. Specifically 887VA and 867
Any firmware which says it supports vectoring, reports vectoring capable to the DSLAM, but it constantly resyncs (every 20 seconds)
If the firmware is older (I think whatever was bundled with 15.1), it reports to the DSLAM as not vectoring capable, and Zero-Touch takes care if it - it syncs fine. (with no vectoring gain)
If we detect flapping services when deploying vectoring, we will force the port into normal VDSL mode so it syncs but does not see any vectoring gain.
My understanding is that a case is open with Cisco (via Spark).
ios 15.6 includes the option to disable vectoring: (we used c860vae-advsecurityk9-mz.156-3.M4.bin)
controller VDSL 0
operating mode vdsl2
vectoring none
-Brent
ouch, that one's still in there? Did you happen to fingerprint and size the amount of affected lines?
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
|
|
|