NSP's service management views provide visibility of multiple service and service tunnel states to assist with assessing the current condition of a given resource and diagnosing any potential problems. The states that can be seen, and their associated values, are described below.

Note: The values described below are limited to those that are supported by the Nokia-provided, product intents. Depending on your specific system configuration, some additional state values may be visible to you.

Life Cycle State indicates the current status of the service or tunnel as it transitions from the planning phase to the deployment phase and beyond. The following states may be observed:

• Saved

  During the service or tunnel creation process, a user can save their initial configurations within service management (an associated intent instance is created). The entity name will be reserved, and the user will be able to resume creation when desired. Entities in a Saved state can be deleted, or modified and saved again. When configuration is complete, Saved entities can transition to either a Planned or Deployed state.

• Planned

  Newly-created services or tunnels, or services or tunnels in a Saved state, can transition to a Planned state. In this state, an associated intent instance is created in NSP's Network Intents function, but the entity is not deployed to the network. While in a Planned state, the entity's resources are reserved, and therefore cannot be used by any other entity. Entities in a Planned state can be deleted (in addition to deleting the entity from service management, this also deletes the intent instance and removes the resource reservations), or modified and kept in a Planned state. When configuration is complete, Planned entities can transition to a Deployed state.

• Deployed

  Services or tunnels in a Planned state can transition to a Deployed State. In this state, the desired configuration is sent down to the network and synchronized. Entities in a Deployed state must transition to a Removed state before being deleted. If a Deployed entity is modified, it will no longer be aligned with the associated intent instance. At this point, the user can either save their changes (which will place the entity in the Deployed-Modified state until network synchronization occurs), or redeploy the entity (which keeps the entity in the Deployed state by triggering network synchronization).

• Deployed-modified

  Services or tunnels in a Deployed-modified state have been modified by the user, but are not synchronized to the network. Entities in a Deployed-modified state must transition to a Removed state before being deleted. Deployed-modified entities can be further modified and saved again, (which keeps the entity in the Deployed-Modified state until network synchronization occurs), or redeployed (which transitions the entity to the Deployed state by triggering network synchronization).

• Removed

  Services or tunnels in a Removed state can be deleted. In this state, the entity is removed from the network, but its resources remain reserved and its associated intent instance continues to exist. Removed entities can be deployed/redeployed (which transitions the entity to the Deployed state) or modified and saved (which keeps the entity in the Removed state).

  NOTE: Services in a Removed state will display an Operational State of 'Unknown'.

• Planned-failed

  Newly-created services or tunnels, or services or tunnels in a Saved state, can transition to a Planned state. When this transition fails, these resources are assigned the Planned-failed state.

• Deployed-modified-failed

  Deployed-modified services or tunnels can be further modified and saved again, or they can be transitioned to Deployed. When this transition fail, these resources are assigned the Deployed-modified-failed state.

• Pull-from-network-saved

  A brownfield service is associated to a template to make it intent-aware. As the association is triggered, the service moves through this transitory state.

• Pull-from-network-failed

  A brownfield service is associated to a template to make it intent-aware. During the association, if the pull from network does not succeed, the service is assigned this state.

Alignment State specifies the alignment state of the service or tunnel. The following states may be observed:

• Aligned

  This state indicates that the service or tunnel is aligned with the network.

• Misaligned

  This state indicates that the service or tunnel is not aligned with the network. The intent instance and the network copy are not aligned.

Admin State indicates the administrative state of the service or tunnel. The following states may be observed:

• Unknown

  The administrative state of the resource is not known.

• Unlocked

  The resource is administratively 'up' and ready to perform services.

• Locked

  The resource is administratively 'down' and is prohibited from performing services.

Operational State indicates whether the service or tunnel is currently operable. The following states may be observed:

• Unknown

  The operational state of the resource is not known.

• Enabled

  The resource is operable and available for use.

• Disabled

  The resource is inoperable and unable to provide services.

Deployer State specifies the state of the deployer. The following states may be observed:

• Running

  The deployer is in progress.

• Success

  The deployer succeeded.

• Failed

  The deployer failed.

Job State indicates the state of the job. The following states may be observed:

• New

  The job is new, and has not yet been processed.

• Running

  The job is queued, or in progress.

• Success

  The job has been processed, and succeeded.

• Failed

  The job has been processed, and failed.

• Cancelled

  The job was cancelled.