Cloud networking is an increasingly important part of the infrastructure that supports industrial automation. Manufacturing operations depend on connected systems, while the networks behind those systems must accommodate changing workloads and architectures. Arista Networks’ 2017 annual report describes several developments in this area: updates to its routing platforms, new ways to deploy its network operating system, and software aimed at simplifying hybrid-cloud management. These announcements offer a useful view of how data center networking was evolving—and of the practical issues technical teams should consider when evaluating network infrastructure.
Cloud networking expands beyond hardware capacity
A network platform is not defined by switching or routing hardware alone. Its operating system and management approach also influence how infrastructure can be deployed and maintained. In its 2017 report, Arista highlighted EOS, its network operating system, alongside CloudVision, and reported having shipped more than 15 million cloud networking ports worldwide with those technologies.
For industrial organizations, the broader lesson is to evaluate the network as a combination of forwarding capacity, software and operational practices. Plant and enterprise environments may have different requirements, but both need teams to understand how network devices are configured, how infrastructure is managed, and how changes fit into the wider architecture. The annual report does not specify how these technologies would be used in industrial control environments, so suitability for a particular operation requires its own technical assessment.
Containerized EOS offers another deployment model
One of the report’s software announcements was containerized EOS, or cEOS. Arista described cEOS as supporting alternate models for procuring, packaging and deploying EOS. This is significant as a deployment concept: it makes the network operating system available in a containerized form, rather than limiting discussion of EOS to its role on network hardware.
For system integrators and infrastructure teams, a different packaging and deployment model can prompt practical design questions. How will a software-based network component fit into existing workflows? What will teams need to consider when managing it alongside physical network devices? How will responsibilities for configuration and ongoing operations be organized? The report establishes that cEOS supports alternative ways to deploy EOS; it does not provide details about specific integrations or use cases. Those should be verified against the requirements of the intended environment.
Hybrid cloud management and operational complexity
Arista also introduced its Any Cloud software platform. The company said the platform was intended to simplify integration and management of hybrid clouds, reducing operational costs and complexity for enterprises. The announcement reflects a challenge faced by organizations that need to manage network infrastructure across more than one environment: coordinating those environments can add management work and make operations harder to oversee.
For operations leaders, the relevant evaluation is not simply whether a platform supports a hybrid-cloud model. Teams should also consider what “simplifying management” means for their own architecture. Important questions include which environments need to be connected, how network operations are currently divided, and where integration effort or complexity is concentrated. The report does not give a technical breakdown of Any Cloud’s functions, so organizations should seek implementation details before drawing conclusions about how it would fit their systems.
Routing capacity, density and power considerations
The annual report also announced Arista’s R2 Series routing platforms. It described the next-generation platforms as offering twice the density and half the power of legacy custom router products, with more than 150 Tbps of capacity. These are company-reported comparisons and specifications from the 2017 report; they should not be treated as a direct measure of performance in any particular installation.
For network architects, capacity is only one part of platform selection. Density and power are also relevant when planning infrastructure, but their significance depends on the existing design and operational requirements. Engineers should compare platform specifications with expected traffic, deployment constraints and the role the equipment will serve. The report’s figures provide context for the announced platform, not a substitute for assessing the needs of a specific data center or enterprise network.
What automation teams should take from these developments
Together, the announcements highlight three areas that technical decision-makers can examine when planning network infrastructure:
- Deployment flexibility: Consider how operating-system packaging and deployment choices align with the team’s architecture and management processes.
- Cross-environment operations: Identify where hybrid-cloud integration creates complexity and what capabilities a management approach would need to address.
- Infrastructure trade-offs: Assess routing capacity, equipment density and power requirements in the context of the intended deployment.
These considerations matter to industrial automation teams because network decisions support the systems and applications used across an organization. They also reinforce the importance of evaluating software, hardware and operational requirements together rather than treating them as isolated purchasing decisions.
Conclusion
Arista’s 2017 annual report presents cloud networking as a combination of network operating software, evolving deployment models, hybrid-cloud management and routing hardware. EOS and cEOS point to different ways of packaging and deploying network software; Any Cloud addresses hybrid-cloud integration and management; and the R2 Series announcement emphasizes capacity, density and power. For engineers, integrators and plant leaders, the practical next step is to map these themes to their own network architecture and verify technical details against the needs of each deployment.