Connection Lifecycle
An IZO™+ Multi Cloud Connect connection moves through a defined set of states from order to termination. The authoritative status list and how to track an order are covered in the Provisioning chapter; this page looks at the lifecycle from an operations point of view, what you can do at each stage once a service is live, and where each action is documented.
Where the lifecycle is defined
The order journey and the full list of statuses, from In progress and Under Provisioning through Provisioned, Active, Termination In Progress and Terminated, together with the two manual-recovery states (Provisioning Failed and Termination API Failure), are documented once in the Provisioning chapter. Rather than repeat them here, this page cross-references them:
|
For this |
See |
|
The full list of order and service statuses and what each means |
|
|
How to place and track an order, and where tracking takes you in inventory |
The operational stages
From an operations standpoint the lifecycle has three working phases:
|
Phase |
State(s) |
What operations does |
|
Delivery |
In progress to Provisioned |
Supply correct parameters and track delivery. No monitoring or changes yet; billing has not started. |
|
In service |
Active |
The working state. Monitor and report on the connection and raise MACD changes (for example a bandwidth uplift). Billing has started. |
|
Retirement |
Termination In Progress to Terminated |
Raise the termination, then complete the cloud-side cleanup. |
Active is the only state in which changes can be made. MACD (Move, Add, Change, Delete) actions, such as a bandwidth change, are always raised against an Active service; there is no separate “billing” state, since a connection being Active is what signals that billing has begun.
What operations owns at each stage
Tata Communications configures and operates the connectivity on its infrastructure and the TCx portal, and fixes a service that fails despite correct parameters. You are responsible for supplying correct parameters, for all cloud-side configuration (accepting the hosted connection, BGP and the service or pairing key), for creating and later deleting cloud-side resources, and for raising a new order or MACD for any change. A correct parameter that still fails on the service is Tata Communications’ to fix; an incorrect or non-existent parameter is the customer’s to correct.
Once a service is Active, day-to-day operations are covered by the rest of this chapter: watch it on the monitoring dashboards, change its bandwidth through Bandwidth Changes, and retire it through Service Deletion.