Home
Support
Product Support
Optical Networking
Cisco Routed Optical Networking
Configuration Guides

Cisco Routed Optical Networking Solution Guide, Release 4.0

Releases

View all Saved Content

PDF

Is this helpful?

Helpful Unhelpful

Feedback

Thank you for your feedback. Your response has been recorded.

Ask about this document

Cisco Configuration Guide, Release 4.2

Table of contents

Expand all sections

About this document

Introduction to Traditional Networks

Routed Optical Networking solution
Traditional multilayer network architectures
Network building blocks
Challenges with current IP and optical networks

Routed Optical Networking

Routed Optical Networking
Legacy architecture and Routed Optical Networking architecture
Routed Optical Networking architecture
Benefits of Routed Optical Networking
Routed Optical Networking deployment models
What's new in Routed Optical Networking 4.0

Routed Optical Networking Solution Components

Hardware components
Components of network planning
Components of automation
IOS-XR software components

Deployment Topologies

Components and connections in metro and regional topology
Components and connections in mesh topology
Components and connections in long haul topology
Components and connections in point-to-point topology with NCS 1010 nodes
Components and connections in multi-degree topology with NCS 1010 nodes

Automation Workflows

Install Routed Optical Networking components
How Routed Optical Networking components communicate
Provision end-to-end service for Cisco routers with only ZR or ZR+ optics
How NSO Routed Optical Networking ML service works
How Crosswork Hierarchical Controller provisions Routed Optical Networking circuit
Automation starter solution and full solution
Troubleshoot provisioning issues on ZR or ZR+ optics

PLE Service Configuration

Private Line Emulation
How PLE works
Properties of circuit-style segment routing
Configure PLE over EVPN-VPWS
Verify PLE configurations

Sample end-to-end configuration

Sample configuration
Planning and design phase
Implement phase
Operate phase
Optimization phase

PLE Service Configuration

Updated: May 5, 2026

Overview

Describes Private Line Emulation service concepts and configuration procedures. It helps to configure PLE over EVPN-VPWS, frequency synchronization, optics payloads, QoS, CEM interfaces, performance measurement, segment routing, and policy verification.

Private Line Emulation

This section explains how Private Line Emulation carries SONET/SDH, OTN, Fiber Channel, and bit-transparent Ethernet services over a packet network. It describes why PLE is important for converging legacy private-line services.

How PLE works

This section describes how EVPN-VPWS pseudowires, CEM interfaces, MPLS or segment routing transport, and supported hardware carry private-line services across packet networks.

Properties of circuit-style segment routing

This section explains circuit-style segment routing properties for PLE transport. It describes bandwidth reservation, working and protect paths, candidate path behavior, liveness detection, and path constraints used to emulate circuit behavior.

Configure PLE over EVPN-VPWS

Use this workflow to configure PLE over EVPN-VPWS by completing the required supporting tasks.

Verify PLE configurations

Use this procedure to verify PLE service configuration and operational state. It explains how to confirm xconnect, CEM, SR-TE, and related policy details after configuring PLE over EVPN-VPWS.

Need help?

Open a support case

(Requires a Cisco Service Contract)

Bias-free language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.