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.
You can find examples of writing custom reports at http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/ucs-director/cloupia-script-cookbook/5-0/CloupiaScript-Cookbook.pdf
Administrators
Summary Report —This report lists the container details including the name, template type, and the date it was created and provides consolidated information about all the provisioned VMs and their status in the container.
Detailed Report without Credentials—This report lists the VM name and type, the resource consumption details (disk size, memory, and CPU), details of the network interface, hostname and status, and port mappings for the container without specific credentials.
Detailed Report with Credentials—This report lists the VM name and type, resource consumption details (disk size, memory, and CPU), hostname and status, details of the network interface, and port mappings for the container along with the specific credentials.
Detailed Report without Credentials (for Administrators)—This report lists the VM name and type information about resource pools, resource consumption details (disk size, memory, and CPU), details of the network interface, hostname and status, and the container port groups without specific admin credentials.
Detailed Report without Credentials (for Administrators)—This report lists the VM name and type, information about resource pools, resource consumption details (disk size, memory, and CPU), CSR virtual appliances deployed by Cisco VACS and their license states, details of the network interface, hostname and status, and the container port groups with specific admin credentials.
End users
Summary Report —This report lists the container details including the name, template type, and the date it was created and provides consolidated information about all the provisioned VMs and their status in the container.
Detailed Report without Credentials—This report lists the VM name and type, the resource consumption details (disk size, memory, and CPU), details of the network interface, hostname and status, and port mappings for the container without specific credentials.
Detailed Report with Credentials—This report lists the VM name and type, resource consumption details (disk size, memory, and CPU), hostname and status, details of the network interface, and port mappings for the container along with the specific credentials.
The default workflows are listed in Cisco UCS Director under .
You can reference a custom workflow in an advanced catalog from the self-service portal, and create a service request to execute a custom workflow. For examples of writing custom tasks, see http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/ucs-director/cloupia-script-cookbook/5-0/CloupiaScript-Cookbook.pdf.
Cisco VACS does not impose any limit on the number of simultaneous container requests. However, we recommend four container requests.
Ideally, containers can be provisioned in about 30 minutes. Time taken to provision containers depends on the number of VMs and its disk size in a container, Host CPU/memory usage, VC work load, and the storage type of a host.
Yes.
You can see the default firewall policies under
.You can modify the default firewall ACLs. For information on how to modify the default firewall ACLs, see the Viewing and Editing the ACLs for the 3 Tier Templates
No.
In the cluster environment, it is expected that all the hosts present in the cluster must be members of the Cisco Nexus 1000v switch. Hence, this error message.
Yes. You can view the Cisco VACS PAK information by navigating to . You can check for CUIC-SERV-STINGRAY.
Yes. For information on how to view the CSR information for your container, see the Viewing the CSR 1000V Licensing Information.
Yes. For information on how to edit the container based firewall rules, see the Managing Firewall Policies
No, you cannot create a container template that needs a combination if public and private IPs.
You can setup Cisco UCS Director to provide notifications using the scripts available in the Cloupia script cook book guide available at http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/ucs-director/cloupia-script-cookbook/5-0/CloupiaScript-Cookbook.pdf
When a container is successfully deployed, Cisco VACS notifies the requester via an e-mail, provided the requester has configured the e-mail settings.
You can provide access to the workload VMs by enabling Static NAT on a VM.
The VM name is automatically defined by Cisco VACS.
Yes. However, you cannot use the catalog for provisioning additional containers.
No approval mechanism is available to verify that a container request is approved prior to deployment.
This error message indicates that the vCenter is unable to create a VM. Please log on to the vCenter and check details to resolve the error.
This error message indicates that the workflow is unable to create a port-profile on Cisco Nexus 1000V. This condition could be caused by a delay in response from the port-profile service on Cisco Nexus 1000V or the port profile has been created on the Cisco Nexus 1000V which is not available on the vCenter during the creation of a VM.
This error occurs when there are insufficient vCPUs or memory on an allocated host. Modify the compute policy to remove the host.
You must enable ERSPAN on the VM interfaces to monitor the workflow.
Yes, Operational reports are available in Cisco UCS Director to monitor resource consumption.
Yes, you can log in via a SSH session or the VC console. However, it is not recommended to log in or confgure the network service VM (VSG and CSR).
No. Re-submission is not supported and is blocked. Roll back the service request, do an inventory collection, and instantiate a new container.
Check the computing and storage policies associated with the container template. The error message is displayed because, based on the conditions (for example, Active VMs, CPU usage, Memory usage) in the respective computing and storage policies, there are no hosts available that meet the policy criteria mentioned in the compute and storage policies.
Feedback