Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Modifying Application Settings

    In Network Management platform, you can modify the configuration settings for the Network Activate application.

    To modify the configuration settings of Network Activate, perform the following steps:

    1. 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.

    2. Right-click Network Activate or Cross Provisioning Platform and select Modify Applications Settings.

      The Modify Application Settings page that appears displays a list of the parameters that can be modified.

    3. Click any parameter to modify it.

      Note: You cannot modify the application settings if another user is currently modifying them.

    4. Click Modify to save the changes that you made in the respective application or click Cancel to retain the original settings.

    To understand the parameters of the Network Activate or Cross Provisioning Platform application settings, refer to Table 1.

    Table 1: Parameters in Network Activate Application Settings

    FIELDS

    DESCRIPTION

    DEPLOYMENT

    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 Network Activate 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 vlanmaps for flexible tagged services

    Select this check box to use vlanmaps for flexible tagged services, instead of normalization. VLAN mapping refers to the swapping of the incoming VLAN ID to a new VLAN ID.

    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.

    UI

    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 P2P 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.

    MONITORING

    Perform Monitoring on Failed Functional Audit

    Select this check box to perform monitoring if the functional audit fails.

    Pseudo-wire 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.

    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

    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.

    OSSCONFIGPARAMETERS

    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

    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.

    Wait for Device Sync Before Releasing Resource

    Select this check box to wait for the device synchronization before resources are released. To revert the decommissioning to the normal behavior, clear this check box.

    Modified: 2017-02-02