vices and changing needs of the customer are Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 NFV Practical Implementation some major reasons for the changes in the network. These are also the reason for not implementing automated solutions as there are frequent changes in the network. Configuration changes are done manually in most of the provider environment or by writing a script as there are no well defined protocols or APIs. There is no such data or service model which can streamline the configuration management through well defined protocols or APIs. There are lots of sources of the configuration changes. Network administrator are either modifying/adding the configuration manually time to time by planning a change window and many are writing a script to automate the configuration but these solutions are not scalable. Cisco NSO is a multi vendor controller for service provider environment as well as enterprise platforms. Network Orchestrator supports virtual devices and provides a centralized way of management of the entire network Infrastructure. It also makes sure that the configuration has been pushed properly and there is no synchronization issue at frequent Internals. Cisco NSO Characteristics Support for multivendor environment. Centralized management of network services. Support for multiprotocol environment. Structured presentation of networking configurations and its state. Support for legacy devices as well which support telnet or ssh. Junos style CLI for configuration of network devices. Support for the abstraction of the configuration to reuse the same model to replicate to other devices. Support for the verification of the state of the existing components before deploying new services and components. Support for the rollback of the configurations. ETSI Management and Orchestration (MANO) Architecture: Cisco Architectural layers: The NFV Orchestrator (NFVO) layer - to orchestrate NFV services using Cisco VNF Manager (VNFM) layer - to manage vNFs using Cisco E