Modern data centers based on hyperscale, leaf-spine switching
architectures are growing so large and complex they are outstripping the
capacity of operators to engineer, configure and manage these networks
using traditional tools and techniques. As a result, data center operators
are looking for new ways to automate workflows, maximize uptime and
increase operational agility while reducing operating costs
When Bloomberg Television opened its state-of-the-art broadcast facility in the
company’s new European Headquarters in London last year, network engineers from
the company’s IT infrastructure team collaborated with Apstra to successfully pilot its
technology in order to gain visibility across and more effectively manage the network
fabric supporting the building’s media production systems.
The enterprise data center has undergone several major shifts since the introduction of
computing as a business resource. Data centers have evolved from mainframes to client/server
to virtual servers, and then to being “software defned,” and fnally to their current state of disaggregation. Today, we sit on the precipice of the next major data center transition—the evolution
to an intent-based data center (IBDC) (Exhibit 1). Each transition saw the cost of computing
decrease and the importance of the network increase, and each enabled organizations to boost
the efciency of their data center operations and improve asset utilization—ultimately leading to a
better experience for users
Customers and partners, and recently investors ask the question “How is one Intent-Based
Networking (IBN) offering different than the others?” And more often than not I hear answers that
sound subjective, descriptive, and subject to interpretation. What is needed are tangible, fact-based
nomenclature that can help you reason about the maturity of IBN solutions. Using this nomenclature,
we should be able to map IBN solutions to an IBN maturity level, starting with Level 0 (low
maturity/incomplete) and going up to Level 3 which enables a fully compliant IBN solution
IT organizations are facing new challenges as a result of digital transformation,
widespread cloud and SaaS adoption, mobile proliferation and pervasive IoT
deployments. They must build and operate their internal data centers to deliver
high availability for mission critical applications, rapidly onboard new applications
and scale capacity on demand – all within the mandate to be cost competitive
with infrastructure as a service providers (IaaS) like AWS and Azure. They are
architecting and building new Intent-Based Data Centers to deliver private cloud
services to their internal and external customers.
This in-depth white paper explains how service providers are capitalizing on Intent-Based Networking — a new and effective networking model that provides a way of abstracting an application, feature, network, or resource in such a way that the intent is exposed, but the implementation is hidden.
AOS delivers powerful, intent-driven automation of network services in vendor-agnostic environments by delivering it as an easily consumable service in response to consumer-specified intent. Network devices serve packets, AOS services serve application workloads.
According to numerous studies, 70-80% of outages are due to configuration change applied to a living system, and not due to initial deployment. Initial, one-time deployment can be seen as sort of a “hello world” application; the real complexities arise as the system evolves. With AOS, configuration, telemetry, and expectations are derived from the single source of truth - the intent - in an idempotent fashion, and as such there is no implementation difference between initial deployment or change management.
Intent Based Analytcs (IBA), an important feature of AOS and a main enabler for closed loop telemetry is described in this whitepaper. Prerequisites for this whitepaper include a basic understanding of the Apstra AOS soluton, such as from the white paper ttled “The Apstra Operatng System (AOS) Architecture Overview.
You may have read in the news about horrific security gaps that have the potential of bringing down whole infrastructures, leaking critical business and personal data, and exposing organizations to massive liability.
There is no question that improving organizations’ security posture is a critical requirement for infrastructure and security teams.
Years ago, there were proprietary networking solutions like IBM Token Ring. Every new PO had to go to the same vendor if customers wanted to ensure connectivity.
Then came Ethernet which promised to be an open interoperable standard. However, vendors recreated lock-in by implementing proprietary VLAN extensions such as private VLANs.
Typically, and since the dawn of time, network infrastructure teams chose the hardware and switch Operating System (OS) first, then designed their infrastructure, including how their infrastructure was built around this choice.
The response to the question “How is one Intent-Based Networking offering different than the others?” typically sounds subjective, descriptive, and open to interpretation. What is needed is a tangible, objective, and fact-based nomenclature that can help you rationalize the maturity of Intent-Based Networking solutions. Using this nomenclature, we should be able to map Intent-Based Networking solutions to a specific maturity level, starting with Level 0 (low maturity/incomplete) up to Level 3 which enables a fully capable Intent-Based Networking solution (mature/complete).
Apstra introduced the notion of Intent-Based Networking and Self-Operating Networks™ in June of 2016, and in our blog “Intent Based Networking: What Is It” we provided a definition of Intent-Based Networking, listing capabilities that a complete Intent-Based Networking system needs to provide. The goal is to categorize maturity levels of various Intent-Based Networking implementations and enable network operators to
When Bloomberg Television opened its state-of-the-art broadcast facility in the company’s new European Headquarters in London last year, network engineers from the company’s IT infrastructure team collaborated with Apstra to successfully pilot its technology in order to gain visibility across and more effectively manage the network fabric supporting the building’s media production systems.
Yahoo Japan Corporation, one of Japan’s largest Internet service providers, is deploying Clos fabric networks for efficiently addressing their ever-growing data center traffic. Apstra® was selected for streamlining the design, build, and operations of these networks.