IPv6 can come
...because with AixBOMS, you are perfectly prepared!
The bad news first:
IPv6 is inevitable, there's no getting around it.
Although this should be common knowledge by now, many companies struggle with it. The reasons for this are widely discussed. The introduction of IPv6 is often treated like an address “roll-out,“ and the functional and organisational advantages are neglected. To be able to use these requires a concept that takes the company's organisational structure into account more than has ever been possible before.
Now for the good news:
With AixBOMS, you can start the introduction immediately!
Little attention is also paid to the use of IPAM tools, which provide efficient support from the very first phase of the migration and even during the planning stages. This now finally offers a favourable opportunity to break away from the rudimentary list maintenance that predominates for IPv4 and to adequately address the far more complex management of IPv6 structures with suitable tools. After all, communication via the corporate network forms the basis for the holistic management and monitoring of the entire IT infrastructure and services.
Leave the worries to others
AixBOMS has a solution for everything!
The result of more than 5 years of intensive work on this topic is a mature AixBOMS Networking. We have already demonstrated its suitability as a powerful expert solution for the professional management of IPv4 and IPv6 networks on multiple occasions in practice when operating worldwide enterprise customer networks.
Problem 1: IPv6 affects all areas of the company
Communication over the company network is fundamental to all business processes. The more complex and heterogeneous its structure and participants, the more difficult any changes become. The introduction of IPv6 affects everything Participants, and this also includes those integrated into daily operations via proprietary systems (such as sensors, sockets, telephones/mobile phones, etc.). It is still not a given today that the manufacturer of these components offers IPv6 support.
Problem 2: Conversion means new acquisition
Even if the manufacturer supports IPv6 today, it may require the purchase of new components and a software update. This can become quite expensive in total, as many devices (routers, switches, etc.) are expensive purchases that are depreciated over several years, or they are small devices that are used in large quantities. Software licenses can also cause problems during a transition if they are IP address-dependent.
Problem 3: Dual-Stack costs extra
If IPv4 and IPv6 are operated (temporarily), this incurs additional costs in many areas, e.g. for switching between the two protocols, for re-packaging and especially for double administration. The latter must adapt to the new IPv6 network structure and cannot simply be maintained 1:1 with the existing IPv4 documentation. Furthermore, intermediate elements are required for the mapping of IPv4 to IPv6 and vice versa. In large networks, this can lead to the limits of what is feasible if one wants to completely forgo the support of suitable tools.
Problem 4: It's impossible without a concept!
Unfortunately, that's only half the story, because in reality, you need two! A concept is needed to define the network structure and address allocation in an IPv6-compliant manner and optimised for the respective area of application. Another one is required when it comes to the gradual introduction
from IPv6 in temporary dual operation and finally the systematic shutdown of IPv4. Those who can use software for this purpose, which knows and can incorporate projects, workflows, work orders, responsibilities, ... alongside the basic information for network and address management such as component, user, locations, organisational structure, ... can take a back seat. Further concepts, e.g. for company-compliant hostname generation, would at least have to be adapted to IPv6 conditions.