Welcome to Quic!!! 😁

richms:

 

amanzi:

 

I'm just starting to plan my move from Voyager to Quic. Can someone confirm the best approach, since there seems to be two different recommendations above? I haven't given my notice to Voyager yet - I want to formulate a plan first.

 

Also, am I correct in thinking that using DHCP over PPPoE would be recommended?

 

 

I gave notice for the 30 days with a date at the end of the month, I signed up with quic and chose the day before that date so only 1 day of duplicate payments.

 

It was not seamless because I was changing wan configuration. when it conked out I had to go into my unifi control plane and reconfigure the wan and it was back up again. I chose not to get a second port service because my ont is buried behind stuff, but after that they wanted the number from it so I had to move boxes to get to it anyway.

 

With the second port service, am I correct in thinking that I can get that to go live with Quic while the Voyager connection is still also live? And then I just move the cable to the Quic port when I'm ready? If so, that sounds like the safest approach. I'm not expecting this to be seamless because I'll need to fiddle with the router config with the new IP addressing, but I like the idea of being able to reconnect with the Voyager connection temporarily if all goes pear shaped.

michaelmurfy:

 

Assuming you’re in a Chorus area you’ll find it’ll be fully automated provisioning. 

 

Just sign up with Quic with the same VLAN settings as Voyager on the day you want and it’ll just magically move across + you shouldn’t notice anything. 

 

Is this a different process if we are in an Enable area?

phrozenpenguin: Is this a different process if we are in an Enable area?

Enable + TFF are not automated (yet) so you’ll get a provisioning email normally the next business day when you submit your order.

Plan changes as well as provisioning on Chorus is now automated. 

michaelmurfy:

 

phrozenpenguin: Is this a different process if we are in an Enable area?

 

Enable + TFF are not automated (yet) so you’ll get a provisioning email normally the next business day when you submit your order.

 

Plan changes as well as provisioning on Chorus is now automated. 

 

Enable and TFF are so far behind, I’m pretty sure they’re still provisioning connections via carrier pigeon - and the pigeon’s on annual leave.

Delorean:

 

Enable and TFF are so far behind, I’m pretty sure they’re still provisioning connections via carrier pigeon - and the pigeon’s on annual leave.

 

@amanzi: With the second port service, am I correct in thinking that I can get that to go live with Quic while the Voyager connection is still also live? And then I just move the cable to the Quic port when I'm ready? If so, that sounds like the safest approach. I'm not expecting this to be seamless because I'll need to fiddle with the router config with the new IP addressing, but I like the idea of being able to reconnect with the Voyager connection temporarily if all goes pear shaped.

Ah just saw this. If you do a 2nd port connection via Quic you can do exactly this. Per your other thread there shouldn't be much to configure (apart from the routed subnet stuff) but this will be the safest approach if you've got a bigger configuration.

Leave PPPoE active and just simply match your VLAN tag as your Voyager connection then things should just move over once you've updated your src-nat / dst-nat rules with your new IP addressing information.