Overview

This chapter provides information about the intended audience of the Cisco MSX platform, what's new in the current release, and related documentation.

Cisco MSX Platform Overview

Cisco MSX is an open software platform that enables service providers to create and manage services across physical and virtual network elements. The Cisco MSX solution utilizes network function virtualization and enables service providers to provide their customers a flexible selection of services that are easily customized through a self-service portal. It reduces the costs for service creation, customer acquisition, service fulfillment, time to repair, and maintenance. With Cisco MSX solution, you can automate end-to-end provisioning for different use cases and service topologies. Each release of the Cisco MSX provides out-of-box capabilities to orchestrate particular use cases, also called service packs (such as, Cisco MSX SD-WAN, Cisco MSX SD-Branch, and Cisco MSX Managed Devices). The Cisco MSX service packs are a suite of prepackaged software capabilities that fully automate the end-to-end service creation including ordering, service chaining, orchestration, service assurance, user self care, real time performance reporting, and user-defined policy changes. With these fully validated service level packages, end customers can quickly turn on, control, and ensure cloud-based managed services offered by the service provider. For more information about Cisco MSX solution, see Cisco Managed Services Accelerator (MSX) 4.2 Solution Overview Documentation.

What’s New in Cisco MSX Platform

Feature

Description

Change Management and Approvals for Device Configuration

The Cisco MSX device configuration workflow includes a change request and approval capability. Modifications to an onboarded device require Change Management approval. For more information, see Configuring Change Management Approvals.

Cisco MSX IDP-initiated Flow Support

The Cisco MSX IDP now includes IDP initiated flow and validation against the Meraki implementation.

For more information, see Configuring IDP-initiated SSO for Meraki.

Tracing End-to-End HTTP Request in Cisco MSX

Cisco MSX supports tracing end-to-end HTTP requests. Cisco MSX injects an X-B3-TraceID header into the requests to make it easier to trace an HTTP request. You can see the Trace ID by expanding the Notification where support is implemented.

Audience

This guide is designed for administrators who use Cisco MSX platform to configure basic operations after installing Cisco MSX.

The platform addendum should be used in conjunction with this guide.

Logging In and Logging Out of the Cisco MSX Portal

To log into the Cisco MSX portal, enter the following URL in your web browser address field, where server-ip is the IP address or fully qualified domain name (FQDN) name of the Cisco MSX server:

https://<server-ip>/vms or https://<your_portal_fqdn>

Depending on your network configuration, the first time your browser connects to the Cisco MSX web server, you may have to update your client browser to trust the security certificate of the server. This ensures the security of the connection between your client and the Cisco MSX web server.

Your user account privileges determine what you can see and do in the user interface. For information on Cisco MSX users and the actions they can perform, see Managing User Roles.

If you are using any third-party applications with Cisco MSX, you can configure single-sign on (SSO) to access these applications from Cisco MSX. For more information about configuring single-sign on, see Configuring Single Sign-On.

To log out, in the left pane of the Cisco MSX portal, click Logout.

Accessing Cisco MSX APIs

In Cisco MSX, OAuth 2.0 access tokens are used to make API requests to the application on behalf of a user. After the user is authenticated using the Cisco MSX credentials, they can obtain the access token which is shown in the procedure below. The same token can be used on each API request to indicate the request is executed on behalf of the user.

Using this procedure, you can use the Cisco MSX APIs for platform or service-pack operations.

Before you begin

Configure authorization server (Auth Server) properties. For more information, see Configuring Authorization Server Properties.

Procedure

Step 1

Obtain the Cisco MSX client credentials.

Use the credential for logging in to the Cisco MSX portal. If you do not have these credentials, contact your Service Provider Administrator.

Step 2

Obtain an access token from the Cisco MSX authorization Server.

Use the following curl command to get the token.

curl -k -d 'grant_type=password&username=*********&password=*****' -H "Content-Type: 
application/x-www-form-urlencoded" -H "Authorization: Basic *******" -X POST 
https://<Product_URL>/idm/v2/token
Step 3

Send the access token to an API.

After obtaining the access token, send the token to an Cisco MSX API in an HTTP authorization header. The below example shows a sample curl command for updating the current password policies. Use the access_token that was obtained in Step 2 to run this curl command. 

curl -k -X PUT --header "Content-type: application/json" --header "accept:
application/json" --header "authorization: Bearer <ACCESS_TOKEN>" -d '{ "accountLocking": {
"enabled": true, "lockoutDurationMin": 30, "lockoutFailCount": 3,
"lockoutFailIntervalSec": 60 }, "agingRule": { "enabled": true, "expireWarningSec":
1209600, "graceAuthNLimit": 3, "maxAgeSec": 0, "minAgeSec": 0 }, "characterRule": {
"enabled": true, "minDigit": 1, "minLowercasechars": 1, "minSpecialchars": 0,
"minUppercasechars": 1 }, "description": "string", "historyRule": { "enabled": true,
"passwdhistorycount": 10, "passwdhistorydurationMonth": 60 }, "lengthRule": { "enabled":
true, "maxLength": 16, "minLength": 8 }, "name": "ppolicy_default" }'
https://<Product_URL>/idm/api/v1/pwdpolicy/ppolicy_default
Your client application requests an access token from the Cisco MSX authorization server, extracts a token from the response, and sends the token to the Cisco MSX API that you want to access.