Cisco Systems

This document describes how to achieve a Virtual Extensible LAN (VXLAN) Ethernet Virtual Private Network (EVPN) Multi-Site design by integrating VXLAN EVPN fabrics with EVPN Multi-Site architecture for seamless Layer 2 and Layer 3 extension. In addition to the technical details, this document presents design considerations and sample configurations to illustrate the EVPN Multi-Site approach. The VXLAN Border Gateway Protocol (BGP) EVPN fabric (or site) can be extended at Layer 2 and Layer 3 with various technologies. However, the sole focus of this document is on how this extension can be achieved by using EVPN Multi-Site architecture, an integrated interconnectivity approach for VXLAN BGP EVPN fabrics. EVPN Multi-Site technology is based on IETF draft-sharma-multi-site-evpn. VXLAN EVPN Multi-Site architecture is independent of the transport network between sites. Nevertheless, this document provides the best practices and recommendations for a successful deployment.

Service providers worldwide face high customer expectations along with growing demand for network services. The need for efficiency, high availability, and rapid time to deployment has never been greater, but the network has never been more complex. Too often, supporting the required density and high availability in access and edge networks means using hundreds of complicated routing platforms and protocols that increase operating costs and
slow time to revenue. Now, Cisco offers a revolutionary approach to high availability and access network density based on virtual network architecture. With the new Cisco® Network Virtualization (nV) technology in the Cisco ASR 9000 Series Aggregation Services Routers, service providers can radically simplify the network, reduce operating costs, and improve network and service resiliency, all while supporting greater scale and density. This document provides an overview of the Cisco virtual network architectural model and describes how Cisco nV capabilities can be used to optimize edge and access services.

This article primarily discusses the SNMP monitoring capabilities of an appliance running Firepower Threat Defense (FTD). It also looks at health policies that can be configured from the Firepower Management Center (FMC), which is another way to monitor the health of the managed devices automatically from the FMC. There are at least three options available for monitoring the health of a Cisco Firepower® appliance running FTD. Two of these options rely on SNMP from two different software sources. The third one relies on custom scripts that FMC runs on its managed devices.

“Multitenancy is a reference to the mode of operation of software where multiple independent instances of one or multiple applications operate in a shared environment. The instances (tenants) are logically isolated, but physically integrated. The degree of logical isolation must be complete, but the degree of physical integration will vary. The more physical integration, the harder it is to preserve the logical isolation. The tenants (application instances) can be representations of organizations that obtained access to the multitenant application (this is the scenario of an ISV offering services of an application to multiple customer organizations). The tenants may also be multiple applications competing for shared underlying resources (this is the scenario of a private or public cloud where multiple applications are offered in a common cloud environment).”

– Gartner

Cisco SD-WAN also helps you connect and manage multiple branch offices while lowering WAN costs and improving security. The solution provides a secure hybrid overlay technology that virtualizes the enterprise WAN with centralized management and control. Cisco SD-WAN builds an overlay fabric that is carrier and transport-agnostic. This allows network-wide segmentation for lines of business, compliance, and business partners. It also offers optimized performance for public clouds and the Internet.

With the Cisco SD-Branch, network functions run inside a virtualized environment. SD-Branch deployments can even split up virtual appliances into discrete functions and then centralize these functions (such as any related to enterprise policy) into the headquarters, private data centre, or hybrid cloud, rather than have to configure and deploy it all in branches. This approach is known as a Software-Defined WAN (SD-WAN).