Service Order States and Service States Overview
Service provisioners create service orders which are requests to provision a service, validate a service, or decommission a service. The service order for provisioning a service defines all the service attributes.
Service Order States
Before a service order can affect a service, it must transition through several states as shown in Figure 1.
When the service provisioner has created the service order, but has not yet attempted to deploy it or schedule it for deployment, the service order is in the Draft state (also, formerly, called Requested state).
After the service provisioner has scheduled the service order for deployment, the service order transitions to the Scheduled state. If the service provisioner schedules the service order for immediate deployment, then the service order will be in the Scheduled state only briefly. However, if the service provisioner has scheduled a later deployment, the service order could be in this state for several hours or days.
When a scheduled service order reaches its time for deployment, it transitions to the transitory In Progress state. From this state, the Junos Space software attempts to deploy the service. Successful deployment transitions the service order to the Completed state.
If the Junos Space software cannot deploy the service because of invalid information in the service order itself, the service order enters the Invalid state. The service provisioner must resolve the issues that cause the failure before re-creating the service order and rescheduling it for deployment.
If the device is down or the Junos Space software is unable to push the service configuration to the device, the service order transitions to the Failed Deploy state. A network operator might need to resolve the problem before the service provisioner reschedules the service order.
After you disable a service order to deactivate the configuration settings on devices mapped to the service, you might require the service settings to be reenabled after you have modified the service parameters, either directly on the device or using the Connectivity Services Director application. In such a case, you can use the reactivation functionality to revive and activate the service properties on devices. To disable a service, the service must not contain any pending or uncommitted changes. Also, the service must be in the Deactivated state. By disabling a service, the traffic processing for the traversed packets is impacted.
In certain network topologies, you might require a service-related settings to be disabled for a certain period to perform troubleshooting or modification to the traffic-handling method, and you might want to reactivate a disabled service later when you have completed network maintenance and analysis work. In such a case, it might be beneficial to use the deactivation functionality for a service order. When you disable a service order, the configuration attributes associated with such a service order are deactivated and commented out in the device settings. The deactivated service is propagated to the devices associated with the service order. To disable a service, the service must not contain any pending or uncommitted changes. Also, the service must be in the Deployed or Re-Activated state.
When you cancel a job, the service order may not fail, but changes the service order state to Scheduled. When the job state is In Progress and until the device responds, the service order state is Scheduled. When the job is Cancelled, the job state becomes Cancelled and the service order state is Scheduled. As a result, the service order cannot be deleted or edited. However, you can move the service order state to Draft by right-clicking any service order or by clicking Actions at the header of the grid and selecting Cancel Order option. The Cancel Order option is enabled or disabled, depending on the state of the service order. This option is enabled only when the service order state is Scheduled and the job state is Cancelled while it is disabled for all the other service order states. When the state of the service order is Draft, you can modify and deploy or delete the service order.
The Deployed-Active or Active state denotes a service that has been deployed and is in an active state (enabled). The Deployed-Inactive or Inactive state denotes a service that has been deployed and is in a deactivated state (disabled). The Deployment-Pending or Pending state denotes a service for which deployment of the service to a device is pending to be performed.
A service is created when a service order to provision a service reaches the Completed state.
If a service exists, it is in the Deployed state. If a new service fails to deploy, the service does not exist.
If an attempt to modify a service fails, the service enters the Fail Deploy state. When a service is in the Fail Deploy state, you can attempt to redeploy it, or you can delete it.
The service also has an audit state of Up or Down, depending on whether the service passed or failed functional audit.
If you modify a service order and successfully redeploy the service, the modified service will operate according to the updated configuration.