Cisco Crosswork Workflow Manager Solutions 2.1 MOPs User Guide

PDF

Cisco Crosswork Workflow Manager Solutions 2.1 MOPs User Guide

CWM Solutions MOPs

Want to summarize with AI?

Log in

Explains CWM Solutions MOPs, application type hierarchy, installation requirements, and default MOPs before you find and inspect MOPs and MOP actions.


Cisco Crosswork Workflow Manager Solutions (CWM Solutions) is a collection of pre-built use cases that offers users a convenient and efficient way to manage their network devices. It provides out-of-the-box use cases that are easy to deploy and ready to use.

The CWM Solutions MOPs application lets users create Methods of Procedure (MOPs) and MOP actions that allow the other CWM Solutions applications to automate and routinize a wide variety of network operations, from detecting the current version of a network operating system installed on a particular device, to upgrading the device operating system and applying new device configurations that change the role the device plays in your network.

CWM Solutions MOPs application

CWM Solutions and the MOPs application in particular are extremely powerful network automation products. Their underlying functionalities are enabled by the workflow automation functions provided by Cisco Crosswork Workflow Automation (CWM) and Cisco Network Services Orchestration (NSO) products.

A full explanation of the capabilities of these products is outside the scope of this guide, which concentrates exclusively on how to use the CWM Solutions MOPs application.

For a deeper dive, and examples of how to create workflows that can serve as MOPs and MOP actions, refer to the Cisco Crosswork Workflow Manager 2.1 Get Started Guide.


Application types and MOP structural hierarchy

When creating or modifying a MOP, the Application Type you select acts as a primary filter. It automatically adds workflows to the Available Actions list for that specific automation strategy.

To effectively manage network automation within CWM Solutions, you must understand the hierarchical relationship between:

  • application types,

  • MOPs,

  • and MOP actions.

Application type hierarchy

The application type serves as the root object that governs the execution strategy and product associations.

If you select the Fleet Upgrade application type, only upgrade-related actions are available. This approach helps you prevent configuration errors and ensures valid execution across the network.

The hierarchy contains these objects:

  • Application Type (root): This is the highest level of categorization, such as Fleet Upgrade or Golden Configuration. It defines the overarching operational logic and ensures that only compatible MOP actions and device series are associated. The application type defines the stages for the procedure: pre, distribute, activate, commit, and post.

  • MOP (procedure): A MOP is a specific instance of an application type. It organizes selected MOP actions into a plan for a specific vendor and product series.

  • MOP Action (step): Each MOP action is an individual workflow and serves as a building block of a MOP. These actions perform specific tasks, such as checking disk space or capturing configuration summaries. The system logs actions to specific application types to ensure they are used only in the correct operational context.


Default MOPs

The MOPs application comes installed with several default, or pre-built, MOPs. These MOPs are provided by Cisco, cannot be modified directly, although they can be copied and the copies modified, and are intended for use with specific CWM Solutions applications, specific supported vendors, and designated device families.

These default MOPs are installed with the MOPs application.

  • Default Juniper Upgrade: For performing fleet upgrades on Juniper Networks Inc. MX series devices running JunOS.

  • Default XE Upgrade: For performing fleet upgrades on Cisco Systems ASR 900 series devices running Cisco IOS XE. This also includes the Cisco ASR 900 Series Aggregation Services Routers, Cisco ASR 920 Series Aggregation Services Routers, Cisco ASR 1000 Series Aggregation Services Routers, Cisco Catalyst 8000V Edge Chassis Platforms, Cisco Catalyst 8300 Series Edge Platforms, and the Cisco Catalyst 9500 Series Switch.

  • Default XR Upgrade: For performing fleet upgrades on Cisco Systems 8000 series devices running Cisco IOS XR. This also includes the Cisco 8000 Series Routers, Cisco ASR 9000 Series Aggregation Services Routers, Cisco Network Convergence System 5500 Series, Cisco Network Convergence System 540 Series Routers, Cisco Network Convergence System 540L Series Routers, and the Cisco Network Convergence System 5700 Series Routers.

  • Default Golden Config - Juniper: For applying Golden Configuration templates on Juniper devices.

  • Default Golden Config - Cisco: For applying Golden Configuration on Cisco Systems devices.

Note

In most cases, you will want to select one of these default MOPs when performing a fleet upgrade or applying a golden configuration. They are usually your safest choice. Each of the default MOPs is customized for the supported vendor and product series, and the customizations are extensive. Each MOP varies significantly in the number of action types it makes available, the selected actions it performs during an upgrade, and the stages it goes through as it performs these actions.