Uninstall Cisco Crosswork

This chapter contains the following topics:

Uninstall the Crosswork Cluster

This section explains the various methods to uninstall the Cisco Crosswork cluster.

Delete the VM using the Cluster Installer Tool

In case of a failed installation, the cluster installer tool is used to cleanup or delete any previously created VMs based on the cluster-state. This is a critical activity during failed deployments. Any changes made to the VM settings or the data center host requires a cleanup operation before redeployment.


Note

The installer cleanup option will delete the cluster deployment based on the inventory in /data directory.

Procedure

Step 1

Enter the directory storing the deployment info.

For example, _cd ~/cw-cluster.

Step 2

Run the container on the host.

docker run --rm -it -v `pwd`:/data <cw-installer docker container>

Step 3

Edit the copy of the template file (for example, v4.tfvars) in a text editor, adding the data center access parameters. Remaining parameters can be provided with dummy values, or entered on the command line during the execution of the operation.

Step 4

Run the _cw-installer.sh install_ script with the clean directive along with the deployment manifest using the -m flag.

Add -o option to remove the Cisco Crosswork image template from the data center.

For example:

./cw-installer.sh clean -m /data/deployment.tfvars -o

Step 5

Enter "yes" when prompted to confirm the operation.

Step 6

(Optional) To clean the cluster quickly (without verification), users can run the installer using the following command: 

docker run --rm -it -v `pwd`:/data <cw installer docker image> -exec './cw-installer.sh clean -m /data/deployment.tfvars'

Delete the VM using the vSphere UI

This section explains the procedure to delete a VM from vCenter. This procedure is used to delete any Crosswork Network Controller application VM.


Note

  • Be aware that this procedure deletes all your app data.

  • If you want to delete Crosswork Data Gateway only, ensure you have done the following:

    • Detach the devices from the Crosswork Data Gateway VM you want to delete. For more information, see Delete Cisco Crosswork Data Gateway VM from Cisco Crosswork topic in the Cisco Crosswork Network Controller 7.0 Administration Guide.

    • Delete the Crosswork Data Gateway VM from Crosswork Network Controller as described in this chapter.

Procedure

Step 1

Log into the VMware vSphere Web Client.

Step 2

In the Navigator pane, right-click the app VM that you want to remove and choose Power > Power Off.

Step 3

Once the VM is powered off, right-click the VM again and choose Delete from Disk.

The VM is deleted.

Uninstall Crosswork Data Gateway

This section explains the methods to remove Crosswork Data Gateway.

Delete the Data Gateway VM from Cisco Crosswork

Before you begin

The data gateway VM you want to delete:

  • Must be in the maintenance mode.

  • Must not be a part of a pool or attached to a device.

Procedure

Step 1

Log into Crosswork Network Controller UI.

Step 2

From the navigation panel, select Administration > Data Gateway Management.

Click the Data Gateway Instances tab.

Step 3

In the Data Gateway Instances list, find the data gateway instance you want to delete and click More icon under Actions column.

Click Delete.

Step 4

If the data gateway instance is not in the maintenance state, Crosswork Network Controller prompts you to switch it to maintenance state. Click Switch to maintenance and continue.

Figure 1. Switch to Maintenance and Continue Pop-up Window

The data gateway instance is deleted.

Delete Crosswork Data Gateway from the Crosswork Cluster

To remove a data gateway from the Crosswork cluster, follow the below steps:

Procedure

Step 1

Remove the data gateway instance from the Crosswork UI. Note down the Data Gateway Instance Name and PDG Identifier from the Crosswork UI.

Step 2

Execute the following commands to remove the pods from the Crosswork cluster:

  • kubectl edit cdgoperator cdgoperator-cr -n cdg

    • If there is only one data gateway in the cluster, remove the CDG array including cdg_dep_plan under the spec section.

    • If there are more than one data gateway in the cluster, remove only the data gateway array entry under cdg_dep_plan which has to be deleted and save it. 

  • kubectl delete infraservices <Data Gateway Instance Name> -n cdg

    For example, kubectl delete infraservices op-cdg -n cdg

  • kubectl delete collectors collector-<PDG Identifier> -n cdg

    For example, kubectl delete collectors collector-26b0053f-5132-4379-a107-f924dfde77f4 -n cdg

  • kubectl delete icon icon-<PDG Identifier> -n cdg

    For example, kubectl delete icon icon-26b0053f-5132-4379-a107-f924dfde77f4 -n cdg

  • If offload pods are present, kubectl delete offload offload-<PDG Identifier> -n cdg

    For example, kubectl delete offload offload-26b0053f-5132-4379-a107-f924dfde77f4 -n cdg

Uninstall Crosswork Applications

This section explains how to uninstall an application in the Crosswork UI. The Uninstall option removes the application, application-specific menus and associated data.


Attention

Crosswork Active Topology (if installed) must be uninstalled before you can uninstall Crosswork Optimization Engine.

Procedure

Step 1

Click on Admin > Crosswork Manager, and select the Application Management tab.

The Crosswork Platform Infrastructure and any applications that are added are displayed here as tiles.

Step 2

Click on the application tile that you want to uninstall, and select the Uninstall option from the drop down list.

Step 3

Click Uninstall to confirm when prompted.

The selected application is uninstalled and the application tile is modified to reflect the same.

Figure 2. Application Management Window
Application Management Window

You can also view the progress of uninstallation in the Job History window (Application Management > Job History). If the uninstall fails, you can reattempt using the relevant options in the Job History window.

Note

 

The uninstall operation does not remove the CAPP file from the repository. The CAPP file will remain visible in the Crosswork UI, in case user wants to install in the future.