- 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 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 Managing Optical Interfaces, OTUs, ODUs, ILAs, and IPLCs on MX Series and PTX Series Routers
- play_arrow Overview of Optical Interfaces, OTUs, and ODUs
- Optical Interfaces Management and Monitoring on MX Series and PTX Series Routers Overview
- Ethernet DWDM Interface Wavelength Overview
- Attenuation and Dispersion in a Fiber-Optic Cable on PTX Series Routers Overview
- Understanding Pre-FEC BER Monitoring and BER Thresholds
- DWDM Controllers Overview
- PTX5000 PIC Description
- PTX3000 PIC Description
- 100-Gigabit Ethernet OTN Optical Interface Specifications
- 100-Gigabit DWDM OTN PIC Optical Interface Specifications
- 100-Gigabit DWDM OTN PIC (PTX Series)
- 100-Gigabit Ethernet OTN PIC with CFP2 (PTX Series)
- 100-Gigabit Ethernet PIC with CFP2 (PTX Series)
- 100-Gigabit Ethernet PIC with CFP (PTX Series)
- 100GbE PICs for PTX Series Routers
- P2-10G-40G-QSFPP PIC Overview
- Understanding the P2-100GE-OTN PIC
- 100-Gigabit DWDM OTN PIC with CFP2 (PTX Series)
- 100-Gigabit DWDM OTN MIC with CFP2
- 100-Gigabit Ethernet OTN Options Configuration Overview
- Configuring the 10-Gigabit or 100-Gigabit Ethernet DWDM Interface Wavelength
- play_arrow Overview of Optical ILAs and IPLCs
- Optical ILA Hardware Component Overview
- Optical ILA Cooling System Description
- Optical ILA AC Power Supply Description
- Optical ILA DC Power Supply Description
- Optical ILA Chassis Status LEDs
- Optical ILA Component Redundancy
- Optical ILA Field-Replaceable Units
- Optical ILA Management Panel
- Optical ILA Management Port LEDs
- Optical Inline Amplifier Description
- Optical ILA Power Supply LEDs
- PTX3000 IPLC Description
- IPLC Architecture and Functional Components Overview
- Understanding IPLC Base and Expansion Modules
- Understanding the IPLC Configuration
- PTX3000 IPLC LED
- Communication of SNMP Traps Between Optical ILA and NMS Systems
- Communication of SNMPv2 and SNMPv3 Commands over OSC Between an Optical ILA and NMS
- Overview of Configuring and Managing Optical ILAs from Connectivity Services Director Using DMI
- IPLC Specifications
- Understanding the Performance Monitors and TCAs for IPLCs
- play_arrow Configuring and Monitoring Optical Interfaces, OTUs, and ODUs
- Viewing a Graphical Image of the Optical Interface Components
- Configuring and Managing OTN Port Details of MX Series and PTX Series Routers for Easy Administration
- Configuring and Managing OTU Details of MX Series and PTX Series Routers for Simplified Management
- Configuring and Managing ODU Details of MX Series and PTX Series Routers for Simplified Management
- Configuring and Managing Optical PIC Details for Effective Provisioning
- Configuring Threshold-Crossing Alarms for OTN Ports for Monitoring Link Performance
- Configuring Threshold-Crossing Alarms for OTUs for Monitoring Link Performance
- Configuring Threshold-Crossing Alarms for ODUs for Monitoring Link Performance
- Viewing Performance Monitoring Details of OTN Ports for Detecting and Diagnosing Faults
- Viewing Performance Monitoring Details of OTUs for Detecting and Diagnosing Faults
- Viewing Performance Monitoring Details of ODUs for Detecting and Diagnosing Faults
- Viewing a Graphical Image of the Chassis of PTX Series Routers
- Diagnosing, Examining, and Correcting Optical Interface Problems
- Changing Alarm Settings for the Optics and OTN Interfaces
- play_arrow Configuring and Monitoring Optical Inline Amplifiers
- Viewing a Graphical Image of Optical Inline Amplifier
- Viewing Optical ILA Configuration and Status Details for Simplified Administration
- Viewing Performance Monitoring Details of Optical ILAs for Detecting and Diagnosing Faults
- Configuring Threshold-Crossing Alarms for Optical ILAs for Monitoring Link Performance
- Changing Alarm Settings for the Optical ILAs
- play_arrow Configuring and Monitoring Optical Integrated Photonic Line Cards
- Viewing a Graphical Image of the Optical Integrated Photonic Line Card
- Configuring Optical IPLC for Easy and Optimal Deployment
- Viewing Performance Monitoring Details of Optical IPLCs for Detecting and Diagnosing Faults
- Configuring Threshold-Crossing Alarms for Optical IPLCs for Monitoring Link Performance
- Increasing the Add and Drop Port Capacity of the IPLC Node to 64 Channels
- Configuring a Two-Degree IPLC Node for Express Traffic by Increasing the Line Capacity
- Configuring Optical IPLC Line Connectivity for Interoperation with Optical ILAs
- Configuring the Wavelengths That Are Added and Dropped by the IPLC
- Configuring the IPLC to Add or Drop Wavelengths to an Optical Interface on a Remote Chassis
- Configuring the IPLC to Add or Drop Wavelengths to an Optical Interface on the Same Chassis
- Bypassing a Wavelength on the IPLC
- Changing Alarm Settings for the Optical IPLCs
- Viewing Routing Engine Switchover Indicators in the Chassis Image
- Viewing Alarm Indicators in the Chassis Image
- Viewing Port Statistics for OTN PICs
- Example: Configuring Two Fiber Line Terminations Using IPLCs for Optical Amplification in a Metro Linear Packet Optical Network
-
- 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
Specifying General Information for Multipoint-to-Multipoint E-LAN Service Definitions
Specifying Site Settings for Multipoint-to-Multipoint E-LAN Service Definitions
UNI or Site Settings for Port-to-Port Interfaces in E-LAN Services
UNI or Site Settings for 802.1Q Interfaces in E-LAN Services
UNI or Site Settings for Q-in-Q Interfaces in E-LAN Services
UNI Settings for Services with Flexible VLAN Tagging (Asymmetric Interface Types)
Creating a Multipoint-to-Multipoint E-LAN Service Definition
This procedure provides the steps to create a definition for a multipoint-to-multipoint E-LAN service.
The standard service definitions that came with your initial software installation are designed to be appropriate for most requirements. You can also create a customized service definition—for example, to set different bandwidth limits on the service than those offered in the standard service definitions.
When the new service definition is complete and published, network operators or service provisioners can use the completed service definition as a base for creating and then activating multipoint-to-multipoint Ethernet services on the network.
The windows appear in the order stated. You can, however, perform these steps in any order by accessing them through the task list in the right panel. If the panel is not visible, click the snap tool on the right side of the main display area.
To create a multipoint-to-multipoint Ethernet service definition, complete these tasks, in the order shown. As you finish a section and click Next, the attributes from the current window are saved and the next window in the sequence appears.
Specifying General Information for Multipoint-to-Multipoint E-LAN Service Definitions
To specify the general information for a multipoint-to-multipoint service definition, in the Network Services > Connectivity view pane, select Service Design > Manage Service Definitions > New > E-LAN Service Definition.
The General window appears.
To specify the general information for a multipoint-to-multipoint service definition:
Fill in the fields on the General window.
Field
Action
Service Definition Name
Type a name for the service definition.
Service Type
Select (E-LAN) Multipoint-to-Multipoint
Instance Type
Select an instance type to choose the type of routing instance for the MultiPoint-to-MultiPoint E-LAN service:
vpls
evpn
virtual-switch
Note:Virtual-switch supports only dot1q as the encapsulation type.
Normalization not required is the only available vlan normalization type.
Protocol
Select the protocol type:
vpls
evpn
evpn e-tree
Note:Different protocols are available based on the instance type you select.
Signaling Protocol
Select a signaling type:
BGP— If BGP signaling is selected, the following fields are available in the Connectivity section of the General Settings page:
Auto-pick Route Target
Auto-pick Route Distinguisher
LDP—If LDP signaling is selected, the following fields are available in the Connectivity section of the General Settings page:
Enable BGP-based Auto Discovery
Auto-pick Route Target, if Auto Discovery is enabled
Auto-pick Route Distinguisher , if Auto Discovery is enabled
Auto-pick VPLS ID, if Auto Discovery is disabled
Auto-pick VPN ID, if Auto Discovery is enabled
Note:You cannot edit the Signaling type in the service order.
Description (Optional)
Type a brief description or other comment that you want to appear in the Service Definition table.
Range: 0 through 200 characters. Space and special characters are allowed.
Enable QoS
When you enable QoS in the service definition, you can specify a QoS profile in the service order to classify traffic into defined service groups to provide the special treatment of traffic across the network service. For example, voice traffic can be sent across certain links, and data traffic can use other links.
Enable L3 Access
Select this check box to create the link into Layer 3. If this check box is selected, the available Ethernet option in the Site Settings window are:
dot1q
qinq
Enable Static PW Labels
Select this check box to enable a pseudowire connection by configuring static values.
Note:The Enable Static PW Labels check box is enabled only when the signaling type is LDP.
Service Template
(Optional) To include a service template for the service, click the Add icon or plus sign (+) to select a service template from the Service Template list. The list of available service templates is displayed. Select the check box beside the template you want and click OK. You are returned to the General Settings page.
The selected service template appears in the Default Service Template field.
You can select one or more service templates as the default service template. By default, the default service templates are attached to the endpoints.
Note:You cannot add or delete a service template while creating a service order.
The remaining service templates on the Service Template list are termed as optional service templates. You can attach the optional service templates to the endpoints on a need basis.
In the View Service Definition Details window, the value for the default service template in the Default Service Template column is True.
For instructions on creating a service template, see Creating a Service Template.
BGP Connectivity Settings—This section is displayed if you select the signaling type as BGP.
Auto-pick Route Target
Select this check box to enable route target to be configued automatically. Clear the check box if you want the route target to be manually configured. By default, manual configuration of route target is enabled.
To override this setting in the service order, select the Editable in Service Order check box.
Auto-pick Route Distinguisher
Define a route distinguisher option:
Select the check box to enable the service provider to specify the route distinguisher.
Select the check box to enable the route distinguisher to be selected automatically.
To override this setting in the service order, select the Editable in Service Order check box.
Enable Multihoming
(Optional) Select this check box to pair any two N-PE devices, for providing redundant connectivity.
When you select this check box, a Multihoming Mode list appears, if you select evpn or evpn e-tree as the protocol type. You can select either single-active or all-active as the multihoming mode.
LDP Connectivity Settings—This section is displayed if you select the signaling type as LDP.
Enable BGP-based Auto Discovery
The Auto Discovery check box is available only if the signaling type is LDP.
Note:If the Enable Static PW Labels check box in the General window is selected for LDP signaling, then the Auto Discovery check box is disabled.
The Auto Discovery check box is not available when the signaling type is BGP.
On disabling the auto discovery specify the VPLS ID.
Auto-pick VPLS ID or VPN ID
This field is available only if the signaling type is LDP and auto discovery is disabled.
Identifies the virtual circuit identifier used for the VPLS routing instance and the VPN ID associated with the router.
Select this check box to enable the VPLS ID and VPN ID to be configued automatically. Clear the check box if you want these attributes to be manually configured. By default, manual configuration is enabled.
Auto-pick Route Target
Select this check box to enable route target to be configued automatically. Clear the check box if you want the route target to be manually configured. By default, manual configuration of route target is enabled.
Auto-pick Route Distinguisher
Define a route distinguisher option:
Select the check box to enable the service provider to specify the route distinguisher.
Select the check box to enable the route distinguisher to be selected automatically.
To override this setting in the service order, select the Editable in Service Order check box.
MAC Settings
MAC learning
To enable MAC learning, select the check box.
Interface MAC limit
Maximum number of MAC addresses learned from an interface.
Range: 1 through 131071 MAC addresses per interface
MAC statistics
To enable MAC statistic, select the check box.
MAC Table Size
Modify the size of the MAC address table for the bridge domain.
Range: 16 through 1048575
To allow the service provisioner to override the MAC settings, select Editable in Service Order.
Click Next to save the information and continue with UNI or site settings.
Specifying Advanced Settings
In this step, you can specify the parameters that define advanced connectivity between sites across the service provider network. Thes settings can be configured in the Advanced settings section of the General Settings page of the Create E-LAN Service Definition wizard.
To specify advanced settings:
Specifying Site Settings for Multipoint-to-Multipoint E-LAN Service Definitions
In this step, you provide the UNI attributes for this service definition. The attributes you set depend on the type of interface you are using in this E-LAN service definition. The following interface types are supported:
ports
802.1Q interfaces
Q-in-Q interfaces
asymmetric interface
UNI or Site Settings for Port-to-Port Interfaces in E-LAN Services
The Site Settings window provides four expanding or collapsing panels: Traffic Treatment, Interface Settings, MTU Settings, and Bandwidth Settings.
To specify the UNI Settings for Port-to-Port interfaces:
Fill in the fields on the Site Settings window.
Field
Action
PE-CE Interface Settings- Ethernet Encapsulation
VLAN Tagging
Select port-port from the list.
The VLAN tagging option you choose determines the other options you can select and specify on the page.
Editable in Service Order
To allow the service provisioner to override the VLAN tagging or Ethernet option attribute, select the check box.
Physical Interface Encapsulation
Select ethernet-vpls, the only valid physical interface encapsulation method allowed for port-to-port services.
Logical Interface Encapsulation
You cannot select a choice in this field because it is not relevant to port-to-port services.
Traffic Type
This drop-down is disabled for port-to-port services. For port-to-port services, all traffic is always transported.
VLAN Normalization
Select a value:
Normalize to VLAN all—To preserve customer VLAN IDs (and customer QoS priorities) across the network.
Note:For services that transport a range of VLANs, you must select VLAN Normalization to all. You cannot transport a range of VLANs without normalization.
Normalize to VLAN none—To preserve no VLAN IDs across the network.
Normalized to Dot1q tag—To transport only single-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network
Normalized to QinQ tags—To transport only double-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network.
Normalization not required—To specify no normalization for port-to-port services
Note:Starting with Release 1.0R2, when you newly install Connectivity Services Director, if you select the option to not require normalization in a service definition, the auto-pick option for VLAN IDs and the option to edit the auto-pick behavior in service order are disabled in the service definition. When you create a service order by associating with that service definition, you need to manually enter the VLAN IDs for the interfaces and cannot use the auto-pick functionality. This same behavior also applies to default service templates in which if you select the normalization-not-required functionality, the auto-pick option for VLAN IDs is disabled.
For more information about VLAN normalization, see Junos Space Layer 2 Services Overview.
For information about VLAN manipulation, see Understanding VLAN Manipulation (Normalization and VLAN Mapping) on Ethernet Services.
Auto Pick VLAN ID
This check box is disabled because in port-to-port services, all traffic and all VLANs on one port are transported to all other ports.
Editable in Service Order
To allow the service provisioner to override the VLAN ID setting, select the check box. This check box is not applicable for port-to-port services.
Default Interface MTU (Bytes)
The default MTU value is 1522 bytes.
MTU Range for manual-config(Bytes)
Specify the low and high values to define the MTU range that you want to define.
The default range is 1522 through 9192 bytes.
PE-CE Interface Rate-Limiting Settings
Enable Interface Rate Limiting
To enable a service provisioner to limit the available bandwidth, select this check box, and type a default bandwidth limit.
Note:Bandwidth settings are available in the service definition when CoS profiles are associated.
Default bandwidth (Mbps)
Specify the default bandwidth value in Mbps.
Default: 10 Mbps
Range: 1 Mbps through 100,000 Mbps
Min Bandwidth (Kbps)
Specify the minimum bandwidth value in Kbps.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Max Bandwidth (Mbps)
Specify the maximum bandwidth value in Mbps. For more information on maximum bandwidth see Table 1
Default: 100 Mbps
Range: 1 Mbps through 100,000 Mbps
Increment (Kbps)
Specify a value that defines which values in the range is made available to the service provisioner.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Bandwidth – Burst Size Settings
Burst Size Calculator
Select the preferred option for calculating the burst size:
MTU Based
If you select the option MTU Based, you can specify a value for MTU Factor in the range 1 through 1087902.
The default value for MTU Factor is 10.
Burst Period Based
If you select the option Burst Period Based, you can specify a value for Burst Period in the range 1 through 7450 milliseconds.
The default value for Burst Period is 1.
Note:The Burst Size Calculator list is enabled only when you select the Enable Interface Rate Limiting check box.
The following table lists the Max Bandwidth (Mbps) for the M Series, MX Series, and ACX Series Routers:
Table 1: Maximum Bandwidth for M Series, MX Series, and ACX Series Routers M Series IQ2E PIC
M Series IQ2 PIC
MX Series 3D PIC
MX Series Non-3D PIC
ACX 2000
GE Port (1G)
XE Port (10G)
GE Port (1G)
XE Port (10G)
GE Port (1G)
XE Port (10G)
GE Port (1G)
XE Port (10G)
GE Port (1G)
XE Port (10G)
32,000 Mbps or 32 Gbps
32,000 Mbps or 32 Gbps
50,000 Kbps or 50 Gbps
50,000 Kbps or 50 Gbps
100,000 Mbps or 100 Gbps
100,000 Mbps or 100 Gbps
50,000 Kbps or 50 Gbps
50,000 Kbps or 50 Gbps
50,000 Kbps or 50 Gbps
50,000 Kbps or 50 Gbps
Click Review to view the defined parameters. You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify. Click Back to return to the previous page of the wizard; else click Cancel to discard the changes.
After you complete reviewing the settings, click Finish to complete the service definition creation.
UNI or Site Settings for 802.1Q Interfaces in E-LAN Services
To specify the UNI Settings for 802.1Q interfaces:
Fill in the fields on the Site Settings window.
Field
Action
PE-CE UNI Settings- Ethernet Encapsulation
VLAN Tagging
Select dot1q from the list.
The Ethernet option you choose determines the other options you can select and specify on the page.
Physical Interface Encapsulation
Select the default physical encapsulation scheme to be used by service orders based on this service definition. We recommend you select flexible-ethernet-services.
Logical Interface Encapsulation
Constrained by your selection in the Physical interface encapsulation box. If you selected the recommended physical encapsulation mode of flexible-ethernet-services, then your only option is to select vlan-vpls for the logical encapsulation method.
Traffic Type
Select Transport single vlan to transport the traffic for a specific VLAN across the network. When you select this option, the service provisioner is prompted for the VLAN-ID when creating a service order based on this service definition. You need to specify the Outer Tag protocol ID.
Select Transport vlan range to limit the traffic across the network to a specific range of VLANs.
If you select this option, the service provisioner is prompted for the VLAN-ID range when creating a service order based on this service definition.
Select Transport vlan list to limit the traffic across the network to a specific list of VLANs.
If you select this option, the service provisioner is prompted for the VLAN-ID list when creating a service order based on this service definition.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
VLAN Normalization
Select a value:
Normalize to VLAN all—To preserve customer VLAN IDs (and customer QoS priorities) across the network.
Note:For services that transport a range of VLANs, you must select VLAN Normalization to all. You cannot transport a range of VLANs without normalization.
Normalized VLAN none—To preserve no VLAN IDs across the network.
Normalized to Dot1q—To transport only single-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network
Normalized to QinQ—To transport only double-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network.
Normalization not required—To specify no normalization for port-to-port services
Note:Starting with Release 1.0R2, when you newly install Connectivity Services Director, if you select the option to not require normalization in a service definition, the auto-pick option for VLAN IDs and the option to edit the auto-pick behavior in service order are disabled in the service definition. When you create a service order by associating with that service definition, you need to manually enter the VLAN IDs for the interfaces and cannot use the auto-pick functionality. This same behavior also applies to default service templates in which if you select the normalization-not-required functionality, the auto-pick option for VLAN IDs is disabled.
For more information about VLAN normalization, see Junos Space Layer 2 Services Overview.
For information about VLAN manipulation, see Understanding VLAN Manipulation (Normalization and VLAN Mapping) on Ethernet Services.
Auto Pick VLAN ID
Indicate how the VLAN ID is determined. By default, this check box is disabled.
Clear this check box to allow the service provider to specify the VLAN ID. This option is normally used when no VLAN normalization is applied. Specify the VLAN ID range in VLAN range for manual input.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Select this check box when VLAN normalization is applied. Specify the VLAN ID pool in VLAN range for auto-pick.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Note:When the range of VLAN IDs that are automatically assigned by the system (with the auto-pick option enabled during the creation of a service definition) is less than or greater than the range of VLAN IDs that are manually specified (with the manual selection option enabled during the creation of a service definition), the following conditions apply during the creation of a service order with the Editable in Service Order check box selected during service definition creation:
If you create a service order with the auto-pick option enabled, the VLAN ID is selected from the auto-pick range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
If you create a service order with the auto-pick option disabled, the VLAN ID is selected from the manually configured range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
VLAN range for auto-pick
Specify the VLAN ID pool.
Range: 1 through 4094
VLAN range for manual input
Specify the VLAN ID range.
Range: 1 through 4094
Outer Tag Protocol ID
Select the outer tag protocol ID if the Customer traffic type is Transport single VLAN:
0x88a8
0x8100
0x9100
Note:For an interface, you must configure a physical port with the possible Tag Protocol Identifiers (TPID) either manually or through a template. Otherwise, the service creation fails for all TPIDs except 0x8100. To configure the TPIDs manually, use the following commands:
Editable in Service Order
To allow the service provisioner to override the outer tag protocol ID setting, select the check box for those options.
Default Interface MTU (Bytes)
The default MTU value is 1522 bytes. To allow the service provisioner to override the MTU setting, select the Editable in Service Order check box.
MTU range for manual-config
In the MTU range fields, type the lowest and highest values for MTU for each UNI.
Note:To allow the service provisioner to override the MTU setting, select Editable in Service Order and, in the MTU range fields, type the highest and lowest MTU values.
PE-CE Interface Rate-Limiting Settings
Enable Interface Rate Limiting
To enable a service provisioner to limit the available bandwidth, select this check box, and type a default bandwidth limit.
Note:Bandwidth settings are available in the service definition when Manage CoS Profiles page is configured with CoS profiles.
Default bandwidth (Mbps)
Specify the default bandwidth value in Mbps.
Default: 10 Mbps
Range: 1 Mbps through 100,000 Mbps
Min Bandwidth (Kbps)
Specify the minimum bandwidth value in Kbps.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Max Bandwidth (Mbps)
Specify the maximum bandwidth value in Mbps. For more information on maximum bandwidth see Table 1
Default: 100 Mbps
Range: 1 Mbps through 100,000 Mbps
Increment (Kbps)
Specify a value that defines which values in the range is made available to the service provisioner.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Bandwidth – Burst Size Settings
Burst Size Calculator
Select the preferred option for calculating the burst size:
MTU Based
If you select the option MTU Based, you can specify a value for MTU Factor in the range 1 through 1087902.
The default value for MTU Factor is 10.
Burst Period Based
If you select the option Burst Period Based, you can specify a value for Burst Period in the range 1 through 7450 milliseconds.
The default value for Burst Period is 1.
Note:The Burst Size Calculator list is enabled only when you select the Enable Interface Rate Limiting check box.
Click Review to view the defined parameters. You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify. Click Back to return to the previous page of the wizard; else click Cancel to discard the changes.
After you complete reviewing the settings, click Finish to complete the service definition creation.
UNI or Site Settings for Q-in-Q Interfaces in E-LAN Services
To specify the site or UNI settings for q-in-q interfaces:
Fill in the fields on the Site Settings window.
Field
Action
PE-CE Interface Settings- Ethernet Encapsulation
VLAN Tagging
Select qinq from the list.
The window expands to include options specific to Q-in-Q interfaces.
Physical Interface Encapsulation
Select the default physical encapsulation scheme to be used by service orders based on this service definition. We recommend you select flexible-ethernet-services.
Logical Interface Encapsulation
Constrained by your selection in the Physical Interface encapsulation box. If you selected the recommended physical encapsulation mode of flexible-ethernet-services, then your only option is to select vlan-vpls for the logical encapsulation method.
Traffic Type
Transport all traffic Transports the traffic from all VLANs across the network. When you select this option, the service provisioner is prompted for the VLAN-ID when creating a service order based on this service definition. You need to specify only the Outer Tag protocol ID.
Transport single vlan Transports traffic for a specific VLAN across the network. You need to specify both Outer Tag protocol ID and Inner Tag protocol ID.
Transport vlan range Limits the traffic across the network to a specific range of VLANs.
If you select this option, the service provisioner is prompted for the VLAN-ID range when creating a service order based on this service definition. You need to specify only the Outer Tag protocol ID .
Transport vlan list Limits the traffic across the network to a specific list of VLANs. If you select this option, the service provisioner is prompted for the VLAN-ID list when creating a service order based on this service definition. You need to specify only the Outer Tag protocol ID.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
VLAN Normalization
Select a value:
Normalize to VLAN all—To preserve customer VLAN IDs (and customer QoS priorities) across the network.
Note:For services that transport a range of VLANs, you must select VLAN Normalization to all. You cannot transport a range of VLANs without normalization.
Normalized VLAN none—To preserve no VLAN IDs across the network.
Normalized to Dot1q—To transport only single-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network
Normalized to QinQ—To transport only double-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network.
Normalization not required—To specify no normalization for port-to-port services
Note:Starting with Release 1.0R2, when you newly install Connectivity Services Director, if you select the option to not require normalization in a service definition, the auto-pick option for VLAN IDs and the option to edit the auto-pick behavior in service order are disabled in the service definition. When you create a service order by associating with that service definition, you need to manually enter the VLAN IDs for the interfaces and cannot use the auto-pick functionality. This same behavior also applies to default service templates in which if you select the normalization-not-required functionality, the auto-pick option for VLAN IDs is disabled.
For more information about VLAN normalization, see Junos Space Layer 2 Services Overview.
For information about VLAN manipulation, see Understanding VLAN Manipulation (Normalization and VLAN Mapping) on Ethernet Services.
Auto Pick VLAN ID
Indicate how the VLAN ID is determined. By default, this check box is disabled.
Clear this check box to allow the service provider to specify the VLAN ID. This option is normally used when no VLAN normalization is applied. Specify the VLAN ID range in VLAN range for manual input.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Select this check box when VLAN normalization is applied. Specify the VLAN ID pool in VLAN range for auto-pick.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Note:When the range of VLAN IDs that are automatically assigned by the system (with the auto-pick option enabled during the creation of a service definition) is less than or greater than the range of VLAN IDs that are manually specified (with the manual selection option enabled during the creation of a service definition), the following conditions apply during the creation of a service order with the Editable in Service Order check box selected during service definition creation:
If you create a service order with the auto-pick option enabled, the VLAN ID is selected from the auto-pick range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
If you create a service order with the auto-pick option disabled, the VLAN ID is selected from the manually configured range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
VLAN range for auto-pick:
Specify the VLAN ID pool.
Range: 1 through 4094
VLAN range for manual input
Specify the VLAN ID range.
Range: 1 through 4094
Outer Tag Protocol ID
Select the outer tag protocol ID if the Customer traffic type is Transport single VLAN:
0x88a8
0x8100
0x9100
Note:For an interface, you must configure a physical port with the possible Tag Protocol Identifiers (TPID) either manually or through a template. Otherwise, the service creation fails for all TPIDs except 0x8100. To configure the TPIDs manually, use the following commands:
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x9100
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x88a8
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x8100
Inner Tag Protocol ID
Select the inner tag protocol ID:
0x88a8
0x8100
0x9100
Note:You cannot specify the Inner Tag protocol ID if the Customer traffic type is Transport single VLAN.
Editable in Service Order
To allow the service provisioner to override the outer and inner tag protocol IDs, select the check boxes for those options.
Default Interface MTU (Bytes)
The default MTU value is 1522 bytes. To allow the service provisioner to override the MTU setting, select the Editable in Service Order check box.
MTU range for manual-config
In the MTU range fields, type the lowest and highest values for MTU for each UNI.
Note:To allow the service provisioner to override the MTU setting, select Editable in Service Order and, in the MTU range fields, type the highest and lowest MTU values.
PE-CE Interface Rate-Limiting Settings
Enable Interface Rate Limiting
To enable a service provisioner to limit the available bandwidth, select this check box, and type a default bandwidth limit.
Note:Bandwidth settings are available in the service definition when Manage CoS Profiles page is configured with CoS profiles.
Default bandwidth (Mbps)
Specify the default bandwidth value in Mbps.
Default: 10 Mbps
Range: 1 Mbps through 100,000 Mbps
Min Bandwidth (Kbps)
Specify the minimum bandwidth value in Kbps.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Max Bandwidth (Mbps)
Specify the maximum bandwidth value in Mbps. For more information on maximum bandwidth see Table 1
Default: 100 Mbps
Range: 1 Mbps through 100,000 Mbps
Increment (Kbps)
Specify a value that defines which values in the range is made available to the service provisioner.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Bandwidth – Burst Size Settings
Burst Size Calculator
Select the preferred option for calculating the burst size:
MTU Based
If you select the option MTU Based, you can specify a value for MTU Factor in the range 1 through 1087902.
The default value for MTU Factor is 10.
Burst Period Based
If you select the option Burst Period Based, you can specify a value for Burst Period in the range 1 through 7450 milliseconds.
The default value for Burst Period is 1.
Note:The Burst Size Calculator list is enabled only when you select the Enable Interface Rate Limiting check box.
Click Review to view the defined parameters. You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify. Click Back to return to the previous page of the wizard; else click Cancel to discard the changes.
After you complete reviewing the settings, click Finish to complete the service definition creation.
UNI Settings for Services with Flexible VLAN Tagging (Asymmetric Interface Types)
You can specify the Ethernet option asymmetric tag depth to create a service that includes any combination of port-based interfaces, 802.1Q interfaces, and Q-in-Q interfaces.
To specify the UNI Settings for q-in-q interfaces:
Fill in the fields on the Site Settings window.
Field
Action
PE-CE Interface Settings- Ethernet Encapsulation
VLAN Tagging
Select asymmetric tag depth from the list.
Physical Interface Encapsulation
Select the default physical encapsulation scheme to be used by service orders based on this service definition. We recommend you select flexible-ethernet-services.
For multipoint-to-multipoint services with Q-in-Q interfaces, the only option is flexible-ethernet-services
Logical Interface Encapsulation
Constrained by your selection in the Physical interface encapsulation box. If you selected the recommended physical encapsulation mode of flexible-ethernet-services, then your only option is to select vlan-vpls for the logical encapsulation method.
Traffic Type
Transport all traffic Transports the traffic from all VLANs across the network. When you select this option, the service provisioner is prompted for the VLAN-ID when creating a service order based on this service definition. You need to specify only the Outer Tag protocol ID..
Transport single vlan Transports traffic for a specific VLAN across the network. You need to specify both Outer Tag protocol ID and Inner Tag protocol ID.
Transport vlan range Limits the traffic across the network to a specific range of VLANs. You need to specify only the Outer Tag protocol ID.
Transport vlan list limits the traffic across the network to a specific list of VLANs. If you select this option, the service provisioner is prompted for the VLAN-ID list when creating a service order based on this service definition. You need to specify only the Outer Tag protocol ID.
If you select this option, the service provisioner is prompted for the VLAN-ID range when creating a service order based on this service definition.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
VLAN Normalization
Select a value:
Normalize to VLAN all—To preserve customer VLAN IDs (and customer QoS priorities) across the network.
Note:For services that transport a range of VLANs, you must select VLAN Normalization to all. You cannot transport a range of VLANs without normalization.
Normalize to VLAN none—To preserve no VLAN IDs across the network.
Normalize to Dot1q tag—To transport only single-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network
Normalize to QinQ tags—To transport only double-tagged frames across the network core. All port, dot1q , and Q-in-Q traffic is transported across the network.
Normalization not required—To specify no normalization for port-to-port services
Note:Starting with Release 1.0R2, when you newly install Connectivity Services Director, if you select the option to not require normalization in a service definition, the auto-pick option for VLAN IDs and the option to edit the auto-pick behavior in service order are disabled in the service definition. When you create a service order by associating with that service definition, you need to manually enter the VLAN IDs for the interfaces and cannot use the auto-pick functionality. This same behavior also applies to default service templates in which if you select the normalization-not-required functionality, the auto-pick option for VLAN IDs is disabled.
For more information about VLAN normalization, see Junos Space Layer 2 Services Overview.
For information about VLAN manipulation, see Understanding VLAN Manipulation (Normalization and VLAN Mapping) on Ethernet Services.
Auto Pick VLAN ID
Indicate how the VLAN ID is determined. By default, this check box is disabled.
Clear this check box to allow the service provider to specify the VLAN ID. This option is normally used when no VLAN normalization is applied. Specify the VLAN ID range in VLAN range for manual input.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Select this check box when VLAN normalization is applied. Specify the VLAN ID pool in VLAN range for auto-pick.
Note:Make sure to select Editable in Service Order if you want the service provisioner to be able to override this setting.
Note:When the range of VLAN IDs that are automatically assigned by the system (with the auto-pick option enabled during the creation of a service definition) is less than or greater than the range of VLAN IDs that are manually specified (with the manual selection option enabled during the creation of a service definition), the following conditions apply during the creation of a service order with the Editable in Service Order check box selected during service definition creation:
If you create a service order with the auto-pick option enabled, the VLAN ID is selected from the auto-pick range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
If you create a service order with the auto-pick option disabled, the VLAN ID is selected from the manually configured range, and the value is displayed in the VLAN range for manual input field. If you attempt to change the VLAN ID manually, the value is restricted to the manually configured range.
VLAN range for auto-pick:
Specify the VLAN ID pool.
Range: 1 through 4094
VLAN range for manual input
Specify the VLAN ID range.
Range: 1 through 4094
Outer Tag Protocol ID
Select the outer tag protocol ID if the Customer traffic type is Transport single VLAN:
0x88a8
0x8100
0x9100
Note:For an interface, you must configure a physical port with the possible Tag Protocol Identifiers (TPID) either manually or through a template. Otherwise, the service creation fails for all TPIDs except 0x8100. To configure the TPIDs manually, use the following commands:
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x9100
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x88a8
set interfaces ae0 aggregated-ether-options ethernet-switch-profile tag-protocol-id 0x8100
Inner Tag Protocol ID
Select the inner tag protocol ID:
0x88a8
0x8100
0x9100
Note:You cannot specify the Inner Tag protocol ID if the Customer traffic type is Transport all traffic.
Editable in Service Order
To allow the service provisioner to override the outer and inner tag protocol IDs, select the check boxes for those options.
MTU range for manual-config
In the MTU range fields, type the lowest and highest values for MTU that the service provisioner can type, for each UNI
Note:To allow the service provisioner to override the MTU setting, select Editable in Service Order and, in the MTU range fields, type the highest and lowest MTU values that the service provisioner can type.
Default Interface MTU (Bytes)
The default MTU value is 1522 bytes. To allow the service provisioner to override the MTU setting, select the Editable in Service Order check box.
PE-CE Interface Rate-Limiting Settings
Enable Interface Rate Limiting
To enable a service provisioner to limit the available bandwidth, select this check box, and type a default bandwidth limit.
Note:Bandwidth settings are available in the service definition when Manage CoS Profiles page is configured with CoS profiles.
Default bandwidth (Mbps)
Specify the default bandwidth value in Mbps.
Default: 10 Mbps
Range: 1 Mbps through 100,000 Mbps
Min Bandwidth (Kbps)
Specify the minimum bandwidth value in Kbps.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Max Bandwidth (Mbps)
Specify the maximum bandwidth value in Mbps. For more information on maximum bandwidth see Table 1
Default: 100 Mbps
Range: 1 Mbps through 100,000 Mbps
Increment (Kbps)
Specify a value that defines which values in the range is made available to the service provisioner.
Default: 1000 Kbps
Range: 64 Kbps through 100,000 Kbps
Bandwidth – Burst Size Settings
Burst Size Calculator
Select the preferred option for calculating the burst size:
MTU Based
If you select the option MTU Based, you can specify a value for MTU Factor in the range 1 through 1087902.
The default value for MTU Factor is 10.
Burst Period Based
If you select the option Burst Period Based, you can specify a value for Burst Period in the range 1 through 7450 milliseconds.
The default value for Burst Period is 1.
Note:The Burst Size Calculator list is enabled only when you select the Enable Interface Rate Limiting check box.
Click Review to view the defined parameters. You can examine and modify the created service order parameters. Alternatively, click the corresponding buttons at the top of the wizard page to navigate to the specific pages pertain to the settings you want to modify. Click Back to return to the previous page of the wizard; else click Cancel to discard the changes.
After you complete reviewing the settings, click Finish to complete the service definition creation.
Reviewing the Configured Settings
The Review page of the service definition or service order creation and modification wizards enable you to view and evaluate the service parameters and components you configured in preceding steps or pages of the wizard. This page provides a comprehensive, single-page view of all the service elements configured in the different pages of the wizard. You can either click the buttons corresponding to the various settings at the top of the wizard page to directly traverse to the page you want to modify or click the navigation buttons at the bottom of the wizard page to go to the different pages of the wizard.
On the Review page, in the Service Templates section, the names of the service templates with which the service definition is associated are displayed. The Default Service Template column indicates whether the attached template is the default template.
To examine and modify the configured service definition settings: