Do you have Questions ?
Ümit Celebi
Key Account Manager
A vendor switch is often avoided for convenience, even though it may be the right strategic response. Whether setting up a new location, consolidating suppliers or optimising support structures, a well-planned switch offers the opportunity to reduce complexity and realign infrastructure. MTF has completed the switch from Cisco to HPE Aruba in its own private cloud environment – during productive operation and with virtually no interruption. The findings show that with the right planning, a vendor switch is feasible and measurable.
In IT, standing still is not an option – especially when it comes to network infrastructure. Data centres form the backbone of numerous services that companies rely on every day. There are many reasons for switching vendors: consolidating to a central partner for servers and networks offers better terms and consistent support. Setting up new locations or relocating creates an opportunity to rethink the architecture. Changing partner relationships or new licensing models can tip the scales.
MTF recently took this step: in its own private cloud environment, the switching infrastructure was switched from Cisco to HPE Aruba. This was not a spontaneous decision, but the result of an evaluation process that weighed up technical requirements, future viability and operational efficiency. A key strategic factor was the consolidation of HPE as a partner for servers and networks – a single point of contact for support, better terms and conditions, and a consistent management philosophy.
Cloud platforms typically run in highly available data centres with redundant connections and complex network structures. This was also the case in the MTF Cloud: Cisco had provided reliable services for years – stability and feature diversity were beyond question. The hardware was not broken, the setup was not unstable.
But as is often the case in mature environments, a pattern emerged over time: the larger the platform became, the greater the effort required for management, provisioning and customisation. Client separation became more complex, and setting up new segments took longer. Automation worked, but not consistently. Monitoring was spread across several tools.
Changing network providers in a data centre is not a trivial decision. Most companies shy away from this step due to the high risk, complex project management, potential production interruptions, investment costs and team training.
These concerns are justified. Nevertheless, a strategically planned vendor switch can be the right answer if requirements have changed and the existing architecture is no longer optimal. The key is thorough evaluation, clear criteria and a structured migration process.
Many companies operate their IT in their own data centres or in hybrid models. The challenges are similar: increasing demands on security, automation and visibility with limited resources. Just because an infrastructure is running does not mean it is optimal. It is worth regularly evaluating whether requirements have changed. IT managers should ask themselves three questions:
Modern network technologies are not only relevant for hyperscalers or cloud providers. Traditional on-premise environments also benefit from simplified administration through centralised management systems, automated rollouts and configuration controls, better segmentation through modern fabric technologies and real-time transparency via telemetry. Vendor lock-in may seem convenient, but it can slow down innovation. If you want to future-proof your network today, you need less ‘more hardware’ – but more intelligence in control.
An evaluation should not focus on which manufacturer offers the most features, but rather on defining a clear set of requirements.
At MTF Cloud, the main question was: How can a modern network environment be operated with as little complexity as possible without sacrificing control? This resulted in a precise catalogue of requirements: Native multi-tenancy capabilities were a basic prerequisite. Automation should run via an API-first architecture with connection to infrastructure-as-code tools. Centralised management with real-time monitoring was a must – proactive anomaly detection instead of reactive troubleshooting. Zero-touch provisioning was not an option, but a requirement.
HPE Aruba came out on top in this evaluation – thanks to its clear, consistent architecture with a modern, cloud-native approach.
Modern network platforms must have certain core capabilities in order to meet the requirements for automation, availability and operational efficiency:
HPE Aruba meets all the technical requirements of a modern network platform. Aruba Central offers centralised management and automated deployment. The Network Analytics Engine provides proactive monitoring. VSX enables hitless upgrades. The strategically decisive factor was also the consolidation of HPE as the central partner for server and network hardware: a single point of contact for support, better conditions through bundled procurement and a consistent management philosophy across different infrastructure levels.
Changing platforms in a productive network is not something that happens ‘on the side’. It is like open-heart surgery – feasible, but only with precise planning and seamless monitoring. MTF opted for a clear strategy: parallel operation before conversion.
In the first phase, the Aruba switches were installed in parallel with the existing Cisco infrastructure. The network ran redundantly for two weeks so that a real test environment with productive workloads could be run. Performance baselines were recorded, monitoring integration was tested, and the team familiarised themselves with the new tools.
The actual migration took place gradually over four weeks. Thanks to the parallel setup and the well-planned and successfully completed test phase, the production systems could then be migrated step by step to the new platform. The existing redundancies ensured that there was no interruption for our customers at any time. In addition, it was possible to roll back at any time if, contrary to expectations, an environment had shown a problem with the new configuration.
A particular focus was placed on integration into existing systems. Thanks to open interfaces such as REST API and streaming telemetry, seamless integration was achieved – from monitoring tools and security solutions to automation platforms. Zero-touch provisioning proved to be a time saver. A new switch was unpacked, plugged in and automatically retrieved its configuration. After a successful production phase, the old Cisco switches remained in place for two weeks as a fallback before being dismantled. Cloud customers did not notice the change – the greatest success.
Three key success factors can be derived from the migration that was carried out:
A network migration is easily achievable with the right planning and a step-by-step approach. Testing, documentation and a clear rollback plan are critical.
Our Professional IT Services experts have been responsible for this transformation themselves and know the pitfalls first-hand – from virtually uninterrupted migration to seamless integration into existing systems. Let's evaluate together how modernisation with HPE Aruba Networking can simplify your IT infrastructure, reduce your costs and make your business fit for the demands of the next decade.
Whether you want to set up a new location, move to a new building or consolidate your supplier relationships, we will accompany you every step of the way. Contact our IT specialists for a no-obligation discussion about your network strategy.
What are the risks of a vendor switch and how can they be minimised?
The main risks are production interruptions, compatibility issues with existing systems and a lack of team expertise. These can be minimised through thorough planning, extensive testing in parallel operation, a step-by-step approach with rollback options, and early team training. A detailed migration process and open interfaces make integration much easier.
Is a vendor switch also worthwhile for SMEs or only for large companies?
A vendor switch can also be worthwhile for smaller companies – especially if consolidation to a central partner can reduce costs, the existing infrastructure is reaching its limits, or modern requirements such as automation, zero trust or cloud integration can no longer be implemented. The principles of cloud operation also apply to classic on-premise environments.
What are the key success factors for a vendor switch?
Three factors are crucial: First, define clear requirements – don't look for features, but honestly evaluate what is really needed. Second, test extensively – never go straight into production, but test with real workloads in parallel operation. Third, get the team on board – technical migration also involves change management with workshops, documentation and learning time.
What advantages does HPE Aruba offer over traditional Cisco architectures?
HPE Aruba CX offers:
- A unified OS across all switch classes
- API-first architecture for end-to-end automation
- Real-time telemetry instead of SNMP polling
- Modern redundancy concepts (VSX) for hitless upgrades
- ZTP and automated provisioning
- Open interfaces that facilitate integration with existing tools
All in all = less complexity and faster operation.
How long does it take for the investment in a vendor switch to pay for itself?
The payback period depends on several factors: With strategic consolidation, better conditions and reduced support costs can become apparent relatively quickly. Efficiency gains through automation continuously reduce operating costs. Prevented downtime through proactive monitoring delivers additional ROI that is difficult to quantify but is critical to the business. The ROI is highly dependent on the initial situation and individual goals.