Congratulations on choosing CSO for SD-WAN, Hybrid WAN, SD-LAN, and NFV lifecycle management. This guide is designed to help you quickly learn the basics of the Administration Portal.
The Administration Portal helps you:
See a compact, graphical view of important information in the Dashboard
Monitor system performance
Manage resources used by tenants and their customers
Configure service level agreement (SLA) parameters and application profiles
Manage tenants
Manage Administration Portal users and roles
Using the previously-mentioned capabilities you can create, provision, manage, and monitor all of the elements required for Contrail SD-WAN, Hybrid WAN, SD-LAN, and Next Generation Firewall (NGFW) deployments:
Hybrid WAN Deployment–CSO creates a secure site-to-site connection with a remote customer premises equipment (CPE) device, in part, to allow deployment of VNFs at the tenant site.
In a Hybrid WAN deployment, the primary goal is to provide the individual site with CSO-managed network services. When you deploy multiple Hybrid WAN sites, each one stands on its own.
Contrail SD-WAN Deployment–CSO creates secure site-to-site connections with remote CPE devices through the use of overlay networks. Multiple sites in an SD-WAN deployment can communicate with each other. Thus network functions can be deployed at any of the sites as needed.
In addition to site-local VNF access, individual SD-WAN sites can be extended to include SD-LAN and Mist WiFi access point capabilities.
SD-LAN Deployment-You can use CSO to manage EX Series LAN access switches that are deployed behind an Internet gateway device at customer sites.
The Internet gateway device can be an existing WAN router, a Contrail SD-WAN CPE, or an NGFW CPE. An SD-LAN deployment can be extended to include Mist WiFi access points.
NGFW Deployment–CSO creates a secure connection to an SRX-based NGFW device to provide managed security to the remote site. You can use CSO to manage the customer-site SRX Series devices and their built-in services thus providing managed security services to remote sites. An NGFW deployment can be extended to include SD-LAN and Mist WiFi access points.
To perform any of the deployments mentioned above, there are some things you need to know how to do within the CSO GUI. An administrator, working within the Administration Portal, must be familiar with a number of tasks. Some are for setup and configuration of CSO and some are needed to configure the components used in the previously-mentioned deployments. The following sections describe those tasks at a high level without linking them to any particular deployment.
The following procedures describe how to perform some of the administration tasks in the Administration Portal.
CSO allows global administrators (cspadmin user and equivalent) in the on-premises version of CSO to define and edit authentication methods, and to add and manage single sign-on servers. The cspadmin user has full access to change the authentication and authorization methods used by the CSO instance. Since the cspadmin user is not available to users in a cloud-hosted version of CSO, this function is reserved for Juniper Networks to perform.
An OpCo administrator (in either on-premises or cloud-hosted CSO versions) has no access to view or change the authentication Methods. The OpCo administrator has full access to add, edit, and delete Single Sign-On (SSO) servers and the authentication and authorization functions they perform for CSO. Figure 1 shows the default Authentication page with overlays showing the authentication types and the initial SSO configuration page.
Figure 1: Authentication Page
To view or change the authentication method used for CSO:
To manage SSO servers, navigate to the Administration > Authentication page.
Follow the Add SSO Server workflow guide to add and configure an SSO server for use with CSO.
You cannot delete an SSO server if the Authentication Method is set to use that server. You must set the authentication method to use either local authentication or another SSO server.
The Administration Portal allows the global administrator (cspadmin or equivalent) of an on-premises CSO installation to add OpCo and tenant-level administrator and user accounts. In a cloud-hosted version of CSO, the Administration Portal allows the OpCo administrator to add other administrators and users to their specific OpCo, and to add tenant-level administrators and users for the tenants of their OpCo.
The following task describes how to add an OpCo administrator.
The Users page appears.
The Add OpCo User page appears, as shown in Figure 2.
Figure 2: OpCo User Page
If you leave the status set to enabled, CSO sends an e-mail to the specified mail address upon completion of the procedure.
If you set the status to disabled, no mail is sent to the user.
CSO uses Role-Based Access Control (RBAC) to isolate control of certain features to specific roles (groups of users). The following task describes how to add a custom role to your tenant.
The Roles page appears.
The Add Role page appears, as shown in Figure 3.
Figure 3: Add Role Page
Pay particular attention to the Access Privileges. Many combinations are possible. Selecting some privileges automatically selects others.
A status message appears about the new role.
CSO automatically logs changes to an audit log. Administrators can view, export, purge and archive audit logs based on date range.
To view or manage audit logs:
The Audit Logs page appears.
Audit log details are displayed on the right part of the page.
The export or purge audit logs window appears.
Archived logs are stored as .zip compressed comma-separated value (CSV) files. These archives can be stored locally or on a remote server.
CSO automatically creates and deletes VPN tunnels between two sites based on user-specified session thresholds. The following procedure describes how to set the dynamic VPN thresholds for all tenants.
Your dynamic VPN thresholds will be applied to all of your tenants.
To upload a license:
The License Files page appears.
The Add License page appears as shown in Figure 4.
Figure 4: Add License Page
The Upload License page displays the progress of the license upload.
The status of the save operation is displayed.
For an on-premises version of CSO, the global administrator (cspadmin user or equivalent) adds CSO licenses to the application. The cspadmin user can also assign licenses to OpCos and tenants. As an OpCo administrator, you can assign the added licenses to your tenants.
The following procedure describes the assignment process.
The CSO Licenses Page is displayed. All assigned licenses and the license counts appear in the list.
The Assign CSO License window appears and shows the quantity for this license and the number available for assignment to tenants.
A new row on the list will appear.
The window will close and the CSO Licenses page will update immediately.
In an on-premises version of CSO, the global administrator (cspadmin user or equivalent) can update the intrusion prevention system (IPS) signature database by navigating to Administration > Signature Database while in the Global domain.
The following procedure describes how to download and apply signature database updates to CSO.
The update begins at the scheduled time. You can find information regarding the update procedure at the Monitor > Jobs page by searching for the signature update job.
OpCo administrators in either on-premises or cloud-hosted versions of CSO can view information about the active signature database installed in CSO and summary information about other database versions.
CSO uses e-mail to send messages, such as first-time access messages for new users and account locked messages. Because of this, you must configure an SMTP server for CSO to use.
The SMTP page appears.
Figure 5: SMTP Page
It is recommended that you send a test e-mail to confirm that your settings are correct. When using the Send Test Mail button, you will get either a success or failure message.
CSO allows OpCo administrators to create and distribute custom terms of use documents for their tenants.
To create a Terms of Use document:
The Terms of Use page appears.
The following task describes the e–mail templates used by CSO.
There are several circumstances under which CSO sends e-mail to users. You can view and edit these e-mail templates to suit your needs using the following procedure:
The Email Templates page appears that shows a list of CSO e-mail templates as shown in Figure 6.
Figure 6: Email Templates Page
The template names indicate under which circumstances the template is used.
The Edit Template page appears.
A successful save message appears.
The following tasks describe how to add tenants in the administration portal:
This task describes how to add a single tenant. Alternatively, you could import a file that contains data for multiple tenants and their sites by clicking Tenants > Import Tenants > Import.
You can add SD-WAN, Hybrid WAN, Next Generation Firewall (NGFW), and LAN services in any combination for your tenant.
Note You cannot add or remove services once the tenant is added. Make your service selections with this in mind.
To add a single tenant:
The Add Tenant window appears.
Figure 7: Add Tenant Window
This task describes how to add multiple tenants using a JSON formatted text file.
To add multiple tenants:
The Import Tenants page appears.
The status of the import and add jobs will appear as messages on the Tenants page.
An OpCo administrator in either cloud-hosted or on-premises versions of CSO can delete existing tenants using the following procedure:
The Tenants page appears.
A confirmation window pops up.
The following tasks describe the Configuration tasks that can be performed within the Administration Portal.
SLA-based steering profiles allow administrators to determine when specific traffic types get switched to a different WAN link based on link performance metrics like jitter, round-trip-time, and packet loss.
This task describes how to add SLA-Based Steering Profiles for use by your tenants in SD-WAN Policy intents.
The SLA-Based Steering Profiles page shows a list of Juniper-supplied steering profiles with names that start with “CSO-”. These profiles can be used as-is in SD-WAN Policies.
The Create SLA Profile page appears as shown in Figure 8.
Figure 8: Create SLA Profile Page
Since SLA-Based Steering profiles are intended to assist CSO in making path switching decisions, it is recommended to leave the Path Preference set to Any. This allows CSO to switch traffic to different WAN paths in situations where SLAs are not being met by the active path.
Path-based steering profiles allow administrators to specify which WAN link is used to transport specific types of traffic.
This task describes how to add a Path-Based Steering Profile for use by your tenants in SD-WAN Policy intents.
The Path-Based Steering Profiles appears.
The Create Path Profile page appears.
Since Path-Based steering profiles are intended to allow an administrator to choose a specific path for certain traffic types to use, it makes sense to choose a specific path in the Path Preference section. This ensures that your path preference is used rather than a system-determined path.
Application traffic type profiles define custom traffic types for use within your SLA profiles. These profiles are added to CSO by the global administrator (cspadmin user or equivalent) in an on-premises version of CSO. For cloud-hosted versions, Juniper manages the creation and enabling of application traffic types.
An OpCo administrator can view the list of application traffic type profiles by navigating to Configuration > Application Traffic Type Profiles. An application traffic type must be enabled so that it can be used in an SLA profile. Only 4 application traffic type profiles can be enabled at one time. Contact the global administrator, or your account team for cloud-hosted CSO, if you need new profiles to be created or enabled.
Breakout profiles are used to enable sites to break out traffic directly from the site (local breakout), through the hub or gateway (backhaul or central breakout), or through a cloud-based security platform (cloud breakout). On the Breakout Profiles page, you can view, add, edit, or delete local, backhaul, and cloud breakout profiles.
To add a breakout profile for your site:
The Breakout Profiles page appears with a list of existing profiles, if any.
The Add Breakout Profile window appears.
Available options are:
Local Breakout (Underlay)
Backhaul
Local Breakout (Cloud)
The available options depend on which application profile types are enabled on your instance of CSO.
Note Cloud breakout profiles default to Any path and cannot be changed.
If you enable rate limiting, all the fields in the Advanced Configuration section are required.
The new profile appears in the list.
CSO ships with a pre-defined set of application signatures for use in firewall and SD-WAN policies. This set of signatures is usually enough to get started. Global and OpCo administrators can create custom signatures.
To create a custom signature:
The Create Application Signature window appears.
A global administrator in an on-premises version of CSO can configure additional signature details in the Signature Classification section of the window.
This option is used to prioritize signature application when traffic matches multiple signatures. Lower numbers have higher priority.
You must assign network services to tenants to enable them to access the network services. The network services are published to the network services catalog by the global administrator (cspadmin or equivalent), or Juniper Networks in the case of cloud-hosted CSO. You can assign services in the following ways:
Assign one or more services to a single tenant:
The Tenants page appears.
The Allocate Network Services to Tenant-Name page appears.
You are returned to the Tenants page and the status of the assign operation is displayed.
Assign a service to one or more tenants:
The Network Services page appears.
The Select Tenant(s) to allocate the Service page appears.
You return to the Network Services page. The count in the Tenants column increases by the number of tenants that you assigned to the service.
CSO allows administrators to manage the resources used for creating Contrail SD-WAN, Hybrid WAN, SD-LAN, and NGFW solutions. These include Points of Presence (POPs), sites, tenant devices, provider hub devices, device templates, and device software images.
The following tasks describe the management of these resources.
Only the global administrator (cspadmin or equivalent) can add a POP to CSO. An OpCo administrator can only view POPs created by the global administrator.
To add a POP to an on-premises version of CSO:
The POPs page appears.
The Add POP window appears. Fill in the required (marked by *) information and click Next until you reach the summary page.
The new POP appears in the list.
CSO allows OpCo administrators to add provider hub devices used in Contrail SD-WAN deployments by accessing Resources > Site Management page.
When an OpCo administrator adds a provider hub from the site management page, they are providing the their tenants with access to an existing provider hub that is already assigned to a POP.
Note The creation of the hub device and its assignment to a POP is handled at the Resources > Provider Hub Devices page.
In cloud-hosted CSO, OpCo administrators can assign one or more provider hub devices to their OpCo, and thus their tenants, or they can leave this task for individual tenant administrators. At least one OAM capable provider hub must be available, through a regional POP, for every tenant so that CSO can manage the CPE devices.
Follow the steps below to allow your tenants access to a specific provider hub.
The Add Provider Hub for <OpCo-Name> window appears.
The list of available hubs is built from the hubs assigned to the selected POP.
Job start and job complete messages appear and the list can be refreshed to show the new hub device.
CSO provides administrators a way to see all tenant devices within their domain. For the global administrator, this includes all configured devices. For an OpCo administrator, this includes only those devices configured within their OpCo.
The view allows you to see the management status, operational status, device model, OS version, and so on.
CSO provides administrators with the ability to add provider hub devices to the system. These devices are multi-tenant hub devices that are associated with a specific regional POP. There are 3 types of provider hub devices: OAM_ONLY, DATA_ONLY, or OAM_AND_Data. The global administrator of an on-premises version of CSO can create any type of provider hub.
In cloud-hosted versions of CSO, Juniper creates and manages all OAM hubs. Thus, an OpCo administrator can only add DATA_ONLY hubs.
To add a DATA_ONLY hub:
The Provider Hub Devices Page appears with a list of available provider hubs.
The Add Provider Hub Device window pops up.
All the fields within the site information section are required.
The management region and site capability pull-down menus have only one choice.
Select the appropriate POP in which to place the new hub device.
The window advances to the WAN tab.
Only SRX templates are available for provider hub devices.
The list of templates is built from the SRX templates available at Resources > Templates > Device Templates.
Required information is marked with an asterisk (*).
You can leave Auto Activate enabled or you can disable it. If disabled, device activation becomes a separate step that is carried out later, perhaps after the hub is put in place at the POP.
The IP prefix and gateway IP address values are dependant on your network infrastructure. These are the addresses that this hub device uses for communication with remote CPE devices.
The window advances to the Summary tab.
Review the summary information and correct as needed.
The device will be modeled, activated, and finally provisioned if the Auto Activation button was left active. If not, activation and provisioning will have to be done separately.
CSO allows administrators to upload various types of images for use on physical and virtual devices. The table below lists the various image types and their uses:
Image Type | Used For |
---|---|
Device Image | Software image for physical devices such as CPE and hub devices. |
VNF Image | Software image for a virtual device |
VNF Script | Provision Script for VNF image |
EMS Plugin Package | Element Management System plugin to support new device families |
Device Extension Package | Extension software package that can be installed on a device |
Boot Config Image | Bootable ISO software image for VNF or virtual devices |
Telemetry Agent Package | Installs a telemetry agent on a device |
Telemetry Agent Plugin | Installable plugin to enable telemetry from a specific set of VNFs |
VNFM Plugin Package | Installable VNF Manager plugin for a specific set of VNFs |
Once uploaded, the various packages can be staged and deployed to tenant devices on a site-by-site or all-sites basis. Staging an image prior to deploying helps to ensure image deployment works on slow network links.
CSO provides administrators with the ability to monitor the CSO system and its tenants.
To view highlights of the CSO monitoring feature:
The map can be zoomed and filtered by alarm severity by selecting the appropriate checkbox from the POPs pull-down menu at the upper left corner of the map.
You can see the severity, time, tenant, site, and a description of the alerts, if any.
The cspadmin user (or equivalent) can create new alert definitions by clicking the Add icon (+) and filling out the fields in the create alert definition window.
The graph at the top of the page shows a count of alarms over a specified time period. You can adjust the time range for the graph to filter the alarms and create additional filters by tenant, site, source, and severity.
You can choose between card display and grid display and filter the metrics by time.
You can see a job history or see upcoming jobs that have been
scheduled for a future time.
Clicking on an individual Job Name shows the details about that job. Further details
may be available by clicking additional links within the job details
pop-up window.
CSO provides a dashboard, which is the default landing page upon successful login. The dashboard can display various graphical information about tenants and sites.
You can customize the dashboard by dragging widgets from the top carousel down to the main dashboard. Different users can have their own dashboards. A user can also have multiple dashboards defined.