Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Force-Deploying a Service


When a service fails a configuration audit because configuration changes on a PE device do not match the configuration required for the service, you can force-deploy the service to push the configuration to the device.

Force deployment pushes the same configuration to the device that was pushed during the deployment of the service, thus allowing the operator to recover from a state in which the configuration on the device was lost or changed out-of-band.

The validation before generating the configuration for a force-deployed service order will be performed against the current configuration on the device and the configuration is not pushed if the validation fails. If the forced deployment is unable to push the configuration again, then you might need to manually configure the device.

This procedure forces deployment of a service on the network.

You cannot force-deploy an invalid service order.

To schedule a service for forced deployment:

  1. In the Network Activate task pane, select Service Provisioning > Manage Services.
  2. In the Manage Services page, select the service you want to force deploy.
  3. Open the Actions menu and click Force Deploy Service.

    The Schedule Force Deployment window appears.

  4. To deploy the service immediately, select Force deploy now, and click OK .

    To deploy the service at a later time, select Force deploy later, select a date and time for deployment, then click OK.

    The time field specifies the time kept by the server, but in the time zone of the client.

    After scheduling the service order for deployment, the provisioning software begins validating the service order.

  5. Use the Jobs workspace to monitor the outcome of the forced deployment. See Viewing Jobs in the Junos Space Network Application Platform User Guide for details about the Jobs workspace.