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 describes the graphical user interface for Cisco Application Services Engine.
This chapter contains the following sections:
Once the Cisco Application Services Engine is bootstrapped, the remaining actions can be performed using the Cisco Application Services Engine GUI.
To access Cisco Application Services Engine GUI, use management network IP of any master node : https://<node-mgmt-ip>
The Dashboard provides a wholistic view of the Cisco Application Services Engine. An administrator can use this view to monitor system health, sites and apps connectivity status and resource utilization.
The Dashboard has the following information:
Overview tile displays system status, cluster status and Cisco Intersight status.
The Sites, Apps, and Infra Services tile displays the sites by connectivity, apps by status and infra services by status.
The Inventory tile provides details of the node type, nodes, containers, pods, deployments, stateful sets, daemon sets, and services.
The Service Node Storage tile provides details about the registered service nodes.
The Utilization tile provides details about the CPU usage.
The Memory tile provides details about the memory usage.
The Apps component in the left navigation pane displays the apps that are hosted on the Cisco Application Services Engine.
When clicked upon, the app work pane shows the app details including Description, Version, Pods, and the Containers running on the selected app.
The Containers tab displays all the configured containers, container status, IP address, and the configured service nodes .
The Pods tab displays the configured pods running on the selected app.
The Version tab displays the the app version number.
The Enable enables the selected app.
The Launch App allows the enabled app to be launched. This opens a new window where the app is launched. Login to the Cisco Application Services Engine user interface to perform any further operations.
The System Resources component in the left navigation pane displays the application resources that are configured on the service node.
The System Resources tab opens a navigation work pane, which displays the Nodes, Pods, Containers, Deployments, Statefulsets, Deamonsets, and the Namespaces running on the node.
The Nodes tab on the navigation work pane displays the details of the service nodes configured and running on the selected app. Upto seven nodes are admitted in a cluster; three master nodes and four worker nodes.
 Note |
Only worker nodes can be registered using the GUI. Master nodes are brought up using the command line as specified in Deploying the Cisco Application Services Engine section. |
The Pods tab on the navigation work pane displays the configured pods running on the selected app.
The Containers tab on the navigation work pane displays all the configured containers, container status, IP address, and the configured service node.
The Deployments tab on the navigation work pane displays all the deployments, status, IP address, and the configured service node.
The Statefulsets tab on the navigation work pane displays all the configured statefulsets, status, IP address, and the configured service node.
The Deamonsets tab on the navigation work pane displays all the configured deamonsets, status, namespaces, IP addresses.
The Services tab from the navigation work pane displays the service name, cluster IP, configured ports and the selectors for the app.
The Namespaces tab from the navigation work pane displays the services, pods, containers, deployments and replicasets of the apps.
The Operations component in the left navigation pane displays the actions that can be performed on Cisco Application Services Engine. Four actions that can be performed under Operations such as :
Firmware Management:
Firmware Management is used to perform cluster (firmware) upgrade or downgrade.
Note |
Refer to Upgrading Existing Release 1.1.3 to Later Releases for more information. |
Tech Support:
An administrator can perform technical support collections.
Audit Logs:
Audit Logs are user triggered configuration changes.
Backup and Restore:
Backup and Restore displays the backed up and restored configuration.
Tech support enables user to collect logs and activities in the system for further troubleshooting by Cisco TAC. Cisco Application Services Engine provides best efforts tech support collection and gives ability to download tech support for individual nodes or consolidated one. Tech support files are hosted on the Cisco Application Services Engine and can be downloaded any time.
Use this procedure to collect Tech Support.
| Step 1 |
For collecting tech support, click Tech Support > Actions and Collect Tech Support. |
| Step 2 |
Enter the description of the issue and click Collect. |
| Step 3 |
For deleting tech support, click Tech Support. Place a check in the tech support log to be deleted. Click Actions > Delete Tech Support. |
| Step 4 |
After tech support is complete, user can download the file for troubleshooting further. |
Use this procedure to view the audit logs.
| Step 1 |
Choose Operations > Audit Logs. |
| Step 2 |
Click Audit Logs. An administrator can monitor configuration modification in the Audit Logs view. Audit logs are unsorted by default. Click on any column to sort them. To check more details about an action, click on the row and you can find out what configuration was changed in the given action. |
Use this procedure to back up and restore cluster configuration details.
| Step 1 |
Click Backup and Restore > Actions. |
||
| Step 2 |
To back up the configuration, click Back up configuration. |
||
| Step 3 |
Enter the Encryption key (this is the key to encrypt the data) and the file name. Click download.The configuration is backed up and the details are displayed on the Backup and Restore page. |
||
| Step 4 |
To restore the configuration, click Actions and Restore configuration. |
||
| Step 5 |
In the Restore configuration window, enter the import type. Choose replace or merge based on the action needed to be performed.
replace will replace existing configuration with backedup configuration. merge will try to merge existing configuration with backed up configuration. |
||
| Step 6 |
Enter the Encryption key (used to back up the configuration), choose the file for import and click import. |
The Infrastructure component is an embedded management controller that enables addition or deletion of sites, cluster configuration and Cisco Intersight to the Cisco Application Services Engine.
Sites:
APIC cluster domain or single fabric, treated as an ACI region and availability zone. It can be located in the same metro-area as other sites, or spaced world-wide.
Cluster Configuration:
Cluster Configuration provides cluster details such as name, app subnet, and service subnet. It also provdes details of the NTP and DNS servers.
Intersight:
The Intersight component is an embedded management controller that enables the capabilities of Cisco Intersight, a cloud-based management platform.
Note |
The Cisco NIA app depends on the Intersight Device Connector for the app to be configured and available on the service node. |
The Administrative component in the left navigation pane displays the users for Cisco Application Services Engine. The Users tab allows the admin to give access to other users.
Use this procedure to give access to other users.
| Step 1 |
Choose Administrative > Users.
|
||
| Step 2 |
Click Actions and then Create local user to create a user. |
||
| Step 3 |
Click Actions and then Delete local user to delete a user. |
||
| Step 4 |
The tile displays the user ID, status, first name, last name, email ID, and privileges of the users. |
Feedback