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.
This chapter contains the following sections.
A Cisco Cloud Services Router (CSR) 1000V virtual router with multiple networks on which workloads are placed and a single uplink with a Layer 3 connection to the datacenter network.
A Cisco Virtual Security Gateway (VSG) zone-based firewall to control and monitor segmentation policies within the networks.
A server load balancer (SLB) to scale up the application capacity.
A Cisco prime Network Services Controller (PNSC) that defines and monitors the zone policies. A PNSC can span across multiple containers and the security policy configuration is done by PNSC.
Each container is provided switching by one Cisco Nexus 1000V switch. The Cisco Nexus 1000V switch instantiates the networks as port profiles. A single Cisco Nexus 1000V switch can provide switching for multiple containers.
Three Tier Internal Container template
For more information about this template, see About Cisco VACS 3 Tier Internal and External Container Templates.
Three Tier External Container template
For more information about this template, see About Cisco VACS 3 Tier Internal and External Container Templates.
Custom Container template
For more information about this template, see About Cisco VACS Custom Container Template.
Cisco VACS requires installation of at least one Cisco Nexus 1000V switch and Cisco PNSC to be used in conjunction with containers. Currently, it does not automate the incorporation of Cisco Nexus 1000V switches and Cisco PNSC appliances that have been installed outside of Cisco VACS.
You can add or edit a container template, and then instantiate containers from the template.
Cisco VACS supports VMware ESX 5.0, 5.1, and 5.5 and VMware vCenter 5.1 and later versions. We recommend that you use vCenter version 5.5 because it is compatible with all versions of VMware ESXi.
The number of virtual machines that you can add to a container template is limited only by the hardware of your setup.
SLB for the 3 tier internal/external templates must be placed in the webzone, while for the custom templates it must be based on the zone that you select.
The Cisco VACS template has the following prerequisites:
Set up a VMware vCenter account on Cisco UCS Director.
Define the Computing Policy. Computing policies determine the computing resources used during provisioning that satisfy group or workload requirements.
Define the Network Pools and Policies. A network pool policy includes the VLAN pool policy, the VXLAN pool policy, Static IP pool policy, and the IP Subnet pool policy.
Define the Storage Policy. A storage policy defines resources, such as the datastore scope, type of storage to use, minimum conditions for capacity, and latency. The storage policy also provides options to configure additional disk policies for multiple disks and to provide datastore choices for use during a service request creation.
Define the Systems Policy. A system policy defines the system-specific information, such as the template to use, time zone, and operating system-specific information.
After you create the template, the following policies are automatically created:
PNSC Firewall Policy—The path to this policy is
.Tiered Application Gateway Policy—The path to this policy is
.Virtual Infrastructure Policy—The path to this policy is
.We recommend that you do not edit the PNSC Firewall, Tiered Application Gateway Policies, and the Virtual Infrastructure Policies.
Computing policies determine the computing resources used during provisioning that satisfy group or workload requirements. You can define advanced policies by mixing and matching various conditions in the computing policy.
![]() Note | Cisco VACS does not use the default network policy or user-created network policy. It, instead, uses the network VLAN/VXLAN pools and IP pool policies for the Cisco VACS application containers. |
Cisco VACS minimizes the interdependency between server and network administrators for information about IP addresses, subnets, networks, firewall contexts, and policies for a network, and the appropriate device configurations and available resources. To support the Cisco UCS Director self-service portal and to automate large-scale deployments, Cisco VACS uses resource pools. You can create these pools ahead of time and use them when required. The resource pools defined in advance enables easier provisioning of containers.
VLAN/VXLAN pools—These pools contain a set of VLAN IDs or Virtual Extensible Local Area Network (VXLAN) segment IDs for instantiating networks. The pool attributes are a set of numerical values from 1 to 3967, 4048 to 4093 or a valid VXLAN range from 4096 to 16000000.
For information about how to add a VLAN/VXLAN pool, see Adding a VLAN or VXLAN Pool Policy.
IP Subnet pools—These pools are used for container workload virtual machines. The pool is specified as a supernet together with the specification of the number of subnets that can be created from it. The attributes of these pools are an IP address prefix and a mask length.
For information about how to add a IP subnet pool, see Adding an IP Subnet Pool Policy.
Static IP pools—These pools are used for management, uplink, and VM networks. Management IP pools contain management IP addresses to automate the instantiation of virtual services, such as Cisco Cloud Services Router (CSR) 1000V, Cisco VSG, and Server Load Balancer (SLB) in a network. The attributes for these pools are derived from the physical router configuration and can be used in the custom containers for the VM networks with a port group option.
For information about adding management IP pools, see Defining Static IP Pool Policies.
Uplink address pools contain IP addresses that are used to automate and configure the uplink interface of the default gateway for a container. The attributes for these pools are the same as that of the management IP pools.
For information about adding uplink address pools, see Defining Static IP Pool Policies.
You can add a VLAN or VXLAN pool policy when you add an entry to the list of VM networks.
Step 1 | From the Cisco UCS Director menu bar, choose The Network sub menu appears. . | ||||||||||||
Step 2 | Select the
VLAN
Pool Policy tab.
| ||||||||||||
Step 3 | Click Add. The Add Policy screen appears. | ||||||||||||
Step 4 | In the
Add
Policy screen, complete the following fields:
| ||||||||||||
Step 5 | Click Submit to add the policy to the list or click Close to exit. |
Step 1 | From the Cisco UCS Director menu bar, choose The Network sub menu appears. . | ||||||||||||||||||||
Step 2 | Select the Static IP Pool Policy tab. | ||||||||||||||||||||
Step 3 | Click Add. The Static IP Pool Policy Information screen appears. | ||||||||||||||||||||
Step 4 | In the
Static IP
Pool Policy Information screen, complete the following fields.
| ||||||||||||||||||||
Step 5 | Click
Submit. You can click
Close to close the wizard
You can click Back to review the information entered up to this point or click Close the wizard. |
Step 1 | From the Cisco UCS Director menu bar, choose The Network sub menu appears. . | ||||||||||||||||||||||||
Step 2 | Select the IP Subnet Pool Policy tab. | ||||||||||||||||||||||||
Step 3 | Click Add. The IP Subnet Pool Policy screen appears. | ||||||||||||||||||||||||
Step 4 | In the
IP Subnet
Pool Policy Information screen, complete the following fields.
| ||||||||||||||||||||||||
Step 5 | Click Submit to add the policy to the list or click Close to exit the dialog box. |
The overlapping IP is a new feature in the IP Subnet Pool Policy, where the same subnet will be allocated to more than one container depending on Context Type Container or Tenant.
The IP Subnet Pool Poilcy can either be of type overlapped or non-overlapped. By default, the overlapped option is set to No, then it works as per the existing behavior.
Tenant—If the subnet is in use by some tenant, the same subnet can be allocated for another tenant.
Container—If the subnet is in use by some container, the same subnet can be allocated for another container.
UCSD—This works as per existing behavior, where different subnets will be allocated to different containers (this is equivalent to the overlapped option set to No).
If the routing type is Public and Overlap is set to Yes and the Context Type is either tenant or container, then the containers that have the same public IPs could lead to potential problem with the IP duplication.
To view the IP Subnet Pool Policy, navigate to
. Two new columns, Overlapped and Context Type are available.The Overlapped column indicates whether the overlapped option is being set to Yes or No.
The Context Type column indicates the level the subnet is being overlapped. It could be either UCSD, Container, or Tenant, where the UCSD is the default value.
Step 1 | From the Cisco UCS Director menu bar, choose The Storage sub menu appears. . | ||||||||||||||||||||||||||||||||
Step 2 | Select the VMware Storage Policy tab. | ||||||||||||||||||||||||||||||||
Step 3 | Click Add. The Add Storage Resource Allocation Policy screen appears. | ||||||||||||||||||||||||||||||||
Step 4 | In the
Add
Storage Resource Allocation Policy screen, complete the following
fields:
| ||||||||||||||||||||||||||||||||
Step 5 | Click Next. | ||||||||||||||||||||||||||||||||
Step 6 | In the Storage Policy - Additional Disk Policies screen, choose a disk type to configure. | ||||||||||||||||||||||||||||||||
Step 7 | Click
Edit (pencil icon) to edit the disk type.
The Edit option is not supported in this release. | ||||||||||||||||||||||||||||||||
Step 8 | Click
Submit.
|
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Choose the VMware System Policy tab. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | In the
System
Policy Information dialog box, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Choose from the
following optional
VM Name
Template features:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Choose the Host Name Template variable names. For example: ${VMNAME} | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | Complete the
following fields:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 8 | Click Submit. |
The End User Self-Service Policy controls the actions or tasks that a user can perform on the VMs deployed in a Cisco VACS application container. The starting point for creating this policy is to specify an Account Type, for example VMware. After you specify an account type, you can continue with creating the policy. After you create the policy, you must assign the policy to an application container template that is created with the same account type. For example, if you have created an end user policy for VMware, then you can specify this policy when you create the Cisco VACS application container template. You cannot view or assign policies that have been created for other account types.
In addition to creating an end user self-service policy, Cisco VACS allows you to perform the following tasks:
View—Displays a summary of the policy.
Edit—Opens the End User Policy dialog box from which you can modify the description or the end user self service options.
Clone—Opens the End User Policy dialog box through which you can create another policy with options specified in another policy.
Delete—Deletes the policy from the system. However, no vDC must be assigned with this policy.
Assigning a policy to a Cisco VACS application container template is the only method through which you can control the tasks that a user can perform on the VMs deployed in a Cisco VACS application container.
Step 1 | On the menu bar, choose . | ||||||||||||
Step 2 | Choose the End User Self-Service Policy tab. | ||||||||||||
Step 3 | Click Add (+). | ||||||||||||
Step 4 | In the Add End User Policy dialog box, select an account type (VMware) from the drop-down list. | ||||||||||||
Step 5 | Click Submit. | ||||||||||||
Step 6 | In the
End User
Policy screen, complete the following fields:
| ||||||||||||
Step 7 | Click Submit. |
Step 1 | On the menu bar, choose . | ||||||
Step 2 | Click the ISO Datastores tab. | ||||||
Step 3 | Click Mark Datastores for ISO. | ||||||
Step 4 | In the
Mark Datastores for ISO screen, complete the
following fields:
| ||||||
Step 5 | Click Submit. |
Step 1 | On the menu bar, choose . | ||||||||||||
Step 2 | Click the Guest OS ISO Image Mapping Policy tab. | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | In the
Guest OS ISO Image Mapping screen, complete the
following fields:
| ||||||||||||
Step 5 | Click Submit. |
Cisco VACS enables you to create application container templates in the required zones based on the application design. The Web, Application, and Database zones are available in the 3 tier internal and 3 tier external templates. Depending on your requirements and security settings, you can choose to create container templates. You can choose to create custom security zones in the custom container templates.
Zones isolate virtual machine workloads that are based on security policies or rules. Cisco VACS enables predefined security policies/rules for 3 tier internal template and 3 tier external template for the web, Application and Database tiers. However, you can modify these policies for each container after the container has been deployed successfully. For more information on modifying these policies, see the Managing Firewall Policies section.
You can also add/modify the access control lists (ACLs) rules for each template that you define. The modified ACL rules will be effective only for all newly created application containers.
The custom container template does not pre-define zones or networks and therefore security policies and ACLs must be defined by the administrator based on the zones that are defined during the creation of the container template.
In Cisco VACS, the notion of zones is also used to define application tiers, such as web tier, app tier, and so on. Tiers are relevant to the load balancing function, where members of a tier express an aspect of application architecture and form a server farm.
The Cisco VACS 3 tier internal and external container template offers a preset collection of virtual resources that you can deploy in your datacenter. The internal template defines and enforces the overall policy in the web, application, and database tiers on a shared VLAN or VXLAN and achieves minimum required segregation and enables you to choose a private or public address on the gateway. This template enables you to have external connectivity only to the web tier and restricts the application and database tiers from exposing their services or from consuming the services exposed by other applications inside a firewall.
The 3 tier internal and external container template uses Enhanced Interior Gateway Routing Protocol (EIGRP) as the default routing protocol if you choose the Public Router IP type. However, you have an option to choose either the EIGRP protocol or set up Static Routing Protocol, and set up other static routes to forward upstream traffic to the container's internal network.
These template types allows you to expose the services of the container to external applications and consume the services exposed by other applications behind the firewall. As with the internal template type, the specific security profile requirements for the tiers are enabled by the zone and security policies.
Select the application container type from the Add Template wizard under the VACS Container tab in Cisco UCS Director to create a new 3 tier internal or external container template.
To create the Cisco VACS 3 tier internal or external container template, perform the following tasks:
Use the following workflow and the procedures in this chapter as a guide to create either the internal or the external templates.
![]() Note |
|
Step 1 | From the Cisco UCS Director menu bar, choose . The Cisco VACS management task icons appear. | ||||||||
Step 2 | Click
Add
Template.
The
Add
VACS wizard appears.
![]() | ||||||||
Step 3 | In the
VACS
Template Specification screen, complete the following fields:
|
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the
VACS
Deployment Options screen, complete the following details:
| ||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click Next. |
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the
VACS
Network Resource Pool
screen, complete the following fields:
| ||||||||||||||||||
Step 2 | Click Next. |
Virtual machine networks provide all of the information about the configured virtual machines for the Cisco VACS templates.
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the VACS – VM Networks screen, select a virtual machine network from the list displayed. If no networks are displayed, click + to add an entry to the VM Networks table. | ||||||||||||||||||||||
Step 2 | In the
Add
Entry to VM Networks screen, complete the following fields:
| ||||||||||||||||||||||
Step 3 | Click Next. You can click Back to review the information that you have provided until this point, or click Close to exit the wizard. |
Enabling the server load balancing (SLB) option is an optional task. Based on your requirements, you can enable this option. By default, the SLB option is disabled.
![]() Note |
|
Step 1 | In the
Server
Load Balancing
screen, complete the following fields:
| ||||||||||||||||||||||||||||||
Step 2 | Click Next. You can click Back to review the information that you have provided until this point, or click Close to exit the wizard. |
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the VACS – Virtual Machines screen , click the + icon to add a virtual machine. | ||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the
Add Entry
to Virtual Machines screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||
Step 3 | Repeat for each zone and then click Next. |
Editing the Firewall ACL Rules for the Templates
Cisco Virtual Application Cloud Segmentation (VACS) Services (Cisco VACS) defines default access control lists (ACLs) for the 3 tier templates. You can view and edit these ACLs.
![]() Note | Use this procedure to edit the firewall access control lists (ACLs) rules for the templates. To modify existing firewall ACL rules for deployed containers, you must use the Firewall Policy menu option available at . For more information, see Editing Firewall ACL Rules. |
Step 1 | On the menu bar, choose . | ||
Step 2 | In the navigation pane, choose an account. | ||
Step 3 | Choose the PNSC Firewall Policies tab. The Cisco UCS Director displays a table of the PNSC firewall policies. These policies include the ACLs. | ||
Step 4 | Select the
accurate firewall policy to view or edit that policy's ACLs.
| ||
Step 5 | Click Edit. | ||
Step 6 | In the PNSC Firewall Specification screen, click Next to leave the information as is. | ||
Step 7 | In the PNSC-Zones Configuration screen, click Next to leave the information as is. | ||
Step 8 | In the PNSC-ACL Rules screen, you can add a new ACL, or edit, delete, or move the existing ACLs. | ||
Step 9 | After you are done adding, editing, deleting and moving the ACLS, click Next. | ||
Step 10 | In the
PNSC-VSG
Configuration screen, retain the default values, and then click
Submit.
You can click Back to review the information entered up to this point or click Close to close the wizard and undo any changes. |
The Cisco VACS Custom Container (or Advanced Container) template enables you to design a container that meets your specific requirements without any restrictions on the number of tiers, zones, networks, or network elements such as, CSR, and/or VSG, and/or SLB or a combination of these network elements and application types. The custom container type allows you to build a template that allows a n-tier application with each tier on a shared or dedicated VLAN or VXLAN segments.
Select the application container type from the Add Template wizard under the VACS Container tab in Cisco UCS Director to create a new custom container template.
To create the Cisco VACS custom container template, perform the following tasks:
Use the following workflow and the procedures in this chapter as a guide to create custom templates.
![]() Note |
|
Step 1 | From the Cisco UCS Director menu bar, choose . The Cisco VACS management task icons appear. | ||||||||
Step 2 | Click
Add
Template.
The
Add
VACS wizard appears.
![]() | ||||||||
Step 3 | In the
VACS
Template Specification screen, complete the following fields:
|
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the
VACS
Deployment Options screen, complete the following details:
| ||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click Next. |
![]() Note |
|
Step 1 | In the
VACS
Network Resource Pool
screen, complete the following fields:
| ||||||||||||||||||||
Step 2 | Click Next. |
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the VACS Security Zones Configuration screen, click + to add security zones to the list. | ||||||||||
Step 2 | In the
Add Entry
to Security Zones screen, complete the following fields:
| ||||||||||
Step 3 | Click Next. |
![]() Note |
|
Step 1 | In the VACS Access Control List Configuration screen, click + to add the ACL rules. | ||||||||||||||||||||
Step 2 | In the
Add Entry
to Access Control List Rules screen, complete the following fields:
| ||||||||||||||||||||
Step 3 | Click Next. |
![]() Note |
|
The Application Layer Gateway performs inspection on the incoming packets for the selected Application layer Protocols.
![]() Note | By default, the first five protocols (HTTP, HTTPS, FTP, DNS, and ICMP) are enabled. |
Virtual machine networks provide all of the information about the configured virtual machines for the Cisco VACS templates.
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the VACS – VM Networks screen, select a virtual machine network from the list displayed. If no networks are displayed, click + to add an entry to the VM Networks table. | ||||||||||||||||||||||||||||||
Step 2 | In the
Add Entry
to VM Networks screen, complete the following steps:
| ||||||||||||||||||||||||||||||
Step 3 | Click Next. You can click Back to review the information that you have provided until this point, or click Close to exit the wizard. |
Enabling the server load balancing (SLB) option is an optional task. Based on your requirements, you can enable this option. By default, the SLB option is not enabled.
![]() Note |
|
Step 1 | In the
Server
Load Balancing screen, complete the following fields:
| ||||||||||||||||||||||||||||||
Step 2 | Click Next. You can click Back to review the information that you have provided until this point, or click Close to exit the wizard. |
![]() Note | The Help link provides you access to the corresponding online help. |
Step 1 | In the VACS – Virtual Machines screen , click the + icon to add a virtual machine. | ||||||||||||||||||||||||||||||||||||||||||||
Step 2 | In the
Add Entry
to Virtual Machines screen, complete the following fields:
| ||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Repeat for each zone and then click Next. |
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||||
Step 2 | Choose the Catalog tab. | ||||||||||||||||||||||||||||||
Step 3 | Click Add (+) | ||||||||||||||||||||||||||||||
Step 4 | In the Catalog Add dialog box, select the type of catalog that you want to add. | ||||||||||||||||||||||||||||||
Step 5 | Click Submit. | ||||||||||||||||||||||||||||||
Step 6 | In the
Add Catalog dialog box, complete the following
fields:
| ||||||||||||||||||||||||||||||
Step 7 | Click Next. | ||||||||||||||||||||||||||||||
Step 8 | Review the catalog information in the Summary page. | ||||||||||||||||||||||||||||||
Step 9 | Click Submit. |
![]() Note | You can resubmit a failed container rollback. |
Step 1 | In the Cisco UCS Director menu bar, choose . | ||||||||||
Step 2 | Right-click the appropriate template and Select Create Container. The Create Container from Template screen appears. | ||||||||||
Step 3 | In the
Create
Container from Template
screen, complete the following fields:
| ||||||||||
Step 4 | Click Submit. |
![]() Note | The edit and delete operations should be performed only when the Cisco VACS application containers are not using these templates. |
Do not edit or clone templates from 1 type to another. It is not recommended to change (add or remove) the optional services while editing an existing template
You can generate summary reports, a detailed report with credentials, and a detailed report without credentials for each container.
Step 1 | On the menu bar, choose . | ||
Step 2 | Click the Application Container tab. | ||
Step 3 | Choose a container or right-click on the container to bring up all of the actions. | ||
Step 4 | Click View Reports. | ||
Step 5 | From the Select
Report Type drop down list, choose the report you want to view.
Reports "with Credentials" show passwords in plain text. Reports "without Credentials" hide passwords in the report. Reports for Administrators contain policy information not given in reports for Self-Service Users. A dialog appears with a report detailing the application container.
|
To view the login passwords and vnc details for the VMs, see the detailed report with credentials.
The login user for CSR/VSG is admin and for SLB is root.
The default enable password for CSR is cisco123.
The Summary Report and the Detailed Report in the Secure Container details are displayed based on the permissions granted by the administrator.
The contents of the Detailed report depends on whether it is a secure report or an unsecure report.
![]() Note | In addition to these reports, Cisco VACS maintains the VACS Resource History Report, which is an audit report that is utilized to debug issues related to resource allocation. For more information, see About the Cisco VACS Resource History Report. |
Summary Report (for Self-Service Users)—displays the details of the workload VMs
Container:Name—displays the container name, container type, the group it belongs to, and the date the template was created.
Virtual Machines—displays the details of the workload VMs.
Event history—displays the deployment history.
Virtual Machine Subnet Information—displays the network and gateway IP addresses and the subnet mask.
CSR Uplink Information—information about the CSR 1000V uplink.
Static Nat Details—displays Static Nat related information.
![]() Note | If the network administrator has granted permissions to view the secure container details, the Stats URL displays the VIP IP address instead of the SLB Management IP Address. |
Detailed Report without Credentials (for Administrators)
Detailed Report with Credentials (for Administrators)
Summary Report (for Self-Service Users)—displays container details such the summary of all the VMs, including the details of the service VMs that are associated with the selected application container.
Detailed Report with credentials (for Self-Service User)
Detailed Report without credentials (for Self-Service User)
Detailed Report without Credentials (for Administrators)
Detailed Report with Credentials (for Administrators)
Container:Name—displays the container name, container type, the group it belongs to, and the date the template was created.
Virtual Machines—displays consolidated information about all the provisioned VMs and their status in the container, resource consumption details such as disk size, memory, and CPU, details of the network interface, hostname and status, and port mappings for the container.
Container Port Groups—displays details about the container port groups with specific admin credentials.
Event history—displays the deployment history.
Server Load Balancing—displays the server load balancing (SLB) primary and secondary virtual machine names, IP addresses, netmask, network gateway, data and management port-groups, Stats URL, Stats username and password, information about the VIP, zone, and real server.
Virtual Machine Subnet Information—displays the network and gateway IP addresses and the subnet mask.
CSR 1000V License Details—displays details about the CSR 1000V virtual appliances deployed by Cisco VACS and the corresponding license states.
CSR Uplink Information—information about the CSR 1000V uplink.
Static Nat Details—displays Static Nat related information.
ERSPAN Details—displays ERSPAN related information.
Upstream Router Configuration Required—This section is displayed when the edge gateway is disabled in a container.
![]() Note | The detailed report with credentials (for Self-Service Users and Administrators) also displays the service VM passwords that were reset or reconfigured using the manager service VM password feature. |
Cisco VACS maintains the resource history report, which is an audit report that displays details associated with the resource allocation and deallocation during the application container deployment, rollback, and all resource allocation related operations. This is used as a troubleshooting mechanism to identify the resource leakages, if any.
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||||||
Step 2 | In the
VACS
Resource History
screen that appears, the following details are displayed:
You are allowed to customize the details that can be displayed in this report using the Customize Table Columns button. You can also filter the display using the Add Advance Filter button. You can also export this report to a local machine using the Export Report button. |
You can choose to delete selected records from the available data or delete all existing records from the database.
Step 1 | On the menu bar, choose The . VACS Resource History screen appears |
Step 2 | Select the row(s) that you want to delete and click the Delete button. In the Delete confirmation box that appears, click Delete to delete the selected record(s). |
Step 3 | Click the Reset button to delete all existing data from the database. |
After the Cisco VACS application container is deployed, you can view all consolidated information about the CSR 1000V licensing using the administrator privileges. The Self-Service users can view the CSR status about a CSR in a container in the view report page.
![]() Note | If the Edge gateway is not enabled in the template, then the corresponding container will not have any CSRs. In this case, this section is not applicable for such containers. |
Step 1 | On the menu bar,
choose
.
The VACS:CSR Licenses screen appears. |
Step 2 | The
VACS:CSR
Licenses screen that appears displays the list of CSRs that are
deployed using Cisco VACS.
All the unlicensed CSR 1000V try to fetch the latest status of the CSR 1000V information every 10 minutes. The available information is as follows: |
Step 3 | Click the
VACS:
CSR License Balance tab.
The
VACS: CSR
LIcense Balance screen appears.
This is a CSR license report that displays the count number for the Cisco VACS licenses and the CSR delegated license balance. |