On Mon, 2006-04-24 at 09:25 +0200, Marc van Selm wrote: On Sunday 23 April 2006 17:42, Lea Roberts wrote: [..]
IPv6 has made it possible to renumber the network almost automatically. it seems possible to make that change without a "flag day" and an outage. however, the tools are mostly *NOT* there for similarly easy renumbering of router ACLs and firewall configs and DNS, so as the size of the network increases, large organizations are saying there is still a significant cost to renumbering (at this time...). one can only hope that appropriate tools will be developed to make full renumbering reasonably painless.
Did anyone try that in a mission crytical 200+ site network? That is what I'm looking at. I'm not conviced yet that one would really like to do that. Is anyone brave enough to calculate the risks and costs for a network like that? (We solved it via the LIR route by the way.)
Unless you have a record of all the places where you have stored the sites IPv6 addresses and have (semi) direct access to change these, do not rely on having external parties update items on your list then it might be 'easily' done, for large varying values of 'easy'. If you do not meet any of the above then you will be in a large amount of pain in doing so. Especially the remote parties problem will cause a lot amount of pain as they need to do it in sync with you and they need to find out where all the changes have to be made. Even changing a 'home' setup can be hard when your DNS for instance is hosted at a remote site where you do not have direct access to. Renumbering is *NOT* simple and *CAN't* be automated (no remote company will allow you full automatic access to change things in their setup, think firewall rules for instance...) Greets, Jeroen