Hey again everyone, Just wanted to say thanks for all the people who reached out to me both on and off list. It seems the general consensus is clearing the dhcp lease before unplugging the old router should do the trick. Will give it a go next time, this service came up as expected late yesterday afternoon.
Thanks again. Jarryd Sullivan -----Original Message----- From: AusNOG [mailto:[email protected]] On Behalf Of Jarryd Sullivan Sent: Tuesday, 5 December 2017 11:49 AM To: [email protected] Subject: [AusNOG] iiNet Business NBN Issues G'day all, Over the years we've done a fair few iiNet NBN installations for our customers, however over the years we've also had a number of problems. I'm wondering if anyone can shed some light on the issues we've had. Pretty much 95% of the time if we swap a router over for a customer (e.g. Cisco 867/887 to a Cisco 1921) we have no end of issues getting a DHCP lease on the new router, the usual support response we get when calling business support is to turn the NTD + Router off for 4 hours and then turn it back on and the issue will be resolved. Early on we used to do this, and confirmed it'd work, but I can't understand why we're waiting 4 hours for a business service just by us simply putting a new router in, so I continued to push harder and harder when calling support, one day I managed to get an helpdesk staff member who was speaking to a Level 2 colleague that managed to immediately clear all active sessions for this customer and within seconds we got a DHCP lease. Today I've got another customer again, same issue changing from an older 887 to a 1921 and the configuration is spot on, it was doing my head in until I remembered this issue. Called support, same response, "NBN limitation, wait 4 hours and it'll start working". To which I asked why this doesn't affect Telstra, Aussie Broadband and a number of other providers using IPoE. The helpdesk staff member then did a "kick user" and then an LDAP resync and then apparently he's logged a dcs clear now, to which my customer is now waiting an unknown period of time until this ticket gets sorted. I'd appreciate any help from anyone, or any suggestions to get this working quicker, and hopefully if anyone from iiNet is on list they can address this issue that's been happening for years? Cheers Jarryd Sullivan ________________________________ The information contained in this message and any attachments may be confidential information. If you are not the intended recipient, you must not use or forward the information contained in these documents. If you have received this message in error, please delete the email and notify the sender. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. _______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog _______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
