<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Connection Troubleshooting

Connection problems on IZO™+ Multi Cloud Connect are worked from the bottom up: is the link physically up, are the VLAN tags consistent end to end, and were the correct cloud-side keys or account identifiers used. Get these right and BGP and traffic follow. 

Link down

  • Check the connection state in Inventory and reachability on the Dashboard. A link that never came up may still be in delivery: confirm the service has reached Active.

  • For a link that was up and dropped, note the time and check the consolidated underlay report for a coinciding underlay event, then raise an incident with the timestamp.

  • A last-mile or access-port fault on the customer premises is the customer’s to resolve; the Tata Communications side is Tata Communications’ to resolve.

VLAN or tag mismatch

IZO™+ Multi Cloud Connect delivers a logical connection over a shared cloud-facing port, identified by service tags. If the connection is up but no traffic passes:

  • Confirm the VLAN or tag configured on your side matches what was provisioned for the service.

  • On Azure, the inner tag (C-tag) is fixed by peering type: private peering uses 113 and Microsoft peering uses 115. Confirm the peering matches the intended type.

  • Confirm the cloud-side virtual circuit is bound to the same tag or VLAN.

Authentication and key failures

Each cloud requires a specific identifier or key, supplied by the customer and accepted on the cloud side. A wrong or unaccepted value stops the connection from coming up:

Cloud

Mandatory identifier

AWS

Account ID (created by the customer) plus remote ASN

Azure

Service key

Google Cloud

Pairing key

Oracle (OCI)

Virtual circuit OCID

IBM Cloud

Account ID

  • Confirm the value entered at ordering matches the one in the cloud console, with no transcription error.

  • Confirm the hosted connection or virtual circuit has actually been accepted on the cloud side; until it is, the connection will not establish.

  • For a dual connection, selecting the port as dual auto-creates the primary and secondary using the same key, so you do not create the secondary manually; a manually duplicated key is a common cause of failure. 

What’s on the cloud side

The hosted connection or virtual circuit, its tag binding and its acceptance are configured in the cloud provider’s console. This page covers the Tata Communications side; for the cloud-side connection request, keys and acceptance, see the relevant per-cloud section. 

Related pages