- play_arrow Overview
- play_arrow Working with Connectivity Services Director
- Connectivity Services Overview
- Getting Started with Connectivity Services Director
- Connectivity Services Director REST API Overview
- Understanding the Need for Connectivity Services Director for Managing Services
- Benefits of a Unified User Interface for Routing and Tunnel Services with Connectivity Services Director
- Connectivity Services Director Overview
- Understanding the Connectivity Services Director User Interface
- Understanding the Usage and Layout of Connectivity Services Director Views and Tasks
- Understanding Task Categories in Connectivity Services Director
- Understanding Connectivity Services Director User Administration
- Logging In to Connectivity Services Director
- Accessing the Services Activation Director GUI
- Changing Your Password for Connectivity Services Director
- Logging Out of Connectivity Services Director
- Getting Started Assistant Overview in Services Activation Director
- play_arrow Service View Tasks and Lifecycle Modes
- Understanding the Service View Tasks Pane in Build Mode
- Understanding the Service View Tasks Pane in Deploy Mode
- Understanding the Service View Tasks Pane in Monitor Mode
- Understanding the Service View Tasks Pane in Fault Mode
- About Build Mode in Service View of Connectivity Services Director
- About Deploy Mode in Service View of Connectivity Services Director
- About Fault Mode in All Views of Connectivity Services Director
- About Monitor Mode in Service View of Connectivity Services Director
- play_arrow Network Services Overview
- Getting Started with Connectivity Services Director
- Prestaging Devices Overview
- Junos Space Layer 2 Services Overview
- Junos Space Layer 3 Services Overview
- Provisioning Process Overview
- Seamless MPLS Support in Junos Space Overview
- Service Attributes Overview
- Service Order States and Service States Overview
- Understanding VLAN Manipulation (Normalization and VLAN Mapping) on Ethernet Services
- VLAN Pool Profiles Overview
- Redundant Pseudowires for Layer 2 Circuits and VPLS
- VPLS over GRE Overview
- Junos Space Network Topology Overview
- Service Recovery Overview
- Multicast L3VPN Overview
- Multi-Chassis Automatic Protection Switching Overview
- Inverse Multiplexing for ATM Overview
- Rendezvous Point
- Understanding Multicast Rendezvous Points, Shared Trees, and Rendezvous-Point Trees
- Understanding PIM Sparse Mode
- Configuring Shared-Tree Data Distribution Across Provider Cores for Providers of MBGP MVPNs
- Configuring SPT-Only Mode for Multiprotocol BGP-Based Multicast VPNs
- Configuring VRF Route Targets for Routing Instances for an MBGP MVPN
- Static Pseudowire Provisioning for VPLS Services
-
- play_arrow Getting Started With Connectivity Services Director
- play_arrow Understanding Connectivity Services Director System Administration and Preferences
-
- play_arrow Working with the Dashboard
- play_arrow About the Dashboard
- play_arrow Using the Dashboard
- play_arrow Dashboard Widget Reference
-
- play_arrow Working in Build Mode
- play_arrow About Build Mode
- play_arrow Discovering Devices
- play_arrow Creating Custom Device Groups
- play_arrow Configuring Quick Templates
- play_arrow Configuring Device Settings
- play_arrow Configuring Class of Service (CoS)
- play_arrow Configuring Link Aggregation Groups (LAGs)
- play_arrow Managing Network Devices
- Viewing the Device Inventory Page in Device View of Connectivity Services Director
- Viewing the Physical Inventory of Devices
- Viewing Licenses With Connectivity Services Director
- Viewing a Device's Current Configuration from Connectivity Services Director
- Accessing a Device’s CLI from Connectivity Services Director
- Accessing a Device’s Web-Based Interface from Connectivity Services Director
- Deleting Devices
- Rebooting Devices
-
- play_arrow Building a Topology View of the Network
- play_arrow Downloading and Installing CSD-Topology
- CSD-Topology Installation and Configuration Overview
- Installation Prerequisites
- Installing the CSD-Topology Software Using the RPM Bundle
- Minimum Hardware and Software Requirements for Junos VM on VMWare
- Installing the JunosVM for CSD-Topology
- Connecting an x86 Server to the Network
- Interactive Method of Installing the RPM Image and CSD-Topology Software from a USB or DVD Drive
- play_arrow Configuring Topology Acquisition and Connectivity Between the CSD-Topology and Path Computation Clients
- play_arrow Accessing the Topology View of CSD-Topology
- Understanding the Network Topology in Connectivity Services Director
- Monitoring the Topology of Network Elements Managed by CSD-Topology Overview
- Specifying Topology Preferences
- CSD-Topology Topology Map Window Overview
- Working with the Graphical Image in the Topology View Window
- Expanding and Collapsing Groups by Using the Topology Map Grouping Shortcut Menu
- Filtering Links, LSPs, and Services by Using the Topology Map Node Shortcut Menu
- Removing the Highlighted LSPs by Using the Topology Map LSPs Shortcut Menu
- Viewing the Service Path by Using the Topology Map Service Shortcut Menu
- Filtering Devices, LSPs, and Services for Sorting and Segregating the Topology View
- Segregating the Displayed Devices by Searching the Entire Topology View
- Resynchronizing the Topology View
- Viewing Device Details of a CSD-Topology for Examining Traffic Transmission
- Viewing LSP Details of a CSD-Topology for Analyzing Network Changes
- Viewing Link Details of a CSD-Topology for Determining the Operational Status
- Viewing Service Details of a CSD-Topology for Monitoring and Troubleshooting Service Parameters
- Viewing Topology Map Group Details in a Pop-Up Dialog Box
- Viewing Topology Map Device Details in a Pop-Up Dialog Box
- Viewing Topology Map Link Details in a Pop-Up Dialog Box
- Viewing Topology Map LSP Details in a Pop-Up Dialog Box
- Viewing Topology Map Service Details in a Pop-Up Dialog Box
- Enabling the Collection of LSP and Service Association Details
- Using Custom Grouping for Devices in a CSD Topology
- Viewing Generated Alarms for Services in the Topology View
- Viewing the Optical Link Details for Examining the Performance of Optical Links
-
- play_arrow Prestaging
- play_arrow Prestaging Devices Overview
- Prestaging Devices Process Overview
- Prestaging Workflow in Connectivity Services Director
- Prerequisites for Prestaging Devices in Connectivity Services Director
- Discovering and Assigning All N-PE Devices
- Discovering and Assigning N-PE Devices with Exceptions
- Prestaging ATM and TDM Pseudowire Devices
- Discovering and Assigning Provider Role or LSP Role for Devices with Exceptions
- Discovering and Assigning All Provider or LSP Devices
- Prestaging Rules
- play_arrow Prestaging: Managing Devices and Device Roles
- Discovering Tunnel Devices
- Adding a UNI
- Unassigning Device Roles
- Deleting UNIs
- Discovering Device Roles
- Excluding Devices from N-PE Role Assignment
- Excluding Interfaces from UNI Role Assignments
- Unassigning N-PE Devices
- Viewing N-PE Devices
- Viewing Prestaging Statistics
- Viewing Prestaging Rules
- Managing Prestage Device Jobs
- Specifying the Wait and Idle Times for Prestaging Devices
- play_arrow Prestaging: Managing IP Addresses
- play_arrow Device Configuration Prerequisites to Prestaging Examples
- play_arrow Prestaging Services
- Creating and Handling a Service Recovery Request
- Selecting a Service Definition in the Wizard for Creating a Service Recovery Request
- Specifying Devices and Filters in the Wizard for Creating a Service Recovery Request
- Reviewing the Configured Settings in the Wizard for Creating a Service Recovery Request
- Viewing Service Recovery Report
- Performing a Service Recovery on a Defined Service
- Processing of Device Change Notifications Overview
- Handling of Out-of-Band Notifications for Service Recovery
- Viewing Service Recovery Instance Details
- Managing Out-of-Band Notifications for Recovered Services
- Viewing Details of an Out-of-Band Notification for Recovered Services
- Viewing Services Rejected During a Service Recovery
- Viewing Service Recovery Jobs
- Performing a Configuration Audit for Recovered Services
- Viewing Configuration Audit Results of Recovered Services
- Recovering Modifications and Deletions Performed for Existing Endpoints
- REST API Changes in Connectivity Services Director for Service Recovery
- Sample XPath Notifications Received on Devices for Deleted Endpoints
- Sample XPath Notifications Received on Devices for a Modified E-LAN Service
- Sample XPath Notifications Received on Devices for a Created E-LAN Service
- Sample XPath Notifications Received on Devices for a Created IP Service
- Sample XPath Notifications Received on Devices for a Created E-Line Service
- Sample XPath Notifications Received on Devices for CFM Profiles Associated with an E-Line Service
- Sample XPath Notifications Received on Devices for CoS Profiles Associated with an E-Line Service
-
- play_arrow Service Design: Working with Service Definitions
- play_arrow Service Design: Predefined Service Definitions
- play_arrow Service Design: Managing E-Line Service Definitions
- Choosing a Predefined Service Definition or Creating a New Service Definition
- Creating an E-Line ATM or TDM Pseudowire Service Definition
- Creating a Multisegment Pseudowire Service Definition
- Modifying a Custom Service Definition
- Publishing a Custom Service Definition
- Unpublishing a Custom Service Definition
- Deleting a Customized Service Definition
- Viewing Service Definitions
- play_arrow Service Design: Managing E-LAN Service Definitions
- play_arrow Service Design: Managing IP Service Definitions
-
- play_arrow Service Provisioning: Working with Customers
- play_arrow Service Provisioning: Managing Customers
-
- play_arrow Working in Deploy Mode
- play_arrow About Deploy Mode
- play_arrow Deploying and Managing Device Configurations
- Deploying Configuration to Devices
- Managing Configuration Deployment Jobs
- Deploy Configuration Window
- Approving Change Requests
- Enabling SNMP Categories and Setting Trap Destinations
- Understanding Resynchronization of Device Configuration
- Resynchronizing Device Configuration
- Managing Device Configuration Files
- Enabling or Disabling Network Ports on Routers
- play_arrow Deploying and Managing Software Images
-
- play_arrow Service Provisioning: Working with Service Orders
- play_arrow Service Provisioning: Viewing the Configured Services and Service Orders
- play_arrow Service Provisioning: Managing E-Line Service Orders
- Creating a Service Order
- Creating an E-Line ATM or TDM Pseudowire Service Order
- Creating an E-Line Multisegment Pseudowire Service Order
- Creating an E-Line Service Order
- Creating a Bulk-Provisioning Service Order for Pseudowire Services
- Creating an Inverse Multiplexing for ATM Service Order
- Provisioning a Single-Ended E-Line Service
- Selecting Specific LSPs for Connectivity Services
- Stitching Two E-Line Pseudowires
- Creating and Deploying a Multisegment Pseudowire
- Deactivating a Service
- Reactivating a Service
- Force-Deploying a Service
- Recovering a Service Definition through Force Upload
- Decommissioning a Service
- Viewing Alarms for a Service
- Inline Editing of E-LAN and IP Service Orders
- Interconnecting an IP Service with an E-LAN Service
- Changing the Logical Loopback Interface for Provisioning
- play_arrow Service Provisioning: Managing E-LAN Service Orders
- play_arrow Service Provisioning: Managing IP Service Orders
- Stitching a Pseudowire to an IP Service
- Creating a Full Mesh IP Service Order
- Creating a Hub-and-Spoke IP Service Order
- Selecting a Published IP Service Definition for a Service Order
- Entering IP Service Order Information
- Selecting Endpoint PE Devices or Nodes
- Creating a Service Order Based on a Service Definition with a Template
- Deploying an IP Service Order
- Creating a Multicast VPN Service Order
- Creating Policies for an IP Service
- play_arrow Service Provisioning: Performing RFC 2544 Benchmark Testing
-
- play_arrow Service Provisioning: Working with Services Deployment
- play_arrow Service Provisioning: Managing Deployed Services
- Managing Service Configuration Deployment Jobs
- Deploying Services Configuration to Devices
- Deploy Configuration Window
- Deleting a Partial Configuration of an LSP Service Order
- Deleting a Service Order
- Deploying a Service
- Validating the Pending Configuration of a Service Order
- Viewing the Configuration of a Pending Service Order
- Viewing Decommissioned E-Line, E-LAN, and IP Service Orders
- Modifying an E-Line Service
- Modifying a Multipoint-to-Multipoint Ethernet Service
- Modifying a Point-to-Multipoint Ethernet Service
- Modifying a Hub-and-Spoke IP Service Order
- Modifying a Full Mesh IP Service
- Understanding Service Validation
- Highlighting of Endpoints in the IP, RSVP LSP, and E-LAN Service Modification Wizards
-
- play_arrow Auditing Services and Viewing Audit Results
- play_arrow Service Provisioning: Auditing Services
- Performing a Functional Audit
- Performing a Configuration Audit
- Troubleshooting N-PE Devices Before Provisioning a Service
- Modifying the Application Settings of Connectivity Services Director
- Troubleshooting the Endpoints of Services
- Basic Requirements of Operational Scripts
- Viewing Configuration Audit Results
- Viewing Functional Audit Results
- Viewing Functional Audit Results for an Inverse Multiplexing for ATM Service
- Modifying a Saved Service Order
- Viewing Service-Level Alarms
- play_arrow Troubleshooting Devices and Services
-
- play_arrow Working in Monitor Mode
- play_arrow About Monitor Mode
- play_arrow Monitoring Traffic
- play_arrow Monitoring Devices
- play_arrow General Monitoring
- play_arrow Monitor Reference
- Error Trend Monitor
- Equipment Status Summary Monitor
- Equipment Summary By Type Monitor
- Port Status Monitor
- Port Utilization Monitor
- Status Monitor for Routers
- Traffic Trend Monitor
- Unicast vs Broadcast/Multicast Monitor
- Unicast vs Broadcast/Multicast Trend Monitor
- Session Trends Monitor
- Current Sessions by Type Monitor
- User Session Details Window
- Current Active Alarms Monitor (All Views Except Service View)
- Top Sessions by MAC Address Monitor
- Top APs by Session Monitor
- Radio Technology Type Statistics Monitor
- Top Talker - Wired Devices Monitor
- Top Users Monitor
- Top APs by Traffic Monitor
- Top Talker - Wireless Devices Monitor
- RF Interference Sources Monitor for Devices
- play_arrow Detecting and Examining the Health and Performance of Services
- Service Monitoring Capabilities in Connectivity Services Director
- Computation of Statistics Polled from Devices for Display in Widgets on Monitoring Pages
- Configuring the Aggregation Method for Viewing Monitoring Details
- Viewing the Service Monitoring Summary Page for a Consolidated Listing of Services
- Monitoring the Service Summary Details of E-Line Services for Optimal Debugging
- Monitoring the Service Summary Details of E-LAN Services for Optimal Debugging
- Monitoring the Service Summary Details of IP Services for Optimal Debugging
- Monitoring the Service Traffic Statistics of E-Line Services for Correlating Device Counters
- Monitoring the Service Traffic Statistics of E-LAN Services for Correlating Device Counters
- Monitoring the Service Traffic Statistics of IP Services for Correlating Device Counters
- Monitoring the Service Transport Details of E-Line Services for Easy Analysis
- Monitoring the Service Transport Details of E-LAN Services for Easy Analysis
- Monitoring the Service Transport Details of IP Services for Easy Analysis
- Viewing Y.1731 Performance Monitoring Statistics for E-Line Services
- Viewing Y.1731 Performance Monitoring Statistics for E-LAN Services
- Using Print Page
- Clearing Interface Statistics
- Viewing MAC Table Details
- Viewing Interface Statistics
- Viewing Interface Status Details
- MPLS Connectivity Verification and Troubleshooting Methods
- Using MPLS Ping
- Pinging VPNs, VPLS, and Layer 2 Circuits
- Monitoring Network Reachability by Using the MPLS Ping Capability
- Monitoring Network Reachability by Using the Layer 3 VPN Ping Capability
- Routing Table Overview
- Viewing Routing Table Details
-
- play_arrow Working in Fault Mode
- play_arrow About Fault Mode
- play_arrow Using Fault Mode
- play_arrow Fault Reference
- Alarm Detail Monitor (All Views Except Service View)
- Alarm Detail Monitor (Service View)
- Current Active Alarms Monitor (Service View)
- Alarms by Category Monitor
- Alarms by Severity Monitor (Service View)
- Alarms by State Monitor
- Alarm Trend Monitor (Service View)
- Alarms by Severity Monitor (All Views Except Service View)
- Alarms by State Monitor (All Views Except Service View)
- Current Active Alarms Monitor (All Views Except Service View)
- Alarm Trend Monitor (All Views Except Service View)
-
- play_arrow End-to-End Configuration Examples
- play_arrow Working with Chassis View
- play_arrow Working with Devices
- play_arrow Managing CLI Configlets
-
- play_arrow Working with User Roles
- play_arrow Managing User Roles
-
- play_arrow Working with Tunnel Services
- play_arrow Tunnel Services Overview
- Tunnel Services Overview
- Traffic Engineering Capabilities
- Components of Traffic Engineering
- Routers in an LSP
- MPLS and RSVP Overview
- Fast Reroute Overview
- Point-to-Multipoint LSPs Overview
- RSVP Operation Overview
- Link Protection and Node Protection
- Connectivity Services Director–NorthStar Controller Integration Overview
- play_arrow Service Design and Provisioning: Managing and Deploying Tunnel Services
- Managing Devices and Tunnel Services Overview
- Discovering Tunnel Devices
- Creating an LSP Service Definition
- Creating an LSP Service Order
- Creating Public and Private LSPs
- Viewing the Configured LSP Services
- Modifying an Explicit Path in RSVP LSP Services
- Modifying an RSVP LSP Service
- Viewing LSP Services in Deploy Mode
- Viewing LSP Service Orders in a Table
- Deactivating an LSP Service
- Reactivating an LSP Service
- Force-Deploying an LSP Service
- Cloning an LSP Service
- Viewing Alarms for an LSP Service
- Managing Deployment of LSP Services Configuration to Devices
- Deploying an LSP Service
- Deleting a Partial Configuration of an LSP Service Order
- Deleting an LSP Service Order
- Validating the Pending Configuration of an LSP Service Order
- Viewing the Configuration of a Pending LSP Service Order
- Viewing the Configuration Details of RSVP LSP Services
- Viewing Decommissioned LSP Service Orders
- play_arrow Monitoring and Troubleshooting Tunnel Services
- Performing a Functional Audit for LSP Services
- Viewing Functional Audit Results for LSP Services
- Examining the LSP Summary Details for Effective Troubleshooting
- Troubleshooting the Endpoints of RSVP LSP Services
- Clearing LSP Statistics
- Monitoring Network Reachability by Using the MPLS Traceroute Capability
- Monitoring Network Reachability by Using the MPLS Ping Capability for RSVP LSPs
-
- play_arrow Appendix: Managing Network Activate Features Using the Older Version of Services Activation Director
- play_arrow Service Design: Working with E-Line, IP, and E-LAN Service Templates
- Service Templates Overview
- Service Templates Workflow
- Applying a Service Template to a Service Definition
- Creating a Service Template
- Deleting a Service Template
- Exporting a Service Template
- Finding Configuration Options
- Importing a Service Template
- Modifying a Service Template
- Specifying Service-Specific Values
- User Privileges in Service Templates
- Provisioning Dynamic Attributes to Specify the Device XPath
- Viewing Service Template Inventory
- play_arrow Service Provisioning: Working with Threshold Alarm Profiles
-
ON THIS PAGE
Example: Configuring Two Fiber Line Terminations Using IPLCs for Optical Amplification in a Metro Linear Packet Optical Network
For metro linear and metro ring topologies that require either north-south or east-west communications, you can connect two integrated photonic line card (IPLC) base modules together to form a single node with two fiber line terminations. This example shows how to configure the Junos OS to support the IPLC base modules in a Metro linear packet optical configuration for adding and dropping wavelengths to a local optical interface, and for bypassing wavelengths to another IPLC. You can set up and configure an IPLC node with two line-side fiber terminations.
Requirements
This example uses the following hardware and software components:
Three PTX3000 Packet Transport Routers running Junos OS Release 15.1F6
Four IPLC base modules
Compatible 10-Gigabit or 100-Gigabit Ethernet OTN PICs
For complete information on all PTX Series Packet Transport Routers hardware components, see PTX Series Packet Transport Routers.
For complete information on all PTX Series Packet Transport Routers software features, see Junos OS for PTX Series Packet Transport Routers, Release 15.1.
Before you start this procedure, complete the following tasks:
Install the IPLCs, FPCs, and PICs in the PTX3000 chassis.
Best Practice:We recommend that you place the two IPLC modules at Node B into the same FPC/PIC slot pair on the PTX3000 chassis. In this example the IPLCs at Node B are located in FPC slots 2 and 3.
Make all connections to and from the PICs in the PTX3000 chassis to the Add and Drop ports on front panel of each IPLC node as shown in Figure 1.
Connect your fiber pairs to the Line IN and Line OUT ports on the front panel of each IPLC node as shown in Figure 1.
For simplicity, Figure 1 does not show the optical ILAs between the three IPLC nodes.
On Node B, connect the two IPLC modules together using the PT IN and PT OUT ports on the front panel of the IPLC as shown in Figure 1.
Be sure to specify wavelength values on each interface as shown in Figure 1. If you must adjust the wavelength values, make sure that you enter a value supported on the IPLC.
Anytime you need to disconnect or connect the fiber span from the Line IN and Line OUT ports on the IPLC module, we recommend you disable the optical supervisory channel and the erbium-doped fiber amplifiers on the IPLC.
Always refer to the PTX3000 Packet Transport Router Hardware Guide when connecting or disconnecting cables on the IPLC modules. See PTX3000 Packet Transport Router Hardware Guide.
Overview
This examples describes how to configure Junos OS to support IPLC base modules in a Metro linear packet optical deployment. The Add/Drop ports of the IPLC modules are physically connected to interfaces housed in the same PTX3000 chassis.
The IPLC modules provide the combined functionality of a 32-port Reconfigurable Optical Add/Drop Multiplexer (ROADM), optical amplification, optical equalization, and optical channel monitoring on a single card.
Topology

