Since it seems to be ipv6 month here at NZNog I thought I would bring this up. Some of you have commented that Orcon is in trial mode for IPv6 and are probably wondering why we haven’t progressed. We have had IPV6 enabled for a while and have a good number of ipv6 customers online now. However we found an issue on the Chorus network which stopped us rolling it out further. (UFB ipv6 was another battle which requires beer!) What we found was some Chrous DSLAMS with certain card types would drop IPV6CP packets in one direction when doing the PPPoE->PPPoA conversation. It would seem that these cards don’t support Ipv6. Weirdly enough it would seem it is the newer card types used for Broadband IP. (citation needed). This in itself isn’t a major but we also found our NFV4 modem would reset its entire PPPoE stack if the IPV6CP conversation started but didn’t complete as expected, so customers would constantly be disconnected and cycle around. (The Genius modem works well with ipv6) The NFV4 issue aside (we are resolving with the Vendor). We approached the Chorus tech team and they helped identify the issue but that’s is where its hit a brick wall. The Chorus op team are not keen on fixing the issue nationwide as it involves new code versions, a massive amount of testing and a long rollout program. (I can understand where they are coming from). To summarise: IPV6 doesn’t work on Chorus EUBA on some line card types Only affect PPPoE->PPPoA translation PPPoE end to end is fine. Chorus say IPV6 not supported on EUBA Customer numbers effected are smallish. We will fix the NFV4 issue, but keen to rollout more IPV6 to all customers, not just the lucky ones on card types which work. Has any other ISP’s (the bigger ones especially) noticed this? As it will require some pressure to get some progress. Cheers, Simon Allard Orcon/Callplus [cid:image92256e.PNG(a)016ea4ce.48a80470] Simon Allard // Senior Network Architect D: 09 550 2790 M: 020 100 0790 F: www.callplus.co.nzhttp://www.callplus.co.nz | www.slingshot.co.nzhttp://www.slingshot.co.nz | www.flip.co.nzhttp://www.flip.co.nz | www.orcon.net.nzhttp://www.orcon.net.nz This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
Hi All, Simon is spot on with the cause/symptoms of the issue. I may have given Simon that perception that " The Chorus op team are not keen on fixing the issue nationwide" but it wasn't intended - Chorus certainly do want to fix this issue (and a couple of others that are floating around!) some of the hurdles are the scale and time of test and rollout that Simon alluded to. Our operational teams are working with the vendor to identify a suitable software version containing the fixes we require - we need to be VERY sure that the release we move to is also suitable for any future changes/features we might want. We need to get this right, as upgrading ~6000 ISAMs is no mean feat! I don’t have any timeframes, but there are a number of people in multiple areas of Chorus working on the what/when/how for a copper network upgrade. IPV6, particularly IPV6CP, will be in the test plan.
'Chorus say IPV6 not supported on EUBA' Might be slightly strongly worded. I personally didn't believe that we have a commitment to provide IPv6, but it should certainly work (I'm not sure of our Product teams view on this!) - hence investigating our options for a long term solution.
Only affect PPPoE->PPPoA translation This also means that IPv6 over VDSL (PTM) should be fine.
(UFB ipv6 was another battle which requires beer!) And should, as far as I know, be working flawlessly on our network:)
I, much like Simon, would be very interested to hear from anyone else who has hit this problem. Cheers, Brent From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Simon Allard Sent: Tuesday, 27 January 2015 9:57 a.m. To: NZNOG Subject: [nznog] Chorus EUBA + IPV6 Since it seems to be ipv6 month here at NZNog I thought I would bring this up. Some of you have commented that Orcon is in trial mode for IPv6 and are probably wondering why we haven’t progressed. We have had IPV6 enabled for a while and have a good number of ipv6 customers online now. However we found an issue on the Chorus network which stopped us rolling it out further. (UFB ipv6 was another battle which requires beer!) What we found was some Chrous DSLAMS with certain card types would drop IPV6CP packets in one direction when doing the PPPoE->PPPoA conversation. It would seem that these cards don’t support Ipv6. Weirdly enough it would seem it is the newer card types used for Broadband IP. (citation needed). This in itself isn’t a major but we also found our NFV4 modem would reset its entire PPPoE stack if the IPV6CP conversation started but didn’t complete as expected, so customers would constantly be disconnected and cycle around. (The Genius modem works well with ipv6) The NFV4 issue aside (we are resolving with the Vendor). We approached the Chorus tech team and they helped identify the issue but that’s is where its hit a brick wall. The Chorus op team are not keen on fixing the issue nationwide as it involves new code versions, a massive amount of testing and a long rollout program. (I can understand where they are coming from). To summarise: IPV6 doesn’t work on Chorus EUBA on some line card types Only affect PPPoE->PPPoA translation PPPoE end to end is fine. Chorus say IPV6 not supported on EUBA Customer numbers effected are smallish. We will fix the NFV4 issue, but keen to rollout more IPV6 to all customers, not just the lucky ones on card types which work. Has any other ISP’s (the bigger ones especially) noticed this? As it will require some pressure to get some progress. Cheers, Simon Allard Orcon/Callplus Simon Allard // Senior Network Architect D: 09 550 2790 M: 020 100 0790 F: www.callplus.co.nz | www.slingshot.co.nz | www.flip.co.nz | www.orcon.net.nz This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments. This communication, including any attachments, is confidential and may be legally privileged. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. No confidentiality or privilege is waived or lost by any mis-transmission or error. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
On Tue, Jan 27, 2015 at 10:37 AM, Brent Marquis
Only affect PPPoE->PPPoA translation This also means that IPv6 over VDSL (PTM) should be fine.
Can confirm, that IPv6 over the Wholesale VDSL service works fine. Should also be doing some Boost VDSL testing next week as well. Cheers Dave
On 27/01/2015 10:38 AM, "Brent Marquis"
Hi All,
Simon is spot on with the cause/symptoms of the issue. I may have given Simon that perception that " The Chorus op team are not
Our operational teams are working with the vendor to identify a suitable software version containing the fixes we require - we need to be VERY sure
keen on fixing the issue nationwide" but it wasn't intended - Chorus certainly do want to fix this issue (and a couple of others that are floating around!) some of the hurdles are the scale and time of test and rollout that Simon alluded to. that the release we move to is also suitable for any future changes/features we might want. We need to get this right, as upgrading ~6000 ISAMs is no mean feat!
I don’t have any timeframes, but there are a number of people in multiple areas of Chorus working on the what/when/how for a copper network upgrade. IPV6, particularly IPV6CP, will be in the test plan.
I can think of something else that should be in that test plan that would make the world of difference for a whole lot of customers too. ;)
'Chorus say IPV6 not supported on EUBA' Might be slightly strongly worded. I personally didn't believe that we
have a commitment to provide IPv6, but it should certainly work (I'm not sure of our Product teams view on this!) - hence investigating our options for a long term solution.
Only affect PPPoE->PPPoA translation This also means that IPv6 over VDSL (PTM) should be fine.
(UFB ipv6 was another battle which requires beer!) And should, as far as I know, be working flawlessly on our network:)
I, much like Simon, would be very interested to hear from anyone else who
has hit this problem.
Cheers, Brent
From: nznog-bounces(a)list.waikato.ac.nz [mailto:
Sent: Tuesday, 27 January 2015 9:57 a.m. To: NZNOG Subject: [nznog] Chorus EUBA + IPV6
Since it seems to be ipv6 month here at NZNog I thought I would bring
nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Simon Allard this up.
Some of you have commented that Orcon is in trial mode for IPv6 and are
probably wondering why we haven’t progressed.
We have had IPV6 enabled for a while and have a good number of ipv6
customers online now. However we found an issue on the Chorus network which stopped us rolling it out further. (UFB ipv6 was another battle which requires beer!)
What we found was some Chrous DSLAMS with certain card types would drop
IPV6CP packets in one direction when doing the PPPoE->PPPoA conversation. It would seem that these cards don’t support Ipv6. Weirdly enough it would seem it is the newer card types used for Broadband IP. (citation needed). This in itself isn’t a major but we also found our NFV4 modem would reset its entire PPPoE stack if the IPV6CP conversation started but didn’t complete as expected, so customers would constantly be disconnected and cycle around. (The Genius modem works well with ipv6)
The NFV4 issue aside (we are resolving with the Vendor). We approached
the Chorus tech team and they helped identify the issue but that’s is where its hit a brick wall. The Chorus op team are not keen on fixing the issue nationwide as it involves new code versions, a massive amount of testing and a long rollout program. (I can understand where they are coming from).
To summarise: IPV6 doesn’t work on Chorus EUBA on some line card types Only affect PPPoE->PPPoA translation PPPoE end to end is fine. Chorus say IPV6 not supported on EUBA Customer numbers effected are smallish.
We will fix the NFV4 issue, but keen to rollout more IPV6 to all
customers, not just the lucky ones on card types which work.
Has any other ISP’s (the bigger ones especially) noticed this? As it will
require some pressure to get some progress.
Cheers, Simon Allard Orcon/Callplus
Simon Allard // Senior Network Architect D: 09 550 2790 M: 020 100 0790 F:
www.callplus.co.nz | www.slingshot.co.nz | www.flip.co.nz |
www.orcon.net.nz
This message and any attachments contain privileged and confidential
are not the intended recipient of this message, you are hereby notified
information. If you that any use,
dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.
This communication, including any attachments, is confidential and may be legally privileged. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. No confidentiality or privilege is waived or lost by any mis-transmission or error. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Hi All,
Some people were interested in this at the time, so it’s probably worth providing an update….
A fix for the below IPV6CP issue is included (along with some other fixes!) in the patch we are currently applying to the copper ISAMs in our network.
The current plan has this patch deployment completing mid to late September.
Cheers,
Brent
Brent Marquis | Layer 2 Network Specialist
[cid:image001.png(a)01D0CDEF.5F3A04A0] Chorus | T : +64 4 8964169 | M :+64 27 2290923
From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Simon Allard
Sent: Tuesday, 27 January 2015 9:57 a.m.
To: NZNOG
Thanks Brent for the update ☺
From: Brent Marquis [mailto:Brent.Marquis(a)chorus.co.nz]
Sent: Monday, 3 August 2015 1:42 p.m.
To: Simon Allard
participants (5)
-
Brent Marquis -
Dave Mill -
Peter Lambrechtsen -
Simon Allard -
Simon Allard