Release Notes for Connectivity Services Director 4.1R1
Junos Space Connectivity Services Director, built to run on Junos Space Network Management Platform, is a robust and holistic application that facilitates automated design and provisioning of E-Line services, virtual private LAN services (E-LAN), IP services, and RSVP-signaled label-switched path (LSP) services, configuration of quality-of-service (QoS) profiles, validation and monitoring of service performance, and management of timing or clock synchronization using Precision Time Protocol (PTP). Connectivity Services Director enables unified management of the ACX Series routers, M Series routers, MX Series routers, PTX Series routers, and TCA Series Timing Appliances in your network. It enables full network life-cycle management by simplifying the discovery, configuration, visualization, monitoring, and administration of large networks containing physical and virtual devices.
Connectivity Services Director enables you to provision point-to-point and multipoint services across networks. You can also configure class of service (CoS (also called QoS)) profiles to group a set of CoS parameters and apply the profiles to one or more interfaces of the devices that are managed by Connectivity Services Director. The Connectivity Services Director software application also contains the applications that were available in the Services Activation Director suite. Network Activate, Transport Activate, OAM Insight, and Sync Design are installed and presented with the same look-and-feel as Services Activation Director, after you install Connectivity Services Director.
The software images for Connectivity Services Director, Junos Space Network Management Platform, additional scripts, Connectivity Services Director API Reference documentation, and the release notes for Connectivity Services Director Release 4.1R1 are available at Junos Space and Junos Space Connectivity Services Director Download.
Table 1 lists the supported platforms for Connectivity Services Director Release 4.1R1 and the corresponding qualified Junos OS releases.
Table 1: Supported Platforms and the Software Versions for Connectivity Services Director Release 4.1R1
Qualified Junos OS Release
ACX Series Universal Metro Routers:
ACX1000, ACX1100, ACX2000, ACX2100, ACX2200, and ACX4000 routers
Release 12.3R1 through Release 12.3X54-D10
MX Series 5G Universal Routing Platforms
MX80, MX104, MX240, MX480, and MX960 routers
Release 12.2R1 through Release 17.4R1.16
MX2010 and MX2020 routers
Release 13.3R1 through Release 17.4R1.16
MX2008, MX150, MX204, and MX10003 routers
M Series Multiservice Edge Routers
Release 10.0 through Release 12.2R1.8
M7i and M10i routers
Release 10.0 through Release 14.2R1.12
PTX Series Packet Transport Routers
Release 13.2R2.2 through Release 17.4R1
Release 13.2R1.7 through Release 17.4R1
Virtual MX Routers (vMX)
Virtual MX Routers (vMX)
Release 14.1R5 through Release 17.4R1.16
Junos Space Network Management Platform Requirements for Connectivity Services Director 4.1R1
Connectivity Services Director Release 4.1R1 is supported on Junos Space Network Management Platform Release 18.4R1.
You can install Connectivity Services Director in a Junos Space Virtual Appliance or the JA2500 Junos Space Appliance. The Junos Space Virtual Appliance can be deployed on a VMware ESXi server. The Junos Space Virtual Appliance requires a VMware ESXi server 5.5, 6.0, or 6.5 that can support a virtual machine with the following configuration:
64-bit quad processor with at least 2.66-GHz speed
One RJ-45 10/100/1000 Network Interface Connector
250-GB hard disk
For detailed information about deploying Junos Space Virtual Appliance, see Junos Space Virtual Appliance Installation and Configuration Guide.
For detailed information about installing and upgrading Connectivity Services Director, see Connectivity Services Director Quick Start Guide.
The following are the operational notes for Connectivity Services Director:
The minimum supported screen resolution is 1280 x 1024. If your screen resolution is less than the supported resolution, the Connectivity Services Director UI might not be displayed properly. For example, icons might not be displayed on the Connectivity Services Director banner, pages might appear truncated, or scroll bars might not work correctly.
The supported Web browsers are Google Chrome 17 and later, Mozilla Firefox 14.0 and later, and Microsoft Internet Explorer 9.0, 10.0, and 11.0.
If you have been logged in to Connectivity Services Director for a long period of time, the connection to the server might time out. Monitoring pages might go blank or you might not be able to access tasks. To resolve this, log out of Connectivity Services Director and then log in again.
If you receive a Java exception error message when you perform an operation, retry the operation. The error condition is usually temporary and harmless.
Only user accounts with administrator (admin) privileges can use the Connectivity Services Director API.
For Connectivity Services Director to be able to discover and manage devices, the following protocol ports must be open between the Junos Space Network Management Platform server and the devices:
Port 22 for SSH connections. If you have changed the SSH port to a port other than port 22 on your Junos Space Network Management Platform, you must change the SSH ports on your managed devices to the port that the Junos Space Network Management Platform is using.
Port 10162 for device-level SNMP traps. Connectivity Services Director receives traps from managed devices on this port. (After you install Connectivity Services Director, use Connectivity Services Director to configure SNMP on your devices to send traps to Connectivity Services Director on this port.)
Port 162 for service-level SNMP traps. Junos Space Network Management Platform uses the port for snap trap collection and correlation.
Port 21 (TCP) and port 69 (UDP). Junos Space Network Management Platform uses these port for uploading the software image and configuration file to the FTP server.
For a prestaged device, if a mismatch is detected for the UNI status in the Connectivity Services Director database and on the device (caused by the application being down or network accessibility problems), the synchronization of the UNI interface might not occur. In this case, the status update happens on next configuration commit operation on the device. To manually resolve this discrepancy, you can trigger a synchronization by unassigning and reassigning the UNI role of the interface.
In a scaled environment, it is recommended that you disable monitoring functionality as it might cause the Connectivity Services Director application to poll the specified devices and retrieve details to be displayed in the widgets in Monitor mode of Service view. You might require the monitoring functionality to be disabled to prevent the slowness in loading the GUI pages. You can disable the monitoring mechanism the following ways:
In the Connectivity Services Director UI, go to System > Preferences > Monitoring and disable monitoring.
Run a script on the Junos Space Appliance. You must stage the script on the device with administrative and execute permissions for the script file before executing the script.
To enable or disable monitoring, enter the following command at the shell prompt (To run shell commands, from the Junos Space Appliance Settings menu, enter 7 at the prompt):
EnableDisableCollector.sh <db_user_name> <db_password> <collectorName> <enable/disable>
db_user_name is the username of the user for the Connectivity Services Director database.
db_password is the password of the user for the database.
collectorName is the name of the collector for which you want to enable or disable retrieval of statistics. You can enter one of the following collector names:
ProvisioningMonitorInterfaceStatusCollector—Defines the polling interval for monitoring the interface status
ProvisioningMonitorInterfaceStatsCollector—Defines the polling interval for monitoring the interface statistics
ProvisioningMonitorServiceStatusCollector—Defines the polling interval for monitoring the service status
ProvisioningMonitorLDPStatsCollector—Defines the polling interval for monitoring the LDP statistics
ProvisioningMonitorY1731PMCollector—Defines the polling interval for monitoring the performance management or Y.1731 statistics
ProvisioningMonitorLSPStatsCollector—Defines the polling interval for monitoring the LSP statistics
EquipmentMonitorDeviceStatusCollector—Defines the polling interval for monitoring the status of a device
The collectorName parameter is optional. If you do not specify a collector name, monitoring is enabled or disabled for all the collectors. If you enter an incorrect collector name, the list of collector names is displayed and you are prompted to select from the list.
enable is the keyword to enable the monitoring functionality and collection of statistics.
disable is the keyword to disable the monitoring functionality and collection of statistics.
We recommend that you use the script to disable the monitoring functionality only with the assistance of a Juniper Technical Assistance Center (JTAC) representative.
For IP services, data plane validation is not performed when you run functional audit for a service that does not contain the vrf-table-label attribute, which maps the inner label of a packet to a specific virtual routing and forwarding (VRF) instance. The Functional Audit Results window displays a message about the vrf-table-label configuration attribute not enabled in the service in such a scenario.
Sometimes, the validation of an E-Line service order fails with an error message stating that a duplicate virtual circuit ID exists, even when you have selected the option to automatically assign a VC ID from the VC ID pool in the service order. This condition occurs because of a resource pool allocation failure—that is, when the same device is managed by more than one Junos Space Network Management Platform application. Consider a device that is added and discovered by two Junos Space Network Management Platform servers. Assume that on one server running Junos Space Network Management Platform, Connectivity Services Director is also installed. The resource pool management functionality on that server reserves resources for devices that are managed only by using that server. If a resource, such as an IP address pool, VLAN ID, or a route target is reserved by both the Junos Space Network Management Platform servers, the reservation on one server is not reflected in the other server. If the same resource is marked for use in a service by multiple Junos Space Network Management Platform instances or servers that manage the same device, you must perform a service recovery operation. This operation recovers services that are present on devices that Junos Space Network Management Platform is not managing. Auto-discovery of services is not supported; therefore, resources used by other Junos Space Network Management Platform servers or modified on a managed device using the CLI are not reserved and displayed in the resource pool. The device configuration must be validated to check for duplicate resources before deploying or validating a service.
When a device is configured from the CLI, apart from the application, service recovery must be performed on Connectivity Services Director. This is required so that Connectivity Services Director can learn all the consumed resources in the network and auto-allocation allocates free resources and also restricts manual configuration of consumed resources.
New and Changed Features
This section lists the new and changed features in Connectivity Services Director Release 4.1R1:
Support for RFC2544 on E-Line and IP Services—Starting with Release 4.1R1, Connectivity Services Director supports the RFC 2544 test methodology in Connectivity Services Director for E-Line and IP services.
The RFC 2544 test feature is available from the Connectivity Services Director UI. To access this feature, go to the Service View page, and click ServicePerformance-RFC2544. For more information, see RFC 2544 Testing Overview.
The RFC 2544 test feature is not supported for E-LAN services as they cannot be provisioned on ACX 2k devices, they can only be provisioned on ACX 5k devices. You can run an RFC 2544 test at device-level. For more information, see Creating an RFC 2544 Test Profile for Devices. You can also refer Example: Configuring Benchmarking Tests to Measure SLA Parameters for E-LAN Services on an MX104 Router Using VPLS to understand how to configure benchmarking tests for E-LAN services using VPLS.
Supported platforms—ACX Series Universal Access Routers and MX Series 5G Universal Routing Platforms
New Tab for RFC2544—Starting with Release 4.1R1, a new tab RFC2544 is added to the Service View page. The RFC2544 tabs displays the RFC2544 test profiles created to measure throughput, latency, frame loss rate, and bursty frames.
The Service Performance tab on the Service View page is renamed to Y1731.
New menu OAM added to the Tasks pane. The OAM menu provides the options Y.1731 and RFC2544. For more information on these menu options, see Understanding the Service View Tasks Pane in Monitor Mode .
The PM Statistics menu option is renamed to Y.1731 and is available under the new menu OAM in the Tasks pane.
This section lists the known limitations in Connectivity Services Director:
For RFC 2544 test feature to function correctly, install the schema compatible for a device and set it as the default schema, prior to the Connectivity Services Director upgrade, and restart the jboss service.
Job details displayed on the Config Deployment Jobs Status page do not contain complete information about failed jobs. To get complete information about failed jobs, including the reason for job failure, you need to verify the server logs stored on the server.
Connectivity Services Director supports role-based access control (RBAC) only at the task category level. There is no support for object-level or task-level access control.
When you edit a service order, the auto-pick option that you enabled during the creation of the service order that is associated with a service definition is not preserved. Also, the parameters for which you enabled automatic selection by the system, such as Unit ID and Route Target, require you to enter values, and the Autopick check boxes do not remain selected.
When you edit an existing service order by clicking the Edit button on the Manage Network Services or Manage Service Deployment pages in Deploy mode of the Service view on the Connectivity Services Director GUI, a fresh service order is created with the name you specified. Only the changed node details are stored in the new service order and the previous details are lost.
This is an expected behavior because only a subset of the configuration settings are required to be propagated to a device from Connectivity Services Director, whenever a service order is modified. As a result, an existing service order is not saved when you modify it; instead, a fresh service order is created. Also, a service order related to a failed or invalid modified service cannot be modified. You need to delete the failed or invalid service order and modify the service again.
When you launch the Chassis view of a device, device labels are missing from the Google Chrome browser. The interface numbers are not displayed beneath the ports and the device name is not shown in the front view of the chassis image. Also, when you click the Perspective button to view the three-dimensional, advanced view of the chassis, the quality of the chassis image displayed is reduced slightly. This behavior with image quality is expected in the Google Chrome browser.
In Monitor mode of the Service view, for the Service Monitoring Summary page, the Traffic Trend data is displayed without a unit of measurement (UOM), a tooltip, or an option to zoom in or zoom out.
When you select the Service Traffic tab in Monitor mode for a specific E-Line LDP resiliency service, the connection status between the source device and other devices is denoted as NA (not available) in the Service Traffic monitor if any of the following conditions occur:
The device does not have Layer 2 circuit data.
Remote procedure call (RPC) commands are failing.
The NETCONF connection fails to be established.
On the pseudowire graph in the Service Traffic monitor, a gray line is displayed for the NA state. After the next polling cycle, the monitoring mechanism of Connectivity Services Director marks the connections status as NA for all connections from the endpoints on which the Layer 2 circuit configuration is deleted.
The connection status value in the Service Traffic monitor is refreshed depending on the polling interval configured on the Monitoring tab of the Preferences page (which you can launch by clicking the down arrow beside the System button on the Connectivity Services Director banner and selecting Preferences).
On the Service Monitoring Summary page that is displayed when you select a service from the Network Services > Connectivity > E-Line Services tree, Network Services > Connectivity > IP Services tree, or Network Services > Connectivity > E-LAN Services tree in the Tasks pane, and select the Service Traffic tab in Monitor mode of Service view, the Traffic Trend (bps) column displays only the rate of egress traffic in the form of a line graph. The rate at which ingress packets are received is not displayed.
When you attempt to validate or provision a service order, the "Service Order Deployed OK" pop-up message is displayed, regardless of the result of the action. This is an incorrect behavior. The same message is displayed even if the validation and provisioning attempts fail. A job ID with a link must be displayed that you can click to navigate to the Job Management page for the results.
When a configuration audit is performed, the XPath attributes in the service configuration are used. Only the addition, modification, and deletion of the XPath attributes are detected, but the creation of a new attribute (child XPath ) on a device is ignored. This behavior is expected because Junos Space Network Management Platform audits only the settings in a user template. If the template has a container, Junos Space Network Management Platform audits only to determine whether the device is configured with this container. If you want to audit any container child, you need to add it into the template. This scenario is similar to an out-of-band configuration change on the device, which Junos Space Platform can determine only whether System of Record mode is set for Junos Space Network Management Platform.
Several delete statements are observed in the service settings on the Service Configuration tab of the Configuration dialog box. The delete statements indicate deleted policy attributes from a corresponding service on a device. When a service is created or modified, its policy options are deleted from the device to prevent the previously existing policies from interfering with the service. The presence of the delete statements is an expected behavior and does not indicate any incorrect service configuration.
You cannot view details of a device prestaging job on the Job Management page. You need to view the Prestage Devices page in Build mode to view the device prestaging details.
When you modify an IP service order for which multicast VPN has been enabled during the creation of the service order, the MVPN check box is disabled on the Service Parameters page of the IP service modification wizard. You cannot modify MVPN settings during the editing of a service order if MVPN is already enabled in the service order.
On the Manage Network Services page, you can search for services using only the service name. For the other fields displayed on this page, the search utility is not supported. You can filter the table by clicking the arrow to display the column drop-down menu in the table and selecting the Filters option.
The search function is supported only for the elements of the tree that are displayed on the page; the global search facility that analyzes all configured elements in the database is not supported.
While prestaging a device, you cannot modify a loopback address or add multiple loopback addresses.
At times, when you attempt to validate an E-LAN service, an error message is displayed stating that the route target is not in the prescribed format of x:y. This error occurs when an autonomous system (AS) number is defined in the device or when the routing options table does not have the AS number of the device stored in it (that is, the AS number is not synchronized properly).
In a scaled environment, thousands of services, each assigned to a different virtual circuit ID (VC ID), the Resource Allocation Details page from the Prestage Devices workspace in Build mode of the Service view contains too many details. It is difficult to determine whether a VC ID has been assigned to a device or not. This is because VC IDs are sorted on the basis of strings and not numbers.
The Decommissioned Service Orders option is available on the Tasks pane only when you select the Connectivity node or the Tunnel node from the Network Services tree on the View pane. This option is not available if you select the Network Services node on the View pane. Also, this option is not available if you expand the Connectivity tree and select E-Line Services, E-LAN Services, or IPServices, or if you expand the Tunnel tree and select RSVP LSPs.
From the Service Monitoring Summary page, which is displayed if you do not select a particular service from the Service view pane and select the Network Services, Connectivity, E-Line Services, IP Services, or VPN Services node on the Service view pane and you want to navigate to the Service Summary page of a specific service, select the corresponding service from the Network Services > Connectivity tree on the View pane.
When you perform a functional audit with the DMI schema as JUNOS 13.2 on the Junos Space Network Management Platform server that is running Connectivity Services Director, the functional audit job fails because the configuration is propagated to devices without the accept and reject tags, which prevents the routes from coming up.
Workaround: Upgrade the DMI schema to JUNOS 14.2, which causes functional audit to succeed and the routes to come up properly.
Sometimes, when you attempt to discovery devices from the Connectivity Services Director GUI after the installation of a new image, the "Service is not available due to resource loading, please retry later." message is displayed. This condition occurs because it takes more time than expected for the resources and schema to be loaded from Junos Space Network Management Platform. As a result, adequate resources are not available to initiate the discovery of devices.
For each E-LAN service order, multiple entries are created in the Connectivity Services Director database. This behavior is expected because a service with "n" endpoints creates "n" entries in the ELANvplsConnectivity table of the database and for each endpoint, data is saved separately with different route distinguishers.
For some fields, such as Interface and LSP Status, that are displayed in the different widgets on the Service Traffic, Service Transport, and Service Summary pages in Monitor mode of the Service view, the values or statuses that are shown are updated based on the polling interval for retrieving data from the devices. As a result, the values or statuses for such fields are reflected in the widgets of the monitoring pages with a delay of a few minutes.
Tags, which enable you to categorize and organize managed devices, are not supported in Connectivity Services Director. Because tags are not supported, you cannot use tags for provisioning LSPs in cases where an ingress device is a router and an egress device is a device tag, which denotes multiple spokes in a full-mesh or hub-and-spoke topology.
In a scaled environment with approximately 3000 services configured, it is observed that the size of the file descriptor increases to the range of 16,000 to 17,000 and remains within this range.
When you edit a service order, you cannot modify the parameters of the MAC Settings and Advanced Settings sections of the service order wizard.
When you edit an E-LAN service order, you cannot modify the device roles. For example, you cannot modify a VPLS spoke to be a point-to-point spoke.
You must clear the browser cache when you need to view and work with the E-LAN service order pages. Otherwise, the webpage is not loaded properly.
To view only MX Series routers on the Assign Quick Templates page, you select MX from the Device Family list. However, you do not have an option to view only ACX Series routers on the Assign Quick Templates page. You select Common from the Device Family list to display all device families, which also includes ACX Series routers.
Deletion of a decommissioned service order results in a “ConstraintViolation” exception. The following error message is displayed:
An error occurred deleting this service order:
Bad Request org.hibernate.exception.ConstraintViolationException: could not delete:
Workaround: Use the following command to manually delete the related EthernetUnis of the service order from the EthernetUni table in the database:
delete from EthernetUni
Enter the delete from EthernetUni command at the shell prompt of the Junos Space Network Management Platform. To run shell commands on a Junos Space Virtual Appliance, enter 7 in the Junos Space Settings menu.
For the discovery of LSPs, Connectivity Services Director creates router profiles on CSD-Topology. Connectivity Services Director uses the same username that it uses to discover devices to discover LSPs. If the user account has privileges for shell access, LSP discovery fails on CSD-Topology. This failure occurs because the CSD-Topology requires the user account to have only CLI-access privilege and not shell-access privilege. Also, if Connectivity Services Director has discovered devices using the root account (with native access), LSP discovery fails on CSD-Topology.
Workaround: Perform the following steps for CSD-Topology to successfully discover LSPs:
Initiate an SSH or Telnet session to the CSD-Topology VM external IP address.
Modify the following CLI command files to be executed to add the cli command before any other command is executed so that access to the CLI shell is obtained. This modification does not impact non-root (non-superuser accounts) because the output of the additional command is ignored. For root users, the CLI shell is invoked first and all other commands (such show configuration and show mpls lsp) are executed correctly:[root@hostname~]# /opt/pcs/db/command/juniper.config[root@hostname~]# /opt/pcs/db/command/juniper.interface[root@hostname~]# /opt/pcs/db/command/juniper.tunnel_path[root@hostname~]# /opt/pcs/db/command/juniper.transit_tunnel
The contents of the preceding files have the CLI command to be executed on the routers. For example, the original contents of
juniper.configfile are as follows:
!Silent set cli screen-width 0 show config|display inheritance|no-more
You must modify this file as follows to include the cli command:
@P cli !P !Silent set cli screen-width 0 show config|display inheritance|no-more
In a scaled environment, the Connectivity Services Director application might allow multiple users to modify a large service at the same time from different browsers or machines. As a result, you might see more than one instances of a single validated service order.
On the Service Summary page for E-LAN services, the Connections matrix does not show the exact VPLS connection present on the device for all endpoints. This problem occurs because the remote procedure calls and CLI commands do not return the remote device IP address when the connection is down.
The monitoring framework polls data from devices based on the serial number of the chassis, rather than the hostname or IP address of the device, which is unique in a network deployment. With the existing monitoring mechanism, when a chassis contains a new serial number, the device chassis is considered a different entity and all historical data (collected for the same host or IP address of the chassis) saved is lost.
The outer and inner tag protocol IDs that you want to configure in a service definition must be preconfigured on the device associated with the service definition for a successful validation and provisioning of the service order.
In certain scenarios, such as after an upgrade from Services Activation Director Release 14.3R1 to Connectivity Services Director Release 1.0, you might observe that alarms related to services are not properly cleared on the Connectivity Services Director GUI. This problem occurs because of the manner in which alarms are transmitted from OpenNMS to Junos Space Network Management Platform.
Workaround: Manually clear the appropriate alarm from the Alarm Details page in Fault mode of Service view after examining the alarm and associated events, and taking any action needed to resolve the condition that triggered the event on the corresponding device.
During creation of a set of an E-Line service with pseudowires, which are doubly tagged on the ingress router and singly tagged on the egress router, it is observed that an additional VLAN swap operation occurs on the Z side. This is effectively a null operation because both the input and output VLAN IDs are set as 133 in this case. This behavior also occurs with a local-switching service.
If you attempt to create a service order with an E-Line LDP service definition, you cannot view the non-editable parameters in service template during service deployment. This problem occurs when you create and publish the service definition with local-stitching by associating it with a service template that contains the circuit cross-connect (CCC) family set, such as set interfaces xe-0/2/0 unit 0 family ccc.
The ILA adapter fails to upgrade if you install the Connectivity Services Director application in a setup where an ILA adapter already exists.
Workaround: Before you install the Connectivity Services Director application you must delete the existing ILA adapter. You can delete the existing ILA adapter at Network Management Platform > Devices > Device Adapter.
If you migrate from Services Activation Director to Connectivity Services Director Release 2.0R3 or earlier, Enable Tunnel services and Enable Local Switching parameters cause functional issues.
In order to overcome these issues and maintain consistency across products, in Connectivity Services Director Release 2.0R4, Enable Tunnel services and Enable Local Switching parameters are renamed Disable Tunnel services and Disable Local Switching respectively.
As a result of this renaming, you might encounter issues when you are migrating from Connectivity Services Director Release 2.0R2 to Connectivity Services Director Release 2.0R4.
Workaround: Use the Modify Service workflow to modify the service according to the new naming convention. For example, if you prefer to enable tunnel services while modifying the existing service, clear the Disable Tunnel services check box.
In specific cases, in an E-LAN service, multiple sites might have the same interface, UnitID, and VLAN ID. Any subsequent addition of a site results in a redundant site addition along with the original site. Though deployment is successful, the extra redundant configuration is pushed to the devices.
Workaround: Perform the following steps:
Disable deploy to device.
Delete one UNI that is duplicate and deploy the service order.
Delete the other UNI and deploy again.
Add the required UNI and deploy.
Enable deploy to device.
This section lists the known issues in Connectivity Services Director Release 4.1R1. For the most complete and latest information about known Junos Space Connectivity Services Director defects, use the Juniper Networks online Problem Report Search application.
The following issues are seen when layer 3 (L3) access is enabled for an ethernet-LAN (eLAN) service definition:
Port tagging is not supported
If tagging is Dot1q, vLAN normalization only normalizes to the Dot1q tag.
If tagging is QinQ or asymmetric tag depth, vLAN normalization only normalizes to the QinQ tags.
Cannot create a service order with a custom path for a label switched path (LSP) with point-to-point (P2P) path and local protection. When you try to create a custom path, the creation of the service order fails with the error “Fast Reroute is not required”.
Workaround: First, create an LSP service definition with P2P path and local protection. Then, create a service order by importing the newly created service definition, and continue to create the custom path.
When a UNI is deleted using the Service Modify functionality, the deleted UNI information is still shown as part of the service configuration.
ACX5448 supports provisioning of only basic E-Line and LSP services on Junos OS Release 18.2.
ACX5448 does not support provisioning of E-LAN and IP service types on Junos OS Release 18.2. [PR1367398]
The fault status of an E-LAN BGP or E-LAN LDP service is not displayed correctly on the user Interface. [PR1344103]
While creating an IP service, if you select more than one interface from the same device, the interfaces appear in the same row, separated by commas. [PR1345660]
When you use an IFD template with a tag-based role to push configuration on a VLAN-based service and then later delete the VLAN-based service to create a service by using the same IFD template with the role changed to port-based, the service creation fails. [PR1346264]
You are unable to delete an IP service that has at least one node configured with an Integrated Routing and Bridging (IRB) Interface. [PR1347272]
The Fault status on the Manage Network Services page is unavailable for an E-LAN service with Transport vlan list as the traffic type. [PR1350669]
If you delete the peer node of a device while editing the node settings of an E-LAN service order and later revert the changes, then the peer node is not displayed on the Edit E-LAN Service page. [PR1366732]
When an Ethernet VPN (EVPN) service, with Ethernet Segment Identifier (ESI) and multihoming set to single-active or all-active, is recovered, the Service Details page does not list peer interfaces.
Also, when the service is modified, the Node Settings and Site Settings pages of the Service do not show the mapping between interfaces of the peer nodes. [PR1362288]
The fault status is unavailable on the Connectivity Services Director GUI for an E-LAN service with evpn or evpn e-tree as the protocol type, when an interface goes down. [PR1355928]
Monitoring information is incomplete for EVPN-VPWS services. [PR1373237]
Monitoring information is incomplete for EVPN services. [PR1373240]
The Service Definition pop-up window enlarges but the content within the pop-up does not get enlarged proportionately. [PR1375906]
In the Service Order page, the Site Settings Rate Limiting column is cropped. [PR1375909]
The Configuration page for a selected template is not displayed after provisioning and preparing to create a service order. [PR1383599]
H-VPLS cannot be configured using Connectivity Services Director Release 3.0. [PR1388345]
JBoss server crashes with out of memory errors when Connectivity Services Director monitoring is enabled. [PR1390204]
Service template configuration cannot be deleted from a service order. [PR1391388]
Entity persistence issue leads to transactional deadlock with impacting multiple services. [PR1396086]
Analysis for Heap/CPU Profiling (HPROF) agent file creation and jobs hang. [PR1401357]
Maximum transmission unit (MTU) validation does not work. [PR1401528]
An existing EP-LINE service cannot be modified for a VRF service. [PR1402417]
Invalid test profiles must be deleted. [PR1405060]
A unique ESI cannot be generated for EVPN multihoming with AS number 36000. [PR1402709]
When L3 Access is enabled, Port cannot be selected as Ethernet Option on the Interface Settings page. Only the QinQ normalization option is displayed on the General Settings page where all normalization options except Normalization not Required should be displayed. [PR1389503]
This section lists the resolved issues in Connectivity Services Director Release 4.1R1. For the most complete and latest information about resolved defects in Junos Space Connectivity Services Director, use the Juniper Networks online Problem Report Search application.
The Next tab on the Node Setting page does not work after upgrading to Connectivity Services Director Release 2.2R1.3. [PR1388424]
Deactivating the VRF service in Connectivity Services Director deactivates the export configuration of the forwarding table. [PR392971]
Devices are not listed in the Connectivity Services Director resource table when running Junos Space Network Management Platform Release 17.1R1 and Connectivity Services Director Release 2.1.8. [PR1398396]
The VLAN-ID cannot be deleted from the VLAN list while modifying a service order. [PR1403281]
The IP transit service deletes all static routes. [PR1370929]
Provisioning services with attached CoS templates fail on ACX Series routers due to one or more invalid configuration statements. [PR1395988]
PW access to L3 is always enabled even when a service definition is created with the PW access to L3 option set as False. [PR1402167]
The hub-and-spoke service is pushing the wrong sytax for an LSP policy. [PR1402444]
A wrong configuration is pushed for the spoke device. [PR1402958]
Error in VRF recovery. Services that are using an integrated routing and bridging (IRB) interface cannot be recovered.[PR1400363]
Workaround: When you add a gig interface, the services using the IRB interface are recovered.
Service orders cannot be created and decommissioned service orders cannot be deleted after upgrading from Junos Space Network Management Platform Release 15.2 and Connectivity Services Director Release 2.0 to Junos Space Network Management Platform Release 17.2R1 and Connectivity Services Director Release 2.2. [PR1405280]
While recovering interfaces for any VPN service with a ge-x/y/z interface, where z > 9, the interfaces are discovered but are listed under Rejected Endpoints. An additional single digit corresponding interface is added to the results. This interface is neither associated with the service nor configured on the device. [PR1401524]