General FAQs
Answers to the questions customers ask most about IZO™+ Multi Cloud Connect, across the service models, ordering, changes, billing and support. Where a question needs a longer answer, it links to the page that covers it in full.
Service models
How many service models are there?
Two: IZO™+ Multi Cloud Connect Direct, which uses a private MPLS underlay, and IZO™+ Multi Cloud Connect Flex, which uses an Internet underlay (and can also run over an MPLS underlay).
Other Models are variations of these models.
Which clouds are supported?
The major providers, each through its own native connectivity service, reached over IZO™+ Multi Cloud Connect. See the per-cloud section for the specifics of each.
Can I connect one cloud to another?
Yes. A cloud-to-cloud design involving Tata Cloud Router (TCR), joins cloud connections on the Tata Communications side; each cloud connection is still created in its own cloud console.
Ordering and prerequisites
What do I need before I order?
A validated legal entity, the sites to connect, and the mandatory identifier for each cloud: AWS an account ID plus remote ASN; Azure a service key; Google Cloud a pairing key; Oracle a virtual circuit OCID; IBM an account ID.
Single or dual connection?
AWS and Google Cloud offer single or dual; Azure is always dual. Selecting a port as dual auto-creates the primary and secondary using the same key, so you do not create the secondary yourself.
Which peering type should I choose?
Public peering to reach public-IP resources, private peering for private-subnet resources, and a transit or combined option to reach both over one link. The exact options vary by cloud.
Changes and lifecycle
When can I change a service?
Once it is Active. Changes (including bandwidth) are raised as MACD change requests; a service that is not yet Active cannot be changed. See Bandwidth Changes.
What does each service state mean?
See the Provisioning Order and Service Status Reference and the operational view in Connection Lifecycle.
What happens if provisioning or termination fails?
Both exception states are recovered manually by Tata Communications; no customer action is needed. See Error Code Reference.
Billing
When does billing start?
When the service becomes Active. A Provisioned service is configured but not yet billing.
I terminated my service but the cloud provider is still charging me. Why?
Terminating in TCx stops Tata Communications billing but does not delete the cloud-side hosted connection, virtual circuit or gateway. Delete those in the cloud console. See Service Deletion.
Where do I find invoices, or query a charge?
In the Billing & Invoice module; raise a billing ticket to query a charge. See Billing and Invoices.
Support and responsibilities
How do I raise a problem or a change?
From Support & Maintenance or from the service in Inventory: an incident for a fault, a service request for a request, a change request for a change. Nominate the contacts who should receive updates.
Who fixes what?
Tata Communications configures and operates the connectivity and fixes a service that fails despite correct parameters. The customer supplies correct parameters, performs all cloud-side configuration, and creates and deletes cloud-side resources. An incorrect or non-existent parameter is the customer’s to correct.
How do I monitor my service?
From the TCx reporting workspace: live dashboards, per-connection At a glance, and the trend, top N and advanced reports. See Monitoring Dashboards.