This procedure describes how to configure Junos OS for the IPLC modules. This is not a complete configuration and does not include full instructions for configuring the router or the associated line cards. Before you start this procedure, complete the following hardware and software tasks on the PTX 3000 router:
Install the IPLCs, associated line cards, and PICs into the PTX3000 chassis so that the hardware configuration matches what is shown in Figure 1. If you need to make changes to the positions of the cards in the chassis, adjust the FPC numbers referenced in Figure 1 and configure them accordingly.
Best Practice:We recommend that you place the two IPLC modules at Node B into the same FPC or PIC slot pair on the PTX3000 chassis. In this example the IPLCs at Node B are located in FPC slots 2 and 3.
Configure the associated wavelengths on the interfaces of the PTX3000 by using the following procedure:
Specify the interface to configure.
content_copy zoom_out_map[edit] user@host# edit interfaces interface-name]
For example:
content_copy zoom_out_map[edit] user@host# edit interfaces et-6/0/0]
Specify the wavelength value supported on the interface.
content_copy zoom_out_map[edit interfaces et-6/0/0] user@host# set wavelength
Note:Be sure to specify wavelength values on each interface as shown in Figure 1. If you must adjust the wavelength values, make sure that you enter a value supported on the IPLC.
Make all connections to and from the PICs in the PTX3000 chassis to the ADD or DROP ports on front panel of each IPLC node as shown in Figure 1.
Connect your fiber pairs to the LINE IN and LINE OUT ports on the front panel of each IPLC node as shown in Figure 1.
For simplicity, Figure 1 does not show the optical inline amplifiers (optical ILAs) between the three IPLC nodes.
On Node B, connect the two IPLC modules together using the PT IN and PT OUT ports on the front panel of the IPLC as shown in Figure 1.
This example results in the following configuration:
Wavelength | Node A | Node B | Node C | |||
---|---|---|---|---|---|---|
Optical Interface Waveform is Switched to on PTX3000 Chassis | IPLC Slot: Port: Mode: | Optical Interface Waveform is Switched to on PTX3000 Chassis | IPLC Slot: Port: Mode: | Optical Interface Waveform is Switched to on PTX3000 Chassis | IPLC Slot: Port: Mode: | |
1554.54 | — | — | et-8/0/4 | Slot: 2 Port: 8 Mode: switch | et-10/0/2 | Slot: 8 Port: 8 Mode: switch |
1556.15 | et-12/0/3 | Slot: 1 Port: 6 Mode: switch | — | Slot: 2 Port: 6 Mode: wss-express-in(bypass) Slot: 3 Port: 6 Mode: wss-express-in (bypass) | et-10/0/3 | Slot: 8 Port: 6 Mode: switch |
1556.96 | et-12/0/2 | Slot: 1 Port: 5 Mode: switch | et-8/0/3 | Slot: 3 Port: 5 Mode: switch | — | — |
1560.20 | et-12/0/1 | Slot: 1 Port: 1 Mode: switch | et-6/0/2 | Slot: 2 Port: 1 Mode: switch Slot: 3 Port: 1 Mode: switch | et-10/0/1 | Slot: 8 Port: 1 Mode: switch |
1561.01 | et-12/0/0 | Slot: 1 Port: 0 Mode: switch | et-6/0/1 et-6/0/0 | Slot: 2 Port: 0 Mode: switch Slot: 3 Port: 0 Mode: switch | et-10/0/0 | Slot: 8 Port: 0 Mode: switch |
3x100G of Ethernet between Node A and Node B through a multi-span link.
3x100G of Ethernet between Node B and Node C through a multi-span link.
1x100G of Ethernet between Node A and Node C through a multi-span link including an optical bypass at through Node B.
In this example:
Wavelengths 1561.01 and 1560.20 are dropped at Node B and are also reused in both directions (Node A and Node C).
Other wavelengths such as wavelength 1556.96 between Node A and Node B and wavelength 1554.54 between Node B and Node C are used in only a single direction.
Wavelengths used in both directions can also be configured for optical buypass if it was necessary to reduce the packet throughput between the nodes. You can configure optical bypasses through the CLI, they do not require manual connection.
If traffic changes, you could configure Node B with 1561.01 and 1560.20 as optical bypass and that creates an additional 2x100G between Node A and Node C, leaving only 100 Gbps of traffic to Node B (and leaving four interfaces unused).
Configuration
The following example requires you to navigate various levels in the configuration hierarchy.
For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.
Before you start this procedure, be sure to complete the tasks described in the Requirementssection of this example.
To configure the IPLC base modules in this example, perform these tasks:
- CLI Quick Configuration
- Configuring the IPLC Base Module at Node A
- Configuring the Two IPLC Base Modules at Node B
- Configuring the IPLC Base Module at Node C
- Results
CLI Quick Configuration
To quickly configure this example, copy the following commands into a text file, remove any line breaks, and then paste the commands into the CLI at the [edit] hierarchy level.
set chassis fpc 1 optical-options wavelength 1556.15 switch et-12/0/3 set chassis fpc 1 optical-options wavelength 1556.96 switch et-12/0/2 set chassis fpc 1 optical-options wavelength 1560.20 switch et-12/0/1 set chassis fpc 1 optical-options wavelength 1561.01 switch et-12/0/0 set chassis fpc 2 optical-options wavelength 1554.54 switch et-8/0/4 set chassis fpc 2 optical-options wavelength 1556.15 wss-express-in set chassis fpc 2 optical-options wavelength 1560.20 switch et-6/0/2 set chassis fpc 2 optical-options wavelength 1561.01 switch et-6/0/1 set chassis fpc 2 optical-options express-in fpc 3 set chassis fpc 3 optical-options wavelength 1556.15 wss-express-in set chassis fpc 3 optical-options wavelength 1556.96 switch et-8/0/3 set chassis fpc 3 optical-options wavelength 1560.20 switch et-8/0/2 set chassis fpc 3 optical-options wavelength 1561.01 switch et-6/0/0 set chassis fpc 3 optical-options express-in fpc 2 set chassis fpc 8 optical-options wavelength 1554.54 switch et-10/0/2 set chassis fpc 8 optical-options wavelength 1556.15 switch et-10/0/3 set chassis fpc 8 optical-options wavelength 1560.20 switch et-10/0/1 set chassis fpc 8 optical-options wavelength 1561.01 switch et-10/0/0
Configuring the IPLC Base Module at Node A
Step-by-Step Procedure
This procedure describes how to configure the IPLC base module in slot 1 of Node A in this example.
Before you start this procedure, be sure to complete the tasks described in the Requirements section of this example.
To configure the IPLC base module in slot 1 of Node A:
From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed on the Tasks pane.
From the View selector, select Device View.
The functionalities that you can configure in this view are displayed.
From the Device View pane, click the plus sign (+) next to the My Network tree to expand the tree and select the PTX300 router for which you want to define the optical IPLC settings.
The network tree is expanded and the selected device is highlighted.
From the Tasks pane, select Device Management > View Physical Inventory.
An image of the device is displayed on the right pane.
Select an optical IPLC in the image of the device.
The Component Info dialog box is displayed.
Click the Status/Config tab at the bottom of the dialog box.
The IPLC Line dialog box is displayed on the right pane with the configuration settings that pertain to the IPLC.
Specify the FPC or PIC slot in which the IPLC base module resides by selecting the slot in the Chassis View.
In this case, because the IPLC base module resides in FPC slot 1, select the IPLC 1 component in the image of the chassis.
Configure wavelength 1561.01 on port 0 of the IPLC base module to be switched to optical interface et-12/0/0. In the Wavelength Configuration section, select the Show All Wavelengths check box, and beside the 1561.01 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1561.01, and then click the drop-down arrow. From the drop-down menu, select et-12/0/0 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1560.20 on port 1of the IPLC base module to be switched to optical interface et-12/0/1. In the Wavelength Configuration section, beside the 1560.20 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1560.20, and then click the drop-down arrow. From the drop-down menu, select et-12/0/1 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.96 on port 5 of the IPLC base module to be switched to optical interface et-12/0/2. In the Wavelength Configuration section, beside the 1556.96 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1556.96, and then click the drop-down arrow. From the drop-down menu, select et-12/0/2 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.15 on port 6 of the IPLC base module to be switched to optical interface et-12/0/3. In the Wavelength Configuration section, beside the 1556.15 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1556.15, and then click the drop-down arrow. From the drop-down menu, select et-12/0/3 to which you want the wavelength of the IPLC base module to be switched.
Click Update to save the specified configuration settings.
Configuring the Two IPLC Base Modules at Node B
Step-by-Step Procedure
This procedure describes how to configure the IPLC base module in slot 2 of Node B in this example.
Before you start this procedure, be sure to complete the tasks described in the Requirements section of this example.
We recommend that you place the two IPLC modules in the same FPC or PIC slot pair on the PTX3000 chassis.
To configure the IPLC base module in slot 2 of Node B:
From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed on the Tasks pane.
From the View selector, select Device View.
The functionalities that you can configure in this view are displayed.
From the Device View pane, click the plus sign (+) next to the My Network tree to expand the tree and select the PTX300 router for which you want to define the optical IPLC settings.
The network tree is expanded and the selected device is highlighted.
From the Tasks pane, select Device Management > View Physical Inventory.
An image of the device is displayed on the right pane.
Select an optical IPLC in the image of the device.
The Component Info dialog box is displayed.
Click the Status/Config tab at the bottom of the dialog box.
The IPLC Line dialog box is displayed on the right pane with the configuration settings that pertain to the IPLC.
Specify the FPC or PIC slot in which the IPLC base module resides by selecting the slot in the Chassis View.
In this case, because the IPLC base module resides in FPC slot 2, select the IPLC 2 component in the image of the chassis.
Create a logical connection between this IPLC base module and the IPLC base module in slot 3. Select FPC 3 from the Express IPLC list in the Settings/Status section.
Configure wavelength 1561.01 on port 0 of the IPLC base module to be switched to optical interface et-6/0/1. In the Wavelength Configuration section, select the Show All Wavelengths check box, and beside the 1561.01 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1561.01, and then click the drop-down arrow. From the drop-down menu, select et-6/0/1 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1560.20 on port 1of the IPLC base module to be switched to optical interface et-6/0/2. In the Wavelength Configuration section, beside the 1560.20 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1560.20, and then click the drop-down arrow. From the drop-down menu, select et-6/0/2 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1554.54 on port 5 of the IPLC base module to be switched to optical interface et-8/0/4. In the Wavelength Configuration section, beside the 1556.54 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1554.54, and then click the drop-down arrow. From the drop-down menu, select et-8/0/4 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.15 on port 6 of the IPLC base module in slot 2 to be bypassed. In the Wavelength Configuration section, beside the 1556.15 row in the wavelength column, select express from the drop-down menu in the configuration column of the table for the corresponding wavelength.
Click Update to save the specified configuration settings.
Step-by-Step Procedure
This procedure describes how to configure the IPLC base module in slot 3 of Node B in this example.
Before you start this procedure, be sure to complete the tasks described in the Requirements section of this example.
To configure the IPLC base module in slot 3 of Node B:
From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed on the Tasks pane.
From the View selector, select Device View.
The functionalities that you can configure in this view are displayed.
From the Device View pane, click the plus sign (+) next to the My Network tree to expand the tree and select the PTX300 router for which you want to define the optical IPLC settings.
The network tree is expanded and the selected device is highlighted.
From the Tasks pane, select Device Management > View Physical Inventory.
An image of the device is displayed on the right pane.
Select an optical IPLC in the image of the device.
The Component Info dialog box is displayed.
Click the Status/Config tab at the bottom of the dialog box.
The IPLC Line dialog box is displayed on the right pane with the configuration settings that pertain to the IPLC.
Specify the FPC or PIC slot in which the IPLC base module resides by selecting the slot in the Chassis View.
In this case, because the IPLC base module resides in FPC slot 3, select the IPLC 3 component in the image of the chassis.
Create a logical connection between this IPLC base module and the IPLC base module in slot 2. Select FPC 2 from the Express IPLC list in the Settings/Status section.
Configure wavelength 1561.01 on port 0 of the IPLC base module to be switched to optical interface et-6/0/0. In the Wavelength Configuration section, select the Show All Wavelengths check box, and beside the 1561.01 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1561.01, and then click the drop-down arrow. From the drop-down menu, select et-6/0/0 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1560.20 on port 0 of the IPLC base module to be switched to optical interface et-8/0/2. In the Wavelength Configuration section, beside the 1560.20 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1561.01, and then click the drop-down arrow. From the drop-down menu, select et-8/0/2 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.96 on port 5 of the IPLC base module to be switched to optical interface et-8/0/3. In the Wavelength Configuration section, beside the 1560.20 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1556.96, and then click the drop-down arrow. From the drop-down menu, select et-8/0/3 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.15 on port 6 of the IPLC base module in slot 3 to be bypassed. In the Wavelength Configuration section, select the Show All Wavelengths check box, and beside the 1560.20 row in the wavelength column, select express from the drop-down menu in the configuration column of the table for the corresponding wavelength.
Click Update to save the configured settings.
Configuring the IPLC Base Module at Node C
Step-by-Step Procedure
This procedure describes how to configure the IPLC base module in slot 8 of Node C in this example.
Before you start this procedure, be sure to complete the tasks described in the Requirements section of this example.
Step-by-Step Procedure
To configure the IPLC base module in slot 8 of Node C:
From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed on the Tasks pane.
From the View selector, select Device View.
The functionalities that you can configure in this view are displayed.
From the Device View pane, click the plus sign (+) next to the My Network tree to expand the tree and select the PTX300 router for which you want to define the optical IPLC settings.
The network tree is expanded and the selected device is highlighted.
From the Tasks pane, select Device Management > View Physical Inventory.
An image of the device is displayed on the right pane.
Select an optical IPLC in the image of the device.
The Component Info dialog box is displayed.
Click the Status/Config tab at the bottom of the dialog box.
The IPLC Line dialog box is displayed on the right pane with the configuration settings that pertain to the IPLC.
Specify the FPC or PIC slot in which the IPLC base module resides by selecting the slot in the Chassis View.
In this case, because the IPLC base module resides in FPC slot 8, select the IPLC 8 component in the image of the chassis.
Configure wavelength 1561.01 on port 0 of the IPLC base module to be switched to optical interface et-10/0/0. In the Wavelength Configuration section, select the Show All Wavelengths check box, and beside the 1561.01 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1561.01, and then click the drop-down arrow. From the drop-down menu, select et-10/0/0 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1560.20 on port 1 of the IPLC base module to be switched to optical interface et-10/0/1. In the Wavelength Configuration section, beside the 1560.20 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1560.20, and then click the drop-down arrow. From the drop-down menu, select et-10/0/1 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1554.54 on port 8 of the IPLC base module to be switched to optical interface et-10/0/2. In the Wavelength Configuration section, beside the 1554.54 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1554.54, and then click the drop-down arrow. From the drop-down menu, select et-10/0/2 to which you want the wavelength of the IPLC base module to be switched.
Configure wavelength 1556.15 on port 6 of the IPLC base module to be switched to optical interface et-10/0/3. In the Wavelength Configuration section, beside the 1556.15 row in the wavelength column, select switch from the drop-down menu in the configuration column of the table for the corresponding wavelength.
From the end-point column, click in the cell corresponding to the wavelength of 1556.15, and then click the drop-down arrow. From the drop-down menu, select et-10/0/3 to which you want the wavelength of the IPLC base module to be switched.
Click Update to save the configured settings.
Results
Verification
Confirm that the configuration is working properly.
Verifying the Topology of Each IPLC Node
Purpose
Verify the topology of each IPLC node.
Action
Run the show chassis fpc optical-properties topology
command with the detail
output level at each IPLC node
and verify that the following fields match the values listed in Table 1.
Port/Wavelength
—Verify that this field lists the proper wavelength values and IPLC port numbers for each node in this example.State
—Verify that the values for this field match what is listed in Table 1 for the mode value of each IPLC port for each node in this example.Connected To
—If the wavelength is being switched, verify that this field lists the correct interface the wavelength is being switched to.
Verify the topology of each IPLC node.
For example, at IPLC Node A, enter the following.
content_copy zoom_out_mapuser@host>show chassis fpc optical-properties topology detail fpc-slot 1
content_copy zoom_out_mapIPLC Topology Information Wavelength(nm) / Port / Frequency(THz) State Connected To Express-in Port DOWN NA Expansion Port DOWN NA 1561.01 0 192.05 Switched et-12/0/0 1560.20 1 192.15 Switched et-12/0/1 1559.39 2 192.25 Blocked NA 1558.58 3 192.35 Blocked NA 1557.77 4 192.45 Blocked NA 1556.96 5 192.55 Switched et-12/0/2 1556.15 6 192.65 Switched et-12/0/3 1555.34 7 192.75 Blocked NA 1554.54 8 192.85 Blocked NA 1553.73 9 192.95 Blocked NA 1552.93 10 193.05 Blocked NA 1552.12 11 193.15 Blocked NA 1551.32 12 193.25 Blocked NA 1550.52 13 193.35 Blocked NA 1549.72 14 193.45 Blocked NA 1548.91 15 193.55 Blocked NA 1548.11 16 193.65 Blocked NA 1547.32 17 193.75 Blocked NA 1546.52 18 193.85 Blocked NA 1545.72 19 193.95 Blocked NA 1544.92 20 194.05 Blocked NA 1544.13 21 194.15 Blocked NA 1543.33 22 194.25 Blocked NA 1542.54 23 194.35 Blocked NA 1541.75 24 194.45 Blocked NA 1540.95 25 194.55 Blocked NA 1540.16 26 194.65 Blocked NA 1539.37 27 194.75 Blocked NA 1538.58 28 194.85 Blocked NA 1537.79 29 194.95 Blocked NA 1537.00 30 195.05 Blocked NA 1536.22 31 195.15 Blocked NA
At Node B, enter the following:
content_copy zoom_out_mapuser@host> show chassis fpc optical-properties topology detail fpc-slot 2 user@host> show chassis fpc optical-properties topology detail fpc-slot 3
At Node C:
content_copy zoom_out_mapuser@host> show chassis fpc optical-properties topology detail fpc-slot 8
Meaning
For example, in Step 1for Node A, you can see that the IPLC module in slot 1 includes the following configuration:
Wavelength 1561.01 is switched to optical interface et-12/0/0
Wavelength 1560.20 is switched to optical interface et-12/0/1
Wavelength 1556.96 is switched to optical interface et-12/0/2
Wavelength 1556.16 is switched to optical interface et-12/0/3
This matches what is listed in Table 1 for Node A and confirms the configuration is operating correctly.