Modifying the Application Settings of Connectivity Services Director
To modify the configuration settings of services activation-related capabilities of Connectivity Services Director, perform the following steps:
- To open the Preferences page, click
in the Connectivity Services Director banner and select Preferences from the list.
The Preferences page appears, with User Preferences as the default tab.
- Click the Services Activation tab.
- Click any parameter, or specify a different value for
parameters that accept values, to modify it.
Note You cannot modify the application settings if another user is currently modifying them.
- Click OK to save the changes that you made in the Connectivity Services Director application or click Cancel to retain the original settings.
Also, you can modify the configuration settings for the Connectivity Services Director application using the Junos Space Platform GUI.
To modify the configuration settings of Connectivity Services Director using the Junos Space Platform GUI, perform the following steps:
- From the Network Management Platform task
pane, select Administration > Applications.
The Applications page that appears displays a list of the applications in the Network Management platform.
- Right-click Network Activate and select Modify Applications Settings.
The Modify Application Settings page that appears displays a list of the parameters that can be modified.
- Click any parameter to modify it.
Note You cannot modify the application settings if another user is currently modifying them.
- Click Modify to save the changes that you made in the Connectivity Services Director application or click Cancel to retain the original settings.
To understand the parameters of the Connectivity Services Director application settings, refer to Table 1.
Table 1: Parameters in Connectivity Services Director Application Settings
Fields | Description |
---|---|
Deployment | |
Check service version | Select this check box to validate the version of the service being configured. |
Deploy configuration to the device | Select this check box to deploy the configuration to the device. |
Enable service alarms | Select this check box to enable the service alarms. Enabling the service alarms causes a GUI impact on the Connectivity Services Director application. When you select the check box and deploy the service, the interface goes down, resulting in the failure to update the fault status. When you right-click Service and select View Service Alarms, the latter does not appear in the results. |
Save configuration in XML format | Select this check box to save the configuration of the device in XML format. |
Show configuration in set format | Select this check box to display the configuration in set format. |
Use two-phase commit for service provisioning | Select this check box to push the configuration on all the network elements automatically, making either one or all successful. |
Use vlan maps for E-Line services | When this check box is selected, normalization of VLAN tags is performed using the input or output VLAN maps. This check box is selected by default. Note: Starting in Connectivity Services Director Release 2.1R1, Use vlan maps for flexible tagged services under Modifying the Application Settings of Connectivity Services Director is renamed to Use vlan maps for E-Line services. |
Use vlan maps for flexible tagged services instead of normalized vlan (VPLS) | When this check box is cleared, normalization of VLAN tags is performed using normalized tags under routing instance. This check box is cleared by default. Note: Starting in Connectivity Services Director Release 2.1R1, normalization of VLAN tags is performed using normalized tags under routing instance while modifying the application settings. |
Audit | |
Enable Functional Audit after deployment | Select this check box to perform the functional audit automatically, after the service is deployed successfully. By default, the functional audit is not checked. Extra time is taken to complete both the functional audit and deployment. |
Functional Audit Waiting Time after deployment | Specify the initial wait time to auto-schedule a functional audit job after deployment. If the entered value is greater than 30 minutes, it is reset to 30 minutes. If the entered value is less than 1 minute, the wait time is ignored. The range is from 1 minute through 30 minutes. |
Perform Functional Audit on Control plane only | Select this check box to make the functional audit ignore the data plane verification and to consider only the control plane. |
User Interface | |
Allow template modification for service | Select this check box to allow the templates to be changed during the service modification. |
Bandwidth Combo Items Count | Specify the bandwidth combo items count. In Create IP service order page, if the bandwidth range exceeds the bandwidth combo items count, then the bandwidth input is taken in text field. The default value is 100. |
Service Detail Wait Time (sec) | Specify the period of time in seconds as the wait period for retrieving service details during service template modification. |
Monitoring | |
Perform Monitoring on Failed Functional Audit | Select this check box to perform monitoring if the functional audit fails. |
Pseudowire Redundancy Transition TimeDelay | Select this check box to dump the configuration files. Specify the time delay to issue the remote procedure call (RPC) call for redundancy service. Since there is no support for the fault management for redundancy service, it should not update the fault status as down, when the interface goes down as the service will be running with the help of backup device. The RPC is issued to check the status of the service. If the value of this time delay is 2 seconds and the interface goes down, it waits for 2 seconds to check whether the service is up, with the help of the backup device and correspondingly updates the fault status. The default value is 2 seconds. |
Statistics Aggregation Reporting | Specify the manner in which the aggregated results are returned for a query that polls and retrieves data from devices. Two aggregation values are supported:
|
Logging | |
Dump Configuration Files | By default, the configuration files are not dumped into the log directory. This is enabled, if there is a need to provide troubleshooting to Juniper Networks Technical Assistance Center (JTAC). |
Dump Deployment Data | Select this check box to write the configlets and error response from the JUNOS devices into the log directory.. |
Log Directory | Specify the default path of the log directory: /var/tmp/jboss |
Prestage Devices | |
Pre-stage Wait Time (Sec) | Specify the number of seconds for which the task to trigger a job for prestaging devices must wait after receiving the first notification for prestaging devices. For example, if you specify the prestage wait time as 20 seconds, the prestaging task waits for a period of 20 seconds, after receiving the first notification for prestaging devices, and then initiates the prestaging-devices job. |
Pre-stage Idle Time (Sec) | Specify the number of seconds after which the job for prestaging devices is initiated, if no notification is received during the idle period. For example, if you specify the prestage idle time as 10 seconds and if no notification for prestaging devices is received within this period, the job for prestaging devices is triggered immediately after 10 seconds. The prestage idle time value takes precedence over the prestage wait time value. |
Loopback Unit | Specify the logical unit of the loopback interface that must be used as the default loopback logical interface for all provisioning tasks that are initiated from Connectivity Services Director. The default logical unit for the loopback interface is 0. |
Route Target | |
BeginIndex | Specify the least value in the preferred range of numbers, among which a certain number is assigned for each BGP service. Route target allows you to distribute VPN routes to only the routers that need them. When a route target value is entered manually, it should be either of the following two formats: Autonomous System number format or IPv4 format. For Autonomous System number format, the pattern is as-number:2-byte-number. For example, target:100:200. Range: The Autonomous System number format number can be in the range from 1 through 65,535. The IPv4 format is ip-address:2-byte-number. For example, target:10.1.1.1:2. |
EndIndex | Specify the greatest value in the preferred range of numbers, among which a certain number is assigned for each BGP service. Route target allows you to distribute VPN routes to only the routers that need them. When a route target value is entered manually, it should be either of the following two formats: Autonomous System number format or IPv4 format. For Autonomous System number format, the pattern is as-number:2-byte-number. For example, target:100:200. Range: The Autonomous System number format number can be in the range from 1 through 65,535. The IPv4 format is ip-address:2-byte-number. For example, target:10.1.1.1:2. The EndIndex value should be lesser than the maximum assigned value. |
Virtual Circuit ID | |
BeginIndex | Specify the least value in the preferred range of numbers, among which a certain number is assigned as the VirtualCircuitID to the new circuit created. This VCID can be manually chosen by the customer or auto-generated by the system. For example, if BeginIndex = 100 and EndIndex = 200, then the VCID would be somewhere between 100 and 200. Minimum: 1 The value of BeginIndex should be less than or equal to EndIndex value. The range is from 0 through 200000. |
EndIndex | Specify the greatest value in the preferred range of numbers, among which a certain number is assigned as the VirtualCircuitID to the new circuit created. This VCID can be manually chosen by the customer or auto-generated by the system. For example, if BeginIndex = 100 and EndIndex = 200, then the VCID would be somewhere between 100 and 200. Maximum: 2147483647. The range is from 0 through 200000. |
Performance Monitoring | |
DataSetSize | DataSetSize is the size of the performance monitoring data set in days. This field indicates the number of days of performance monitoring data could be stored for display. The default value is 2880. |
Enable Performance Monitoring through scripts | Select the check box to collect the performance data through scripts and opennms will store the data in its database. If this check box is not selected, then performance data such as one-way delay, two-way delay, and frame loss are collected through RPC and stored in the application database. |
OSS Config Parameters | |
Alcatel Primary Server IP | Specify the IP address of the primary server. |
Alcatel Primary Server Port | Specify the port number of the primary server. |
Backup Server IP | Specify the IP address of the backup server. |
Backup Server Port | Specify the port number of the backup server. |
HTTP Connection Timeout | Specify the duration of HTTP connection before the time-out elapses. |
Maximum API Requests | Specify the maximum number of simultaneous API requests permitted. |
OSS Log Directory | Specify the directory path of the OSS log directory. |
OSS Log Filename | Specify the OSS log filename. |
OSS User Name | Specify the user name for accessing the OSS server. |
OSS User Password | Specify the hashed password for accessing the OSS server. |
Synchronize OSS Inventory daily at given time | Sets the daily time at which the CPP system synchronizes third-party devices, added or deleted from the CPP system, with the OSS server. |
Use primary server | If the check box is enabled, the CPP system communicates with the primary OSS server. |
Service Decommission | |
Service Recovery | |
OutofBand Notification | Select either of the following options from the OutofBand Notification Action list to specify the action you want to be performed when an OutOfBand notification is received by Connectivity Services Director:
|
Store OutofBand Notification XML | Select the check box to enable the storage of OutOfBand notification XML in the Connectivity Services Director database. By default, this check box is not selected, which disables the saving of OutofBand notification XML in the Connectivity Services Director database. |
Device Sync Wait Time | Specify the device synchronization waiting time. This is the maximum wait time to complete the device synchronization. After this time duration, irrespective of the device synchronization status, the resources are released. The default value is 60 seconds. The range is from 30 seconds through 300 seconds. |
Reports (accessible from the Modify Connectivity Services Director Settings page in the Administration workspace of the Junos Space Platform GUI) | |
Retention period for generated Reports days | Move the slider right or left to specify the time period for which the generated reports must be retained in the Connectivity Services Director database. By default, Connectivity Services Director keeps reports for 30 days. However, Network Administrators can change the retention period from 0 to 365 days. |
Search (accessible from the Modify Connectivity Services Director Settings page in the Administration workspace of the Junos Space Platform GUI) | |
Index auto update interval in seconds | Specify a time interval after which Connectivity Services Director initiates the next indexing on the Search tab. By default this option is selected and the search index update interval is set to 900 seconds. Connectivity Services Director indexes the device inventory data periodically to enable users to perform efficient searches. |
Pause indexing during device import | Select this check box to stop indexing while devices are imported into Connectivity Services Director. If you are running short of system memory, selecting this option can help save some memory and speed up the discovery and import of new devices. |
Topology (accessible from the Modify Connectivity Services Director Settings page in the Administration workspace of the Junos Space Platform GUI) | |
Retention period for Deleted Link days | Move the slider right or left to specify a retention period for the deleted links in Topology. You can also disable the retention of deleted links by moving the slider to the extreme left to denote Never. You can define a maximum of 365 days for deleted links to be maintained in Topology View. |