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:
- Select Service View from the View Selector.
The workspaces that are applicable to routing and tunnel services
are displayed.
- From the Junos Space user interface, click the Deploy icon in the Connectivity Services Director banner. The functionalities
that you can configure in this mode are displayed in the task pane.
- From the Service View pane, which is the left pane in
the window, click the plus sign (+) next to Network Services to expand
the tree and display the different service types that you can configure.
- Click the plus sign (+) beside Tunnel to view services
based on protocols, and expand the LSPs tree to select
an LSP service.
- From the task pane, select Service Provisioning >
Manage LSP. The top part of the right pane displays the Manage
LSP Network Services page, with the table of services, and the bottom
part of the right pane displays the Manage Service Deployment page,
with the table of service orders.
- From the Manage LSP Network Services page, select the
check box next to the service you want to forcibly deploy.
The top pane displays information about the services that have
been previously created, such as the name of the service, the functional
audit status, the performance management status, and the deployment
state of the service. You can modify the properties of the service,
conduct a functional or configuration audit, force-deploy or deactivate
the service, and view alarms associated with a particular service
order for debugging and corrective action. Services can be in one
of the following service states:
Completed—The service order has been successfully
deployed.
Scheduled for deployment—The service provisioner
has scheduled the service order for deployment.
Deployment Failed—An attempted service deployment
was not successfully completed or failed an audit.
In Progress—The Connectivity Services Director application
is in the process of deploying the service.
Requested—The service provisioner has created the
service order, but has not yet attempted to deploy it or schedule
it for deployment.
Invalid—The service order is not valid.
- Open the Actions menu and click Force
Deploy Service.
The Schedule Force Deployment window appears.
- 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.
- Use the Jobs workspace to monitor the outcome of the forced
deployment.
