This section explains Cisco Optical Network Controller functions, including optical domain control, path computation, model-based abstraction, and software support. Use it to understand core controller capabilities.
Cisco Optical Network Controller functions is a Cisco Optical Network Controller capability that
-
supports the related optical network management workflow,
-
provides context for configuration, monitoring, or troubleshooting tasks, and
-
helps operators understand how the feature behaves before they use it.
Cisco Optical Network Controller functions details
Cisco Optical Network Controller (Cisco ONC) is an optical SDN Controller for Cisco optical networks. Cisco Optical Network Controller behaves as a Provisioning Network Controller (PNC) and performs these functions.
-
Collects information about the inventory (device types, circuits and more) and topology (node arrangment) of the managed network.
-
Monitors the physical or virtual topology of the network.
-
Notifies of changes in topology and service changes.
-
Supports the creation and deletion of optical paths.
Optical SDN controller
Optical SDN controller is a specialized SDN controller that
-
manages and controls devices within a optical technology domain, and
-
communicates with the higher-level SDN controller via east-west interfaces
Core functions of Cisco Optical Network Controller
Cisco Optical Network Controller collects data necessary for optical applications. This data is used to provide abstract network information to higher layer controllers. This abstraction enables centralized control of optical network.
Cisco Optical Network Controller supports several functions.
-
Optical Domain Controller
Cisco Optical Network Controller behaves as a domain controller for Cisco optical products. The domain controller feeds data into hierarchical controllers for high-level network orchestration. Cisco Optical Network Controller has a North Bound Interface (NBI) based on the OIF transport API (T-API) standard which enables it to connect to any hierarchical controller which has a TAPI compliant South Bound Interface (SBI) and provides its functions to the controller.
-
Path Compute Engine (PCE)
PCE service provides optical path computation to ensure optically valid paths are provisioned within the supplied constraints. PCE uses the latest network status to compute the optical path.
-
Model Based Network Abstraction
Cisco Optical Network Controller supports a standardized TAPI model which enables it to abstract the device level details from the hierarchical controller.
For more details on Cisco Optical Site Manager (COSM), see COSM Configuration Guide.
For more details on Cisco Optical Network Planner (CONP), see CONP Configuration Guide.
For further details about Cisco Optical Network Controller, see the Cisco Optical Network Controller (CONC) Data Sheet .
TAPI is disabled by default to ensure proper device integration and data collection, enabling seamless operation. You must enable it before onboarding devices.
You must not enable TAPI after onboarding devices in Cisco Optical Network Controller. It must be enabled only before onboarding any of the devices.
You must enable TAPI after de-boarding all the devices.
To enable or disable TAPI, see Enabling and Disabling the TAPI Northbound Interface