The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Cisco Elastic Services Controller Install and Upgrade Guide describes the installation requirements, the installation procedures, and the upgrade procedures for Cisco Elastic Services Controller.
This preface contains the following sections:
This guide is responsible for network administrators who are responsible for installing, provisioning, configuring, and monitoring Virtual Network Functions (VNFs). ESC can be deployed on OpenStack, VMware vCenter, and KVM and manage its VNFs a Virtual Infrastructure Manager (OpenStack and VMware vCenter).
The administrator must be familiar with the VIM layer, VMware and OpenStack resources, and the commands used.
The below table defines the terms often used in this guide.
Terms |
Definitions |
---|---|
ESC |
Cisco Elastic Services Controller (ESC) is a Virtual Network Function Manager (VNFM), performing life cycle management of Virtual Network Functions. |
HA |
ESC High Availability (HA) is a solution for preventing single points of ESC failure and achieving minimum ESC downtime. |
KPI |
Key Performance Indicator (KPI) measures performance management. KPIs specify what, how and when parameters are measured. KPI incorporates information about source, definitions, measures, calculations for specific parameters. |
NFV |
Network Function Virtualization (NFV) is the principle of separating network functions from the hardware they run on by using virtual hardware abstraction. |
NFVO |
NFV Orchestrator (NFVO) is a functional block that manages the Network Service (NS) lifecycle and coordinates the management of NS lifecycle, VNF lifecycle (supported by the VNFM) and NFVI resources (supported by the VIM) to ensure an optimized allocation of the necessary resources and connectivity. |
NSO |
Cisco Network Services Orchestrator (NSO) is an orchestrator for service activation which supports pure physical networks, hybrid networks (physical and virtual) and NFV use cases. |
Service |
A Service consists of single or multiple VNFs. |
VIM |
The Virtualized Infrastructure Manager (VIM) adds a management layer for the data center hardware. Its northbound APIs are consumed by other layers to manage the physical and virtual resources for instantiation, termination, scale in and out procedures, and fault & performance alarms. |
VM |
A Virtual Machine (VM) is an operating system OS or an application installed on a software, which imitates a dedicated hardware. The end user has the same experience on a virtual machine as they would have on dedicated hardware. |
VNF |
A Virtual Network Function (VNF) consists of a single or a group of VMs with different software and processes that can be deployed on a Network Function Virtualization (NFV) Infrastructure. |
VNFM |
Virtual Network Function Manager (VNFM) manages the life cycle of a VNF. |
vMS |
Cisco vMS is a Network Functions Virtualization (NFV) orchestration platform that enables fast deployment of cloud-based networking services. |
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.