VNMC is a virtual appliance, based on Red Hat Enterprise Linux, that provides centralized device and security policy management of Cisco virtual services. Designed for multiple-tenant operation, VNMC provides seamless, scalable, and automation-centric management for virtualized data center and cloud environments. With both a built-in UI and an XML API, VNMC enables centralized management of Cisco virtual services by an administrator or through an API.
VNMC is built on an information model-driven architecture in which each managed device is represented by its subcomponents (or
), which are parametrically defined. This model-centric approach enables VNMC to provide a secure, multiple-tenant virtualized infrastructure with Cisco Adaptive Security Appliance 1000V (ASA 1000V) and Cisco Virtual Security Gateway (VSG) virtual services.
All ASA 1000Vs and VSGs are centrally managed, thereby simplifying provisioning and troubleshooting in a scaled-out data center. By using device profiles with their specified device configuration policies, you can deploy consistent policies to one or more profile-managed resources.
Security profiles enable you to represent a security policy configuration in a profile that:
Reduces administrative errors during security policy changes
Reduces audit complexities
Enables a highly scaled-out data center environment
Stateless Device Provisioning
The management agents in VSG and ASA 1000V are stateless, receiving information from VNMC and thereby enhancing scalability.
Security Policy Management
Security policies are authored, edited, and provisioned for all VSGs and ASA 1000Vs in a data center, which simplifies the operation and management of security policies, and ensures that the required security is accurately represented in the associated security policies.
Context-Aware Security Policies
VNMC interacts with VMware vCenter to create virtual machine (VM) contexts that enable you to institute highly specific policy controls across the entire virtual infrastructure.
Dynamic Security Policy and Zone Provisioning
VNMC interacts with the Cisco Nexus 1000V VSM to bind the security profile with the corresponding Cisco Nexus 1000V Series switch port profile. When VMs are dynamically instantiated and applied to appropriate port profiles, their association to trust zones is also established.
VNMC can manage compute and edge firewall security policies in a dense multi-tenant environment, so that you can rapidly add or delete tenants, and update tenant-specific configurations and security policies. This feature significantly reduces administrative errors, ensures segregation of duties within the administrative team, and simplifies audit procedures.
Role-Based Access Control
Role-Based Access Control (RBAC) simplifies operational tasks across different types of administrators, while allowing subject-matter experts to continue with their normal procedures. With RBAC, organizations can reduce administrative errors and simultaneously simplify auditing requirements. VNMC supports local and remote authentication with RBAC.
The VNMC XML application programming interface (API) allows external system management and orchestration tools to programmatically provision VSGs and ASA 1000Vs, and provides transparent and scalable operation management.
For Internet Explorer and Mozilla Firefox, the supported Adobe Flash Player plugin version is 11.2.
For Chrome, the supported Adobe Flash Player plugin version is 11.3.300.265.
1.We recommend Mozilla Firefox 20.0 with Adobe Flash Player 11.2.
2.Before you can use Chrome with VNMC 2.1, you must first disable the Adobe Flash Players that are installed by default with Chrome. For more information, see Configuring Chrome for Use with VNMC.
VNMC is a multi-hypervisor virtual appliance that could be deployed on either VMware vSphere or Microsoft Hyper-V Server 2012 (Hyper-V Hypervisor). See the VMware Compatibility Guide
to verify thatVMware supports your hardware platform. See the Windows Server Catalog
to verify that Microsoft Hyper-V supports your hardware platform.
Release 4.1, 5.0, or 5.1 with VMware ESXi (English Only)
Release 4.1 or 5.0 (English Only)
Microsoft Windows Server 2012 with Hyper-V (Standard or Data Center)
Microsoft SCVMM 2012 SP1 or later
Configuring Chrome for Use with VNMC
To use Chrome with VNMC 2.1, you must disable the default Adobe flash players that are installed by default with Chrome.
Note You must perform this procedure each time your client machine reboots. Chrome automatically enables the Adobe flash players when the system on which it is running reboots.
To disable default Adobe flash players in Chrome:
Step 1 In the Chrome URL field, enter
Step 2 Click
Step 3 Locate the Flash player plugins, and disable each one.
Step 4 Download and install Adobe Flash player version 11.3.300.265.
Step 5 Close and reopen Chrome before logging into VNMC 2.1.
Performance and Scalability
Table 4 lists the performance and scalability data for VNMC 2.1.
Table 4 VNMC 2.1 Performance and Scalability
ASA 1000Vs and VSGs
NTP Requirements for Deploying and Operating VNMC
You must do the following for proper VNMC operation with VMware, ASA 1000V, VSG, and VSM:
2. Before you perform any operation on VNMC after you deploy the OVA, configure NTP servers for VNMC, ASA 1000V, VSG, and VSM. If you do not do so, ASA 1000Vs, VSGs, and VSMs will not be able to register with VNMC. See Configuring NTP.
Before you perform any operation in VNMC, configure NTP on ASA 1000V, VSG, and VSM. If you do not do so, ASA 1000Vs, VSGs, and VSMs will not be able to register with VNMC.
To configure NTP in VNMC, ASA 1000V, VSG, and VSM:
VNMC can be installed on the VMWare Provisory and the Microsoft Hyper-V Hypervisor. The following are some of the VNMC features that are not supported when VNMC is installed on Hyper-V Hypervisor.
When you are adding a rule to create the ACL policy:
The option to match any one rule is disabled. The only available option is to match all the rules.
The service condition is disabled.
When you are setting source or destination conditions, the VM attribute type is not supported.
When you are adding an object group:
When the attribute type is Network, the attribute name Service is not supported.
The VM attribute type is not supported.
When you are working with vZones, the option to match any one rule is disabled. The vZone must match all the conditions.
You can create a clone for an organization, policy, or policy set at a VNMC destination of your choice. The hierarchy of an organization's clone and the names of the elements in it cannot be changed. Once created, a clone cannot be renamed or moved to another location.
You can search for instances of organizations in VNMC using the search tab in the policy management, tenant management, and resource management tabs.
When you enter an organization name as a pattern or a regular expression in the search text box, the search result is displayed. From the search result, you can expand the organization's hierarchy and launch devices and polices in that organization.
Condition Match Criterion in vZone
You can now choose a condition match criterion when you add a vZone. This option enables you to choose all conditions or any one condition to be applied on the vZone.
Service Attribute in Object Group
You can group different types of objects within the same field; for example, you can group port and protocols. The service attribute in the ACL rule enables you to configure protocol and destination port in a single condition.
The following topics describe the limitations in VNMC 2.1:
VNMC VM Manager and VMware vCenter Server Connections
VNMC VM Manager automatically connects to the VMware vCenter server on HTTP port 80. A vCenter extension file is required to establish a connection between VM Manager and vCenter. The extension file is exported from VNMC and linked on the VM Managers tab. You install it as a plugin on all vCenter servers to which you want to connect.
If you upgrade vCenter to a new version and use the same IP address, vCenter attributes are not updated in VNMC. For example, the vCenter attributes for VMs and hosts on the upgraded vCenter are not updated.
To resolve this issue, add the vCenter to VNMC again by choosing
Resource Management > Resources > Virtual Machines > VM Managers
Add VM Manager
Characters in Names Retrieved from vCenter
If you choose
Resource Management > Resources > Virtual Machines
, the following characters are not allowed in names that are retrieved from vCenter:
" ' ^ & ` < > ? = \ "
If a name that is retrieved from vCenter contains any of these characters, VNMC does not recognize the characters.
Names that can be affected include:
VM DNS name
VM parent application name
VM resource pool name
Hypervisor cluster name
As a result of this behavior, VNMC attribute names do not display correctly in the UI and might be evaluated differently when these attributes are used in policy conditions.
Value Displayed in Parent App or Resource Pool Field
The VM Properties pane displays Parent App and Resource Pool fields, but only one field contains a value at any time. For example, if the parent application name is displayed, the resource pool name is not displayed. This situation occurs because a VM can be part of a parent application or part of a resource pool, but not both simultaneously.
You can view the VM Properties pane by choosing
Resource Management > Resources > Virtual Machines > VM Managers >
is a vCenter.
is the ESXi host IP address in dotted-decimal format (
is a specific VM.
Searching for Organization Names
If an organization name contains special characters, it will not be searchable.
The open bugs for VNMC are available in the Cisco Bug Toolkit
. The Cisco Bug Toolkit enables you to search for a bug by identifier or product and version, and can provide additional details about the bug, such as more information or that the bug has been fixed.
Table 5 identifies the bugs that are open in the VNMC 2.1 release.
When more than 512 Policy Object groups are added for a tenant in VNMC 2.1, the API does not respond with an error. However, the GUI displays an error message stating that the maximum capacity is exceeded. This results in the creation of incorrect policy objects.
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks
. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.