Cisco Crosswork Optimization Engine Installation guide

Type
Installation guide

This manual is also suitable for

Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
First Published: 2020-07-06
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright ©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com
go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any
other company. (1721R)
©2020 Cisco Systems, Inc. All rights reserved.
CONTENTS
Overview of Cisco Crosswork Optimization Engine 1
CHAPTER 1
Overview of Cisco Crosswork Optimization Engine 1
Segment Routing Path Computation Element (SR-PCE) 2
Audience 3
Installation Requirements 5
CHAPTER 2
Cisco Crosswork Optimization Engine Network Requirements 5
Cisco Crosswork Optimization Engine Installation Requirements 9
Virtual Machine Requirements 9
Cisco IOS XR Software Version Support 12
Cisco Network Services Orchestrator and Network Element Driver Requirements 12
Device and TE Tunnel Scale Support 13
IGP and Inter-AS 14
Supported Web Browsers 14
Cisco Crosswork Optimization Engine Ports 15
Collection Considerations 15
Cisco Crosswork Data Gateway Installation Requirements 16
Virtual Machine (VM) Requirements 16
Tested Cisco Operating Systems 18
Ports Used 19
Install Cisco Crosswork Optimization Engine 21
CHAPTER 3
Installation Workflow 21
Install Cisco Crosswork Optimization Engine 22
Install Cisco Crosswork Optimization Engine 22
Install using OVF Tool 28
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
iii
Verify the VM Configuration 30
Log In to the GUI From a Browser 31
Troubleshoot the Installation 32
Install Cisco Crosswork Data Gateway 35
Cisco Crosswork Data Gateway OVF Parameters and Deployment Scenarios 35
Install Cisco Crosswork Data Gateway Using vCenter 42
Install Cisco Crosswork Data Gateway Via OVF Tool 50
Post-installation Tasks 52
Log In and Log Out 53
Generate An Enrollment Package 54
Export Enrollment Package 55
Import Controller Signing Certificate File 57
View the Controller Signing Certificate File 60
Enroll Cisco Crosswork Data Gateway With Cisco Crosswork Optimization Engine 61
Enroll Cisco Crosswork Data Gateway 61
Cisco Crosswork Data Gateway Authentication and Bootstrap 65
Troubleshoot the Cisco Crosswork Data Gateway Installation and Enrollment 66
De-enroll Cisco Crosswork Data Gateway 67
Upgrade Cisco Crosswork Optimization Engine 71
CHAPTER 4
Upgrade Workflow 71
Upgrade Cisco Crosswork Optimization Engine 72
Upgrade Cisco Crosswork Data Gateway 79
Crosswork Patch Framework 79
Remove Cisco Crosswork Optimization Engine and Cisco Crosswork Data Gateway 83
CHAPTER 5
Deleting Cisco Crosswork Optimization Engine and Cisco Crosswork Data Gateway 83
Device Configurations 85
APPENDIX A
Prerequisites for Onboarding Devices 85
Multiple Cisco SR-PCE HA Pairs 86
SR-PCE Configuration Examples 90
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
iv
Contents
CHAPTER 1
Overview of Cisco Crosswork Optimization
Engine
This section provides the following topics:
•Overview of Cisco Crosswork Optimization Engine, on page 1
•Segment Routing Path Computation Element (SR-PCE), on page 2
•Audience, on page 3
Overview of Cisco Crosswork Optimization Engine
Cisco Crosswork Optimization Engine is part of the Cisco Crosswork Network Automation suite of products.
Cisco Crosswork Optimization Engine provides real-time network optimization allowing operators to effectively
maximize network utilization as well as increase service velocity.
Crosswork Optimization Engine provides the following:
• A topology map that gives valuable real-time visualization of devices, links, link utilization, and TE
tunnels (Segment Routing policies and RSVP-TE tunnels) in the network.
Throughout this document TE tunnels refer to both SR policies and RSVP-TE
tunnels.
Note
• A UI that allows for easy manageability of TE tunnels. Crosswork Optimization Engine enables the
network operator to perform the following tasks:
• Provision TE tunnels and modify or remove them using an intuitive workflow
• Continuously track TE tunnel dynamic path computations to maintain SLA objectives
• Preview TE tunnels before deploying it to the network
• Crosswork Optimization Engine function packs (with correct licensing) that provide closed-loop
optimization to define the optimization intent, implement the intent, and continuously monitor, track,
and react to maintain the original intent.
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
1
Cisco Crosswork Optimization Engine Architecture
In order to provide for better scalability and improved performance the data collection functionality has been
separated out into its own VM and software package called Cisco Crosswork Data Gateway. The license to
use Cisco Crosswork Data Gateway is included with the Crosswork Optimization Engine license. Cisco
Crosswork Data Gateway gathers all the information from the monitored devices and forwards it to Crosswork
Optimization Engine for analysis and processing. Crosswork Optimization Engine can then be used by the
operator to manage the network or respond to changes in the network. In addition to collecting data for
Crosswork Optimization Engine, Cisco Crosswork Data Gateway can also be configured to gather and forward
data to other network monitoring and management tools.
There are two ways in which you can configure devices to send telemetry information to Cisco Crosswork
Data Gateway and Crosswork Optimization Engine:
•(Recommended) Integrate Cisco Network Services Orchestrator (Cisco NSO) with Crosswork Optimization
Engine
In this scenario, Crosswork Optimization Engine uses Cisco NSO as a provider to manage the devices
for any required model-driven telemetry (MDT) sensor paths for data collection. Cisco NSO pushes the
required configuration changes to the managed devices.
• Manually apply telemetry configuration on your devices
See the "Prerequisites for Device Telemetry" topic in the Cisco Crosswork Optimization Engine User
Guide
Crosswork Optimization Engine is designed and tested to be used with the Cisco Crosswork Data Gateway
1.1.3 release.
Note
This guide explains the installation process to set up both Crosswork Optimization Engine and Cisco Crosswork
Data Gateway for use. For information on how to use Crosswork Optimization Engine, refer to the Cisco
Crosswork Optimization Engine User Guide.
For more information about the Cisco Crosswork Network Automation platform and Cisco Crosswork
Optimization Engine, see the Cisco Crosswork Network Automation Product page on Cisco.com.
Segment Routing Path Computation Element (SR-PCE)
Crosswork Optimization Engine uses the combination of telemetry and data collected from the Cisco Segment
Routing Path Computation Element (SR-PCE) to analyze and compute optimal TE tunnels.
Cisco SR-PCE (formerly Cisco XR Traffic Controller (XTC)) runs on the Cisco IOS XR operating system.
SR-PCE provides stateful PCE functionality that helps control and move TE tunnels to optimize the network.
PCE describes a set of procedures by which a Path Computation Client (PCC) can report and delegate control
of head-end tunnels sourced from the PCC to a PCE peer. The PCC and PCE establish a Path Computation
Element Communication Protocol (PCEP) connection that SR-PCE uses to push updates to the network.
Crosswork Optimization Engine discovers all devices that are part of the IGP domain including those that do
not establish PCEP peering with SR-PCE. However, PCEP peering is required to deploy TE tunnels to the
device.
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
2
Overview of Cisco Crosswork Optimization Engine
Segment Routing Path Computation Element (SR-PCE)
Audience
This guide is for experienced network administrators who install Cisco Crosswork Optimization Engine and
Cisco Crosswork Data Gateway in their network. This guide assumes that you are familiar with the following:
• Linux system administration
• Routing and switching terminology and concepts
• Configuration of SR policies and RSVP-TE tunnels
• Deploying OVF templates using VMware vCenter
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
3
Overview of Cisco Crosswork Optimization Engine
Audience
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
4
Overview of Cisco Crosswork Optimization Engine
Audience
CHAPTER 2
Installation Requirements
This section provides general guidelines and minimum requirements for individual components installed on
a single server.
This section contains the following topics:
•Cisco Crosswork Optimization Engine Network Requirements, on page 5
•Cisco Crosswork Optimization Engine Installation Requirements, on page 9
•Cisco Crosswork Data Gateway Installation Requirements, on page 16
Cisco Crosswork Optimization Engine Network Requirements
The following figures show the different topology models, and the corresponding network components and
connections needed to install and use Cisco Crosswork Optimization Engine.
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
5
Figure 1: Crosswork Optimization Engine Network Components - 1 NIC Network Topology
Figure 2: Crosswork Optimization Engine Network Components - 2 NIC Network Topology
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
6
Installation Requirements
Cisco Crosswork Optimization Engine Network Requirements
Figure 3: Crosswork Optimization Engine Network Components - 3 NIC Network Topology
There are three types of traffic flowing between the network components, as explained in the following table.
Table 1: Types of Network Traffic
DescriptionTraffic
For accessing the UI and command line, and passing Data/Control information between
servers (for example, Cisco Crosswork Optimization Engine to Crosswork Data
Gateway or NSO)
Management
Data and configuration transfer between CDG and Cisco Crosswork Optimization
Engine, and other data destinations (external Kafka/gRPC).
Data/Control
Device configuration and management and telemetry data being forwarded to the CDG.Device Access
Cisco Crosswork Optimization Engine Virtual Machine (VM)
The Cisco Crosswork Optimization Engine VM has the following vNIC deployment options:
Table 2: Cisco Crosswork Optimization Engine vNIC deployment modes
DescriptionvNICNo. of vNICs
Management, Data/Control and Device access passing through a single NICManagement1
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
7
Installation Requirements
Cisco Crosswork Optimization Engine Network Requirements
DescriptionvNICNo. of vNICs
ManagementManagement2
Data/Control and Device accessData/Control
Cisco Crosswork Data Gateway (CDG) VM
The Cisco Crosswork Data Gateway VM has the following vNIC deployment options:
Table 3: CDG vNIC deployment modes
DescriptionvNICNo. of vNICs
Management, Data/Control and Device access passing through a single NICvNIC01
ManagementvNIC02
Data/Control and Device accessvNIC1
Management
vNIC03
Device AccessvNIC1
Data/ControlvNIC2
Cisco Network Services Orchestrator (NSO) VM
The NSO VM has the following vNICs:
• Management: Used for Crosswork applications to reach NSO.
• Device Access: Used for NSO to reach devices or NSO Resource Facing Services (RFS).
Preference for the number of vNICs can vary from one deployment to another. The number of vNICs can be
dependent on the security and traffic isolation needs of the deployment. CDG and Crosswork accommodates
this variability by introducing a variable number of vNICs.
Note
Routed and Device Networks
Connectivity between the various components should be accomplished via an external routing entity. The
figures show various line styles suggesting possible routing domains within the routed network.
• Solid—Management routing domain.
• Dotted—Data/Control routing domain (information transferred between Cisco Crosswork Optimization
Engine and Cisco Crosswork Data Gateway, and other data destinations (external Kafka/gRPC)).
• Dashes—Device access routing domain (from Cisco Crosswork Data Gateway and NSO).
The IP/subnet addressing scheme on each of these domains depends on the type of deployment.
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
8
Installation Requirements
Cisco Crosswork Optimization Engine Network Requirements
Routing between domains is needed for Crosswork and NSO to reach the devices. However, proper firewall
rules need to be in place to allow only select sources (for example, Crosswork and NSO) to reach the devices.
On the device network, devices can be reached in-band or using out-of-band management interfaces, depending
on the local security policies of each deployment.
A controller supporting Segment Routing Path Computation Element (SR-PCE) is both a device and a
Software-Defined Networking (SDN) controller. Some deployments may want to treat an SR-PCE instance
as a device, in which case they would need access via the device network. Some deployments may want to
treat an SR-PCE instance as an SDN controller and access it on the Management routing domain. Crosswork
supports both models. By default, Crosswork will use eth0 (Management) to access SR-PCE as an SDN
controller on the Management domain (shown in the figures). To enable Crosswork access to an SR-PCE
instance as a device on the device network (not shown in the figures): When adding an SR-PCE as a provider,
add the Property Key and Property Value as outgoing-interface and eth1 (Data/Control)
respectively.
CiscoCrossworkOptimizationEngineInstallationRequirements
Cisco Crosswork Optimization Engine deployment requirements vary, depending on which of the platform's
components are installed together and the number of devices being managed. This section provides general
guidelines and minimum requirements for installing Cisco Crosswork Optimization Engine on a single host,
unless otherwise specified.
Virtual Machine Requirements
You can deploy Cisco Crosswork Optimization Engine as a VM on a host that meets the minimum requirements
specified in Table 4: Cisco Crosswork Optimization Engine VM Requirements.
Table 4: Cisco Crosswork Optimization Engine VM Requirements
DescriptionRequirement
• VMware vCenter Server 6.7 Update 3g or later
(ESXi 6.7 Update 1 installed on hosts).
• VMware vCenter Server 6.5 Update 2d or later
(ESXi 6.5 Update 2 installed on hosts)
Hypervisor and vCenter
Installation should be done only from
vCenter. Installation is not supported on
ESXi directly.
Note
96 GBMemory
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
9
Installation Requirements
Cisco Crosswork Optimization Engine Installation Requirements
DescriptionRequirement
Storage requirements vary based on factors such as
the number of devices being supported and the type
of deployment selected.
Due to their performance, solid state drives (SSD) are
preferred over traditional hard disk drives (HDD). If
you are using HDD, the minimum speed should be
10,000 RPM.
For demonstration and lab environments, we
recommend the thin provision format because it
requires the least amount of storage on the host
machine. This deployment configuration uses roughly
23 GB of storage. For live systems, we recommend
the Thick provision eager zeroed format that
allocates 1 TB of storage by default. This should be
sufficient for most customer use cases.
For more information, see the volume requirements
displayed in the VMware GUI when configuring disk
space, as shown in Install Cisco Crosswork
Optimization Engine , on page 22.
Storage
16 vCPUs
CPU and memory overcommitment can occur when
the number of vCPUs running on a host is greater than
the total number of the host's physical processor cores.
VMware vCenter/ESXi permits this in order to allow
flexibility in deploying and running the VMs on
physical hosts. It is natural to assume that vCenter
users will try to maximize usage of physical resources
by deploying and running a reasonably high amount
of VMs on a specific ESXi host. However, this can
lead to a problem manifested in a "soft lockup"
situation, where a VM will not be able to get a vCPU
allocated in a reasonable amount of time.
vCPU/CPU Planning (avoid overcommittment)
For live deployments, we recommend that you use
dual interfaces, one for the Management network and
one for the Data network, between Cisco Crosswork
Optimization Engine and Cisco Crosswork Data
Gateway.
Network Connections
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
10
Installation Requirements
Virtual Machine Requirements
DescriptionRequirement
• You have a public IP address (IPv4 or IPv6) to
assign to the Cisco Crosswork Optimization
Engine VM's Management network. The default
gateway must be reachable using this IP address.
It is preferred that the DNS and NTP
servers are reachable using the
Management network. However, it is
not mandatory. The only requirement
is that these servers are reachable on
one of the networks connected to the
server.
Note
• You have a public or private IP address (IPv4 or
IPv6) to assign to the Cisco Crosswork
Optimization Engine VM's Data network. This
IP address must be able to reach the gateway
address for the network where Cisco Crosswork
Data Gateway will be installed.
IP Addresses
The IPv4 or IPv6 addresses or host names of the NTP
servers you plan to use. If you want to enter multiple
NTP servers, separate them with spaces. These should
be the same NTP servers you use to synchronize the
Cisco Crosswork Optimization Engine VM clock,
devices, clients, and servers across your network.
Confirm that the NTP servers are reachable on the
network before attempting installation. The installation
will fail if the servers cannot be reached.
NTP Servers
The IPv4 or IPv6 addresses of the DNS servers you
plan to use. These should be the same DNS servers
you use to resolve host names across your network.
Confirm that the DNS servers are reachable on the
network before attempting installation. The installation
will fail if the servers cannot be reached.
DNS Servers
The search domain you want to use with the DNS
servers, for example, cisco.com. You can have only
one search domain.
DNS Search Domain
The text of the legal disclaimer displayed to clients
accessing the VM using the CLI. Consult your
organization's IT or legal department for this content.
Disclaimer
Important Notes
• The VM runs Ubuntu Server 18.04.1 (ubuntu-18.04.1-server).
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
11
Installation Requirements
Virtual Machine Requirements
• Kubernetes runs within the Cisco Crosswork Optimization Engine VM and uses Docker for
containerization. The number of containers varies as applications are added or deleted.
Dual stack configuration is not supported in Cisco Crosswork Optimization Engine. Therefore, all addresses
for the environment must be either IPv4 or IPv6. Do not attempt to configure both in a single interface.
Note
Cisco IOS XR Software Version Support
Cisco Crosswork Optimization Engine supports the following Cisco IOS XR software versions.
Table 5: Cisco IOS XR Software Versions
PCC Software Version
(Headend Routers)
SR-PCE
Software
Version
Cisco XRv
9000
Cisco NCS 560
series
Cisco NCS 540
series
Cisco NCS 5500
series
Cisco ASR 9000
6.6.3 + SMU6.6.3 + SMU6.6.3 + SMU
2
6.6.3 + SMU 1
6.6.3 + SMU6.6.3 + SMU
7.1.27.1.27.1.27.1.27.1.27.1.2
1This SMU is available via the Cisco NCS 5508 Software Download Center.
2This SMU is available via the Cisco NCS 540-ACC-SYS Router or Cisco NCS 540x-ACC-SYS Router
Software Download Center.
• Segment Routing Traffic Matrix (SRTM) is only available in Cisco ASR 9000 devices.
• Software Maintenance Updates (SMUs) are required for both PCC/Headend and SR-PCE versions
indicated in the table. To download the Cisco IOS XR versions and updates, see the IOS XR Software
Maintenance Updates (SMUs) document. The correct SMUs to download will have "Optima" or the bug
ID appended to the filename. For example: asr9k-x64-6.6.3.Optima.tar
Note
Cisco Network Services Orchestrator and Network Element Driver
Requirements
The requirements in Table 3 are applicable only if you plan to use Cisco Network Services Orchestrator.
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
12
Installation Requirements
Cisco IOS XR Software Version Support
Table 6: Cisco NSO and NED requirements
Version/NotesSoftware/Driver
• NSO 5.2.0.3 (NSO Telemetry - Traffic Collector
Function Pack 1.0.0)
See the Telemetry - Traffic Collector Function
Pack Installation Guide 1.0 (PDF) for
information on how to install the function pack.
Note
Cisco Network Services Orchestrator (Cisco NSO)
7.18.3, 7.21Cisco IOS XR Network Element Driver (NED)
6.36Cisco IOS Network Element Driver
Device and TE Tunnel Scale Support
The following number of devices and TE tunnels (SR policies and RSVP-TE tunnels) are supported.
Table 7: Device and TE Tunnel (SR Policies and RSVP-TE Tunnels) Scale Support
TE TunnelsDevicesFeature
2,000 SR Policies• 5,000 nodes
• 50,000 interfaces
SR Policy Visualization and
Provisioning
2,000 RSVP-TE Tunnels• 5,000 nodes
• 50,000 interfaces
RSVP-TE Tunnel (PCE
initiated) Visualization and
Provisioning
2,000 RSVP-TE Tunnels• 5,000 nodes
• 50,000 interfaces
RSVP-TE Tunnel (PCC
initiated) Visualization only
—• 2,000 nodes
• 20,000 interfaces
Bandwidth Optimization
Function Pack
—• 5,000 nodes
• 50,000 interfaces
Bandwidth On Demand
Function Pack (with Priority
Mode)
—• 2,000 nodes
• 20,000 interfaces
Bandwidth On Demand
Function Pack (without Priority
Mode)
—500 nodesDemand Deduction Function
Pack
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
13
Installation Requirements
Device and TE Tunnel Scale Support
IGP and Inter-AS
The following table captures the IGP and inter-AS features that Cisco Crosswork Optimization Engine supports.
Table 8: IGP and Inter-AS Support
Inter-ASIS-ISOSPFFeature
Egress Peer Engineering
(EPE) is limited to EPE
adjacency segment IDs
(SIDs)
SupportedSupportedTopology Visualization
(including SR Policies)
EPE is limited to EPE
adjacency SIDs
SupportedSupportedSR Policy Creation,
Modification, and
Deletion
Not SupportedSupportedSupportedBandwidth on Demand
Function Pack
Not SupportedOnly single level is
supported
Only single area is
supported
Bandwidth Optimization
Function Pack
Supported with IGP
between ASes but not
EPE.
SupportedSupportedRSVP TE
Table 9: RSVP-TE Tunnel Traffic Steering Configuration
Inter Area/Level, Multiple IGP,
Inter-AS
Intra Area/LevelFeature
Requires Static Route configuration
pointing to the tunnel interface:
router static
address-family ipv4 unicast
<destination-ip>
<tunnel-interface>
Requires Autoroute Announce
configuration in individual tunnel
interface:
int tunnel-te <id>
autoroute-announce
exclude-traffic
segment-routing
PCC Initiatied
Requires Autoroute Announce
configuration under MPLS TE:
mpls traffic-eng
pcc
stateful-client
autoroute-announce
PCE Initiatied
Supported Web Browsers
This version of Cisco Crosswork Optimization Engine supports the web browsers shown in Table 4.
The recommended display resolution: 1600 x 900 pixels or higher (minimum: 1366 x 768).
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
14
Installation Requirements
IGP and Inter-AS
Table 10: Supported Web Browsers
VersionBrowser
75 or laterGoogle Chrome
(recommended)
70 or laterMozilla Firefox
In addition to using a supported browser, all client desktops accessing geographical map information in the
Cisco Crosswork Optimization Engine topology maps must be able to reach the mapbox.com map data URL
directly, using the standard HTTPS port 443. Similar guidance may apply if you choose a different map data
provider, as explained in "Configure Geographical Map Settings" in the Cisco Crosswork Optimization Engine
User Guide .
Cisco Crosswork Optimization Engine Ports
The following ports are needed by Cisco Crosswork Optimization Engine to operate correctly.
Table 11: Eth0 - Management NIC
DirectionUsed for...ProtocolPort
InboundSSH access to CrossworkTCP22
InboundWeb UI access to CrossworkTCP30603
OutboundCrosswork ControllerTCP30607
OutboundDNSTCP/UDP53
OutboundNTPUDP123
OutboundREST API to SR-PCETCP8080
OutboundCDG vitals collectionTCP30607
Table 12: Eth1 - Data NIC
DirectionUsed for...ProtocolPort
BothCDG sending collected data (Kafka)TCP30993
OutboundCDG MonitoringTCP30649
Collection Considerations
MDT Collection
When Cisco NSO is used in conjunction with Cisco Crosswork Optimization Engine, the telemetry
configurations are pushed to the devices by Cisco NSO. To use Cisco NSO, it is important during installation
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
15
Installation Requirements
Cisco Crosswork Optimization Engine Ports
to check the "Is NSO used as the provider for device management?" checkbox under Crosswork Collection
Configuration (see Install Cisco Crosswork Optimization Engine , on page 22).
If you do not plan to use to use Cisco NSO, you must apply the telemetry configuration on your devices. See
the "Prerequisites for Device Telemetry" topic in the Cisco Crosswork Optimization Engine User Guide.
The default MDT collector port is 9010.
Note
Device Limits
Cisco Data Gateway collection supports 1000 devices. If your network requires collection of more than 1000
devices, multiple Cisco Data Gateways must be deployed.
Cisco Crosswork Data Gateway Installation Requirements
This section provides information about the general guidelines and minimum requirements for installing Cisco
Crosswork Data Gateway.
This section contains the following topics:
•Virtual Machine (VM) Requirements, on page 16
•Tested Cisco Operating Systems, on page 18
•Ports Used, on page 19
Virtual Machine (VM) Requirements
You can deploy Cisco Crosswork Data Gateway as a VM on a host that meets the following minimum
requirements:
• Although Cisco Crosswork Data Gateway supports both IPv6 and IPv4, it is required to use IPv4 as
Cisco Crosswork Optimization Engine supports only IPv4.
• IPv4 on a single interface (demo mode) is not supported.
Note
Table 13: Cisco Crosswork Data Gateway VM requirements
DescriptionRequirement
• VMware vCenter Server 6.7 Update 3g or later (ESXi 6.7 Update 1 installed on
hosts)
• VMware vCenter Server 6.5 Update 2d or later (ESXi 6.5 Update 2 installed on
hosts)
Hypervisor
32 GBMemory
Cisco Crosswork Optimization Engine 1.2.1 Installation Guide
16
Installation Requirements
Cisco Crosswork Data Gateway Installation Requirements
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98

Cisco Crosswork Optimization Engine Installation guide

Type
Installation guide
This manual is also suitable for

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI