Cisco Cisco Network Services Manager 5.0 Referencia técnica
Page 5
OL-28510-02
Reference Guide
. These include some predefined POD (or device stack) examples. These are the
supported variations in physical architecture for Network Services Manager 5.0.2 but could be
modified by Cisco Advanced Services to accommodate for other common variations. Any
modifications to these default POD examples should be thoroughly tested in a sandbox
environment before being deployed in a live system. See below for these variations (Topology
Variations).
The Admin user will use a web client for common administrative functions. This web client can
The Admin user will use a web client for common administrative functions. This web client can
also be used to instantiate metamodels.
Prerequisites
To deploy a Cisco Network Services Manager environment you need to have a system
administrator level knowledge of: networking, VMware, server, and PC technologies.
A basic deployment consists of two Linux servers, which can each be deployed as an OVA.
These servers are usually deployed on a separate vCenter cluster (or single ESXi server) reserved
A basic deployment consists of two Linux servers, which can each be deployed as an OVA.
These servers are usually deployed on a separate vCenter cluster (or single ESXi server) reserved
for management of the equipment. For standard deployments where a single stack of equipment
is expected, the guest VM requirements are:
•
Engine 2 GB of RAM, 40 GB HDD and dual CPU. The base requirements for the Engine
may change when managing multiple sites or multiple stacks of equipment.
•
Controller 1 GB of RAM, 40 GB HDD and a dual CPU. These requirements will not change
in the foreseeable future.
The devices are those required for a Cisco Virtualized Multi-Services Data Center (VMDC) 2.1
Compact POD, with a Cisco ASR 1000 (ASR 1000) pair above the Cisco Nexus 7000 (Nexus
7000) devices for connectivity to the Internet or a corporate network.
Management interfaces and data path configuration are the most common sources of delays in a
Management interfaces and data path configuration are the most common sources of delays in a
deployment. The management interfaces and associated VLAN must be configured and tested
for device access before starting the deployment. The data path for tenant data needs to be
deployed and verified as part of the static configuration of the equipment stack (for example,
VPC, trunks, port channels, etc.).
The deployment requires CLI and SNMP credentials for all of the equipment that will be
The deployment requires CLI and SNMP credentials for all of the equipment that will be
managed. If the deployment matches one of the physical topology sample models, you can enter
the credentials and interconnect information either via the WebUI or by preparing a REST
request body for the POD as the physical topology is described and using that to create a new
POD in Network Services Manager.